public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Christopher Fowler <cfowler@outpostsentinel.com>
To: Ilguiz Latypov <ilatypov@superbt.com>
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: X Windows Performance with DOC 2000
Date: 21 Jun 2002 20:15:23 -0400	[thread overview]
Message-ID: <1024704926.2582.1.camel@devel> (raw)
In-Reply-To: <Pine.LNX.4.44.0206211931530.18637-100000@server.superbt.com>

Even if I could get it to work, I'm still going with CF.  M-SYS really
needs to change the name Disk on Chip to Chip on Chip.  It is not
seamless as their marketing department would like you to believe.

Chris

On Fri, 2002-06-21 at 20:01, Ilguiz Latypov wrote:
> 
> I found one message of March 6, 2002 where the MTD-patched GRUB displayed 
> the prompt.  I think this was half a success as I am an optimist :-)
> 
> I believe you did create a file system on top of NFTL layer and put the 
> /boot/grub/menu.lst configuration file there.  This file tells GRUB which 
> partition to open and which kernel to load.
> 
> The difficulties with reformatting DoC by using the M-Sys'es DFORMAT might 
> be due to grub_firmware indeed.
> 
> > So I do a dformat /win:D000 /s:DOC504.exb /FIRST /NOFORMAT /Y and I get
> > the following error:
> > 
> > Error writing EXB
> > Status code 26 (flUnknownMedia) received from flPlaceExbByBuffer.
> > Format Failed.
> 
> Perhaps, running the same utility with /s:* and without /noformat may help 
> in erasing the ext2 partitions.
> 
> See pages 5 and 7 of
> 
>     http://www.m-sys.com/files/Manuals%5Cdoc%5CDOC_Tool.pdf
> 
> Ilguiz
> 
> On 21 Jun 2002, cfowler wrote:
> 
> > #2) Grub destroyed my first DOC.  I use doc-lilo.  Everytime I flash a  
> >     new kernel on the DOC I have to re-run doc-lilo.
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 
> 

  reply	other threads:[~2002-06-22  0:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-14  3:09 X Windows Performance with DOC 2000 David Cooper
2002-06-15 22:32 ` Charles Manning
2002-06-17 22:30   ` David Cooper
2002-06-17 22:32     ` Ilguiz Latypov
2002-06-18  0:22       ` David Cooper
2002-06-18  0:40         ` Brendan J Simon
2002-06-21 23:33           ` Christopher Fowler
2002-06-18 14:11         ` Ilguiz Latypov
2002-06-20 19:41           ` David Cooper
2002-06-20 21:59             ` David Woodhouse
2002-06-21  0:33               ` David Cooper
2002-06-21  0:39                 ` David Woodhouse
2002-06-21  5:46                   ` David Cooper
2002-06-21  7:04                     ` David Woodhouse
2002-06-26 18:30                       ` David Cooper
2002-06-26 21:28                         ` David Woodhouse
2002-06-21 13:56                     ` Ilguiz Latypov
2002-06-21 14:09                       ` cfowler
2002-06-21 14:12                         ` David Woodhouse
2002-06-21 14:28                           ` cfowler
2002-06-22  0:01                             ` Ilguiz Latypov
2002-06-22  0:15                               ` Christopher Fowler [this message]
2002-06-22  1:14                                 ` David Cooper
2002-06-22  1:11                                   ` Gonzalo Servat
2002-06-22  9:18                                 ` David Woodhouse

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=1024704926.2582.1.camel@devel \
    --to=cfowler@outpostsentinel.com \
    --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