MTD and 2.4

MTD and 2.4

[Jason Walker]

Greeting all

	I have a rather interesting situation.  I have a box with a DickOnChip on
it, and someone else built a 2.2.x kernel for it.  I need to get a 2.4.x
kernel on it.  I did not build the 2.2.x kernel that is on it now, so I
don't know how it's done.  I *suspect* they used the kernel patxches from
M-systems, but I am not positive.  I have tried their patches for 2.4 but
they are incredibly outdated and don't compile (they were meant for
2.4.0pre8)  On the 2.2.x kernel the devices come up as /dev/fla.  I don't
need to maintain backwards compatibility with the 2.2.x formats, so if I
need to use another one that is cool.  I read all the documentation on the
website and the kernel *still* won't work.  This is a DiskOnChip Millenium
chip, btw.  If I need to post error messages or my kernel config, that is
fine.. Any help would be appreciated. thank!

Jason Walker

US Wireless Online



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: MTD and 2.4

[David Woodhouse]

jasonw@uswo.net said:
> This is a DiskOnChip Millenium chip, btw.  If I need to post error
> messages or my kernel config, that is fine.. Any help would be
> appreciated. thank! 

Enable the #define DOC_SINGLE_DRIVER in docprobe.c and make sure you've 
enabled CONFIG_MTD_DOC2001. If it still doesn't work, show us the startup 
messages.

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

RE: MTD and 2.4

[Michel STEMPIN]

> I *suspect* they used the kernel patxches from
> M-systems, but I am not positive.
If it is the case, you should see a copyright message both during the boot
process and in /proc/kmsg
Then, you will need to figure out if its built in the kernel (in which case
your linux is not redistributable), or as a separate module loaded in the
initrd (do a lsmod and check for a doc module).

--
Michel Stempin
MIS
COM One SA, 11 parc de Marticot, 33610 CESTAS, FRANCE
Tel: +33(0)5 57 97 72 72
Fax: +33(0)5 56 78 84 78
Email: mstempin@com1.fr

RE: MTD and 2.4

[Jason Walker]

Sorry it took so long to respond, things have been busy.

I did as you said, enabled CONFIG_MTD_DOC2001 and checked out the #define in
docprobe.c and it was already enabled.  I recompiled and I get the same
error.  Let me see if I can type it out, as I have no way to cut and paste
it

M-Systems DiskOnChip Driver. (C) 1999 Machine Vision Holdings, Inc.
request_module[doc2000]: Root fs not mounted
Cannot find driver for DiskOnChip Millennium at 0xD0000
M-Systems NAND Flash Translation Layer driver. (C) 1999 MVHI
$Id: nftl.c,v 1.57 2000/12/01 17:51:54 dwmw2 Exp $
<--TCP initializes here-->
...
request_module[block-major-100]: Root fs not mounted
VFS: Cannot open root device "6401" or 64:01
Please append a correct "root=" boot option
Kernel panic: VFS: cannot mount root fs blah blah blah

What is it that I am missing?  This is 2.4.4, and no patches have been
applied as of yet.

Thanks for your time!

Jason Walker

-----Original Message-----
From: owner-mtd@infradead.org [mailto:owner-mtd@infradead.org]On Behalf
Of David Woodhouse
Sent: Monday, April 30, 2001 12:04 PM
To: Jason Walker
Cc: MTD Mailing List
Subject: Re: MTD and 2.4



jasonw@uswo.net said:
> This is a DiskOnChip Millenium chip, btw.  If I need to post error
> messages or my kernel config, that is fine.. Any help would be
> appreciated. thank!

Enable the #define DOC_SINGLE_DRIVER in docprobe.c and make sure you've
enabled CONFIG_MTD_DOC2001. If it still doesn't work, show us the startup
messages.

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: MTD and 2.4

[David Woodhouse]

jasonw@uswo.net said:
>  I did as you said, enabled CONFIG_MTD_DOC2001 and checked out the
> #define in docprobe.c and it was already enabled. 

> request_module[doc2000]: Root fs not mounted

Argh. Sorry, _disable_ DOC_SINGLE_DRIVER and use doc2001.
The less likely to work alternative is to leave it _enabled_ and use 
doc2000. The message above is because it's trying to load the doc2000 
driver, because DOC_SINGLE_DRIVER is enabled and the doc2000 option isn't 
(only the doc2001 option).

This will be made less complex - the DOC_SINGLE_DRIVER is an attempt to 
merge it all into one, but some people still find the doc2001 driver to be 
more reliable.

--
dwmw2

RE: MTD and 2.4

[Jason Walker]

ok, this appears to be working a little better. at least I get different
errors :)
M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
DiskOnChip Millennium found at address 0xD0000
Flash chip found: Manufacturer ID: 98, Chip ID: E6 (Toshiba blah blah..)
same message 3 more times
4 flash chips found, Total DiskOnChip size: 32mbytes
mtd: Giving out device 0 to DiskOnChip Millennium
M-Systems NAND Flash Transition Layer driver. (C) 1999 MVHI
$Id blah blah blah
mtd->read = c0174410, size = 33554432, erasesize = 8192
NFTL_setup
Cannot calculate an NFTL geometry to match size of 0xfa60.
Using C:1001 H:16 S:4 (== 0xfa40 sects)
Partition check:
	nftla:<6>NFTL_request
