3D drivers matrix - the evolution
Did you game well? If no, is it because you had 3D driver issues and couldn’t make head nor tail out of this mess? Here, I discuss the most recent driver releases on the most demanding 3D application there is today on the GNU/Linux desktop.
You guessed it, 3D desktops! Since this article is getting a bit old, it’s time for an update.
3D drivers matrix—the evolution
Yup, the matrix is back—the driver matrix, that is. Following several comments and some further experiments on my part, I am glad to bring you an updated driver table.
Before that however, the news!
ATI
ATI/AMD is churning out updated drivers monthly. They are more stable, faster, cater to more recent revisions of Xorg—but they still won’t support AIGLX nor do they provide hardware-accelerated GL_EXT_texture_from_pixmap. They also cut support to r100/r200 cards. Too bad.
- Login or register to post comments
- Printer-friendly version
- 2230 reads
- PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is releasedAfter three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release. |
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future TechThe metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world. Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility. |
today's howtos
|
aaaah-ha!
NVIDIA: Those chips still suffer from an annoying bug, however: when you fill up the frame buffer, all subsequent windows (or dialogues) will appear black. The only way to solve that is to either increase the frame buffer size (possible with integrated 6150, for example) or reduce frame buffer use (close some windows, minimize then restore the black window, disable some plugins).
Please note that you pretty much HAVE to add those options to xorg.conf:
Option "AddARGBGLXVisuals" "true"
Option "TripleBuffer" "true"
Otherwise, you may not get working window borders.
Now we know.