public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Frederic Marmond <fmarmond@eprocess.fr>
To: Ilguiz Latypov <ilatypov@superbt.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: can't boot with DiskOnChip2000 / nftlmount UnitSizeFactor ????
Date: Wed, 29 May 2002 17:53:57 +0200	[thread overview]
Message-ID: <3CF4F995.4060608@eprocess.fr> (raw)
In-Reply-To: Pine.LNX.4.44.0205291138490.3100-100000@server.superbt.com

...
i made a "nftl_format /dev/mtd0 2097152", from the lastest CVS from 
mtd-tool...
it works fine, and i can make a fs (ext2) on /dev/nftla1 (after, of 
course having made a fdisk /dev/nftla)

but the message still remain at boot time (see it in dmesg
NFTL driver: nftlcore.c $Revision: 1.82 $, nftlmount.c $Revision: 1.25 $
Sorry, we don't support UnitSizeFactor of != 1 yet.
Could not find valid boot record
Could not mount NFTL device
)

this check is in nftlmount.c in kernel directory (drivers/mtd/nftlmount.c)
do you mean that i can comment this check?
do you know what is the risk?

Fred

Ilguiz Latypov wrote:

>On Wed, 29 May 2002, Frederic Marmond wrote:
>
>>is there any info to make my nftlmount works, even if i have this
>>message? ("Sorry, we don't support UnitSizeFactor of != 1 yet.")
>>
>
>I circumvented such problem by re-formatting the chip with the MTD
>nftlformat utility.  The latter has a built-in check for erase block size
>which you may need to remove if you find the risk acceptable.
>
>Ilguiz
>
>

      reply	other threads:[~2002-05-29 15:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29 15:17 can't boot with DiskOnChip2000 / nftlmount UnitSizeFactor ???? Frederic Marmond
2002-05-29 15:40 ` Ilguiz Latypov
2002-05-29 15:53   ` Frederic Marmond [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CF4F995.4060608@eprocess.fr \
    --to=fmarmond@eprocess.fr \
    --cc=ilatypov@superbt.com \
    --cc=linux-mtd@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox