From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33098)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bernhard@bwalle.de>) id 1WimNi-00087A-1m
	for qemu-devel@nongnu.org; Fri, 09 May 2014 11:06:45 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bernhard@bwalle.de>) id 1WimNZ-0005l1-KE
	for qemu-devel@nongnu.org; Fri, 09 May 2014 11:06:37 -0400
Received: from smtprelay02.ispgateway.de ([80.67.31.25]:49502)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bernhard@bwalle.de>) id 1WimNZ-0005kS-DN
	for qemu-devel@nongnu.org; Fri, 09 May 2014 11:06:29 -0400
Date: Fri, 9 May 2014 17:06:21 +0200
From: Bernhard Walle <bernhard@bwalle.de>
Message-ID: <20140509150621.GA9474@euler.fritz.box>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Qemu-devel] uvesafb doesn't work with seabios
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: kraxel@redhat.com

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