diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2013-February/022408.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2013-February/022408.html | 195 |
1 files changed, 195 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-February/022408.html b/zarb-ml/mageia-dev/2013-February/022408.html new file mode 100644 index 000000000..90053fc8d --- /dev/null +++ b/zarb-ml/mageia-dev/2013-February/022408.html @@ -0,0 +1,195 @@ +<!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=%3C510EA6E4.8070400%40earthlink.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="022352.html"> + <LINK REL="Next" HREF="022430.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=%3C510EA6E4.8070400%40earthlink.net%3E" + TITLE="[Mageia-dev] Grub2 vs. Grub Legacy in M3">mrmazda at earthlink.net + </A><BR> + <I>Sun Feb 3 19:05:24 CET 2013</I> + <P><UL> + <LI>Previous message: <A HREF="022352.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI>Next message: <A HREF="022430.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22408">[ date ]</a> + <a href="thread.html#22408">[ thread ]</a> + <a href="subject.html#22408">[ subject ]</a> + <a href="author.html#22408">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 2013-02-02 10:08 (GMT) Barry Jackson composed: + +><i> Felix Miata wrote: +</I> +>><i> Good start: +</I>>><i> 1-/boot/grub2/i386-pc/core.img in a Grub Legacy stanza succeeds +</I> +>><i> Not good from then on: +</I>>><i> 1-Grub2 error message due to not finding some png file +</I> +><i> You removed the png by using --no-suggests +</I> +One cannot remove what is not present. What I did was block installation of +packages that the grub2 package does not declare to be required. Grub2 should +not be configured to show user an error resulting from its own installation +misconfiguration. That looks like a bug. + +>><i> 2-25 item Grub 2.00 menu (grub.cfg: +</I>>><i> <A HREF="http://fm.no-ip.com/Tmp/Linux/Mdv/grub.cfg.gx27b-cauldron3-1.txt">http://fm.no-ip.com/Tmp/Linux/Mdv/grub.cfg.gx27b-cauldron3-1.txt</A> ). +</I>>><i> After selecting a selection from a master bootloader, there's no good +</I>>><i> reason to see similar selections as in the previous menu unrelated to +</I>>><i> the chosen selection. IOW, when not a master bootloader (i.e. +</I>>><i> "chainloaded" via core.img, only Mageia entries attributable to selected +</I>>><i> filesystem hosting core.img should be in this menu. +</I> +><i> If that is what you want then:- +</I>><i> # urpme os-prober +</I> +Why was it installed when I did 'urpmi --no-suggests grub2' if it's not +required? + +# urpme os-prober +To satisfy dependencies, the following 2 packages will be removed... + grub2-yada + os-prober-yada... + +>><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> +What's wrong with nice legible BIOS native fonts? + +>><i> 4-default menu selection for Cauldron causes this cmdline: +</I> +>><i> BOOT_IMAGE=/boot/vmlinuz-prv +</I>>><i> root=UUID=bbe8a402-5fb1-4247-b372-5bb6cff4e18c ro splash +</I> +>><i> which is nothing like the default Grub Legacy menu stanza's cmdline result: +</I> +>><i> root=LABEL=22cauldrn splash=verbose noresume video=1152x864 vga=794 3 +</I> +>><i> obviously caused by Grub2 installation disregarding content of +</I>>><i> pre-existing menu.lst .... +</I> +><i> grub2 does not pay any attention to legacy menu.lst - it's a totally +</I>><i> different, unrelated bootloader. +</I> +><i> If you want grub2 to use an existing legacy menu.lst then you can use +</I>><i> grub2-menulst2cfg tool to create a grub.cfg from menu.lst. +</I> +><i> Usage: grub2-menulst2cfg [INFILE [OUTFILE]] +</I> +Nice in theory, but the root device is off by -1. Default menu.lst cmdline +includes root=LABEL=22cauldrn instead of UUID or device name, which is +apparently disregarded by grub 2. + +menuentry 'Cauldron defkernel' { + legacy_kernel '(hd0,22)/boot/vmlinuz' '(hd0,21)/boot/vmlinuz' +'root=LABEL=22cauldrn' 'splash=verbose' 'noresume' 'video=1152x864' 'vga=794' +'3' '' + legacy_initrd '(hd0,22)/boot/initrd' '(hd0,21)/boot/initrd' +} + +It works when I s/hd0,21/hd0,22/g. + +>><i> 5-semi-legible blue on black graphical progress bar instead of normal +</I>>><i> complement of startup messages when splash=verbose +</I> +><i> The font colours were chosen to complement the background image which +</I>><i> you chose not to install. +</I> +I saw no fonts in that progress bar. I asked for no progress bar. + +>><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> +# lspci | grep VGA +00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated +Graphics Controller (rev 02) + +>><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> +grub2-menulst2cfg picked up the ones that work in Grub Legacy (vga= +((<A HREF="http://www.kernel.org/doc/Documentation/kernel-parameters.txt">http://www.kernel.org/doc/Documentation/kernel-parameters.txt</A>)) & video= +((<A HREF="http://www.kernel.org/doc/Documentation/fb/modedb.txt">http://www.kernel.org/doc/Documentation/fb/modedb.txt</A>))), which are kernel +parameters. They do the same thing loaded via Grub2 as when loaded via Grub +Legacy. + +>><i> 8-KDM is on tty2, the location I reserve for certain class of recurring +</I>>><i> activities, instead of where expected on tty7 +</I> +><i> Dunno - I have never seen this. +</I> +Booting with 3 on cmdline and later doing startx or init 5? On current boot I +used 3 on cmdline, logged in on tty2 & tty3, did startx on tty3, and found X +is running on tty3. On exiting the X session I did init 5. That put KDM on +tty1. On openSUSE & Fedora the problem is essentially the same, e.g.: +<A HREF="https://bugzilla.novell.com/show_bug.cgi?id=768788">https://bugzilla.novell.com/show_bug.cgi?id=768788</A> + +>><i> 9-preferred initial runlevel as evidenced by menu.lst cmdline options +</I>>><i> was not specified +</I> +><i> Again menu.lst is nothing to do with grub2 +</I> +Maybe grub2-menulst2cfg should be used instead of grub2-mkconfig when grub2 +is added to a system with grub previously installed. +-- +"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="022352.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI>Next message: <A HREF="022430.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22408">[ date ]</a> + <a href="thread.html#22408">[ thread ]</a> + <a href="subject.html#22408">[ subject ]</a> + <a href="author.html#22408">[ 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> |