Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 12 Dec 2015 13:39:04 -0500
From:      Michael Powell <nightrecon@hotmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: problems running OpenGL code
Message-ID:  <n4hpld$ueg$1@ger.gmane.org>
References:  <566C3DAD.8090809@hiwaay.net> <20151212173509.fba928df.freebsd@edvax.de> <566C51CB.8040604@hiwaay.net> <566C536F.8080507@hiwaay.net> <n4hla4$hkm$3@ger.gmane.org> <566C5C67.9070704@hiwaay.net> <n4hn2p$jpe$1@ger.gmane.org> <566C6201.4070208@hiwaay.net>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
William A. Mahaffey III wrote:

[snip]
>>
>> VESA mode(s) will never give you any support for GL and there won't be
>> any way (to my limited knowledge) to run code that depends on GL
>> libraries.
> 
> 
> *Rats* !!!! I had an old Linux box where VESA did provide (gruesomely
> slow) OpenGL software rendering, but that was eons ago. All of my
> desktop (XFCE 4.12) works AOK, ditto for browser, etc., although many of
> the screensavers crash w/ messages about .... GLX extension not enabled
> :-/ .... Oh well ....
> 

I've never been completely certain of this, and hopefully someone who does 
know can chime in (stuff I'd like to know more about as well), but I have 
been under the impression it is the MESA stack which is tapped to do 
software rendering via CPU as a fallback for when 3D hardware acceleration 
is unavailable. Of course, software(s) need to be built with the facility to 
utilize these code pathways...

But back to the original problem of code testing. If that is the primary 
problem one suggestion may be to disable (in BIOS) the Kabini GPU and 
scrounge up some other older AMD/ATI card from the 'supported' section list 
on the ~/Graphics FreeBSD wiki page. Return to the work at hand and consider 
dealing with the Jaguar situation as support evolves.

-MIke






Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?n4hpld$ueg$1>