Between me and my laptop.
Dear Lazyweb,
2.6.14.7-5 dmesg stuff:
...loading modules... (no mention of anything IDE or disk wise aside of VFS and RAMDISK)
RAMDISK: Compressed image found at block 0
VFS: Cannot open root device "hda3" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Using grub as a boot loader. I reinstalled several times to just make sure it's not grub. I rebuilt the initrd (using PLD's geninitrd) several times and it looks like the process went correctly, but still no boot. The kernel boots with the options "root=/dev/hda3 rootfstype=ext3", /boot being on hda1(ext2) and / on hda3(ext3) with swap on hda2.
When booting with 2.4.32 I get errors about kmod being unable to execute modprobe to include ext3, but I didn't rebuilt it's initrd so I imagine the initrd is working to that point since I'm not seeing those errors on the 2.6 dmesg.
I have the same result, in terms of kernal panic and leading up messages, whether I'm booting on the laptop or on my desktop so it's not the controller. There's no disk read errors so I imagine it's not the hard drive. Therefore it's software or PEBKAM(read: configuration error).
kthxbye
2.6.14.7-5 dmesg stuff:
...loading modules... (no mention of anything IDE or disk wise aside of VFS and RAMDISK)
RAMDISK: Compressed image found at block 0
VFS: Cannot open root device "hda3" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Using grub as a boot loader. I reinstalled several times to just make sure it's not grub. I rebuilt the initrd (using PLD's geninitrd) several times and it looks like the process went correctly, but still no boot. The kernel boots with the options "root=/dev/hda3 rootfstype=ext3", /boot being on hda1(ext2) and / on hda3(ext3) with swap on hda2.
When booting with 2.4.32 I get errors about kmod being unable to execute modprobe to include ext3, but I didn't rebuilt it's initrd so I imagine the initrd is working to that point since I'm not seeing those errors on the 2.6 dmesg.
I have the same result, in terms of kernal panic and leading up messages, whether I'm booting on the laptop or on my desktop so it's not the controller. There's no disk read errors so I imagine it's not the hard drive. Therefore it's software or PEBKAM(read: configuration error).
kthxbye