Hi Ben,
ok, I already use linux-image-2.6.32-5-686 and there it works, as
already posted above.
I thougt trunk is the newest one, because of the "pole position" in
grub.cfg:
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, with Linux 2.6.32-trunk-686" --class debian
--class gnu-linux --class gnu --class os {
insmod ext2
set root='(/dev/sda,2)'
search --no-floppy --fs-uuid --set
0f631a94-878c-4a49-970a-694cac15e33f
echo Loading Linux 2.6.32-trunk-686 ...
linux /boot/vmlinuz-2.6.32-trunk-686
root=UUID=0f631a94-878c-4a49-970a-694cac15e33f ro quiet
echo Loading initial ramdisk ...
initrd /boot/initrd.img-2.6.32-trunk-686
}
menuentry "Debian GNU/Linux, with Linux 2.6.32-trunk-686 (recovery
mode)" --class debian --class gnu-linux --class gnu --class os {
insmod ext2
set root='(/dev/sda,2)'
search --no-floppy --fs-uuid --set
0f631a94-878c-4a49-970a-694cac15e33f
echo Loading Linux 2.6.32-trunk-686 ...
linux /boot/vmlinuz-2.6.32-trunk-686
root=UUID=0f631a94-878c-4a49-970a-694cac15e33f ro single
echo Loading initial ramdisk ...
initrd /boot/initrd.img-2.6.32-trunk-686
}
menuentry "Debian GNU/Linux, with Linux 2.6.32-5-686" --class debian
--class gnu-linux --class gnu --class os {
insmod ext2
set root='(/dev/sda,2)'
search --no-floppy --fs-uuid --set
0f631a94-878c-4a49-970a-694cac15e33f
echo Loading Linux 2.6.32-5-686 ...
linux /boot/vmlinuz-2.6.32-5-686
root=UUID=0f631a94-878c-4a49-970a-694cac15e33f ro quiet
echo Loading initial ramdisk ...
initrd /boot/initrd.img-2.6.32-5-686
}
IMHO it would be better to use a name for the kernels which enables
update-grub to build the grub.cfg / menu.lst in the right order.
cu,
Ralf
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c18b3a1.9050...@family-moll.de
