From: "Egan Ford" <egan@sense.net>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] efibootmgr error
Date: Sat, 19 Jan 2002 06:44:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805885@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805880@msgid-missing>
Matt, thank you for the rapid response. It does work.
> -----Original Message-----
> From: linux-ia64-admin@linuxia64.org
> [mailto:linux-ia64-admin@linuxia64.org]On Behalf Of Matt_Domsch@Dell.com
> Sent: Friday, January 18, 2002 12:05 PM
> To: egan@sense.net; linux-ia64@linuxia64.org
> Subject: RE: [Linux-ia64] efibootmgr error
>
>
> > One of my cluster nodes gets this error when running efibootmgr:
> >
> > write_variable():open(/proc/efi/vars/Efi-47c7b226-c42a-11d2-8e
> > 57-00a0c969723
> > b): No such file or directory
>
> It means that the specific file doesn't exist. What BIOS/Firmware are you
> using? Is it EFI 1.1-based?
>
> There's a new copy of efibootmgr 0.4.0-test4 that I posted to linux-ia64 a
> couple weeks ago that fixes this. Rather than assume a fixed variable
> exists, it uses the first variable it can to do the writing.
>
> Please download and try
> http://domsch.com/linux/ia64/efibootmgr/efibootmgr-0.4.0-test4.tar.gz.
>
> Thanks,
> Matt
>
> --
> Matt Domsch
> Sr. Software Engineer
> Dell Linux Solutions www.dell.com/linux
> #1 US Linux Server provider with 24.5% (IDC Dec 2001)
> #2 Worldwide Linux Server provider with 18.2% (IDC Dec 2001)
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
prev parent reply other threads:[~2002-01-19 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 18:33 [Linux-ia64] efibootmgr error Egan Ford
2002-01-18 19:05 ` Matt_Domsch
2002-01-19 6:44 ` Egan Ford [this message]
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-105590698805885@msgid-missing \
--to=egan@sense.net \
--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 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.