[gutsy][regression][fglrx] X doesn't start

Bug #115188 reported by Denis Moyogo Jacquerye
64
Affects Status Importance Assigned to Milestone
X.Org X server
Fix Released
Unknown
linux-restricted-modules-2.6.22 (Ubuntu)
Fix Released
Wishlist
Bryce Harrington

Bug Description

After upgrading to the kernel 2.6.22-3, the corresponding fglrx module and driver on Gutsy and xserver-xorg, X doesn't start
xserver-xorg (1:7.2-0ubuntu11)
xserver-xorg-core (2:1.3.0.0.dfsg-4ubuntu1)
fglrx-control (8.34.8+2.6.22.1-3.5)
xorg-driver-fglrx (7.1.0-8.34.8+2.6.22.1-3.5)

Here's the error X gives:
[atiddxSetup] X version mismatch - detected X.org 1.3.0.0, required X.org 7.1.0.0
(EE) Failed to load module fglrx (module requirement mismatch, 0)
(EE) No drivers available.

Fatal server error:no screens found
XIO: fatal IO error 104 (Connection reset by peer) on X server :0.0
     after 0 requests (0 known processed) with 0 events remaining.

Revision history for this message
Denis Moyogo Jacquerye (moyogo) wrote :

downgrading to xorg_7.2-0ubuntu11_i386.deb
xserver-xorg-core_1.2.0-3ubuntu8_i386.deb
xserver-xorg-dev_1.2.0-3ubuntu8_i386.deb
prevents this bug.

Revision history for this message
Giedrius (giedrbac) wrote :

Same here. I was able to solve this problem only by downgrading
xserver-xorg-core_1.2.0-3ubuntu8_i386.deb

Revision history for this message
Kees Cook (kees) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. It seems that the closed-source ati driver is incorrectly testing the Xorg server version (see the attached Debian bug report). The only sane option, unfortunately, is to wait for an update from ATI that fixes this problem.

Changed in xorg:
assignee: nobody → keescook
importance: Undecided → Wishlist
status: Unconfirmed → Confirmed
Kees Cook (kees)
Changed in xorg-server:
assignee: keescook → nobody
Revision history for this message
Kees Cook (kees) wrote :

See if the attached script successfully fixes the fglrx driver. This is only a workaround, as it totally disables the Xorg version check. If it doesn't work, you can restore the backup file it makes for you.

Revision history for this message
Giedrius (giedrbac) wrote :

Patch works for me.
If there is something else I can help you in fixing this issue, please let me know. I'll do my best to help.

Thank you for such fast response.

Revision history for this message
Luca Corti (cortez) wrote :

After patching X starts but:

