There is no problem using the initial RAM disk
(initrd) with kernel 2.4.9
But with kernel 2.4.10 system reports the following
messages:
RAMDISK: compressed image found at block 0
Freeing initrd memory: 1153k freed
VFS: Mounted root (ext2 filesystem)
Freeing unused kernel (memory: 224k freed)
Kernel panic: No init found. Try passing init=option
to kernel
When I compile the 2.4.10 The following option is
supported:
<*> RAM disk support(128000) Default RAM disk size
[*] Initial RAM disk (initrd) support
The version of lilo is 21.6. My lilo.conf is as this:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=CapitelFW-2.4.9
image=/hda2/boot/linux-2.4.91
label=CapitelFW-2.4.9
initrd=/hda2/root/initrd.gz
append="root=/dev/ram0 init=linuxrc rw"
image=/hda2/boot/linux-2.4.10-ac
label=CapitelFW-ac12
initrd=/hda2/root/initrd.gz
append="root=/dev/ram0 init=linuxrc rw"
_________________________________________________________
Do You Yahoo!? ??¼?????Ż?????! http://mail.yahoo.com.cn
<font color=#6666FF>???ģ????ƣ????ˣ?û???ɣ??????????ɣ?</font>????
?Ż?ȫ????????! http://cn.chat.yahoo.com/c/roomlist.html
This is the same problems, which I am facing and have posted a mail as well,
but so far repose has been received, please any one who can help do reply.
Regards.
Talha
----- Original Message -----
From: "hanhbkernel" <[email protected]>
To: <[email protected]>
Sent: Friday, October 12, 2001 8:24 AM
Subject: initrd problem of 2.4.10
> There is no problem using the initial RAM disk
> (initrd) with kernel 2.4.9
> But with kernel 2.4.10 system reports the following
> messages:
>
> RAMDISK: compressed image found at block 0
> Freeing initrd memory: 1153k freed
> VFS: Mounted root (ext2 filesystem)
> Freeing unused kernel (memory: 224k freed)
> Kernel panic: No init found. Try passing init=option
> to kernel
>
> When I compile the 2.4.10 The following option is
> supported:
> <*> RAM disk support(128000) Default RAM disk size
>
> [*] Initial RAM disk (initrd) support
>
> The version of lilo is 21.6. My lilo.conf is as this:
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> message=/boot/message
> linear
> default=CapitelFW-2.4.9
> image=/hda2/boot/linux-2.4.91
> label=CapitelFW-2.4.9
> initrd=/hda2/root/initrd.gz
> append="root=/dev/ram0 init=linuxrc rw"
> image=/hda2/boot/linux-2.4.10-ac
> label=CapitelFW-ac12
> initrd=/hda2/root/initrd.gz
> append="root=/dev/ram0 init=linuxrc rw"
>
>
>
> _________________________________________________________
> Do You Yahoo!? ??¼?????Ż?????! http://mail.yahoo.com.cn
>
> <font color=#6666FF>???ģ????ƣ????ˣ?û???ɣ??????????ɣ?</font>????
> ?Ż?ȫ????????! http://cn.chat.yahoo.com/c/roomlist.html
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
> There is no problem using the initial RAM disk
> (initrd) with kernel 2.4.9
> But with kernel 2.4.10 system reports the following
> messages:
>
> RAMDISK: compressed image found at block 0
> Freeing initrd memory: 1153k freed
> VFS: Mounted root (ext2 filesystem)
> Freeing unused kernel (memory: 224k freed)
> Kernel panic: No init found. Try passing init=option
> to kernel
>
> When I compile the 2.4.10 The following option is
> supported:
> <*> RAM disk support(128000) Default RAM disk size
This is an unusually large size (128MB). Is your ramdisk
really that large? Try reducing this to a more sane value
(say 4096) and add the "ramdisk=" line to your /etc/lilo.conf
if your ramdisk goes above 4MB.
>
> [*] Initial RAM disk (initrd) support
>
> The version of lilo is 21.6. My lilo.conf is as this:
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> message=/boot/message
> linear
> default=CapitelFW-2.4.9
> image=/hda2/boot/linux-2.4.91
> label=CapitelFW-2.4.9
> initrd=/hda2/root/initrd.gz
> append="root=/dev/ram0 init=linuxrc rw"
> image=/hda2/boot/linux-2.4.10-ac
> label=CapitelFW-ac12
> initrd=/hda2/root/initrd.gz
> append="root=/dev/ram0 init=linuxrc rw"
On Fri, Oct 12, 2001 at 01:24:53PM +0800, hanhbkernel wrote:
> There is no problem using the initial RAM disk
> (initrd) with kernel 2.4.9
> But with kernel 2.4.10 system reports the following
> messages:
>
> RAMDISK: compressed image found at block 0
> Freeing initrd memory: 1153k freed
> VFS: Mounted root (ext2 filesystem)
> Freeing unused kernel (memory: 224k freed)
> Kernel panic: No init found. Try passing init=option
> to kernel
Check that /lib/ld-* in the initrd has execute permission.
Regards,
Mark.
--- Mark van Walraven <[email protected]> ?????ģ?>
> On Fri, Oct 12, 2001 at 01:24:53PM +0800,
> hanhbkernel wrote:
> > There is no problem using the initial RAM disk
> > (initrd) with kernel 2.4.9
> > But with kernel 2.4.10 system reports the
> following
> > messages:
> >
> > RAMDISK: compressed image found at block 0
> > Freeing initrd memory: 1153k freed
> > VFS: Mounted root (ext2 filesystem)
> > Freeing unused kernel (memory: 224k freed)
> > Kernel panic: No init found. Try passing
> init=option
> > to kernel
>
> Check that /lib/ld-* in the initrd has execute
> permission.
>
> Regards,
>
> Mark.
thanks for your help but I have checked /lib/ld-* in
the initrd.the permission is right.please give me more
help
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
_________________________________________________________
Do You Yahoo!? ??¼?????Ż?????! http://mail.yahoo.com.cn
<font color=#6666FF>???ģ????ƣ????ˣ?û???ɣ??????????ɣ?</font>????
?Ż?ȫ????????! http://cn.chat.yahoo.com/c/roomlist.html
On Fri, Oct 19, 2001 at 11:39:55AM +0800, hanhbkernel wrote:
> thanks for your help but I have checked /lib/ld-* in
> the initrd.the permission is right.please give me more
> help
What command line arguments do you pass to linux, and in what order?
I presume your initrd has /bin/sh? What happens if boot with init=/bin/sh?
Mark.