Announcement

Collapse
No announcement yet.

Catalyst 12-1 released

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Forage
    replied
    Originally posted by liam View Post
    Have you tried disabling all your plugins?
    If by plugins you mean Gnome extensions then yes. The problems occurred right after a complete clean install (not even preserving the home folder) without any extensions installed. I installed 3 non-intrusive ones much later so those aren't the cause.

    Originally posted by liam View Post
    If that doesn't work open a VT and sign in. Then run "pkill gnome-shell && gnome-shell --replace -d :0"
    Good one. Will try that.

    Originally posted by liam View Post
    What version of GS are you running, BTW?
    The latest from the Gnome 3 ppa, 3.2.2.1.

    Leave a comment:


  • liam
    replied
    Originally posted by Forage View Post
    I'm having the same issues ever since Ubuntu 11.10 with Gnome-Shell, not just with the latest drivers. I too have the latest updates from the Gnome 3 ppa, but that should not be the cause. The packages only received minor updates compared to Ubuntu's default.

    Have you tried disabling all your plugins?
    If that doesn't work open a VT and sign in. Then run "pkill gnome-shell && gnome-shell --replace -d :0"
    Then you can see what the errors were if it fails again.
    What version of GS are you running, BTW?

    Leave a comment:


  • Forage
    replied
    Originally posted by lakerssuperman View Post
    Having said that, I am experiencing random crashes with Gnome Shell which may be due to the fact that I am running the version from the Gnome 3 PPA.
    I'm having the same issues ever since Ubuntu 11.10 with Gnome-Shell, not just with the latest drivers. I too have the latest updates from the Gnome 3 ppa, but that should not be the cause. The packages only received minor updates compared to Ubuntu's default.

    Leave a comment:


  • chronniff
    replied
    I'm using this release on unity in ubuntu 11.10, and it definately seems snappier moving around the desktop.....couple of complaints, as always seems to be the case with this driver; xv video is taking a big nosedive on my system (I'm using a 5770) stuttering during playback is significant and very disappointin. The stuttering happened in the last release, but unredirecting the video from the compiz buffer almost always fixed it, sadly this is not the case anymore. Using gl for the video gets fixed by unredirecting, however if I'm watching videos that are 720p and above seems to cause a bug that prevents me from ever getting back to the desktop after awhile. Also, has anyone else had severe lag issues when scrolling in any maximized browser (chrome(ium) or firefox) in the past several releases? This may be specific to unity, but it is extremely annoying....in chromium I can enable the experimental "GPU compositing on all pages" flag and it mostly fixes it, however since it is an experimental setting once in a while it causes frustrating rendering errors (I'm using the dev build btw).

    Other than those problems is seems like a decent release as far as catalyst goes, other than the bugs which I don't expect to be fixed for several months knowing these developers. I really wish someone smarter than myself would finally fix the dynamic power management in the open source driver to a point that it was somewhere on par with catalyst. Whenever that happens I would gladly walk away from this blob forever.

    Leave a comment:


  • rockmanz
    replied
    Originally posted by lakerssuperman View Post
    The "export CLUTTER_VBLANK=none" option works very nicely to speed up Gnome Shell window movement. Having said that, I am experiencing random crashes with Gnome Shell which may be due to the fact that I am running the version from the Gnome 3 PPA. Otherwise it's pretty stable.

    The one issue I still is that the driver still incorrectly detects my LCD TV as a projector and won't let me adjust overscan. This is really annoying and should be something that is addressed as the Fusion hardware is ideally suited for HTPC and tv applications.
    Have you tried:
    sudo aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0

    Leave a comment:


  • lakerssuperman
    replied
    The "export CLUTTER_VBLANK=none" option works very nicely to speed up Gnome Shell window movement. Having said that, I am experiencing random crashes with Gnome Shell which may be due to the fact that I am running the version from the Gnome 3 PPA. Otherwise it's pretty stable.

    The one issue I still is that the driver still incorrectly detects my LCD TV as a projector and won't let me adjust overscan. This is really annoying and should be something that is addressed as the Fusion hardware is ideally suited for HTPC and tv applications.

    Leave a comment:


  • Kodama
    replied
    here's my experience with catalyst 12.1.

    I'm running Arch Linux with an HD 6950.
    With xorg-server 1.11.3 and Catalyst 12.1. X crashes and sends you back to login-screen when watching videos due to a broken xv output. This makes video editing (kdenlive), video-chat (skype) and playing videos in mplayer impossible.
    Flash videos in fullscreen lag, stutter and even freeze.
    This also was the case in Catalyst 11.11 and 11.12. I have no idea why AMD doesn't fix these serious issues.
    The only workaround is to downgrade to xorg-server 1.10.4. Everything works fine there.

    Since I use awesome as my window manager I can't say anything about gnome3 performance though.
    Other Arch users report the same thing: https://aur.archlinux.org/packages.php?ID=29111

    Hopefully the next version of catalyst will finally fix these issues.

    Leave a comment:


  • Kano
    replied
    Must be a joke or? 64 bit win has compat libs for 32 bit of course, so you need everything twice. Just not the kernel part of the drivers, but the userspace one. Thats why the 64 bit install images are bigger than the 32 bit ones by a huge amount. Thats not because of slightly bigger executeables. But 16 bit support was dropped on 64 bit win.

    Leave a comment:


  • kraftman
    replied
    Originally posted by wsnipex View Post
    I'm wondering why it is so hard to make a pure 64bit driver.
    This not only still depends on 32bit libs, but now it even needs libstdc++6:i386 to build on x86_64
    +1

    Why do we have to install 32bit libraries to use the driver on 64bit system? Is this the case on 64bit Windows, too?

    Leave a comment:


  • Smotko
    replied
    Originally posted by yaji View Post
    Add "export CLUTTER_VBLANK=none" to your .profile file (home folder).
    This fixed my issue, thank you!

    Leave a comment:

Working...
X