diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2013-February/022430.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2013-February/022430.html | 245 |
1 files changed, 245 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-February/022430.html b/zarb-ml/mageia-dev/2013-February/022430.html new file mode 100644 index 000000000..82a23de90 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-February/022430.html @@ -0,0 +1,245 @@ +<!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=%3C510FA853.7000907%40zen.co.uk%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="022408.html"> + <LINK REL="Next" HREF="022447.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Grub2 vs. Grub Legacy in M3</H1> + <B>Barry Jackson</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Grub2%20vs.%20Grub%20Legacy%20in%20M3&In-Reply-To=%3C510FA853.7000907%40zen.co.uk%3E" + TITLE="[Mageia-dev] Grub2 vs. Grub Legacy in M3">zen25000 at zen.co.uk + </A><BR> + <I>Mon Feb 4 13:23:47 CET 2013</I> + <P><UL> + <LI>Previous message: <A HREF="022408.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI>Next message: <A HREF="022447.html">[Mageia-dev] musical session locations (was: Grub2 vs. Grub Leg...) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22430">[ date ]</a> + <a href="thread.html#22430">[ thread ]</a> + <a href="subject.html#22430">[ subject ]</a> + <a href="author.html#22430">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 03/02/13 18:05, Felix Miata wrote: +><i> On 2013-02-02 10:08 (GMT) Barry Jackson composed: +</I>><i> +</I>>><i> Felix Miata wrote: +</I>><i> +</I>>>><i> Good start: +</I>>>><i> 1-/boot/grub2/i386-pc/core.img in a Grub Legacy stanza succeeds +</I>><i> +</I>>>><i> Not good from then on: +</I>>>><i> 1-Grub2 error message due to not finding some png file +</I>><i> +</I>>><i> You removed the png by using --no-suggests +</I>><i> +</I>><i> One cannot remove what is not present. What I did was block installation +</I>><i> of packages that the grub2 package does not declare to be required. +</I>><i> Grub2 should not be configured to show user an error resulting from its +</I>><i> own installation misconfiguration. That looks like a bug. +</I>><i> +</I>>>><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> +</I>>><i> If that is what you want then:- +</I>>><i> # urpme os-prober +</I>><i> +</I>><i> Why was it installed when I did 'urpmi --no-suggests grub2' if it's not +</I>><i> required? +</I>><i> +</I>><i> # urpme os-prober +</I>><i> To satisfy dependencies, the following 2 packages will be removed... +</I>><i> grub2-yada +</I>><i> os-prober-yada... +</I>><i> +</I> +Right, sorry - I agree - I never really envisaged anyone not wanting +os-prober installed, however it should really be a Suggests - I will +change that. + +However I should have pointed out that it can be disabled in +/etc/defaults/grub with + +GRUB_DISABLE_OS_PROBER=true + +>>><i> 3-Grub2 menu uses same awful spindly-looking font responsible in large +</I>>>><i> part for my distaste for *buntu +</I>><i> +</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> +</I>><i> What's wrong with nice legible BIOS native fonts? +</I> +Try commenting out the line in /etc/defaults/grub + +#GRUB_THEME=... + +and also temporarily rename /boot/grub2/fonts + +Run "grub2-mkconfig -o /boot/grub2/grub.cfg" +after changing anything in /etc/deafult/grub before rebooting. + + +Is that better for you? + +><i> +</I>>>><i> 4-default menu selection for Cauldron causes this cmdline: +</I>><i> +</I>>>><i> BOOT_IMAGE=/boot/vmlinuz-prv +</I>>>><i> root=UUID=bbe8a402-5fb1-4247-b372-5bb6cff4e18c ro splash +</I>><i> +</I>>>><i> which is nothing like the default Grub Legacy menu stanza's cmdline +</I>>>><i> result: +</I>><i> +</I>>>><i> root=LABEL=22cauldrn splash=verbose noresume video=1152x864 +</I>>>><i> vga=794 3 +</I>><i> +</I>>>><i> obviously caused by Grub2 installation disregarding content of +</I>>>><i> pre-existing menu.lst .... +</I>><i> +</I>>><i> grub2 does not pay any attention to legacy menu.lst - it's a totally +</I>>><i> different, unrelated bootloader. +</I>><i> +</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> +</I>>><i> Usage: grub2-menulst2cfg [INFILE [OUTFILE]] +</I>><i> +</I>><i> Nice in theory, but the root device is off by -1. Default menu.lst +</I>><i> cmdline includes root=LABEL=22cauldrn instead of UUID or device name, +</I>><i> which is apparently disregarded by grub 2. +</I>><i> +</I>><i> menuentry 'Cauldron defkernel' { +</I>><i> legacy_kernel '(hd0,22)/boot/vmlinuz' '(hd0,21)/boot/vmlinuz' +</I>><i> 'root=LABEL=22cauldrn' 'splash=verbose' 'noresume' 'video=1152x864' +</I>><i> 'vga=794' '3' '' +</I>><i> legacy_initrd '(hd0,22)/boot/initrd' '(hd0,21)/boot/initrd' +</I>><i> } +</I>><i> +</I>><i> It works when I s/hd0,21/hd0,22/g. +</I>><i> +</I>That looks like an upstream bug - I will investigate. + +>>><i> 5-semi-legible blue on black graphical progress bar instead of normal +</I>>>><i> complement of startup messages when splash=verbose +</I>><i> +</I>>><i> The font colours were chosen to complement the background image which +</I>>><i> you chose not to install. +</I>><i> +</I>><i> I saw no fonts in that progress bar. I asked for no progress bar. +</I>><i> +</I> +OK remove the theme as above and set: + +GRUB_CMDLINE_LINUX="3" + +... for runlevel 3 and just remove the "splash" on that line for verbose +output. + +>>><i> 6-post ESC, startup messages are inappropriately tiny +</I>><i> +</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> +</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> +</I> +Hmm - dunno then - I do see a drop in size which appears to happen after +grub2 has handed over to the kernel. + +>>><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> +</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'm suspecting this is not a grub2 issue but I may be wrong. +><i> +</I>><i> grub2-menulst2cfg picked up the ones that work in Grub Legacy (vga= +</I>><i> ((<A HREF="http://www.kernel.org/doc/Documentation/kernel-parameters.txt">http://www.kernel.org/doc/Documentation/kernel-parameters.txt</A>)) & +</I>><i> video= ((<A HREF="http://www.kernel.org/doc/Documentation/fb/modedb.txt">http://www.kernel.org/doc/Documentation/fb/modedb.txt</A>))), which +</I>><i> are kernel parameters. They do the same thing loaded via Grub2 as when +</I>><i> loaded via Grub Legacy. +</I>><i> +</I>>>><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> +</I>>><i> Dunno - I have never seen this. +</I>><i> +</I>><i> Booting with 3 on cmdline and later doing startx or init 5? +</I> +I think that startx and init are deprecated in favour of proper systemd +commands now. + +><i> On current +</I>><i> boot I used 3 on cmdline, logged in on tty2 & tty3, did startx on tty3, +</I>><i> and found X is running on tty3. On exiting the X session I did init 5. +</I>><i> That put KDM on tty1. On openSUSE & Fedora the problem is essentially +</I>><i> 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>><i> +</I> +I don't think this is grub2 related. +Graphical desktop should default to tty1 now, however I have seen an +issue where it moves to tty7 after stopping and re-starting +prefdm.service. I have not checked this recently. + +>>><i> 9-preferred initial runlevel as evidenced by menu.lst cmdline options +</I>>>><i> was not specified +</I>><i> +</I>>><i> Again menu.lst is nothing to do with grub2 +</I>><i> +</I>><i> Maybe grub2-menulst2cfg should be used instead of grub2-mkconfig when +</I>><i> grub2 is added to a system with grub previously installed. +</I> +Yes that could be an option, although for the majority of users I +suspect that os-prober does what is needed. +</PRE> + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="022408.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI>Next message: <A HREF="022447.html">[Mageia-dev] musical session locations (was: Grub2 vs. Grub Leg...) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22430">[ date ]</a> + <a href="thread.html#22430">[ thread ]</a> + <a href="subject.html#22430">[ subject ]</a> + <a href="author.html#22430">[ 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> |