summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-July/017338.html
blob: 18ee77864b608763eb2679ef3835bdf4265b1c5f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
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>