2008-03-28 17:38:08 |
csemichon |
bug |
|
|
added bug |
2008-03-28 17:38:08 |
csemichon |
bug |
|
|
added attachment 'Capture-Pilotes de périphériques.png' (Capture-Pilotes de périphériques.png) |
2008-03-28 17:38:08 |
csemichon |
bug |
|
|
added attachment 'CoreDump.gz' (CoreDump.gz) |
2008-03-28 17:38:08 |
csemichon |
bug |
|
|
added attachment 'Dependencies.txt' (Dependencies.txt) |
2008-03-28 17:38:08 |
csemichon |
bug |
|
|
added attachment 'ProcMaps.txt' (ProcMaps.txt) |
2008-03-28 17:38:08 |
csemichon |
bug |
|
|
added attachment 'ProcStatus.txt' (ProcStatus.txt) |
2008-03-28 17:38:08 |
csemichon |
bug |
|
|
added attachment 'Registers.txt' (Registers.txt) |
2008-03-28 17:38:08 |
csemichon |
bug |
|
|
added attachment 'Stacktrace.txt' (Stacktrace.txt) |
2008-03-28 17:38:08 |
csemichon |
bug |
|
|
added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt) |
2008-03-28 17:49:15 |
Apport retracing service |
bug |
|
|
added subscriber Crash bug triagers for universe packages |
2008-03-28 17:49:22 |
Apport retracing service |
bug |
|
|
added attachment 'Stacktrace.txt' (Stacktrace.txt (retraced)) |
2008-03-28 17:49:27 |
Apport retracing service |
bug |
|
|
added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt (retraced)) |
2008-04-02 17:23:55 |
Bryce Harrington |
linux-restricted-modules-2.6.24: status |
New |
Incomplete |
|
2008-04-02 19:35:08 |
csemichon |
bug |
|
|
added attachment 'Xorg.0.log' (Xorg.0.log) |
2008-04-02 21:30:18 |
Bryce Harrington |
title |
fgl_glxgears crashed with SIGSEGV |
[fglrx] fgl_glxgears crashed with SIGSEGV |
|
2008-04-04 19:55:07 |
csemichon |
bug |
|
|
added attachment 'Xorg.0.log' (After disabling AIGLX) |
2008-04-05 12:35:27 |
csemichon |
bug |
|
|
added attachment 'Xorg.0.log' (/var/log/Xorg.0.log after 2.6.24-15 update) |
2008-04-05 17:04:40 |
csemichon |
bug |
|
|
added attachment 'Xorg.0.log' (/var/log/Xorg.0.log Instalation of ATI driver with EnvyNG 1.1.1) |
2008-04-06 06:30:39 |
csemichon |
bug |
|
|
added attachment 'Xorg.0.log' (/var/log/Xorg.0.log after update) |
2009-03-12 14:59:06 |
Jonathan Thomas |
linux-restricted-modules-2.6.24: status |
Incomplete |
Invalid |
|
2009-03-12 14:59:06 |
Jonathan Thomas |
linux-restricted-modules-2.6.24: statusexplanation |
Thanks for the very thorough report! Just one thing to ask - could you attach the complete Xorg.0.log file (it has some additional info beyond the fglrx lines which can be useful).
Looking through the logs, a few things jump out:
(WW) fglrx(0): Failed to open DRM connection
(WW) fglrx(0): No DRM connection for driver fglrx.
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
The above is saying, "You don't have 3D because DRM (and consequently DRI) is not enabled. You appear to be missing the kernel drm module".
(II) fglrx(0): Display1: No EDID information from DDC.
(II) fglrx(0): Display1: Failed to get EDID information.
The above says that there is a problem retrieving EDID info from your monitor, so it won't be able to auto-detect resolutions, dpi's, and so forth. This is probably unrelated to the DRM issue though. See bugs.launchpad.net/ubuntu/+bug/edidfail for more details on this type of issue.
(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
(WW) fglrx(0): could not detect X server version (query_status=-3)
This looks weird. It appears your fglrx driver wasn't able to make sense of your X.org version. X.org changed their numbering scheme from 7.x.x.x to 1.3.x several months back. I had thought -fglrx caught this though, so am surprised to see an error showing up in an Xorg.0.log. Potentially this could be a clue why your kernel drm module didn't load.
Can you try manually forcing it to load (I think `modprobe fglrxdrm` might do it, but that's just a guess.) |
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! |
|