summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-July/017338.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-July/017338.html')
-rw-r--r--zarb-ml/mageia-dev/2012-July/017338.html168
1 files changed, 168 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-July/017338.html b/zarb-ml/mageia-dev/2012-July/017338.html
new file mode 100644
index 000000000..18ee77864
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-July/017338.html
@@ -0,0 +1,168 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] MGA2 Installer + Bootloader stage issue: initrd regeneration not happening?
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20MGA2%20Installer%20%2B%20Bootloader%20stage%20issue%3A%20initrd%0A%20regeneration%20not%20happening%3F&In-Reply-To=%3C5001BF33.8040901%40colin.guthr.ie%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="017335.html">
+ <LINK REL="Next" HREF="017339.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] MGA2 Installer + Bootloader stage issue: initrd regeneration not happening?</H1>
+ <B>Colin Guthrie</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20MGA2%20Installer%20%2B%20Bootloader%20stage%20issue%3A%20initrd%0A%20regeneration%20not%20happening%3F&In-Reply-To=%3C5001BF33.8040901%40colin.guthr.ie%3E"
+ TITLE="[Mageia-dev] MGA2 Installer + Bootloader stage issue: initrd regeneration not happening?">mageia at colin.guthr.ie
+ </A><BR>
+ <I>Sat Jul 14 20:49:23 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="017335.html">[Mageia-dev] MGA2 Installer + Bootloader stage issue: initrd regeneration not happening?
+</A></li>
+ <LI>Next message: <A HREF="017339.html">[Mageia-dev] MGA2 Installer + Bootloader stage issue: initrd regeneration not happening?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#17338">[ date ]</a>
+ <a href="thread.html#17338">[ thread ]</a>
+ <a href="subject.html#17338">[ subject ]</a>
+ <a href="author.html#17338">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>'Twas brillig, and Olivier Blin at 14/07/12 17:30 did gyre and gimble:
+&gt;<i> Colin Guthrie &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>&gt; writes:
+</I>&gt;<i>
+</I>&gt;&gt;<i> Hi,
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> While debugging <A HREF="https://bugs.mageia.org/show_bug.cgi?id=6692#c8">https://bugs.mageia.org/show_bug.cgi?id=6692#c8</A> I
+</I>&gt;&gt;<i> realised that the initrd is generated when the kernel is installed, but
+</I>&gt;&gt;<i> it's not regenerated again later.
+</I>&gt;<i>
+</I>&gt;<i> Hi,
+</I>&gt;<i>
+</I>&gt;<i> /root/drakx/ddebug.log might give some clue about what failed.
+</I>
+Not a huge deal in it that gives (me) clues:
+
+* starting step `setupBootloader'
+* to put in /mnt/etc/modprobe.preload evdev
+* modify_append:
+* modify_append: resume=UUID=f06016be-3bda-495d-900e-72f5c7d13a41
+* running: /sbin/display_driver_helper --is-kms-allowed with root /mnt
+* modify_append: nokmsboot resume=UUID=f06016be-3bda-495d-900e-72f5c7d13a41
+* bootloader::suggest_onmbr: type empty, onmbr 1, unsafe 0
+* adding /boot/vmlinuz-3.3.6-desktop-2.mga2
+* current labels: linux
+* adding /boot/vmlinuz-3.3.6-desktop-2.mga2
+* current labels: linux linux-nonfb
+* adding /boot/vmlinuz-3.3.6-desktop-2.mga2
+* current labels: linux linux-nonfb failsafe
+* looking for configured grub on partitions
+* setupBootloaderBefore end
+* step `setupBootloader' finished
+...
+* fs::get::device2part: unknown device &lt;&lt;/dev/sda&gt;&gt;
+* running: keytab-lilo.pl us with root /mnt
+* program not found: keytab-lilo.pl
+* writing grub config to /mnt/boot/grub/menu.lst
+* Installing boot loader...
+* running: sh /boot/grub/install.sh with root /mnt
+
+
+ GNU GRUB version 0.97 (640K lower / 3072K upper memory)
+
+ [ Minimal BASH-like line editing is supported. For the first word, TAB
+ lists possible command completions. Anywhere else TAB lists the possible
+ completions of a device/filename. ]
+grub&gt; root (hd0,0)
+ Filesystem type is ext2fs, partition type 0x83
+grub&gt; setup --stage2=/boot/grub/stage2 (hd0)
+ Checking if &quot;/boot/grub/stage1&quot; exists... no
+ Checking if &quot;/grub/stage1&quot; exists... yes
+ Checking if &quot;/grub/stage2&quot; exists... yes
+ Checking if &quot;/grub/e2fs_stage1_5&quot; exists... yes
+ Running &quot;embed /grub/e2fs_stage1_5 (hd0)&quot;... 17 sectors are embedded.
+succeeded
+ Running &quot;install --stage2=/boot/grub/stage2 /grub/stage1 (hd0)
+(hd0)1+17 p (hd0,0)/grub/stage2 /grub/menu.lst&quot;... succeeded
+Done.
+grub&gt; quit
+* step `summary' finished
+
+
+
+&gt;<i>
+</I>&gt;&gt;<i> I'm not sure why this isn't working but perhaps someone more familiar
+</I>&gt;&gt;<i> with the installer itself (TV?) could comment?
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> I was under the impression the initrd would be regenerated at the end?
+</I>&gt;&gt;<i> Does this even happen or have I just assumed this? I'm pretty sure in
+</I>&gt;&gt;<i> the past it did used to regenerate it but I could be mistaken.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> So the question then remains, how do we ensure that either:
+</I>&gt;&gt;<i> a) the initrd is regenerated at the end of the install process
+</I>&gt;<i>
+</I>&gt;<i> That's ensured at the bootloader installation step.
+</I>&gt;<i> If not present for every configured kernel, an initrd will be created.
+</I>
+What if the initrd is present? e.g. it was created when the kernel was
+installed. Would it still be REgenerated at this stage? (I always
+presumed it would be or that it was not generated at the install time).
+
+Looking at the script /sbin/installkernel I see:
+
+ [ -z &quot;$DURING_INSTALL&quot; ] || exit 0
+
+So it shouldn't do anything when run as part of the kernel post
+install... So perhaps some other package triggers an initrd generation?
+
+Looking at things happening live... I see that the symlink
+initrd-desktop.img is created, but it points nowhere. I wonder could one
+of the bootsplash scripts do something like resolve the symlink name and
+then recreate the initrd automatically because the file does not exist?
+
+
+Col
+
+--
+
+Colin Guthrie
+colin(at)mageia.org
+<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
+
+Day Job:
+ Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
+Open Source:
+ Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
+ PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
+ Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
+
+
+</PRE>
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="017335.html">[Mageia-dev] MGA2 Installer + Bootloader stage issue: initrd regeneration not happening?
+</A></li>
+ <LI>Next message: <A HREF="017339.html">[Mageia-dev] MGA2 Installer + Bootloader stage issue: initrd regeneration not happening?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#17338">[ date ]</a>
+ <a href="thread.html#17338">[ thread ]</a>
+ <a href="subject.html#17338">[ subject ]</a>
+ <a href="author.html#17338">[ 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>