public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Selwyn Tang <selwyn@hectrix.com>
To: linux-mtd@lists.infradead.org
Subject: Re: redhat 9, doc 2000
Date: Tue, 07 Oct 2003 10:55:33 +0800	[thread overview]
Message-ID: <3F822B25.2020600@hectrix.com> (raw)
In-Reply-To: <20031006213435.38037.qmail@web9906.mail.yahoo.com>

On 10/07/2003 05:34 AM, Slim wrote:
> the above, but the doc-grub always loads despite changing the boot
> device in the bios setup.  Now I can't boot from the hard drive unless I
> disable all access to the doc.  Any workaround?

I think you have built a GRUB firmware and written it on the DOC. But
there is a catch that the firmware will register as a BIOS extension
that will take over the boot sequence from the BIOS. You should patch
GRUB with the ctrlbypass functionality. It allows you to bypass the GRUB
on DOC and boot according to your BIOS by holding CTRL while booting. I
used grub-2003-01-08.doc.patch here. Refer to p.262-266 of Karim's book.

Now, to get back to boot from your harddisk and have a chance to rewrite
the correct firmware, you may try hotplugging your DOC after the system
is booted. Although it is a bit undesirable and dangerous, I tried once
and it seemed alright. Once, I even accidentally pulled out a DOC with a
screwdriver while the system was still running, and the DOC was not
damaged at all.

Selwyn

  parent reply	other threads:[~2003-10-07  2:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1A6b7A-0004WA-Gx@pentafluge.infradead.org>
2003-10-06 21:34 ` redhat 9, doc 2000 Slim
2003-10-06 21:51   ` Ilguiz Latypov
2003-10-06 22:00   ` Michael McLellan
2003-10-07  2:55   ` Selwyn Tang [this message]
     [not found] <E1A7v07-0003hH-Sp@pentafluge.infradead.org>
2003-10-10 20:09 ` Slim
     [not found] <E1A6pZU-0003Bs-DJ@pentafluge.infradead.org>
2003-10-09 16:33 ` Slim
2003-10-10  1:40   ` Selwyn Tang
2003-10-10  5:19     ` David Woodhouse
2003-09-29 14:05 Chiasson, John
2003-09-30  2:00 ` Selwyn Tang

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=3F822B25.2020600@hectrix.com \
    --to=selwyn@hectrix.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