A Clean, Fresh, Configured Eabi Rootfs Tarball

[jpmatrix]

so what about the new rootfs ? i'd like to try before leaving the zaurus scene

[apink]

My spectrum24 network-cf didn't work (missing firmware ?), so i configured usb-networking. Runnning apt-get update now  

I am trying to get my usb networking going also, but am not as successful as you were.  I have tried several different /etc/network/interfaces options but do not know what is going on.  I have a usb network adapter and a basic home network.  My network automatically hands out ip addresses so I thought

Code: [Select]

auto eth0
iface eth0 inet dhcp
would do it.  No luck.  How did you configure your usb-networking? Any pointers will be appreciated.

Edit:  fixed.  Newbie at the controls.

Code: [Select]

allow-hotplug eth0
iface ith0 inet dhcp is what worked in /etc/network/interfaces.
I also have to do

Code: [Select]

echo -n 1 >/sys/bus/usb/devices/1-2/bConfigurationValue to get the usb-ethernet adapter working because debian thinks there is not enough power to run the device.
https://www.oesf.org/forum/index.php?showto...amp;hl=pegasus#
I also had eth4 showing up for some reason when doing ifconfig -a.  This seemed to be causing some MAC address collision or some such, according to this post over at ubuntu:
http://ubuntuforums.org/showthread.php?t=221768
I just rebooted and things seemed to clear up.

[kkazakov13]

so what about the new rootfs ? i'd like to try before leaving the zaurus scene

Just leave ... why do you care? Why is your effort about Z still high after you know at 100% that you sell it and don't use it ?

[bunkford]

Is there anyway to make this a hdImage.tgz so I can actually use this image? I can't seem to unzip the bz2 stuff for some reason to the microdrive of my 3200.

[ZDevil]

Is there anyway to make this a hdImage.tgz so I can actually use this image? I can't seem to unzip the bz2 stuff for some reason to the microdrive of my 3200.

What is the error? Are you trying to extract the tarball in uboot emergency mode?
The easier way is to use the Sharp bootloader kernels (new yonggun/poky/angstrom).
Or try extracting the rootfs tarball in another ROM/on another computer first.

[gsgmx]

regarding the updated install desription - i'm still in the cacko 1.23 "user group" but very eager to try debian.

i don't understand:

-- added yonggun kernel modules: 2.6.22.9, 2.6.23.1, 2.6.23.3 (so users just need to flash the kernel)
....
I. Get the latest yonggun kernel here: http://yonggun.tistory.com/66

how these two fit together, because the newest kernel is a 2.6.24 kernel whose modules are not included.

Do i understand something wong?


George

[ZDevil]

regarding the updated install desription - i'm still in the cacko 1.23 "user group" but very eager to try debian.

i don't understand:

-- added yonggun kernel modules: 2.6.22.9, 2.6.23.1, 2.6.23.3 (so users just need to flash the kernel)
....
I. Get the latest yonggun kernel here: http://yonggun.tistory.com/66

how these two fit together, because the newest kernel is a 2.6.24 kernel whose modules are not included.

Do i understand something wong?
George

It's because the rootfs tarball was made before the release of the yonggun kernel 2.6.24. That's why i added in Step 2 to extract the 2.6.24 kernel modules on top of the rootfs tarball.
The 2.6.24 kernel modules will be included in the next rootfs tarball, while I would keep the old ones there for those who want to experiment things.
There is a list of things to fine-tune/improve/modify in the current rootfs. But it is still working.

[AmigaFalcon]

Hi,

I have just installed Yonggun's  kernel.img.2.6.24-yonggun-hda1 kernel and modules-2.6.24-yonggun.tar.gz modules....aswell as Zdevil's zaurus_eabi_rootfs_071201.tar.bz2 Rootfs onto my internal CF drive.

Everything seems to work ok so far, I just have a couple of questions:

1) Should such things as my SD card "automount" when inserted? With my installation, when I insert an SD card it is not automatically detected. So, is this normal for this installation?

