Help - Search - Members - Calendar
Full Version: A Clean, Fresh, Configured Eabi Rootfs Tarball
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > Debian
Pages: 1, 2, 3, 4, 5, 6
Locutus73
QUOTE(ZDevil @ Jan 2 2008, 03:13 AM) *
QUOTE(urkden @ Dec 31 2007, 04:05 PM) *
Zdevil said in this thread that he didn't appreciate it. In titchy linux (OABI) I don't have any issue. Everything looks great on both machines. It would be interesting to solve it. I'll try asap video performance (after network card is configured) and share my exprience. Thanks.

Not exactly. It's just that I don't see window shadowing on both my C860 and C3200, so there is nothing I can say about that. smile.gif

BTW the r3 of the EABI rootfs is underway. Now I am waiting for 2or0's packages to be added to jpmatrix's feed, so that apt-get and apt-pinning can work smoothly.

wpa-supplicant will also be added to the rootfs, but I can't test it because I am not using it now.

Any more suggestion?


Try to add http://www.angstrom-distribution.org/unsta..._1.0-r3_all.ipk
I used this package (with some tweaks, something in rc.d if I recall correctly) in order to load a WPA enabled firmware in my Ambicom WL1100C-CF at boot time
zecrazytux
hey everybody smile.gif

does anyone know if there's a kernel with ieee80211 tkip support for C1000 ?
youggun's 2.6.22 does not :-(

Capn_Fish
I think there's a yonggun 2.6.23.x out now, at least I saw it mentioned somewhere.
scottlfa
Indeed there is.
zecrazytux
is it possible to install a new kernel without flashing (and maybe to be able to choose which kernel to boot) ?
2or0
QUOTE(zecrazytux @ Jan 8 2008, 04:18 PM) *
hey everybody smile.gif

does anyone know if there's a kernel with ieee80211 tkip support for C1000 ?
youggun's 2.6.22 does not :-(


Here is the ieee80211 tkip module for 2.6.22.9. Just remove 'tar.gz' in the file name.

Click to view attachment
jpmatrix
2or2,

as you're in a compilation rush, would you compile kernel 2.6.23 without uboot or altboot or i-don't-know-boot, AND/OR compile the fuse modules for it please?

moreover, how do you compile your kernel ? i tried to compile the fuse module for my angstrom 2.6.23 kernel but it doesn't want to insmod. i need the fuse module for gmailfs and flickrfs

thanks in advance!
zecrazytux
QUOTE(2or0 @ Jan 9 2008, 12:14 PM) *
QUOTE(zecrazytux @ Jan 8 2008, 04:18 PM) *
hey everybody smile.gif

does anyone know if there's a kernel with ieee80211 tkip support for C1000 ?
youggun's 2.6.22 does not :-(


Here is the ieee80211 tkip module for 2.6.22.9. Just remove 'tar.gz' in the file name.

Click to view attachment



lots of thanks 2or0 ! i tried to compile my own kernel, with the gnu eabi toochain which is packaged for debian
i got a kernel.img of about 1.5mo but unfortunatly it doesn't work with my c1000 :-(
Now that's broken :s but thanks to your help i'll repair it and make wifi to work wink.gif
zecrazytux
QUOTE(2or0 @ Jan 9 2008, 12:14 PM) *
QUOTE(zecrazytux @ Jan 8 2008, 04:18 PM) *
hey everybody smile.gif

does anyone know if there's a kernel with ieee80211 tkip support for C1000 ?
youggun's 2.6.22 does not :-(


Here is the ieee80211 tkip module for 2.6.22.9. Just remove 'tar.gz' in the file name.

Click to view attachment


well, it does'nt work :-(
vermagic is different, as the module is for 2.6.22.9 and the kernel is 2.6.22.9-yonggun... I don't know if that's the reason.
I get an error inserting the module: invalid format :-(

can you share kernel sources, pathces and the .config file ?
lots of thanks !

Edit: in fact i think i could build most of my own modules if you give me the module/build directory tongue.gif
ZDevil
QUOTE(Locutus73 @ Jan 8 2008, 10:53 PM) *
QUOTE(ZDevil @ Jan 2 2008, 03:13 AM) *


BTW the r3 of the EABI rootfs is underway. Now I am waiting for 2or0's packages to be added to jpmatrix's feed, so that apt-get and apt-pinning can work smoothly.

wpa-supplicant will also be added to the rootfs, but I can't test it because I am not using it now.

Any more suggestion?


Try to add http://www.angstrom-distribution.org/unsta..._1.0-r3_all.ipk
I used this package (with some tweaks, something in rc.d if I recall correctly) in order to load a WPA enabled firmware in my Ambicom WL1100C-CF at boot time


Thanks! I am also thinking of upgrading my home network security to WPA. For now the Z is the roadblock.
So to add to the booting script?
If it works for me I will add these stuff to the updated rootfs.
Locutus73
QUOTE(ZDevil @ Jan 11 2008, 08:58 PM) *
Thanks! I am also thinking of upgrading my home network security to WPA. For now the Z is the roadblock.
So to add to the booting script?


Yes.
If I recall correctly (It's been months since I booted my zaurus last time) the ipk install script tries to add something to rcN.d's scripts but it fails because of an updtate-rc.d's wrong syntax. If you examine the ipk contents, just check the install script, and correct the update.rc.d command.
It would be useful to build a correct deb package and to add it to the repositories.

QUOTE(ZDevil @ Jan 11 2008, 08:58 PM) *
If it works for me I will add these stuff to the updated rootfs.

Good.
I want to refresh my Debian install, but I'm too lazy to redo my complicate setup, so I'll wait for your ready rootfs wink.gif

I think that all your work could lead to another installation method.
We could use your rootfs to build an installer using this following steps:
1) Install u-boot
2) Prepare an ext-2 sd with your rootfs (or a minimal rootfs, without X, but with your zaurus customizations).
3) Boot from the sd with your fs. The fs should be slightly modified in order to have some installation scripts. It should have some sort of script able to:
a ) Setup the network
b ) Partition and format the internal microdrive
c ) Install a base debian rootfs using debootstrap (I love debootstrap because It prepares an uptodate minimal debian system)
d ) Run a script that applies all post-install steps (install zaurus specifics debs and customizations, save the network config and the fstab prepared during installation); this script could be downloaded online in order to be updated without touching the installer.
3b) Alternatively to 3) user can choose an option that clones the SD rootfs using rsync on the internal microdrives and then modifies just the network config and the fstab.
4) Reboot from internal microdrive and all eventually run some post install script (one could prepare something in order to interactively change the timezone and the locales)

This could lead to a definitive, and neutral, Debian installer, that installs an uptodate minimal sid filesystem, with the minimal customizations needed to run on the Zaurus.

P.S.: how do you manage the user issue in your rootfs? I mean, I had to tweak startx scripts in order to run X server as root through sudo and all the other stuff as a normal user.
shade
QUOTE(2or0 @ Jan 9 2008, 02:14 PM) *
Here is the ieee80211 tkip module for 2.6.22.9. Just remove 'tar.gz' in the file name.

Click to view attachment

It's doesn't work :'(
Locutus73
QUOTE(Locutus73 @ Jan 13 2008, 05:43 PM) *
If I recall correctly (It's been months since I booted my zaurus last time) the ipk install script tries to add something to rcN.d's scripts but it fails because of an updtate-rc.d's wrong syntax. If you examine the ipk contents, just check the install script, and correct the update.rc.d command.

I checked the zaurus and there's no rcN.d init script. The whole process is managed by udev/hostap, so you have just to install the ipk
Locutus73
QUOTE(ZDevil @ Dec 19 2007, 04:50 AM) *
3. a preinstalled application menu (for icewm and others), which is missing in the current tarball

This should be done automatically with the debian update-menus command.
Any supposed release date for the updated rootfs? rolleyes.gif
ZDevil
Okay, now I have a little time slipping back to this project. (My Eee PC is just keeping me occupied all the time ... it's my primary computer day in and day out now cool.gif )

QUOTE(Locutus73 @ Feb 3 2008, 07:00 PM) *
QUOTE(ZDevil @ Dec 19 2007, 04:50 AM) *
3. a preinstalled application menu (for icewm and others), which is missing in the current tarball

This should be done automatically with the debian update-menus command.
Any supposed release date for the updated rootfs? rolleyes.gif


Exactly. But I am still thinking about using this because what the update-menus generates is not entirely convenient. Just too many submenus. And its syntax is a bit clumsy to edit.
Can someone confirm that wpa_supplicant works in EABI? It would be super nice if someone can post a concise how-to.
Besides the program menu, I am testing a nice app called Mercury: http://www.marengo-ltd.com/mercury/ It works very well on my Eee PC 701 (xubuntu 7.10 Gutsy).
It's practically the linux version of Quicksilver for Mac.
Any thought here?
matthis
Thanks for this great image it works perfectly for me, with sharp-bootloader-yonggun kernel.
Where can I find kexec? Its not in debian rep for arm...

EDIT: OK, I used the one in Angstrom feed wink.gif
ZDevil
I am overwhelmingly by so many interesting updates and solutions popping up over these weeks!
ATM I am still very busy with work(, apart from helping in debugging a few things on the eee pc... tongue.gif) Will get back on track asap.

To catch up with the fast development, here is a brief summary of the new cool stuff for the next rootfs tarball. Feel free to suggest what you want to add and what you think may be useful to general users)

The goal is very simple: to create a constantly updated, kernel-neutral (as possible) rootfs integrating the fruits scattering in the threads, bootable with uboot AND sharp bootloader and with one or more than one systems (sharp/cacko/pdaX/Angstrom).


0) Kernel
2or0's new kernel:
http://www.oesf.org/forum/index.php?showtopic=25351
http://yonggun.tistory.com/66

Dualboot without uboot:
http://yonggun.tistory.com/67

(Thanks to 2or0's great work!!).


Solutions/Patches under consideration:
1) Jumping stylus pointer:
rmmod mousedev
source: http://www.oesf.org/forum/index.php?showto...st&p=174536

2) mplayer:
http://www.oesf.org/forum/index.php?showtopic=25456, esp Post#4

3) browser (icehamster):
http://www.oesf.org/forum/index.php?showtopic=25435

4) internet phone:
Kphone/pi, wengophone
http://www.oesf.org/forum/index.php?showtopic=25326

5) WPA-supplicant
http://www.oesf.org/forum/index.php?showtopic=25325

6) Simple right-click (1-step tap-plus-keypress)
http://www.oesf.org/forum/index.php?showtopic=25459

7) fbiterm
http://www.oesf.org/forum/index.php?showtopic=25463

8) Mercury (to replace the system menu; update-menus is okay but has rooms for improvement)
http://www.oesf.org/forum/index.php?showto...st&p=174312


8) Additional packages/programs to include:
-- localepurge
-- Xfce4 (or any other lightweight WM that can generate and handle program menus easily)
-- Iceweasel (to be tested)
-- OpenOffice (to be aliened and tested)

9) Some tweaks to reduce writes on flash drives
From Eee PC sources:
http://wiki.debian.org/DebianEeePC/TipsAnd...40c3a4e9b00ac1f
https://help.ubuntu.com/community/EeePC#hea...598caa70481700b
http://ubuntu-eee.tuxfamily.org/index.php5...our_Flash_Drive

adf
nice! How is hardware support--bluetooth/GPRS dialup, wifi, screen rotatation..that sort of thing?
...and then all that is need is a glitch free android running in debian on this setup tongue.gif
2or0
QUOTE(ZDevil @ Feb 19 2008, 08:12 AM) *
8) Mercury (to replace the system menu; update-menus is okay but has rooms for improvement)
http://www.oesf.org/forum/index.php?showto...st&p=174312


I recommend grun which is in the feed.
ZDevil
QUOTE(2or0 @ Feb 20 2008, 01:09 PM) *
QUOTE(ZDevil @ Feb 19 2008, 08:12 AM) *
8) Mercury (to replace the system menu; update-menus is okay but has rooms for improvement)
http://www.oesf.org/forum/index.php?showto...st&p=174312


