Help - Search - Members - Calendar
Full Version: Running Zubuntu From Internal Memory
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > Ubuntu
cortez
Hi,

I've posted how-to instructions on my blog. Following these instructions makes it possible to run Zubuntu from internal flash memory. This should work for all currently supported models.

Most part of Zubuntu is squashed into the small amount of internal memory, except for the /usr and /var directories. Unfortunately these have to be located on a different place, being a CF, SD, or MD.

Cheers,
cortez
ppyo
QUOTE(cortez @ Jan 5 2009, 05:14 AM) *
Hi,

I've posted how-to instructions on my blog. Following these instructions makes it possible to run Zubuntu from internal flash memory. This should work for all currently supported models.

Most part of Zubuntu is squashed into the small amount of internal memory, except for the /usr and /var directories. Unfortunately these have to be located on a different place, being a CF, SD, or MD.

Cheers,
cortez


Hi Cortez
Once again, congrats on your achievement, very cool!
Now the question: How about keeping Cacko in the internal flash and Zubuntu in SD? This due to Cack being a lot smaller than Zubuntu. How can I do this?
Thanks in advance!

Capn_Fish
Easy*:

-Get Cacko kernel, put it in Cacko's /boot (if it doesn't exist, make it, call it zImage)
-Untar the Zubuntu stuff to SD
-Look at the Zubuntu files in /boot (minus the kernel)
-Copy them to Cacko's /boot and adapt as necessary
-Flash the Kexec/altboot/whatever it is kernel
-Reboot and enjoy

*These steps have not been tested by me, and are from my understanding, based off of other posts.
jfv
QUOTE(Capn_Fish @ Jan 5 2009, 07:47 PM) *
Easy*:

-Get Cacko kernel, put it in Cacko's /boot (if it doesn't exist, make it, call it zImage)
-Untar the Zubuntu stuff to SD
-Look at the Zubuntu files in /boot (minus the kernel)
-Copy them to Cacko's /boot and adapt as necessary
-Flash the Kexec/altboot/whatever it is kernel
-Reboot and enjoy

*These steps have not been tested by me, and are from my understanding, based off of other posts.


That can't possibly work. The GUI, programs, etc. that make Cacko what it is do not reside in the kernel. What is needed is to make a mirror of /bin, /lib, /usr, /home, /etc, etc :-) and copy to the SD. I've tried to do that with the Sharp ROM but it didn't work and I'm not sure why.

I'd love to hear of anybody who managed to get Cacko or Sharp alongside Zubuntu in the multiboot setup with detailed instructions. Thanks.

EDIT: Maybe I misunderstood your instructions. Do you mean that the Cacko ROM (except the kernel) will be left untouched by the reflash?
So if I start with a Cacko/Sharp ROM in my internal flash it will still be there? Maybe I'll try that. Thanks.

EDIT 2: /boot on Sharp ROM is readonly. I vaguely recall there is a way to get around this. Any suggestions?

EDIT 3: Figured out how to do the remount ( mount -o remount,rw / ), now the Sharp ROM shows up as internal flash option in the omegamoon boot menu but I have the same problem with "init" as in this post.
cortez
QUOTE(ppyo @ Jan 6 2009, 12:44 AM) *
Hi Cortez
Once again, congrats on your achievement, very cool!
Now the question: How about keeping Cacko in the internal flash and Zubuntu in SD? This due to Cack being a lot smaller than Zubuntu. How can I do this?
Thanks in advance!

This is kind of off-topic... running Cacko from internal memory should work. The only important thing would be to adjust the kernel-cmdline by adding the correct mtdpart parameters. That's all. By doing that Cacko should boot normally. Running it from a memory card would mean a lot more tweaking though
pelrun
That would be because the kernel cmdline being passed to the cacko kernel has a wrong/missing mtdparts option - you have to explicitly and correctly describe your nand partition layout.
jfv
QUOTE(cortez @ Jan 6 2009, 12:25 AM) *
QUOTE(ppyo @ Jan 6 2009, 12:44 AM) *
Hi Cortez
Once again, congrats on your achievement, very cool!
Now the question: How about keeping Cacko in the internal flash and Zubuntu in SD? This due to Cack being a lot smaller than Zubuntu. How can I do this?
Thanks in advance!

This is kind of off-topic... running Cacko from internal memory should work. The only important thing would be to adjust the kernel-cmdline by adding the correct mtdpart parameters. That's all. By doing that Cacko should boot normally. Running it from a memory card would mean a lot more tweaking though


