fredagen den 1 oktober 2010 19.47.35 skrev Bob Williams:
On Friday 01 Oct 2010 15:27:44 Ulf Sassenberg wrote:
On Thursday 30 Sep 2010 19:47:53 Will Stephenson wrote:
On Thursday 30 Sep 2010 18:25:38 Ken Schneider - openSUSE wrote:
You logged in as a new user and didn't have the problems you see in your account and you still think it's a driver issue? Think again, it has to be a errant config setting in your user login. If it were a driver issue it would affect any user that logged in.
That assumes any user's config triggers the driver problem.
That notwithstanding:
Bob, just a thought - you don't have any slideshow Frame applets displaying large images do you? I accidentally pointed 4.3's Frame at a folder of 18MP images once and the huge pixmaps sent to my weedy graphics card caused the X server to hang up for a second or two whenever the image changed. Haven't checked to see if it still occurs though.
Will
No slideshows. Big images only get opened in Digikam or Gimp, and they're not running unless needed. I have two monitors, running in twinhead mode, displaying 8 desktops with effects such as rotating desktop cube active. I've tried switching off effects, without it making any difference, but I'll try again now ...
... nope, still getting freezes, associated with activity spikes visible in gkrellm, usually in the fourth core, but sometimes others.
Bob
I doubt this is relevant in your case but I have experienced OpenGL applications freezing the computer for 5-10 seconds. This is with NVIDIA 9600 on an intel dual core equipped desk top running 11.3. However in this case I could trace the problems to the preload module. I have not experienced the same problem on my little intel equipped netbook also running 11.3 + KDE4.5. After removing preload the computer is running fine. It looks as if there is some kind of race condition so that the computer randomly starts all right, but mostly not, using preload. Ulf
Ulf,
That sounds interesting, and worth a try, given the similarities between our systems. Could you give me some guidance on how to remove the preload module, please? And how to re-enable it if it turns out not to be the culprit.
Many thanks.
Bob
Bob, I merely renamed preloadtrace.ko (search in lib/modules/...) to something else. But the proper way would of course be to change the init script. I usually compile my own kernel so this problem only surfaced while testing the opensuse kernel. Ulf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org