(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 1.3.0.0
(WW) fglrx(0): detected X server is not compatible
(WW) fglrx(0): atiddxDriScreenInit failed
(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): ********************************************* *

So without 3D acceleration....

Revision history for this message
Kees Cook (kees) wrote :

Ah, there appear to be multiple version tests. Try this new patch script. Again, it's a hack, be careful. :)

Revision history for this message
JoergMechnich (joerg-mechnich) wrote :

Nice work!

Went flawlessly for me.

Changed in xorg-server:
status: Unknown → Unconfirmed
Revision history for this message
Dario Zanzico (dario.zanzico) wrote :

I don't know if it's related, but after downgrading x.org and running te patch script I'mnot able to use beryl on xgl anymore...

some info:
strace beryl-xgl:
....
gettimeofday({1179561915, 382907}, NULL) = 0
gettimeofday({1179561915, 382955}, NULL) = 0
write(4, "&l\2\0R\0\0\0", 8) = 8
read(4, "\1\1\266\20\0\0\0\0R\0\0\0 \0@\3N\2k\3N\2k\3\0\0\0\0\313"..., 32) = 32
gettimeofday({1179561915, 383248}, NULL) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

everything else seems to be running fine.

Revision history for this message
Andres Freund (andres-anarazel) wrote :

Unforunately debian/ubuntu/whatever propably wont be able to ship something patched - as far as I know the ati licence prohibits modifying any binary only part of their driver.

Andres

Revision history for this message
Bryce Harrington (bryce) wrote :

But can we ship the script for the user to use to patch the driver? Or would that be too gray of an area?

Revision history for this message
Bryce Harrington (bryce) wrote :

I was able to reproduce the bug on my NV 285 laptop with fglrx, and can confirm that kees' patch script fixed it.

Revision history for this message
Dario Zanzico (dario.zanzico) wrote :

Theberyl problem is not related, sorry. Now i'm able to use compiz after patching with the script. So I can report the script as working! Thanks

Revision history for this message
Dario Zanzico (dario.zanzico) wrote :

The Beryl problem is not related, sorry. Now i'm able to use compiz after patching with the script. So I can report the script as working! Thanks

Changed in xorg-server:
status: Unconfirmed → Fix Released
Revision history for this message
Pavel Rojtberg (rojtberg) wrote :

how about updating the fglrx driver in ubuntu to something less ancient, like 8.37.6, which officially supports xorg1.3?

Revision history for this message
Anthony Durity (anthony-durity) wrote :

I second what Pavel Rojtberg says; Gutsy is meant to be the development branch of Ubuntu so why not use the latest fglrx (as of this moment) 8.37.6 ?

If you follow the Assigned To link above to the Debian bug database [1] you find that ATI (I _think_ it's ATI, there seems to be zero branding however) has this reported [2] and fixed in 8.37.6

Here is a description of how to install it (which is easy enough but not _that_ easy)

From this page [3] download the latest binaries [4], yes! binaries... oooh evil.
Copy to /usr/share/ati
You need a couple of debian packages

sudo apt-get install debhelper
sudo apt-get install dpkg-dev

Then...

sudo sh ati-driver-installer-8.37.6-x86.x86_64.run --buildpkg Ubuntu/gutsy

Now you should have...

sahos@sahos-laptop:/usr/share/ati$ ls -l *.deb
-rw-r--r-- 1 root root 3318892 2007-06-06 23:41 fglrx-amdcccle_8.37.6-1_i386.deb
-rw-r--r-- 1 root root 912460 2007-06-06 23:41 fglrx-kernel-source_8.37.6-1_i386.deb
-rw-r--r-- 1 root root 5780050 2007-06-06 23:41 xorg-driver-fglrx_8.37.6-1_i386.deb
-rw-r--r-- 1 root root 40366 2007-06-06 23:41 xorg-driver-fglrx-dev_8.37.6-1_i386.deb

So...

sudo dpkg -i xorg-driver-fglrx_8.37.6-1_i386.deb
sudo dpkg -i fglrx-kernel-source_8.37.6-1_i386.deb

Now install module assistant to help you build the kernel module; install the kernel headers if you don't have them by now (you mean to say you don't have them by now?!)

sudo apt-get install module-assistant
sudo apt-get install linux-headers-generic

Delete the useless fglrx stuff that linux-restricted-modules installs - if there's a better more non-lethal way please let me know...

sudo rm -rf /lib/linux-restricted-modules/2.6.22-6-generic/fglrx

Now close all package managers and go to /usr/src then

sudo module-assistant

Choose PREPARE, choose SELECT, choose fglrx-kernel and then GET, BUILD and INSTALL - keep hitting esc until you get to the command line again and then

sudo depmod -a

Reboot and enjoy

ps: If I skipped any steps please fill them in - thanks!

1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420174
2: http://ati.cchtml.com/show_bug.cgi?id=609
3: http://ati.amd.com/support/drivers/linux/linux-radeon.html
4: https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.37.6-x86.x86_64.run

Revision history for this message
Zenigata (andrea-loyer) wrote :

Hi,

I bumped into the same problem under Feisty with the X.org from gutsy. I tried the solution from Anthony, but it seems that 3D still does not want to work. The patch from Kees does not seems to work either, but I'm not sure version it is verry version dependent or not.

Revision history for this message
Zenigata (andrea-loyer) wrote :

here the thing I got when I try the 8.37.6-1 driver :

(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 7.1.0.0
(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): ********************************************* *

Revision history for this message
berg (berg-foss) wrote :

in berg@berg-laptop:~$ uname -a
Linux berg-laptop 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 GNU/Linux
berg@berg-laptop:~$
at this time I have the same behavior yet for fglrx

I have to use ati driver instead

Revision history for this message
berg (berg-foss) wrote :
Revision history for this message
berg (berg-foss) wrote :
Revision history for this message
Matteo Z (matteozandi) wrote :

FIXED!

matteo@gutsy:~$ uname -a
Linux gutsy 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 GNU/Linux
matteo@gutsy:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI MOBILITY RADEON X700
OpenGL version string: 2.0.6473 (8.37.6)

matteo@gutsy:~$ dpkg -l | grep linux-restricted-modules
ii linux-restricted-modules-2.6.22-6-generic 2.6.22.2-6.1 Non-free Linux 2.6.22 modules on x86/x86_64
ii linux-restricted-modules-common 2.6.22.2-6.1 Non-free Linux 2.6.22 modules helper script

Revision history for this message
Sergey (hvmptydvmpty) wrote :

fglrx just got upgraded to 8.37 in gutsy, but I'm reluctant to install it on my amd64 arch because it depends on libc6-i386, which doesn't seem right.

Revision history for this message
Kees Cook (kees) wrote :

New l-r-m published with 8.37.6 driver.

Changed in linux-restricted-modules-2.6.22:
assignee: nobody → bryceharrington
status: Confirmed → Fix Released
Revision history for this message
Kees Cook (kees) wrote :

Sergey, I'm not sure what you mean. Where do you see the libc6-i386 dependency? Here's what I see for l-r-m:

Source: linux-restricted-modules-2.6.22
Version: 2.6.22.2-6.1
Provides: nvidia-kernel-1.0.9631, nvidia-kernel-1.0.7184, nvidia-kernel-1.0.9755
Depends: linux-image-2.6.22-6-generic, linux-restricted-modules-common (>= 2.6.22), module-init-tools, nvidia-kernel-common

Revision history for this message
Sergey (hvmptydvmpty) wrote :

My apologies, I wasn't clear. l-r-m installs just fine, thank you!

I meant the xorg-driver-fglrx 8.37.6 package. I couldn't submit a separate bug for this because this name is not in the package list on bug submission page (it's from restricted, I guess that's why). When I try to upgrade, Synaptic asks to install libc6-i386.

Revision history for this message
Kaltsi (kaltsi) wrote :

I can't use the ati driver .....

sudo module-assistant -f
Starting the Dialog UI...

Updated infos about 86 packages
Selecting previously deselected package fglrx-kernel-2.6.22-14-generic.
(Reading database ... 122396 files and directories currently installed.)
Unpacking fglrx-kernel-2.6.22-14-generic (from .../fglrx-kernel-2.6.22-14-generic_8.38.6-1+2.6.22-14.41_i386.deb) ...
dpkg: dependency problems prevent configuration of fglrx-kernel-2.6.22-14-generic:
 fglrx-kernel-2.6.22-14-generic depends on xorg-driver-fglrx (= 8.38.6-1); however:
  Version of xorg-driver-fglrx on system is 8.40.4-1.
dpkg: error processing fglrx-kernel-2.6.22-14-generic (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 fglrx-kernel-2.6.22-14-generic

I: Direct installation failed, trying to post-install the dependencies

Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages will be REMOVED:
  fglrx-kernel-2.6.22-14-generic
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 1188kB disk space will be freed.
Do you want to continue [Y/n]?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.