From: Matt_Domsch@Dell.com
To: linux-ia64@vger.kernel.org
Subject: efibootmgr 0.4.2-test1
Date: Thu, 31 Jul 2003 19:02:05 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105967815211635@msgid-missing> (raw)
Announcing efibootmgr 0.4.2-test1. If you have systems you can test
this on, please do so. It appears to work fine on my BigSur.
* Thu Jul 31 2003 Matt Domsch <Matt_Domsch@dell.com>
- Applied patch from Dann Frazier to enable creating netboot entries.
- update AUTHORS with Dann's netboot contribution.
- Until we can get the ACPI HID and UID programatically, make the user
pass them in when creating a netboot entry.
- Add O_DIRECT support for reading the disk.
- Fix unparse_hardware_path() for the PCI case - the device and function
values were printed in reverse order.
- Fix the README file to reflect all the options that can be passed, and
add a new item for netboot entries.
- whitespace cleanups
If there are no problems with this, I'd like to also fix up the
unaligned access messages that the kernel prints when this creates new
boot entries, but I wanted to clear the plate of this stuff first.
The netboot entries are kind of interesting. Dann added the -i
<interface> option, but we don't know a programatic way to get ahold of
the ACPI HID and UID information for the device path, so we make the
user pass it in. That can be removed if we find an automated method for
determining it. The README gives examples of what to use:
6) A system administrator wants to create a boot option to network
boot (PXE). Unfortunately, this requires knowing a little more
information about your system than can be easily found by
efibootmgr, so you've got to pass additional information - the ACPI
HID and UID values. These can generally be found by using the EFI
Boot Manager (in the EFI environment) to create a network boot
entry, then using efibootmgr to print it verbosely. Here's one example:
Boot003* Acpi(PNP0A03,0)/PCI(5|0)/Mac(00D0B7F9F510) \
ACPI(a0341d0,0)PCI(0,5)MAC(00d0b7f9f510,0)
In this case, the ACPI HID is "0A0341d0" and the UID is "0".
For the zx2000 gigE, the HID is "222F" and the UID is "500".
For the rx2000 gigE, the HID is "0002" and the UID is "100".
You create the boot entry with:
'efibootmgr -c -i eth0 -H 222F -U 500 -L netboot'
For kernels that support O_DIRECT (2.5.x), this should allow us to read
the last sector of an odd-sized disk. If you can test this, please
report success or failure.
Tarballs at:
http://domsch.com/linux/ia64/efibootmgr/efibootmgr-0.4.2-test1.tar.gz
http://domsch.com/linux/ia64/efibootmgr/efibootmgr-0.4.2-test1.tar.gz.asc
Feedback welcome!
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next reply other threads:[~2003-07-31 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 19:02 Matt_Domsch [this message]
2003-08-01 1:54 ` efibootmgr 0.4.2-test1 Martin Pool
2003-08-01 2:09 ` Matt_Domsch
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=marc-linux-ia64-105967815211635@msgid-missing \
--to=matt_domsch@dell.com \
--cc=linux-ia64@vger.kernel.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