Michael, you where right! the problem was the "flash_erase" step missing in my procedure.<br><br>I ended up mounting the jffs2 fs image on my Host system and discovered that the "/dev" is missing!<br><br>
So, when the kernel says: "<span class="q">Warning: unable to open an initial console" is not a problem mounting the FS, indeed, the FS is perfectly mounted now, but lacks of /dev directory!!<br><br>So, i think there's a buildroot bug here... it creates a JFFS but forgets to create the /dev directory...
<br><br><br>PD: Michael,Ulf consider yourself "free beer" awarded if you ever come to spain! :)<br></span><br><br><br><div><span class="gmail_quote">2007/10/19, Jorge S. <<a href="mailto:jorgesolla@gmail.com">
jorgesolla@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Michael,Ulf and all:<br><br>I did what you sugested:<br>
<br>I'm using an EXT2 initrd with all the flash_tools.<br><br><br># ./flash_erase /dev/mtd2<br>Erasing 1 Kibyte @ 6067e0 -- 99 % complete.<br># mkdir /mnt/flash
<br># mount -t jffs2 /dev/mtdblock2 /mnt/flash<span class="q"><br>JFFS2 write-buffering enabled buffer (1056) erasesize (8448)<br></span>JFFS2 notice: (298) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
<br># cd /mnt/flash/<br># ls -la<br>drwxr-xr-x 3 root root 0 Dec 31 1969 .<br>drwxr-xr-x 4 root root 1024 Dec 31 17:05 ..<br># cd ..<br># mount<br>rootfs on / type rootfs (rw)<br>/dev/root on / type ext2 (rw)
<br>proc on /proc type proc (rw)<br>devpts on /dev/pts type devpts (rw)<br>tmpfs on /tmp type tmpfs (rw)<br>/dev/sda1 on /mnt/usb type msdos (rw,fmask=0022,dmask=0022,codepage=cp850)<br>/dev/mtdblock2 on /mnt/flash type jffs2 (rw)
<br><br># /mnt/usb/armtool/flash_info /dev/mtd2 <br>Device /dev/mtd2 has 0 erase regions<br><br>The procedure looks working fine, i also issued a "flash_info" just for testing and enabled the debug messages for jffs2 on my kernel.
<br><br>After the flash_erase procedure using the initrd, i reboot the system, then using u-boot "loadb" command, i dump the JFFS2 rootfs to the DataFlash and set the kernel bootargs to boot from /dev/mtdblock2.
<br><br>Now i have a different behavior while booting but *still* no success, this is what the kernel says when booting:<span class="q"><br><br>JFFS2 write-buffering enabled buffer (1056) erasesize (8448)<br></span>JFFS2 notice: (1) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
<span class="q"><br>VFS: Mounted root (jffs2 filesystem).<br></span>Freeing init memory: 132K<span class="q"><br>Warning: unable to open an initial console.<br><br></span>... and stays here forever. (I know this warning comes from the kernel not seeing the /dev/console device...so i assume its unable to properly mount the rootfs)
<br><br><br> As Ulf is suggesting, i think there's something wrong when using mkfs.jffs2 to create the jffs2 filesystem.<br><br>Questions:<br><br>1) Do you guys have a ready-made jffs2 image proben to work that i can use to check my system? If your image works, then i can discard my kernel/u-boot configuration and focus on a possible problem when the
mkfs.jffs2 process is being done.<br><br>2) Are there any "must have" options enabled on the kernel configuration to deal with MTD rootfs? Maybe i'm missing something.<br><br>3) Any other ideas? I'm getting crazy on this :(
<br><br><br>As usual, BIG thanks helping and sorry about my poor english.<br><br> <br><br><br><br>
</blockquote></div><br>