8.6 problems on Kubuntu Hardy

[aeleneski]

I moved this into its own thread from the general 8.6 thread. Well I seem to be having some big problems here. I tried building with the --buildandinstallpkg, but that had errors. So I tried just the regular --buildpkg Ubuntu/hardy, then dpkg -i to the deb files. This seemed to work, so upon restart I go to run fglrxinfo and I get back


fglrxinfo: ../../src/xcb_io.c:350: _XReply: Assertion `!dpy->xcb->reply_data' failed.
Abort

Also, if I do dkms status I recieve all of this

dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
fglrx, 8.471, 2.6.22-14-generic, i686: built
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
fglrx, 8.443.1, 2.6.22-14-generic, i686: built
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
fglrx, 8.452.1, 2.6.22-14-generic, i686: built
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
fglrx, 8.455.2, 2.6.22-14-generic, i686: built
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
fglrx, 8.476, 2.6.22-14-generic, i686: installed
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
fglrx, 8.476, 2.6.24-16-generic, i686: built



Should all these errors be there? I have tried remove the individual versions by doing something like

sudo dkms remove -m fglrx -v 8.476 --all
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.

Error! Bad conf file.
File: /var/lib/dkms/fglrx/8.476/source/dkms.conf does not represent
a valid dkms.conf file.


I have also tried switching back to 8.5. This seems to install fine, but then upon restart and doing fglrxinfo I receive

fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.4 (2.1 Mesa 7.0.3-rc2)

[aeleneski]

Ok, well I went back and installed all of those drivers for which I was getting the dkms status errors for (back to 7.12). Then I did the dkms remove command. When that was finished I did dkms status, and nothing came up. Then I restarted, and installed 8.6, restarted again. Now when I do fglrxinfo I get display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon Xpress Series
OpenGL version string: 2.1.7659 Release

Segmentation fault


Same sort of thing for glxinfo where it prints everything fine, but then says Segmentation fault at the end. I am now able to run fgl_glxgears fine now, without it crashing like before. I have been running fine now for about 15 minutes, so I unsure of the the seg fault is. But something else I noticed is that when installing the driver I suddenly would lose my sound, it would mute everything.

[Kano]

It seems something with dkms uninstall wents wrong, you can do before you install new driver:

rm -rf /var/lib/dkms/fglrx

[aeleneski]

It seems something with dkms uninstall wents wrong, you can do before you install new driver:

rm -rf /var/lib/dkms/fglrx

Well when I went back an installed/removed all previous drivers there is now nothing in that directory. So I re-installed 8.06 and get the segmentation fault in my previous post. I have even tried purging all fglrx relation packages using dpkg -P fglrx... And then after that, upon reinstall of 8.06 I still get the seg fault.

I also notice that now with 8.06 installed upon a restart or shutdown of my laptop it freezes again like some earlier drivers and I have to push the power button and then the process seems to continue. I think I remember this being a problem with the atievents hanging?

My xorg.conf is now

# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "ServerLayout"

# Uncomment if you have a wacom tablet
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
Inputdevice "Generic Keyboard"
Inputdevice "Configured Mouse"
Inputdevice "Synaptics Touchpad"
Option "AIGLX" "on"
EndSection

Section "Files"
EndSection

Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "int10"
Load "vbe"
Load "glx"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizEdgeScroll" "0"
EndSection

Section "InputDevice"
Identifier "stylus"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "InputDevice"
Identifier "eraser"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "InputDevice"
Identifier "cursor"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
Option "TexturedVideo" "Off"
Option "VideoOverlay" "On"
Option "OpenGLOverlay" "Off"
Busid "PCI:1:5:0"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
Defaultdepth 24
SubSection "Display"
Modes "1280x800"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "DRI"
Mode 0666
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection


I remember the shutdown problem seemed to be fixed with something like this Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "BlockSignalsOnLock" "on"
Option "KernelModuleParm" "locked-userpages=0"
Option "XAANoOffscreenPixmaps" "true"
Busid "PCI:1:5:0"
EndSection


But it seems to do nothing now as both versions of xorg.conf act the same.

[revolutio]

I got the same error with fglrxinfo after trying to install the 8.6 drivers:
fglrxinfo: ../../src/xcb_io.c:350: _XReply: Assertion `!dpy->xcb->reply_data' failed.
Aborted


I'm running Ubuntu Hardy. For installation I was following these instructions (http://wiki.cchtml.com/index.php/Ubuntu_Hardy_Installation_Guide#Method_2:_Manual_M ethod_.28installing_Catalyst_8.6.29). I've tried twice with the same results and this is the only other mention of this problem I have come across.

I'm concerned that I had uninstalled the previous drivers improperly, is there a thorough way to do so so that I can eliminate that as a cause? The second time I had used the 'rm -rf /var/lib/dkms/fglrx' trick.

[aeleneski]

I got the same error with fglrxinfo after trying to install the 8.6 drivers:


I'm running Ubuntu Hardy. For installation I was following these instructions (http://wiki.cchtml.com/index.php/Ubuntu_Hardy_Installation_Guide#Method_2:_Manual_M ethod_.28installing_Catalyst_8.6.29). I've tried twice with the same results and this is the only other mention of this problem I have come across.

I'm concerned that I had uninstalled the previous drivers improperly, is there a thorough way to do so so that I can eliminate that as a cause? The second time I had used the 'rm -rf /var/lib/dkms/fglrx' trick.


Well, I sort of explained what I did above. When doing dkms status, it showed me that through many kernel upgrades and driver updates some uninstalls did not happen correctly. So, I just went back through the driver versions, installed all the ones that were showing errors, and did dkms remove to uninstall the version. In the end, I was able to successfully install driver version 8.6, but upon doing fglrxinfo I get the segfault said above, and also I am unable to play games in wine because of screen corruption. In the meantime I have just gone back to 8.5, and will wait until 8.7 comes out.

[Inkaine]

Which graphics card do you use?

For I have had exactly the same error running ArchLinux on an internal AMD Radeon 3200 (aka 780G IGP chipset). Reverting back to Catalyst 8.5 worked fine for me though. (Except for wine which keeps complaining about wrong pixel format...) Hope it will be fixed in 8.7.

[aeleneski]

Which graphics card do you use?

For I have had exactly the same error running ArchLinux on an internal AMD Radeon 3200 (aka 780G IGP chipset). Reverting back to Catalyst 8.5 worked fine for me though. (Except for wine which keeps complaining about wrong pixel format...) Hope it will be fixed in 8.7.

I am using an Xpress200m.