And what would these correct mtdpart parameters be?
tanjian2
Hi,
I installed zubuntu - it was so easy. I see from your sig that you have pdaXii13 on the microdrive - is it possible to dual boot this on a C3000? Can you point me at what might need changed to make it happen?
What exactly does updater.sh and zImage.bin replace on the C3000? Is it the boot loader? How does the new one detect what distros/devices are bootable?

Thanks for all the work on zubuntu.
Capn_Fish
Look at my (apparently incorrect for Cacko) Cacko instructions above. It gives a good idea of how to add distros to the boot list.
jfv
QUOTE(Capn_Fish @ Jan 6 2009, 02:01 PM) *
Look at my (apparently incorrect for Cacko) Cacko instructions above. It gives a good idea of how to add distros to the boot list.


So I've located the mntpart info in /proc/cmdline in the Sharp ROM, I copied that to /boot/kernel-cmdline, followed the flashing procedure again and still get the same init error.
ofels
QUOTE(tanjian2 @ Jan 6 2009, 06:05 PM) *
What exactly does updater.sh and zImage.bin replace on the C3000? Is it the boot loader? How does the new one detect what distros/devices are bootable?


updater.sh is the script which normally flashes kernel and root image into NAND memory.

The zImage.bin provided by cortez is a special kernel image which pretends to be a kernel but instead shows the boot screen with all partitions found which either have a kernel-cmd-line file or a *.nfo file in the /boot directory.
After the user selected a partition it loads the kernel file from the /boot directory (usually labelled zImage) and boots the corresponding distribution as usual.

The only difference to the normal boot process is the kernel location (/boot/zImage instead of a NAND image).

Oliver
tanjian2
Thanks to everyone for the replies.
I guess I should have read Cortez's blog more closely as he also explains how it all works. Also searched this forum - thanks for bearing with me.
I have created the /boot directory and added the nfo file and zImage.
Not sure yet where to find the command line for pdaxrom.... but booting fails
Why do I need to pass the NAND partition into the kernel - given pdaXrom for the C3000 actually runs of the microdrive - is it sufficient to put the correct kernel in /boot and then set root=/dev/hda1 for the commandline (no it fails too)? The kernel boots but I can not work out what it is looking for and not finding.....
Any more help would be appreciated.


speculatrix
cacko's root would be an mtdblock device, not hdaX. I'm hoping to get this working too, so if someone can post the exact text for the cacko /boot nfo file, it'd be great (assuming that you previously had cacko installed, then installed zubuntu to hard drive, and flashed the multiboot kernel)
scottlfa
How much faster is it running from flash? Booting etc?
ppyo
QUOTE(speculatrix @ Jan 7 2009, 06:23 PM) *
cacko's root would be an mtdblock device, not hdaX. I'm hoping to get this working too, so if someone can post the exact text for the cacko /boot nfo file, it'd be great (assuming that you previously had cacko installed, then installed zubuntu to hard drive, and flashed the multiboot kernel)



This is what I found in /proc for the kernel-cmdline file:

CODE
console=ttyS0 root=/dev/mtdblock2 mtdparts=sharpsl-nand:7168k@0k(smf),32768k@7168k(root),-(home) jffs2_orphaned_inodes=delete EQUIPMENT=0 LOGOLANG=1 DEFYEAR=2006 LOGO=1 LAUNCH=q


I am still tinkering with it, but so far I get as far as the blue splash screen that reads Loading Linnux and QTopia. I think I need to do it with a fresh Cacko installation.

BTW Zubuntu works great! Many, many thanks again, Cortez!
Jon_J
ppyo,
Let us know if you get this working. It appears that you at least get "Cacko" on the bootmenu if you can get to the blue splash screen.
Here's what I have on my SL-C3100:
I installed a fresh Cacko 1.23 full, and added some of meanie's packages to it.
Then I flashed Eviljazz's kernel, (kernel-fastfpe-cachedfb) which contains the new audio driver, latest tetsu kernel, and newer SD card driver for cards above 1GB.
Then I installed Angstrom opie to my hard drive, with kexec-tools. Using this page, I enabled Cacko to be kexec'ed from within Angstrom:
http://www.linuxtogo.org/gowiki/AngstromAndCacko
Then later, I installed zubuntu to an SD card and flashed the new multiboot kernel.
I have been trying to get Cacko to show up on this menu, but have had no luck.
I can boot Angstrom or zubuntu from the menu.

I read your post above, and decided to try the cmdline that you posted. It doesn't work on my C3100
When I look in /proc/cmdline, all I see is:
console=ttyS0 root=/dev/mtdblock2
This line is the same in /var/log/dmesg
I'm thinking the reason I don't have any numbers or the "other" strings in this line, is because I flashed Eviljazz's kernel to my Cacko.
Maybe, just the latest tetsu kernel would be better for this. I really need the (> 1GB SD driver)

