System lockup with catalyst 8.01

[jasonxh]

My system gets frozen whenever I try to log out from gnome, restart, shutdown, etc., even when I press Ctrl+Alt+Backspace to restart X. Switching to console works, but I can't issue a gdm restart in console either. Seems like the driver is refusing to reinitialize itself.

Anyone has experienced this?

[jasonxh]

My system gets frozen whenever I try to log out from gnome, restart, shutdown, etc., even when I press Ctrl+Alt+Backspace to restart X. Switching to console works, but I can't issue a gdm restart in console either. Seems like the driver is refusing to reinitialize itself.

Anyone has experienced this?

BTW, I'm on Ubuntu feisty, with custom kernel 2.6.23.13 and Xorg 7.2.

[bridgman]

There are a couple of reports of this on the 8.01 thread. For some people, disabling the overlay options seems to make a difference :

Option "OpenGLOverlay" "off"
Option "VideoOverlay" "off"

Which graphics card are you using ?

[jasonxh]

There are a couple of reports of this on the 8.01 thread. For some people, disabling the overlay options seems to make a difference :



Which graphics card are you using ?

Thanks for the hint. I'll try meddling with the overlay options tonight. I'm using mobility X1300, on a thinkpad T60.

[jasonxh]

bridgman, it doesn't solve my problem at all. Still freezes my system. What a joke is ATI making at its customers!

What is this NEW code base driver truly for? With this laggy 2d and bugs after bugs and absolutely nothing to do with the word "stable", who's gonna enjoy the "increased" 3d fps???

[bridgman]

Hi jason;

Sorry this didn't work. I'll see if we have been able to reproduce the problem in house yet.

The challenge here is that a lot of the worst issues don't show up on any of our in house systems or even in the beta test program, so without driving to your house, finding a clue on the forum threads, or getting a lot of info via Bugzilla we don't have a way to reproduce and fix the bug OR to stop it from happening in the future.

I'm not sure if there is a Bugzilla ticket open for this one, but if not please file one and include hw info, logs & conf. That can really help our chances of configuring a system close enough to yours that we can see the problem and fix it.

We'll go through this more in the Q&A, but the "new code base" is the 3d part and the low level, ASIC-specific bits of the X ("2d") driver. The rest of the X driver is *not* new code, but the dev team is now able to spend a lot more time on the "old code" so we do seem to be picking off more issues every month.

[knutbert]

I'm not sure if there is a Bugzilla ticket open for this one, but if not please file one and include hw info, logs & conf.

I suppose you are talking about http://ati.cchtml.com/ , right?

While reporting (http://ati.cchtml.com/show_bug.cgi?id=987) the "failed to initialize ASIC" issue I am experiencing (http://phoronix.com/forums/showthread.php?t=7451), I noticed that version 8.452.1 is not in the bugzilla pull-down menus yet - 7.12 is the latest version listed. :(

The ATI Linux Feedback program (http://support.ati.com/ics/survey/survey.asp?deptID=894&surveyID=508&type=web) is even stuck at version 8.433 (Catalyst 7-11)... :D

Maybe you could trigger some updating of these tools...?

Regards,
knutbert

[ig-88]

i have the lockups too, and i'm using a hd2600xt by gigabyte on a p35 motherboard by msi using gutsy.
probably this helps finding the issue.

[jasonxh]

Hi bridgman, I wasn't aware that you are from AMD/ATI, so forgive me if anything I said sounds improper.

Anyway it's nice to see that someone from inside is taking complaints from customers and trying to resolve problems.

[krnlg]

I'd just like to add that for several releases of fglrx right back to the start of the "new style driver" at least, if I stop gdm with "/etc/init.d/gdm stop", the system will very often freeze if I then try to switch to the virtual console on which X was running - hard reset needed. (2.6.18 kernel)
On the other hand generally speaking if I kill X from within it, rather than using the gdm service stop command from the console, the VT gets freed properly and nothing seems to break.

[BurnHead]

I just wanted to add that I'm experiencing the same problem here. Logging out of my GNOME session or killing the X server via Ctrl-Alt-Backspace completely freezes the system. I'm using Ubuntu Hardy Heron (kernel 2.6.24-4) with the latest upgrades and the latest ATI Catalyst driver (Catalyst 8.01).
If you need further information (logfiles, etc.) then feel free to ask me about it.

My machine:
- Samsung R60Plus Notebook,
- Intel Core2Duo T5450 CPU
- ATI Mobility Radeon X2300
- 2048 MB RAM

[DeeZiD]

I have the same problem when logging out or shutting down.
KDE4-kdm
Ubuntu Gutsy

MSI GX710 Notebook
ATi Radeon HD2600 mobility
Catalyst 8.01

regards Dennis

[bridgman]

Hi bridgman, I wasn't aware that you are from AMD/ATI, so forgive me if anything I said sounds improper.

No worries. If everyone started saying only nice things the forum wouldn't be fun any more :D

Can everyone experiencing this lockup at shutdown please try disabling the three functions -- OpenGLOverlay, VideoOverlay and TexturedVideo -- and let us know what you find and what GPU you are running (and, if you feel generous, *which* of the options made the difference) ? It seems that this workaround is working for some folks but not for others, and it's not clear yet what conditions make the difference.

[ig-88]

i'm sorry but no option works for me. i crashes always. using a hd2600xt

[ivanovic]

Can everyone experiencing this lockup at shutdown please try disabling the three functions -- OpenGLOverlay, VideoOverlay and TexturedVideo -- and let us know what you find and what GPU you are running (and, if you feel generous, *which* of the options made the difference) ? It seems that this workaround is working for some folks but not for others, and it's not clear yet what conditions make the difference.

Okay, so here I am, I did some testing on it and no matter what I do, it does crash.

So first my sysspecs, then what I did:
I am running gentoo unstable x86 with vanilla 2.6.23.11 on a HD3850 512MB. My xorg-x11 server version is x11-base/xorg-server-1.4.0.90-r2 and I am running latest 8.01 driver.

The problem: It is not possible to shutdown X11 and use the terminal/restart from the terminal. *But* this does not happen always. I do at least have to use some app that is using OpenGL or running Xorg for some time. I don't know for sure which one it is. At least there is no problem when I directly start and quit Xorg, that is not enough...

Here is what I did to try to fix the problem:
1) First I did remove the file /etc/ati/amdpcsdb.
2) Comment out *all* XVideo related options in /etc/X11/xorg.conf.
3) Restart the whole system (restarting X was no option, that is the system basically crashed / showed no graphics output anymore on the terminal after quiting X).
4) After the restart of the system and the start of xorg (the overlay option were *all* commented out in xorg.conf), I did have a look at the automatically created file /etc/ati/amdpcsdb. In there those options were set:
VideoOverlay=Son
OpenGLOverlay=Soff
5) After some hours of normal usage (that is viewing videos and such), I did try to shutdown the system. The same crash of unloading fglrx did occur. I was still able to ssh into the system, *but* unloading fglrx was not possible because rmmod did tell me that it was still being in use. So another ctrl+alt+del reboot.
6) After the reboot I did just edit the file /etc/X11/xorg.conf to explicitly set these to 'off':
Option "TexturedVideo" "off"
Option "VideoOverlay" "off"
Option "OpenGLOverlay" "off"
Right after the start of Xorg, I did have a look at /var/log/Xorg.0.log and there was still the message that VideoOverlay was not supported on this card and that I should use TexturedVideo instead. I was a little surprised, but thought it could just be a general message, so I did not care. After some hours of normal usage, turning off Xorg did not work again, just a nice and black screen.
7) One reboot later I did remove the file /etc/ati/amdpcsdb, started xorg and had another look at the log, now the enty regarding texturedvideo was gone, so I though everything should work when shutting down xorg.
8) When shutting down xorg, the same as before did happen. The problem was not fixed.

So what info can I provide now?
1) The content of /etc/ati/amdpcsdb does override whatever is defined in /etc/X11/xorg.conf. IMO this is a bug...
2) Nothing of those options did change anything.

I hope that I can post some more chars, so that I don't have to double post, to post my current config and some log output...

content of /etc/X11/xorg.conf after step '8)':
Section "ServerLayout"
Identifier "Server Layout"
Screen "Screen0" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/local/share/fonts"
EndSection

Section "Module"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
Load "freetype"
Load "glx" # libglx.a
Load "dri" # libdri.a
Load "drm" # libdrm.a
EndSection

Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
Option "XkbModel" "cymotionlinux"
Option "XkbLayout" "de"
Option "XkbVariant" "nodeadkeys"
Option "CoreKeyboard"
EndSection

Section "InputDevice"
Identifier "Mouse1"
Driver "evdev"
Option "Protocol" "event"
Option "evBits" "+1-2"
Option "keyBits" "~272-287"
Option "relBits" "~0-2 ~6 ~8"
EndSection

Section "Monitor"
Identifier "Dell2405FPW"
HorizSync 31.5 - 100.0
VertRefresh 50.0 - 120.0
Option "DPMS"
EndSection

Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
BusID "PCI:1:00:0"
Screen 0
# Option "XAANoOffscreenPixmaps" "true"
# fglrx options
Option "TexturedVideo" "off"
Option "VideoOverlay" "off"
Option "OpenGLOverlay" "off"
EndSection

Section "Screen"
Identifier "Screen0"
Device "ATI Graphics Adapter"
Monitor "Dell2405FPW"
DefaultDepth 24
EndSection

Section "DRI"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
EndSection

Section "Extensions"
Option "Composite" "Disable"
# Option "XVideo" "Enable"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection

[ivanovic]

Continuing the post before...


