1:54 p.m.
Hi, everyone,
My name is Les Howell. I do semiconductor test programs for mainframe
ATE.
My current issue is with GRUB2. I am slightly visually impaired due to
glaucoma. This is important, because setting my system up to use bigger
fonts is vital for me to use it. The problem I ran into when upgrading
to F17 from F16 is that the font settings do not work the same in Grub
2. I have worked very hard at finding solutions and using them from our
friend Google and from the forum, but have not yet been successful. My
issue is therefore of several parts:
1. Where can I find a really good manual on Grub2?
2. What is the exact process to upgrade the font to say size 18 or so
in Grub2?
3. What is the exact process to change the font and color in Grub2.
I found a solution that seemed to appear redundantly on various places
that suggested the following process:
A. find the font you want.
B. use # grub-mkfont inputfontname -o /grub/fonts/fontname
C. edit /etc/default/grub by adding a line to the new font as:
GRUB_FONT="/boot/grub2/fonts/fontname"
D. use # grub-mkcfg
I did these steps, but no joy. In addition, the fonts I tried all gave
me errors on one or more of the symbols (19 different fonts, mostly
mono-space or arial for visibility reasons.)
I know this is not a users forum, but this issue has implications that
need addressing at a much deeper stage.
It is difficult for me to research this due to the vision problem, and
it is important for me to be able to participate more.
Thank you for your attention.
2:20 p.m.
On 12/07/2012 07:54 PM, les wrote:
Hi, everyone,
My name is Les Howell. I do semiconductor test programs for mainframe
ATE.
My current issue is with GRUB2. I am slightly visually impaired due to
glaucoma. This is important, because setting my system up to use bigger
fonts is vital for me to use it. The problem I ran into when upgrading
to F17 from F16 is that the font settings do not work the same in Grub
2. I have worked very hard at finding solutions and using them from our
friend Google and from the forum, but have not yet been successful. My
issue is therefore of several parts:
1. Where can I find a really good manual on Grub2?
2. What is the exact process to upgrade the font to say size 18 or so
in Grub2?
3. What is the exact process to change the font and color in Grub2.
I found a solution that seemed to appear redundantly on various places
that suggested the following process:
A. find the font you want.
B. use # grub-mkfont inputfontname -o /grub/fonts/fontname
C. edit /etc/default/grub by adding a line to the new font as:
GRUB_FONT="/boot/grub2/fonts/fontname"
D. use # grub-mkcfg
I did these steps, but no joy. In addition, the fonts I tried all gave
me errors on one or more of the symbols (19 different fonts, mostly
mono-space or arial for visibility reasons.)
I know this is not a users forum, but this issue has implications that
need addressing at a much deeper stage.
It is difficult for me to research this due to the vision problem, and
it is important for me to be able to participate more.
Thank you for your attention.
|
Does it help reducing the resolution via GRUB_GFXMODE= like
GRUB_GFXMODE=640x480 ?
JBG
||
|
2:42 p.m.
On Fri, 2012-12-07 at 20:20 +0000, "Jóhann B. Guðmundsson" wrote:
On 12/07/2012 07:54 PM, les wrote:
> Hi, everyone,
> My name is Les Howell. I do semiconductor test programs for mainframe
> ATE.
>
> My current issue is with GRUB2. I am slightly visually impaired due to
> glaucoma. This is important, because setting my system up to use bigger
> fonts is vital for me to use it. The problem I ran into when upgrading
> to F17 from F16 is that the font settings do not work the same in Grub
> 2. I have worked very hard at finding solutions and using them from our
> friend Google and from the forum, but have not yet been successful. My
> issue is therefore of several parts:
> 1. Where can I find a really good manual on Grub2?
> 2. What is the exact process to upgrade the font to say size 18 or so
> in Grub2?
>
> 3. What is the exact process to change the font and color in Grub2.
>
> I found a solution that seemed to appear redundantly on various places
> that suggested the following process:
> A. find the font you want.
> B. use # grub-mkfont inputfontname -o /grub/fonts/fontname
> C. edit /etc/default/grub by adding a line to the new font as:
> GRUB_FONT="/boot/grub2/fonts/fontname"
> D. use # grub-mkcfg
>
> I did these steps, but no joy. In addition, the fonts I tried all gave
> me errors on one or more of the symbols (19 different fonts, mostly
> mono-space or arial for visibility reasons.)
> I know this is not a users forum, but this issue has implications that
> need addressing at a much deeper stage.
>
> It is difficult for me to research this due to the vision problem, and
> it is important for me to be able to participate more.
>
> Thank you for your attention.
>
>
Does it help reducing the resolution via GRUB_GFXMODE= like
GRUB_GFXMODE=640x480 ?
JBG
Hi, Johan,
Thank you for the suggestion. I didn't consider that, but I should
have.
But this time I ran grub2-mkconfig, whereas I think the first time I ran
grub-mkconfig. I could not find grub-mkconfig this time, so I must have
been incorrect.
Anyway, I edited /etc/default/grub and removed the font line and added
the GFXMODE line.
I ran the command grub2-mkconfig -o grub.cfg and got the following
errors:
It returned several errors:
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.6.8-2.fc17.x86_64
Found initrd image: /boot/initramfs-3.6.8-2.fc17.x86_64.img
Found linux image: /boot/vmlinuz-3.3.4-5.fc17.x86_64
Found initrd image: /boot/initramfs-3.3.4-5.fc17.x86_64.img
ERROR: ddf1: seeking device "/dev/dm-4" to 18446744073709421056
ERROR: hpt37x: seeking device "/dev/dm-4" to 4608
ERROR: hpt45x: seeking device "/dev/dm-4" to 18446744073709547008
ERROR: pdc: seeking device "/dev/dm-4" to 137438913024
ERROR: pdc: seeking device "/dev/dm-4" to 137438920192
ERROR: pdc: seeking device "/dev/dm-4" to 137438927360
ERROR: pdc: seeking device "/dev/dm-4" to 137438934528
ERROR: sil: seeking device "/dev/dm-4" to 18446744073709289984
No volume groups found
Found Windows Recovery Environment (loader)
on /dev/mapper/pdc_eadgiihiejp1
Found Windows 7 (loader) on /dev/mapper/pdc_eadgiihiejp2
done
I'm about to reboot and see what happens. I did save a backup of the
grub.cfg just incase.
thanks,
Les H
2:51 p.m.
On Fri, 2012-12-07 at 20:20 +0000, "Jóhann B. Guðmundsson" wrote:
On 12/07/2012 07:54 PM, les wrote:
> Hi, everyone,
> My name is Les Howell. I do semiconductor test programs for mainframe
> ATE.
>
> My current issue is with GRUB2. I am slightly visually impaired due to
> glaucoma. This is important, because setting my system up to use bigger
> fonts is vital for me to use it. The problem I ran into when upgrading
> to F17 from F16 is that the font settings do not work the same in Grub
> 2. I have worked very hard at finding solutions and using them from our
> friend Google and from the forum, but have not yet been successful. My
> issue is therefore of several parts:
> 1. Where can I find a really good manual on Grub2?
> 2. What is the exact process to upgrade the font to say size 18 or so
> in Grub2?
>
> 3. What is the exact process to change the font and color in Grub2.
>
> I found a solution that seemed to appear redundantly on various places
> that suggested the following process:
> A. find the font you want.
> B. use # grub-mkfont inputfontname -o /grub/fonts/fontname
> C. edit /etc/default/grub by adding a line to the new font as:
> GRUB_FONT="/boot/grub2/fonts/fontname"
> D. use # grub-mkcfg
>
> I did these steps, but no joy. In addition, the fonts I tried all gave
> me errors on one or more of the symbols (19 different fonts, mostly
> mono-space or arial for visibility reasons.)
> I know this is not a users forum, but this issue has implications that
> need addressing at a much deeper stage.
>
> It is difficult for me to research this due to the vision problem, and
> it is important for me to be able to participate more.
>
> Thank you for your attention.
>
>
Does it help reducing the resolution via GRUB_GFXMODE= like
GRUB_GFXMODE=640x480 ?
JBG
Hi, Johan,
No joy! Reboot then ran through the disk stuff, then a quick flash of
something about grub in big text, then back to the small text and
apparently the fine resolution screen. I could not trap the message
screen despite several attempts. I think there should be a grub log, so
I will look at the manual some more and work on figuring this out.
Thanks for your help.
For the developers, think about adding the grub change stuff to the
universal access stuff in some way. It is tough when it is hard to use
the various stuff to figure things out when you are working with a
disadvantage to begin with.
Thanks, Johan, and by the way, I found the manual this time in my web
search. I needed that.
1:46 a.m.
On Fri, 2012-12-07 at 12:51 -0800, les wrote:
Hi, Johan,
No joy! Reboot then ran through the disk stuff, then a quick flash of
something about grub in big text, then back to the small text and
apparently the fine resolution screen. I could not trap the message
screen despite several attempts. I think there should be a grub log, so
I will look at the manual some more and work on figuring this out.
Thanks for your help.
For the developers, think about adding the grub change stuff to the
universal access stuff in some way. It is tough when it is hard to use
the various stuff to figure things out when you are working with a
disadvantage to begin with.
Thanks, Johan, and by the way, I found the manual this time in my web
search. I needed that.
Hi Les, do the comments on this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=850783
help you in changing the font size at all? From memory, what you need to
do is edit /boot/grub2/themes/system/theme.txt and change the font sizes
specified there, then re-generate the grub2 config and possibly re-do
grub2-install (I forget exactly which steps are required). I'm not sure
if there's an 'update-safe' way of doing this.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
6:34 a.m.
On 12/08/2012 01:46 AM, Adam Williamson wrote:
I'm not sure
if there's an 'update-safe' way of doing this.
Instead of updating the "system" theme he could copy&paste the
/boot/grub2/themes/system directory and call it "/boot/grub2/themes/les"
and in /etc/default/grub add:
GRUB_THEME="/boot/grub2/themes/les/theme.txt"
1:22 p.m.
On Sat, 2012-12-08 at 06:34 -0600, Michael Cronenworth wrote:
On 12/08/2012 01:46 AM, Adam Williamson wrote:
> I'm not sure
> if there's an 'update-safe' way of doing this.
Instead of updating the "system" theme he could copy&paste the
/boot/grub2/themes/system directory and call it "/boot/grub2/themes/les"
and in /etc/default/grub add:
GRUB_THEME="/boot/grub2/themes/les/theme.txt"
Hi, guys,
I know I am doing something wrong, as it seems that there is still that
"flash" of a message that occurs. I think there is an error in the grub
file that is generated that prevents the changes from taking effect.
However I cannot locate the error in the script by looking at it, nor
can I find a log of the error message. Is there someplace special where
grub2 saves error messages?
As to the bugzilla, I could not load some of the attachments, nor do
the comments make sense to me of what needs to be done. The issue of
"update safe" is very important as well. Doing this once is tough
enough, and I am not sophisticated in scripting to write a solid script
to redo it again.
Anyway, here is what I need the screen to do:
1. increase the text size to something like 18 point when seen in Gedit
for example.
2. wait for up to 90 seconds so I can make it back from a cup of coffee
on a reboot (I write software and do simulations, which occasionally I
break the OS or memory overflows and even stuffs the swap space. I know
get more memory, but that will just delay the problem, not fix it.;0)
3. Hopefully last through the various system updates, or worst case be
simple enough to fix by a simple 1 or 2 file copy commands.
Changing font size and adding a delay would seem to be simple, but it
doesn't seem to be that way.
Thanks.
Les H
2:06 p.m.
On 2012-12-07 11:54 (GMT-0800) les composed:
My name is Les Howell. I do semiconductor test programs for
mainframe
ATE.
My current issue is with GRUB2. I am slightly visually impaired due
to
glaucoma. This is important, because setting my system up to use bigger
fonts is vital for me to use it. The problem I ran into when upgrading
to F17 from F16 is that the font settings do not work the same in Grub
2. I have worked very hard at finding solutions and using them from our
friend Google and from the forum, but have not yet been successful. My
issue is therefore of several parts:
1. Where can I find a really good manual on Grub2?
2. What is the exact process to upgrade the font to say size 18 or so in Grub2?
3. What is the exact process to change the font and color in Grub2.
I found a solution that seemed to appear redundantly on various places
that suggested the following process:
A. find the font you want.
B. use # grub-mkfont inputfontname -o /grub/fonts/fontname
C. edit /etc/default/grub by adding a line to the new font as:
GRUB_FONT="/boot/grub2/fonts/fontname"
D. use # grub-mkcfg
I did these steps, but no joy. In addition, the fonts I tried all
gave
me errors on one or more of the symbols (19 different fonts, mostly
mono-space or arial for visibility reasons.)
I know this is not a users forum, but this issue has implications that
need addressing at a much deeper stage.
It is difficult for me to research this due to the vision problem,
and
it is important for me to be able to participate more.
Is this problem restricted to machine(s) only you use?
If yes, were Grub Legacy behavior and features adequate for your needs?
If yes, consider removing Grub2 and installing Grub Legacy using CPIO and/or
MC and the instructions on
http://orgs.man.ac.uk/documentation/grub/grub_3.html#SEC9. That way Yum won't
try to remove or disturb it.
I don't install any bootloader during system installation when the only
bootloader option presented is Grub2, but I don't have any systems that
require features Grub Legacy lacks.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
8:07 p.m.
On Sat, 2012-12-08 at 15:06 -0500, Felix Miata wrote:
On 2012-12-07 11:54 (GMT-0800) les composed:
> My name is Les Howell. I do semiconductor test programs for mainframe
> ATE.
> My current issue is with GRUB2. I am slightly visually impaired due to
> glaucoma. This is important, because setting my system up to use bigger
> fonts is vital for me to use it. The problem I ran into when upgrading
> to F17 from F16 is that the font settings do not work the same in Grub
> 2. I have worked very hard at finding solutions and using them from our
> friend Google and from the forum, but have not yet been successful. My
> issue is therefore of several parts:
> 1. Where can I find a really good manual on Grub2?
> 2. What is the exact process to upgrade the font to say size 18 or so in Grub2?
> 3. What is the exact process to change the font and color in Grub2.
> I found a solution that seemed to appear redundantly on various places
> that suggested the following process:
> A. find the font you want.
> B. use # grub-mkfont inputfontname -o /grub/fonts/fontname
> C. edit /etc/default/grub by adding a line to the new font as:
> GRUB_FONT="/boot/grub2/fonts/fontname"
> D. use # grub-mkcfg
> I did these steps, but no joy. In addition, the fonts I tried all gave
> me errors on one or more of the symbols (19 different fonts, mostly
> mono-space or arial for visibility reasons.)
> I know this is not a users forum, but this issue has implications that
> need addressing at a much deeper stage.
> It is difficult for me to research this due to the vision problem, and
> it is important for me to be able to participate more.
Is this problem restricted to machine(s) only you use?
If yes, were Grub Legacy behavior and features adequate for your needs?
If yes, consider removing Grub2 and installing Grub Legacy using CPIO and/or
MC and the instructions on
http://orgs.man.ac.uk/documentation/grub/grub_3.html#SEC9. That way Yum won't
try to remove or disturb it.
I don't install any bootloader during system installation when the only
bootloader option presented is Grub2, but I don't have any systems that
require features Grub Legacy lacks.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
Hi, Felix,
I certainly could do that, but what would happen then to updates?
Would the tools be clobbered with the grub2 stuff later?
Meanwhile, the latest manual says to use grub-mkconfig, which doesn't
exist on my machine. There is however /sbin/grub2-mkconfig which I
would assume is the correct one.
If I invoke it with out a -o filename, I get the output to the screen
like a good unix command should ;-)
However that output contains the following:
---------------output text chunk on os-prober -------
### BEGIN /etc/grub.d/30_os-prober ###
ERROR: ddf1: seeking device "/dev/dm-4" to 18446744073709421056
ERROR: hpt37x: seeking device "/dev/dm-4" to 4608
ERROR: hpt45x: seeking device "/dev/dm-4" to 18446744073709547008
ERROR: pdc: seeking device "/dev/dm-4" to 137438913024
ERROR: pdc: seeking device "/dev/dm-4" to 137438920192
ERROR: pdc: seeking device "/dev/dm-4" to 137438927360
ERROR: pdc: seeking device "/dev/dm-4" to 137438934528
ERROR: sil: seeking device "/dev/dm-4" to 18446744073709289984
No volume groups found
Found Windows Recovery Environment (loader)
on /dev/mapper/pdc_eadgiihiejp1
menuentry 'Windows Recovery Environment (loader)
(on /dev/mapper/pdc_eadgiihiejp1)' --class windows --class os
$menuentry_id_option 'osprober-chain-9ACC23A9CC237E9F' {
insmod part_msdos
insmod ntfs
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root 9ACC23A9CC237E9F
else
search --no-floppy --fs-uuid --set=root 9ACC23A9CC237E9F
fi
drivemap -s (hd0) ${root}
chainloader +1
}
Found Windows 7 (loader) on /dev/mapper/pdc_eadgiihiejp2
menuentry 'Windows 7 (loader) (on /dev/mapper/pdc_eadgiihiejp2)' --class
windows --class os $menuentry_id_option
'osprober-chain-96DE247FDE2459AF' {
insmod part_msdos
insmod ntfs
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root 96DE247FDE2459AF
else
search --no-floppy --fs-uuid --set=root 96DE247FDE2459AF
fi
chainloader +1
}
### END /etc/grub.d/30_os-prober ###
-------------------------end of output text -----
Moreover the manual says the correct command syntax is:
grub-mkconfig -o /boot/grub/grub.cfg
There is no file: /boot/grub/grub.cfg
There is a file: /boot/grub2/grub.cfg
So I am thinking the following: my first attempts never wrote the file
at all. Moreover the date of the grub.cfg file in grub2 is earlier than
the date of the grub.cfg.bak backup I made.
Therefore my question is:
Should I invoke "grub2-mkconfig -o /boot/grub2/grub.cfg"
And will that take the changes made to the /etc/default/grub file? And
if this will work without messing things up, who will make the changes
to the grub manual (including updating the name to "grub2 manual"?
Are there other caveats to look out for?
I appreciate all your help guys. Thanks.
2:38 a.m.
On 2012-12-08 18:07 (GMT-0800) les composed:
On Sat, 2012-12-08 at 15:06 -0500, Felix Miata wrote:
> Is this problem restricted to machine(s) only you use?
> If yes, were Grub Legacy behavior and features adequate for your
needs?
> If yes, consider removing Grub2 and installing Grub Legacy using
CPIO and/or
> MC and the instructions on
> http://orgs.man.ac.uk/documentation/grub/grub_3.html#SEC9. That way Yum won't
> try to remove or disturb it.
> I don't install any bootloader during system installation
when the only
> bootloader option presented is Grub2, but I don't have any systems that
> require features Grub Legacy lacks.
I certainly could do that, but what would happen then to updates?
Which updates? Grub2 won't get updated if it isn't installed. You'll need to
update Grub's menu yourself at kernel update time. You can make that easier
on yourself by maintaining /boot/vmlinuz-cur and /boot/vmlinuz-prv symlinks
to the two most recent kernels and use the symlinks in Grub's menu. I have a
boot partition I don't mount as boot, and keep a fully self-maintained Grub
on it to use instead of all the Grubs installed to / partitions.
Once any Legacy Grub is installed and working properly, it _never_ needs to
be updated to a newer version. Only the boot menu needs to be kept maintained
to match the installed kernels and initrds. With the much more complex and
still significantly evolving Grub2, that's not so.
Would the tools be clobbered with the grub2 stuff later?
Which tools?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
12:06 p.m.
On 12/09/2012 02:38 AM, Felix Miata wrote:
Which updates? Grub2 won't get updated if it isn't installed.
You'll
need to update Grub's menu yourself at kernel update time. You can make
that easier on yourself by maintaining /boot/vmlinuz-cur and
/boot/vmlinuz-prv symlinks to the two most recent kernels and use the
symlinks in Grub's menu. I have a boot partition I don't mount as boot,
and keep a fully self-maintained Grub on it to use instead of all the
Grubs installed to / partitions.
Actually, grubby in Fedora is still perfectly capable of updating the
old grub.conf. To set this up, create a symlink:
# ln -s /boot/grub/grub.conf /etc
And create /etc/sysconfig/kernel:
# UPDATEDEFAULT specifies if new-kernel-pkg should make
# new kernels the default
UPDATEDEFAULT=yes
# DEFAULTKERNEL specifies the default kernel package type
DEFAULTKERNEL=kernel
Easy peasy
--
========================================================================
Ian Pilcher arequipeno(a)gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.
========================================================================
12:49 p.m.
On 12/09/2012 10:06 AM, Ian Pilcher wrote:
Actually, grubby in Fedora is still perfectly capable of updating
the
old grub.conf. To set this up, create a symlink:
# ln -s /boot/grub/grub.conf /etc
And create /etc/sysconfig/kernel:
# UPDATEDEFAULT specifies if new-kernel-pkg should make
# new kernels the default
UPDATEDEFAULT=yes
# DEFAULTKERNEL specifies the default kernel package type
DEFAULTKERNEL=kernel
Easy peasy
No, it's not "easy peasy". It's arguably incorrect on i686
with more than 3GB of RAM, where DEFAULTKERNEL=kernel-PAE
probably should be used. In any case it's incomplete
because it omits important documentation of this choice.
A comment should indicate which piece(s) look at the file:
# This file is consulted by /usr/sbin/new-kernel-pkg
# as part of installing a new Linux kernel.
Also, the "ln -s" could be improved:
# (cd /etc; ln -s ../boot/grub/grub.conf grub.conf)
The path should be relative, and naming the last component
redundantly as the last argument makes it clear that a new
path /etc/grub.conf resolves to ../boot/grub.grub.conf.
--
5:31 p.m.
On Sun, 2012-12-09 at 10:49 -0800, John Reiser wrote:
On 12/09/2012 10:06 AM, Ian Pilcher wrote:
> Actually, grubby in Fedora is still perfectly capable of updating the
> old grub.conf. To set this up, create a symlink:
>
> # ln -s /boot/grub/grub.conf /etc
>
> And create /etc/sysconfig/kernel:
>
> # UPDATEDEFAULT specifies if new-kernel-pkg should make
> # new kernels the default
> UPDATEDEFAULT=yes
>
> # DEFAULTKERNEL specifies the default kernel package type
> DEFAULTKERNEL=kernel
>
> Easy peasy
No, it's not "easy peasy". It's arguably incorrect on i686
with more than 3GB of RAM, where DEFAULTKERNEL=kernel-PAE
probably should be used. In any case it's incomplete
because it omits important documentation of this choice.
A comment should indicate which piece(s) look at the file:
# This file is consulted by /usr/sbin/new-kernel-pkg
# as part of installing a new Linux kernel.
Also, the "ln -s" could be improved:
# (cd /etc; ln -s ../boot/grub/grub.conf grub.conf)
The path should be relative, and naming the last component
redundantly as the last argument makes it clear that a new
path /etc/grub.conf resolves to ../boot/grub.grub.conf.
--
Ok, guys,
Here is the story. The command in the grub manual is wrong. You need
to use "# grub2-mkconfig -o /boot/grub2/grub.cfg"
Editing /etc/default/grub to set the default screensize works. The
second line with the wonderful uuid in it is waaayyy too long, but I can
at least read the stuff I need to and the wait now works.
I opened a terminal entered superuser and entered:
vi /etc/default/grub
entered insert mode with "i", then edited the GRUB_TIMEOUT line to be:
GRUB_TIMEOUT=90
and added at the end:
GRUB_GFXMODE=640x480
Then I :wq from vi, and backed up /boot/grub2/grug.cfg using:
cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.bak
And then ran:
# grub2-mkconfig -o /boot/grub2/grub.cfg"
Next I rebooted:
# reboot
When it came up things were as expected. The problem was the reference
to grub-mkconfig and the file to output, along with some other error I
made on the first entry.
Hope this helps someone else, and could someone please change the grub2
manual? The info is right in this message.
Thanks for all your help,
Les H
6:32 p.m.
On Dec 9, 2012, at 4:31 PM, les <hlhowell(a)pacbell.net> wrote:
Ok, guys,
Here is the story. The command in the grub manual is wrong. You need
to use "# grub2-mkconfig -o /boot/grub2/grub.cfg"
The upstream GRUB manual is correct, the issue is that it's renamed on Fedora to avoid
conflict with GRUB Legacy commands, e.g. grub-install vs grub2-install. It's
confusing.
Chris Murphy
5:44 p.m.
On Sun, 2012-12-09 at 17:32 -0700, Chris Murphy wrote:
On Dec 9, 2012, at 4:31 PM, les <hlhowell(a)pacbell.net> wrote:
>
> Ok, guys,
> Here is the story. The command in the grub manual is wrong. You need
> to use "# grub2-mkconfig -o /boot/grub2/grub.cfg"
The upstream GRUB manual is correct, the issue is that it's renamed on Fedora to
avoid conflict with GRUB Legacy commands, e.g. grub-install vs grub2-install. It's
confusing.
We should probably stop doing that for F19 when grub-legacy finally
goes...
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
1:27 p.m.
On Sun, 2012-12-09 at 03:38 -0500, Felix Miata wrote:
On 2012-12-08 18:07 (GMT-0800) les composed:
> On Sat, 2012-12-08 at 15:06 -0500, Felix Miata wrote:
>> Is this problem restricted to machine(s) only you use?
>> If yes, were Grub Legacy behavior and features adequate for your needs?
>> If yes, consider removing Grub2 and installing Grub Legacy using CPIO and/or
>> MC and the instructions on
>> http://orgs.man.ac.uk/documentation/grub/grub_3.html#SEC9. That way Yum
won't
>> try to remove or disturb it.
>> I don't install any bootloader during system installation when the only
>> bootloader option presented is Grub2, but I don't have any systems that
>> require features Grub Legacy lacks.
> I certainly could do that, but what would happen then to updates?
Which updates? Grub2 won't get updated if it isn't installed. You'll need to
update Grub's menu yourself at kernel update time. You can make that easier
on yourself by maintaining /boot/vmlinuz-cur and /boot/vmlinuz-prv symlinks
to the two most recent kernels and use the symlinks in Grub's menu. I have a
boot partition I don't mount as boot, and keep a fully self-maintained Grub
on it to use instead of all the Grubs installed to / partitions.
Once any Legacy Grub is installed and working properly, it _never_ needs to
be updated to a newer version. Only the boot menu needs to be kept maintained
to match the installed kernels and initrds. With the much more complex and
still significantly evolving Grub2, that's not so.
> Would the tools be clobbered with the grub2 stuff later?
Which tools?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
Which tools:
grub-mkconfig etc.
4155
days inactive
4158
days old
15 comments
8 participants
participants (8)
-
Adam Williamson -
Chris Murphy -
Felix Miata -
Howard Howell -
Ian Pilcher -
John Reiser -
Jóhann B. Guðmundsson -
Michael Cronenworth