Hi,
(Note that I've been rolling my own kernels since 2.6.0, and was
even able to make 2.6.27 work.)
The boot error is:
Cannot open root UUID=blah-blah-fa6507 or unknown-block(0,0)
The big difference between Now and Then is that I also moved from
booting off of /dev/hda using lilo to /dev/sda using grub2.
In my home-rolled kernel, I don't use an initrd because I compile in
the relevant fs and chipset drivers.
Here are the (I think) relevant portions of grub.cfg:
### BEGIN /etc/grub.d/00_header ###
set root=(hd1,2)
search --fs-uuid --set [snip]fa6507
### BEGIN /etc/grub.d/05_debian_theme ###
set root=(hd1,2)
search --fs-uuid --set [snip]fa6507
### BEGIN /etc/grub.d/10_linux ###
set root=(hd1,2)
search --fs-uuid --set ec2cfda3-185d-4d41-a708-01472ffa6507
menuentry "Linux 2.6.28smp64" {
set root=(hd1,2)
linux /boot/vmlinuz-2.6.28smp64 root=UUID=[snip]fa6507 ro
}
menuentry "Debian GNU/Linux, linux 2.6.28-1-amd64" {
linux /boot/vmlinuz-2.6.28-1-amd64 root=UUID=[snip]fa6507 ro
initrd /boot/initrd.img-2.6.28-1-amd64
}
$ grep EXT[23] /usr/src/linux/.config
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
Any (helpful) thoughts?
--
Ron Johnson, Jr.
Jefferson LA USA
"I am not surprised, for we live long and are celebrated poopers."
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
