• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 2 [3]
31  Linux Stuff / General Linux questions / Re: HOWTO mount JFFS2 image on Linux host without NAND flash on: April 16, 2009, 07:06:03 AM
Don't know if it helps, but here is what I do to mount a JFFS2-Image on my Debian-Box:
Code:
linBox:/home/kaibo# modprobe mtdblock
linBox:/home/kaibo# modprobe jffs2
linBox:/home/kaibo# modprobe mtdram total_size=200000
linBox:/home/kaibo# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 0c350000 00020000 "mtdram test device"
linBox:/home/kaibo# dd if=/usr/src/sheeva/Image/ubuntu.jffs2 of=/dev/mtdblock0
278272+0 records in
278272+0 records out
142475264 bytes (142 MB) copied, 2.59761 s, 54.8 MB/s
linBox:/home/kaibo# mount -t jffs2 /dev/mtdblock0 /mnt
linBox:/home/kaibo# ls /mnt
bin   dev  home  media opt   root  selinux  sys  usr
boot  etc  lib mnt proc  sbin  srv      tmp  var

And yes, all files are there - not only the directories.
32  Linux Stuff / Kernel / Re: Problems reflashing UImage, bad blocks on: April 16, 2009, 06:52:49 AM
It seems to pause on boot, just after initalizing eth0. It seems like it's scanning the flash or something. Is this normal?

Code:
md: autorun ...
md: ... autorun DONE.
eth0: link up, full duplex, speed 100 Mbps
..... pause ~ 60 seconds .....
Empty flash at 0x0e2b2080 ends at 0x0e2b2800
VFS: Mounted root (jffs2 filesystem).
...

-tmk
Mine does that as well.  For me it not only does this when booting but when doing other stuff as well - I notice it during heavy io-operations (from/to nand/usb/mmc).

Regarding the Bad Blocks: I have 19 of them in total. As long as they have been marked as such it shouldn't be a problem. Bad Blocks on Flash-Devices are, while not convenient, common and hence tolerated and handled accordingly. However, there should not be an increase of Bad Blocks.
33  Linux Stuff / Kernel / Re: anyone compile a custom kernel yet? on: April 15, 2009, 08:47:19 PM
I found that I had to set mainlineLinux to yes, then reset the plug and set arcNumber before that went away.
I can confirm that. Having it done that way it works like a charm!  Grin
34  Linux Stuff / Kernel / Re: anyone compile a custom kernel yet? on: April 15, 2009, 11:56:08 AM
Thanks a lot for the fast response on this! However, the error stays the same. Is there an additional chip needed in the kernel-config?

On a sidenote (even though it might be obvious): Having the enviroment-variables set as described in the Troubleshooting-Chapter results in the original kernel not booting anymore.
35  Linux Stuff / Kernel / Re: anyone compile a custom kernel yet? on: April 15, 2009, 05:44:18 AM
Compiled my Kernel yesterday (almost) without hassles. It took the approximated 45 Minutes on the Plug itself, which is fine for my purposes. But somehow I must have missed something.

I set everything up as stated in the Wiki (getting kernel using snapshot) and compiled it using the steps provided by moshiach in this thread (Thanks for that!). However, after flashing the Image and booting it, I get this:
Code:
Error: unrecognized/unsupported machine ID (r1 = 0x0000020f).

Available machine support:

ID (hex) NAME
00000690 Marvell DB-88F6281-BP Development Board
00000691 Marvell RD-88F6192-NAS Development Board
00000682 Marvell RD-88F6281 Reference Board
00000831 Marvell SheevaPlug Reference Board
0000085b QNAP TS-119/TS-219

Please check your kernel config and/or bootloader.

Did I miss something? Maybe a kernel-option that is not being set by using make defconfig? Even though I find it odd that a SheevaPlug is listed as supported...
Pages: 1 2 [3]