NFTL Read request, from sector 0x000 for 0x0002 sectors
Waiting for mutex
Got mutex
NFTL read request of 0x2 sectors @ 0 (req->nr_sectors == 2)
NFTL read request completed OK
end_request(1)
	nftla1
...TCP junk...
request_module[block-major-100]: root fs not mounted
cannot open root device 6401 blah blah blah

So, it ends the same :P
as I mentioned before, it installs to fla1 before, on the 2.2.x kernel that
I don't have the source for...would this be a problem? Also, I am using
dLILO to boot this kernel. lilo.conf is using /dev/fla1...is that wrong? I
have NFTL support, but no FTL support.  I am going to try to make it boot
off of /dev/nftla1 and see what happens. I am not confident it will help
though. thanks for the time!

Jason

-----Original Message-----
From: linux-mtd-admin@lists.infradead.org
[mailto:linux-mtd-admin@lists.infradead.org]On Behalf Of David Woodhouse
Sent: Friday, May 04, 2001 5:27 PM
To: Jason Walker
Cc: MTD Mailing List
Subject: Re: MTD and 2.4



jasonw@uswo.net said:
>  I did as you said, enabled CONFIG_MTD_DOC2001 and checked out the
> #define in docprobe.c and it was already enabled.

> request_module[doc2000]: Root fs not mounted

Argh. Sorry, _disable_ DOC_SINGLE_DRIVER and use doc2001.
The less likely to work alternative is to leave it _enabled_ and use
doc2000. The message above is because it's trying to load the doc2000
driver, because DOC_SINGLE_DRIVER is enabled and the doc2000 option isn't
(only the doc2001 option).

This will be made less complex - the DOC_SINGLE_DRIVER is an attempt to
merge it all into one, but some people still find the doc2001 driver to be
more reliable.

--
dwmw2



______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

Re: MTD and 2.4

[David Woodhouse]

jasonw@uswo.net said:
> request_module[block-major-100]: root fs not mounted cannot open root
> device 6401 blah blah blah 

Quite why someone felt it necessary to register block major 100 for the 
strangely named 'fla' device, when there was already a perfectly usable 
major assigned for NFTL, I have no idea.

Switching your root device to /dev/nftla1 should fix it.

--
dwmw2

RE: MTD and 2.4

[Jason Walker]

of course, when I am using the 2.2.17 kernel used to install this stuff, it
says this then running dLILO:
cannot locate block-major-93

when I have /dev/nftla1 in my lilo.conf. hmmmm. I assume that's because I
don't have nftla in thsi mystery 2.2.x kernel.

perhaps rdev'ing the 2.4 kernel I am working on would be a better approach.

Jason

-----Original Message-----
From: David Woodhouse [mailto:dwmw2@redhat.com]On Behalf Of David
Woodhouse
Sent: Friday, May 04, 2001 8:23 PM
To: Jason Walker
Cc: MTD Mailing List
Subject: Re: MTD and 2.4



jasonw@uswo.net said:
> request_module[block-major-100]: root fs not mounted cannot open root
> device 6401 blah blah blah

Quite why someone felt it necessary to register block major 100 for the
strangely named 'fla' device, when there was already a perfectly usable
major assigned for NFTL, I have no idea.

Switching your root device to /dev/nftla1 should fix it.

--
dwmw2

Re: MTD and 2.4

[David Woodhouse]

jasonw@uswo.net said:
>  perhaps rdev'ing the 2.4 kernel I am working on would be a better
> approach. 

Or just pass 'root=/dev/nftla1' on the command line, making sure the LILO 
doesn't try to be clever. I think you need to use 'append=' for that.

You have to make sure that nftla is in the root device table in init/main.c 
for that, too.

--
dwmw2

Invalid ioctl

[Edmund Troche]

I created a 8MB partition (nftla1) on a 8MB DoC 2000, and tried to cp a jffs
image that was created with mkfs.jffs, and got the following message:
    Invalid ioctl 5401 (MEMGETINFO = 80204d01)
    ECC needs a full sector write (adr: 9de00 size 134)

The DiskOnChip is being found @ address 0xD6000 and it correctly detects it as
8MB. JFFS and MTD support is compiled in, no modules in this case.

Anyone familiar with what may be the problem? Thanks in advance for any help.


Edmund Troche

Re: Invalid ioctl

[Edmund Troche]

I have  the same results with a 48MB DoC 2000 also.


Edmund

Edmund Troche wrote:

> I created a 8MB partition (nftla1) on a 8MB DoC 2000, and tried to cp a jffs
> image that was created with mkfs.jffs, and got the following message:
>     Invalid ioctl 5401 (MEMGETINFO = 80204d01)
>     ECC needs a full sector write (adr: 9de00 size 134)
>
> The DiskOnChip is being found @ address 0xD6000 and it correctly detects it as
> 8MB. JFFS and MTD support is compiled in, no modules in this case.
>
> Anyone familiar with what may be the problem? Thanks in advance for any help.
>
> Edmund Troche
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/