content of /etc/ati/amdpcsdb after step '8)':
AMDPCSDBV1
[AMDPCSROOT/SYSTEM/MCIL]
PXACAutoSwitch=V0
PXDCAutoSwitch=V0
CVRULE_CUSTOMIZEDMODESENABLED=V1
DALLinuxSupport=V1
DALNonStandardModesBCD=R14001050000000601792134400 00006018001440000000601856139200000060160012000000 00601280076800000060144009000000006012800960000000 601680105000000060
DALRULE_ADDNATIVEMODESTOMODETABLE=V1
DALRULE_DYNAMICMODESUPPORT=V1
DALRULE_GetLCDFakeEDID=V1
DALRULE_GetTVFakeEDID=V1
DALRULE_NOFORCEBOOT=V1
DALRULE_POWERPLAYDISREGARDDISPLAY=V1
DALRULE_RESTRICTDISPLAYSBASEDONPANELRES=V0
GCORULE_FlickerWA=V1
GCORULE_LCDValidatePixelClkOnly=V1
GXOM5XDisableLaneSwitch=V1
R6LCD_RETURNALLBIOSMODES=V1
TVEnableOverscan=V1
DALLastSelected=V16
DALLastConnected=V16
DALLastTypes=V221
DALObjectData0=R0101000101000101000101000102000102 00030102030102010400010400030104030104010200010200 03010203010201080001080003080103080103080203080203 08010308010308040308040308010308010308020308020308 01030801011000011000031001031001031002031002031001 03100103100403100403100103100103100203100203100103 10010308100308100308100308100308100308100308100308 10030810030810030810030810030810030810030810030810 01200001200003012003012001020001020003010203010201 04000104000301040301040102000102000301020301020308 20030820030801030801030802030802030801030801030804 03080403080103080103080203080203080103080103102003 10200310010310010310020310020310010310010310040310 04031001031001031002031002031001031001030810030810 03081003081003081003081003081003081003081003081003 08100308100308100308100308100308100101000101000101 00000000010200000000010100020002010400000000010100 02000401020000000001010002000201080000000001080002 00010108000200020108000200010108000200040108000200 01010800020002010800020001011000000000011000020001 01100002000201100002000101100002000401100002000101 10000200020110000200010108000200100108000200100108 00020010010800020010010800020010010800020010010800 02001001080002001001200000000001010002002001020000 00000101000200020104000000000101000200040102000000 00010100020002010800020020010800020001010800020002 01080002000101080002000401080002000101080002000201 08000200010110000200200110000200010110000200020110 00020001011000020004011000020001011000020002011000 02000101080002001001080002001001080002001001080002 00100108000200100108000200100108000200100108000200 10000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000
DALObjectData1=R0000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000
DALSelectObjectData0=R0101000101000101000101000102 00010200030102030102010400010400030104030104010200 01020003010203010201080001080003080103080103080203 08020308010308010308040308040308010308010308020308 02030801030801011000011000031001031001031002031002 03100103100103100403100403100103100103100203100203 10010310010308100308100308100308100308100308100308 10030810030810030810030810030810030810030810030810 03081001200001200003012003012001020001020003010203 01020104000104000301040301040102000102000301020301 02030820030820030801030801030802030802030801030801 03080403080403080103080103080203080203080103080103 10200310200310010310010310020310020310010310010310 04031004031001031001031002031002031001031001030810 03081003081003081003081003081003081003081003081003 08100308100308100308100308100308100308100101000101 00010100000000010200000000010100020002010400000000 01010002000401020000000001010002000201080000000001 08000200010108000200020108000200010108000200040108 00020001010800020002010800020001011000000000011000 02000101100002000201100002000101100002000401100002 00010110000200020110000200010108000200100108000200 10010800020010010800020010010800020010010800020010 01080002001001080002001001200000000001010002002001 02000000000101000200020104000000000101000200040102 00000000010100020002010800020020010800020001010800 02000201080002000101080002000401080002000101080002 00020108000200010110000200200110000200010110000200 02011000020001011000020004011000020001011000020002 01100002000101080002001001080002001001080002001001 08000200100108000200100108000200100108000200100108 00020010000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000
DALSelectObjectData1=R0000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000
DALCurrentObjectData=R011000000000
DALR6 DFPI 2_MaxModeInfo=R0000000080070000B0040000000000004B0 00000
DAL_DFP2ColorTemperatureSourceAC10A010=R0200000064 190000
AsicOnLowPower=V0
[AMDPCSROOT/SYSTEM/LibXUtil/Display1]
Map=V0
Enable=V1
[AMDPCSROOT/SYSTEM/LDC]
LastViewedPage=SWillkommen

Output of "grep -i 'video' /var/log/Xorg.0.log" after step '8)':
X.Org Video Driver: 2.0
ABI class: X.Org Video Driver, version 2.0
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
Module class: X.Org Video Driver
(II) AMD Video driver is running on a device belonging to a group targeted for this release
(II) AMD Video driver is signed
ABI class: X.Org Video Driver, version 2.0
(**) fglrx(0): Option "VideoOverlay" "off"
(**) fglrx(0): Option "TexturedVideo" "off"
ABI class: X.Org Video Driver, version 2.0
ABI class: X.Org Video Driver, version 2.0
(II) fglrx(0): ATI Video BIOS revision 9 or later detected
(--) fglrx(0): VideoRAM: 262144 kByte, Type: DDR3
(II) fglrx(0): Supported VESA Video Modes:
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): Supported additional Video Mode:
ABI class: X.Org Video Driver, version 2.0

Do you need any additional information? Like I said, nothing of those steps made a difference regarding the problem when shutting down Xorg. My guess is that the problem is somewhere at unloading the module, so that Xorg does not quit correctly. At least there is no kernel panic, so that I can cleanly reboot via ssh or ctrl+alt+del...

[BurnHead]

Unfortunately this didn't do the trick for me either. I disabled OpenGLOverlay, VideoOverlay and TexturedVideo in my xorg.conf but the problem is still the same - when logging out (or when pressing Ctrl-Alt-Backspace) my system just freezes while still displaying the gnome background. In my case pressing Ctrl-Alt-Del does not work.

I believe my Mobility X2300 is based on the RV515 chip.

[Kano]

I have got similar issues. I just use kdm not gdm, but the problem is that the dm can't be killed completly. In the error case not even with killall -9.

[Fenix-TX]

I have the same problem.
card: ati radeon 9600
system: kubuntu gutsy, kernel 2.6.23-1 custom

[ivanovic]

Okay, some more work later and now it looks like it works. Here is what I did:

