From: Peter Keel <seegras@discordia.ch>
To: linux-mtd@lists.infradead.org
Subject: Re: How to Clean bad Grubfirmware off DOC?
Date: Fri, 28 Jun 2002 20:47:40 +0200 [thread overview]
Message-ID: <20020628184740.GA6828@discordia.ch> (raw)
In-Reply-To: <3D1B22F2.18643@webmta2>
* on the Thu, Jun 27, 2002 at 10:36:34PM +0800, g_friend@etang.com wrote:
> >Since you cannot boot with the doc2000 installed, I'd recommend trying the
> >following, **very carefully**:
> > 1. Turn off system
> > 2. Remove DoC from board (I assume it's an ISA/PCI board with DoC socketed?)
> > 3. Install *empty* DoC board
> > 4. Boot into DOS
> > 5. Install latest M-Sys DOS utilities (if not already done)
> > 6. *** CAREFULLY *** install DoC into socket
> > 7. Run DFORMAT utility to replace grub firmware
> >*Disclaimer: This procedure has worked for me, but it could do *bad things*
> >to your DoC. Use it only as a last resort.
>
> By saying above ,do you mean "hot plug" ?
And do you mean you have to have
- DOS (why shouldn't I use Linux?)
- An Empty DOC
??
> >If your machine supports "Network" boot, you may want to try configuring GRUB
> >with the "--enable-diskonchip-biosnetboot" option. This will allow you to
> >selectively boot from the DoC, returning to booting from a hard drive or
> >floppy when needed.
IF your board does support that. Mine does not. That's why the whole
fun started. That, and the inability of grub to access my filesystem.
Peter
--
Those who give up essential liberties for temporary safety deserve
neither liberty nor safety. -- Benjamin Franklin
next prev parent reply other threads:[~2002-06-28 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 14:36 How to Clean bad Grubfirmware off DOC? g_friend
2002-06-28 18:47 ` Peter Keel [this message]
2002-06-28 21:58 ` Mark Meade
2002-06-28 23:06 ` Peter Keel
-- strict thread matches above, loose matches on Subject: below --
2002-06-27 14:59 Mark Meade
2002-06-27 13:00 Mark Meade
2002-06-27 9:43 g_friend
2002-06-28 16:40 ` Peter Keel
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=20020628184740.GA6828@discordia.ch \
--to=seegras@discordia.ch \
--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