I recommend grun which is in the feed.


Actually gmrun is already included in the present rootfs tarball posted here and is part of the system menu (if you pick "Run"). The difference between gmrun and mercury is that the latter does not only launch programs but also features incremental searching and lists most frequently used programs on the top, which is pretty close to what QuickSilver does on Mac OS: http://noypeee.blogspot.com/2007/12/mercur...uicksilver.html
2or0
QUOTE(ZDevil @ Feb 21 2008, 02:15 AM) *
QUOTE(2or0 @ Feb 20 2008, 01:09 PM) *
QUOTE(ZDevil @ Feb 19 2008, 08:12 AM) *
8) Mercury (to replace the system menu; update-menus is okay but has rooms for improvement)
http://www.oesf.org/forum/index.php?showto...st&p=174312


I recommend grun which is in the feed.


Actually gmrun is already included in the present rootfs tarball posted here and is part of the system menu (if you pick "Run"). The difference between gmrun and mercury is that the latter does not only launch programs but also features incremental searching and lists most frequently used programs on the top, which is pretty close to what QuickSilver does on Mac OS: http://noypeee.blogspot.com/2007/12/mercur...uicksilver.html


Not gmrun but grun. wink.gif

Description: gRun includes features such as a history, command completion from the history and from PATH, recognition of console mode applications and launching a terminal for them, file extension associations and a dual fork()/execvp() application launcher.
ZDevil
Hmm. I will look into grun again. IIRC, grun has a problem with window positioning and size, and gmrun is an improved version of grun. But 2or0 is right, there are far more functionality in grun (and gmrun also) than I was aware of.

Two more things to add to the list:
WM:
I will pick up xfce4 again and see how it fares in Debian. Instead of running menu-update, a better solution to the system menu in IceWM is to make use of the menus generated in Xfce4 (the gnome menus), which are much more tidy and organized. Having two WMs in a preinstalled system to choose from and play with is not such a bad idea. If there is xfce4 I will also do some basic setup on the desktop for OOTB use.

Locales:
Will preinstall and include the localepurge package, such that users can run it once upon installation to reclaim tens of MBs.

But first of all, I will have to do a NAND flash restore to uboot my setup on 3200 again, change it back to ext3 from ext2, and turn to 2or0's sharp bootloader way again... when I get extremely bored. rolleyes.gif
ZDevil
Oh yea, I almost forgot two very important things!

Iceweasel: it seems to be back again/soon! The debian-armel mailing list says the segfault error that everyone is experiencing may be due to libgtk2 version problem. I've libgtk2 has been updated and iceweasel in some unofficial feed.
http://groups.google.com/group/linux.debia...4f87cdfd206636e

OpenOffice!! I bump into a Fedora armel repo and find armel ports of OOos there!
http://ooo.services.openoffice.org/pub/Ope.../armeabiport01/
These are armel ports compiled with the Java options. It's interesting to see how alien can manage that. It will be cool if we can finally manage to put OOo back in Debian/Zaurus again after the good old Pocketworkstation.
jpmatrix
QUOTE(ZDevil @ Feb 28 2008, 06:10 PM) *
OpenOffice!! I bump into a Fedora armel repo and find armel ports of OOos there!
http://ooo.services.openoffice.org/pub/Ope.../armeabiport01/
These are armel ports compiled with the Java options. It's interesting to see how alien can manage that. It will be cool if we can finally manage to put OOo back in Debian/Zaurus again after the good old Pocketworkstation.


i've yet tried this one some times ago :

http://www.oesf.org/forum/index.php?showtopic=24789

i had no luck... but perhaps it will work now...
ZDevil
I came across several cool tips to reduce writing to the flash disks in several pointers for Eee PC. I am testing them in me Debian/Zaurus set up and they seem to work. Will include them also. smile.gif
jpmatrix
so what about the new rootfs ? i'd like to try before leaving the zaurus scene wink.gif
apink
QUOTE(LinuxGadget @ Dec 11 2007, 02:01 PM) *
My spectrum24 network-cf didn't work (missing firmware ?), so i configured usb-networking. Runnning apt-get update now rolleyes.gif


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
auto eth0
iface eth0 inet dhcp


