irclog2html for #tuxscreen on 20030403

10:31.02*** join/#tuxscreen mallum (~mallum@pc-80-193-218-21-hw.blueyonder.co.uk)
12:00.26*** join/#tuxscreen julie_ (~julie@ultrasparc.ipv6.magenet.com)
12:32.20*** join/#tuxscreen Morn (~julie@ultrasparc.ipv6.magenet.com)
15:43.01*** join/#tuxscreen gatofisch (~trillian@eastquad-170-211.reshall.umich.edu)
16:52.29*** join/#tuxscreen andersee (~andersen@codepoet.org)
16:52.29*** mode/#TuxScreen [+o andersee] by ChanServ
17:27.44*** join/#tuxscreen pattieja (~pattieja@sc2-24.217.177.39.charter-stl.com)
18:19.53*** join/#tuxscreen loubail (~loubail@f02m-1-32.d1.club-internet.fr)
18:19.55loubailhi all
18:20.09loubail<PROTECTED>
18:20.14loubailis somebody MTD buff? or else have tried to install arm linux kernel with a jffs2 ?
18:20.15loubail:p:p
18:20.16loubail:$
18:48.43anderseeloubail: yes
18:49.51loubailreally?
18:49.54loubailgreat
18:50.17*** join/#tuxscreen JemaitriseARM (~trillian@lns-p19-16-81-56-180-205.adsl.proxad.net)
18:50.32JemaitriseARMI just ate my tux!!
18:50.44loubailwell JemaitriseARM is working with me on the arm embedded system
18:50.47JemaitriseARMI couldnt stand it anylonger :(
18:50.58loubailwe are trying to mount a jffs2 root fs
18:51.06loubailbut we get this sort of messages:
18:51.46loubailjffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020014:
18:51.46loubail0xf9be in
18:51.46loubailstead
18:51.57loubailans finally
18:51.58loubailVFS: Mounted root (jffs2 filesystem).
18:51.58loubailFreeing init memory: 48K
18:51.58loubailWarning: unable to open an initial console.
18:51.58loubailKernel panic: No init found.  Try passing init= option to kernel.
18:52.04anderseeloubail: on the tuxscreen?
18:52.13loubailon a arm linux device an altera one
18:52.14kergothsounds like wrong eraseblock size or something similar
18:52.15anderseeloubail: I assume you have blob installed already?
18:52.22loubailwe use armboot
18:52.35loubailwhich support the card we use : epxa1db (from altera)
18:52.48anderseeloubail: I agree with kergoth's assessment
18:54.06loubailokay we will try at once to change that
18:54.15loubailhope it will fix this problem
18:56.08loubailwe have tried to use mkf.jffs2 with the little endian option
18:57.03loubailWell do u know whether blob support altera epxa1db device?
18:57.06anderseeTry setting 'mkfs.jffs2 --pad --little-endian --squash -e 0x20000'
18:57.16anderseeor some other eraseblock size
18:57.27anderseeThe right size depends on your flash
18:57.43loubailthanks a lot for your advices kergoth and andersee
18:57.45loubail:$
18:58.12JemaitriseARMindeed
18:58.13loubailJemaitriseARM is currently rebuilding the jffs2
19:07.05loubailwell we got news
19:07.16loubailnow there's no 0x1985 messages
19:07.32loubailbut we already get
19:07.42loubailmtdblock_open
19:07.43loubailok
19:07.43loubailVFS: Mounted root (jffs2 filesystem).
19:07.43loubailFreeing init memory: 48K
19:07.43loubailWarning: unable to open an initial console.
19:07.43loubailKernel panic: No init found.  Try passing init= option to kernel.
19:11.16anderseeloubail: does your kernel have a CONFIG_CMDLINE set in the .config
19:11.16andersee?
19:12.07loubailwe give the kernel parameters with armboot
19:12.25loubailand the kernel boot display these parameters
19:12.28anderseeok.  So what are your kernel boot args?
19:12.44anderseeDo you have something like root=/dev/mtdblock1
19:13.17loubailroot=/dev/mtdblock0 mem=31M console=ttyUA0,57600
19:13.29loubailsorry
19:13.32loubailnot that
19:13.41loubailroot=/dev/mtdblock0 mem=16M rootfstype=jffs2 console=ttyUA0,57600
19:13.47anderseejust to humor me, try root=/dev/mtdblock1
19:14.47loubailwell the kernel boot tells us :
19:14.48loubailCreating 1 MTD partitions on "EPXA flash":
19:14.48loubail0x00400000-0x00800000 : "jffs"
19:14.48loubailmtd: Giving out device 0 to jffs
19:15.13loubailwell with mtdblock1 it tells us : NetWinder Floating Point Emulator V0.95   1998-1999 Rebel.com
19:15.14loubailmtdblock_open
19:15.14loubailVFS: Cannot open root device "mtdblock1" or 1f:01
19:15.14loubailPlease append a correct "root=" boot option
19:15.14loubailKernel panic: VFS: Unable to mount root fs on 1f:01
19:16.37loubailwell at once we have tried to use this kernel parameter init=/sbin/init
19:16.56loubailand it doesn't work we've got the same kernel panic and warning
19:17.51anderseeok
19:19.34anderseeloubail: tried sticking something like a staticly linked /bin/sh or busybox into your rootfs?
19:20.55JemaitriseARMandersee: in fact were not sure what really is mandatory in the fs
19:23.06JemaitriseARMin fact we have that in our jffs2:
19:23.15JemaitriseARM.
19:23.15JemaitriseARM./sbin
19:23.15JemaitriseARM./sbin/init
19:23.15JemaitriseARM./sbin/depmod
19:23.15JemaitriseARM./sbin/modprobe
19:23.16JemaitriseARM./sbin/lsmod
19:23.18JemaitriseARM./sbin/insmod
19:23.20JemaitriseARM./bin
19:23.22JemaitriseARM./bin/mount
19:23.24JemaitriseARM./bin/umount
19:23.26JemaitriseARM./bin/mkdir
19:23.28JemaitriseARM./bin/cp
19:23.30JemaitriseARM./bin/ls
19:23.32JemaitriseARM./bin/echo
19:23.34JemaitriseARM./bin/bash
19:23.36JemaitriseARM./bin/cat
19:23.38JemaitriseARM./bin/mknod
19:23.40JemaitriseARM./bin/rm
19:23.42JemaitriseARM./etc
19:23.44JemaitriseARM./root.txt
19:23.48JemaitriseARMwithout root.txt :)
19:23.58anderseeJemaitriseARM: and where did you get all these binaries from?
19:24.12JemaitriseARMwe used a script
19:24.23anderseeJemaitriseARM: a script?
19:25.01JemaitriseARMhttp://www.embeddedlinuxinterfacing.com/chapters/04/buildrootfilesystem
19:25.07JemaitriseARMyes we used this script
19:25.41JemaitriseARMbut we didnt use all the files we were supposed to according to this script
19:25.42anderseeJemaitriseARM: I notice you did not include /dev
19:26.03anderseeJemaitriseARM: I strongly recommend you start from a _working_ system
19:26.07JemaitriseARMwe thought /dev could be dynamicaly made by the kernel
19:26.41JemaitriseARMwe thought we might use montavista, which is already available on our card
19:26.42anderseeJemaitriseARM: iff you are using devfs, have mounted the devfs filesystem, and have setup devfsd...
19:26.58JemaitriseARMoops ok, we didnt know that :)
19:27.07anderseeJemaitriseARM: that might be for the best, since you do not have a lot of experience it seems
19:27.17JemaitriseARMyes this is true
19:27.31anderseeJemaitriseARM: or, since you are on #tuxscreen, you might want to try the tuxscreen buildroot system and adapt it for your needs...
19:27.50JemaitriseARMwe would be delighted
19:28.18anderseehttp://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/tuxscreen/buildroot-tux/
19:28.30anderseeThis is pretty similar to what I presume you are building
19:28.39anderseehttp://tuxscreen.net/ for details
19:28.41JemaitriseARMthank you
19:28.42JemaitriseARMok
19:29.06JemaitriseARMin fact we didnt even know about that (and yet google was intensively used)
19:40.33loubailhave to go thanks a lot for your help
19:45.28JemaitriseARMbye
19:45.30*** part/#tuxscreen JemaitriseARM (~trillian@lns-p19-16-81-56-180-205.adsl.proxad.net)

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with blootbot logs, split per channel, etc.