From: Veselin Mijuskovic <panzer@etf.bg.ac.yu>
To: Ilguiz Latypov <ilatypov@superbt.com>
Subject: Re: DOC2000 + GRUB/LILO booting problems
Date: Mon, 18 Mar 2002 14:48:55 +0100 [thread overview]
Message-ID: <20020318134855.GA22168@etf.bg.ac.yu> (raw)
In-Reply-To: <Pine.LNX.4.44.0203141100270.3848-100000@server.superbt.com>
Ilguiz Latypov [Thu, Mar 14, 2002 at 11:06:28AM -0500, Re: DOC2000 + GRUB/LILO booting problems]:
>
> Veselin,
>
> Could you overwrite the NFTL information when installing grub_firmware?
I'm pretty new to MTD and all these stuff, but if this is the
case, how the kernel mounts the /dev/nftla1 with no problems at all when I
boot from the hard disk?
> I believe one can re-format the chip with
> nftl_format /dev/mtd0 0x18000
>
Isn't it dangerous? It's a 16MB DOC2000 - are these the right
parameters? Can I overwrite bad block table with the above command?
How can I recover bad block table (I can make 'dd if=/dev/mtd0 of=some_file'
to create a backup copy, can I)?
Sorry to bother you with this, but it's rather important.
Cheers,
--
| \|/ Panzer (a.k.a Veselin Mijuskovic), Unix SysAdmin
/|\ | Computer Centre, School of Electical Engineering, University of Belgrade
-------------------------------------------------------------------------------
Unix is very friendly, it's just picky about who its friends are
next prev parent reply other threads:[~2002-03-18 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 15:20 DOC2000 + GRUB/LILO booting problems Veselin Mijuskovic
2002-03-14 16:06 ` Ilguiz Latypov
2002-03-18 13:48 ` Veselin Mijuskovic [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-18 15:34 Ilguiz Latypov
2002-03-18 15:57 ` David Woodhouse
2002-03-18 16:17 ` Veselin Mijuskovic
[not found] ` <Pine.LNX.4.44.0203181430360.23362-100000@server.superbt.com>
2002-03-19 11:24 ` Veselin Mijuskovic
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=20020318134855.GA22168@etf.bg.ac.yu \
--to=panzer@etf.bg.ac.yu \
--cc=ilatypov@superbt.com \
/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