|
|
#1 | |
|
Registered User
Join Date: Dec 2006
Posts: 11
|
Hi
I've been testing the 190.36 and 190.40 drivers lately. They work fine as long as no compositing is used, OpenGL apps work great, too, but as soon as I enable compositing (either KWin or Compiz) the display keeps locking up all the time, that is, it freezes for some time (1-10 seconds) then works for a few seconds before it freezes again. I don't have this problem with the 185.18.31 drivers. Any idea what could cause this? Thanks in advance. |
|
|
|
|
|
|
#2 | |
|
Registered User
Join Date: Nov 2007
Posts: 70
|
Option "UseEvents" "true"
This is your problem. UseEvents is broken with the 190 drivers. Set this to false in your xorg.conf. |
|
|
|
|
|
|
#3 |
|
Registered User
Join Date: Dec 2006
Posts: 11
|
Thanks, that solved the problem for now (well, actually it really just hides the actual problem but I can live with that).
|
|
|
|
|
|
#4 | |
|
Registered User
Join Date: Mar 2009
Posts: 36
|
i got the same problem with kwin + compositing effects and any opengl related applications, especially wine games, x freezes occasionally for 1-5 seconds. thanks for the info about the "UseEvents" option, i was reading the readme and it says:
Enables the use of system events in some cases when the X driver is waiting for the hardware. The X driver can briefly spin through a tight loop when waiting for the hardware. With this option the X driver instead sets an event handler and waits for the hardware through the poll() system call. does it cause any disadvantages i should be aware of ? thanks in advance and best regards |
|
|
|
|
|
|
#5 |
|
Registered User
Join Date: Dec 2006
Posts: 11
|
You might notice a slightly higher CPU load in some situations due to the busy waiting. Other than that there probably shouldn't be any disadvantages.
|
|
|
|
![]() |
| Thread Tools | |
|
|