On Monday February 9 2009, David C. Rankin wrote:
Randall R Schulz wrote:
...
% rpm -qa |egrep -i fglrx ati-fglrxG01-kmp-pae-8.561_2.6.27.7_9.1-1.1 x11-video-fglrxG01-8.561-1.1
(From the AMD / ATI repository for openSUSE 11.1.)
OK, still on the 8-12 driver from the repository and not from the ati-driver-package. Huh? This is a crappy answer, but I have got to hand over the reins to you on this one, you be in uncharted waters, well beyond the charted seas of my knowledge.
You shouldn't feel obligated nor should you apologize.
I could only suggest, you try the driver package from the ati site and see if the problem persists.
I tried (very clumsily) to switch to the radeon driver, and was sorry. I was picking up the pieces for quite a while. I have, frankly, never had a good experience trying to modify or reconfigure anything at the X11 server or video-card driver level, and if "once bitten, twice shy," then I'm very, very shy about this.
My understanding from the links above is that the atieventd daemon/module whatever it is, is the part of the package that responds to machine/user input events like 'lid closed' 'sleep' 'suspend' and for whatever reason the driver you have on your box is interpreting something as an event that it shouldn't even be listening to and whatever it is, the conversation 'it' and atieventd seems quite vivacious.
That might make it a culprit the other symptom I reported but about which I received no replies: At certain intervals after the machine becomes idle, the X11 server begins consuming 100%, mostly kernel mode. That condition comes and goes a few times (I don't know the pattern or timing very precisely 'cause it happens on intervals of 10s of minutes and I haven't had the patience to monitor it carefully or long enough) but eventually becomes "permanent" (instead of intermittent). As soon as I touch the mouse or keyboard, everything goes back to normal (I can watch the patterns using htop from another system logged in via ssh). Another thing I noticed is that the /etc/init.d script for atieventsd seems to have some bugs (or not be properly written), 'cause while I can see the process running, YaST's System Services (Runlevel) module reports it as stopped.
You also might want to research the 'aticonfig --set-policy=STRING' string. From the aticonfig man page it discusses:
External Events Daemon Options: Following options will not change the config file. They are used to send commands to the atieventsd external events daemon. --set-policy=STRING Sets the event policy for the daemon to be STRING. See the atieventsd(8) manpage for further details.
Maybe you can turn the listening off?
At the moment, I just did a "/etc/init.d/atieventsd stop". I'll see what consequences that has...
-- David C. Rankin
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org