Xorg update seems to break ATI Catalyst

Hi all
Just a quick note for users of the proprietary ATI Catalyst driver, the latest Xorg update seems to break it (at least on my system).
Boot sequence proceeds as normal until GDM loads, then the screen oscillates slowly between black and white.
Any suggested fix?

Hi there
Did Pacman upgrade your kernel alongside Xorg?. Maybe you need to rebuild the fglrx module.
Best of Luck

Similar Messages

  • [SOLVED] ATI Catalyst / Xorg issue with Multihead (3monitor)

    i'm having problems for a long time, with different versions of the ATI Catalyst driver and Xorg,
    right now i'm using this versions,
    catalyst-hook 11.2-2
    catalyst-utils 11.2-1
    lib32-catalyst-utils 11.2-1
    xorg-server 1.9.4.901-1
    xorg-server-common 1.9.4.901-1
    xorg-server-utils 7.6-2
    the catalyst package are from the catalyst server recommended by the Arch Wiki
    http://catalyst.apocalypsus.net/repo/catalyst/x86_64
    the problem that i have is that when i try to pass from one monitor to another, when
    i pass to the 3rd one the X crashes, this happen always with the same monitor no matter what.
    here is the backtrace from the startx logs,
    Backtrace:
    0: /usr/bin/X (xorg_backtrace+0x28) [0x49f788]
    1: /usr/bin/X (0x400000+0x60349) [0x460349]
    2: /lib/libpthread.so.0 (0x7f28028b7000+0xf150) [0x7f28028c6150]
    3: /usr/lib/xorg/modules/drivers/fglrx_drv.so (0x7f27fecf4000+0x86ffff) [0x7f27ff563fff]
    4: /usr/lib/xorg/modules/drivers/fglrx_drv.so (0x7f27fecf4000+0x86fb5d) [0x7f27ff563b5d]
    5: /usr/bin/X (0x400000+0x13bce2) [0x53bce2]
    6: /usr/bin/X (0x400000+0x13be31) [0x53be31]
    7: /usr/bin/X (0x400000+0x13a880) [0x53a880]
    8: /usr/bin/X (miPointerUpdateSprite+0x18c) [0x45871c]
    9: /usr/bin/X (0x400000+0x5892d) [0x45892d]
    10: /usr/bin/X (0x400000+0x164266) [0x564266]
    11: /usr/bin/X (mieqProcessDeviceEvent+0x172) [0x49ef52]
    12: /usr/bin/X (mieqProcessInputEvents+0xcc) [0x49f08c]
    13: /usr/bin/X (ProcessInputEvents+0x9) [0x469969]
    14: /usr/bin/X (0x400000+0x2cf73) [0x42cf73]
    15: /usr/bin/X (0x400000+0x2131e) [0x42131e]
    16: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f2801837dcd]
    17: /usr/bin/X (0x400000+0x20ec9) [0x420ec9]
    Segmentation fault at address (nil)
    Fatal server error:
    Caught signal 11 (Segmentation fault). Server aborting
    i wanted to know if there is any official forum / bug tracker  of amd/ati where report this bug,
    or if one of you had this kind of problem before and can give me a hand to resolve this, i would be grateful.
    here is the ati report about the system info,
    http://pastebin.com/jU73mU4W
    http://ideone.com/mcISC
    thanks in advance.
    regards.
    Last edited by hord (2011-07-10 20:26:12)

    solved!
    since the cursor used through the proprietary catalyst driver have issues, use instead the SW cursor,
    Section "Device"
    Option "SWCursor" "true"
    EndSection
    [0] http://ati.cchtml.com/show_bug.cgi?id=86
    [1] http://ati.cchtml.com/show_bug.cgi?id=117
    [2] http://phoronix.com/forums/showthread.p … post209030
    Last edited by hord (2011-07-10 20:25:23)

  • Arch linux doesn't boot after installing AMD ATI Catalyst

    I have a laptop which has a integrated graphic card intel 4th generation (4600) and an AMD ATI R9 m265x (hybrid Intel/AMD graphics card) so I have just installed AMD ATI Catalyst proprietary ones by following
    AMD Catalyst ArchWiki.
    I have used "Installing from the unofficial repository" method so in my pacman.conf I have added below entry for [catalyst-stable]:
    [catalyst-stable]
    Server = http://catalyst.wirephire.com/repo/catalyst/$arch
    ## Mirrors, if the primary server does not work or is too slow:
    #Server = http://70.239.162.206/catalyst-mirror/repo/catalyst/$arch
    #Server = http://mirror.rts-informatique.fr/archlinux-catalyst/repo/catalyst/$arch
    #Server = http://mirror.hactar.bz/Vi0L0/catalyst/$arch
    Then I have update pacman's database and install below packages:
    catalyst-hook
    catalyst-utils-pxp
    lib32-catalyst-utils-pxp
    (No need to install catalyst-total-pxp as I have installed catalyst-utils-pxp)
    After installing it, I have configured the driver, configuring X using below command:
    # aticonfig --initial
    In order to use PowerXpress support I have installed catalyst-utils-pxp package plus additional lib32-catalyst-utils-pxp.
    To perform a switch into Intel's IGP I have also installed the mesa-libgl  package and Intel's drivers: xf86-video-intel  and intel-dri .
    I have enable the automatic update by enabling the catalyst-hook.service with below commands since it automatically rebuilds the fglrx modules while the system shuts down or reboots (so I haven't to do it manually each time kernel is updated using Catalyst-generator):
    # systemctl enable catalyst-hook
    # systemctl start catalyst-hook
    And finally I have blacklisted radeon module by creating "/etc/modprobe.d/blacklisted.conf" file which content is:
    blacklist radeon
    and also I have ensured that fglrx line is added in "/etc/modules-load.d/Catalyst.conf" file.
    To avoid problems, I have rebuilt the fglrx module by doing (I know it is not necessary as it is done by catalyst-hook):
    catalyst_build_module all
    Once I reboot, arch linux does not boot. Last lines printed out are below and then it freezes:
    Starting temp files linker to catalyst...
    Starting Catalyst event Daemon...
    [ OK ] Started Catalyst event Daemon
    Starting Catalyst's fglrx kernel' module builder...
    [ OK ] Started temp files linker for catalyst.
    [ OK ] Started Catalyst's fglrx kernel' modue builder.
    [ OK ] Started gnome Display manager.
    [ OK ] Started Network manager.
    [ OK ] Reached target Multi-User system.
    [ OK ] Reached target Graphical Interface.
    [ OK ] Reached target Network.
    I have tried to put nomodeset as a kernel parameter but it does not work. Also, after reading ArchWiki, I have noticed that it is recommended to don't do this as I am using catalyst-utils-pxp because intel driver needs it so I have removed nomodeset parameter from kernel but It continues not working.
    Any ideas?
    Package versions:
    Kernel version 3.17.6-1-ARCH
    catalyst-hook 14.12-1
    catalyst-utils-pxp 14.12-1
    lib32-catalyst-utils-pxp 14.12-1
    xorg-server 1.16.2.901-1
    xf86-video-intel 2.99.916-3
    Last edited by toni (2014-12-13 19:38:38)

    FInally I managed to boot arch linux.
    I had to downgrade xorg-server from 1.16.2.901-1 to 1.15.2-1.
    It seems there is a problem with Catalyst 14.12-1 and xorg-server 1.16.2.901-1.
    Also I had to replace desktop manager from gdm to lightdm as gdm raises segmentation faults using xorg-server versions 1.16.2.901-1 and 1.15.2-1.
    Finally I had to add an entry in pacman.conf:
    [xorg115]
    Server = http://catalyst.wirephire.com/repo/xorg115/$arch
    ## Mirrors, if the primary server does not work or is too slow:
    #Server = http://mirror.rts-informatique.fr/archlinux-catalyst/repo/xorg115/$arch
    #Server = http://mirror.hactar.bz/Vi0L0/xorg115/$arch
    Then performs following actions:
    1)  # pacman -Syuu catalyst-hook catalyst-utils-pxp
    2) Uninstall all the packages xf86* such as xf86-video-intel, xf86-input-evdev,  xf86-input-synaptics, etc.
    3) Install the packages uninstalled in step 2 and install them again using xorg115 repo, for example, # pacman -S xorg115/xf86-video-intel xorg115/xf86-input-evdev xorg115/xf86-input-synaptics
    I have put a comment here.
    Last edited by toni (2014-12-14 12:31:29)

  • [Solved] Screen lockup since xorg 1.6.3-4 upgrade (catalyst)

    Hey there,
    since i yesterday upgradet my system (pacman -Syu) and pacman installed a new xorg-server version (from 1.6.3-3 to 1.6.3-4) and xf86-inpud-evdev my screen gets completely locked up after i start GDM. Only thing that helps is to press the reset button.
    Now i went back to the radeonhd driver wich works quiet well so far.
    Does anyone know what this could be?
    xorg.conf for catalyst:
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "extmod"
    Load "dbe"
    Load "xtrap"
    Load "record"
    Load "dri"
    Load "glx"
    Load "GLcore"
    Load "freetype"
    EndSection
    Section "ServerFlags"
    Option "DontZap" "false"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "evdev"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "fglrx"
    VendorName "ATI Technologies Inc"
    BusID "PCI:1:0:0"
    # Option "RenderAccel" "on"
    # Option "EnablePageFlip" "on"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "DRI"
    Mode 0666
    EndSection
    This one worked until yesterday.
    I tried to reinstall catalyst several times but it didnt help.
    Thank you for your help
    Marcel
    Last edited by jack_slayton (2009-08-27 14:40:40)

    I have the same problem everytime an update releated to xorg is released. Only reinstalling catalyst doesn't is, but recompiling and installing new(er) catalyst(-utils) packages solves the problem - at least on my pc. Maybe this works for you too.

  • AutoUpdate/Ati Catalyst Broken!

    AutoUpdate/Ati Catalyst Broken!? When using AutoUpdate here are some things I had to do to get it working:
    ) installed standard Creative drivers for my X-FI Titanium 2.7.007
    it worked
    2)? installed ATI Catalyst 9.0
    it stopped working.
    3) by mistake I let Windows Update install its WHQL Creative driver
    AutoUpdate started working
    used the other shortcut for AutoUpdateA.exe to get updates for Creative products in windows 7 64, and it worked everytime to reinstall the Creative 2.7.007
    4) three weeks later I installed Catalyst 9.2 drivers, and immediately after reboot, AutoUpdate is broken.
    Windows 7 Action Center reports errors with Creative AutoUpdate.
    If I delete Creative drivers using CTZAPP, Windows Update upon reboot will install its own update to Creative's drivers......... I reinstall Creative 2.7.007 and Creative AutoUpdate still works.
    5) installed ATI Catalyst and it is broken again. The Catalyst installation breaks it everytime. Reinstalling Windows Update version of Creative drivers, uninstalling those and installing Creative's several times usually fixes AutoUpdate. Within a few days, Autoupdate will be broken.
    Anybody else have the issue with Catalyst 9.0 to 9.2 and Creative AutoUpdate?
    Keep in mind, this is not my "new cause" of the week. I just did a clean format a week or so ago, and I am trying to duplicate the problems others are having with AutoUpdate. About 40-45% of users have ATI cards I would guess and I am trying to figure out if this is a common thing with about half of the Creative users. We install Creative drivers and go along for a few weeks, as many people always say, and then something goes wrong.......A new Catalyst is released about once a month or every six weeks.

    #Re: AutoUpdate/Ati Catalyst Broken!B <div class="lia">"" try and just uninstall the CCC (Catalyst Control Center) and not the actual video drivers. Its the CCC (the little red "ATI" box in your task manager on the lower right) that is causing this problem. You will still have accelerated video with the drivers installed but not the special ATI utility to configure them. Use the built-in Windows 7 advanced graphics utility when you right click on the desktop (right-click and choose "Screen Resolution"). Inside that window is a link called "Advanced settings" which will let you do the same functions as the CCC does without the CCC's interference.
    I hope this hel
    ps.
    Well this is not a good solution as you will loose advanced settings for your graphic card.

  • ATI Catalyst 8.5 Proprietary Linux Display Driver released

    New ATI Catalyst™ 8.5 Proprietary Linux Display Driver was released the day before yesterday and according to release notes it has many improvements.
    New Features
    This release of the Catalyst™ Linux software driver introduces Mipmap Detail, Catalyst A.I., and AA Filters in the 3D ORCA page of the Catalyst™ Control Center Linux Edition.
    Resolved Issues
    * The following section provide a brief description of resolved issues with the latest version of the ATI Catalyst™ Linux software suite. These include:
    * Support for video playback on the second head in dual head mode is now available. Further details can be found in topic number 737-26985
    * Unresolved symbols in Xorg log under RHEL 4u6 32 and 64 bit no longer occur. Further details can be found in topic number 737-34284
    * The desktop background color is no longer displayed incorrectly when using xcommgr. Further details can be found in topic number 737-34285
    * Change VT no longer fails when kernel module is not loaded. Further details can be found in topic number 737-34286
    * Switching to the virtual terminal multiple times no longer results in X displaying corruption. Further details can be found in topic number 737-34287
    * Catalyst Control Center: The Preference page is now localized for all supported languages. Further details can be found in topic number 737-34275
    * The Linux kernel module is no longer installed to wrong location if the Linux kernel is updated. Further details can be found in topic number 737-34288
    * Random system hangs no longer occur when calls to the ATI driver are made from Ring3. Further details can be found in topic number 737-34289
    * X window no longer fails to respond when GoogleEarth is maximized. Further details can be found in topic number 737-34290
    * A segmentation fault no longer occurs when running SPECViewperf on systems containing an ATI FireGL V5100 series product and running SUSE 10.3 x86. Further details can be found in topic number 737-34276
    * Enabling Composite extension no longer displays 8x AA for graphic cards that do not support 8x AA under the Ubuntu 7.10 operating system. Further details can be found in topic number 737-34291
    * Display corruption is no longer noticed at logon when compiz is enabled. Further details can be found in topic number 737-34292
    * Launching the glxgears application no longer results in segmentation faults. Further details can be found in topic number 737-34293
    * GoogleEarth: Launching the application in horizontal mode on a system running X no longer results in corruption being noticed. Further details can be found in topic number 737-34293
    * Specviewperf 8.1 64 bit version: Segmentation faults no longer occurs on IGP systems. Further details can be found in topic number 737-34294
    * Maya 2008: Moving the render window no longer results in the operating system failing. Further details can be found in topic number 737-34295
    * Glxgears corruption is no longer noticed in big desktop mode. Further details can be found in topic number 737-34296
    Known Issues
    * The following section provides a brief description of known issues associated with the latest version of ATI Catalyst™ Linux software suite. These issues include:
    * Desktop corruption may be noticed when dragging the overlay/video when using dual-display mode. Further details can be found in topic number 737-29578
    * Bandwidth corruption may be noticed when setting the desktop resolution to 2048x1536 on systems containing an ATI Radeon HD 3200 series of product. Further details can be found in topic number 737-33499
    * SECAM, NTSC or PAL signal changes when using aticonfig or Catalyst Control Center but does not apply to the TV display output. Further details can be found in topic number 737-34297
    * Running X server without a window manager may result in the X server flashing green for a moment, going black, and the computer becoming unresponsive. Further details can be found in topic number 737-34299
    * Desktop corruption may be noticed when dragging the overlay/video when using dual-display mode. Further details can be found in topic number 737-34298
    * Connecting a CRT display device to a system containing an ATI Mobility Radeon X1600 product may result in the display device flashing multiple times or failing to display an image when attempting to launch the Catalyst Control Center. Further details can be found in topic number 737-34300
    * Corruption may be noticed when connecting a DFP display device to a system running X after setting the TV mode to 1080i. Further details can be found in topic number 737-34301
    * Quake 3 Arena (demo): Segmentation faults may occur when attempting to play the game. Further details can be found in topic number 737-34302
    * Specviewperf: Launching the application may result in the Linux operating system failing to respond. Further details can be found in topic number 737-34282
    * Opening a terminal and running semi-automated DPPT tests via lnxtest.sh may result in the operating system failing to respond. Further details can be found in topic number 737-34283
    * A segmentation fault may occur when running SPECViewperf on systems containing an ATI FireGL V5100 series product and running SUSE 10.3 x86. Further details can be found in topic number 737-34319
    * FGL_GLXGEARS or GLXGEARS: X may fail to respond when launching either of the applications. Further details can be found in topic number 737-34316
    * Maya 2008: Various comparison failures may be noticed. Further details can be found in topic number 737-34277
    * The X Server may fail to reset clearly when AIGLX is enabled. Further details can be found in topic number 737-34317
    * DiscoveryStudio1.7: The print preview and save as functions may fail to work properly. Further details can be found in topic number 737-34278
    * SPEC Viewperf 8.1: A performance drop may be noticed when running the application under Linux. Further details can be found in topic number 737-34279
    * Maya2008: The hardware render buffer may fail to render/display the image. Further details can be found in topic number 737-34280
    * May2008: The hardware render Perl script may display an error message when rendering. Further details can be found in topic number 737-34281
    I wonder when it will appear in Arch's repositories

    Yea, it would be great as at Phoronix forums some people are reporting 10% performance increase in games
    EDIT: Some release notes from AMD
    New Features
    This release of the Catalyst™ Linux software driver introduces UYVY and YUY2 pixel format support. This support provides interleaved stream support for video playback applications such as TVTime and MythTV.
    Resolved Issues
    The following section provide a brief description of resolved issues with the latest version of the ATI Catalyst™ Linux software suite. These include:
    *Enemy Territory: Quake Wars: Playing the demo on a system running X no longer results in corruption being noticed. Further details can be found in topic number 737-35208
    *Maya 2008: An incorrect colormap is no longer displayed for texture selector on systems running X. Further details can be found in topic number 737-35207
    *Quake 3 Arena (demo): Segmentation faults no longer occur when attempting to play the game. Further details can be found in topic number 737-35206
    *Quake3: Corruption is no longer noticed when changing the display resolution when the game is running. Further details can be found in topic number 737-35209
    *SECAM, NTSC or PAL signal changes when using aticonfig or Catalyst Control Center and now gets applied to the TV display output. Further details can be found in topic number 737-34297
    *Running X server without a window manager no longer results in the X server flashing green for a moment, going black, and the computer becoming unresponsive. Further details can be found in topic number 737-34299
    *Corruption is no longer noticed when connecting a DFP display device to a system running X after setting the TV mode to 1080i. Further details can be found in topic number 737-34301
    *Clock Gating is now supported and enable under the Linux operating system. Further details can be found in topic number 737-35191
    *The desktop background color is no longer displayed incorrectly when using xcommgr. Further details can be found in topic number 737-35192
    *Using the wrong delimiter in aticonfig --set-dispattrib=<disp>,<attr>, <value> no longer results in a segmentation fault. Further details can be found in topic number 737-35194
    *Audio out is now functioning after the installation of the ATI graphics drivers for Ubuntu 7.10. Further details can be found in topic number 737-35196
    *Bandwidth corruption is no longer noticed when setting the desktop resolution to 2048x1536 on systems containing an ATI Radeon HD 3200 series of product. Further details can be found in topic number 737-33499
    *Playing a video clip using mplayer with the Xv extension enabled no longer results in an error indicating that Xv could not find a free Xv port. Further details can be found in topic number 737-35198
    *Corruption is no longer noticed when enabling Big Desktop on systems containing an ATI FireGL X1 series of product and running X. Further details can be found in topic number 737-35199
    *Running the X server generations test no longer results in the operating system failing to respond or a Kernel panic to occur after first server generation on SuSE 10.3 64 bit. Further details can be found in topic number 737-35200
    *Attempting to resize a 2D application window no longer results in poor performance being noticed when composing is enabled. Further details can be found in topic number 737-35201
    *Screen flicker is no longer noticed after running amdcccle in X. Further details can be found in topic number 737-35202
    *Corruption is no longer noticed when connecting a DFP display device to a system running X after setting the TV mode to 1080i. Further details can be found in topic number 737-35203
    *Glxgears corruption is no longer noticed in big desktop mode. Further details can be found in topic number 737-35204
    *Starting glxgears and/or fgl_glxgears no longer results in the gears failing to render on SuSE 10.2 x86_64. Further details can be found in topic number 737-35205
    *FGL_GLXGEARS or GLXGEARS: X no longer fails to respond when launching either of the applications. Further details can be found in topic number 737-35210
    Known Issues
    The following section provides a brief description of known issues associated with the latest version of ATI Catalyst™ Linux software suite. These issues include:
    *DiscoveryStudio1.7: The print preview and save as functions may fail to work properly. Further details can be found in topic number 737-35219
    *Desktop corruption may be noticed when dragging the overlay/video when using dual-display mode. Further details can be found in topic number 737-29578
    *Bandwidth corruption may be noticed when setting the desktop resolution to 2048x1536 on systems containing an ATI *Radeon HD 3200 series of product. Further details can be found in topic number 737-33499
    *Connecting a CRT display device to a system containing an ATI Mobility Radeon X1600 product may result in the display device flashing multiple times or failing to display an image when attempting to launch the Catalyst Control Center. Further details can be found in topic number 737-34300
    *DiscoveryStudio1.7: The print preview and save as functions may fail to work properly. Further details can be found in topic number 737-34278
    *Setting the Overscan to an invalid value may result in segmentation faults. Further details can be found in topic number 737-35211
    *An incorrect error message may be returned when applying an unsupported TV geometry in a console terminal. Further details can be found in topic number 737-35212
    *Desktop corruption may be noticed when dragging the overlay/video when using dual-display mode. Further details can be found in topic number 737-35213
    *An X segmentation fault may occur when launching SUZI/textured video. Further details can be found in topic number 737-35214
    *Creating two successive connections may result in direct GL context to fail. Further details can be found in topic number 737-35215
    *Moving the mouse or tapping a key may fail to close an OpenGL screen-saver and bring the user back to the x desktop. Further details can be found in topic number 737-35216
    *The X Server may fail to reset clearly when AIGLX is enabled. Further details can be found in topic number 737-35217
    *Opening a terminal and running semiautomated DPPT tests via lnxtest.sh may result in the operating system failing to respond. Further details can be found in topic number 737-35218
    Last edited by Zibi1981 (2008-06-19 15:42:23)

  • ATI Catalyst 12.6 Released - Early Results

    I have updated my Windows 7 x64 workstation, equipped with VisionTek ATI Radeon HD 5670, to use the new ATI Catalyst 12.6 release, just out.  I upgraded from their last stable release, 12.2.
    http://support.amd.com/us/gpudownload/windows/Pages/radeonaiw_vista64.aspx
    Early indications, with just a few hours testing, are that the GPU-enhanced features of Photoshop CS6 x64 appear to work OK with this ATI driver version:
    I've been able to enable use of the Graphics Processor in Advanced mode, as with 12.2.
    I've been able to enable OpenCL and it appears to stay enabled.
    Liquify works well and it appears fast.
    Oil Paint works well and fast, though there's a slight flicker when panning the image.
    The new blurs (e.g., Iris Blur) work well and fast.
    Animated zooms are smooth.
    Painting with various brushes, including bristle and mixer brushes, seems just about as quick as with earlier driver versions.
    No change to the prior slow performance of the Smudge Tool with larger brushes. That may be a Photoshop issue.
    Accelerated color-management (Normal and Advanced GPU modes) appears to work the same as before.  No change to the inaccuracy issue with documents in the ProPhoto RGB profile.
    New Problems Discovered
    I now see a minor new transparency glitch, as reported by others in the thread below, where I did not see this problem with Catalyst 12.2:  http://forums.adobe.com/message/4530588#4530588
    Questionable Things With Workarounds (Geek Stuff):
    The driver insists on putting a couple of things in front of the system PATH on installation that are absolutely not needed, and worse, can cause problems on a development system (e.g., with Visual Studio).  These can be removed without downside I can see.
    The installer sets a registry value that causes the recording of a whole bunch of extraneous events in the System Event Log.  This can be undone by setting this value:
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Atierecord]
    "eRecordEnable"=dword:00000000
    Recommendations:
    Keep in mind I only updated to this version of the driver earlier today, so I haven't got a lot of experience with it yet.  Early indications are that it's not bad, but if you're already on Catalyst 12.2 and you have a stable system, I see no reason to upgrade. 
    The new version does not appear to be faster, and there is the one new issue where there's a slight transparency glitch in 16 bits/channel documents showing on the screen after a canvas rotation.
    I'll update this thread if I find more things to report.  Given the new transparency issue and the fact that I had no problems with 12.2, I'll probably test with 12.6 for a few days then drop back to 12.2.
    -Noel

    You're very welcome, folks.  Thanks for taking the time to send your thoughts, and for your contributions here as well.
    I've logged one full day of hard use including Photoshop and many other tasks, and I've seen zero glitches (outside the one I mentioned above, which is pretty minor) with the Catalyst 12.6 release.
    -Noel

  • AMD/ATI Catalyst 7.12 Released

    7.12 Release Notes wrote:
    New Features
    This release of the ATI Catalyst™ Linux driver introduces support for the following new operating systems:
        * Red Flag DT 6.0 Support
        * OpenSUSE 10.3 support
    Resolved Issues
    The following section provide a brief description of resolved issues with the latest version of the ATI Catalyst™ Linux software suite. These include:
        * A memory leak is no longer noticed when running OpenGL applications
        * Running X -configure no longer results in a segmentation fault in the fglrx driver
        * fglrxinfo no longer reports OpenGL Render string: as Mesa GLX Indirect on systems containing an ATI Rialto AGP series of product
    Known Issues
    The following section provides a brief description of known issues associated with the latest version of ATI Catalyst™ Linux software suite. These issues include:
        * There is no support for video playback on the second head in dual head mode. Further details can be found in topic number 737-26985
        * Desktop corruption may be noticed when dragging the overlay/video when using dual-display mode. Further details can be found in topic number 737-29578
        * A black screen may be observed on some hardware when switching to the console or leaving the X window system when a Vesa framebuffer console driver is used. Further details can be found in topic number 737-30687
        * Corruption may be noticed in the lower right corner of the display after the system is running for a long period of time
        * Display flicker may be noticed when the gnome screen-saver starts
        * Diagonal tearing may be noticed when playing a video file using a video player that utilizes the XVideo extension
        * Video playback may look blocky when playing a video file using a video player that utilizes the XVideo extension
        * Video Playback may display wrong colors and additional shadow images when cropping or expanding a video file using a video player that utilizes the XVideo extension
        * Connecting a display device that supports 1680x1050 to a system running Linux may result in a maximum display resolution of 1280x1024 only being available
        * Custom mode lines in xorg.conf may be ignored by the fglrx driver
        * Building RPM packages for Mandriva may fail
    Of other note, apparently the libGL soname issue that we devs have noticed with the catalyst-utils package should be fixed.
    I'm building packages now - once you get them, feel free to post your experiences.
    Last edited by Cerebral (2007-12-21 00:41:17)

    robbel wrote:
    thayer wrote:Oy... interestingly enough, after upgrading and restarting X I've lost my native resolution of 1680*1050.  xrandr --query reports the new max as 1280*1024.  Reverting both catalyst and catalyst-utils restores the proper resolution. For the record, I have an ATI Radeon Mobility X1400.
    Hey,
    I have exactly the same problem (Radeon 9700 Mobility here). My native resolution is 1400x1050 and it used to work just fine but the newest driver maxes out at 1280x1024 (as reported by xrandr).
    Shame ATI can't write drivers.
    Thanks for posting the old packages.
    Best,
    Philipp
    Me too. Normally I use 1440x900 resolution, but after updating, my resolution is totally wrong. Thanks for the packages!
    Last edited by LinuxPatsku (2007-12-21 10:00:16)

  • [SOLVED] xorg update has broken nvidia-173xx driver

    Hi,
    I've been using arch for around 2 and a half months on 2 computers (a dell Inspiron 2200 and an old home built pc). So far I've been able to figure out most things myself.  However, following today's xorg update x seems to be broken. My laptop, which does not use nvidia, seems to be fine. On the pc i installed the i686 version and am running kde 4.5.1
    I have reinstalled nvidia-173xx and nvidia-173xx-utils, and run nvidia-xconfig but this has not helped any.
    Although the installation is carried out there is an error stating:
    ERROR: Module nvidia does not exist in /proc/modules In order to use the new nvidia driver, exit xserver and unload it manually
    A google search on the above error didn't advance me any further, either.
    I have also waited for today's kernel update but that hasn't seemed to fix things.
    If I run "startkde" i get an error message stating that it can't connect to the x server.
    "startx" says much the same only more verbose.
    /var/log/Xorg.0.log has the following information :
    dlopen: /usr/lib/xorg/modules/drivers/nvidia_dvr.so undefined sym$
    failed to load /usr/lib/xorg/modules/drivers/nvidia_dvr.so
    unloadable module "nvidia"
    failed to load module "nvidia" (loader failed, 7)
    I've done a lot of esearch but can't find any solutions to my issue. The following thread seems to be related :
    https://bbs.archlinux.org/viewtopic.php?id=103716
    but i can't seem to find an answer there either.
    Any help would be appreciated.
    Cheers
    Last edited by rabid_works (2010-09-29 19:32:42)

    ok, went to downgrade using
    #pacman -U ...
    but i have yet another error due to a conflict between files :
    xorg-server: /usr/lib/xorg/protocol.txt is already present in the file system
              xorg-server: /usr/share/man/Xserver.1.gz is already present on the file system
              xorg-server; /usr/share/xkb/README.compiled is afready present in the file system
    is it possible to safely force the installation?
    sorry if thatś a lazy question but I've been looking at this for so long that i can't fathom the idea of futher searching.
    EDIT: ok, i had a break and realised it'd be safer to simply rename and the delete the problematic files. The downgrade went fine. I have X back.
    thanks for the help.
    Last edited by rabid_works (2010-09-29 18:52:27)

  • XFCE Keyboard Layout applet not working after latest xorg update..

    Is this a bug in the xorg update or most the kbd layou be reompiled or? I am not able to swtich between my two kbd layouts anymore.. Downgrading the org packages made it work again but I guess that's not a long term solution...
    Regards,
    BTJ

    Hi mattywix - can you add any more detail please ?
    I have a recent experience that sounds related to your problem - I have a 15" macbook pro bought new in the UK a couple of years ago (macbookpro 5,3), which has been running perfectly under snow leopard until a couple of days ago when my trackpad stopped recognising the standard "left" click.
    "Right" click, scroll and pointer movement continued to work fine.
    Booting in safe mode seemed to give me back the left click but this was immediately lost when I returned to standard boot up.
    Doing a full reinstall from original disks, all seemed fine. Over 1.6Gb of software updates and everything worked great. Then the final run of S/W update took me from os-x 10.6.6 to 10.6.7 plus a few other changes and again the trackpad stopped recognising "left" click.
    Plugging in an external drive which had a copy of my system as at OS-X 10.6.3 and booting off that - everything works fine again.
    I can only conclude that there's an issue with the 10.6.7 upgrade and my 2 year old MBP hardware so will have to reinstall yet again but stop at 10.6.6
    My concern is that after the first upgrade to 10.6.7 I put the laptop on charge to top it up from about 70% and came back to find the machine abnormally hot. With your comment about toasting the logic board, I wonder if there's a bug in the power control software too which I was lucky enough to catch before my machine suffered the same damage as yours ?
    Sorry to hear about your bad luck but thanks for warning us about it.
    Alick

  • Can't install ATI Catalyst

    Hate to ask for help, but can't find anything from google.  Also sorry if this is the wrong place to post it.  Anywho, I'm having trouble installing ATI Catalyst.  When I installed Arch I installed the oss drivers, but I can't play any resource heavy games (like Urban Terror).  If there's another way o fix it without installing Catalyst, that's cool to.
    Anyway, when I do pacman -S catalyst I get:
    resolving dependencies...
    looking for inter-conflicts...
    :: catalyst-utils conflicts with libgl. Remove libgl? [Y/n] y
    error: failed to prepare transaction (could not satisfy dependencies)
    :: ati-dri: requires libgl>=7.2
    I'm not exactly sure how I should take care of that.  Do I need to remove everything installed by the OS driver or what?

    Alright so I think I've got it good. 
    http://crunchbanglinux.org/pastebin/176 - xorg.conf
    I removed libgl and xf86-video-ati, thats all the OS driver comes with, right?  Tryin' to make sure I have everything cleaned up. ;o

  • ATI Catalyst /displays/properties/graphics controller

    First, I have successfully installed my ATI video card and have downloaded all of the needed updated drivers.
    However, I am receiving the following warning message: The ATI Catalyst Control Center is not supported by the
    driver version of my enabled graphics adapter the ( Intel(R) 82845G/GL/GE/PE/GV) graphics controller. It goes on to say please update your ATI graphics driver. Or enable your ATI using the displays manager which, is located in the "ATI Catalyst Control Center".
    I've gone to the ATI Catalyst Control Center. There I find basic and advanced settings. I tried using the basic step by
    step easy set up wizard, and quick settings. I could not get past step one on either one. This wizard told me it was to convert a video file to a differn't video format. My question is would converting a video file to a differn't video format fix the driver version and graphics adapter? Or do I maybe need to install a differn't graphics adapter/controller?

    Please stay with your other post.
    HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
    HP Photosmart Premium C309G, HP Photosmart 6520
    HP Touchpad, HP Chromebook 11
    Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
    Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
    Windows 7/8 UEFI/Legacy mode, MBR/GPT

  • ATI Catalyst 9.2 and "Incompatible display adapter has been disabled."

    Hi,
    I have this issue... on 3 GPUs. Only one is working.  2 x 3870x2 in crossfire / Vista x64 SP1
    I tried everything possible : uninstall all ATI software before, clean registry, delete files, temporary files, many uninstall and reboots, trying different settings in BIOS . Same issue.
    This time I choose to install 9.2 drivers only (without Control Center), but the result is the same.
    The problem appears since v8.11, but I was able to install at the end by cleaning / reinstalling many times.
    v8.12, v9.1, v9.2 are impossible to install correctly on my system. I'm very disapointed.
    I've been waiting about 6 month for 8.10 to have stable drivers...
    Maybe installing ATI drivers should be proposed to Olympic Games category...
    I asked to ATI if they have a tool to clean all previous drivers, and they suggested this link :
    https://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&questionID=1447
    Look at the utility cat-uninstaller.exe date : 10/08/2003 !!!
    It's possible that the problem comes from old drivers, but I refuse to format / reinstall the system each time ATI release a new driver. I did that for 8.12 and I had the same issue.
    For users who have this problem : OPEN A TICKET TO ATI CUSTOMER CARE !!!
    http://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&questionID=31625
    That's the olny way to solve this issue.
    My system below :
    AMD Phenom 9950 BE / Sunbeam Core-Contact Freezer / ASUS M3A32-MVP DELUXE-WIFI-AP (AMD 790FX/SB600 - BIOS v1406) / OCZ Reaper HPC Edition 8Go ( 4*2Go ) PC8500 1066MHz Cas 5-5-5-18 / Quad CrossfireX : dual MSI R3870X2-T2D1G-OC - ATI Catalyst 8.11 / RAID0 : 2x Samsung - Spinpoint F1 - 320 Go 7200 rpm SATA II 16 Mo cache / PSU : Thermaltake - TOUGHPOWER 1200W / VISTA x64 SP1

    I did tests on my second system :
    System 2 :
    AMD Athlon X2 6400+ / ASUS M3A79-T Deluxe (AMD 790FX/SB750) / 8GB DDR2 800MHz Corsair Doninator / RAID0 2x Samsung 200 Go SATA II
    CrossfireX : 2x MSI RX3870-T2D512E-OC (v120 + v803) / ATI Catalyst 9.1 / Cooler Master Real Power M620 (620W/efficiency >80%) / VISTA x64 SP1
    On this system :
    Catalyst 9.1 working and Crysis Warhead too
    Catalyst 9.2 installation is OK, but :
        - Crysis Warhead hang at 85% when a level is loaded
        - Crysis v1.2.1 load correctly, but hang after 1 minute
        - I noticed that when I lanch CPU-Z 0.3.2 I have on "Bus Interface"
            -card 1 : PCI-E x16 2.0@ x16 2.0
            -card 2 : PCI-E x16 2.0@ x16          (in catalyst 8.10, both are @2.0)
    Uninstall 9.2 and visual c++ x64, reboot, install 9.1 => 2 x GPU disabled error 43 !!!
    Going back to 8.10 : it's the last working stable revision from MSI.
    For users who use MSI Live update, and drivers from MSI : what are the last ATI Catalyst revision drivers furbished by MSI ?
    I would like to have feedback (vista x64, crossfirex).
    Thanks

  • ATI Catalyst 13.3 beta 2 Poisonous to Photoshop CS6

    Last night I installed the new ATI Catalyst 13.3 beta 2 driver.  The 13.2 betas had worked seemingly okay.  But with 13.3 beta 2, Photoshop CS6 13.1.2 crashes in Advanced mode when any document is opened...
       Faulting application name: Photoshop.exe, version: 13.1.2.0, time stamp: 0x50e86765
    Faulting module name: atio6axx.dll, version: 6.14.10.12172, time stamp: 0x51423773
    Exception code: 0xc0000094
    Fault offset: 0x000000000118a67f
    Faulting process id: 0x186c
    Faulting application start time: 0x01ce232bdf156c88
    Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Photoshop.exe
    Faulting module path: C:\Windows\system32\atio6axx.dll
    Report Id: 2676a2f8-8f1f-11e2-bb85-005056c00008
    I'm still trying things, to see if there are workarounds, or modes in which it works, but for now, my advice:
    Avoid installing Catalyst 13.3 beta 2.
    I'll follow up here when I learn more.
    -Noel

    One manifestation of this new driver version is that Photoshop CS6 now thinks there is an insane amount of VRAM...
    This is a problem that showed up in Catalyst 12.10 and persisted through 13.1, then was miraculously solved in 13.2 betas.  Now it has returned.
    And from what I've been able to see during testing, it crashes Photoshop in all GPU accelerated modes, not just Advanced.
    Here's what sniffer_gpu reports:
    C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)>sniffer_gpu
    Device: 000000000029A888 has video RAM(MB): 2048
    Device: 000000000029A888 has video RAM(MB): 2048
    Vendor string:    ATI Technologies Inc.
    Renderer string:  AMD Radeon HD 7800 Series
    Version string:   3.0.12172 Compatibility Profile Context 12.100.17.0
    OpenGL version as determined by Extensionator...
    OpenGL Version 3.0
    Has NPOT support: TRUE
    Has Framebuffer Object Extension support: TRUE
    OpenGL ok
    OpenCL ok, version=1.2 AMD-APP (1124.2)
    Return code: 3
    After a crash I see this:
    Adobe Photoshop Version: 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00) x64
    Operating System: Windows 7 64-bit
    Version: 6.1 Service Pack 1
    System architecture: Intel CPU Family:6, Model:12, Stepping:2 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
    Physical processor count: 12
    Logical processor count: 24
    Processor speed: 3458 MHz
    Built-in memory: 49150 MB
    Free memory: 43300 MB
    Memory available to Photoshop: 44751 MB
    Memory used by Photoshop: 95 %
    Image tile size: 1024K
    Image cache levels: 2
    Photoshop crashed on 3/17/2013 at 1:06:00 PM (AllocateSharedGLResources)
    OpenGL Drawing: Disabled.
    OpenGL Drawing Mode: Advanced
    OpenGL Allow Normal Mode: True.
    OpenGL Allow Advanced Mode: True.
    OpenGL Allow Old GPUs: Not Detected.
    OpenCL Version: 1.2 AMD-APP (1124.2)
    OpenGL Version: 3.0
    Video Rect Texture Size: 16384
    OpenGL Memory: 2048 MB
    Video Card Vendor: ATI Technologies Inc.
    Video Card Renderer: AMD Radeon HD 7800 Series
    Display: 2
    Display Bounds: top=0, left=1600, bottom=1200, right=3200
    Display: 1
    Display Bounds: top=0, left=0, bottom=1200, right=1600
    Video Card Number: 2
    Video Card: Radmin Mirror Driver V3
    Driver Version: 3.1.0.0
    Driver Date: 20070808000000.000000-000
    Video Card Driver:
    Video Mode: 1600 x 1200 x 4294967296 colors
    Video Card Caption: Radmin Mirror Driver V3
    Video Card Memory: 0 MB
    Video Card Number: 1
    Video Card: AMD Radeon HD 7800 Series
    Driver Version: 12.100.17.0
    Driver Date: 20130314000000.000000-000
    Video Card Driver: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.d ll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
    Video Mode: 1600 x 1200 x 4294967296 colors
    Video Card Caption: AMD Radeon HD 7800 Series
    Video Card Memory: 2048 MB
    A complete reset of all preferences makes no difference - Photoshop still crashes with any GPU mode.
    It also crashes Photoshop CS5. 
    -Noel

  • Does firmware update 7.1 break the Airport Extreme Base Station?

    Does firmware update 7.1 break the Airport Extreme Base Station?
    See Digg
    http://www.jayhaynes.net/2007/04/donot_install.html
    April 10, 2007
    Do NOT install AirPort 802.11n Firmware 7.1
    This Firmware 7.1 update for AirPort Extreme Base Station with 802.11n should definitely NOT be installed.
    Here was my problem:
    I used AirPort Utility 5.1 to install the update. It is automatic - launch the utility and it asks if you want to install the update. I said yes because I had problems getting two AirPort n base stations networking together to extend my range (I gave up finally and just used an AirPort Express to extend the range).
    After the firmware update, some sites would not load at all (www.nytimes.com) and others took forever to load. And worse, I could not send any email from any of my IMAP accounts. It seemed to be a DNS problem.
    I have two 802.11n AirPorts, so I finally went back to the other one (7.0) and everything worked fine. The Apple tech support guy offered to replace my broken (7.1) AirPort.
    Foolishly, I wanted to make sure the problem was actually with the 7.1 update and not the AirPort itself. So I updated my second 802.11n base station with 7.1. And it casued the exact same problem (some sites not loading, no outgoing email).
    The Apple tech (at this point I was speaking with a wireless specialist) put me on hold to test a few of his AirPorts to see if he could revert back to firmware 7.0 or (ii) install a clean version of 7.1 (in case the version on my drive was corrupted).
    Unfotunately neither option was possible, which is a design flaw in AirPort Utility.
    Apple is sending me two new AirPorts in 1-2 days, which is great service, but I will not be installing firmware update 7.1 again. Fool me once...
    http://www.apple.com/support/downloads/airportextremebasestationwith80211nfirmwa re71.html
    AirPort Extreme Base Station    

    Turns out that the firmware 7.1 does not render the AEBS useless.
    My problem was resolved when I turned off my DSL modem, the AEBS and the computer. Then restarted in same order going to the next one after the first is compeletly up and running. I had no problems whatsoever after that.
    Seems that the firmware update makes the IPs 'stick' somehow. I would think that even a reset of AEBS might have done it but I never got to that stage.
    All my computers came alive in no time.
    I suggest Smith tries this. Simply reset the whole network. Ah yes, my cable modem has an internal battery, I needed to disconnect this too. Only then did the modem go into the 'acquiring' or 'distribution' mode.

Maybe you are looking for