From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HVcI9-0004tO-Ox
	for qemu-devel@nongnu.org; Sun, 25 Mar 2007 19:38:29 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HVcI7-0004tC-Dv
	for qemu-devel@nongnu.org; Sun, 25 Mar 2007 19:38:28 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HVcI7-0004t7-8k
	for qemu-devel@nongnu.org; Sun, 25 Mar 2007 18:38:27 -0500
Received: from wx-out-0506.google.com ([66.249.82.238])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <khubert@gmail.com>) id 1HVcFv-0001yM-Lu
	for qemu-devel@nongnu.org; Sun, 25 Mar 2007 19:36:11 -0400
Received: by wx-out-0506.google.com with SMTP id i30so2914431wxd
	for <qemu-devel@nongnu.org>; Sun, 25 Mar 2007 16:36:10 -0700 (PDT)
Message-ID: <9a158e2e0703251636p2209eed0u5e1b8f736343a8e6@mail.gmail.com>
Date: Sun, 25 Mar 2007 16:36:10 -0700
From: "Kyle Hubert" <khubert@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: [Qemu-devel] QEMU + -std-vga + XFree86
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Hi, I'm working with QEMU on an XFree86 machine. I was desirous of
having 1600x1200 working in the virtual machine, so I looked at using
the -std-vga option with the "vesa" X driver.

While initializing X, I get the following:

(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 0.0
(II) VESA(0): VESA VBE Total Mem: 0 kB
(II) VESA(0): VESA VBE OEM: ^A

The log continues on to say:

(II) VESA(0): Total Memory: 0 64KB banks (0kB)
(II) VESA(0): Generic Monitor: Using hsync range of 28.00-51.00 kHz
(II) VESA(0): Generic Monitor: Using vrefresh range of 43.00-60.00 Hz
(II) VESA(0): Not using mode "1600x1200" (no mode of this name)
(II) VESA(0): Not using mode "1280x1024" (no mode of this name)
(II) VESA(0): Not using mode "1024x768" (no mode of this name)
(II) VESA(0): Not using mode "800x600" (no mode of this name)
(II) VESA(0): Not using built-in mode "640x480" (insufficient memory
given virtual size)

I'm not positive this is my problem, but it looks like it isn't
reporting the vram size correctly, does this sound correct?

Thanks for the time.

-Kyle