2) Also, a few applications, such as XMMS and Dillio, etc are nowhere to be seen in the program launcher/taskbar. I have to execute these apps from the command line instead. Infact, very few apps (system file browsers, word processors, etc) are visible from the application launch menu - which is surprising considering how large the Rootfs is. I guess they are all hidden somewhere on the drive? Again, is this standard for this distro?

3) There are no app links setup on the desktop, no access to any GUI Filebrowser on desktop (or even in the app launcher) , etc unlike distros such as PdaXRom where everything is immediately accessible...

So, I just want to know if these things are normal or have I screwed up the installation somehow causing the configuration of these things not to work properly...

thanks for any info...

[ArchiMark]

Is there anyway to make this a hdImage.tgz so I can actually use this image? I can't seem to unzip the bz2 stuff for some reason to the microdrive of my 3200.

What is the error? Are you trying to extract the tarball in uboot emergency mode?
The easier way is to use the Sharp bootloader kernels (new yonggun/poky/angstrom).
Or try extracting the rootfs tarball in another ROM/on another computer first.

ZDevil,

I had the same problem today trying to decompress the bz2 file. When you boot in the emergency mode on the 3200 and login and then try to decompress with the 'tar -xjpf' option it returns an error message saying that it can't use or find the 'j' option...in other words, it doesn't have any bz2 decompress capability available.

Don't understand what you mean exactly by 'use the Sharp bootloader kernels (new yonggun/poky/angstrom)' ?

In the meantime, I am going to try and extract tarball on another computer now....

UPDATE: Here's what I'm getting so far during extraction...do these messages mean that I have problems with extracted files???

Code: [Select]

