Grub2 mkconfig does not parse or read /etc/default/grub

ldelossa · #1 2nd March 2012, 03:37 AM

Hey guys, I have fedora 16 and I'm trying to set grub2 default's, wall paper, and hide recovery by adding entries in the grub file in /etc/default/grub. For some reason it doesnt seem grub is even looking at that file. Any ideas?

sonoran · #2 2nd March 2012, 04:17 AM

Did you add the arguments:

Code:

grub2-mkconfig -o /boot/grub2/grub.cfg

https://fedoraproject.org/wiki/Grub2

ldelossa · #3 2nd March 2012, 04:22 AM

Yeah I did all the normal commands and it finds each Linux image and windows os it just seems editing the grub default file doesn't do anything at all

JEO · #4 2nd March 2012, 04:32 AM

Perhaps if you posted the entries you put in the file it would help to determine the problem?

David Batson · #5 2nd March 2012, 06:45 AM

For some of the entries I read that the grub font has to be set.

http://www.fedoraforum.org/forum/sho....php?p=1557391

http://fedoraforum.org/forum/showthread.php?p=1556175

Dutchy · #6 2nd March 2012, 07:41 AM

Are you sure you've add the -o part?
Otherwise it is just a test run and nothing gets written.

ldelossa · #7 2nd March 2012, 02:41 PM

I'm at work right now away from my computer but I know that the /etc/defaults/grub file is completely unedited accept for adding GRUB_DEFAULT="my window 7 image name" No matter what options I put into there it doesn't change anything. Grub2 is simply not parsing the /etc/default/grub file, I saw on fedora site to put the grub default txt into /usr/local/etc/defaults/ but that didn't seem to work either, I will try to make-font command and see if that does anything when I get home later.

chrismurphy · #8 2nd March 2012, 07:03 PM

Confirm that the hardware is for sure BIOS only, and not UEFI firmware based (which uses GRUB Legacy EFI, not GRUB2).

Please post /etc/default/grub and /boot/grub2/grub.cfg

nsnbm · #9 3rd March 2012, 05:32 AM

Hello Idelossa,

I have made the error of not including what I added to the /etc/default/grub file within the double quotation marks. When my edits were outside those marks, grub2-mkconfig didn't read them. Ben.

ldelossa · #10 3rd March 2012, 06:15 PM

Quote:

Originally Posted by nsnbm

Hello Idelossa,

I have made the error of not including what I added to the /etc/default/grub file within the double quotation marks. When my edits were outside those marks, grub2-mkconfig didn't read them. Ben.

Yes I made sure everything is formatted correctly, and I do sys admin work with linux and I was playing around with Grub2, I'm very familiar with it It's just something special about fedora. I really think the mkfont option is going to fix it -- I just havent had access to my laptop yet haha.

chrismurphy · #11 3rd March 2012, 09:15 PM

It's doubtful there's anything special with Fedora. I regularly use /etc/default/grub to make behavioral modification, and grub2-mkconfig always honors that file.

leigh123linux · #12 3rd March 2012, 10:15 PM

post

Code:

cat /etc/default/grub

chrismurphy · #13 3rd March 2012, 10:21 PM

Yeah I asked for that and grub.cfg yesterday because I think there's either a syntax error in the grub file, or a mismatch between the desire default system naming in grub.cfg and what's been put into the grub file.

It's also possible that one of the scripts, or os-prober is puking on something, and not completing the script creation. So it would be useful to know if there is a /boot/grub/grub.cfg.new file present or not. If present, there's script failure occurring somewhere, then we'll have to use either set -x or bash -x to get more information on where the script is failing.

leigh123linux · #14 4th March 2012, 07:24 AM

Quote:

Originally Posted by chrismurphy

Yeah I asked for that and grub.cfg yesterday because I think there's either a syntax error in the grub file, or a mismatch between the desire default system naming in grub.cfg and what's been put into the grub file.

It's also possible that one of the scripts, or os-prober is puking on something, and not completing the script creation. So it would be useful to know if there is a /boot/grub/grub.cfg.new file present or not. If present, there's script failure occurring somewhere, then we'll have to use either set -x or bash -x to get more information on where the script is failing.

If he doesn't post the requested file I will close the thread (I hate time wasters).

chrismurphy · #15 4th March 2012, 08:27 PM

Personally I'd give to the end of Monday at least. Might be a work laptop not available over the weekend. OP said yesterday they haven't had access. But yes, it's like, you're having problems with GRUB "ignoring" /etc/default/grub and you don't post it first thing? What are the chances: user error vs "something special about Fedora".

I give it ~1000 to 1 odds.