* Remove the deamon 'atieventsd'.

That one seems to be broken and causing the problems. That not everyone is having those probs might be related to that it is working correctly for some or that they are not having it active.
Part of the problem for me might be related to this (though it is just a *very* blind guess):
$ aticonfig --lsp
Error: POWERplay is not supported on your hardware.
Since my card is a HD3850, it should have POWERplay, maybe some problems are coming from here. At least I do know, that the problems are related to this very app. The textured video stuff and overlay itself *might* be part of it, too, not sure here at all.

I was now able to use my system for ~4h, did some videocutting/viewing and was able to shutdown Xorg and to restart it without any problem.

[jasonxh]

In order to help track down the problem, I installed this new driver again. I did all the tricks bridgman suggested in xorg.conf, still no go. I noticed a subtle difference as compared to 8.40.4, i.e. the last OLD codebase driver which I'm still stick to for all these months. It's this authatieventsd.sh script. Using the OLD driver, I never see it in running processes, so I assume it's only run at the X startup, and quits when it finishes its job. But in the NEW driver, this process keeps running


sh -c /etc/ati/authatieventsd.sh grant :0 (null)


So I did some experiments after switching to console

1. Issue a gdm stop, which takes CONSIDERABLY longer than with the OLD driver. However, X is still running and I can not kill it.
2. Manually kill the authatieventsd.sh process, and X is automatically released. (Note that authatieventsd.sh will be respawned by atieventsd immediately, which is OK)
3. Issue a gdm start, which seems normal.

And whoops, the gdm (and X) was successfully restarted. While I don't know if authatieventsd.sh is supposed to be running all the time in the new driver, I'm almost sure that it has something to do with the freezing problem. Hope this gives clues.

My xorg.conf and Xorg.0.log should give you every detail of my configuration and hardware.

xorg.conf:

# /etc/X11/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(5) 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"
Identifier "Default Layout"
Screen "Default Screen" 0 0
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Logitech VX Revolution"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "Synaptics Touchpad"
EndSection

Section "Files"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

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

Section "ServerFlags"
Option "AIGLX" "off"
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 "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
Option "XAxisMapping" "6 7"
Option "YAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Logitech VX Revolution"
Driver "evdev"
Option "SendCoreEvents" "true"
Option "vendor" "0x046d"
Option "product" "0xc521"
Option "version" "0x0111"
Option "evBits" "+0-2 -3"
Option "HWHEELRelativeAxisButtons" "7 6"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
Option "SHMConfig" "true"
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 "Builtin Monitor"
HorizSync 30.0 - 67.0
VertRefresh 50.0 - 75.0
Option "DPMS"
EndSection

Section "Device"
Identifier "ATI Mobility Radeon X1300 Internal"
Driver "fglrx"
Option "VideoOverlay" "off"
Option "OpenGLOverlay" "off"
Option "TexturedVideo" "off"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Mobility Radeon X1300 Internal"
Monitor "Builtin Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "DRI"
Mode 0666
EndSection

Section "Extensions"
Option "Composite" "Disable"
EndSection


P.S. As ivanovic mentioned, the freezing problem does not occur EVERY time; it's often after some time of use, like 10 minutes or so. I've never been able to figure out what exactly makes the difference. If you're repeating my steps above and not experiencing noticable lag of gdm stop, then you're in the lucky cycle, which means you can then directly issue a gdm start. In other words, the problem didn't occur in your test. However if it does occur and you skip step 2, then you will fail to start X with the message like "an X server has already started on display :0.0".

[jasonxh]

Xorg.0.log: (unable to post full log due to length limit)

X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: Linux Ubuntu
Current Operating System: Linux jason-laptop 2.6.23.13-custom #3 SMP Sat Jan 12 17:18:22 EST 2008 i686
Build Date: 18 January 2008
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present

