, January 21, 2003 2:21 PM
To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED]
Subject: RE: mkinitrd trouble
_I_AM_NO_EXPERT_
Did you compile the kernel with cramfs, also?
You didn't mention it.
-Original Message-
From: James Miller [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 21,
on Tue, Jan 21, 2003 at 12:49:13PM -0600, James Miller wrote about mkinitrd trouble:
> Hello all
>
> I am pulling my hair trying to get Debian Woody to boot with an initrd
> image. I have compiled the kernel 2.4.18 with Loopback device support, RAM
> disk support , 8192KB,
_I_AM_NO_EXPERT_
Did you compile the kernel with cramfs, also?
You didn't mention it.
-Original Message-
From: James Miller [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 21, 2003 2:01 PM
To: [EMAIL PROTECTED]
Subject: mkinitrd trouble
Hello all
I am pulling my hair trying t
On 21 Jan 2003, 12:49:13, James Miller wrote:
> Here is a snippet of lilo.conf
> default=Linux
>
> image=/vmlinuz
> label=Linux
> read-only
>
> image=/vmlinuz
> label=Linux-initrd
> initrd=/inird-2.4.18-12.img
don't you mean
initrd-2.4.18-12.img . . .
> a
Hello all
I am pulling my hair trying to get Debian Woody to boot with an initrd
image. I have compiled the kernel 2.4.18 with Loopback device support, RAM
disk support , 8192KB, and initrd (all compiled into the kernel). I am able
to run mkinird just fine 'mkinird 2.4.18-12 -o /initrd-2.4.18-12
5 matches
Mail list logo