From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2013-February/022446.html | 137 +++++++++++++++++++++++++++ 1 file changed, 137 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-February/022446.html (limited to 'zarb-ml/mageia-dev/2013-February/022446.html') diff --git a/zarb-ml/mageia-dev/2013-February/022446.html b/zarb-ml/mageia-dev/2013-February/022446.html new file mode 100644 index 000000000..0edb4d8a1 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-February/022446.html @@ -0,0 +1,137 @@ + + + + [Mageia-dev] Grub2 vs. Grub Legacy in M3 + + + + + + + + + +

[Mageia-dev] Grub2 vs. Grub Legacy in M3

+ Barry Jackson + zen25000 at zen.co.uk +
+ Mon Feb 4 21:27:45 CET 2013 +

+
+ +
On 04/02/13 19:18, Felix Miata wrote:
+> On 2013-02-04 14:27 (GMT) Barry Jackson composed:
+>
+>> Felix Miata wrote:
+>
+>>> 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.
+>
+>> Maybe a limitation of legacy_kernel.
+>> Normally to use labels in grub2 the 'search' command is used without any
+>> reference to the device assignment.
+>> Like:-
+>
+>> menuentry 'Mageia-2 multiboot' {
+>> search --no-floppy --label --set=root mageia-2
+>> multiboot /boot/grub2/i386-pc/core.img
+>> }
+>
+>>> 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.
+>
+>> That syntax is apparently correct, as legacy_kernel needs to know what
+>> the original legacy command was.
+>> I have tested here in a clean mga3 installation and it works for me.
+>
+>> Please re-test and if it fails again please attach the original menu.lst
+>> and the resulting grub.cfg along with any error messages.
+>
+> It's entirely unclear what "re-test" here means, unless maybe by
+> incorporating your immediately preceding thread response. Current
+> behavior of Grub2 menu overall and first grub.cfg stanza is acceptable
+> having used/using the following:
+>
+> http://fm.no-ip.com/Tmp/Linux/Mdv/menu.lst.04-cldrn-gx27b.txt
+>
+> http://fm.no-ip.com/Tmp/Linux/Mdv/etc-default-grub-cldrn-gx27b.txt
+>
+> http://fm.no-ip.com/Tmp/Linux/Mdv/grub.cfg.06-cldrn-gx27b.txt
+>
+> Only error message I recall is about vga= from Grub2 before first
+> kernel/init messages appear.
+
+I was referring to re-testing the use of grub2-menulst2cfg again, since 
+it works perfectly here.
+
+If you truly get errors from the grub.cfg produced by it then I would 
+like to report this upstream. I suspect there is something slightly 
+unusual in your menu.lst that it can't handle, so we will need both 
+menu.lst and the output .cfg, plus any error messages that may be useful.
+
+Since your comments earlier I have decided to split out the theme into a 
+separate package, so that a minimal installation using grub2 will not 
+pull in the font, image etc.
+
+I have pushed a new version that Suggests: os-prober in the meantime.
+
+So, in future an install of grub2 with --no-suggests will be without a 
+theme or os-prober, and perform as per the modifications I suggested above.
+
+Thanks for your constructive comments Felix,
+
+Barry
+
+
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1