SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As I understand it mesa now includes a native implementation of direct3d9. So does wine take advantage of this by default, or do we still need the wine-staging patches? How can I tell if direct3d is enabled/in use?
It may work with newer versions, too. But since I switched to an Intel GPU I can't test it anymore.
It only works with AMD and NVidia cards (Intel with the ilo driver, but it's still very buggy). If you run an application from the terminal, it will tell you if it's activated or not.
LIBGL_DEBUG=verbose glxinfo | grep DRI shows that DRI3 is activated, yet I still can't get it running in wine:
Code:
err:d3dadapter:dri3_create_adapter9 Unable to create ID3DAdapter9 (fd=159)
err:d3d9:d3dadapter9_new No available native adapters in system.
What am I missing?
Shouldn't
Code:
Driver "Intel"
actually be
Code:
Driver "intel"
?
Often you might be able to get away with the xorg.conf.d files but when you're trying to find out why something is or isn't working a full xorg.conf might be useful.
Run xorgsetup and it should autogenerate a full xorg.conf in /etc/X11 that can be edited as needed with a full setup to tinker with for debugging.
Also have you rebuilt wine with the wine-nine add-on?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.