public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Henrik Nordstrom <hno@marasystems.com>
To: Mark Meade <mark@lakeshoremicro.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: 48meg DOC
Date: Mon, 2 Sep 2002 15:46:57 +0200	[thread overview]
Message-ID: <200209021546.57583.hno@marasystems.com> (raw)
In-Reply-To: <20020902132838.NFAO11061.sccrmhc01.attbi.com@there>

Mark Meade wrote:

> You shouldn't need to have GRUB on the DoC to support multiple partitions.
> Grub is simply the bootloader -- the MTD/DoC stuff should work the same
> regardless of the presence of GRUB/LILO/whatever.

I ask because the 5.1.2 M-Sys DOS firmware seems to crap out badly if there is 
multiple partitions in the DoC disk image.. and it is a bit hard to boot the 
system if the DoC firmware does not play..

WIth a single partition everithing works just fine.

If I add another partition to the DoC disk image then the DOS firmware no 
longer boots the OS from the DoC, and if I load GRUB or DOS via the netwok 
(PXE) then GRUB cannot read the partition table and finds yet another ghost 
harddrive in the system, and DOS does not find any partition table on the 
DoC.. Funny eh?

> Use the GRUB firmware if the DoC is the primary non-volatile storage in
> your system.  Off-topic, but if you have a MBR in your target system, what
> is the DoC used for?

I am referring to the MBR of the DoC, not any other device. The DoC emulates a 
harddrive and as such it has a MBR for the DOS partition table and OS 
bootstrap code.

> I have not found a reliable way to use DFORMAT to load the Grub firmware.

With the 5.1.2 version of DFORMAT GRUB installed just fine as a binary flash 
image using the DFORMAT dos tool.. only that it didn't like the NTFL 
complaining about UnitSizeFactor once booted..

  dformat /win:d600 /BDKF0:grub_firmware

Haven't yet had time to test the 4.2 DFORMAT utility. Expect to do so during 
the day.

Regards
Henrik

  reply	other threads:[~2002-09-02 13:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-30 14:04 48meg DOC Mateo Anderson
2002-08-30 15:49 ` Henrik Nordstrom
2002-09-01 14:38   ` Mark Meade
2002-09-01 15:05     ` Henrik Nordström
2002-09-02 13:27       ` Mark Meade
2002-09-02 13:46         ` Henrik Nordstrom [this message]
2002-09-02 15:55         ` David Woodhouse
2002-09-02 16:52           ` Mark Meade
  -- strict thread matches above, loose matches on Subject: below --
2002-09-02  5:39 Mateo Anderson
2002-09-02  9:06 ` David Woodhouse
2002-09-02  9:32 Mateo Anderson

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=200209021546.57583.hno@marasystems.com \
    --to=hno@marasystems.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mark@lakeshoremicro.com \
    /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