Anyway, if I really want to boot Cacko, I can boot it through Angstrom.
If I ever get Cacko 1.23 to appear on the multiboot menu, I'm going to take a picture of it, since it seems very difficult to achieve... smile.gif
ppyo
QUOTE(Jon_J @ Jan 8 2009, 10:55 PM) *
ppyo,
Let us know if you get this working. It appears that you at least get "Cacko" on the bootmenu if you can get to the blue splash screen.
Here's what I have on my SL-C3100:
I installed a fresh Cacko 1.23 full, and added some of meanie's packages to it.
Then I flashed Eviljazz's kernel, (kernel-fastfpe-cachedfb) which contains the new audio driver, latest tetsu kernel, and newer SD card driver for cards above 1GB.
Then I installed Angstrom opie to my hard drive, with kexec-tools. Using this page, I enabled Cacko to be kexec'ed from within Angstrom:
http://www.linuxtogo.org/gowiki/AngstromAndCacko
Then later, I installes zubuntu to an SD card and flashed the new multiboot kernel.
I have been trying to get Cacko to show up on this menu, but have had no luck.
I can boot Angstrom or zubuntu from the menu.

I read your post above, and decided to try the cmdline that you posted. It doesn't work on my C3100
When I look in /proc/cmdline, all I see is:
console=ttyS0 root=/dev/mtdblock2
This line is the same in /var/log/dmesg
I'm thinking the reason I don't have any numbers or the "other" strings in this line, is because I flashed Eviljazz's kernel to my Cacko.
Maybe, just the latest tetsu kernel would be better for this. I really need the (> 1GB SD driver)

Anyway, if I really want to boot Cacko, I can boot it through Angstrom.
If I ever get Cacko 1.23 to appear on the multiboot menu, I'm going to take a picture of it, since it seems very difficult to achieve... smile.gif


Jon, I have the same kernel, but my Z is an Akita. There might be a difference between Akita and Borzoi re Cacko boot.
My setup:
2GB sd card, three ext2 partitions:
Zubuntu (1GB)
Cacko (450MB)
Pdaxrom (400MB)
I installed Zubuntu, then on the Cacko partition I created the boot directory containing Eviljazz' kernel, the kernel-cmdline in my previous post, and the .nfo file (a plain text file with the description of the distro for the boot menu). Nothing on the Pdaxrom partition yet.
My Akita still has Cacko 1.23 in NAND.
I flash Cortez' kernel & updater.
Zubuntu & Cacko show in the menu. Zubuntu runs perfectly, Cackto starts booting, gets to the blue splash screen, then nothing...
I will try with a fresh install of Cacko, and then I'll try to upgrade to Eviljazz' kernel.
I'll keep you guys posted.
cortez
@ppyo: So it is hereby confirmed that the Akita bootkernel shows a kernel image in NAND, am I correct?
@Jon_J: On my SL-C3100 the kernel image in NAND also shows up in the bootmenu. Since you report that in your case cacko (in NAND) isn't shown, I wonder if your using the latest kernel (MD5: 7bf1d0f9c119892cb4cfd4526a880f5e). Could you check that?

If someone could confirm this for C7x0 also, this would be great. I just want to make sure that the different kernels are now all working fine. I tend to lose track sometimes huh.gif

Cheers,
cortez
tanjian2
Regarding C3000 and dual booting Zubuntu and pdaXii13 - I have revert to my pdaxrom and extracted the cmdline from /proc/cmdline.
However, when I go back to using the zubuntu bootloader it still fails boot pdaxrom.
As I understand pdaxrom for the c3000 boots from NAND then mounts the microdrive and continues booting from there. I had hoped to simply skip the NAND bit and have the zubuntu loader boot straight from the microdrive - but I can't get any of these to successfully boot pdaxrom. Has anyone got a C3000 to dual boot with pdaxrom? Can anyone offer any further help or direction?

Thanks
Jon_J
QUOTE(cortez @ Jan 9 2009, 04:39 AM) *
@ppyo: So it is hereby confirmed that the Akita bootkernel shows a kernel image in NAND, am I correct?
@Jon_J: On my SL-C3100 the kernel image in NAND also shows up in the bootmenu. Since you report that in your case cacko (in NAND) isn't shown, I wonder if your using the latest kernel (MD5: 7bf1d0f9c119892cb4cfd4526a880f5e). Could you check that?

If someone could confirm this for C7x0 also, this would be great. I just want to make sure that the different kernels are now all working fine. I tend to lose track sometimes huh.gif

