diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-July/017342.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-July/017342.html | 215 |
1 files changed, 215 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-July/017342.html b/zarb-ml/mageia-dev/2012-July/017342.html new file mode 100644 index 000000000..dd268b849 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-July/017342.html @@ -0,0 +1,215 @@ +<!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=%3C5001C538.20108%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="017341.html"> + <LINK REL="Next" HREF="017343.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=%3C5001C538.20108%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 21:15:04 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="017341.html">[Mageia-dev] MGA2 Installer + Bootloader stage issue: initrd regeneration not happening? +</A></li> + <LI>Next message: <A HREF="017343.html">[Mageia-dev] MGA2 Installer + Bootloader stage issue: initrd regeneration not happening? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#17342">[ date ]</a> + <a href="thread.html#17342">[ thread ]</a> + <a href="subject.html#17342">[ subject ]</a> + <a href="author.html#17342">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>'Twas brillig, and Colin Guthrie at 14/07/12 20:12 did gyre and gimble: +><i> 'Twas brillig, and Colin Guthrie at 14/07/12 20:04 did gyre and gimble: +</I>>><i> 'Twas brillig, and Colin Guthrie at 14/07/12 19:49 did gyre and gimble: +</I>>>><i> 'Twas brillig, and Olivier Blin at 14/07/12 17:30 did gyre and gimble: +</I>>>>><i> Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> writes: +</I>>>>><i> +</I>>>>>><i> Hi, +</I>>>>>><i> +</I>>>>>><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>>>>>><i> realised that the initrd is generated when the kernel is installed, but +</I>>>>>><i> it's not regenerated again later. +</I>>>>><i> +</I>>>>><i> Hi, +</I>>>>><i> +</I>>>>><i> /root/drakx/ddebug.log might give some clue about what failed. +</I>>>><i> +</I>>>><i> Not a huge deal in it that gives (me) clues: +</I>>>><i> +</I>>>><i> * starting step `setupBootloader' +</I>>>><i> * to put in /mnt/etc/modprobe.preload evdev +</I>>>><i> * modify_append: +</I>>>><i> * modify_append: resume=UUID=f06016be-3bda-495d-900e-72f5c7d13a41 +</I>>>><i> * running: /sbin/display_driver_helper --is-kms-allowed with root /mnt +</I>>>><i> * modify_append: nokmsboot resume=UUID=f06016be-3bda-495d-900e-72f5c7d13a41 +</I>>>><i> * bootloader::suggest_onmbr: type empty, onmbr 1, unsafe 0 +</I>>>><i> * adding /boot/vmlinuz-3.3.6-desktop-2.mga2 +</I>>>><i> * current labels: linux +</I>>>><i> * adding /boot/vmlinuz-3.3.6-desktop-2.mga2 +</I>>>><i> * current labels: linux linux-nonfb +</I>>>><i> * adding /boot/vmlinuz-3.3.6-desktop-2.mga2 +</I>>>><i> * current labels: linux linux-nonfb failsafe +</I>>>><i> * looking for configured grub on partitions +</I>>>><i> * setupBootloaderBefore end +</I>>>><i> * step `setupBootloader' finished +</I>>>><i> ... +</I>>>><i> * fs::get::device2part: unknown device <</dev/sda>> +</I>>>><i> * running: keytab-lilo.pl us with root /mnt +</I>>>><i> * program not found: keytab-lilo.pl +</I>>>><i> * writing grub config to /mnt/boot/grub/menu.lst +</I>>>><i> * Installing boot loader... +</I>>>><i> * running: sh /boot/grub/install.sh with root /mnt +</I>>>><i> +</I>>>><i> +</I>>>><i> GNU GRUB version 0.97 (640K lower / 3072K upper memory) +</I>>>><i> +</I>>>><i> [ Minimal BASH-like line editing is supported. For the first word, TAB +</I>>>><i> lists possible command completions. Anywhere else TAB lists the possible +</I>>>><i> completions of a device/filename. ] +</I>>>><i> grub> root (hd0,0) +</I>>>><i> Filesystem type is ext2fs, partition type 0x83 +</I>>>><i> grub> setup --stage2=/boot/grub/stage2 (hd0) +</I>>>><i> Checking if "/boot/grub/stage1" exists... no +</I>>>><i> Checking if "/grub/stage1" exists... yes +</I>>>><i> Checking if "/grub/stage2" exists... yes +</I>>>><i> Checking if "/grub/e2fs_stage1_5" exists... yes +</I>>>><i> Running "embed /grub/e2fs_stage1_5 (hd0)"... 17 sectors are embedded. +</I>>>><i> succeeded +</I>>>><i> Running "install --stage2=/boot/grub/stage2 /grub/stage1 (hd0) +</I>>>><i> (hd0)1+17 p (hd0,0)/grub/stage2 /grub/menu.lst"... succeeded +</I>>>><i> Done. +</I>>>><i> grub> quit +</I>>>><i> * step `summary' finished +</I>>>><i> +</I>>>><i> +</I>>>><i> +</I>>>>><i> +</I>>>>>><i> I'm not sure why this isn't working but perhaps someone more familiar +</I>>>>>><i> with the installer itself (TV?) could comment? +</I>>>>>><i> +</I>>>>>><i> I was under the impression the initrd would be regenerated at the end? +</I>>>>>><i> Does this even happen or have I just assumed this? I'm pretty sure in +</I>>>>>><i> the past it did used to regenerate it but I could be mistaken. +</I>>>>>><i> +</I>>>>>><i> So the question then remains, how do we ensure that either: +</I>>>>>><i> a) the initrd is regenerated at the end of the install process +</I>>>>><i> +</I>>>>><i> That's ensured at the bootloader installation step. +</I>>>>><i> If not present for every configured kernel, an initrd will be created. +</I>>>><i> +</I>>>><i> What if the initrd is present? e.g. it was created when the kernel was +</I>>>><i> installed. Would it still be REgenerated at this stage? (I always +</I>>>><i> presumed it would be or that it was not generated at the install time). +</I>>>><i> +</I>>>><i> Looking at the script /sbin/installkernel I see: +</I>>>><i> +</I>>>><i> [ -z "$DURING_INSTALL" ] || exit 0 +</I>>>><i> +</I>>>><i> So it shouldn't do anything when run as part of the kernel post +</I>>>><i> install... So perhaps some other package triggers an initrd generation? +</I>>>><i> +</I>>>><i> Looking at things happening live... I see that the symlink +</I>>>><i> initrd-desktop.img is created, but it points nowhere. I wonder could one +</I>>>><i> of the bootsplash scripts do something like resolve the symlink name and +</I>>>><i> then recreate the initrd automatically because the file does not exist? +</I>>><i> +</I>>><i> The initrd was generated at 12:49:00 So it was after these packages were +</I>>><i> installed that it happened.... +</I>>><i> +</I>>><i> Sat Jul 14 12:47:48 2012:lib64kms1 +</I>>><i> Sat Jul 14 12:47:48 2012:mageia-theme-common +</I>>><i> Sat Jul 14 12:47:58 2012:bootsplash +</I>>><i> Sat Jul 14 12:47:58 2012:bridge-utils +</I>>><i> Sat Jul 14 12:47:58 2012:dash +</I>>><i> Sat Jul 14 12:47:58 2012:plymouth-plugin-script +</I>>><i> Sat Jul 14 12:47:59 2012:plymouth +</I>>><i> Sat Jul 14 12:47:59 2012:plymouth-scripts +</I>>><i> Sat Jul 14 12:47:59 2012:plymouth-system-theme +</I>>><i> Sat Jul 14 12:48:00 2012:dracut +</I>>><i> Sat Jul 14 12:48:00 2012:mageia-theme-Default +</I>>><i> Sat Jul 14 12:48:07 2012:kernel-desktop-3.3.6-2.mga2 +</I>>><i> +</I>>><i> +</I>>><i> One of them must be the guilty party!! +</I>><i> +</I>><i> As there was a period where the symlink existed but the initrd did not, +</I>><i> I am presuming running /sbin/install kernel exited correctly without +</I>><i> creating the initrd. +</I>><i> +</I>><i> However, both plymouth and mageia-theme-Default seem to correctly honour +</I>><i> DURING_INSTALL. +</I>><i> +</I>><i> I'm confused as to what is causing it to be generated... can anyone else +</I>><i> see it? +</I> + +Oh wait, I think I see it: + +In the post of mageia-theme-Default it has: + +if [ "$1" == "0" ]; then + /usr/sbin/plymouth-set-default-theme -R Mageia-Default +fi + + +This causes an initrd rebuild (-R argument) and doesn't check +DURING_INSTALL. + +That's the problem. + +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="017341.html">[Mageia-dev] MGA2 Installer + Bootloader stage issue: initrd regeneration not happening? +</A></li> + <LI>Next message: <A HREF="017343.html">[Mageia-dev] MGA2 Installer + Bootloader stage issue: initrd regeneration not happening? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#17342">[ date ]</a> + <a href="thread.html#17342">[ thread ]</a> + <a href="subject.html#17342">[ subject ]</a> + <a href="author.html#17342">[ 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> |