How To Install Debian On Your Zaurus (obsolete)

[zecrazytux]

I'll drink a large rum to zecrazytux, I thought I might need to redo the install....  Saved!

huhu, join us now and share the rhuuuum, you'll be freeee, hacker...


Does anybody ever tried to use kazehakase ? i got a segfault :-(


I still have problems with the keymap: i can't get a right click, even when using keylaunch :-(
The ctrl and alt keys are well recognized (as i can do a ctrl alt arrow to switch desktops or alt tab to switch windows)

if it can helps:

- for X:

- i took xserver-kdrive-fbdev from angstrom
- make sure /etc/X11/X is a symbolic link to /usr/bin/Xfbdev (or use the .xserverrc config file to specify wich xserver should be used)
- on SID, remove the file /etc/X11/xorg.conf, it works great without  
- i used tslib (and other ts packages like tslib-conf) from angstrom:
add "expor TSLIB_TSDEVICE=/dev/input/event1" to your /etc/rc.local script
- rmmod mousedev (i haven't looked how to disable the loading of this module at boot, yet)

and as explain everywhere, just write a tiny .xsession configuration file to start your graphical session with startx


so i now need to fix the right click and to configure openbox and fbpanel
if somebody is interested i certainly could release a sid quite correctly configured rootfs.

[Chero]

Chero, test this if you can't wait (actually because I can't wait to see your result ...  ).

There are three little extra steps involved:
1. Add these extra files:
-- Download these essential utilities to the SD:
  http://armel-debs.applieddata.net/debian/p...bs-65_armel.deb
  http://armel-debs.applieddata.net/debian/p...bs-65_armel.deb
  http://kfreebsd-gnu.debian.net/debian/pool...2-8.1_armel.deb
  http://kfreebsd-gnu.debian.net/debian/pool...9p6-1_armel.deb
-- Put these attachments to the SD too:
 [ Invalid Attachment ]   [ Invalid Attachment ]

2. Follow the steps as described, and after extracting the rootfs and the kernel modules, extract the zaurus-hardware-eabi thingie also.

3. After the first login:
-- First install those few armel packages.
-- Then run the afterinstall.sh (remove the .txt extension).

the first two links are down, but they are on kfreebsd as well - first have to eat now - will continue this afternoon

i had problems with this repo two days ago when i installed my debian for my c1000. There is an other repo (duplicate or an other domain name):
http://ftp.gnuab.org/debian

I noticed it is not a good idea to mix repo-s. I was mixing applieddata and kfreebsg-gnu, but it gave me lots of dependency-errors. When switching to ftp.easynet.be for everything (main and unreleased) it all installs smoothly :
- gnumeric
- evolution
- dates - contacts - tasks
- homebank
- wxwidgets
- leafpad
- icewm-experimental - xfce - xfce-goodies
- ...

[zecrazytux]

I noticed it is not a good idea to mix repo-s. I was mixing applieddata and kfreebsg-gnu

kfreebsd's binaries works great with a linux kernel ?

well, gnuab.org is the official armel debian repository, and it seems the packages from applieddata and gnuab are exactly the same (look the versions, date and time they where uploaded)

To me, that's only a question of qos
gnuab is always up, whereas i had problems with applied going down

[ZDevil]

I still have problems with the keymap: i can't get a right click, even when using keylaunch :-(
The ctrl and alt keys are well recognized (as i can do a ctrl alt arrow to switch desktops or alt tab to switch windows)

if it can helps:

- for X:

- i took xserver-kdrive-fbdev from angstrom
- make sure /etc/X11/X is a symbolic link to /usr/bin/Xfbdev (or use the .xserverrc config file to specify wich xserver should be used)
- on SID, remove the file /etc/X11/xorg.conf, it works great without  
- i used tslib (and other ts packages like tslib-conf) from angstrom:
add "expor TSLIB_TSDEVICE=/dev/input/event1" to your /etc/rc.local script
- rmmod mousedev (i haven't looked how to disable the loading of this module at boot, yet)

and as explain everywhere, just write a tiny .xsession configuration file to start your graphical session with startx

so i now need to fix the right click and to configure openbox and fbpanel
if somebody is interested i certainly could release a sid quite correctly configured rootfs.

That's a very instructive post. Thanks!  
1) No right-click: I also discovered this using 2.6.23.1 yonggun (even with keylaunch). 2or0, any hint?

2) X and touchscreen: My original zaurus-hardware-eabi tarball had all these settings (.xsession, .xserverrc, touchscreen settings etc). 2or0 told me his repackaged Angstrom debs can manage all these. Perhaps I need to extract the repackaged Angstrom debs in the new tarball and see if there is anything to add to. What do you think, 2or0?
2or0's xserver package is already using Angstrom's kdrive.
Sidenote: It seems to me that touchscreen pointer can use /dev/input/ts0, /dev/input/event1 or /dev/input/touchscreen0, as long the ts modules are in place (under /usr/lib/ts).
I would export  TSLIB_TSDEVICE in ~/.profile, but it's just the same.

3) Things to add to the after installation scripts:
-- rm /usr/bin/X && ln -s xfbdev /usr/bin/X
-- rm /etc/X11/xorg.conf
-- rmmod /dev/mousedev

[ZDevil]

I found an issue with the x-yonggun package:

It's very nice to have the xmodmap from pdaXrom (under /etc/X11/kb).
And the settings use xbindkey to map L/M/R mouse buttons to XF86LaunchA, XF86LaunchB, XF86LaunchC (Calendar, Address, Mail) respectively.
However, these three keys don't seem to work.
In xev, they don't seem to map to any keycode or keysym.

I also noticed that the basic settings in .xsession are handled in the included .xinitrc, which is nice. (I feel home more with this as I used to pdaXrom a lot  ).

Interestingly the five silkscreen keys do show something in xev (from top to bottom):
87 = F15
89 = F16
84 = F17
79 = F18
81 = F19

So does that mean we can make use of these mappings also?  (If positive then I feel even closer to pdaXrom ... )

[2or0]

I still have problems with the keymap: i can't get a right click, even when using keylaunch :-(
The ctrl and alt keys are well recognized (as i can do a ctrl alt arrow to switch desktops or alt tab to switch windows)

if it can helps:

- for X:

- i took xserver-kdrive-fbdev from angstrom
- make sure /etc/X11/X is a symbolic link to /usr/bin/Xfbdev (or use the .xserverrc config file to specify wich xserver should be used)
- on SID, remove the file /etc/X11/xorg.conf, it works great without  
- i used tslib (and other ts packages like tslib-conf) from angstrom:
add "expor TSLIB_TSDEVICE=/dev/input/event1" to your /etc/rc.local script
- rmmod mousedev (i haven't looked how to disable the loading of this module at boot, yet)

and as explain everywhere, just write a tiny .xsession configuration file to start your graphical session with startx

so i now need to fix the right click and to configure openbox and fbpanel
if somebody is interested i certainly could release a sid quite correctly configured rootfs.

That's a very instructive post. Thanks!  
1) No right-click: I also discovered this using 2.6.23.1 yonggun (even with keylaunch). 2or0, any hint?

2) X and touchscreen: My original zaurus-hardware-eabi tarball had all these settings (.xsession, .xserverrc, touchscreen settings etc). 2or0 told me his repackaged Angstrom debs can manage all these. Perhaps I need to extract the repackaged Angstrom debs in the new tarball and see if there is anything to add to. What do you think, 2or0?
2or0's xserver package is already using Angstrom's kdrive.
Sidenote: It seems to me that touchscreen pointer can use /dev/input/ts0, /dev/input/event1 or /dev/input/touchscreen0, as long the ts modules are in place (under /usr/lib/ts).
I would export  TSLIB_TSDEVICE in ~/.profile, but it's just the same.

3) Things to add to the after installation scripts:
-- rm /usr/bin/X && ln -s xfbdev /usr/bin/X
-- rm /etc/X11/xorg.conf
-- rmmod /dev/mousedev

1) First, I should mention that xserver-kdrive-fbdev is not from angstrom. Look at this thread: https://www.oesf.org/forum/index.php?s=&...st&p=163836
When I used angstrom fbdev, mouse keys did not work but thanks to svs57 I could use mouse keys.

2) I don't think that my setting will work on angstrom kernel. So when I repackaged angstrom ones, I had to carefully take a look the script and to add settings for my kernel. For example, TSLIB_TSDEVICE = /dev/input/ts0 in mine but /dev/input/touchscreen0 in angstrom.

3) In my package, xserver loads Xfbdev instead of X. You don't need make a link.

