From: Kelledin (kelledin+AXPskarpsey.dyndns.org)
Date: Sun Oct 12 2003 - 02:05:13 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sunday 12 October 2003 01:29 am, Arkadiy Chapkis - Arc wrote:
> Right now I still cannot boot new kernel due to some issues
> with ramdisk - seems like mkinitrd didn't creat proper image,
> I mounted it on loopback and saw only two files there:
> /bin/insmod and /bin/nash. Comparing to the 2.4.18-27.7 one
> that I have from distro, it's nothing. And the error I'm
> getting is: VFS: Cannot open root device sda1....

If you're compiling your own kernel, you might as well just link
your boot-time drivers statically and dispense with a ramdisk.
;-)

AFAIK the new 2.6 style of initrd is changed, btw, but I haven't
checked into exactly what's different. Something called
initramfs IIRC. I suspect it takes some new fancy dancing to
build an initrd under 2.6, which would explain your initrd
troubles.

HTH,

--
Kelledin
"If a server crashes in a server farm and no one pings it, does
it still cost four figures to fix?"

_______________________________________________
Axp-list mailing list
Axp-listredhat.com
https://www.redhat.com/mailman/listinfo/axp-list

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]