On Thursday 21 April 2005 10:33 pm, Anders Johansson wrote:
On Friday 22 April 2005 06:03, Danny Sauer wrote:
I'm not sure. There's only one initrd in /boot, and it's whatever Yast put in there. I'm just doing this: kernel /boot/vmlinuz root=/dev/hda1 initrd /boot/vmlinux-2.6.8-24.10-default.gz
erm, what? That's not an initrd, that's a kernel. The initrd is called, well, initrd :)
There's a /boot/vmlinuz-2.6.8-24.10-default and a /boot/vmlinux-2.6.8-24.10-default.gz - note the z v/s x in the file name and the .gz extension on one. I figured that the x meant "this is an initrd, load me into memory". 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. There's a vmlinux-blah.gz and a symvers-blah.gz, and a grub directory (as well as an evil recursive symlink to /boot). There's also vmlinuz and vmlinuz-blah, which are both the same kernel as far as I can tell from booting them. :)
If that wasn't a typo in this mail then that would be why it doesn't boot. You seriously need an initrd with a reiserfs module in it
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? Let's assume that one of those .gz files actually is an initrd - is there a kernel command line that should force the loading of the reiserfs module? I'm wondering if maybe the lack of a module dep file is preventing the reiser module from automatically loading, maybe? What filesystems does the default kernel support? Just ext2, or could I redo this using ext3 for the root? --Danny, noting that this is the reason he doesn't use initrds - such a pain