64M DOC2000
I've just tried a 64M Doc2000 with kernel 2.2.16 and the IGEL driver, and it is not recognised. I have no problems with 16M and 32M parts. Can someone on the list confirm that this is the case?
Ian T.
To unsubscribe, send "unsubscribe mtd" to [email protected]
Quoted 3 lines · [email protected] said:
I've just tried a 64M Doc2000 with kernel 2.2.16 and the IGEL driver, and it is not recognised. I have no problems with 16M and 32M parts. Can someone on the list confirm that this is the case?
No clue. Try it with the free driver and see what happens.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to [email protected]
The part is recognised by the mtd driver with 2.4.0.
I can partition it with fdisk /dev/nftl and create
ext2 disks.
However, when I try to copy data to it I start getting input/output errors after I've got a certain amount of data (yet to be determined) on it.
Ian T.
Quoted 10 lines · David Woodhouse
Quoted 3 lines · [email protected] said:
I've just tried a 64M Doc2000 with kernel 2.2.16 and the IGEL driver, and it is not recognised. I have no problems with 16M and 32M parts. Can someone on the list confirm that this is the case?
No clue. Try it with the free driver and see what happens.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to [email protected]
Quoted 2 lines · [email protected] said:
The part is recognised by the mtd driver with 2.4.0. I can partition it with fdisk
/dev/nftland create ext2 disks.
Good.
Quoted 3 lines
However, when I try
to copy data to it I start getting input/output errors after I've got a certain amount of data (yet to be determined) on it.
Urgh. That may be normal though :(
Can you post the whole of the kernel's output while you're doing this, including what it says when it probes and finds the device?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to [email protected]
Actually I had to play with the code to get it to recognise the device. This
is probably due to my test setup.
I boot from a hard drive and set the DOC up from within Linux. This means contending
with the LILO/DOC interaction so I use DOC2.FFF to blank out the conflicting region.
The detection code misses the device when using this, because it reads FFs instead of the
55 and AA signature. I took out that detection and restricted doc_locations[] to
the actual location of the DOC and the device is found.
Kernel output to follow.
Ian T.
Quoted 11 lines · David Woodhouse
Quoted 2 lines · [email protected] said:
The part is recognised by the mtd driver with 2.4.0. I can partition it with fdisk
/dev/nftland create ext2 disks.Good.
Quoted 3 lines
However, when I try
to copy data to it I start getting input/output errors after I've got a certain amount of data (yet to be determined) on it.
Quoted 7 lines
Urgh. That may be normal though :(
Can you post the whole of the kernel's output while you're doing this, including what it says when it probes and finds the device?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to [email protected]