I’ve been using openSuSE 11.1 for almost two weeks and am generally impressed with how smoothly the installation went and the stability of the platform. I do have a few X server (or perhaps nvidia driver) issues that I’d like some help with.
(The most serious problem.) When an X session (running KDE4) is idle for some period of time (say about 10 minutes) its CPU utilization shoots to 100%. I disabled the screensaver to rule that out and it made no difference. If I have two X sessions running (on vt7 and vt8), the one not currently selected will go to 100% while the one I am using behaves normally. If both sessions are idle, I can see from the text-based console that both X processes have moved to 100% (it’s a dual core machine). I don’t see any telling messages in the X log files or dmsg. As soon as I switch to the inactive window, it’s X CPU utilization drops to normal (even if I don’t type anything or move the mouse) and everything works just fine after that. X is very stable (no crashes so far), but the CPU utilization when idle is hard to explain and very “expensive.”
This appears to be entirely a cosmetic problem, but KDE4 widgets or defined rectangular regions in the task bar occasionally blink between “normal” and “mostly black”. Mousing over them seems to get them to behave for a while. Nothing crashes and I cannot see any lasting effects of the problem. My wife says she’s seen entire windows do this, but I’ve never seen that (yes, my non-technical wife uses Linux… I am blessed). This happens with both the fancy KDE4 effects enabled and disabled.
DPMS doesn’t work if a screen saver is enabled (I saw someone else mention this as well). Disabling the screen saver will allow DPMS to turn off the monitor, as expected, after the time expires.
I cannot find any references to my first or second problem, so I am wondering if this is an interaction with my nvidia driver (which is up to date). Here’s the info about it:
I know my way around the server side of Linux pretty well, but have never really developed any expertise with X so I am not sure how to debug this or what other info the X experts might find useful. Let me know!
I have experienced exact same problem with x-window on SUSE 11.1 64-bit using ATI X1300 (old) video card. Also updated the video driver - no affect. After idle for approx 10 mins - starts using 100% of CPU. I do not have solution, but wanted to note have experienced same issue with different video card / system.
I’m experiencing the same issue with my HP nc6120 [intel 915GM video card].
I’m running opensuse 11.1 with KDE3 [KDE4 is not a way I want to go now]. But I still have few KDE4 packages that have been installed automatically.
The key words of the issues are: kded4, DPMS and powerdevil.
I’m experiencing the same thing on a Dell Precision M4400 with an nVidia Quadro FX 770M display adapter. The software is openSUSE 11.1 and NVidia 177.82-1.1. The backlight can be off or on, lid closed or open, and no indications of what’s going on in the logs that I can find.
I would prefer not to leave my backlight on 24-hours a day as I typically don’t shut the computer down at night.
goddamn! I had the same issue with my last install. I tried everything (including reinstall). My resolution was to change GPU. The card giving errors was a gigabyte GV-8400. I swapped it for an older 7950XT (I paid a **** load for this card originally) that fixed my out of control CPU usage. There is a chance that this is a reporting issue. It has popped up a few times already in this thread. should we BUG this??
I have this problem too
DELL XPS m1530 ,opensuse 11.1 ,NVidia 177.82
gnome with compiz enabled.
when my pc is idle and screensaver is active,
my computer consume lots of CPU .
that is when my pc is idle and screensaver is active,my pc’s cpu load is very high,after i move mouse or press any key to inactive screensaver ,cpu usage become normal.
I install kde 4.1 ,but rare use it . i realize some people said that is might because powerdevil ,so i install the newst powerdevil,but have no affect about the high cpu usage.
is this a bug,any one have workaround about it?
