Re: initramfs problems

[Carmelo AMOROSO <carmelo.amoroso@st.com>]

Hi Tiago,
as in the previous mail, please for STLinux related issue, use bugzilla 
channel at https://bugzilla.stlinux.com/

Carmelo

Tiago Maluta wrote:
> Hi,
> 
> I'm with problems to attach an iniramfs to vmlinux. I'm using:
> linux-2.6.17.14_stm22_0038
> 
>>From Documentation/filesystem/ramfs-romfs-initramfs.txt I got that I
> can start initramfs by three ways
> 
> a) gzipped cpio archive
> b) directory containing a filesystem
> c) textfile
> 
> My first approach was using option b)
> 
> I read Documentation/early-userspace/README and populated a simple fs.
> Basically, for my first test, I used the filesystem that already use
> on MTD block.
> 
> I settled the folder CONFIG_INITRAMFS_SOURCE using menuconfig General
> Setup --> () Initramfs source file(s)
> 
> But I got kernel panic:
> 
> VFS: Cannot open root device "<NULL>" or unknown-block(2,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
> 
> 
> After I tryed option c) setting CONFIG_INITRAMFS_SOURCE with a
> fileneme containing:
> 
> dir /dev 755 0 0
> nod /dev/console 644 0 0 c 5 1
> nod /dev/loop0 644 0 0 b 7 0
> dir /bin 755 1000 1000
> slink /bin/sh busybox 777 0 0
> file /bin/busybox initramfs/busybox 755 0 0
> dir /proc 755 0 0
> dir /sys 755 0 0
> dir /mnt 755 0 0
> file /init initramfs/init.sh 755 0 0
> 
> But I dind't know exactly how this option work (I made just for free
> my consciousness certainly that doesn't work)
> 
> I think the problem could be at GDB parameter. I'm using:
> 
> st40load_gdb \
>         -t $JEI_IP \
>         -b $KERNEL \
>         -c $BOARD \
>         console=ttyAS1,115200 \
>         root=/dev/nfs rw \
>         $ETHERNET \
>         $IDE \
>         $MTD \
>         nfsroot=$SERVERIP:$SERVERDIR,$TCP_UDP \
>         ip=$TARGETIP::$GWIP:$NETMASK:$NAME::$AUTOCONF \
>         mem6m \
>         bigphysarea\x1512
> 
> I also tried but init option (but I think with initramfs I could not
> be necessary).
> 
> Best regards,
> Tiago Maluta
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>