Cheers,
cortez

Yes, the MD5 matches.

Edit:
Do you also have "usr.bin" in your /boot directory? I'm just curious if this is interfering.
Also, the "zImage" file that I'm using is from Eviljazz's kernel, not the original Cacko kernel.
(you'll notice the filesizes are different in these two kernels)
klaxon
QUOTE(cortez @ Jan 9 2009, 11:39 AM) *
If someone could confirm this for C7x0 also, this would be great. I just want to make sure that the different kernels are now all working fine. I tend to lose track sometimes huh.gif


No, It doesn't work on my C860. I can see Cacko in the bootmenu but it can't boot.
jfv
QUOTE(cortez @ Jan 9 2009, 04:39 AM) *
@ppyo: So it is hereby confirmed that the Akita bootkernel shows a kernel image in NAND, am I correct?
@Jon_J: On my SL-C3100 the kernel image in NAND also shows up in the bootmenu. Since you report that in your case cacko (in NAND) isn't shown, I wonder if your using the latest kernel (MD5: 7bf1d0f9c119892cb4cfd4526a880f5e). Could you check that?

If someone could confirm this for C7x0 also, this would be great. I just want to make sure that the different kernels are now all working fine. I tend to lose track sometimes huh.gif

Cheers,
cortez


I tried to multiboot the Sharp ROM on my C860 both in NAND and on an SD card. In both setups, it shows up on the Omegamoon splash screen list and, when I choose it, I get the usual splash screen with "Sharp" and some japanese text, but then the boot fails with some init errors (reported elsewhere on this thread). Zubuntu boots fine BTW.

Cortez, I really appreciate your work and Zubuntu is quite likely the way forward, but it's not there yet. Multiboot is a wondeful idea and gives those of us who still need older ROMs a bridge. Please don't disregard this issue. Thanks.
felipe
Hi,
I have a very similar question as the one from tanjian2. Until now no answers yet and perhaps I can join my voice to him on trying to find an answer to this: how do you use pdaxrom with kexecboot (multibooting kernel)? It would be nice if I can run it entirely from the microdrive (I have a Z sl c-3200). Sorry if this is a bit offtopic.
Regards,

Felipe.
speculatrix
could the reason for being unable to boot cacko be down to the OS being in two parts, a core squashfs install (only ever read-only, with files/dirs called xyz.rom) and then a cramfs part (read-write if remounted such), so that the multiboot kernel wotsit can't actually see cacko's file systems?

does this mean to get cacko to boot you'd want to boot it normally (i.e. flash a cacko-compatible kernel), then copy off it's file systems, add the kernel image and nfo file (as required by multiboot), repack into an ext2 of the right size to fit in the flash partition. then reflash the multiboot kernel. then copy the ext2 file system into flash?

I did once, BTW, ask about getting unionfs into sharp/cacko kernel so that the nasty symlinking from cramfs to squashfs could be avoided, I don't think it went anywhere?
same
I was thinking in using the nand partition to store a /swapfile and not the OS.
Anyone tried it? or at least tested the nand speed with hdparm (if it's possible)?
speculatrix
QUOTE(same @ Jan 15 2009, 11:39 AM) *
I was thinking in using the nand partition to store a /swapfile and not the OS.
Anyone tried it? or at least tested the nand speed with hdparm (if it's possible)?


I'd DEFINITELY not use the internal flash for a swapfile - it's a raw flash device so there's NO wear levelling whatsover and you'll kill your internal flash and permanently brick your device. Use an SD card instead and if it dies, it's a US$10 item to replace.

Although onboard flash should be good for 1000's or even 10's of 1000's of erase/write, swap will use that up pretty quickly especially since it won't spread the writes. Flashing a new kernel, unless you did it every day for three years, won't hurt.

For onboard flash, you really need to be using a suitable file system!
same
speculatrix: tx for your opinion, I expected that but needed confirmation as the need for more ram makes me think silly quiestions jeje
Jon_J
speculatrix,
How is booting Cacko from the multiboot menu so different than the method using kexec-tools in Angstrom to boot Cacko?
I was going to try this method in zubuntu:
http://www.linuxtogo.org/gowiki/AngstromAndCacko
But kexec-tools in not available for zubuntu in the repositories.
Here's what I get when I try to install "kexec-tools" with "apt-get install"
CODE
Package kexec-tools is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or is only available from another source
E: Package kexec-tools has no installation candidate
speculatrix
QUOTE(Jon_J @ Jan 15 2009, 02:58 PM) *
speculatrix,
How is booting Cacko from the multiboot menu so different than the method using kexec-tools in Angstrom to boot Cacko?


the multiboot kernel would need to have squashfs or cramfs installed. I'm a little hazy as I havent' run cacko in yonks;

although I have cacko in flash and zubuntu on microdrive, and have put the cacko kernel into /boot so I can kexec it to try and boot cacko, it segfaulted part way in, so the only way I can boot cacko is to flash its kernel. It's a matter of finding the time to have a decent play with it.
tanjian2
QUOTE(speculatrix @ Jan 15 2009, 04:03 PM) *
QUOTE(Jon_J @ Jan 15 2009, 02:58 PM) *
speculatrix,
How is booting Cacko from the multiboot menu so different than the method using kexec-tools in Angstrom to boot Cacko?


the multiboot kernel would need to have squashfs or cramfs installed. I'm a little hazy as I havent' run cacko in yonks;

although I have cacko in flash and zubuntu on microdrive, and have put the cacko kernel into /boot so I can kexec it to try and boot cacko, it segfaulted part way in, so the only way I can boot cacko is to flash its kernel. It's a matter of finding the time to have a decent play with it.

Is this true for PdaXrom ? As I understood it Meanies pdaxrom for the C3000 boots of the Nand, mounts the microdrive and then runs up from the microdrive.
Seems simple to add this to the Zubuntu multi boot - I have a /boot directory and the requiste kernel and commandline - however, it just keeps spitting out errors about the file system when it boots.

Sorry for hijacking this thread - should I start another?
ppyo
QUOTE(cortez @ Jan 9 2009, 05:39 AM) *
@ppyo: So it is hereby confirmed that the Akita bootkernel shows a kernel image in NAND, am I correct?
@Jon_J: On my SL-C3100 the kernel image in NAND also shows up in the bootmenu. Since you report that in your case cacko (in NAND) isn't shown, I wonder if your using the latest kernel (MD5: 7bf1d0f9c119892cb4cfd4526a880f5e). Could you check that?

If someone could confirm this for C7x0 also, this would be great. I just want to make sure that the different kernels are now all working fine. I tend to lose track sometimes huh.gif

Cheers,
cortez


Hi all

Finally got some time to work on my Z again.
I can happily report that as of today I have Zubuntu and Cacko running in my C1000! Cacko is running from internal flash!
I had to do a completely fresh reinstall of Cacko:
First, flash Cacko 1.23 original
Then flash Katastrophos kernel with sd modules (>1GB)
Finally, flash Cortez' kernel.
Ta daaaa!!! laugh.gif
*dances happily*

I might have to copy the whole thing to a 4GB sd card. 2GB is a little tight with 1 GB for Zubuntu, 450MB for Cacko (plus internal flash), and 420MB for a future distro (pdaXrom?). Or I might just turn the latter into a common /home partition.

On the Zubuntu side I am trying to deal with minor issues:
- lxlauncher is not stable, crashes frequently. Too bad, coz it is needed
- Firefox is sooooo slow, I am using Dillo
- all PDF viewers I've tried are slow, xpdf segfaults
- installed KA/Pi & KO/Pi, and they work fine but will not sound alarms
- some other stuff

Again many, many thanks to Cortez for such an uber-cool achievement!!!

Gotta change signature to add Zubuntu!!! tongue.gif
klaxon
Great new !
I hope the same for my C860 but there are not Katastrophos kernel unfortunately.
jfv
What is the use of the Katastrophos kernel if Cacko is running from internal flash? If all it adds is SD support, shouldn't Cacko boot without it?
ppyo
QUOTE(jfv @ Jan 24 2009, 10:16 AM) *
What is the use of the Katastrophos kernel if Cacko is running from internal flash? If all it adds is SD support, shouldn't Cacko boot without it?


I use the Katastrophos kernel because it has a nicer sound driver, you don't HAVE to use it. What matters is that the kernel you're using has to have support for SD cards bigger than 1GB. 1GB is simply way too small if you want to have two or more distros available in your Z.
Cheers!
mjiba
QUOTE(ppyo @ Jan 23 2009, 11:55 PM) *
QUOTE(cortez @ Jan 9 2009, 05:39 AM) *
@ppyo: So it is hereby confirmed that the Akita bootkernel shows a kernel image in NAND, am I correct?
@Jon_J: On my SL-C3100 the kernel image in NAND also shows up in the bootmenu. Since you report that in your case cacko (in NAND) isn't shown, I wonder if your using the latest kernel (MD5: 7bf1d0f9c119892cb4cfd4526a880f5e). Could you check that?

If someone could confirm this for C7x0 also, this would be great. I just want to make sure that the different kernels are now all working fine. I tend to lose track sometimes huh.gif

Cheers,
cortez


Hi all

Finally got some time to work on my Z again.
I can happily report that as of today I have Zubuntu and Cacko running in my C1000! Cacko is running from internal flash!
I had to do a completely fresh reinstall of Cacko:
First, flash Cacko 1.23 original
Then flash Katastrophos kernel with sd modules (>1GB)
Finally, flash Cortez' kernel.
Ta daaaa!!! laugh.gif
*dances happily*

I might have to copy the whole thing to a 4GB sd card. 2GB is a little tight with 1 GB for Zubuntu, 450MB for Cacko (plus internal flash), and 420MB for a future distro (pdaXrom?). Or I might just turn the latter into a common /home partition.

On the Zubuntu side I am trying to deal with a few minor issues (lxlauncher is not stable, installed Ka/Pi, but will not sound alarms, etc...)
Again many, many thanks to Cortez for such an uber-cool achievement!!!

Gotta change signature to add Zubuntu!!! tongue.gif



ppyo, could you give a few more details as to how you were successful? Which Katastrophos kernal did you use? What Zimage is in your Cacko partition. I just tried this on my C1000 and ended up with a kernal panic when trying to boot cacko.

ppyo
QUOTE(mjiba @ Jan 24 2009, 12:31 PM) *
QUOTE(ppyo @ Jan 23 2009, 11:55 PM) *
QUOTE(cortez @ Jan 9 2009, 05:39 AM) *
@ppyo: So it is hereby confirmed that the Akita bootkernel shows a kernel image in NAND, am I correct?
@Jon_J: On my SL-C3100 the kernel image in NAND also shows up in the bootmenu. Since you report that in your case cacko (in NAND) isn't shown, I wonder if your using the latest kernel (MD5: 7bf1d0f9c119892cb4cfd4526a880f5e). Could you check that?

If someone could confirm this for C7x0 also, this would be great. I just want to make sure that the different kernels are now all working fine. I tend to lose track sometimes huh.gif

Cheers,
cortez


Hi all

Finally got some time to work on my Z again.
I can happily report that as of today I have Zubuntu and Cacko running in my C1000! Cacko is running from internal flash!
I had to do a completely fresh reinstall of Cacko:
First, flash Cacko 1.23 original
Then flash Katastrophos kernel with sd modules (>1GB)
Finally, flash Cortez' kernel.
Ta daaaa!!! laugh.gif
*dances happily*

I might have to copy the whole thing to a 4GB sd card. 2GB is a little tight with 1 GB for Zubuntu, 450MB for Cacko (plus internal flash), and 420MB for a future distro (pdaXrom?). Or I might just turn the latter into a common /home partition.

On the Zubuntu side I am trying to deal with a few minor issues (lxlauncher is not stable, installed Ka/Pi, but will not sound alarms, etc...)
Again many, many thanks to Cortez for such an uber-cool achievement!!!

Gotta change signature to add Zubuntu!!! tongue.gif



ppyo, could you give a few more details as to how you were successful? Which Katastrophos kernal did you use? What Zimage is in your Cacko partition. I just tried this on my C1000 and ended up with a kernal panic when trying to boot cacko.


Ok, here we go, besides what I posted above:

Katastrophos kernel: http://katastrophos.net/zaurus/kernels/current
I used the one for Akita, of course. I like it because it has a nice sound driver. You may get good results with Tetsu's kernel too, but I have not tried Tetsu's. This is the zImage I used.

In your Cacko partition in the SD card you MUST have a boot directory containing the kernel file (ZImage), an Image.nfo text file (short distro description that will be used by the boot menu), and a kernel-cmdline text file.
My kernel-cmdline file looks like this:

CODE
console=ttyS0 root=/dev/mtdblock2 mtdparts=sharpsl-nand:7168k@0k(smf),32768k@7168k(root),-(home) jffs2_orphaned_inodes=delete EQUIPMENT=0 LOGOLANG=1 DEFYEAR=2006 LOGO=1 LAUNCH=q


After Cacko booted successfully for the first time I installed the modules that enable Cacko to work with SD cards greater than 1GB.
You must change fstab so Cacko will mount the correct SD partition as /mnt/card. Unchanged, it mounted the Zubuntu partition as it is the first one on my SD card.

I hope this covers all that you need. Good luck!
mjiba
QUOTE(ppyo @ Jan 24 2009, 01:41 PM) *
QUOTE(mjiba @ Jan 24 2009, 12:31 PM) *
QUOTE(ppyo @ Jan 23 2009, 11:55 PM) *
QUOTE(cortez @ Jan 9 2009, 05:39 AM) *
@ppyo: So it is hereby confirmed that the Akita bootkernel shows a kernel image in NAND, am I correct?
@Jon_J: On my SL-C3100 the kernel image in NAND also shows up in the bootmenu. Since you report that in your case cacko (in NAND) isn't shown, I wonder if your using the latest kernel (MD5: 7bf1d0f9c119892cb4cfd4526a880f5e). Could you check that?

If someone could confirm this for C7x0 also, this would be great. I just want to make sure that the different kernels are now all working fine. I tend to lose track sometimes huh.gif

Cheers,
cortez


Hi all

Finally got some time to work on my Z again.
I can happily report that as of today I have Zubuntu and Cacko running in my C1000! Cacko is running from internal flash!
I had to do a completely fresh reinstall of Cacko:
First, flash Cacko 1.23 original
Then flash Katastrophos kernel with sd modules (>1GB)
Finally, flash Cortez' kernel.
Ta daaaa!!! laugh.gif
*dances happily*

I might have to copy the whole thing to a 4GB sd card. 2GB is a little tight with 1 GB for Zubuntu, 450MB for Cacko (plus internal flash), and 420MB for a future distro (pdaXrom?). Or I might just turn the latter into a common /home partition.

On the Zubuntu side I am trying to deal with a few minor issues (lxlauncher is not stable, installed Ka/Pi, but will not sound alarms, etc...)
Again many, many thanks to Cortez for such an uber-cool achievement!!!

Gotta change signature to add Zubuntu!!! tongue.gif



ppyo, could you give a few more details as to how you were successful? Which Katastrophos kernal did you use? What Zimage is in your Cacko partition. I just tried this on my C1000 and ended up with a kernal panic when trying to boot cacko.


Ok, here we go, besides what I posted above:

Katastrophos kernel: http://katastrophos.net/zaurus/kernels/current
I used the one for Akita, of course. I like it because it has a nice sound driver. You may get good results with Tetsu's kernel too, but I have not tried Tetsu's. This is the zImage I used.

In your Cacko partition in the SD card you MUST have a boot directory containing the kernel file (ZImage), an Image.nfo text file (short distro description that will be used by the boot menu), and a kernel-cmdline text file.
My kernel-cmdline file looks like this:

CODE
console=ttyS0 root=/dev/mtdblock2 mtdparts=sharpsl-nand:7168k@0k(smf),32768k@7168k(root),-(home) jffs2_orphaned_inodes=delete EQUIPMENT=0 LOGOLANG=1 DEFYEAR=2006 LOGO=1 LAUNCH=q


After Cacko booted successfully for the first time I installed the modules that enable Cacko to work with SD cards greater than 1GB.
You must change fstab so Cacko will mount the correct SD partition as /mnt/card. Unchanged, it mounted the Zubuntu partition as it is the first one on my SD card.

I hope this covers all that you need. Good luck!


Thanks for your reply- but I just can't get this to work. I've been at it all morning with no success. Here's what I've got:

1) Fresh flash of Cacko 1.23 full
2) Flash Katastrophos kernal: sharprom-kernel-fastfpe-cachedfb (and I saved the zImage file for later use on SD)
3) boot Cacko first time and install module to mount >1 GB SD cards
4) fix fstab in Cacko to mount correct partition on SD
5) prepared SD card with 3 partitions: 1+GB ext2 for Zubuntu filesystem: 400 MB ext2 for Cacko: Linux Swap
6) created /boot directory in Cacko partition with zImage, image.nfo, and kernel-cmdline (your cmdline matched mine exactly when I checked on first Cacko boot)
7) Flash Zubuntu
8) boot Zubuntu- so far so good-and it looks great!
9) reboot and choose Cacko from list: this is where it all goes wrong. Cacko starts to boot like normal, but then lots of errors and a kernel panic.

And that's it. I can't figure out where I am going wrong with this.
Any suggestions would be much appreciated.

As for now, I need a break. Will try again later.
jfv
ppyo, you are the only one who reported successfully booting Cacko (or Sharp) using cortez's mutliboot kernel (internal flash or SD card) and it's not clear what's the magic. I was asking about the Katastrophe kernel to find out whether it was relevant for the successful boot.
ppyo
QUOTE(jfv @ Jan 24 2009, 03:03 PM) *
ppyo, you are the only one who reported successfully booting Cacko (or Sharp) using cortez's mutliboot kernel (internal flash or SD card) and it's not clear what's the magic. I was asking about the Katastrophe kernel to find out whether it was relevant for the successful boot.


I don't really know if the Katastrophos kernel is vital. I did not try with Cacko's original kernel, as I was going to use it as last resort...)
I don't know if it is relevant, but my SD card is a 2GB SD card (not SDHC), and all three partitions are ext2.
I did all the flashing from CF.
Hmpf... what else, what else?...
I can't think of anything else...
Sorry guys. But I'll try to answer all your questions to the best of my (very limited) ability.
Cheers!
pelrun
Are the errors related to missing files? The mtdparts option in kernel-cmdline must match the partition sizes in your internal flash.
mjiba
QUOTE(pelrun @ Jan 25 2009, 04:23 AM) *
Are the errors related to missing files? The mtdparts option in kernel-cmdline must match the partition sizes in your internal flash.


