The Thursday 2005-04-21 at 23:55 -0500, Danny Sauer wrote:
When I try to specify "kernel /boot/vmlinux-2.6.8-24.10-default.gz" grub says "invalid format", but when I specify "initrd /boot/vmlinux-2.6.8-24.10-default.gz" grub says it found a Linux initrd. It says that for vmlinuz as well, though, so I think maybe it treats anything unknown as a Linux initrd...
Either way, theres no file called /boot/initrd.
I think it gets created during the install. And yes, it works fine in a chroot, I tried once.
The packages all installed successfully, where would an initrd have come from? Wouldn't that be in the same package as the kernel? Is it installed somewhere other than /boot, or at a later time in the install process?
It comes either in the rpm kernel package, or it is created during the install run. Perhaps both. I'll try to check. [...] Ah, yes (suse 9.3): cer@nimrodel:~> rpm -q -f /boot/vmlinuz-2.6.11.4-20a-default \ /boot/initrd-2.6.11.4-20a-default kernel-default-2.6.11.4-20a kernel-default-2.6.11.4-20a If yours is missing, something failed.
What filesystems does the default kernel support? Just ext2, or could I redo this using ext3 for the root?
Both ext2/3 would work. Actually, ext3 also uses modules, in the initrd, but as it can be mounted as ext2, it does so. Later, when running, you can perhaps remount as ext3 (automatic :-? ), create the proper initrd, and reboot.
--Danny, noting that this is the reason he doesn't use initrds - such a pain
Funny you didn't notice before :-) I hope you get your hardware working. Next time, don't use a metal table top ;-) -- Cheers, Carlos Robinson