| 1 |
On Mon, 31 Oct 2005 21:31:33 +0100 |
| 2 |
Holly Bostick <motub@××××××.nl> wrote: |
| 3 |
|
| 4 |
|
| 5 |
> What else could I do alongside it, other than running an emerge or |
| 6 |
> something? |
| 7 |
> |
| 8 |
|
| 9 |
You could switch to a non-proprietary gfx driver, and try that, though it |
| 10 |
might not work with the ATI card you have. |
| 11 |
|
| 12 |
Try emerging app-benchmarks/stress and running that. That runs everything |
| 13 |
but X. And it tunable to see what's taking resources. |
| 14 |
|
| 15 |
The other thing to try is stoppping everything, with X still running and starting |
| 16 |
up one of the rss-glx screensavers. It it runs with no issue, start a second instance |
| 17 |
or a second one, then another - as many as the system will handle until it starts |
| 18 |
showing the problem. |
| 19 |
|
| 20 |
Have top running in a term to see if you can find out what taking all the resources. |
| 21 |
|
| 22 |
Last time it happened to me, it was Xorg itself causing the issue. |
| 23 |
|
| 24 |
Bob |
| 25 |
- |
| 26 |
-- |
| 27 |
gentoo-user@g.o mailing list |
Archives