Actually, the errors, as far as I can read them as they scroll down the page, are strings of numbers (forgive my ignorance here-I'm sure a more experienced user could ID what they are) and then they stop with a kernel panic.
I am using the mtdparts option from Cacko after a fresh flash (found in /proc/mtdparts i believe). Mine happen to be the same a those posted earlier in this forum.
gsgmx
QUOTE(ppyo @ Jan 24 2009, 09:15 PM) *
QUOTE(jfv @ Jan 24 2009, 03:03 PM) *
ppyo, you are the only one who reported successfully booting Cacko (or Sharp) using cortez's mutliboot kernel (internal flash or SD card) and it's not clear what's the magic. I was asking about the Katastrophe kernel to find out whether it was relevant for the successful boot.


I don't really know if the Katastrophos kernel is vital. I did not try with Cacko's original kernel, as I was going to use it as last resort...)
I don't know if it is relevant, but my SD card is a 2GB SD card (not SDHC), and all three partitions are ext2.
I did all the flashing from CF.
Hmpf... what else, what else?...
I can't think of anything else...
Sorry guys. But I'll try to answer all your questions to the best of my (very limited) ability.
Cheers!


Hi ppyo,

your configuration is very near to my preferred setup i wish to have for my first trial of zubuntu.
I would like to have a save boot option if SD fails, so optimum is cacko totally bootable without SD.
Why - in the past SD card have failed in my zaurus - if they would again the Z would be useless until i have a new SD containing the needed partitions.
I don't understand why you still need a SD partition for cacko - you write you are booting cacko from internal flash?

Is the safe SD less boot still possible with your setup?

George
ppyo
QUOTE(gsgmx @ Jan 25 2009, 03:16 PM) *
QUOTE(ppyo @ Jan 24 2009, 09:15 PM) *
QUOTE(jfv @ Jan 24 2009, 03:03 PM) *
ppyo, you are the only one who reported successfully booting Cacko (or Sharp) using cortez's mutliboot kernel (internal flash or SD card) and it's not clear what's the magic. I was asking about the Katastrophe kernel to find out whether it was relevant for the successful boot.


I don't really know if the Katastrophos kernel is vital. I did not try with Cacko's original kernel, as I was going to use it as last resort...)
I don't know if it is relevant, but my SD card is a 2GB SD card (not SDHC), and all three partitions are ext2.
I did all the flashing from CF.
Hmpf... what else, what else?...
I can't think of anything else...
Sorry guys. But I'll try to answer all your questions to the best of my (very limited) ability.
Cheers!


Hi ppyo,

your configuration is very near to my preferred setup i wish to have for my first trial of zubuntu.
I would like to have a save boot option if SD fails, so optimum is cacko totally bootable without SD.
Why - in the past SD card have failed in my zaurus - if they would again the Z would be useless until i have a new SD containing the needed partitions.
I don't understand why you still need a SD partition for cacko - you write you are booting cacko from internal flash?

Is the safe SD less boot still possible with your setup?

George


I am booting Cacko from SD because that's the only way to have multiboot (Zubuntu, Cacko, other?). I am booting the Cacko kernel from SD card but the filesystem is in internal flash. I also use the SD card for extra storage.
SD cards will eventually fail. I am backing mine up about once a week. The safe way would be to have a backup SD card.
adf
QUOTE(pelrun @ Jan 25 2009, 01:23 AM) *
Are the errors related to missing files? The mtdparts option in kernel-cmdline must match the partition sizes in your internal flash.



tried using cat /proc/cmdline > kernel_cmdline

Got garbage, inode errors, and finally a spawning too fast error. Previously I'd been stuck on the cacko blue loading screen.
I'm trying the eviljazz fastfpe/framebuufer kernel, because cacko will be a z-pod (no sound in ubuntu, mplayer working) using quasar and kino2

Any suggestions?

other then the lack of sound, zubunty jaunty is running fine

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.