From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HVdJJ-0007Pe-GU for qemu-devel@nongnu.org; Sun, 25 Mar 2007 20:43:45 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HVdJH-0007Id-NG for qemu-devel@nongnu.org; Sun, 25 Mar 2007 20:43:44 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HVdJH-0007I2-Be for qemu-devel@nongnu.org; Sun, 25 Mar 2007 19:43:43 -0500 Received: from wx-out-0506.google.com ([66.249.82.224]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HVdH5-0001Gx-DA for qemu-devel@nongnu.org; Sun, 25 Mar 2007 20:41:27 -0400 Received: by wx-out-0506.google.com with SMTP id i30so2930059wxd for ; Sun, 25 Mar 2007 17:41:27 -0700 (PDT) Message-ID: <460716B3.4060803@codemonkey.ws> Date: Sun, 25 Mar 2007 19:41:23 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] QEMU + -std-vga + XFree86 References: <9a158e2e0703251636p2209eed0u5e1b8f736343a8e6@mail.gmail.com> In-Reply-To: <9a158e2e0703251636p2209eed0u5e1b8f736343a8e6@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Kyle Hubert wrote: > 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. You probably have to increase your hsync and vrefresh ranges. Regards, Anthony Liguori > 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 > > >