On Sat, 2006-01-14 at 04:26, ext Dur??n wrote: > I'm trying to make a jffs2 image and then dump it with dd to an empty > partition in the RSMMC (empty=485MB, swap=24MB). > > I'm following this steps: > > 1. Create the jffs2 image: > > $ mkfs.jffs2 --eraseblock=0x20000 --pad=0x1E500000 -r mmc/ -o > root.jffs2 > > Note: "mmc" have only a text file. > > > 2. Check the image mounting it: > > # modprobe loop > # modprobe mtdblock > # losetup /dev/loop0 root.jffs2 > # modprobe blkmtd erasesz=128 device=/dev/loop0 > # mount -t jffs2 /dev/mtdblock0 /mnt Shouldn't it be /dev/mmcblk0? Maybe it's easier to edit /etc/fstab (check what are the options for jffs2). Then the automatic mounting (done by ke-recv program) should also work. However, I have not tested jffs2 MMCs... BR; Kimmo > > But when I try to mount the jffs2 image the mount gives a seg faults and > there's this kernel panic: > > > ------------------------ > Jan 14 02:57:23 Lain kernel: JFFS2 version 2.2. (NAND) (SUMMARY) (C) > 2001-2003 Red Hat, Inc. > Jan 14 02:57:49 Lain kernel: divide error: 0000 [#1] > Jan 14 02:57:49 Lain kernel: PREEMPT > Jan 14 02:57:49 Lain kernel: Modules linked in: jffs2 zlib_deflate > zlib_inflate blkmtd mtdblock mtd_blkdevs mtdcore loop arc4 > ieee80211_crypt_wep vmnet vmmon hostap_cs hostap ieee80211_crypt > snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_via82xx > snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss uhci_hcd snd_pcm > snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device > usbcore snd soundcore > Jan 14 02:57:49 Lain kernel: CPU: 0 > Jan 14 02:57:49 Lain kernel: EIP: 0060:[pg0+393781387/1068684288] > Tainted: P VLI > Jan 14 02:57:49 Lain kernel: EFLAGS: 00010246 (2.6.15-dieg) > Jan 14 02:57:49 Lain kernel: EIP is at jffs2_scan_medium+0x16b/0x580 > [jffs2] > Jan 14 02:57:49 Lain kernel: eax: 0001ff78 ebx: c4708800 ecx: > 0000000c edx: 00000000 > Jan 14 02:57:49 Lain kernel: esi: d7dc8000 edi: d7df5750 ebp: > c3a6dd80 esp: c208fd84 > Jan 14 02:57:49 Lain kernel: ds: 007b es: 007b ss: 0068 > Jan 14 02:57:49 Lain kernel: Process mount (pid: 4826, > threadinfo=c208e000 task=c0948ad0) > Jan 14 02:57:49 Lain kernel: Stack: c3a6dd80 d7df5750 cb560000 00001000 > c3a6dd80 c208fda4 00000f28 00000000 > Jan 14 02:57:49 Lain kernel: 00000000 00001000 c4708800 cb560000 > c4708800 00000f28 c4708800 00000000 > Jan 14 02:57:49 Lain kernel: d7c5e9ef c4708800 c0159880 00020000 > 000000d2 00000163 d7c64d9e 00020000 > Jan 14 02:57:49 Lain kernel: Call Trace: > Jan 14 02:57:49 Lain kernel: [pg0+393796079/1068684288] > jffs2_build_filesystem+0x1f/0x320 [jffs2] > Jan 14 02:57:49 Lain kernel: [vmalloc+32/48] vmalloc+0x20/0x30 > Jan 14 02:57:49 Lain kernel: [pg0+393821598/1068684288] jffs2_sum_init > +0x4e/0xe0 [jffs2] > Jan 14 02:57:49 Lain kernel: [pg0+393797528/1068684288] > jffs2_do_mount_fs+0x1b8/0x220 [jffs2] > Jan 14 02:57:49 Lain kernel: [pg0+393804982/1068684288] > jffs2_do_fill_super+0xc6/0x210 [jffs2] > Jan 14 02:57:49 Lain kernel: [pg0+393807295/1068684288] > jffs2_get_sb_mtd+0x11f/0x160 [jffs2] > Jan 14 02:57:49 Lain kernel: [pg0+393807780/1068684288] jffs2_get_sb > +0x124/0x1f0 [jffs2] > Jan 14 02:57:49 Lain kernel: [alloc_vfsmnt+185/288] alloc_vfsmnt > +0xb9/0x120 > Jan 14 02:57:49 Lain kernel: [do_kern_mount+82/224] do_kern_mount > +0x52/0xe0 > Jan 14 02:57:49 Lain kernel: [do_new_mount+153/224] do_new_mount > +0x99/0xe0 > Jan 14 02:57:49 Lain kernel: [do_mount+425/464] do_mount+0x1a9/0x1d0 > Jan 14 02:57:49 Lain kernel: [copy_mount_options+116/192] > copy_mount_options+0x74/0xc0 > Jan 14 02:57:49 Lain kernel: [sys_mount+157/224] sys_mount+0x9d/0xe0 > Jan 14 02:57:49 Lain kernel: [sysenter_past_esp+84/117] > sysenter_past_esp+0x54/0x75 > Jan 14 02:57:49 Lain kernel: Code: 39 53 78 0f 87 6d ff ff ff 89 2c 24 > e8 6f 08 4f e8 8b b3 80 00 00 00 85 f6 74 25 8b 46 18 85 c0 0f 85 ce 00 > 00 00 31 d2 8b 46 20 <f7> b3 04 01 00 00 85 d2 0f 85 3e 01 00 00 8d b4 > 26 00 00 00 00 > ------------------------------ > > I've tried mounting the jffs2 rootfs image from maemo.org and it mounts, > so I think that it's my fault creating the image. > > Anybody can guide my please ? > > Thanks. > > > > El vie, 13-01-2006 a las 16:50 -0500, Andrew Diller escribi??: > > I'm sure it will work, however you won't be able to plug the device into > > a host computer and have the flash card mount on the desktop, like you > > can now with a Windows or Macintosh computer. > > > > Diego Fdez. Dur??n wrote: > > > Can I format the RSMMC with JFFS2 filesystem in order to take advantage > > > of the on the fly compression and extend the life of the memory card ? > > > > > >
