[SOLVED] DEbian jessie: AMD catalyst (fglrx) installed but slow.
DebianThis forum is for the discussion of Debian 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.
DEbian jessie: AMD catalyst (fglrx) installed but slow.
Hya,
System
Debian jessie 64bit. (as of 15/Apr/2014)
fglrx version. 1:14.3~beta1.0-1
Situation.
glxinfo says that direct rendering is Yes, however it is very slow.
dmesg says
Code:
<3>[fglrx:KAS_Mutex_Release] *ERROR* Mutex released without holding it.
bugs.debian.org says (bug=741397) that
Code:
Bug#739054: fixed in fglrx-driver 1:14.3~beta1.0-1
We believe that the bug you reported is fixed in the latest version of
fglrx-driver, which is due to be installed in the Debian FTP archive.
I guess I still have this error.
This happened after dist-upgrade. Kernel modules were rebuilt.
you may have installed the driver but I do not think you are using it. open a terminal and type lsmod | grep fglrx and see if the module is loaded.
if not try modprobe fglrx . if you compiled it your self did you run the aticonfig --initial for a single monitor.
did you try fglrxinfo
Quote:
$ glxinfo | grep "direct rendering"
If it says "direct rendering: yes" then you're good to go! If the $ glxinfo command is not found install the mesa-demos package.
remember you can test it also
Quote:
You can also use:
fgl_glxgears
as the fglrx alternative test to glxgears.
as for this
Quote:
Situation.
glxinfo says that direct rendering is Yes, however it is very slow.
Don't have this problem. Quit using the fglrx driver some time ago as the FOSS driver works very well. In fact better than the fglrx on my hardware.
+1 -- Same experience as described by Widget. I'm using the radeon driver that comes with the kernel and it works fine. What graphics card do you have? Also this link may be of interest.
jdk
I found another problem with update-initramfs, which lead me to this thread.
I removed libc-x32 (also dev package), and rebuilt kernel modules again,
aticonfig --initial (I have not done this step until today)
My penguin is in good shape now.
++++++
I am not sure which step worked.
By the way, Debian does not recommend to turn X86_x32 on for security reason. On the other hand, package manager installs libc-x32. I guess it might be somewhat preposterous.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.