On Tue, 20 Jan 2004, David B. Zafman wrote:
> Jiann-Ming Su wrote:
> >Okay, I compiled the RH kernel from the 0.9.96 release on my debian system.
> >I've downloaded Aneesh's new deb packages. But, I get the following boot
> >do_ssisys: Illegal op 44 in state 0
> >Usage: init 0123456SsQqAaBbCcUu
> >The system doesn't seem to freeze, but it doesn't continue any farther. I'm
> >able to reboot it with Ctrl-Alt-Del.
> I wonder if you are building a proper RAMDISK for debian. We modified
> the mkinitrd in redhat to add SSI specific action during boot. The
> "do_ssisys" by itself may not be a problem, but it does indicate that at
> the point the SSI initialization system calls have not been executed
> (state 0). The "Usage" from init is also very weird. Hopefully, Annesh
> has some insights.
Okay, I was able to run the ssi-create script successfully. As future
reference, you want to make sure /var/log isn't a mounted filesystem
because the script wants to move the existing log directory.
I made the initrd image as follows:
mkinitrd -d /etc/mkinitrd-openssi -r /dev/sda4 -o /tmp/initrd-2.4.20ssi.img /lib/modules/2.4.20-pre3/
It kindly gzipped it for me, and I added it to my boot directory. My grub
entry looks like
kernel /boot/vmlinuz-2.4.20-openssi root=/dev/sda4 init=/linuxrc
However, I still run into the same problem:
Trying to move old root to /initrd ... okay
Freeing unused kernel memory: 112k freed
do_ssisys: Illegal op 44 in state 0
Usage: init 0123456SsQqAaBbCcUu
The system doesn't lock up but just kind of hangs there. I can reboot with
Ctrl-Alt-Del. I'm not sure if this matters, but I'm booting with grub from
Jiann-Ming Su jsu2@... 404-712-2603
Development Team Systems Administrator
General Libraries Systems Division