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. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
