From: "Mahlon E. Smith" <mahlon@martini.nu>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: grub2, pxe, and default boot
Date: Wed, 19 May 2010 13:47:55 -0700 [thread overview]
Message-ID: <20100519204755.GE7759@martini.nu> (raw)
In-Reply-To: <20100518174546.GC7759@martini.nu>
On Tue, May 18, 2010, Vladimir '??-coder/phcoder' Serbinenko wrote:
> Mahlon E. Smith wrote:
> > sh:grub> ls -lh
> > Device hd0: Filesystem type pxefs <---- uh oh
> >
>
> Upgrade
Bumped up to 1.98. Closer, but still not quite working.
grub> ls
(pxe)
grub> insmod ext2
grub> insmod biosdisk
grub> ls -lh
Device hd0: Partition table
Device fd0: Unknown filesystem
Device pxe: Filesystem type pxefs
grub> ls (hd0,1)/
error: no such partition.
grub> chainloader (hd0,1)+1
error: no such partition.
I'm pretty sure I've got the right partition numbering. (This is a
VirtualBox tester.)
# fdisk -l
Disk /dev/hda: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 16 128488+ 83 Linux
/dev/hda2 17 3916 31326750 8e Linux LVM
Are my expectations correct with what I'm trying to do here? Are there
other modules I should be loading via insmod first?
I can't find any info out there on this specific PXE stuff with grub2.
I humbly offer writing up some wiki content in trade for getting this
working. :)
--
Mahlon E. Smith
http://www.martini.nu/contact.html
next prev parent reply other threads:[~2010-05-19 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 16:13 grub2, pxe, and default boot Mahlon E. Smith
2010-05-18 16:34 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-18 17:45 ` Mahlon E. Smith
2010-05-19 20:47 ` Mahlon E. Smith [this message]
2010-05-19 20:55 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20100519204755.GE7759@martini.nu \
--to=mahlon@martini.nu \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.