A Clean, Fresh, Configured Eabi Rootfs Tarball

[ZDevil]

Hey, Fatty! Glad to see you here again!
Okay, i'll get the (tar)ball rolling tonight.

Longing for playing with the Z w/ Debian! You'll save my life!
I did buy a new Sandisk 8G and tried installing again, but still got the same kernel panic issue. But I finally figured out what had been happening: I didn't press [2] while booting with uboot! So the issue is not CF related  
[OT] not back to the place-you-know-where for some time, and only recently noticed you won't be back there. So see you here   . My wife is getting better now but the health issue is on me though ...

Fatty, the tarball is ready now. Have fun!
Just forget about the incidence in the place-you-know-where.... I can't think of any word to describe it except "ridiculous".
Take good care of yourself and your wife!  

[sagouin]

This is working good on my C1000 with kernel 2.6.22.9 yonggun on a 2GB SD card (Sandisk 133X)
Thank you very much for sharing your work !

[scottlfa]

Dutifully downloading this one, great job guys

[jpmatrix]

perhaps i'll backup my existing eabi and try the zdevil rootfs on my C3000 with angstrom 2.6.23
that way we'll know if works well with this configuration

[Fatty]

Fatty, the tarball is ready now. Have fun!

Tks. Downloading.

If you don't mind, I'll direct those interested from you-know-where to this post.  

[Fatty]

This sounds interesting. You probably remember I had a kernel panic issue with Titchy due to the kernel not recognizing my A-Data 16GB internal. I'm guessing that this kernel won't either (though it would be handy).  This raises 2 possibilities-- will u-boot handle my internal cf issue, and if not is there a reasonable way to do a 1000 style sd installation on a 3100 (and then use the internal cf as /home, or something like, ultimately)?  

Also, how is the sound?

I used to think I have the same kernel panic issue with my swapped CF (TwinMOS 4GB). Recently I have swapped it to another Sandisk ultraII 8G, and got the same result. Till yesterday I finally figured out that it's all because I didn't press [2] (boot from Internal CF) while booting uboot. Now my Z can boot in Debian with the original TwinMOS CF. Stupid me  

[ZDevil]

Fatty, the tarball is ready now. Have fun!

Tks. Downloading.
If you don't mind, I'll direct those interested from you-know-where to this post.  

No problem. Just let me know if there is any issue of the tarball.
Feel free to post it *anywhere*.
BTW i've already posted it in Dinorex's forum.  

[adf]

This sounds interesting. You probably remember I had a kernel panic issue with Titchy due to the kernel not recognizing my A-Data 16GB internal. I'm guessing that this kernel won't either (though it would be handy).  This raises 2 possibilities-- will u-boot handle my internal cf issue, and if not is there a reasonable way to do a 1000 style sd installation on a 3100 (and then use the internal cf as /home, or something like, ultimately)?  

Also, how is the sound?

I used to think I have the same kernel panic issue with my swapped CF (TwinMOS 4GB). Recently I have swapped it to another Sandisk ultraII 8G, and got the same result. Till yesterday I finally figured out that it's all because I didn't press [2] (boot from Internal CF) while booting uboot. Now my Z can boot in Debian with the original TwinMOS CF. Stupid me  

..and me maybe, it would appear

[jpmatrix]

zdevil,

your rootfs seems to work on my c3000 !

mainly i had to :

-unable to open initial console on 1st boot : solved by rebooting

-modules.dep not found on boot : solved by depmod -a   on first root login

-startx : icewm launch is ok ! but stylus doesn't go where i click !

apparently /dev/input/ts0 does not exist
and ts.conf is misconfigured (module_raw corgi is not commented)
lets's nano-ing a little

EDITED:

stylus troubles solved by :

rmmod mousedev  (for the stylus jittering)
cd /dev/input
ln -s ts0 event1
then startx, open a console and ts_calibrate to recalibrate the screen



thanks for your work Zdevil ! it looks it works on a c3000 too !

[ZDevil]

I have no idea what causes the issues of initial console and depmod. They played well in my case. I wonder if it has to do with something one has to do with the freshly installed kernel (I did this rootfs on my already working 3200 setup).

The stylus thing is tricky. As I suspect at the end of the instructions, you need to play with other options if you use non-yonggun kernels.

Thanks, jpmatrix for the feedback. Perhap it's not such a bad idea to keep the tarball polished and updated every now and then?  

[crossblaim]

from where you make the step 3 to format internal drive? from uboot?

[jpmatrix]

I have no idea what causes the issues of initial console and depmod. They played well in my case. I wonder if it has to do with something one has to do with the freshly installed kernel (I did this rootfs on my already working 3200 setup).

The stylus thing is tricky. As I suspect at the end of the instructions, you need to play with other options if you use non-yonggun kernels.

Thanks, jpmatrix for the feedback. Perhap it's not such a bad idea to keep the tarball polished and updated every now and then?  

yesssss
what do you think is better : i make another thread (or a special entry in the wiki for the c3000) or you modify your initial first thread to add the c3000 ?

[ZDevil]

from where you make the step 3 to format internal drive? from uboot?

Hmm. Here is a thing about uboot: it seems not being able to handle ext3 partition properly (but correct me if I am wrong).
So perhaps it is safer to do the extraction before installing uboot (if it has not been installed yet). Let me swap steps 1, 2, 3. That doesn't hurt anything at all.
Thanks for reminding me of this.

[band-aid]

How would I go about installing this on my SL-C3200's internal drive? I'm wanting to do a complete clean install of the yongun kernel and use this rootfs. What would be the easiest way to do this coming from Angstrom?

[Fatty]

from where you make the step 3 to format internal drive? from uboot?

Hmm. Here is a thing about uboot: it seems not being able to handle ext3 partition properly (but correct me if I am wrong).
So perhaps it is safer to do the extraction before installing uboot (if it has not been installed yet). Let me swap steps 1, 2, 3. That doesn't hurt anything at all.
Thanks for reminding me of this.

True. I didn't find mkfs tool within uboot. So I have to nand back to Sharp rom, do format and reinstall uboot. It doesn't cost much time though.

BTW, how can I re-calibrate the pointer? It isn't quite accurate on top and bottom region.

Lastly, as I'm not quite familiar with uboot, after uboot/kernel being flashed, where is the remaining space of the flash memory going?