marks$ tar -xjpf zaurus.tar.bz2
tar: ./bin/uncompress: Cannot hard link to `./bin/gunzip': Operation not supported
tar: ./bin/bunzip2: Cannot hard link to `./bin/bzip2': Operation not supported
tar: ./bin/bzcat: Cannot hard link to `./bin/bzip2': Operation not supported
tar: ./bin/bzegrep: Cannot hard link to `./bin/bzgrep': Operation not supported
tar: ./bin/bzfgrep: Cannot hard link to `./bin/bzgrep': Operation not supported
tar: ./bin/bzless: Cannot hard link to `./bin/bzmore': Operation not supported
tar: ./bin/bzcmp: Cannot hard link to `./bin/bzdiff': Operation not supported
tar: ./dev/tty4: Cannot mknod: Operation not permitted
tar: ./dev/sndstat: Cannot mknod: Operation not permitted
tar: ./dev/ram14: Cannot mknod: Operation not permitted
tar: ./dev/loop5: Cannot mknod: Operation not permitted
tar: ./dev/tty2: Cannot mknod: Operation not permitted
tar: ./dev/full: Cannot mknod: Operation not permitted
tar: ./dev/midi02: Cannot mknod: Operation not permitted
tar: ./dev/audio1: Cannot mknod: Operation not permitted
tar: ./dev/ram7: Cannot mknod: Operation not permitted
tar: ./dev/ram6: Cannot mknod: Operation not permitted
tar: ./dev/rmidi0: Cannot mknod: Operation not permitted
tar: ./dev/smpte2: Cannot mknod: Operation not permitted
tar: ./dev/dsp2: Cannot mknod: Operation not permitted
tar: ./dev/urandom: Cannot mknod: Operation not permitted
tar: ./dev/midi00: Cannot mknod: Operation not permitted
tar: ./dev/mixer3: Cannot mknod: Operation not permitted
tar: ./dev/initctl: Cannot mkfifo: Invalid argument
tar: ./dev/midi01: Cannot mknod: Operation not permitted
tar: ./dev/tty9: Cannot mknod: Operation not permitted
tar: ./dev/agpgart: Cannot mknod: Operation not permitted
tar: ./dev/ram5: Cannot mknod: Operation not permitted
tar: ./dev/ptmx: Cannot mknod: Operation not permitted
tar: ./dev/midi03: Cannot mknod: Operation not permitted
tar: ./dev/ram16: Cannot mknod: Operation not permitted
tar: ./dev/dsp3: Cannot mknod: Operation not permitted
tar: ./dev/ram3: Cannot mknod: Operation not permitted
tar: ./dev/midi0: Cannot mknod: Operation not permitted
tar: ./dev/audio: Cannot mknod: Operation not permitted
tar: ./dev/mixer: Cannot mknod: Operation not permitted
tar: ./dev/tty8: Cannot mknod: Operation not permitted
tar: ./dev/ram8: Cannot mknod: Operation not permitted
tar: ./dev/loop3: Cannot mknod: Operation not permitted
tar: ./dev/audio3: Cannot mknod: Operation not permitted
tar: ./dev/ram0: Cannot mknod: Operation not permitted
tar: ./dev/ram15: Cannot mknod: Operation not permitted
tar: ./dev/loop0: Cannot mknod: Operation not permitted
tar: ./dev/mixer1: Cannot mknod: Operation not permitted
tar: ./dev/loop4: Cannot mknod: Operation not permitted
tar: ./dev/ram4: Cannot mknod: Operation not permitted
tar: ./dev/zero: Cannot mknod: Operation not permitted
tar: ./dev/mem: Cannot mknod: Operation not permitted
tar: ./dev/sequencer: Cannot mknod: Operation not permitted
tar: ./dev/smpte3: Cannot mknod: Operation not permitted
tar: ./dev/loop2: Cannot mknod: Operation not permitted
tar: ./dev/midi1: Cannot mknod: Operation not permitted
tar: ./dev/mpu401stat: Cannot mknod: Operation not permitted
tar: ./dev/tty1: Cannot mknod: Operation not permitted
tar: ./dev/ram12: Cannot mknod: Operation not permitted
tar: ./dev/tty: Cannot mknod: Operation not permitted
tar: ./dev/tty5: Cannot mknod: Operation not permitted
tar: ./dev/smpte0: Cannot mknod: Operation not permitted
tar: ./dev/tty6: Cannot mknod: Operation not permitted
tar: ./dev/mixer2: Cannot mknod: Operation not permitted
tar: ./dev/midi3: Cannot mknod: Operation not permitted
tar: ./dev/audioctl: Cannot mknod: Operation not permitted
tar: ./dev/ram1: Cannot mknod: Operation not permitted
tar: ./dev/null: Cannot mknod: Operation not permitted
tar: ./dev/loop6: Cannot mknod: Operation not permitted
tar: ./dev/dsp: Cannot mknod: Operation not permitted
tar: ./dev/ram11: Cannot mknod: Operation not permitted
tar: ./dev/loop7: Cannot mknod: Operation not permitted
tar: ./dev/rmidi1: Cannot mknod: Operation not permitted
tar: ./dev/console: Cannot mknod: Operation not permitted
tar: ./dev/dsp1: Cannot mknod: Operation not permitted
tar: ./dev/midi2: Cannot mknod: Operation not permitted
tar: ./dev/rmidi3: Cannot mknod: Operation not permitted
tar: ./dev/ram13: Cannot mknod: Operation not permitted
tar: ./dev/rmidi2: Cannot mknod: Operation not permitted
tar: ./dev/tty3: Cannot mknod: Operation not permitted
tar: ./dev/ram10: Cannot mknod: Operation not permitted
tar: ./dev/port: Cannot mknod: Operation not permitted
tar: ./dev/mpu401data: Cannot mknod: Operation not permitted
tar: ./dev/random: Cannot mknod: Operation not permitted
tar: ./dev/smpte1: Cannot mknod: Operation not permitted
tar: ./dev/audio2: Cannot mknod: Operation not permitted
tar: ./dev/kmem: Cannot mknod: Operation not permitted
tar: ./dev/ram2: Cannot mknod: Operation not permitted
tar: ./dev/loop1: Cannot mknod: Operation not permitted
tar: ./dev/ram9: Cannot mknod: Operation not permitted
tar: ./dev/tty7: Cannot mknod: Operation not permitted
tar: ./dev/tty0: Cannot mknod: Operation not permitted
tar: ./dev/xconsole: Cannot mkfifo: Invalid argument
tar: ./dev/fb0: Cannot mknod: Operation not permitted
tar: ./dev/fb1: Cannot mknod: Operation not permitted
tar: ./dev/fb2: Cannot mknod: Operation not permitted
tar: ./dev/fb3: Cannot mknod: Operation not permitted
tar: ./dev/fb4: Cannot mknod: Operation not permitted
tar: ./dev/fb5: Cannot mknod: Operation not permitted
tar: ./dev/fb6: Cannot mknod: Operation not permitted
tar: ./dev/fb7: Cannot mknod: Operation not permitted
tar: ./dev/apm_bios: Cannot mknod: Operation not permitted
tar: ./etc/X11/kb/Corgi/xmodmap_ru-phonetic: implausibly old time stamp 1969-12-31 16:00:00
tar: ./etc/X11/kb/Corgi/xmodmap_ru: implausibly old time stamp 1969-12-31 16:00:00
tar: ./etc/X11/kb/Corgi/xmodmap_us: implausibly old time stamp 1969-12-31 16:00:00
tar: ./etc/X11/kb/Tosa/xmodmap_ru: implausibly old time stamp 1969-12-31 16:00:00
tar: ./etc/X11/kb/Tosa/xmodmap_us: implausibly old time stamp 1969-12-31 16:00:00
tar: ./etc/X11/kb/Akita/xmodmap_ru-phonetic: implausibly old time stamp 1969-12-31 16:00:00
tar: ./etc/X11/kb/Akita/xmodmap_ru: implausibly old time stamp 1969-12-31 16:00:00

[ZDevil]

@ArchiMark:
Make sure that the partition containing the debian rootfs (the destination of the extraction) is ext3 formatted.
Extract the rootfs tarball in another environment/on another computer (as long as it can read ext3). The emergency linux mode has rather limited functionality.
Also do not extract the rootfs to a FAT partition.
By kernels using the Sharp bootloader, I mean those kernels which are flashed and boot using the original bootloader used in Sharp rom, Cacko rom, pdaXrom  (up to beta3), pdaXii, and Angstrom, i.e. no uboot is installed.

[ZDevil]

I have just installed Yonggun's  kernel.img.2.6.24-yonggun-hda1 kernel and modules-2.6.24-yonggun.tar.gz modules....aswell as Zdevil's zaurus_eabi_rootfs_071201.tar.bz2 Rootfs onto my internal CF drive.
Everything seems to work ok so far,

Glad to know that. I know Debian works because it just works on both my C860 and C3200.  

So, I just want to know if these things are normal or have I screwed up the installation somehow causing the configuration of these things not to work properly...

It seems to me that there is nothing messed up in your setup. What you need is just a few configurations. Here they are:

1) Should such things as my SD card "automount" when inserted? With my installation, when I insert an SD card it is not automatically detected. So, is this normal for this installation?

Just edit /etc/fstab and add an entry for mount SD card (/dev/mmcblk0p1) there.

2) Also, a few applications, such as XMMS and Dillio, etc are nowhere to be seen in the program launcher/taskbar. I have to execute these apps from the command line instead. Infact, very few apps (system file browsers, word processors, etc) are visible from the application launch menu - which is surprising considering how large the Rootfs is. I guess they are all hidden somewhere on the drive? Again, is this standard for this distro?

There are several solutions:
Solution 1: Edit "~/.icewm/menu" and add whatever you want there. A tedious way.
Solution 2: Install a program call "menu" and run "update-menus". But the result is less than satifactory as there are too many trivial folders and categories and duplicated entries.
Solution 3: Add "icewm-menu-gnome2" in ~/.icewm/menu . See http://myy.helia.fi/~karte/icewm.html for instructions.  But again I find the menu generated not so optimal.
Solution 4: Use my "icewm_meuntools" scriptpack which is a slightly modified and enhanced version of Meanie's tools in pdaXii.  Extract the tarball somewhere, then enter the extracted "icewm_menutools_0.1a" directory, and run "./install.sh" there. A few seconds later you'll see a new IceWM menu with program icons sorted, plus a few goodies.      [ Invalid Attachment ]

3) There are no app links setup on the desktop, no access to any GUI Filebrowser on desktop (or even in the app launcher) , etc unlike distros such as PdaXRom where everything is immediately accessible...

Again there are several solutions.
Solution 1: Use Rox desktop, just like in pdaXrom. See here for how to install it: http://www.debianhelp.co.uk/rox.htm
Solution 2: Use idesk, and it requires manual editing of the config file. Just "apt-get install idesk". See http://idesk.sourceforge.net/wiki/index.php/Main_Page for how to set up the menu file.
Solution 3: Use pcmanfm. Go to "Preferences > Desktop", then check "Show file icons on desktop". You can also set desktop wallpaper there (but I find it slower than using icewmbg directly). Also add "pcmanfm &" in .xinitrc, above the line "icewm-session".

[ZDevil]

Just to add:

From now on before the release of the next OOTB rootfs tarball, I will put things up in scriptpacks and post them in the forum every now and then.
The scriptpacks address (some of) the issues and questions raised about the present rootfs tarball and provide easy, and ideally painless and foolproof, solutions.

I think doing things this way is both easier for me to refine the present rootfs tarball, and existing users can keep track of the changes and choose to install them to their liking.

How's that?

[ArchiMark]

@ArchiMark:
Make sure that the partition containing the debian rootfs (the destination of the extraction) is ext3 formatted.
Extract the rootfs tarball in another environment/on another computer (as long as it can read ext3). The emergency linux mode has rather limited functionality.
Also do not extract the rootfs to a FAT partition.
By kernels using the Sharp bootloader, I mean those kernels which are flashed and boot using the original bootloader used in Sharp rom, Cacko rom, pdaXrom  (up to beta3), pdaXii, and Angstrom, i.e. no uboot is installed.

As always, thanks for your help, ZDevil!

I just realized that I had wanted to extract the files to my internal drive on my 3200, which I formatted as instructed. However, when I had problem extracting it there from the SD card since the emergency mode doesn't seem to be able to handle bz2 files, only tar files, I decided to try extracting it onto the card itself using my MacBook/OSX/Terminal....but you're right the SD card is formatted as FAT...hence the problems....

So, I guess I need to reformat the SD card and re-copy the files to it....

Would be a lot simpler if we could either

A) get the rootfs tarball in tar format, not bz2 so that we could extract it from card over to internal drive on 3200 or

 find out if there is a way to extract bz2 file on card over to internal drive....

Thanks.

[LinuxGadget]

That would be nice!  

This way it should be easier to concentrate on one problem - solve it - and move on.

Although a bit busy at the moment, i'll be definitely be a testing those scriptpacks.

Just to add:

From now on before the release of the next OOTB rootfs tarball, I will put things up in scriptpacks and post them in the forum every now and then.

...

How's that?

[ZDevil]

Thanks! I will also add uninstaller scripts if possible, so users can revert the changes and start afresh.
I am doing the scriptpacks just because I am too lazy to make a .deb.
Perhaps I can put all the scriptpacks together into an new customization .deb (with choices for installing /not installing each module) and post it together with the new customized rootfs.

Things already done:
1) IceWM: new root program menu, desktop icons, wallpaper rotation (landscape <-> portrait), more menu entries (rotation, screenshot, gksu, etc.)
2) Mouse right click: new slim and fast binaries
3) Dualboot option/desktop icon (may add it to IceWM menu)
4) New packages (browser, localepurge, ssh, etc)
5) gnome-helper (yelp) hack: to fix key [1] acting as F1 in gnome apps and calling gnome-helper in e.g. gnumeric and epiphany
6) New working repos list in /etc/apt/sources.list
7) Some tweaks to reduce disk writing (esp. for flash disks)

Things to be done (any help greatly appreciated!):
1) bluetooth
2) WPA support
3) automount SD/CF cards