would do it. No luck. How did you configure your usb-networking? Any pointers will be appreciated. tongue.gif

Edit: fixed. Newbie at the controls.

CODE
allow-hotplug eth0
iface ith0 inet dhcp

is what worked in /etc/network/interfaces.
I also have to do
CODE
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.
http://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
QUOTE(jpmatrix @ Mar 5 2008, 11:41 PM) *
so what about the new rootfs ? i'd like to try before leaving the zaurus scene wink.gif


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
QUOTE(bunkford @ Mar 21 2008, 04:19 PM) *
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:

QUOTE
-- 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
QUOTE(gsgmx @ Mar 21 2008, 06:13 PM) *
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:

QUOTE
-- 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
QUOTE(ZDevil @ Mar 21 2008, 10:07 AM) *
QUOTE(bunkford @ Mar 21 2008, 04:19 PM) *
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
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
QUOTE(AmigaFalcon @ Mar 29 2008, 12:43 AM) *
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. smile.gif

QUOTE
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:
QUOTE
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.

QUOTE
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. smile.gif Click to view attachment
QUOTE
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
QUOTE(ZDevil @ Mar 28 2008, 11:42 PM) *
@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

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

Thanks.
LinuxGadget
That would be nice! rolleyes.gif

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.


QUOTE(ZDevil @ Mar 29 2008, 08:37 AM) *
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
LinuxGadget
QUOTE(ZDevil @ Mar 30 2008, 12:05 PM) *
...
Things already done:
...
7) Some tweaks to reduce disk writing (esp. for flash disks)


That's really great for my C1k, maybe it speeds things up a little bit?

QUOTE(ZDevil @ Mar 30 2008, 12:05 PM) *
...
Things to be done (any help greatly appreciated!):
1) bluetooth
2) WPA support
3) automount SD/CF cards


So what's up with bluetooth? Some time ago i managed to sync my phone contacts with opensync and evolution by bluetooth. Maybe i can help? wink.gif
ZDevil
QUOTE(LinuxGadget @ Mar 30 2008, 01:21 PM) *
So what's up with bluetooth? Some time ago i managed to sync my phone contacts with opensync and evolution by bluetooth. Maybe i can help? wink.gif


Yes, Please do! Thanks! smile.gif

ArchiMark
Want to install Debian to my internal 6GB microdrive.

So, extracted the tarball and modules file on ext3 formatted SD card using another computer. Seems OK,

Meanwhile, using fdisk I formatted my internal microdrive into 2 partitions; large ext3 partition (hda1) and a small swap partition (hda2).

Then I formatted the hda1 partition using
CODE
mke2fs -j /dev/hda1
.

So, now some questions please to help minimize my making mistakes....

1) I did not format the hda2 swap partition. Do I need to do that?

2) Do I need to mount the hda1/hda2 partitions before doing rest of install? If so, mount to?

Instructions say
QUOTE
Step 3:
Edit /etc/fstab and assign the correct mount points to the root partition and the swap partition.
The default is set to boot from the internal drive.
Just comment the lines for /dev/hdaX and uncomment the lines for /dev/mmcblk0pX if debian boots from SD.


However, I just looked at '/etc/fstab' file on SD card. It shows the following:

CODE
/dev/root          /               ext2      rw                          1  1
/dev/shm          /tmp         tmpfs    size=16M                 1  2
/dev/mmcda1   /mnt/card  auto      noauto, owner          0  0
none               /dev/pts     devpts   gid=5, modes=620   0  0



So, this is a lot different than what instructions say I'll see.....


3) Then do I need to copy over all the files from SD card to internal microdrive in order to install it there or can I install to microdrive using files on SD? What would be best way?


Appreciate all the help!

Thanks,

