On Sun, Feb 04, 2007 at 01:13:50PM -0500, Gmail wrote:
[Please trim your quotes]
This seems to get me part of the way there. I created a modified initrd
that does a modprobe -q hpt366 before it loads the generic ide module.
The hpt366 module was already in the initrd image. I modified my
Gmail wrote:
Hello. I'm running the 'testing' release. I found that once I upgrade
to the 2.6.18 kernel my box wouldn't boot.
[...]
What appears to be happening is that while the kernel starts to boot, it
seems to change the drive letter of the disk containing the / partition
to /dev/hde.
Nick Boyce wrote:
Gmail wrote:
Hello. I'm running the 'testing' release. I found that once I upgrade
to the 2.6.18 kernel my box wouldn't boot.
[...]
What appears to be happening is that while the kernel starts to boot, it
seems to change the drive letter of the disk containing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/03/07 22:56, Gmail wrote:
Hello. I'm running the 'testing' release. I found that once I upgrade
to the 2.6.18 kernel my box wouldn't boot.
The boot lines in my grub's menu.lst lines are (with different
variations for version number):
Thanks, Nick.
This seems to get me part of the way there. I created a modified initrd
that does a modprobe -q hpt366 before it loads the generic ide module.
The hpt366 module was already in the initrd image. I modified my
/etc/fstab to reflect hda instead of hde for the root drive.
My
Gmail wrote:
Thanks, Nick.
This seems to get me part of the way there. I created a modified initrd
that does a modprobe -q hpt366 before it loads the generic ide module.
The hpt366 module was already in the initrd image. I modified my
/etc/fstab to reflect hda instead of hde for the root
Hello. I'm running the 'testing' release. I found that once I upgrade
to the 2.6.18 kernel my box wouldn't boot.
The boot lines in my grub's menu.lst lines are (with different
variations for version number):
/boot/vmlinuz-2.6.18-3-686 root=/dev/hda1 ro vga=791
What appears to be happening
7 matches
Mail list logo
