public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Russ Dill <Russ.Dill@asu.edu>
To: John Sutton <john@scl.co.uk>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Booting from DOC2000 with GRUB loader
Date: Wed, 01 May 2002 13:15:36 -0700	[thread overview]
Message-ID: <1020284137.873.2359.camel@russ> (raw)
In-Reply-To: <02050120383503.07252@diva.localdomain>

 
> or nftl_format /dev/mtd0 98304  (bytes)

this one is correct

> I'm nervous about messing this up because since I put grub on the DoC, the
> machine only ever boots from the DoC - completely ignores floppy, scsi disks
> and cdrom.  So if I screw up this nftl_format and trash grub, I'm going to end
> up with an unbootable system ;-(  (OK, I'll just have to pull the DoC chip out
> of the board *again*, but even this gives me the eebies, so tight is the damn
> thing stuck in its socket!  And anyway, if the system is unbootable with the
> DoC chip in there, how am I ever going to reprogram it?)
> 
> Help much appreciated!

*** WARNING *** WARNING *** WARNING *** WARNING ***

THIS CAN DAMAGE YOUR HARDWARE AND BLOW YOU UP
(but it seems to work for me)

*** WARNING *** WARNING *** WARNING *** WARNING ***

I have an ISA card for the DOC2000, I boot up my workstation, carefully
plug in the isacard, modprobe doc2000, insmod docprobe insmod mtdchar
(if necessary) insmod nftl (if necessary). Do whatever I need to do,
rmmod nftl, rmmod docprobe, rmmod doc2000, and remove the card. On my
machine, doing this using the devfsd nodes causes an oops after the
first time, a simple workaround is using hand made device files.

*** WARNING *** WARNING *** WARNING *** WARNING ***

THIS CAN DAMAGE YOUR HARDWARE AND BLOW YOU UP
(but it seems to work for me)

*** WARNING *** WARNING *** WARNING *** WARNING ***

  parent reply	other threads:[~2002-05-01 20:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-01 19:17 Booting from DOC2000 with GRUB loader John Sutton
2002-05-01 19:49 ` Ilguiz Latypov
2002-05-01 19:49 ` Nikhil Goel
2002-05-01 20:15 ` Russ Dill [this message]
2002-05-02  7:47 ` John Sutton
2002-05-02  9:32   ` Russ Dill
2002-05-02 10:56     ` John Sutton
2002-05-02 16:09       ` Ilguiz Latypov
2002-05-02 17:33         ` Jasmine Strong
2002-05-02 17:39       ` Jasmine Strong
2002-05-02 18:17         ` Frederick Lefebvre
2002-05-02 18:45           ` Ilguiz Latypov
2002-05-03 13:40     ` John Sutton
2002-05-03 16:19       ` Jasmine Strong
  -- strict thread matches above, loose matches on Subject: below --
2002-04-26  2:19 Zhiwei Yu
2002-04-26  2:35 ` Russ Dill

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=1020284137.873.2359.camel@russ \
    --to=russ.dill@asu.edu \
    --cc=john@scl.co.uk \
    --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