public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Daniel Cox" <DCox@microbits.com.au>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Grub
Date: Tue, 29 May 2001 09:24:16 +0100	[thread overview]
Message-ID: <19508.991124656@redhat.com> (raw)
In-Reply-To: <sb13d79c.074@mail.microbits.com.au>

DCox@microbits.com.au said:
> There is no patch for .5.96 and I cant find grub .5.97!

There appears to be a 'grub-0.5.96-doc.patch' in my working directory. I've 
committed it. 

0.5.97 is what the current CVS version is called, I think.


> However even with the --enable-diskonchip option for ./configure, root
> (dc0) does not work - selected disk does not exist! For now I am
> running from a hard disk (hd0). 

Does it even print the messages about probing for a DiskOnChip?

DCox@microbits.com.au said:
>  Once the firmware is installed, the following appears
>   Could not find valid boot record
>   Could not mount NFTL device

Argh. I've been seeing a lot of that recently. Something in the sanity 
checks is failing. I'll put some more verbose messages in.


DCox@microbits.com.au said:
>  nftl_format works but removes the firmware. 

Give it an offset and it'll skip the firmware.
	nftl_format /dev/mtd0 49152


DCox@microbits.com.au said:
>  How can I get the firmware installed along with a formatted
> partition? 

If you mean the original firmware, then you have to do that from DOS with
DFORMAT. If you mean Grub, then install Grub as before (having fixed it) 
and then use nftl_format with an offset of (IIRC) 65536.


DCox@microbits.com.au said:
>  How can I access the DOC device from Grub? 

The Grub support was never 100% completed. It worked to a certain extent but
wasn't reliable. I never got time to debug it, although it should be
relatively simple. It seemed that the first time you read a sector it would
return incorrect data. The next time it would work. So repeating the
'kernel=' command a few times till Grub stopped complaining about errors,
and then booting, worked. 


>  Does JFFS work with the DOC? I read the archive and it was recently
> mentioned that it does not work.

The DiskOnChip hardware driver only accepts write requests of a single 
page. It needs to be fixed to allow larger writes - to loop till it's done.
At that point, you should be able to use JFFS on it, although you only have 
error detection, not error _correction_. The ideal solution is to add the 
planned ECC support to JFFS2 and use that.

--
dwmw2

  reply	other threads:[~2001-05-29  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29  7:38 Grub Daniel Cox
2001-05-29  8:24 ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-22 15:21 GRUB Erik Smit
2002-11-25 10:09 ` GRUB Henrik Nordstrom
2001-04-09 19:26 GRUB Carson, Jon A.
2001-04-05 21:00 GRUB Chris Robson

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=19508.991124656@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=DCox@microbits.com.au \
    --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