From: "Phung Chi Kien" <kienpc@dubmail.net>
To: <linux-mtd@lists.infradead.org>
Cc: tdrury@siliconmotorsports.com
Subject: Re: NFTL device not found (boot floppies) (Tim Drury)
Date: Sat, 23 Aug 2003 09:07:01 +0700 [thread overview]
Message-ID: <001d01c3691b$3ec5f4e0$a500a8c0@kienpc> (raw)
In-Reply-To: E19q9eF-0004P5-7H@pentafluge.infradead.org
You should use DOS utilities (dformat) from M-sys to format the DOC with
driver version 5.1.4. After that reboot the PC and I think NFTL driver can
mount your DOC.
> Date: Thu, 21 Aug 2003 20:06:56 -0400
> From: "Tim Drury" <tdrury@siliconmotorsports.com>
> To: <linux-mtd@lists.infradead.org>
> Subject: NFTL device not found (boot floppies)
> Message-ID: <000601c36841$4d06a570$3301a8c0@SIMOTORSPORTS>
> Content-Type: text/plain;
> charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Precedence: list
> Message: 1
>
>
> I'm building a couple boot floppies for my target system - an Elan/586
> based system with a 32MB DOC 2000. I built the kernel with MTD built in
> (not modules) according to the faq. On bootup I get the following:
>
> ----
> NFTL driver: nftlcore.c $Revision: 1.94 $, nftlmount.c $Revision: 1.34 $
> DiskOnChip 2000 found at address 0xE0000 Flash chip found: Manufacturer
> ID: EC, Chip ID: 75 (Samsung: NAND 32MiB 3,3V) 1 flash chips found.
> Total DiskOnChip size: 32 MiB Could not find valid boot record
> NFTL: could not mount device
> ----
>
> Could this be because I'm using 2-floppy boot system with the /dev fs on
> the second floppy (which hasn't been inserted yet)? After I insert it
> and /dev is loaded, I try to do anything with /dev/nftla I get errors. I
> made /dev/nftla and /dev/nftla1 using 'mknod /dev/nftla b 90 0' and
> 'mknod /dev/nftla b 90 1' on the 2nd boot disk.
>
> % fdisk /dev/nftla
>
> Unable to open /dev/nftla
>
> % fdisk /dev/nftla1
>
> Unable to open /dev/nftla1
>
> I can see the MTD via /proc:
>
> % cat /proc/mtd
> dev: size erasesize name
> mtd0: 02000000 00004000 "DiskOnChip 2000"
>
> Any ideas?
>
> -tim
parent reply other threads:[~2003-08-23 2:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E19q9eF-0004P5-7H@pentafluge.infradead.org>]
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='001d01c3691b$3ec5f4e0$a500a8c0@kienpc' \
--to=kienpc@dubmail.net \
--cc=linux-mtd@lists.infradead.org \
--cc=tdrury@siliconmotorsports.com \
/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