Dualbooting/multiplebooting With Kexec!

[pasteur]

Which version? You can use the beta 3 flasher to resize it, than install r198, if that's what you're trying to do.

BETA3.
(I just wanted to install apps at /)

Reading your quote I am interested in flashing r198.
Can I use both r198 and debian with kexec?

[matthis]

I just tried cackofix0.2 and can't reboot sharprom anymore... looks bad!!

/root/.dev/_default.tar.gz: No such file or directory
mount: Could not find a spare loop device
mount: Mounting /dev/mtdblock3 on /home failed: No such file or directory
/etc/rc.d/rc.sysinit: /etc/ledmode: No such file or directory

and errors go on... what's the problem with loop device??

thanks

EDIT: I did the whole install.sh script backwards, putting back the original files and moving back the moved files etc... looks like I'm back to normal!!

I guess I'll do without the cackofix for now...

[linx]

Hello there I just tried to get my dualbooting zaurus up and working with Debian on Internal Disk and Cacko in NAND. I got a full working Cacko system I applied the patch for the hdd requirement and everything seemed to be ok even after I flashed eviljazz's better kernel. ( I couldn't make my wireless card to work but that's another issue) Then I fdisked my internal drive to a 5.7GB hda1 partition and the rest of the microdrive as swap. I put on hda1 the debian eabi rootfs of the other topic installed everything and then flashed with yonggun's latest 2.6.24.4 kernel with the updater.sh on the post from ZDevil. When I rebooted I had a problem loading Debian something about not mounting root filesystem properly then I tried fdisking again untaring again the debian eabi and this time I flashed yonggun's kernel with the angstorm updater.sh and gnu-tar. Everything worked alright I logged into Debian. I couldnt get the wifi network card working there either (I insert it i see those messages but there is no light blinking or anything, it's like it doesn't want to try to connect) anyway. I installed kexec-tools.deb and it asked me if i wanted to kexec a particular kernel at boot and I chose "0" no (not sure if i did the right thing) then I run the script after i put it and the eviljazz's kernel renamed to "sharp_zImage.bin" in the home folder...everything seems to run alright but when it goes rebooting it starts loading Cacko but  says something like:

lnode #<random number> was a directory with children - removing those too...
.
.
<a bunch of those messages with different numbers each time>
.
VFS: Mounted root (jffs2 filesystem) readonly
Freeing init memory: 84K
Kernel panic: No init found. Try passing init= option to kernel.

and that's it just stays there. I don't remember if i got these messages when i only had cacko installed, i think not. Any ideas what that is or what it may mean or how to solve it?
Since my debian install seems to be working properly. what can i do with the NAND if there is no easy solution to that problem? Just leave it like that?
Thank you very much in advance and sorry for the length of the post.
PS: I had that problem with "initial console" so I did something like MAKEDEV console and everything was ok after that.
PS2: btw that tune2fs command for journalising ext2 didn't work on my zaurus it just complained that tune2fs was not found.

[AltairTK]

Hello, i have a little problem with this procedure on Zaurus C1000.
I have install the latest Cacko 1.23 and upgraded Kernel.
I have a Debian EABI customized (named Andromeda http://yonggun.tistory.com/77) rootfs in the SD card which use a 2.6.24-4 yonggun Kernel and modules.
I follow the instructions for Cacko, sizing partition in NAND to 32Mb and, after flash, it's boot with any problems.
I flash yonggun Kernel 2.6.24-4 with your updater.sh (for C1000 only) and Debian boot...
The "Andromeda" have just included kexec. I have copy Cacko kernel into /boot directory, renamed cacko-zImage.bin and gave the commands:
kexec -u
kexec -l /boot/cacko-zImage.bin
kexec -e

Kernel start....but at the moment there are "2 milions"    of errors and terminate with a Kernel Panic: Attempted to kill init!
Where I wrong?
The procedure is not compatible with kernel 2.6.24-4?

I thank you for your help !

[xamindar]

Anyone still do this?

I tried following "2.1.2 Remove the required disk partitioning setting" and ended up with an unbootable system.  
I flashed the NAND of the japanese sharp rom
Then booted into the emergency D+B menu and ran the cackofix script.
Rebooted, and nothing.....just the startup screen staying there forever.

Does anyone know what I did wrong? I did this with a fresh nand of the japanese sharp rom so there shouldn't be anything wrong with it. Is this script really made for cacko and sharp rom?

I then flashed the tetsu kernel to see where it stops at and it gives a bunch of errors complaining about not finding a spare loop device, can't find /etc/ledmode, a bunch of /etc/rc.d/rc.sysinit missing files, and can't even find /etc/fstab! What in the world happened? Looks like that cackofix script erased a lot of important system files?

[nickk9]

I have the same problem as linx has.  But i have C1000, installed andromeda rootfs on SD and younggun's SD booting kernel over the working cacko in NAND. And have 'Kernel panic: No init found. Try passing init= option to kernel.' and the end of CACKO booting with kexec -e.

[xamindar]

Ok, I have a working debian system on my internal hard drive.
I also have a working sharp rom on NAND and I can boot to either one by flashing the apropriate kernel.

But I can NOT get kexec to work at all. When I launch the boot_sharp.sh  I get the initial sharp kernel starting to boot....then I get a lot of
"Child dir [random characters here] (ino #3374) of ino #3248 appears to be a hard link" with different ino numbers and then it spits out
"sh: can't access tty: job control turned off" and drops me to what looks like the emergency console of the sharp rom.

Anyone know what the issue is?  Has anyone even been successful booting the sharp rom with kexec? I don't see any success stories in here. Please help if you can, I am so close.

[pelrun]

The solution is exactly the same as for my pdaxrom kexec fix - you need to recompile the sharprom kernel with the correct NAND layout information hardcoded in it, otherwise it only sees a truncated filesystem.

[matthis]

@Pelrun

Could you explain this in more detail please?
I would be happy to build a kexec-ready sharprom kernel. I tried before but didn't know where/what to alter.

Thanks in advance.


Matthis

[xamindar]

The solution is exactly the same as for my pdaxrom kexec fix - you need to recompile the sharprom kernel with the correct NAND layout information hardcoded in it, otherwise it only sees a truncated filesystem.

Hmm, ok. Wonder why that info wasn't included in the howto. Seems like pretty important info. Thanks.
Anyone know if such a kernel exists? Or do I need to compile my own?
I was trying it with the tetsu kernel which I have really grown to love with all its nice tweeks. I wonder if the stock sharp kernel works - hence this issue not being mentioned in the howto.

[matthis]

OK, I found the way to go! Thanks Pelrun for the hint!! Only the boot params needed to be changed, so it was rather easy.

Since this topic is rather long I started a new one. Feel free to move it back here if necessary:

Kexec how-to really working: : see https://www.oesf.org/forum/index.php?showtopic=25983

[gojira]

You're essentially doing a "kexec -f" when switching to pdaXrom, which isn't ideal as debian doesn't get properly shut down first. The correct method is to edit /etc/init.d/reboot and add kexec -e just before /sbin/reboot. Then the pdaXrom boot procedure changes to:

Code: [Select]

kexec -l PDAXROMIMAGE
rebootDebian will shut down, and the system will restart into pdaXrom.

kexec-tools includes /etc/rc6.d/S85kexec, so now all you have to do is kexec -l then shutdown -r

Thanks for the tip. I did some searching and found this useful script for booting with kexec in a cleaner way: http://forums.debian.net/viewtopic.php?p=6...4704fd8a7f46ca3

I have modified it and attached it to the howto. I have tested it and it works great.

Now I am heading to compile a standard armel .deb of kexec-tools and will upload it if it works.

now you have kexec-tools you don't need that script at all (or just change it to "kexec -l /boot/zImage.whatever && shutdown -r now"