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

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'

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

2003-11-11 Thread Herbert Xu
Nicola Larosa <[EMAIL PROTECTED]> wrote: > > 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 mo

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: b