All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: BALATON Zoltan <balaton@eik.bme.hu>, Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel@lists.sourceforge.net,
	Gerd Hoffmann <kraxel@redhat.com>,
	qemu devel list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [edk2] syslinux vs. OVMF
Date: Tue, 26 May 2015 23:27:32 +0300	[thread overview]
Message-ID: <5564D734.3000703@msgid.tls.msk.ru> (raw)
In-Reply-To: <alpine.GSO.2.01.1505262204350.1051@mono>

26.05.2015 23:17, BALATON Zoltan wrote:
> On Tue, 26 May 2015, Laszlo Ersek wrote:
>> On 05/26/15 19:04, Michael Tokarev wrote:
>>> No, I mean I see the same error message "Failed to read blocks: 0xC"
>>> after syslinux.efi load.  The banner is new, with a few changed details.
>>
>> Interesting -- no clue where "Failed to read blocks" comes from. Not
>> syslinux, not iPXE, not shim, not grub, not edk2, not the kernel...
> 
> I think it comes from syslinux/efi/diskio.c:41....

Indeed. Thank you very much for finding this.

FWIW, 0xC means RETURN_NO_MEDIA.  Which is kind of strange.
But it is the first load which is done by syslinux.efi, not
by ipxe rom.

Thanks,

/mjt

  reply	other threads:[~2015-05-26 20:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.GSO.2.01.1504062122470.1832@mono>
     [not found] ` <5523E12E.8010103@redhat.com>
     [not found]   ` <1428653687.11559.5.camel@nilsson.home.kraxel.org>
2015-04-10 10:06     ` [Qemu-devel] [edk2] syslinux vs. OVMF Laszlo Ersek
2015-04-10 11:04       ` [Qemu-devel] virtio-net regression [was: syslinux vs. OVMF] Laszlo Ersek
2015-04-10 14:36         ` Laszlo Ersek
2015-04-10 19:56           ` Laszlo Ersek
2015-05-26 14:36       ` [Qemu-devel] [edk2] syslinux vs. OVMF Michael Tokarev
2015-05-26 16:49         ` Laszlo Ersek
2015-05-26 17:04           ` Michael Tokarev
2015-05-26 18:38             ` Laszlo Ersek
2015-05-26 20:17               ` BALATON Zoltan
2015-05-26 20:27                 ` Michael Tokarev [this message]
2015-05-26 20:42                   ` BALATON Zoltan
2015-05-26 21:31             ` Michael Tokarev

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=5564D734.3000703@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=balaton@eik.bme.hu \
    --cc=edk2-devel@lists.sourceforge.net \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=qemu-devel@nongnu.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.