Bug 751829

Summary: GRUB2 doesn't honor settings in /etc/default/grub
Product: [Fedora] Fedora Reporter: hannes <johannes.lips>
Component: grub2Assignee: Peter Jones <pjones>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: dennis, mads, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-16 21:47:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
etc/default/grub and /boot/grub2/grub.cfg none

Description hannes 2011-11-07 17:34:07 UTC
Created attachment 532101 [details]
etc/default/grub and /boot/grub2/grub.cfg

Description of problem:
Whatever values I define in /etc/default/grub /sbin/grub2-mkconfig -o /boot/grub2/grub.cfg does not write them into /boot/grub2/grub.cfg

Version-Release number of selected component (if applicable):
rpm -qa grub2\*
grub2-1.99-12.fc16.x86_64


How reproducible:
always


Actual results:
640x480 resolution in grub and during bootup.

Expected results:
Resolution which fits to my screen.

Additional info:

Comment 1 Mads Kiilerich 2011-11-09 18:23:19 UTC
Is grub.cfg not updated (check the timestamp) or do the settings not work as you expected?

What should your /etc/default/grub settings do - and which documentation says so?

(See also http://ask.fedoraproject.org/question/74/vga0x307-is-deprecated-but-cant-get-gfxmode-to?answer=132#132 )

Comment 2 hannes 2011-11-09 19:18:59 UTC
I think my entry in /etc/default/grub was wrong it should rather be:
GRUB_GFXPAYLOAD_LINUX=1280x800
and not just GRUB_GFXMODE=1280x800. This seems to set the right resolution.

Comment 3 Mads Kiilerich 2011-11-10 22:03:17 UTC
hannes, please be more explicit. 

Has the issue been 'gone away'?

Or can you provide more information and clarify what the problem is?

Comment 4 Mads Kiilerich 2012-04-16 21:47:56 UTC
No response - assuming the problem has been solved.