(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
(II) fglrx(0): pEnt->device->identifier=0x81e4650
(II) fglrx(0): === [atiddxPreInit] === begin
(II) fglrx(0): PCI bus 1 card 0 func 0
(**) fglrx(0): Depth 24, (--) framebuffer bpp 32
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) fglrx(0): Default visual is TrueColor
(**) fglrx(0): Option "OpenGLOverlay" "off"
(**) fglrx(0): Option "VideoOverlay" "off"
(**) fglrx(0): Option "TexturedVideo" "off"
(**) fglrx(0): Option "DPMS"
(II) fglrx(0): PCS database file /etc/ati/amdpcsdb not found
(II) fglrx(0): Creating PCS database from initial defaults instead
(==) fglrx(0): RGB weight 888
(II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
(==) fglrx(0): Gamma Correction for I is 0x06419064
(==) fglrx(0): Gamma Correction for II is 0x06419064
(==) fglrx(0): Buffer Tiling is ON
(--) fglrx(0): Chipset: "ATI Mobility Radeon X1300" (Chipset = 0x7149)
(--) fglrx(0): (PciSubVendor = 0x17aa, PciSubDevice = 0x2005)
(--) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI
(--) fglrx(0): Linear framebuffer (phys) at 0xd8000000
(--) fglrx(0): MMIO registers at 0xee100000
(==) fglrx(0): ROM-BIOS at 0x000c0000
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 3.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
(II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS
(II) fglrx(0): VESA VBE OEM Software Rev: 9.12
(II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc.
(II) fglrx(0): VESA VBE OEM Product: M52CSP
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
(II) fglrx(0): ATI Video BIOS revision 9 or later detected
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
(II) fglrx(0): Using adapter: PCI:1:0:0.
(--) fglrx(0): VideoRAM: 65536 kByte, Type: DDR1
(II) fglrx(0): PCIE card detected
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(II) fglrx(0): Connected Display1: LCD on internal LVDS [lvds]
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: LEN Model: 4022 Serial#: 0
(II) fglrx(0): Year: 2006 Week: 29
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Digital Display Input
(II) fglrx(0): Max H-Image Size [cm]: horiz.: 29 vert.: 21
(II) fglrx(0): Gamma: 2.20
(II) fglrx(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): redX: 0.610 redY: 0.330 greenX: 0.300 greenY: 0.530
(II) fglrx(0): blueX: 0.150 blueY: 0.130 whiteX: 0.313 whiteY: 0.329
(II) fglrx(0): Supported VESA Video Modes:
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 108.0 MHz Image Size: 287 x 215 mm
(II) fglrx(0): h_active: 1400 h_sync: 1448 h_sync_end 1560 h_blank_end 1688 h_border: 0
(II) fglrx(0): v_active: 1050 v_sync: 1051 v_sync_end 1054 v_blanking: 1066 v_border: 0
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 90.0 MHz Image Size: 287 x 215 mm
(II) fglrx(0): h_active: 1400 h_sync: 1448 h_sync_end 1560 h_blank_end 1688 h_border: 0
(II) fglrx(0): v_active: 1050 v_sync: 1051 v_sync_end 1054 v_blanking: 1066 v_border: 0
(II) fglrx(0): LTD141EN9B
(II) fglrx(0): EDID (in hex):
(II) fglrx(0): 00ffffffffffff0030ae224000000000
(II) fglrx(0): 1d100103801d1578ea6f959c544c8726
(II) fglrx(0): 21505421080081800101010101010101
(II) fglrx(0): 010101010101302a7820511a10403070
(II) fglrx(0): 13001fd71000001825237820511a1040
(II) fglrx(0): 307013001fd7100000180000000f0090
(II) fglrx(0): 43329043280f010030649055000000fe
(II) fglrx(0): 004c5444313431454e39420a20200045
(II) fglrx(0): End of Display1 EDID data --------------------
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(II) fglrx(0): Primary Controller - LCD on internal LVDS
(II) fglrx(0): Internal Desktop Setting: 0x00000001
(II) fglrx(0): POWERplay version 3. 5 power states available:
(II) fglrx(0): 1. 392/324MHz @ 60Hz [enable load balancing]
(II) fglrx(0): 2. 128/135MHz @ 60Hz [low voltage, enable sleep]
(II) fglrx(0): 3. 209/135MHz @ 60Hz [low voltage, enable sleep]
(II) fglrx(0): 4. 324/135MHz @ 60Hz [enable sleep]
(II) fglrx(0): 5. 338/324MHz @ 60Hz [enable sleep, thermal diode mode]
(==) fglrx(0): Qbs is not supported in this release. Disabled.
(==) fglrx(0): FAST_SWAP disabled
(==) fglrx(0): PseudoColor visuals disabled
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(==) fglrx(0): Center Mode is disabled
(==) fglrx(0): TMDS coherent mode is enabled
(II) fglrx(0): Total of 15 modes found for primary display.
(--) fglrx(0): Virtual size is 1400x1050 (pitch 0)
(--) fglrx(0): Display dimensions: (290, 210) mm
(--) fglrx(0): DPI set to (122, 126)
(--) fglrx(0): Virtual size is 1400x1050 (pitch 1408)
(==) fglrx(0): NoAccel = NO
(==) fglrx(0): NoDRI = NO
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) fglrx(0): Depth moves disabled by default
(==) fglrx(0): Capabilities: 0x00000000
(==) fglrx(0): CapabilitiesEx: 0x00000000
(==) fglrx(0): cpuFlags: 0x8000001d
(==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
(**) fglrx(0): ATI GART size: 256 MB
(II) fglrx(0): [pcie] 258048 kB allocated
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536
(==) fglrx(0): UseFastTLS=0
(==) fglrx(0): BlockSignalsOnLock=1
(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
(II) fglrx(0): doing DRIScreenInit
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0x2000
(II) fglrx(0): [drm] mapped SAREA 0x2000 to 0xb7c53000
(II) fglrx(0): [drm] framebuffer handle = 0x3000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.45.4
(II) fglrx(0): Date: Jan 16 2008
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.23.13-custom
(II) fglrx(0): Build-Kernel MODVERSIONS: no
(II) fglrx(0): Build-Kernel __SMP__: no
(II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
(II) fglrx(0): [drm] register handle = 0x00004000
(II) fglrx(0): Interrupt handler installed at IRQ 16.
(II) fglrx(0): Exposed events to the /proc interface
(II) fglrx(0): DRI initialization successfull!
(II) fglrx(0): FBADPhys: 0xc0000000 FBMappedSize: 0x01007000
(II) fglrx(0): FBMM initialized for area (0,0)-(1408,2984)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1408,1050) (front color buffer - assumption)
(II) fglrx(0): Largest offscreen area available: 1408 x 1934
(==) fglrx(0): Backing store disabled
(**) fglrx(0): DPMS enabled
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
(II) fglrx(0): Acceleration enabled
(II) fglrx(0): X context handle = 0x1
(II) fglrx(0): [DRI] installation complete
(II) fglrx(0): Direct rendering enabled
(==) fglrx(0): Silken mouse enabled
(==) fglrx(0): Using hardware cursor

[oyvind]

First of all, if you have useful input, please consider contributing to the bug report I've filed for this issue at: http://ati.cchtml.com/show_bug.cgi?id=992. Just don't expect to get any feedback :p.

Something about atieventsd and authatieventsd.sh was mentioned in the official 8.01-thread in connection with the freeze-on-logout problem. Ivanovic, in this thread, also points at atieventsd, so I decided to do some testing.

If I have atieventsd running, the X session will often freeze on logout. However, Linux itself doesn't crash, it's just the Xorg process that goes wild (which in many cases results in a feeling of total crash, but hey, this isn't Windows :)). It seems that some kind of event is dispatched when the session ends, so that atieventsd spawns the following script:

/bin/sh -c /etc/ati/authatieventsd.sh grant :0 (null)

I'm not 100% sure those are exactly the args that are passed, but something like it (don't have it in front of me, logged in from a different machine). It seems this is causing some nasty race in combination with xauth+Xorg, which causes Xorg to crash/freeze. The spawned script does not exit, and Xorg consumes 100% CPU. The ~/.Xauthority file is locked.

I was able to get the box back up on its feet from an SSH-session by:
- Killing atieventsd and the script it spawned
- Shut down gdm
- Killing Xorg with kill -9
- Removing fglrx kernel module, then reload it.
- Fire up gdm, and boom, Xorg comes back up with the GDM greeter.

Now, for the fix that worked for me:
Nuke atieventsd. Prevent it from starting up, kill it, etc. On Ubuntu, I just removed all startup symlinks from the /etc/rcX.d/ directories. You can also execute "/usr/sbin/update-rc.d -f atieventsd remove" (as root). Then reboot. If you want the startup links restored, just reinstall the fglrx-package ..

I've done 25 login/logout cycles in a row without atieventsd running, and Xorg has never frozen.

What's the point with this extra daemon, anyways ? Seems like kind-of a hack. If it's supposed to help with hotplug keys on laptops it has certainly never worked for me (Thinkpad Z61m). Those buttons have never worked. I always use aticonfig+xrandr. Also, I don't think the packaged version of fglrx that comes with Ubuntu Gutsy (8.37.6) enables this daemon. It's gone from my startup sequence, at least, until I hear official news from AMD that this buggy behaviour has been fixed.

Thanks to Ivanovic for the hint.

[DirtyHairy]

Hmmm, if atieventsd is the culprit, then I would wager that the driver is in fact locking up on switching powerstates which is performed by atieventsd (which reproducibly locks up my machine, see my post in the main thread). You might want to check this assertion by manually trying to switch powerstates via aticonfig...

As this happens on every switch for me only when Textured2D is enabled, this also would explain why meddling with the textured options seems to reduce the chance of locking up for some people.

If this is indeed correct, then disabling atieventsd (and possibly any related acpid scripts) would be a temporary fix, although not a very satisfactory one --- powersaving is no gimmick but vital for laptop users.

[oyvind]

Hmmm, if atieventsd is the culprit, then I would wager that the driver is in fact locking up on switching powerstates which is performed by atieventsd (which reproducibly locks up my machine, see my post in the main thread). You might want to check this assertion by manually trying to switch powerstates via aticonfig...

Ah, I forgot that that this was part of the daemon's purpose. In fact, I've disabled automatic VGA powerstate switching (configured in /etc/default/fglrx on Ubuntu). I remember I had problems with that (suspend/resume related IIRC). Got a large, fresh battery, instead :D.

Just for reference, I have an ATI X1400 mobile, and I can switch between all three powerstates without any problems, using aticonfig. But I do have the freeze-on-logout-problem when atieventsd is running. I cannot switch powerstates when driving two screens, but that's not an error according to aticonfig output.

But why would the daemon switch powerstate on logout, in the first place ?


As this happens on every switch for me only when Textured2D is enabled, this also would explain why meddling with the textured options seems to reduce the chance of locking up for some people.

Perhaps, yes, I fiddled with video options at first, but don't remember the reason I thought that helped. Also, Textured2D is not an official option, but a "secret" beta/alpha thing, right ? Wouldn't expect that to work very well, when there are so many other problems. I tried it, but didn't like the horrible tearing and flickering.


If this is indeed correct, then disabling atieventsd (and possibly any related acpid scripts) would be a temporary fix, although not a very satisfactory one --- powersaving is no gimmick but vital for laptop users.
Yeah, batteries suck. But I've never noticed a huge gain in battery life with VGA powerstate at its lowest level. Maybe because my graphics card isn't very powerful and a bit old, don't know.

[bridgman]

1) The content of /etc/ati/amdpcsdb does override whatever is defined in /etc/X11/xorg.conf. IMO this is a bug...

Good point. I just realized that earlier this morning. Forcing the options off in xorg.conf won't do anything if they are forced on in amdpcsdb. I believe the settings can be changed via aticonfig rather than having to edit amdpcsdb but haven't played with that myself.

Having said that, it's not clear if these options actually make a difference with the lockup, so I wouldn't bother playing with them for now.

[ivanovic]

Good point. I just realized that earlier this morning. Forcing the options off in xorg.conf won't do anything if they are forced on in amdpcsdb. I believe the settings can be changed via aticonfig rather than having to edit amdpcsdb but haven't played with that myself.
The problem is that *most* of those options are not available in amdccle. There only a *very* minor subset of the stuff that gets set is available. And since the xorg.conf is basically setup by an admin, what the admin says should be valued, that is those values should override whatever is set in amdpcsdb.


Having said that, it's not clear if these options actually make a difference with the lockup, so I wouldn't bother playing with them for now.

Right, looks like the overlay options do not really are the reason for the lockup.

It is really great to get some feedback directly from the people at AMD/ATI, a whole lot better than just "Hmm, can you hear me? Is there anybody around?". Thanks for answering posts here in the forums, bridgman.

[ig-88]

I turning off the overlay options in /etc/ati/amdpcsdb doesn't solve the problems for me.

[yoshi314]

i didn't restart my system after installing 8.1 so i guess the daemon didn't work at all. x locks up with a cursor on screen. mouse doesn't work, system is totally locked up.

i hate to test it, doing a hard reset each time. x300se card here.

at least it's nice to know that some people of ati/amd show up on forums and actually care. all this together makes me look into ati linux future with hope.

[linrunner]

Hi!

My conclusion after 2 days of googling, testing and fiddling with almost every option;):
the problem is somehow related to powerstate switching.

My system:
Thinkpad T60 (Model 2007-QPG)
X1400
Ubuntu 7.10 (Kernel 2.6.22-14.47)
Catalyst 8.1 installed according to
http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide

My test configuration to reproduce the problem:
/etc/X11/xorg.conf
Section "Device"
Identifier "Generic Video Card"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection

/etc/default/acpi-support (abbrev.)
SAVE_VBE_STATE=false
POST_VIDEO=false
USE_DPMS=true

/etc/default/acpi-support (abbrev.)
FGLRX_ACPI_SWITCH_POWERSTATES=true

Because i'm not using 3d most of the time i'm reducing power consumption with:
/etc/X11/gdm/PostLogin/Default
/usr/bin/aticonfig --set-powerstate=1

Reproducing the problem:
As long as I'm not using any 3d features in my X session I can logout/shutdown without hang.
As soon as I try to activate Compiz (which by the way doesn't work with the driver ... :confused:) or start fgl_glxgears, the following logout freezes the machine.

My current Workaround:
/etc/default/acpi-support
FGLRX_ACPI_SWITCH_POWERSTATES=false

Setting Option "NoDRI" in xorg.conf works too.

Hope it helps!

linrunner

[linrunner]

EDIT: double post.

[linrunner]

My conclusion was wrong: FGLRX_ACPI_SWITCH_POWERSTATES=false
is not an reliable workaround.

I either have to turn 3D off completely Option "NoDRI" or disable atieventsd.

linrunner>

[bridgman]

The problem is that *most* of those options are not available in amdccle. There only a *very* minor subset of the stuff that gets set is available. And since the xorg.conf is basically setup by an admin, what the admin says should be valued, that is those values should override whatever is set in amdpcsdb.

FY, I'm told that aticonfig can modify all of the settings in amdpcsdb, not just the ones supported by cccle.

[oyvind]

Hmmm, if atieventsd is the culprit, then I would wager that the driver is in fact locking up on switching powerstates which is performed by atieventsd (which reproducibly locks up my machine, see my post in the main thread). You might want to check this assertion by manually trying to switch powerstates via aticonfig...
<snip>


Not all automatic powerstate switching is done by this daemon. There is also an acpid control script in /etc/acpi/fglrx-powermode.sh, which is executed for lid and AC events. This will work even without the atieventsd daemon running ! I think the daemon is needed if you want throttling for thermal events or display hotplugging. I don't have overheating problems and don't care for automatic display hotplugging. Can anyone from AMD confirm this ?

So, without atieventsd running, I'm still successfully using automatic powerstate switching when I pull the AC plug or close/open the LID.

[mal13]

I have same poweroff/logout/switchuser problem.
Also if my x doesn't start correctly when i start my pc... and i let it stay there like for 5+ minutes it's stuck and hard reset is only way to restart.
As i asked elsewhere... do i really have to wait another month (at least) before this gets fixed???
Restaring from power button is bad for any os so hopefully this will be fixed....ASAP.

Kubuntu 7.10 w/ latest updates.
Ati 2400 pro pcie.

[legzelda]

After removing atieventsd, I can log out and restart X. However, if two or more users are simultaneously logged-in, my computer still "freezes" when logging out and restarting X on my system. I'm using a Dell E1505, X1400, Ubuntu 7.10.

[toxic-hero]

i also tried the suggested fix with disabled atieventsd daemon but had no luck. x still crashes on logout or ctrl-alt-bkspce. i killed atieventsd daemon a few times manually. it's also no difference if i'm logged in alone or there are two or more logged users.


i'm on:
hp compaq nx8220
ati mobility radeon x600
kubuntu gutsy 7.10
default kernel
catalyst 8.01 installed with envy


thanks for your work,

toxic

[BurnHead]

i also tried the suggested fix with disabled atieventsd daemon but had no luck. x still crashes on logout or ctrl-alt-bkspce. i killed atieventsd daemon a few times manually. it's also no difference if i'm logged in alone or there are two or more logged users.


I also tried that a few days ago - with no luck. But as I'm using Hardy Heron (Ubuntu 8.04) and the 8.01 drivers recently got included in the default repositories, I switched back to the fglrx driver packaged by the Ubuntu team. And to my very surprise everything works fine again now.
I don't know about the differences between the original AMD/ATI driver packages and the ones built by the Ubuntu devs though.

[ivanovic]

Over here on gentoo unstable everything works nicely with the atieventsd turned off. I have also turned on the overlay options again and had no more crashes. So for me the cause of the problems was atieventsd.

[zlatan]

Hm, my system locks up imediatly after starting X... with 8.1 and 7.12 driver on gutsy...
I don't know what is wrong.. kernel module built correctly via dkms and everything installs fine...
Xorg.0.log:

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu8.3)
Current Operating System: Linux speedZ 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686
Build Date: 18 January 2008
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Jan 26 19:40:52 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "SyncMaster"
(**) | |-->Device "Generic Video Card"
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.

This is where it halts completly... reset button is all there is left.
I'm I the only one experiencing this issue?... as i see all of You manage to start X... but have issues later.

[Swoopy]

Do you have an AGP based Radeon HD2x00 card, Zlatan?
What you describe seems common behaviour with fglrx right now, there have been many reports (including regarding my own Radeon HD2600XT AGP on a VIA K8T800Pro motherboard) that the current fglrx driver doesn't work for HD2x00-based AGP cards, at least not on many common VIA motherboard chipsets.
My system freezes, with a black screen for most incarnations of the fglrx driver, or with a partially drawn Ubuntu Gutsy 7.10 (64-bit) GDM login screen for version 8.433. Disabling direct rendering sometimes makes the driver work but slower than the open-source non-accelerated radeonhd driver which is what I'm currently using.

http://www.phoronix.com/scan.php?page=article&item=843&num=1

[zlatan]

heh... thanks for the info...

I'm actually using x1600pro AGP but i suppose it's the same issue.
RadeonHD gives me a green tinted screen(19" CRT)... probably because it lacks support for TV-out(PAL CRT TV) currently... unless the situation has improved recently...

EDIT: just tried it again(radeonHD)... still green... probably trying to run primary display at 50Hz :D And I really do not want to disconnect my TV all the time.

[israel_miranda]

Do you have an AGP based Radeon HD2x00 card, Zlatan?
What you describe seems common behaviour with fglrx right now, there have been many reports (including regarding my own Radeon HD2600XT AGP on a VIA K8T800Pro motherboard) that the current fglrx driver doesn't work for HD2x00-based AGP cards, at least not on many common VIA motherboard chipsets.
My system freezes, with a black screen for most incarnations of the fglrx driver, or with a partially drawn Ubuntu Gutsy 7.10 (64-bit) GDM login screen for version 8.433. Disabling direct rendering sometimes makes the driver work but slower than the open-source non-accelerated radeonhd driver which is what I'm currently using.

http://www.phoronix.com/scan.php?page=article&item=843&num=1

Swoopy, I seem to have the same problem you commented.
My system is:
Pentium 4 (Northwood) 2.6ghz HT
Motherboard Intel D865PERL
Saphire X700 AGP 256Mb (rialto chip)
19" CRT Monitor.
Kernel 2.6.22-3-686 (pre-compiled from backports.org)
Debian GNU/Linux 4.0 Etch (Stable)
Xorg 7.1.0-19


The system freezes when loading gdm. I see a partially loaded image, mostly blank.

I had the IRQ loading problem with 8.42 versions, wich is speciffically an AGP bug, wich partially worked but with a very
poor performance, fglx_gears very slow and compiz full of glitches(white titles, and after some minutes totally blank screen).

With the 7.11, 7.12 and 8.1 catalyst driver, my system totally freezes when loading gdm.
The strangest thing, is that there is NO ERROR in the logs, gdm log, Xorg log and even syslog log. The module loads flawlessly, I disabled the gdm startup and loaded the module manually, just loading the module doesn't freeze the system, but when gdm "uses" it the system freezes/lockup, I had posted this problem here before:
http://www.phoronix.com/forums/showthread.php?t=7228&highlight=x700
but the suggestion I had(lowering the agp aperture) didn't work.

It seems to me that the problem is still related to the IRQ assignment. Right after where would be the log error about the IRQ, the system freezes and there is no more lines in the log.

I thought this problem would be solved with a new driver release....

I'm very dissapointed with AMD/ATI. Nvidia is a year in advance, if we talk about driver support. They even support Freebsd, wich I'd like to use as well, but not without 3d acceleration.

Bridgman, I'd gladly join the AGP beta testers group, as someone said before here in the forums, I feel the AGP users are not well represented in the beta testers. How do I do that?

Swoopy, in your post above you posted a link to a how-to install the radeonhd driver. Do you mean that there is no solution to use the newest fglrx proprietary driver in agp cards?


I'm very upset with the support of the driver in the *nix systems. :(
If I don't get it working on the next driver release, I'll sell my ATI card, and buy a NVIDIA one. I can't wait anymore, AIGLX is out there for a year already. I'll also tell all of my friends who use linux to stay away from ATI cards..... I'd hate to do that, but here in Brazil, a lot of ppl still use AGP cards, the majority I'd dare to say, we don't change our hardware every year, my box is in good use for 5 years already. Many of my friends buy ATI cards because they are cheaper(at least here) and have a good hardware.

Just hope they can continue to do so, if ATI improve their linux driver in a short time.
The cost/benefit price/performance relationship on ATI cards, is excelent.
So should be their linux/freebsd drivers.

[phlegm]

Running
sudo /usr/sbin/update-rc.d -f atieventsd remove

fixed the hang on logout for me.