Re: [Fwd: M-Sys drivers]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Good theory. The thing that gets me is that I see this same error when I fdisk a device like /dev/sda1 in place of /dev/sda. Is it possible that the nftl driver is handing out the wrong partition information? Is there a way that I can know for sure that the device was formatted correctly by the nftl driver?
I'm having this same problem with the MD-2800-D08 and MD-2202-D32-X.
If you development folks have any suggestions I'm game. Please enlighten me!
Quoted 47 lines · Donald Green
I've put the config put up. It is for a 2.6.20 kernel. I won't have a chance to boot the image you made until sometime early next week but I'd be happy to give it a try. It sounds like you had the same experience I did. I loaded the nftl driver and it formatted the DOC. I was theorizing that this creates an incorrect bad sector map and that that could be corrected by using dformat. My process fails when I try to complete the fdisk formatting operation by commiting the changes with the w command.
-Don
-----Original Message-----
From: Andy Kennedy [mailto:[email protected]] Sent: Friday, August 10, 2007 10:57 AM
To: Donald Green
Subject: Re: [Fwd: M-Sys drivers]Quoted 5 lines · Donald Green
Hi Andy:
The kernel I have in the iso I'm sending is built for a Geode and
uses
Quoted 7 lines
the natsemi Ethernet driver, will these settings work? If not let me know what processor and Ethernet driver your target has and I can rebuild it.
-Don
I'm sure that that will work. . . it isn't much different from the Pentium-MMX (they're all pretty much the same until you get to the PII anyways). There would probably be some obscure functionality differences, but if I can get a good kernel config - hey, that's the price I'm willing to pay. Can you also send me a config file and version of the kernel you have?
If you'd be willing to try it, I'd like for you to attempt to load my floppy on your computer to see if you can mount the nftla1 -- one issue,
however, is that when I load the nftl driver (I have it as a module in the initrd), it formats the DOC -- which may blow your system away. . . but if you are willing to take the risk I'd like to know if my configuration works. It is kernel 2.6.22.1 without any patches and then
there's BusyBox. I don't know the BusyBox version but if you boot the disk, you'll see the version. Booting the disk is harmless -- it is just loading that module that seems to really hose up everything.
Thanks again for your help!
Andy
Re: [Fwd: M-Sys drivers] ; Re: DiskOnChip 2000 (DOC 2000) woes.
Quoted 6 lines · Andy Kennedy
Good theory. The thing that gets me is that I see this same error when I fdisk a device like
/dev/sda1in place of/dev/sda. Is it possible that the nftl driver is handing out the wrong partition information? Is there a way that I can know for sure that the device was formatted correctly by the nftl driver?
Quoted 7 lines
I'm having this same problem with the MD-2800-D08 and MD-2202-D32-X.
If you development folks have any suggestions I'm game. Please enlighten me!
Donald Green wrote:
[quote=http://www.ibiblio.org/pub/Linux/docs/HOWTO/Disk-on-Chip-HOWTO]
2. The TrueFFS Linux driver package contains three different folders:
+ Documentation: this contains a PDF document describing the various functions of TrueFFS.
+ dformat_5_1_4_37: this contains a utility dformat, which is used to update the firmware on the DiskOnChip (DOC) and to create low level partitions on the DOC.
+ doc-linux-5_1_4_20: this contains patches, initrd scripts and other utilities.
3. Now apply the patch to the kernel. We will use the linux-2_4_7-patch file that is present in linux_binary.5_1_4/doc-linux-5_1_4_20/driver. The following commands are used for this purpose:
cd linux_binary.5_1_4/doc-linux-5_1_4_20/driver
patch -p1 -d /usr/src/linux < linux-2_4_7-patch
This will create a directory named doc in the linux/drivers/block directory.
[/quote]
Okay, so do I have to install the 5.1.4 DOC driver to make the DOC2000 work with 2.6.22.1??? Should I back up to 2.4.18 like the howto says?
Andy
Using configured DiskOnChip probe address 0xd8000
DiskOnChip 2000 found at address 0xD8000
Flash chip found: Manufacturer ID: EC, Chip ID: 75 (Samsung:NAND 32MiB 3,3V 8-bit) Flash chip at floor 1, chip 0 is different:
Unknown flash chip found: F9 F9
Please report to [email protected]
Flash chip at floor 2, chip 0 is different:
Unknown flash chip found: F9 F9
Please report to [email protected]
Flash chip at floor 3, chip 0 is different:
Unknown flash chip found: F9 F9
Please report to [email protected]
1 flash chips found. Total DiskOnChip size: 32 MiB
For giggles, I recompiled again with the old driver. The above is the message I get. This supports my theory that the flash drive that I'm attempting to fdisk is NOT the base chip, but appears to be a partition of the device. David/List???? What am I doing wrong?
Andy
Quoted 73 lines · Andy Kennedy
Good theory. The thing that gets me is that I see this same error when I fdisk a device like
/dev/sda1in place of/dev/sda. Is it possible that the nftl driver is handing out the wrong partition information? Is there a way that I can know for sure that the device was formatted correctly by the nftl driver?I'm having this same problem with the MD-2800-D08 and MD-2202-D32-X.
If you development folks have any suggestions I'm game. Please enlighten me!
Quoted 38 lines · Donald Green
I've put the config put up. It is for a 2.6.20 kernel. I won't have a chance to boot the image you made until sometime early next week but I'd be happy to give it a try. It sounds like you had the same experience I did. I loaded the nftl driver and it formatted the DOC. I was theorizing that this creates an incorrect bad sector map and that that could be corrected by using dformat. My process fails when I try to complete the fdisk formatting operation by commiting the changes with the w command.
-Don
-----Original Message-----
From: Andy Kennedy [mailto:[email protected]] Sent: Friday, August 10, 2007 10:57 AM
To: Donald Green
Subject: Re: [Fwd: M-Sys drivers]Quoted 6 lines · Donald Green
Hi Andy:
The kernel I have in the iso I'm sending is built for a Geode and
uses
Quoted 8 lines
the natsemi Ethernet driver, will these settings work? If not let me know what processor and Ethernet driver your target has and I can rebuild it.
-Don
I'm sure that that will work. . . it isn't much different from the Pentium-MMX (they're all pretty much the same until you get to the PII anyways). There would probably be some obscure functionality differences, but if I can get a good kernel config - hey, that's the price I'm willing to pay. Can you also send me a config file and version of the kernel you have?
Quoted 13 lines
If you'd be willing to try it, I'd like for you to attempt to load my floppy on your computer to see if you can mount the nftla1 -- one issue,
however, is that when I load the nftl driver (I have it as a module in the initrd), it formats the DOC -- which may blow your system away. . . but if you are willing to take the risk I'd like to know if my configuration works. It is kernel 2.6.22.1 without any patches and then
there's BusyBox. I don't know the BusyBox version but if you boot the disk, you'll see the version. Booting the disk is harmless -- it is just loading that module that seems to really hose up everything.
Thanks again for your help!
Andy______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/