Follow-up Comment #2, bug #29385 (project grub): I checked all of that pretty carefully before posting.
Here is the grub1 menu.lst entry: title 2.6.34-rc2 root (hd0,2) kernel (hd0,2)/boot/bzImage-2.6.34-rc2 root=/dev/hda7 vga=0x16c and the matching grub2 grub.cfg entry: menuentry "2.6.34-rc2" --class debian --class gnu-linux --class gnu --class os { insmod ext2 set root='(hd0,3)' #set gfxpayload=1024x768 linux (hd0,3)/boot/bzImage-2.6.34-rc2 root=/dev/hda7 } Note that there is no initrd involved. The only difference, apart from the apparently broken gfxpayload/vga support in this version of grub2, is that once the kernel is up and running, the linux apm module cannot run after the grub2 boot. The module is present and found in both cases. But the apm module issues the error message about the missing device after grub2 but not after grub1. Similar results on other at least one other module. For example, after a grub2 boot:- # modprobe apm FATAL: Error inserting apm (/lib/modules/2.6.34-rc2/kernel/arch/x86/kernel/apm.ko): No such device # ls -l /lib/modules/2.6.34-rc2/kernel/arch/x86/kernel/apm.ko -rw-r--r-- 1 root root 37190 Mar 30 17:17 /lib/modules/2.6.34-rc2/kernel/arch/x86/kernel/apm.ko _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?29385> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ _______________________________________________ Bug-grub mailing list Bug-grub@gnu.org http://lists.gnu.org/mailman/listinfo/bug-grub