![]() Registered Member ![]()
|
Hello,
I'm using debian for some months now, but I decided to move from Cinnamon to KDE yesterday. I have a Lenovo Z51-70 laptop, which has an integrated Intel HD 5500 graphics chipset and an AMD R7 M260/265 as dedicated graphic card. I first installed the Intel HD graphics driver, then the fglrx drivers. Now, I have the graphic acceleration activated (it wasn't the case before the drivers installation).
When I play a game like Frets on Fire, or when I launch benchmarking, I have a good fluidity. But for daily graphic tasks like an alt+tab, or resizing a window, the performance are very bad compared to when I didn't had installed the drivers. Sorry but I don't know what logs should I give you, I'm still a beginner \ô/ Thank you in advance. Tenryu Edit : Wut, I write "thank you in advance" but there is actually no question. So here it is : does anyone has a solution, or maybe something where I can start ? I can give you any log. |
![]() ![]()
|
Please post the output of
qdbus org.kde.KWin /KWin supportInformation (in "code" tags) Is resizing something simple as "xterm" as slow as resizing eg. firefox? |
![]() Registered Member ![]()
|
Resizing Iceweasel is a bit less smoother than resizing xterm (I guess that it's normal due to the graphics components charge). The top bar (whatever is the being resized window) randomly blinks, and the edges of the window is breaks during resizing. Let say I'm resizing from the bottom right angle, the top half of the right edge is delayed compared to the bottom half of the same edge. (Half or so).
Also, when a window appears (opposite of "fades" ?), it is like if I was on a 10Hz screen, I see the different sizes / opacities of the window before it is finally 100% open. It is not that troublesome by itself, but it's disturbing knowing that before installing the drivers, all was very fine, very smooth.
|
![]() ![]()
|
You're using xrender compositing:
> Qt Graphics System: native > Compositing is active > Compositing Type: XRender xrender acceleration in fglrx is reported to be "suboptimal", but if KWin switched to it, that may indicate GLX isn't available itfp (broken GL installation, happens because fglrx GL is incompatible with mesa GL) => paste the output of "glxinfo", if it says "error", running "sudo aticonfig --initial" and a reboot *might* fix it. If it looks like the driver is fglrx/catalyst, try to use the GL backend in "kcmshell4 kwincompositing" |
![]() Registered Member ![]()
|
Selecting OpenGL instead of XRender made things better, thank you !
An other strange thing that I didn't mention and that is still occurring : when I right click anywhere to get a contextual menu, nothing is popping up (only the "shadow" of the supposed to be menu). Then, when I use "down" arrow (or right, to get to a deeper menu), the label of the menu appears (not all at once, but each time I use the arrow, one appear). If I use the mouse, they appear all at once when the mouse is into the space delimited by the shadow. Sorry for unclear explanation, I try to print screen, but it seems that it doesn't work during a right-click.. Thank you again I don't know if it is useful anymore, but I paste the glxconfig command (isn't it weird that the 2 first lines variable are set to 0 ?)
|
![]() ![]()
|
> when I right click anywhere to get a contextual menu, nothing is popping up
Do you use some fade-in animation (ie. the fade effect or similar) - or instant animation speed? If not, does enabling/slowing it down change a thing about this? |
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]