Comment 4 for bug 208368

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.)