From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HVkfd-0004Dq-00 for qemu-devel@nongnu.org; Mon, 26 Mar 2007 04:35:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HVkfb-0004B1-F8 for qemu-devel@nongnu.org; Mon, 26 Mar 2007 04:35:16 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HVkfb-0004Ay-9b for qemu-devel@nongnu.org; Mon, 26 Mar 2007 03:35:15 -0500 Received: from wx-out-0506.google.com ([66.249.82.227]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HVkdM-0000Wo-5m for qemu-devel@nongnu.org; Mon, 26 Mar 2007 04:32:56 -0400 Received: by wx-out-0506.google.com with SMTP id i30so3045016wxd for ; Mon, 26 Mar 2007 01:32:49 -0700 (PDT) Message-ID: <9a158e2e0703260132u673c6048oa33ae0b0cbd71a5@mail.gmail.com> Date: Mon, 26 Mar 2007 01:32:49 -0700 From: "Kyle Hubert" Subject: Re: [Qemu-devel] QEMU + -std-vga + XFree86 In-Reply-To: <46d6db660703260040r47bc25f3q9d945df9ed4bc6a9@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> <46d6db660703260040r47bc25f3q9d945df9ed4bc6a9@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 > no obvious problem in the xf86config file. > when all fails, use the framebuffer :) and Xfbdev (fbdev driver instead > of vesa) The framebuffer seems to miss every other vertical scan line. I'm not sure if I make sense, but the video wraps around the screen onto itself vertically. Thus rendering half of it on top (with vertical black lines every other pixel) > 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. I tried using the newer video appendage and it didn't seem to work. I had to use the older vga=. I believe you are talking about the kernel boot param, yes? How about this for more information. The XFree86 VBE extension does the following code: pInt->ax = 0x4F00; pInt->es = SEG_ADDR(RealOff); pInt->di = SEG_OFF(RealOff); pInt->num = 0x10; xf86ExecX86int10(pInt); Resulting in: TotalMem = B_O16(vbe->TotalMem); /* Some BIOS'es are off by one */ TotalMem += TotalMem & 1U; xf86DrvMsgVerb(screen, X_INFO, 3, "VESA VBE Total Mem: %li kB\n", TotalMem * 64); Which is annoying it ignores the X config's manual VideoRam in the device section. Perhaps the vgabios doesn't correctly implement this interrupt? Looking in the 0.6a release of vgabios, you see in vbe.c: // VBE Total Memory (in 64b blocks) vbe_info_block.TotalMemory = VBE_TOTAL_VIDEO_MEMORY_DIV_64K; So, it's intended to return correctly. Yet the XFree86 driver reports a zero return. Perhaps the vgabios.bin coming with QEMU is incorrect? I don't see anything in vgabios.diff which suggests this code was changed. -Kyle