LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   OpenGL screensaver (and other OpenGL apps) won't work! (http://www.linuxquestions.org/questions/slackware-14/opengl-screensaver-and-other-opengl-apps-wont-work-4175472514/)

mattallmill 08-07-2013 12:50 PM

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?

Regards,

Matt

WhiteWolf1776 08-07-2013 01:28 PM

Did you blacklist these?

blacklist radeon
blacklist radeonhd

follow these steps:
http://docs.slackware.com/howtos:har...aphics_drivers

I thought that driver would be working with 3.10 kernels fine... hmmmm

ReaperX7 08-07-2013 08:56 PM

Quote:

Originally Posted by mattallmill (Post 5005037)
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?

glxinfo
lsmod
lspci

mattallmill 08-08-2013 09:54 AM

Quote:

Originally Posted by ReaperX7 (Post 5005250)
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?

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.

Regards,

Matt


All times are GMT -5. The time now is 01:14 PM.