[M24-1P] No 3D acceleration after distupgrade to 8.10

[Schmallon]

Hardware: Notebook HP nx8220, Mobility x600

After upgrading to 8.10, fglrx still loads but 3D acceleration does not work anymore. Although DRI is not disabled in xorg.conf, Xorg.0.log says it is:
-----------------------------------
(II) Module xaa: vendor="X.Org Foundation"
 compiled for 1.5.2, module version = 1.2.0
 ABI class: X.Org Video Driver, version 4.1
(**) fglrx(0): NoDRI = YES
(**) fglrx(0): Capabilities: 0x00000000
...
(WW) fglrx(0): ***********************************
(WW) fglrx(0): * DRI initialization disabled! *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ***********************************
...
(EE) fglrx(0): XMM failed to open CMMQS connection.
(II) fglrx(0): XMM failed to initialize!
--------------------------

Running glxinfo gives me
--------------------------
X Error of failed request: BadRequest (invalid request code or no such operation)
  Major opcode of failed request: 159 (GLX)
  Minor opcode of failed request: 19 (X_GLXQueryServerString)
  Serial number of failed request: 10
  Current serial number in output stream: 10
-------------------------

I tried un- and reinstalling anything fglrx-related using envyng without any success.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
     Subsystem: Hewlett-Packard Company Device [103c:0934]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M24 1P [Radeon Mobility X600] [1002:3150]
     Subsystem: Hewlett-Packard Company Device [103c:0934]

[bart (bart-wp)]

I have the same Problem on a DELL Optiplex 740
ATI RV516 [Radeon X1300/X1550 Series] rev 0

[Mario Limonciello (superm1)]

Hi guys,

It's quite possible these are different issues, but we just need a few more things before this can be forwarded upstream.

Bart, can you please post full lspci -vvnn output, Xorg.0.log and dmesg output so we can ensure it's the same issue?

Schmallon,
Can you post dmesg output to accompany this?

Thanks

[Mario Limonciello (superm1)]

Bart:
based on that information it didn't even try to load the kernel module. Can you check the output of
modinfo fglrx

If you receive "modinfo: could not find module fglrx", then please try to purge fglrx-kernel-source and reinstall it and try again.

[bart (bart-wp)]

Hi Mario,
yes, that solved the problem for me. Thanks.
Greetings
Bart

[Bryce Harrington (bryce)]

Aha, the cut and paste of the error missed the real issue:

(II) fglrx(0): driver needs X.org 1.4.x.y with x.y >= 99.906
(II) fglrx(0): detected X.org 7.4.2.0
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *

So fglrx appears to be failing to properly test the xserver version.

What version of -fglrx are you running? If you're running less than the version shipped with Intrepid, please upgrade to that, which should work fine with the 1.5.2 X server in Intrepid.

[Schmallon (matthias-kleine)]

The error message you are referring to is related to the bug posted by Mario Limonciello which, as it looks like, was already resolved. The original error is unfortunately unrelated to this error message (see xorg.log posted by me) and still persists for me.

[Muanis (muanis)]

Just to let know, I've been using ATI Driver 8.11 on Hardy Heron. After issuing a dist-upgrade could not boot into X.

After trying a lot of stuff the remove --purge and a reinstall just got meu booted into X again.

[Bryce Harrington (bryce)]

I've posted a new version of the -fglrx driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get fglrx 8.620 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.