Kernel 2.4.22-k7-1: initrd cannot mount proc from cramfs image

2003-11-11 Thread Nicola Larosa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

[Found the thread about init/cramfs, this seems a different issue.]


I installed the kernel-image-2.4.22-1-k7 package on an Asus L3355M laptop,
but it won't boot, giving the same kernel panic with both lilo and grub.


Relevant parameters for lilo:

boot=/dev/hda
root=/dev/hda5
# compact
install=/boot/boot-menu.b
map=/boot/map

image=/boot/vmlinuz-2.4.22-1-k7
label=linux
initrd=/boot/initrd.img-2.4.22-1-k7
read-only


Relevant parameters for grub:

title   Debian GNU/Linux, kernel 2.4.22-1-k7
root(hd0,4)
kernel  /boot/vmlinuz-2.4.22-1-k7 root=/dev/hda5 ro
initrd  /boot/initrd.img-2.4.22-1-k7
boot


Here are the last lines on the screen before the panic:


RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 3532 blocks [1 disk] into ram disk... done.
Freeing initrd memory: 3532k freed
VFS: mounted root (cramfs filesystem).
mount: Usage: mount [-t filesystemtype] [-o options,...] device mountpoint
This is a builtin command. /etc/fstab and /etc/mtab are NOT supported.

cat: No file proc/sys/kernel/real-root-dev.
/linuxrc: cannot create proc/sys/kernel/real-root-dev: directory nonexistent
VFS: Cannot open root device "hda5" or 03:05
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 03:05


Having mounted the initrd cramfs image with the command

# mount /boot/initrd.img-2.4.22-1-k7 /initrd -o loop

the contents of the linuxrc script are:


#!/bin/sh
#
# $Id: linuxrc,v 1.7 2003/08/05 10:14:01 herbert Exp $

export PATH=/sbin:/bin

mount -nt proc proc proc
root=$(cat proc/sys/kernel/real-root-dev)
echo 256 > proc/sys/kernel/real-root-dev
umount -n proc
mount -nt tmpfs tmpfs tmp || mount -nt ramfs ramfs tmp
echo $root > tmp/root


It looks like it cannot mount the proc filesystem. The command

# /initrd/bin/mount --help

includes a mention of the -n parameter, so that may not be the problem.


Adding the boot parameter "devfs=mount" to grub results in the following
added line, but still no joy:


- --- 01.txt2003-11-11 08:20:43.0 +0100
+++ 02.txt  2003-11-11 08:21:08.0 +0100
@@ -2,6 +2,7 @@
 RAMDISK: Loading 3532 blocks [1 disk] into ram disk... done.
 Freeing initrd memory: 3532k freed
 VFS: mounted root (cramfs filesystem).
+Mounted devfs on /dev
 mount: Usage: mount [-t filesystemtype] [-o options,...] device mountpoint
 This is a builtin command. /etc/fstab and /etc/mtab are NOT supported.


Any hint about what to look for? Thanks.


- --
"The open-source movement seems on the verge of winning its bid to
define the computing infrastructure of tomorrow - and the core of
that infrastructure will be Unix machines running on the Internet."
 -- Eric S. Raymond

Nicola Larosa - [EMAIL PROTECTED]


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/sJS7Xv0hgDImBm4RAun6AKC+JB/mXYP/sgEXAFGe8J5nAd/1gACfY/c1
iNRSjTTqIfG36dEjMAzpOaY=
=gG5z
-END PGP SIGNATURE-





Re: Kernel 2.4.22-k7-1: initrd cannot mount proc from cramfs image

2003-11-11 Thread Nicola Larosa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Thanks for the attention, Herbert.


> If you're using busybox then try regenerating the initrd image with
> BUSYBOX=no.

I did not generate the image, i'm using a stock kernel-image-2.4.22-1-k7
package, no trace of busybox in the initrd image, and it's not even installed
on this machine. Do you suggest I try mkinitrd'ing a new image anyway?



- --
"There are, in the end, no worthwhile "things" in the world;
there are only worthwhile doings." -- Steve Talbott, NetFuture

Nicola Larosa - [EMAIL PROTECTED]


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/sOkuXv0hgDImBm4RAh1xAJ976HWTyvqMuaaJd+zGjS51LowJugCgpjDe
6hXVhZ46R8bNVfdJaNzYppk=
=nJJF
-END PGP SIGNATURE-





Re: Kernel 2.4.22-k7-1: initrd cannot mount proc from cramfs image

2003-11-12 Thread Nicola Larosa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

>> If you're using busybox then try regenerating the initrd image with
>> BUSYBOX=no.

> I did not generate the image, i'm using a stock kernel-image-2.4.22-1-k7
> package, no trace of busybox in the initrd image, and it's not even installed
> on this machine. Do you suggest I try mkinitrd'ing a new image anyway?

Since there are no other ideas, I'll open a bug in the BTS.


- --
"There are, in the end, no worthwhile "things" in the world;
there are only worthwhile doings." -- Steve Talbott, NetFuture

Nicola Larosa - [EMAIL PROTECTED]


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)

iD4DBQE/sfQ9Xv0hgDImBm4RAgsNAJi19ykLtxlhxsfhzqeCjoLJPKZuAKCSE1oH
mRVNt0w01ln2z9/E9kzqSw==
=weE1
-END PGP SIGNATURE-