From: Kevin O'Connor <kevin@koconnor.net>
To: Bernhard Walle <bernhard@bwalle.de>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] uvesafb doesn't work with seabios
Date: Mon, 12 May 2014 01:29:18 -0400 [thread overview]
Message-ID: <20140512052918.GA2100@morn.localdomain> (raw)
In-Reply-To: <705f2182cbc05c35147afbe7c06c62a6@bwalle.de>
On Sun, May 11, 2014 at 04:19:55PM +0200, Bernhard Walle wrote:
> Am 2014-05-11 14:37, schrieb Kevin O'Connor:
> >On Sun, May 11, 2014 at 01:42:57PM +0200, Bernhard Walle wrote:
> >>Am 10.05.14 17:07, schrieb Kevin O'Connor:
> >>> Also, it looks like uvesafb can call x86emu. Older versions of x86emu
> >>> are known to not emulate some instructions properly, and it has caused
> >>> problems for SeaVGABIOS. The most recent version of SeaVGABIOS from
> >>> SeaBIOS git has additional checks for this - can you grab the seabios
> >>> git, set CONFIG_DEBUG_LEVEL to 8, build SeaVGABIOS (set
> >>> CONFIG_VGA_BOCHS), and post the logs from both Linux and QEMU with the
> >>> above options?
> >>
> >>It doesn't change the result (that it doesn't work). It only makes the
> >>kernel failing much faster and of course there's much more debugging
> >>output: http://bwalle.de/tmp/debugoutput (250k).
> >
> >Were there any Linux or userspace messages with the above?
>
>
> Yes:
>
> uvesafb: Getting VBE info block failed (eax=0x1d2, err=0)
> uvesafb: vbe_init() failed with -22
> uvesafb: probe of uvesafb.0 failed with error -22
It does look like the x86emu issue. You can try applying the
SeaVGABIOS patch below to confirm it.
-Kevin
--- a/vgasrc/vgaentry.S
+++ b/vgasrc/vgaentry.S
@@ -47,7 +47,14 @@ _rom_header_signature:
// Force a fault if found to be running on broken x86emu versions.
DECLFUNC x86emu_fault
+msg: .ascii "SeaVGABIOS: x86emu leal trap!\n"
x86emu_fault:
+#if CONFIG_DEBUG_IO
+ movw %cs:DebugOutputPort, %dx
+ movl $30, %ecx
+ movl $msg, %esi
+ rep outsb %cs:(%esi), (%dx)
+#endif
1: hlt
jmp 1b
next prev parent reply other threads:[~2014-05-12 5:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 15:06 [Qemu-devel] uvesafb doesn't work with seabios Bernhard Walle
2014-05-10 15:07 ` 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 [this message]
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=20140512052918.GA2100@morn.localdomain \
--to=kevin@koconnor.net \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).