public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Sean Simmons <ssimmons@rdinstruments.com>
To: linux-mtd@lists.infradead.org
Subject: Unable to fdisk DOC2000
Date: Sun, 13 May 2001 13:17:40 -0700	[thread overview]
Message-ID: <3AFEEBE4.40007@rdinstruments.com> (raw)

Hello,
   I'm using a stock 2.4.4 kernel with the MTD driver
compiled into the kernel.  I've managed to get the driver to
recognize the DOC so that it says:

M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
DiskOnChip 2000 found at address 0xCE000
Flash chip found: Manufacturer ID: 98, Chip ID: 73 (Toshiba TH58V128DC)
1 flash chips found. Total DiskOnChip size: 16 Mb

The FTL driver, however gives:

ftl_cs: FTL header not found.

The NFTL driver then says:

M-Systems NAND Flash Translation Layer driver. (C) 1999 MVHI
$Id: nftl.c,v 1.57 2000/12/01 17:51:54 dwmw2 Exp $
Could not find valid boot record
Could not mount NFTL device

According to a post I saw earlier, this means the DOC is "hosed"
and needs to be formatted.  When I run nftl_format I get:

Erase size not 8 Kb - I'm confused

I removed the check for the erase size as someone else suggested
and nftl_format appeared to work okay going through Phase 1, 2a,
2b, and 3 with no errors.

However, when I try to fdisk /dev/nftla I get:

Unable to open /dev/nftla

When I cat /proc/mtd I get:

mtd0: 01000000 "DiskOnChip 2000"

which looks different than I expected.

Does anybody have any idea why fdisk won't work?

Thanks,


Sean Simmons
Lead Firmware Engineer                    9855 Businesspark Ave
RD Instruments                            San Diego, CA 92131
email:  ssimmons@rdinstruments.com        phone:  (858)693-1178
web:    http://www.rdinstruments.com      fax:    (858)695-1459

             reply	other threads:[~2001-05-13 20:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-13 20:17 Sean Simmons [this message]
2001-05-13 21:15 ` Unable to fdisk DOC2000 David Griffith

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=3AFEEBE4.40007@rdinstruments.com \
    --to=ssimmons@rdinstruments.com \
    --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