openSUSE 11.1 Dell optiplex PIV GX260 (tested on 3 different gx260's with 1Mb framebuffer and 8Mb framebuffer chosen from bios) X only works with: Option "NoAccel" in /etc/xorg.conf Driver section. Without this line X crashes the computer needing a power down to reboot. This slows the screen down so as to be unacceptable. is there a workaround to get rid of having to use Comes from https://bugzilla.novell.com/show_bug.cgi?id=445320
Created attachment 21497 [details] Console output from the X server when crashing
(In reply to comment #1) > Created an attachment (id=21497) [details] > Console output from the X server when crashing > Confirming this for my case. I have a Hermes Barebone 845GL, and since updating to OpenSUSE 11.1, the X server crashes without "NoAccel". Setting "ExaNoComposite" as suggested elsewhere does not help. I did not experience any problems up to OpenSUSE 10.2. lspci reveals: 00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 01) 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01) Using an external terminal I could capture the log output as submitted above. Michael
(In reply to comment #2) > Confirming this for my case. I have a Hermes Barebone 845GL, and since updating > to OpenSUSE 11.1, the X server crashes without "NoAccel". Setting > "ExaNoComposite" as suggested elsewhere does not help. I did not experience any > problems up to OpenSUSE 10.2. Setting "AccelMethod" to "XAA" resolved the problem for me. Michael
fixed summary, as the crash is just a side effect of the GPU hanging. If you can reproduce it with UXA on kernel 2.6.30 or newer, and attach intel_gpu_dump output, that may help, though we haven't been doing much about 8xx bugs.
Please test with my patches on bug #23082.
Feedback timout, and we've fixed a bunch of 8xx bugs since reported. Please re-open if the problem still exists with the current code.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.