Announcement

Collapse
No announcement yet.

AMD Catalyst 8.5 For Linux

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

  • #61
    d2kx said to
    ./ati-driver-installer-8-5-x86.x86_64.run --extract install

    add the patch to
    install/common/lib/modules/fglrx/build_mod/firegl_public.c

    ./ati-installer.sh 8.493 --buildpkg Debian/sid (as root)

    I'm confused, now, what patch to add to the file, since I hear that there are a couple of patches .

    The one I added either worked or I'm doing something wrong, but when I try to install fglrx-kernel-src and it says that it couldn't build the module or something like that, then doing 'modprobe fglrx' says that the module is not loaded.

    It's a 32 bit dual core system.

    Jesus, when are the fglrx developers going to this a lot easier?
    sundown
    Senior Member
    Last edited by sundown; 22 May 2008, 02:32 PM.

    Comment


    • #62
      Me too

      Originally posted by jjjj View Post
      This has to be the weirdest problem ever;

      sudo ./ati-driver-installer-8-5-x86.x86_64.run --buildpkg Ubuntu/hardy
      Created directory fglrx-install.br4952
      Verifying archive integrity... All good.
      Uncompressing ATI Proprietary Linux Driver-8.493............................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. ........
      ==================================================
      ATI Technologies Linux Driver Installer/Packager
      ==================================================
      Generating package: Ubuntu/hardy
      Resolving build dependencies...
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      E: Couldn't find package can't
      Unable to resolve can't parse dependency ooobasis30-en_us-res
      can't parse dependency ooobasis30-en_us-help
      can't parse dependency ooobasis30-en_us
      can't parse dependency ooobasis30-en_us-base
      can't parse dependency ooobasis30-en_us-math
      can't parse dependency ooobasis30-en_us-calc
      can't parse dependency ooobasis30-en_us-onlineupd
      can't parse dependency ooobasis30-en_us-impress
      can't parse dependency ooobasis30-en_us-draw
      can't parse dependency ooobasis30-en_us-writer. Please manually install and try again.
      Removing temporary directory: fglrx-install.br4952
      yeah i got the same thing, must be because of the force-architecture to install Ooo3 beta, anybody know why its happening and/or how to fix it?

      Comment


      • #63
        Get Rid of the Watermark

        There's an updated version of the driver on the site right now, ATI support just confirmed to me that there was a silent update for that last night. For those who have the flawed 8.5 installed already and are getting the watermark just download the installer again from ATI's site and then just extract the signature from the installer with

        grep -a signature= ati-driver-installer-8-5-x86.x86_64.run


        Then you'll get this:

        signature="8260783741db03d98508ca69a1795f0e:ba4e4c 0e72f633e1b53dfb5bc0546f38b652410502f6428dcc28fe59 99486f37:e0014c5275b833bcb23aac5f924a3a3fe0554b532 7b936bbe638ff5d971f6c36e0564d0575ea33ecb53aac5f954 b676ae1034a0f27be36e0bc31fe51971f6c39"

        Just copy the part between the quotation marks and put it into /etc/ati/signature overwriting the line that says UNSIGNED.

        I did this to fix the watermark on my Xubuntu Hardy 32Bit system and it works fine.

        Comment


        • #64
          Has anyone detected if using the authatieventsd.sh from the 8.5 package locks X on exit?

          Maybe this issue only affects Ubuntus, dunno.

          Here's diff with the patched file:
          --- /etc/ati/authatieventsd.sh 2008-04-11 22:20:43.000000000 +0300
          +++ /etc/ati/authatieventsd.sh.dpkg-new 2008-05-22 21:55:19.000000000 +0300
          @@ -34,9 +34,7 @@

          # Check xdm/kdm

          -# XDM_AUTH_MASK=/var/lib/xdm/authdir/authfiles/A$1*
          - XDM_AUTH_MASK=/var/run/xauth/A$1*
          -
          + XDM_AUTH_MASK=/var/lib/xdm/authdir/authfiles/A$1*
          XDM_AUTH_FILE=`ls -t $XDM_AUTH_MASK 2>/dev/null | head -n 1` # Choose the newest file
          if [ -n "$XDM_AUTH_FILE" ]; then
          SERVER_AUTH_FILE=$XDM_AUTH_FILE

          Comment


          • #65
            I'm using a Dell laptop with a X1400 Ati video card, updated Ubuntu Hardy, kde 3.5.9, self compiled QtCurve theme and Gtk-Qt.

            Today i installed the new 8.5 drivers, and after some time i reverted to the 8.4 ones, because i had some serious (and fastidious) visual artifacts in the icons in the kde tray.
            These artifacts seemed to increase with time.......
            I had never seen anything similar before, and going back to the 8.4 fixed it.......

            Anyone else has seen this? Is it a thing than can be solved?



            Greetings.

            Comment


            • #66
              I'me on Ubuntu 8.04 and I have install AMD Catalyst 8.5 with the automatic installer of the package. After, I have write the command line to configure xorg.conf:

              sudo aticonfig --initial -f

              After I have restart my computer. The computer restart and I'me on the deesktop. I see un picture "AMD Testing Use only, no 3D". When I go on CAtalyst control center I see that I'me on Mesa. On my xorg.conf driver "fglrx" is there so I think it's ok. What can I do to have the 3D?

              Comment


              • #67
                Originally posted by pierluc View Post
                What can I do to have the 3D?
                You can download the drivers again, because tonight they uploaded a new version, where the signature bug was corrected.

                Greetings.

                Comment


                • #68
                  Of course you need to dl a new file when you can patch it with one sed line Verify MD5 sum, it will match!

                  Before:
                  378ed98c6b8e30eba1614eb5f2ba0696 *ati-driver-installer-8-5-x86.x86_64.run

                  Fix:
                  Code:
                  signature="8260783741db03d98508ca69a1795f0e:ba4e4c0e72f633e1b53dfb5bc0546f38b652410502f6428dcc28fe5999486f37:e0014c5275b833bcb23aac5f924a3a3fe0554b5327b936bbe638ff5d971f6c36e0564d0575ea33ecb53aac5f954b676ae1034a0f27be36e0bc31fe51971f6c39"
                  sed -i 's/\(signature=\).*/\1"'$signature'"/' ati-driver-installer-8-5-x86.x86_64.run
                  After:
                  303a7c2c5a42f21cb92692cf77c83052 *ati-driver-installer-8-5-x86.x86_64.run

                  Comment


                  • #69
                    Originally posted by daniell View Post
                    Hi!

                    Anyone using the new driver with the latest 2.6.25.4 kernel? I can't get around compiling the kernel module

                    I am. No probs compiling the kernel module, though.

                    Comment


                    • #70
                      Originally posted by kudlaty View Post
                      Oh dear. The watermark is only a minor issue and Kano's hotfix worked for me (thanks, Kano!), but how did you guys compile the kernel module for 2.6.25?

                      When loading the module, all I get is "fglrx: Unknown symbol init_mm"?
                      The "real" fix for this beside hacking the code AMD/ATI provides is to export the required modules when building the kernel. As of kernel 2.6.25 several modules are seen as deprecated and meant to be removed very soon. Those are the ones which are seen as "just used by some binary drivers, they ain't really compatible with GPL anyway, so lets get rid of them". To have the driver work without changing anything in the driver itself, just activate this item in your kernel:
                      Code:
                      Symbol: UNUSED_SYMBOLS [=y]                                                                                     
                      Prompt: Enable unused/obsolete exported symbols                                                                 
                        Defined at lib/Kconfig.debug:42                                                                               
                        Location:                                                                                                     
                          -> Kernel hacking
                      Using it, there should not be a problem compiling and using the proprietary fglrx 8.5 driver with a 2.6.25.x kernel. But since it is likely that this feature will soon be removed from the kernel, AMD/ATI probably has to do something...

                      Comment

                      Working...
                      X