UnitSizeFactor of != 1

UnitSizeFactor of != 1

[Stephen Lee]

Hi,

I'm trying to format and install Peewee Linux on a 32M DiskOnChip2000
and have done the following:

1. Formatted the DOC with "dformat /win:D000 /s:doc524.exb". There were
no apparent errors.
2. Rebooted under Redhat7.1 with a stock 2.4.20 kernel with the
following kernel config settings:

CONFIG_MTD=y
CONFIG_MTD_DEBUG=y
CONFIG_MTD_DEBUG_VERBOSE=1
CONFIG_MTD_CHAR=y
CONFIG_MTD_DOC2000=y
CONFIG_MTD_DOCPROBE=y
CONFIG_MTD_DOCPROBE_ADDRESS=0
CONFIG_NFTL=y
CONFIG_NFTL_RW=y


and here's a portion of the kernel boot log:

Possible DiskOnChip with unknown ChipID FF found at 0xc8000
Possible DiskOnChip with unknown ChipID FF found at 0xca000
Possible DiskOnChip with unknown ChipID FF found at 0xcc000
Possible DiskOnChip with unknown ChipID FF found at 0xce000
DiskOnChip 2000 found at address 0xD0000
Flash chip found: Manufacturer ID: 98, Chip ID: 75 (Toshiba
TC58256FT/DC)
1 flash chips found. Total DiskOnChip size: 32 MiB
mtd: Giving out device 0 to DiskOnChip 2000
Possible DiskOnChip with unknown ChipID FF found at 0xd2000
Possible DiskOnChip with unknown ChipID FF found at 0xd4000
Possible DiskOnChip with unknown ChipID FF found at 0xd6000
Possible DiskOnChip with unknown ChipID FF found at 0xd8000
Possible DiskOnChip with unknown ChipID FF found at 0xda000
Possible DiskOnChip with unknown ChipID FF found at 0xdc000
Possible DiskOnChip with unknown ChipID FF found at 0xde000
Possible DiskOnChip with unknown ChipID FF found at 0xe0000
Possible DiskOnChip with unknown ChipID FF found at 0xe2000
Possible DiskOnChip with unknown ChipID FF found at 0xe4000
Possible DiskOnChip with unknown ChipID FF found at 0xe6000
Possible DiskOnChip with unknown ChipID FF found at 0xe8000
Possible DiskOnChip with unknown ChipID FF found at 0xea000
Possible DiskOnChip with unknown ChipID FF found at 0xec000
Possible DiskOnChip with unknown ChipID FF found at 0xee000
$Id: ftl.c,v 1.43 2002/02/13 15:31:37 dwmw2 Exp $
ftl_cs: FTL header not found.
NFTL driver: nftlcore.c $Revision: 1.85 $, nftlmount.c $Revision: 1.25 $
NFTL_notify_add for DiskOnChip 2000
NFTL_setup
Sorry, we don't support UnitSizeFactor of != 1 yet.
Could not find valid boot record
Could not mount NFTL device


Consequently I have no /dev/nftla. MAKEDEV from the mtd utilites was
run. cat /proc/mtd says:

mtd0: 02000000 00004000 "DiskOnChip 2000"

3. I then ran "nftl_format /dev/mtd0", rebooted and got nftla1
recognized. Fdisk worked fine with the device.

My question is whether "dformat /win:D000 /s:doc524.exb" should have
been sufficient to get DOC recognized correctly by the kernel or do I
have to run ntfl_format? If ntfl_format is required, can I simply fdisk
and format as a fat12 partition under linux?

Thanks,
Stephen

UnitSizeFactor of != 1

[Mark Meade]

On Saturday 22 March 2003 05:12 pm, Stephen Lee wrote:

> 1. Formatted the DOC with "dformat /win:D000 /s:doc524.exb". There were
> no apparent errors.
> 2. Rebooted under Redhat7.1 with a stock 2.4.20 kernel with the
> following kernel config settings:

<snip>

> NFTL driver: nftlcore.c $Revision: 1.85 $, nftlmount.c $Revision: 1.25 $
> NFTL_notify_add for DiskOnChip 2000
> NFTL_setup
> Sorry, we don't support UnitSizeFactor of != 1 yet.

<snip>

> My question is whether "dformat /win:D000 /s:doc524.exb" should have
> been sufficient to get DOC recognized correctly by the kernel or do I
> have to run ntfl_format? If ntfl_format is required, can I simply fdisk
> and format as a fat12 partition under linux?

Stephen,

With the 2.40.20 kernel, nftl_format is not required if you use the earlier 
version of the DiskOnChip DFORMAT utility (version 4.2).  This is still 
available at m-sys.com.

By default, dformat creates a fat12 partition that should be recognized under 
Linux.

Either way, if the nftl device is recognized, you should be able to run fdisk 
and format as fat12, ext2, etc.

Mark

UnitSizeFactor of != 1

[Stephen Lee]

On Sat, 2003-03-22 at 16:39, Mark Meade wrote:
> On Saturday 22 March 2003 05:12 pm, Stephen Lee wrote:
> 
> > 1. Formatted the DOC with "dformat /win:D000 /s:doc524.exb". There were
> > no apparent errors.
> > 2. Rebooted under Redhat7.1 with a stock 2.4.20 kernel with the
> > following kernel config settings:
> 
> <snip>
> 
> > NFTL driver: nftlcore.c $Revision: 1.85 $, nftlmount.c $Revision: 1.25 $
> > NFTL_notify_add for DiskOnChip 2000
> > NFTL_setup
> > Sorry, we don't support UnitSizeFactor of != 1 yet.
> 
> <snip>
> 
> > My question is whether "dformat /win:D000 /s:doc524.exb" should have
> > been sufficient to get DOC recognized correctly by the kernel or do I
> > have to run ntfl_format? If ntfl_format is required, can I simply fdisk
> > and format as a fat12 partition under linux?
> 
> Stephen,
> 
> With the 2.40.20 kernel, nftl_format is not required if you use the earlier 
> version of the DiskOnChip DFORMAT utility (version 4.2).  This is still 
> available at m-sys.com.
> 
> By default, dformat creates a fat12 partition that should be recognized under 
> Linux.
> 
> Either way, if the nftl device is recognized, you should be able to run fdisk 
> and format as fat12, ext2, etc.

Thanks Mark. I had a problem with V4.2 DFORMAT not allowing me to boot
from the C: drive (Linux) as the DOC would always take over booting if
the floppy was not inserted - even with the bios set to boot only from A
or C (primary master). DINFO showed the DOC mapped as D drive. In the
end, I DFORMATted with 5.12, used nftl_format (took at least 1/2hr for
32Meg!), fdisked as 1 fat12 partition and then formatted with
mkfs.msdos. On to PeeWee Linux!

Thanks,
Stephen