* Is this normal?
@ 2003-04-08 3:23 Gregg C Levine
2003-04-08 8:15 ` David Woodhouse
0 siblings, 1 reply; 3+ messages in thread
From: Gregg C Levine @ 2003-04-08 3:23 UTC (permalink / raw)
To: linux-mtd
Hello from Gregg C Levine
As the subject says, "Is this normal?". I have a DOC-2000, installed
on an ISA based carrier board. I have also replaced its flakey M-SYS
firmware with the GRUB based one.
Since I have Lilo installed on the drive, as well as a currently
inactive grub, I half expected to see the Lilo multiple kernel boot
prompt. Instead I saw the grub menu that I have placed there. As it
happens I do not have an image placed on the DOC-2000.
Also, when I re-installed the card after removing it, it did the same
thing, and this filesystem is newer then the firmware. (An engineering
casualty occurred, and I needed to reinstall Linux on the drive.)
Now the question remains: Any suggestions, again, for constructing
that image to place on the DOC-2000? And how would I tell the computer
to boot it, or the resident hard drive?
-------------------
Gregg C Levine hansolofalcon@worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke." Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Is this normal?
2003-04-08 3:23 Is this normal? Gregg C Levine
@ 2003-04-08 8:15 ` David Woodhouse
2003-04-08 17:02 ` Gregg C Levine
0 siblings, 1 reply; 3+ messages in thread
From: David Woodhouse @ 2003-04-08 8:15 UTC (permalink / raw)
To: Gregg C Levine; +Cc: linux-mtd
On Tue, 2003-04-08 at 04:23, Gregg C Levine wrote:
> so replaced its flakey M-SYS firmware with the GRUB based one.
> Since I have Lilo installed on the drive, as well as a currently
> inactive grub, I half expected to see the Lilo multiple kernel boot
> prompt. Instead I saw the grub menu that I have placed there.
That is indeed normal. Since you removed the M-Systems firmware, there's
nothing to make the DiskOnChip appear as a 'normal' hard drive via the
BIOS 'normal' INT 13h disc access routines. So LILO cannot possibly
work.
> Now the question remains: Any suggestions, again, for constructing
> that image to place on the DOC-2000? And how would I tell the computer
> to boot it, or the resident hard drive?
You are, as ever, very difficult to comprehend. What image to place on
the DOC2000? Format it (with the Grub firmware) with DFORMAT, or with
nftl_format if you must, make an ext2 file system on /dev/nftl, and have
Grub's boot menu boot from the ext2 file system.... what are you
missing?
--
dwmw2
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Is this normal?
2003-04-08 8:15 ` David Woodhouse
@ 2003-04-08 17:02 ` Gregg C Levine
0 siblings, 0 replies; 3+ messages in thread
From: Gregg C Levine @ 2003-04-08 17:02 UTC (permalink / raw)
To: linux-mtd; +Cc: 'David Woodhouse'
(See Below!)
> -----Original Message-----
> From: linux-mtd-bounces@lists.infradead.org [mailto:linux-mtd-
> bounces@lists.infradead.org] On Behalf Of David Woodhouse
> Sent: Tuesday, April 08, 2003 4:15 AM
> To: Gregg C Levine
> Cc: linux-mtd@lists.infradead.org
> Subject: Re: Is this normal?
>
> On Tue, 2003-04-08 at 04:23, Gregg C Levine wrote:
> > so replaced its flakey M-SYS firmware with the GRUB based one.
> > Since I have Lilo installed on the drive, as well as a currently
> > inactive grub, I half expected to see the Lilo multiple kernel
boot
> > prompt. Instead I saw the grub menu that I have placed there.
>
> That is indeed normal. Since you removed the M-Systems firmware,
there's
> nothing to make the DiskOnChip appear as a 'normal' hard drive via
the
> BIOS 'normal' INT 13h disc access routines. So LILO cannot possibly
> work.
>
> > Now the question remains: Any suggestions, again, for constructing
> > that image to place on the DOC-2000? And how would I tell the
computer
> > to boot it, or the resident hard drive?
>
> You are, as ever, very difficult to comprehend. What image to place
on
> the DOC2000? Format it (with the Grub firmware) with DFORMAT, or
with
> nftl_format if you must, make an ext2 file system on /dev/nftl, and
have
> Grub's boot menu boot from the ext2 file system.... what are you
> missing?
>
> --
> dwmw2
Hello from Gregg C Levine
Basically yes. When I wrote the message that you're confused about it
was very early in the morning here, and at that time I don't even
pretend to make myself clear to others. I apologize.
How do I go about formatting it with the Grub firmware in place? And
since I am leaning towards formatting it with an ext2 file system, how
do I go about attaching it to the device name you chose. And then have
it come up on the Grub's boot menu boot from the ext2 file system.
Yes, that's what I was missing.
Gregg C Levine hansolofalcon@worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke." Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-04-08 17:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-04-08 3:23 Is this normal? Gregg C Levine
2003-04-08 8:15 ` David Woodhouse
2003-04-08 17:02 ` Gregg C Levine
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox