From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HVjrH-0002j1-Q1 for qemu-devel@nongnu.org; Mon, 26 Mar 2007 03:43:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HVjrG-0002d2-1G for qemu-devel@nongnu.org; Mon, 26 Mar 2007 03:43:15 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HVjrF-0002ce-Ty for qemu-devel@nongnu.org; Mon, 26 Mar 2007 02:43:13 -0500 Received: from wr-out-0506.google.com ([64.233.184.236]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HVjp1-0002Oy-Hc for qemu-devel@nongnu.org; Mon, 26 Mar 2007 03:40:55 -0400 Received: by wr-out-0506.google.com with SMTP id i20so1587645wra for ; Mon, 26 Mar 2007 00:40:53 -0700 (PDT) Message-ID: <46d6db660703260040r47bc25f3q9d945df9ed4bc6a9@mail.gmail.com> Date: Mon, 26 Mar 2007 09:40:52 +0200 From: "Christian MICHON" Subject: Re: [Qemu-devel] QEMU + -std-vga + XFree86 In-Reply-To: <9a158e2e0703260012y66ea83afmfca69400070844f3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9a158e2e0703251636p2209eed0u5e1b8f736343a8e6@mail.gmail.com> <46d6db660703252337u60c66342n9927165f4ca15dd8@mail.gmail.com> <9a158e2e0703260012y66ea83afmfca69400070844f3@mail.gmail.com> 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 On 3/26/07, Kyle Hubert wrote: > It does work in cirrus mode for 1024x768. I was under the impression > that it was all the cirrus driver would support. However, the std-vga > mode supports vga 799 and 798 in the console. (1600x1200:24bpp and > 1600x1200:16bpp respectively) > > The X driver seem forever confused saying there is no available video memory. > > Thanks a lot for the help. > no obvious problem in the xf86config file. when all fails, use the framebuffer :) and Xfbdev (fbdev driver instead of vesa) you might need a patch called vesafb-tng to reach such size. I haven't tried successfully though. Appending the proper parameters -append "video=vesafb:1600x1200@60", I basically reach at most 1280x1024. -- Christian