[SOLVED] OpenGL screensaver (and other OpenGL apps) won't work!
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.
OpenGL screensaver (and other OpenGL apps) won't work!
I recently formatted my hard drive today and installed the latest -current (06 Aug 2013), and installed the AMD Catalyst Beta 13.8 driver. Now the Euphoria screensaver, which uses OpenGL, does not work. It used to work under KDE-4.9.5 with AMD Catalyst 13.1, and xorg-server 1.12.3. I'm wondering whether it has anything to do with the fact that the Catalyst driver is still in Beta status, or is there something that I can do to fix this situation?
I recently formatted my hard drive today and installed the latest -current (06 Aug 2013), and installed the AMD Catalyst Beta 13.8 driver. Now the Euphoria screensaver, which uses OpenGL, does not work. It used to work under KDE-4.9.5 with AMD Catalyst 13.1, and xorg-server 1.12.3. I'm wondering whether it has anything to do with the fact that the Catalyst driver is still in Beta status, or is there something that I can do to fix this situation?
Regards,
Matt
That bolded text is part of the problem.
Unfortunately, and not to be hurtful, because -Current is always in a state of flux with updates pinpointing the exact cause it hit or miss. You should be using only the latest official release if you use a proprietary driver. Otherwise, sticking to the open source driver is the only way to know what exactly the problem is.
We can try to pinpoint it, but it might not be 100% correct...
Can you post the readout of the following diagnostic utilities?
Unfortunately, and not to be hurtful, because -Current is always in a state of flux with updates pinpointing the exact cause it hit or miss. You should be using only the latest official release if you use a proprietary driver. Otherwise, sticking to the open source driver is the only way to know what exactly the problem is.
We can try to pinpoint it, but it might not be 100% correct...
Can you post the readout of the following diagnostic utilities?
glxinfo
lsmod
lspci
Thanks for the reply, ReaperX7.
I've decided, since posting this, to go back to a working configuration; i.e., kernel 3.9.10, and Catalyst 13.1. It works well with KDE 4.9.5, and I plan on staying with this config until the proprietary driver situation improves. Thanks anyway.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.