Description of problem: when the notebook is rebooted both from windows7 and from fedora16, the menù of grub2 doesn't appear and fedora16 is automatically started. It seem a problem of the graphic board that doesn't replace it's framebuffer when notebook is rebooted, in fact setting a background for grub2 menu the graphic board is obliged to empty it's framebuffer and the menù appears normally. Version-Release number of selected component (if applicable): fedora16 and grub2 How reproducible: the problem arises just at reboot, not when the system is shutted down and turned on. Steps to Reproduce: 1. 2. 3. Actual results: To resolve the problem i have edited /etc/default/grub e setting GRUB_DEFAULT=0 instead of GRUB_DEFAULT=saved. But doing just this the menù the menu appeared to fragments, so i edited the same file to insert a background for grub2 menù. In this way the menù is readable. Expected results: i expect that this is solved in future for my graphic board. Additional info: my notebook: HP Pavilion g6-1105sl, 64bit. ----content of /etc/default/grub: GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="Fedora" GRUB_DEFAULT=0 GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 rd.luks=0 KEYTABLE=it LANG=en_US.UTF-8" GRUB_DISABLE_RECOVERY=true GRUB_GFXMODE=1024x768x32 GRUB_BACKGROUND=/sfondoalbero.png -----output of lspci -k|grep -iA 6 vga 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) Subsystem: Hewlett-Packard Company Device 1668 Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) Subsystem: Hewlett-Packard Company Device 1668 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) -----content of /boot/grub2/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then load_env fi set default="0" if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { insmod vbe insmod vga insmod video_bochs insmod video_cirrus } insmod part_msdos insmod ext2 set root='(hd0,msdos5)' search --no-floppy --fs-uuid --set=root d7aae254-1a91-4fa8-9181-948df1434dd5 if loadfont /grub2/unicode.pf2 ; then set gfxmode=1024x768x32 load_video insmod gfxterm fi terminal_output gfxterm insmod part_msdos insmod ext2 set root='(hd0,msdos6)' search --no-floppy --fs-uuid --set=root 391a8cdd-cdbd-4232-bf15-d4150eeaa049 insmod png background_image -m stretch /sfondoalbero.png set timeout=5 ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/10_linux ### menuentry 'Fedora Linux, with Linux 3.2.6-3.fc16.x86_64' --class fedora --class gnu-linux --class gnu --class os { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos5)' search --no-floppy --fs-uuid --set=root d7aae254-1a91-4fa8-9181-948df1434dd5 echo 'Loading Linux 3.2.6-3.fc16.x86_64 ...' linux /vmlinuz-3.2.6-3.fc16.x86_64 root=UUID=391a8cdd-cdbd-4232-bf15-d4150eeaa049 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 rd.luks=0 KEYTABLE=it LANG=en_US.UTF-8 echo 'Loading initial ramdisk ...' initrd /initramfs-3.2.6-3.fc16.x86_64.img } menuentry 'Fedora Linux, with Linux 3.2.5-3.fc16.x86_64' --class fedora --class gnu-linux --class gnu --class os { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos5)' search --no-floppy --fs-uuid --set=root d7aae254-1a91-4fa8-9181-948df1434dd5 echo 'Loading Linux 3.2.5-3.fc16.x86_64 ...' linux /vmlinuz-3.2.5-3.fc16.x86_64 root=UUID=391a8cdd-cdbd-4232-bf15-d4150eeaa049 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 rd.luks=0 KEYTABLE=it LANG=en_US.UTF-8 echo 'Loading initial ramdisk ...' initrd /initramfs-3.2.5-3.fc16.x86_64.img } menuentry 'Fedora Linux, with Linux 3.2.3-2.fc16.x86_64' --class fedora --class gnu-linux --class gnu --class os { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos5)' search --no-floppy --fs-uuid --set=root d7aae254-1a91-4fa8-9181-948df1434dd5 echo 'Loading Linux 3.2.3-2.fc16.x86_64 ...' linux /vmlinuz-3.2.3-2.fc16.x86_64 root=UUID=391a8cdd-cdbd-4232-bf15-d4150eeaa049 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 rd.luks=0 KEYTABLE=it LANG=en_US.UTF-8 echo 'Loading initial ramdisk ...' initrd /initramfs-3.2.3-2.fc16.x86_64.img } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/30_os-prober ### menuentry "Windows 7 (loader) (on /dev/sda1)" --class windows --class os { insmod part_msdos insmod ntfs set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root 846A1A506A1A3EFC chainloader +1 } menuentry "Windows Recovery Environment (loader) (on /dev/sda2)" --class windows --class os { insmod part_msdos insmod ntfs set root='(hd0,msdos2)' search --no-floppy --fs-uuid --set=root FE5E24575E240B4B drivemap -s (hd0) ${root} chainloader +1 } menuentry "Windows Recovery Environment (loader) (on /dev/sda3)" --class windows --class os { insmod part_msdos insmod ntfs set root='(hd0,msdos3)' search --no-floppy --fs-uuid --set=root BA4E901A4E8FCD97 drivemap -s (hd0) ${root} chainloader +1 } ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### ### BEGIN /etc/grub.d/90_persistent ### ### END /etc/grub.d/90_persistent ###
(In reply to comment #0) > when the notebook is rebooted both from windows7 and from fedora16, the menù of > grub2 doesn't appear and fedora16 is automatically started. ... > GRUB_GFXMODE=1024x768x32 > GRUB_BACKGROUND=/sfondoalbero.png These settings has not been created by anything Fedora. Please report the result if you remove these two lines and run grub2-mkconfig -o /boot/grub2/grub.cfg
Mads, I think the whole point of this report is that a reboot does not correctly show a grub menu, unless you force it to show a background (hence the two added lines in GRUB). In my own PC, I was never able to show it (with or without a background) but I assumed it was due to my lack of grub2-foo
(In reply to comment #1) > (In reply to comment #0) > > when the notebook is rebooted both from windows7 and from fedora16, the menù of > > grub2 doesn't appear and fedora16 is automatically started. > ... > > GRUB_GFXMODE=1024x768x32 > > GRUB_BACKGROUND=/sfondoalbero.png > > These settings has not been created by anything Fedora. > > Please report the result if you remove these two lines and run > grub2-mkconfig -o /boot/grub2/grub.cfg i have just tryed to follow this way, but the problem remained... these settings allow me to set the background for grub2 menu. (In reply to comment #2) > Mads, I think the whole point of this report is that a reboot does not > correctly show a grub menu, unless you force it to show a background (hence the > two added lines in GRUB). > > In my own PC, I was never able to show it (with or without a background) but I > assumed it was due to my lack of grub2-foo gianluca is right, and i have the same problem with archlinux and GRUB (not grub2). I think the problem is in the graphic board...
Ok, that has some similarities with Bug 810557 - Video mode not correctly set on warm boot (reboot) Bug 788429 - Backlight on Asus Eee PC 1005PEB does not work correctly (fixed) - it seems like something sometimes leaves the system in a state that doesn't work well with grub2. What grub2 version is used? Can you try with f17? (This issue will probably not be fixed in f16, but there might be chance that it works or can be fixed f17.)
Mads, in my case I think I'm using the latest F16 version of grub, grub2-1.99-13.fc16.2.x86_64. I can surely plan to switch on F17 that laptop. Is a regular upgrade (compared to a full reinstall) enough to have meaningful results?
Yes, any way of upgrading is fine - as long as a new boot loader is installed.
(In reply to comment #0) > Description of problem: [snip] > ----content of /etc/default/grub: > > GRUB_TIMEOUT=5 > GRUB_DISTRIBUTOR="Fedora" > GRUB_DEFAULT=0 > GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 > rd.luks=0 KEYTABLE=it LANG=en_US.UTF-8" > GRUB_DISABLE_RECOVERY=true > GRUB_GFXMODE=1024x768x32 > GRUB_BACKGROUND=/sfondoalbero.png > Hi, I', just had the exact same problem after installinf f17 (bug #825506), and solved it by adding the 'GRUB_GFXMODE' line, with the value in quotes: GRUB_GFXMODE="1024x768" Hope it helps. Regards, daniel.
(In reply to comment #7) > I', just had the exact same problem after installinf f17 (bug #825506) Daniel, are you sure you had exactly the same problem? In this report the menu works fine immediately after power on - the problem is that the video card doesn't get reset properly when rebooting without power off. In your report the video doesn't work at all, also not immediately after power on. ???
(In reply to comment #8) > > Daniel, are you sure you had exactly the same problem? In this report the > menu works fine immediately after power on - the problem is that the video > card doesn't get reset properly when rebooting without power off. In your > report the video doesn't work at all, also not immediately after power on. > ??? Mads, you're right, my mystake. Not exactly the same problem... obviously wasn't reading carefully. Sorry for the inconvenience, and thanks for your quick reply. Regards, daniel.
Ok, I just verified he bug is still there with Fedora 17.
Gianluca, in a comment 2 you said you didn't get as far as getting this problem. But now you can reproduce the original problem? What is in /etc/default/grub - and have you run grub2-install and grub2-mkconfig?
Mads, the "I was never able to show it" in comments 2 refers to grub graphics. In other words, I could always see the issue on a warm boot, and never managed to workaround it by setting a background I hope this sentence is more clear, as you probably guessed, English is not my mother tongue... Now, I checked into /etc/default and the upgrade process left me with a grub.rpmnew file. I renamed it to grub and run grub2-mkconfig. The result is visible grub menu (at last!) even on warm boot, but text only. I am not sure if it was supposed to have the fireworks background seen on Mairin's blog, but at least I can pick the correct item on every boot.
Could you tell what Preffered mode in the output of "videoinfo" command in the shell is. What is the resolution of the panel in question? Could you try the patch I've attached to the bug report #827003 ?
The patch is included in the unofficial beta6 scratch build on http://koji.fedoraproject.org/koji/taskinfo?taskID=4121699 Install grub2 and grub2-tools rpms, grub2-install /dev/sda grub2-mkconfig -o /boot/grub2/grub.cfg
Created attachment 588921 [details] videoinfo output I installed the rpms from the scratch build and they seem to perform as well as the previous ones, that is, menu is visible on warm boot but no other graphic is there (still not sure that's normal or not) A screenshot of videoinfo is attached (is there a better way to grab that screen besides using a camera?). The panel seems to be properly recognized, it's one of those common 1366x768 ones.
Sorry, I'm a little bit confused and not sure which problems still persisnt in F17. If I understand correctly only missing background is the issue. If so then bug is fixed since there isn't supposed to be a background in the first place unless you set some. Mi dispiace ma ho un poce delle probleme di capirte. Se capisco cortaamente la unica problema che rimane in F17 è che non hai il imagine del fondo. Se questo è vero alora questo bug è già coretto prechè non c'è un imagine del fondo se non hai instalato manualemente. Se la lingua è una problema per te possiamo continuare in italiano.
Yeah, in comment #12 I said the menu is now working as expected both with cold or warm start. I just was not sure whether the background was expected to show or not, so I guess you can close this. Thank you very much (and kudos for the Italian part :))
Ok, thanks. I assume Francesco agree with you ;-) Mairin's menu theme was dropped from the /etc/default/grub created by anaconda because of reported performance problems. You can get it with: GRUB_THEME=/boot/grub2/themes/system/theme.txt there is better performance with a simple background image: GRUB_BACKGROUND="/boot/grub2/themes/system/background.png"
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.