Mark
ZDevil
A suggestion of partitioning of microdrive: /dev/hda1 = swap partition; /dev/hda2 = root partition
Reason: swap partition is accessed faster in the beginning of the drive. (Flash disks don't seem to have this issue)

Swap partition: you have to do: mkswap /dev/hda1 (or /dev/hda2)

"Installation" of the rootfs: Just copy/extract the content of the rootfs tarball to the microdrive partition. Make sure that your kernel matches the partition. So if your rootfs is in /dev/hda1, use yonggun's hda1 kernel, and so is hda2.
ZDevil
About /etc/fstab:
Change to this:
CODE
/dev/hda2    /     ext3   rw,noatime      1  1
/dev/hda1    /none  swap  sw                0  0
proc         /proc   proc  defaults         0  0
sysfs        /sys    sysfs  defaults        0  0
/dev/shm     /tmp   tmpfs  size=16M         1  2
ArchiMark
QUOTE(ZDevil @ Mar 30 2008, 08:19 AM) *
A suggestion of partitioning of microdrive: /dev/hda1 = swap partition; /dev/hda2 = root partition
Reason: swap partition is accessed faster in the beginning of the drive. (Flash disks don't seem to have this issue)

Swap partition: you have to do: mkswap /dev/hda1 (or /dev/hda2)

"Installation" of the rootfs: Just copy/extract the content of the rootfs tarball to the microdrive partition. Make sure that your kernel matches the partition. So if your rootfs is in /dev/hda1, use yonggun's hda1 kernel, and so is hda2.


Thanks, ZDevil!

OK, re-did my microdrive as you suggested.... think I'm getting close now to getting install working...

Edited fstab as you suggested... (however, when I reopened fstab in vi, this time it looked like the way it was mentioned in instructions, so was OK, weird....).

When I tried to copy over tarball contents to microdrive, it couldn't do it, said there wasn't room....
Now, I realize that I made a mistake by trying to mount hda2 per criteria in fstab, as it was trying to copy file to root, but this is the small area in the linux emergency mode....

So, now, I need to mount hda2 properly to copy files over to it using cp -R /mnt/card /mnt/???

What is the right mount point for hda2 in order to be able to copy the files over it?

Do I need to do the same thing now for hda1, the swap partition??

Also, regarding yonggun's kernel, I downloaded the hda1 one and renamed it to zImage.bin as in instructions...so, the only other Sharp bootloader files on that webpage were for mmcdablk0p1 and mmcdablk0p2....none for hda2. So, is this OK to use zImage.bin that I downloaded?

Thanks,


ZDevil
Follow the first post of this thread: http://www.oesf.org/forum/index.php?showtopic=25029

I made a mistake about the /etc/fstab. You don't need the line for tmpfs (i.e. the last line in my previous post).
ArchiMark
QUOTE(ZDevil @ Mar 30 2008, 10:06 AM) *
Follow the first post of this thread: http://www.oesf.org/forum/index.php?showtopic=25029


I'm trying, ZDevil, I'm trying....

rolleyes.gif

But, don't I need to copy over the files from my SD card to my internal drive before flashing kernel?? Or are saying that I can install those files from SD card to microdrive during install or later??

If I need to copy files over now, then I need to know what is the proper way to mount hda2 from commant prompt...


QUOTE
I made a mistake about the /etc/fstab. You don't need the line for tmpfs (i.e. the last line in my previous post).


Oh, OK....

Thanks!
ZDevil
mkdir /mnt/cf (the name of the mount point doesn't matter)
mount -t ext3 /dev/hda2 /mnt/cf

Ready your root partition and rootfs before flashing the kernel.
ArchiMark
QUOTE(ZDevil @ Mar 30 2008, 10:20 AM) *
mkdir /mnt/cf (the name of the mount point doesn't matter)
mount -t ext3 /dev/hda2 /mnt/cf


Right, ZDevil....mounted OK now....


QUOTE
Ready your root partition and rootfs before flashing the kernel.


If by this you mean copy over the extracted tarball and module files to root level of hda2 then that is what I'm doing now on Z..... given the size of the files, I think it will take some time to complete copying all the files...

THANKS again for all your help. Truly appreciate it!!!!

biggrin.gif

UPDATE: Just tried flashing and it says error message something like :

CODE
  
Zaurus SD Updater
/mnt/card/$UPDATE_SHELL not found


So, something is not ready yet....

blink.gif



This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.