diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2013-February/022448.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2013-February/022448.html | 162 |
1 files changed, 162 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-February/022448.html b/zarb-ml/mageia-dev/2013-February/022448.html new file mode 100644 index 000000000..abc7ab90e --- /dev/null +++ b/zarb-ml/mageia-dev/2013-February/022448.html @@ -0,0 +1,162 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Grub2 vs. Grub Legacy in M3 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Grub2%20vs.%20Grub%20Legacy%20in%20M3&In-Reply-To=%3C51103321.4070604%40earthlink.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="022483.html"> + <LINK REL="Next" HREF="022433.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Grub2 vs. Grub Legacy in M3</H1> + <B>Felix Miata</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Grub2%20vs.%20Grub%20Legacy%20in%20M3&In-Reply-To=%3C51103321.4070604%40earthlink.net%3E" + TITLE="[Mageia-dev] Grub2 vs. Grub Legacy in M3">mrmazda at earthlink.net + </A><BR> + <I>Mon Feb 4 23:16:01 CET 2013</I> + <P><UL> + <LI>Previous message: <A HREF="022483.html">[Mageia-dev] musical session locations +</A></li> + <LI>Next message: <A HREF="022433.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22448">[ date ]</a> + <a href="thread.html#22448">[ thread ]</a> + <a href="subject.html#22448">[ subject ]</a> + <a href="author.html#22448">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 2013-02-04 12:23 (GMT) Barry Jackson composed: + +><i> Felix Miata wrote: +</I> +>><i> On 2013-02-02 10:08 (GMT) Barry Jackson composed: +</I> +>>><i> Felix Miata wrote: +</I> +>>>><i> 3-Grub2 menu uses same awful spindly-looking font responsible in large +</I>>>>><i> part for my distaste for *buntu +</I> +>>><i> Yes could be a lot better, but it's mainly a choice based on licensing, +</I>>>><i> probably will be improved in the future. +</I> +>><i> What's wrong with nice legible BIOS native fonts? +</I> +><i> Try commenting out the line in /etc/defaults/grub +</I> +><i> #GRUB_THEME=... +</I> +Done on my first edit to the file. + +><i> and also temporarily rename /boot/grub2/fonts +</I> +Will try to remember if again presented with graphics mode fonts, which I'm +not currently getting due to either GRUB_GFXPOAYLOAD_text and/or +GRUB_TERMINAL_OUTPUT=console and/or grub2-menulst2cfg. + +><i> Run "grub2-mkconfig -o /boot/grub2/grub.cfg" +</I>><i> after changing anything in /etc/deafult/grub before rebooting. +</I> +><i> Is that better for you? +</I> +Will have to reserve that for after figuring out how to get stanzas sorted +acceptably. For now grub2-menulst2cfg as corrected is working better. Even +better is using the master bootloader to load kernel and initrd directly, but +here I'm trying out Grub2 now that it has advanced to v1.0 status. + +>>>><i> 6-post ESC, startup messages are inappropriately tiny +</I> +>>><i> Sounds like the same issue I used to have when I was using nvidia +</I>>>><i> graphics with nouveau. +</I>>>><i> Using intel I don't see this. +</I> +>><i> # lspci | grep VGA +</I>>><i> 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated +</I>>><i> Graphics Controller (rev 02) +</I> +><i> Hmm - dunno then - I do see a drop in size which appears to happen after +</I>><i> grub2 has handed over to the kernel. +</I> +I know what's happening, figured out within several months of the kernel devs +unleashing KMS into the wild. KMS responds to video= for selecting mode to +use for tty framebuffers. But before KMS initializes, the kernel responds to +vga= if present as it has for over a decade, replacing the default 80x25 mode +with whatever mode the vga= parameter corresponds to. + +Absent cmdline parameter for graphics mode init theme, quiet, or other means +to hide init messages, ttys are set to any supplied vga= framebuffer mode. +Shortly after the vga= response, KMS kicks in and switches to the video= mode +if present. If no valid video= mode is present, KMS initializes with the +EDID-provided PreferredMode, which here would be specified as 1600x1200, +corresponding to vga=0x31e (16 bit) or 0x31f (24 bit) if the gfxchip was +unsupported by KMS. + +Initial Grub2 installation isn't preconfigured with with any video=, so +without being kicked into a graphics init mode by Plymouth or otherwise, +first tty drawing is in 80x25 mode, shortly followed by KMS initializing EDID +PreferredMode 1600x1200, which is what results in the tiny text, 75 rows in a +12" vertical space, or about .16"/4.064mm per row, a bit over 11pt, which for +me is about 72% of optimal height produced by 1152x864. I use a "bigger" +display (21" nominal CRT) to make stuff bigger, not fit more stuff. + +>>>><i> 7-tty text is too tiny to use (same as startup messages; screen's +</I>>>>><i> preferred mode 1600x1200 used instead of legible mode 1152x864) +</I> +>>><i> Probably configurable in /etc/defaults/grub but off hand I don't know +</I>>>><i> the variable name - should be in the maunual somewhere. +</I> +><i> I'm suspecting this is not a grub2 issue but I may be wrong. +</I> +It's not directly. KMS is using whatever nominal size font is preconfigured +for the framebuffers. Whatever physical size font results depends for its +context on the EDID-provided video mode and the display's physical size. +Framebuffer fonts, except on *buntu, have been preconfigured the same across +all other distros I've used AFAICR since before I first began using Linux +last century. Grub2's part is that there isn't an installation option here +(that I remember) for the user to specify Grub2 pass a video= cmdline option +if he doesn't want the EDID PreferredMode used on the ttys. KMS has been +around so long I've already forgotten how Mandriva's installer was dealing +with the vga= option that was the usual pre-KMS method of sizing framebuffer +text. Pre-widescreen displays, vga=791 was pretty typical. +-- +"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 *** <A HREF="http://fm.no-ip.com/">http://fm.no-ip.com/</A> +</PRE> + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="022483.html">[Mageia-dev] musical session locations +</A></li> + <LI>Next message: <A HREF="022433.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22448">[ date ]</a> + <a href="thread.html#22448">[ thread ]</a> + <a href="subject.html#22448">[ subject ]</a> + <a href="author.html#22448">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |