I need your help .

I need your help .

[李建泰]

Hi ..
Mr. Woodhouse .
My name is HiramLee .
I living in Taiwan .
I read your data on  http://www.linux-mtd.infradead.org/doc2000.html this
web side .
And I tried to put the disk-on-chip function in my linux kernel .
That is my process below .
1. cd /usr/src/linux
2. make menuconfig
3. Turn on "NTFL support " ,"M-Systems Disk-On-Chip 2000 and Millennium"
    ," Loopback device support " and " RAM disk support " in the kernel (not
a module)
   and what I need ...

4. make dep
5. make clean
6. make bzImage
7. make modules
8. make modules_install
9. copy the bzImage file to the /boot then setup the lilo and reboot
10.  mknod /dev/fla b 62 0   (make a doc device node)

The Kernel is working very well but there is a boot message show up about
the disk-on-chip when loading the kernel .
"DiskOnChip Millennium found at address 0xD8000
  Flash chips found : Manufacturer ID:98,Chip ID:E6 (Toshiba TC58V64AFT/DC)
 1 flach chips found. Total DiskOnChip size:8MiB"
"M-Systems NAND Flash Translation Layer Driver .(c) 1999 MVHI
$Id: nftlcore.c ,v 1.73 2001/06/09 01:09:43 dwmw2 Exp$
Sorry, we don,t support UnitSizeFactor of !=1 yet
Sorry, we don,t support UnitSizeFactor of !=1 yet
Could not find valid boot record
Could not mount NFTL device"

Could you answer me what this message mean ??
I try on kernel-2.4.2 and 2.4.8 version thay both have this problem .
I can't  mount my disk on chip device (Computer say "Unable to open device
/dev/fla")
Could you teach me what can I do .
And my disk on chip could work .
                                  Please    Thank you very much

                                                                   HiramLee

Re: I need your help .

[David Woodhouse]

hiram@thyme.com.tw said:
> 3. Turn on "NTFL support " ,"M-Systems Disk-On-Chip 2000 and
> Millennium"," Loopback device support " and " RAM disk support " in the
> kernel (not a module) 

You don't really need loopback or ramdisk support. But they don't hurt.

> 10.  mknod /dev/fla b 62 0   (make a doc device node) 

That's the wrong device node. It would be /dev/nftla, and any partitions 
would be /dev/nftla1, /dev/nftla1 etc. 

 mknod /dev/nftla b 93 0
 mknod /dev/nftla1 b 93 1
 mknod /dev/nftla2 b 93 2

> Sorry, we don,t support UnitSizeFactor of !=1 yet
> Sorry, we don,t support UnitSizeFactor of !=1 yet
> Could not find valid boot record
> Could not mount NFTL device"

This is complaining because the logical erase size of the NFTL format is 
more than a single _physical_ erase block. The code _ought_ to work like 
that, but hasn't been tested. Other people on the mailing list have asked 
before - I'm not sure what their conclusions were. I think I need to test 
this setup myself and commit the code.

--
dwmw2

Re: I need your help .

[Mark Meade]

hiram@thyme.com.tw said:

> Sorry, we don,t support UnitSizeFactor of !=1 yet

I've seen this happen with the latest versions (5.0) of the M-Systems firmware.  Using the
4.2 version (still available at www.m-sys.com) makes this problem go away.

To clarify, use the DOS DFORMAT utility with the DOC42.EXB file.  The TrueFFS driver for
Linux is *not* needed - as this is what the open-source MTD drivers are replacing.