[Th] geninitrd borked?

[Cezary Krzyzanowski]

Dnia 19-12-2006, wto o godzinie 23:24 +0100, Łukasz Jernaś napisał(a):

> root=0303 (tried /dev/hda3 also) I'll check the rest tomorrow, I can barely 
> see the screen now :/ 
> 

I've generated initrd almost identical as Your. I've booted it
successfully with 2.6.18.4_laptop-0.3 kernel.

[root at kacper ~]# geninitrd -v -f /boot/initrd-2.6.18.4_laptop-0.3.gz
`uname -r`
Finding IDE modules using ide_hostadapter
Finding IDE modules using PCI ID database
Using modules:  kernel/drivers/ide/ide-core.ko.gz
kernel/drivers/ide/pci/piix.ko.gz kernel/drivers/ide/ide-disk.ko.gz
kernel/fs/xfs/xfs.ko.gz
/bin/initrd-busybox -> /tmp/initrd.qlkO6P/bin/initrd-busybox
Loading module [ide-core] without options.
Loading module [piix] without options.
Loading module [ide-disk] without options.
Loading module [xfs] without options.
Adding rootfs finding based on root= option support.
1969 bloków

Output from geninitrd suggests we got the same initrd image. I've set
udev off (as nothing from Your geninitrd suggests udev) no splashes (FB
or BOOTSPLASH), just initramfs as the default initrdfs.

Please edit the init script and let the whole file for set -x, to show
where what gets fckd.

Cz at rny