From: Peter Keel <killer@discordia.ch>
To: linux-mtd@lists.infradead.org
Subject: Re: GRUB on DoC Millennium/2000 - Instructions
Date: Mon, 24 Jun 2002 17:01:38 +0200 [thread overview]
Message-ID: <20020624150138.GA4570@discordia.ch> (raw)
In-Reply-To: <200206181253609.SM02488@there>
Hello.
First off, this is very well written; I like it. I got this far:
* on the Tue, Jun 18, 2002 at 12:55:17PM -0400, Mark Meade wrote:
> 9. Verify GRUB boot
>
> The PC should now boot from the DiskOnChip. The BIOS may say something like
> "Searching for boot record from Network...". The first DoC messages
> displayed should be:
>
> DoC Mil D000
> Jumping to Grub
> DiskOnChip Millennium found at d0000
>
> Where D000 is the "window" described earlier.
>
> When the boot process completes, there should be a "grub>" command line. We
> haven't installed a kernel or a "menu.lst" file on the DiskOnChip yet, so
> this step is just to verify that the "grub_firmware" was installed correctly,
> and that the DoC will boot.
Since I can't boot from NIC, I have it booting normal, like a disk.
Everytime, that is. Now I can't change back to lilo on the harddisk.
I have no floppy of course. And I don't like soldering the DoC off.
> At this point, you can either reboot again, change the boot sequence back to
> IDE (or whatever), and boot back into Linux. Alternatively, if you know
> where your kernel and root filesystem is on the hard drive, simply type
> something like:
>
> kernel (hd0,0)/vmlinuz-doc root=/dev/hda2
> boot
I'd love to. Of course, for some reason my grub can't read the
filesystem on the disk. The Question now is:
"If grub can't read the filesystem, how do I tell grub where the
kernel resides, and how do I find this out where it is?".
This probably belongs to some grub-mailinglist, but I don't feel like
subscribing one more mailinglist, and more importantly, I think it would
be nice to have that information included in this text as well.
Right now I'm trying to reformat and setup the disk in another machine,
in the hope that "kernel (hd0,0)/vmlinuz-doc root=/dev/hda1\nboot"
will do the trick then; if not, I really need a solution as outlined
above..
Cheers
Peter
--
Those who give up essential liberties for temporary safety deserve
neither liberty nor safety. -- Benjamin Franklin
next prev parent reply other threads:[~2002-06-24 15:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 16:55 GRUB on DoC Millennium/2000 - Instructions Mark Meade
2002-06-18 17:56 ` David Woodhouse
2002-06-18 19:03 ` Mark Meade
2002-06-20 2:56 ` Dzuy Nguyen
2002-06-24 15:01 ` Peter Keel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-24 19:08 Mark Meade
2002-06-24 15:19 Mark Meade
2002-06-24 15:40 ` Peter Keel
2002-06-24 16:40 ` Ilguiz Latypov
2002-06-24 18:50 ` Peter Keel
2002-06-20 15:01 Mark Meade
2002-06-20 16:13 ` Dzuy Nguyen
2002-06-20 17:13 ` cfowler
2002-06-18 16:43 Mark Meade
2002-06-18 18:41 ` 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=20020624150138.GA4570@discordia.ch \
--to=killer@discordia.ch \
--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