Date: Mon, 7 May 2007 19:39:27 -0700 (PDT) From: Gore Jarold <gore_jarold@yahoo.com> To: jahnke@sonatabio.com Cc: freebsd-emulation@freebsd.org Subject: Re: vmware3 on FreeBSD 6.2 - minor (?) svga problem ... more #2 Message-ID: <935714.70175.qm@web63015.mail.re1.yahoo.com> In-Reply-To: <1178585762.938.176.camel@pinot.fmjassoc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Frank Jahnke <jahnke@sonatabio.com> wrote: > On Mon, 2007-05-07 at 17:18 -0700, Gore Jarold > wrote: > > > > > Feb 16 17:26:57: VMX|Using unified VGA. > > Feb 16 17:26:57: VMX|SVGA frame buffer address > > 0x7efc0000 > > Feb 16 17:26:57: MKS|SVGA changing width from 2364 > to > > 5760 > > Feb 16 17:26:57: MKS|SVGA changing height from > 1773 to > > 1200 > > Feb 16 17:26:57: MKS|The host frame buffer is too > big > > (27648000 > 16777216). > > Feb 16 17:26:57: VMX|Msg_Post: Error > > Feb 16 17:26:57: VMX|[msg.svga.powerOnFailed] > Failed > > to initialize SVGA device. > > Feb 16 17:26:57: > > [snip] > > > > Feb 16 17:30:41: MKS|The host frame buffer is too > big > > (27648000 > 16777216). > > > > is suspicious ... does this mean I should bump > down to > > 16 million colors in my X config ? > > This is worth a try. I did not think that how the > host was set up would > matter, but it seems that vmware creates a frame > buffer large enough to > cover the entire screen area (and depth). That > makes sense, as you are > able to make the vmware window as large as the > physical screen (at least > on the original linux version). I seem to recall > that there is a > variable in a set-up file where you can increase the > size of the buffer, > but I can't find it right now. > > Here's what mine reads for the same area: > > Apr 08 02:04:31: VMX|Using unified VGA. > Apr 08 02:04:31: VMX|SVGA frame buffer address > 0x7efc0000 > Apr 08 02:04:31: MKS|SVGA changing width from 2364 > to 2560 > Apr 08 02:04:31: MKS|SVGA changing height from 1773 > to 960 > Apr 08 02:04:31: MKS|SVGA phys sizes: 2560x960x32 > bpl 10240 offset 0 fb > 0x00960000/0x00960000 > Apr 08 02:04:31: MKS|Msg_Post: Warning > Apr 08 02:04:31: MKS|[msg.xinfo.findOriginalMode] No > DGA mode found > compatible with 2560x960, depth 24, bpp 32 > Apr 08 02:04:31: MKS|[msg.xinfo.dgaPowerOnFailed] > XFree86 direct > graphics (DGA extension) power on failed. > Apr 08 02:04:31: MKS|[msg.svgax.dgaPowerOnFailed] > Full-screen SVGA will > not be available. > > As you can tell, my screen area is smaller as far as > number of pixels > goes. > > Dropping the bit depth to see if this is the cause > is a good idea. > Heck, try monochrome to give you the largest bang > for the change. Changing my Defaultdepth lines in each of my defined screens in xorg.conf, to 16 instead of 24, solved the problem. I can now power on a VM that I create. I still get a lot of errors on the way: No DGA mode found compatible with 5760x1200, depth 16, bpp 16 XFree86 direct graphics (DGA extension) power on failed. Full-screen SVGA will not be available. and: The virtual machine will not be able to run in full-screen SVGA mode, because your X server is not an XFree86 server and does not support the XFree86 DGA extension for direct-to-frame-buffer graphics. and: and some vmnet errors, but I suspect these are easy to solve. Many thanks for all of your help! ____________________________________________________________________________________ Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?935714.70175.qm>