public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Edmund Troche <edmund@troche.org>
To: linux-mtd@lists.infradead.org
Subject: Errors getting JFFS to work
Date: Thu, 10 May 2001 22:29:43 -0500	[thread overview]
Message-ID: <3AFB5CA7.A413ECCF@troche.org> (raw)
In-Reply-To: A3E34B558F5CD211B4980008C7A4A99003163ECC@sparrow.eng.gilbarco.com

Hi,

I've been following the mtd-howto instructions on how to get JFFS mounted in a
DoC, but with no luck so far, perhaps I'm missing something that might be
obvious to some of you. In a nutshell, I have a 386EX board with a 8MB DoC
2000, which I have had running with Linux 2.4.3 and the M-Systems code. I would
very much prefer to use the MTD code instead of the M-Systems code, therefore
I've been trying to get this working for the last couple of nights. The kernel
( 2.4.3) has the MTD support compiled in, no modules. When I boot it recognizes
the DoC correctly and it seems like I can ntfl_format and fdisk without
problems. The problems seems to start when I try to copy and image created with
mkfs.jffs into the mtd character device 0. Below I have attached some of the
terminal output from some of my commands. The utilities are being built from a
"util" directory that I created under my 2.4.3 kernel distribution (
/usr/src/linux/util ) according to the README in the mtd/util directory. So I
imagine my utilities are using the distribution header files. If anyone needs
some more information regarding this, please let me know and I will be happy to
provide it.


Thanks for your help.

Edmund



----------------------------- TERMINAL OUTPUT ---------------------------

/ # ./fdisk /dev/nftla

Command (m for help): p

Disk /dev/nftla: 16 heads, 1 sectors, 1020 cylinders
Units = cylinders of 16 * 512 bytes

     Device Boot    Start       End    Blocks   Id  System
/dev/nftla1             1      1020      8159+  83  Linux

Command (m for help): q

/ # cp /jffs.image /dev/mtd0
MTD_open
MTD_ioctl
Invalid ioctl 5401 (MEMGETINFO = 80204d01)
MTD_write
.......
....... (lots of MTD_write)
.......
MTD_write
ECC needs a full sector write (adr: 9de00 size 134)
MTD_close
/ # mount -t jffs /dev/mtdblock0 /mnt/jffs
mtdblock_open
ok
JFFS: Trying to mount device 1f:00.
jffs_scan_flash(): start pos = 0x0, end = 0x800000
check_partly_erased_sector():checking sector which contains offset 0x0 for
flipp
ing bits..
Kernel panic: Didn't read all bytes in flash_safe_read(). Returned 0

-----------------------------------------------------------------------

  reply	other threads:[~2001-05-11  3:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-07 12:34 Invalid ioctl answer + another question Williams, Kevin M.
2001-05-11  3:29 ` Edmund Troche [this message]
2001-05-11 16:37   ` Errors getting JFFS to work David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3AFB5CA7.A413ECCF@troche.org \
    --to=edmund@troche.org \
    --cc=linux-mtd@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox