1 |
Ahh, now that I understand your question it is clear to me that I don't |
2 |
know the answer ;-) Sorry! |
3 |
|
4 |
David Wilk wrote: |
5 |
|
6 |
>Sure, and that's what I tried first. I had a separate initrd line |
7 |
>(for lilo) like you have below and lilo would only load the initrd and |
8 |
>not the initramfs in the kernel. I need both loaded like isolinux |
9 |
>does. |
10 |
> |
11 |
>I only tried passing the initrd line to the kernel in hopes that the |
12 |
>kernel would somehow help in loading it's initramfs. After all, it is |
13 |
>kept in the kernel image itself. |
14 |
> |
15 |
>The specific exampe here is the way the gentoo livecd works. It loads |
16 |
>both an initramfs (first) as well as an initrd (later in boot |
17 |
>process). I would like to mimic that behavior with lilo (or grub if |
18 |
>necessary). |
19 |
> |
20 |
>I know this is confusing. Hell, it took me a good while just to |
21 |
>figure out that the gentoo livecd hid their boot splash in an |
22 |
>initramfs hidden in the kernel! I appreciate your help with this. |
23 |
> |
24 |
>thanks, |
25 |
>Dave |
26 |
> |
27 |
> |
28 |
>On Wed, 12 Jan 2005 04:01:33 -0600, William Kilian <will@×××.com> wrote: |
29 |
> |
30 |
> |
31 |
>>You have to tell lilo a separate initrd line. Here's an example: |
32 |
>> |
33 |
>>image=/boot/vmlinuz-2.4.19 |
34 |
>> label=2.4.19 |
35 |
>> initrd=/boot/initrd-2.4.19.img |
36 |
>> read-only |
37 |
>> root=/dev/ram0 |
38 |
>> append="init=/linuxrc" |
39 |
>> |
40 |
>>I think lilo loads the initrd, but the kernel just finds it. So |
41 |
>>appending a kernel argument wouldn't help load the initrd. At any rate, |
42 |
>>I know you don't specify "initrd=whatever" in the append line with lilo. |
43 |
>>Note that grub also has to be told separately where the initrd is. And |
44 |
>>if you watch closely grub tells you when it boots something like |
45 |
>>"loading initrd", then "loading kernel". |
46 |
>> |
47 |
>>William Kilian |
48 |
>> |
49 |
>>David Wilk wrote: |
50 |
>> |
51 |
>> |
52 |
>> |
53 |
>>>Yes absolutely. Sorry about that. here's the append line for |
54 |
>>>isolinux.cfg (CD): |
55 |
>>> |
56 |
>>>append initrd=initrd root=/dev/ram0 init=/linuxrc acpi=ht |
57 |
>>>looptype=squashfs loop=/livecd.squashfs udev nodevfs cdroot vga=791 |
58 |
>>>dokeymap splash=silent,theme:metal console=ttyS0,9600n8 console=tty0 |
59 |
>>> |
60 |
>>>I've put the same thing into /etc/lilo.conf with and without the |
61 |
>>>initrd in there. |
62 |
>>> |
63 |
>>>Dave |
64 |
>>> |
65 |
>>> |
66 |
>>>On Tue, 11 Jan 2005 17:31:57 -0500, Chris Gianelloni |
67 |
>>><wolf31o2@g.o> wrote: |
68 |
>>> |
69 |
>>> |
70 |
>>> |
71 |
>>> |
72 |
>>>>On Tue, 2005-01-11 at 14:59 -0700, David Wilk wrote: |
73 |
>>>> |
74 |
>>>> |
75 |
>>>> |
76 |
>>>> |
77 |
>>>>>Howdy folks, |
78 |
>>>>> |
79 |
>>>>>I've taken the gentoo 2004.3 livecd and customized it a bit as an |
80 |
>>>>>install cd. I made my own kernel with an internal initramfs with |
81 |
>>>>>gensplash that uses an external initrd as well just like the livecd. |
82 |
>>>>>This works perfectly (just like the livecd) when the BIOS is |
83 |
>>>>>configured to boot from the CD. |
84 |
>>>>> |
85 |
>>>>>I have, however, a method to allow booting from the CD without |
86 |
>>>>>actually bootstraping from the CD. THe running system (from the HD) |
87 |
>>>>>mounts the CD, copies the kernel and initrd onto the HD, runs lilo |
88 |
>>>>>with those as defaults and then reboots. When the system comes back |
89 |
>>>>>up, it loads the CD kernel and initrd off the HD and the system boots |
90 |
>>>>>just as if the BIOS had booted the CD. |
91 |
>>>>> |
92 |
>>>>>My problem is this. Although the kernel and internal initramfs load |
93 |
>>>>>just fine off the CD resulting in a beautiful bootsplash screen, it |
94 |
>>>>>does no such thing when loaded off the HD. THe kernel boots fine, but |
95 |
>>>>>the initramfs is not loaded and there is no bootsplash. I have the |
96 |
>>>>>same kernel boot 'append' line in both isolinux.cfg on the CD as well |
97 |
>>>>>as in /etc/lilo.conf on the HD. |
98 |
>>>>> |
99 |
>>>>> |
100 |
>>>>> |
101 |
>>>>> |
102 |
>>>>Could you post the append line? It might make it easier for people to |
103 |
>>>>visualize. |
104 |
>>>> |
105 |
>>>> |
106 |
>>>> |
107 |
>>>> |
108 |
>>>> |
109 |
>>>>>I've spent days puzzling over which lilo or kernel parameters might |
110 |
>>>>>make this work and have come up with nothing. If anyone has any ideas |
111 |
>>>>>I would love to hear them. |
112 |
>>>>> |
113 |
>>>>> |
114 |
>>>>> |
115 |
>>>>> |
116 |
>>>>-- |
117 |
>>>>Chris Gianelloni |
118 |
>>>>Release Engineering - Operational/QA Manager |
119 |
>>>>Games - Developer |
120 |
>>>>Gentoo Linux |
121 |
>>>> |
122 |
>>>> |
123 |
>>>> |
124 |
>>>> |
125 |
>>>> |
126 |
>>>> |
127 |
>>>> |
128 |
>>>-- |
129 |
>>>gentoo-catalyst@g.o mailing list |
130 |
>>> |
131 |
>>> |
132 |
>>> |
133 |
>>> |
134 |
>>-- |
135 |
>>gentoo-catalyst@g.o mailing list |
136 |
>> |
137 |
>> |
138 |
>> |
139 |
>> |
140 |
>-- |
141 |
>gentoo-catalyst@g.o mailing list |
142 |
> |
143 |
> |
144 |
-- |
145 |
gentoo-catalyst@g.o mailing list |