From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: grub2 x64 uefi 2.x boot failure
Date: Sat, 22 Jan 2011 12:18:07 +0100 [thread overview]
Message-ID: <4D3ABCEF.6060206@gmail.com> (raw)
In-Reply-To: <AANLkTi=cpQzXZ80ii4fjBCXRzd1mBOiE=5=bKyD9b7jw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
On 01/22/2011 08:07 AM, KESHAV P.R. wrote:
> Hi phcoder,
> This mail is regarding the grub2 efi tarball I sent
> you about missing reloc and other info while comparing elilo and
> grub2. Can you please test the tianocore duet UEFI 2.3 x86_64 build
> floppy image from
> https://github.com/skodabenz/Tianocore_DUET_memdisk_compiled/zipball/master
>
This image is completely unfunctional. It doesn't offer any menu with
bootable images, file manager hangs and there is no shell.
So please
a) Do the debugging I asked you to.
b) If you send the images first test them yourself.
> (qemu ovmf build fails for now) with grub2 efi 1.99~rc1. I also have a
> similar bug which an Archlinux x86_64 user reported with Asus P8P67-m
> PRO motherboard running AMI Aptio x86_64 UEFI firmware (
> https://bbs.archlinux.org/viewtopic.php?pid=881606#p881606 ). Thanks
> in advance.
>
> Regards.
>
> Keshav
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2011-01-22 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 7:07 grub2 x64 uefi 2.x boot failure KESHAV P.R.
2011-01-22 10:47 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-01-22 11:18 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=4D3ABCEF.6060206@gmail.com \
--to=phcoder@gmail.com \
--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.