Announcement

Collapse
No announcement yet.

AMD Releases New Catalyst Linux Legacy Driver

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

  • #16
    Originally posted by e8hffff View Post
    How stupid. Such a big company as AMD/ATI and they put a transparent image on your screen. Why not put a warning in the control centre, rather then mes sup someone's screen if they're forced to use the beta drivers.
    "Mess up the screen"? "Forced to use the beta drivers"? What?!?

    Comment


    • #17
      When you forget the bad 12-6 drivers, then this one is at least in two points better:

      a) no libpciaccess bug
      b) kernel 3.4 support (not 3.5), but only tested 64 bit right now

      some things i would do for packaging:

      a) use control file from 12-4 driver as pci-ids are identical
      b) add a signature
      c) patch amdpcsdb.default to enable

      HWUVD_H264Level51Support=V1

      d) update xvba-va-driver with h264 l5.1 support patch

      maybe somebody could post a patch for kernel 3.5 support, thats what i still need...

      Comment


      • #18
        I've playing Diablo on my Lenovo W500 (with a Radeon HD 3650 and Catalyst 12.4 driver). After installing this driver the system hangs after logging in to the game and I must do a hard reset. I'll do more testing later to make sure the problem persists, but the only change was that I installed the new drivers. For this reason (and the dumb screen overlay) I'll very likely be reverting to the old driver version.

        Comment


        • #19
          just save /etc/ati/control + signature and copy it back later.

          Comment


          • #20
            Moved to the open driver a long time ago. Use it 24/7 now. Could not care less about "legacy" drivers.

            Comment


            • #21
              Originally posted by joshuapurcell View Post
              I've playing Diablo on my Lenovo W500 (with a Radeon HD 3650 and Catalyst 12.4 driver). After installing this driver the system hangs after logging in to the game and I must do a hard reset. I'll do more testing later to make sure the problem persists, but the only change was that I installed the new drivers. For this reason (and the dumb screen overlay) I'll very likely be reverting to the old driver version.
              Looks like the driver is working now for playing Diablo... not sure why it didn't work to begin with. I did re-run the following command (but I didn't see any obvious changes with the xorg.conf):
              Code:
              amdconfig --initial

              Comment

              Working...
              X