[2or0]

In xev, they don't seem to map to any keycode or keysym.

Try it again without xbindkeys in the memory or remap the keys using xbindkeys-config.

[ZDevil]

Great. I will play with the keys on train on the way home this evening.  
So it seems that the stuff after install tarball actually does not 100% work for the Angstrom kernel, am I right?
If that's true, then perhaps it is a good idea to indicate this explicitly.
Could you give me more details of the (in)compatibility between the after install tarball (which are targeted at the yonggun kernel and EABI rootfs) and the Angstrom kernels?

Then maybe in those cases the users need to use the Angstrom stuff (xfbdev, ts).

And the upcoming Poky kernels (by cortez) may add more variables to this debian game...

Up to now I feel most comfortable with the yonggun kernel. Thanks again!  

[zecrazytux]

Great. I will play with the keys on train on the way home this evening.  
So it seems that the stuff after install tarball actually does not 100% work for the Angstrom kernel, am I right?
If that's true, then perhaps it is a good idea to indicate this explicitly.
Could you give me more details of the (in)compatibility between the after install tarball (which are targeted at the yonggun kernel and EABI rootfs) and the Angstrom kernels?

Then maybe in those cases the users need to use the Angstrom stuff (xfbdev, ts).

And the upcoming Poky kernels (by cortez) may add more variables to this debian game...

Up to now I feel most comfortable with the yonggun kernel. Thanks again!  

i'm sayin' shit... i run *poky*'s 2.6.21 kernel ! (not angstrom's one)
can't get a right click, that's boring

[jpmatrix]

i've sound working ! .... but only on headphones...... when i plug/unplug it seems something is happening but the zaurus speaker is dead quite ...... any idea.?

[ZDevil]

@jpmatrix: have you tried alsamixer? It is installed if you have run 2nd-cfg.sh. Use the [M] key to mute/unmute, and the arrow Up/Down key to turn values up and down.
I am curious to see how far the scripts can go since you are using the Angstrom kernel (2.6.23).
If they don't do much then I have to edit the instructions again and limit the after install tarball to yonggun's kernel only, leaving the Angstrom settings to jpmatrix's post and perhaps also the older zaurus-hardware-eabi tarball on page 3. I was so naive to assume that things just work in the same way for both the Angstrom and yonggun kernels...

[jpmatrix]

@jpmatrix: have you tried alsamixer? It is installed if you have run 2nd-cfg.sh. Use the [M] key to mute/unmute, and the arrow Up/Down key to turn values up and down.
I am curious to see how far the scripts can go since you are using the Angstrom kernel (2.6.23).
If they don't do much then I have to edit the instructions again and limit the after install tarball to yonggun's kernel only, leaving the Angstrom settings to jpmatrix's post and perhaps also the older zaurus-hardware-eabi tarball on page 3. I was so naive to assume that things just work in the same way for both the Angstrom and yonggun kernels...

that's strange because i had to manually apt-get install alsa-utils in order to have alsamixer. but anyway that didn't help xmms to produce sound on the zaurus speaker...
another issue for the 2.6.23 (i think) : my belkin BT CF card no longer works    lots of error messages as i hciattach it....

[ZDevil]

Thanks.
Alright, then I will take out the after installation notes from the Angstrom kernel + EABI system, because obviously it seems to bring more confusions than without it. And i will make it clear that the after installation tarball is for yonggun's kernel only.

[jpmatrix]

Thanks.
Alright, then I will take out the after installation notes from the Angstrom kernel + EABI system, because obviously it seems to bring more confusions than without it. And i will make it clear that the after installation tarball is for yonggun's kernel only.

perhaps it depends on the 0827 rootfs i used too... by the way i noticed alsa-oss didn't get installed too...
you were right perhaps i should launch 2nd-cfg script again to see if more packages get installed.ok i try !

[ZDevil]

Not only this, I agree with 2or0 that some of the packages and the scripts in the after installation tarball (now 1.1  ) are not suitable for the Angstrom kernels. And his X server is no longer Angstrom's as well. So YMMV.
Sorry for the confusion caused so far, because my 3200 is running the yonggun kernel so there is no way for me to check how the same things may work for the Angstrom kernel. I just started out naively presuming that it's the same, but that seems not to be the case.
If it turns out that the script works somehow or need some modification, please do!
Posting to the OESF wiki now ...