Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12311 - xf86-video-openchrome unusable with VIA vn896 Chrome 9 HC
Attached to Project:
Arch Linux
Opened by gabriele lanaro (gabriele.lanaro) - Monday, 01 December 2008, 23:24 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 27 December 2008, 14:06 GMT
Opened by gabriele lanaro (gabriele.lanaro) - Monday, 01 December 2008, 23:24 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 27 December 2008, 14:06 GMT
|
DetailsDescription:
screen freeze when starting X and moving mouse, don-t quit pressing Ctrl-alt-backspace Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: Set video driver "openchrome" in xorg.conf startx |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Saturday, 27 December 2008, 14:06 GMT
Reason for closing: None
Additional comments about closing: solution found in the first comment
Saturday, 27 December 2008, 14:06 GMT
Reason for closing: None
Additional comments about closing: solution found in the first comment
xorg.conf.openchrome
In short, try:
Section "Device"
...
Driver "openchrome"
Option "XaaNoImageWriteRect"
EndSection
or
Section "Device"
...
Driver "openchrome"
Option "NoAccel" "true"
EndSection
or
Section "Device"
...
Driver "openchrome"
Option "AccelMethod" "EXA"
Option "ExaNoComposite" "True"
Option "MigrationHeuristic" "greedy"
Option "ExaScratchSize" "8192"
Option "MaxDRIMem" "16384"
EndSection
No time to test it today, I will try it tomorrow.
thank you very much for the solution, I think that the bug can be closed.
For the record, this is openchrome bug #263 (http://www.openchrome.org/trac/ticket/263)