Andrei GUDIU wrote:
Try to enable EXA and play with Option MigrationHeuristic greedy
I can confirm this solved my X problem. And it was really really a slow X.
I added
Option AccelMethod EXA
Option MigrationHeuristic greedy
in Section Device.
This also fixes issues
Try to enable EXA and play with Option MigrationHeuristic greedy
I can confirm this solved my X problem. And it was really really a slow X.
I added
Option AccelMethod EXA
Option MigrationHeuristic greedy
in Section Device.
I can confirm the problem, but it was not an X problem only...everything was
slow.
The problem was that my interrupts were up to 82.9%. Disabled acpiprt and
acpimadt in the kernel and it all works ok.
On Wed, May 6, 2009 at 11:35 AM, Andrei GUDIU andr...@openbsd-box.orgwrote:
Try to enable EXA
Gregory Edigarov wrote:
Hello,
Does anybody else notice strange X performance degradation?
It takes forever for X to start, and after it start it takes forever for
them to bring up firefox... and after all it is really slw
Well I turned off the acpi completely, that seems to solve
Tobias Ulmer wrote:
Try to enable EXA and play with Option MigrationHeuristic greedy
Thanks, I will try that later today.
--
With best regards,
Gregory Edigarov
Hello,
Does anybody else notice strange X performance degradation?
It takes forever for X to start, and after it start it takes forever for
them to bring up firefox... and after all it is really slw
--
With best regards,
Gregory Edigarov
(--) checkDevMem: using aperture
Check top(1) without a runing X first. You might have problems with
interrupts. If that's the case, top should show prettu high interrupt %'s.
Espcially some nvidia chipsets have these problems.
If you are suffering from high interrupt load, try disabling acpirt(4)
or if that does not work,
It's not an interrupt load.
top seems normal, even running X, 0.0 - 0.9 % interrupt.
but everything is very slow.
Otto Moerbeek wrote:
Check top(1) without a runing X first. You might have problems with
interrupts. If that's the case, top should show prettu high interrupt %'s.
Espcially some
hmm, on Mon, May 04, 2009 at 12:24:20PM +0200, Otto Moerbeek said that
Check top(1) without a runing X first. You might have problems with
interrupts. If that's the case, top should show prettu high interrupt %'s.
Espcially some nvidia chipsets have these problems.
If you are suffering from
9 matches
Mail list logo