From: Bernhard Walle <bernhard@bwalle.de>
To: qemu-devel@nongnu.org
Cc: kraxel@redhat.com
Subject: [Qemu-devel] uvesafb doesn't work with seabios
Date: Fri, 9 May 2014 17:06:21 +0200 [thread overview]
Message-ID: <20140509150621.GA9474@euler.fritz.box> (raw)
Hello,
I'm using QEmu 2.0.0 on a Linux host (x86-64) with a quite special
target system that uses uvesafb ('video=uvesafb:1024x768-32'). I get
following errors in the target system:
uvesafb: Getting mode info block for mode 0x2 failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0x3 failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0x4 failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0x5 failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0x6 failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0x7 failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0xd failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0xe failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0xf failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0x10 failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0x11 failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0x12 failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0x13 failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block for mode 0x6a failed (eax=0x4f01, err=1)
uvesafb: vbe_init() failed with -22
uvesafb: probe of uvesafb.0 failed with error -22
With QEmu 1.6, it worked. I bisected that down to following commit:
commit 6eefccc0bb9c34051b1e21880fc3a1c1c8686edd
Author: Gerd Hoffmann <kraxel@redhat.com>
Date: Mon Dec 2 13:01:20 2013 +0100
roms: update vgabios binaries
And indeed, when I switch 'vgabios-stdvga.bin' to the old variant, it works.
What can I do to track down the problem? I tried to build the svga bios
inside the QEMU tree, but I didn't succeed. Building it in the current
seabios git tree worked, but I got a different error...
Regards,
Bernhard
next reply other threads:[~2014-05-09 15:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 15:06 Bernhard Walle [this message]
2014-05-10 15:07 ` [Qemu-devel] uvesafb doesn't work with seabios Kevin O'Connor
2014-05-11 11:42 ` Bernhard Walle
2014-05-11 12:37 ` Kevin O'Connor
2014-05-11 14:19 ` Bernhard Walle
2014-05-12 5:29 ` Kevin O'Connor
2014-05-12 18:53 ` Bernhard Walle
2014-05-12 20:07 ` Kevin O'Connor
2014-05-13 5:52 ` Bernhard Walle
2014-05-13 9:20 ` Bernhard Walle
2014-05-13 15:41 ` Kevin O'Connor
2014-05-13 18:08 ` Gerhard Wiesinger
2014-05-13 18:20 ` Kevin O'Connor
2014-05-13 19:48 ` Bernhard Walle
2014-05-14 19:08 ` Bernhard Walle
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=20140509150621.GA9474@euler.fritz.box \
--to=bernhard@bwalle.de \
--cc=kraxel@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.