Announcement

Collapse
No announcement yet.

AMD Catalyst 8.5 For Linux

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

  • #91
    Originally posted by FreeBzH View Post
    Did anyone try with AGP cards ? like HD2400/2600 AGP
    Yes, finally my HD2400 agp is working, after so many months.
    Strange thing is that at login screen the resolution is wrong, after that it's correct. I'm on Ubuntu 8.04.

    Comment


    • #92
      Originally posted by jjjj View Post
      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
      I do get locks at logout! i experienced them with both gdm and slim.

      I'm going to try this.



      then i'd like bridgman to aswer me why:

      - my catalyst control center still displays version: 1.0 since a lot of releases.

      - most important: why it detects just 128MB of video ram (while i've got 512MB, checked it also under windows).

      - composite performance (not AIGLX) is so poor (my 9200se was a lot faster).

      - and if the change to the authatieventsd.sh does have effect, why killing Xorg it hangs! :-)

      i'm running a Mobility HD2600 (M76) with 512MB from laptop "Asus Pro31sa" on a 64bit system.

      thak's! :-)

      Comment


      • #93
        Originally posted by Wise Ferret View Post
        I have mobility radeon x1600 on 32-bit hardy, using gnome.
        Using 8.5 with compiz works beautifully, and indeed noticeably faster than 8.3. However, switching to metacity results quickly in an entire garbled screen, full of artifacts. Could this be the fault of my configuration? The relevant section in my xorg.conf is:

        Section "Device"
        Identifier "Generic Video Card"
        Boardname "ati"
        Busid "PCI:1:0:0"
        Driver "fglrx"
        Screen 0
        Option "XAANoOffscreenPixmaps" "on"
        Option "VideoOverlay" "off"
        Option "OpenGLOverlay" "off"
        Option "TexturedVideo" "on"
        Option "Textured2D" "on"
        Option "TexturedXrender" "on"
        Option "UseFastTLS" "1"
        EndSection
        Sounds like you should use Compiz then

        Seriously, first thing I would try is turning off TexturedXrender and then maybe Textured2D. I'm not 100% sure, but I believe both of those are work-in-process today and I expect Metacity would lean on TexturedXrender pretty hard.

        Originally posted by Vighy View Post
        - my catalyst control center still displays version: 1.0 since a lot of releases.
        I believe that refers to the framework version, not the detailed content of tabs & controls. Each of the components also has a (much larger) version number which gets bumped on every change but I don't think we display those externally.

        Originally posted by Vighy View Post
        - most important: why it detects just 128MB of video ram (while i've got 512MB, checked it also under windows).
        What I've been told is that this is the amount of memory which is mapped into the CPU address space and can be drawn into directly by the CPU; the rest is only accessible to the acceleration hardware. Not 100% sure but this seems to make sense; typically the largest value you see mapped is 256K. Since all of the stuff you see on the screen is either drawn by the acceleration hardware or blitted to the screen by the acceleration hardware it probably doesn't matter what this value is set to, as long as it is big enough to hold the actual front buffer displayed on the screen.

        Originally posted by Vighy View Post
        - composite performance (not AIGLX) is so poor (my 9200se was a lot faster).
        What exactly do you mean by composite performance here, and why do you say "not AIGLX" ? Under Compiz (are you using Compiz ?) I believe all of the compositing is done via AIGLX. If you are using Metacity and the TexturedXrender paths, those are still work-in-progress -- there seemed to be a huge preference for prioritizing AIGLX.

        Originally posted by Vighy View Post
        - and if the change to the authatieventsd.sh does have effect, why killing Xorg it hangs! :-)
        Honestly, there seems to be a huge list of things which cause driver-to-driver handoffs to hang and nowhere near enough standards or infrastructure to make sure it succeeds. This seems to be the most system-specific and kernel-specific aspect of the whole X driver space and success seems to be based in part on making the same design assumptions as all of the OTHER driver bits which bang on the same hardware. The issue with atieventsd.sh is only one of maybe a hundred different things that can cause hangs when switching between drivers. One day kernel modesetting will fix most of these problems; in the meantime there's just a lot of testing and tweaking to keep all the different bits of a Linux system roughly in sync.

        Originally posted by Vighy View Post
        i'm running a Mobility HD2600 (M76) with 512MB from laptop "Asus Pro31sa" on a 64bit system.
        Last edited by bridgman; 05-24-2008, 04:23 PM.

        Comment


        • #94
          @Bridgman:

          Seriously, first thing I would try is turning off TexturedXrender
          Hey John you just made my day man!!
          I set Texturedxrender to "off" and now screen is not getting grambled with the 2D Kwin manager at KDE 4!!

          So the solution guys is just set "off" TexturedXRender, Textured2D is OK to remain "on"!

          I will update my guide at Compiz-Fusion forum now!

          Always do the amdpcsdb trick after the change..., aticonfig --input=/etc/X11/xorg.conf --tls=1

          Comment


          • #95
            Artifacts in OpenOffice, GDM and Google Earth (at least)

            I know that this issue has been reported before but I think that this deserves another comment. I am running a Gentoo amd64 2007.1 system (to say so, but updated the system a couple of weeks ago), I have a Radeon X300, 1 GB RAM, an AMD Athlon 64 3000+, Gnome and Catalyst 8.5. I used to navigate with Google Earth and everything was absolutely fine as well as Open Office 2.4 and GDM 2.20.3. After I installed Catalyst 8.5 GDM appeared corrupted, which I found later to be an issue with Catalyst not detecting the monitor refresh rate properly at 1920*1200 or so, at least to my knowledge (which with 8.4 worked flawlessly) and the context buttons had some annoying artifacts (that look like shadowed text). The same applies to Open Office, which suffers the same problem with the buttons, the drop-down menus, the context messages and text (oddly, it does not affect the text one writes). Google Earth locks the system, seems to change screen resolution and the monitor turns off and the system stops responding, although the same happened with 8.4 (I noted that after reinstalling 8.4 to see what happened). Besides those things, video is running very well, and a general impression shows a solid work.

            Comment


            • #96
              Furthermore now with TexturedXrender "off" I take 175fps at RACER whereas before I scored 40fps and all the artifacts at 2D desktop...

              I definately believe that it is broken for 8.5 driver...

              Comment


              • #97
                Also Compiz-Fusion is even better now! Good work guys!

                Any idea when Crossfire will be ready??

                Comment


                • #98
                  @bridgman:
                  Hey John

                  I would have sent this to you in private but I couldn't so here's my message...

                  I would like to invite you to Compiz-Fusion forum and also I would like you to take a look at our guide there for a good ATI setup and help us a bit with your 'inside' knowledge and experience man...

                  Your help would be more than welcome not to say needed...

                  The forum thread locates here http://forum.compiz-fusion.org/showthread.php?t=6794

                  Truly Yours

                  Jim

                  Comment


                  • #99
                    Maybe Bridgman can answer this question :
                    What are the default settings used if the section device in xorg.conf is empty ? (except for Identifier and Driver entries )

                    Comment


                    • I always like your answers because are clear and precise.

                      Originally posted by bridgman View Post
                      What exactly do you mean by composite performance here, and why do you say "not AIGLX" ? Under Compiz (are you using Compiz ?) I believe all of the compositing is done via AIGLX. If you are using Metacity and the TexturedXrender paths, those are still work-in-progress -- there seemed to be a huge preference for prioritizing AIGLX.
                      I mean without compiz... using a compositor like the one integrated in xfce4. Changing workspace it takes a lot. While without compositing it's instantaneous. I can live without it, i just wanted to know if it was a know issue :-)

                      Originally posted by bridgman View Post
                      Honestly, there seems to be a huge list of things which cause driver-to-driver handoffs to hang and nowhere near enough standards or infrastructure to make sure it succeeds. This seems to be the most system-specific and kernel-specific aspect of the whole X driver space and success seems to be based in part on making the same design assumptions as all of the OTHER driver bits which bang on the same hardware. The issue with atieventsd.sh is only one of maybe a hundred different things that can cause hangs when switching between drivers. One day kernel modesetting will fix most of these problems; in the meantime there's just a lot of testing and tweaking to keep all the different bits of a Linux system roughly in sync.
                      Ok i solved the hang on logout. It was because I changed to slim lately (from gdm) and in the authatieventsd.sh there's no rule for slim.

                      I created it, how can i contribute? writing on the unofficial bugzilla could be a way?
                      If i propose the patch will be added on the next version (once fixed every possible problem.) ?

                      thank's again Bridgman! :-D

                      Comment


                      • Originally posted by Maxhysteria View Post
                        What are the default settings used if the section device in xorg.conf is empty ?
                        The whole idea of leaving the section empty is to get away from fixed settings. The driver code looks at the connected displays, compares them to whatever you had last time you ran, and makes an educated guess about how you want the displays configured this time.

                        The simplest and most common example is that if you had the same displays hooked up to the same connectors as last time, then the displays should be configured in the same way as you last set them.

                        Comment


                        • Luckily to me the new 8.5 is the best working driver yet, videos seems to run smooth 720p ones too.
                          Using Fedora 9 (downgraded Xorg from guide) everything else works great exept there is small spike in game like Warsow.
                          Every time in game some new weapon is used it loads either sound or something to memory and makes small spike (really small but matters), never noticed that before.
                          Not sure if its cause im trying ext4 fs or pulseaudio delays a bit or then the last cause might be Catalyst AI, turned it on and havent bothered trying it off. =p

                          And yes, 3d is working better than before assuming those spikes are over, the overall performance is really great, cant hardly believe it how smooth it feels and fast too (compared to windows side). =)

                          Hope we get next driver with some better compatibility to bleeding edge software. =)

                          EDIT: Yes it seems that Catalyst AI indeed causes that spike, most likely when new animation comes it loads it into memory somehow, turning Catalyst AI off takes spikes away in Warsow but gaming doesnt really feel as good as having the feature on.
                          Last edited by jasa68; 05-25-2008, 05:14 PM.

                          Comment


                          • Originally posted by bridgman View Post
                            Sounds like you should use Compiz then

                            I believe that refers to the framework version, not the detailed content of tabs & controls. Each of the components also has a (much larger) version number which gets bumped on every change but I don't think we display those externally.

                            What I've been told is that this is the amount of memory which is mapped into the CPU address space and can be drawn into directly by the CPU; the rest is only accessible to the acceleration hardware. Not 100% sure but this seems to make sense; typically the largest value you see mapped is 256K. Since all of the stuff you see on the screen is either drawn by the acceleration hardware or blitted to the screen by the acceleration hardware it probably doesn't matter what this value is set to, as long as it is big enough to hold the actual front buffer displayed on the screen.
                            ok i'm sorry but it's not true: as you can see where it says: video ram it says how much you have and not how much cpu mapped.

                            http://ati.cchtml.com/attachment.cgi?id=605
                            http://www.phoronix.net/image.php?id...md_v8600_fglrx

                            infact it show 1024MB for that card that's the firegl v8600 with 1GB of ram, while mine that should show 512MB it show 128MB.
                            On the unofficial bugzilla there's an open bug involving another HD2600 chip, but not M76.
                            http://ati.cchtml.com/show_bug.cgi?id=1037



                            Originally posted by bridgman View Post
                            Honestly, there seems to be a huge list of things which cause driver-to-driver handoffs to hang and nowhere near enough standards or infrastructure to make sure it succeeds. This seems to be the most system-specific and kernel-specific aspect of the whole X driver space and success seems to be based in part on making the same design assumptions as all of the OTHER driver bits which bang on the same hardware. The issue with atieventsd.sh is only one of maybe a hundred different things that can cause hangs when switching between drivers. One day kernel modesetting will fix most of these problems; in the meantime there's just a lot of testing and tweaking to keep all the different bits of a Linux system roughly in sync.
                            ok but the funny thing is that, after my added rule to authatieventsd.sh it's able to login and logout properly with slim. (you can get the lines of the rule here: http://ati.cchtml.com/show_bug.cgi?id=992#c36 ).
                            But as you could read there in the bugzilla, it still hangs if after a while i've logged in an worked for a bit of time, I try to logout, Xorg hangs.
                            It seems not modesetting related, because otherwise it should hang everytime, and i can sure you that it doesn't reach the moment to switch modesetting: it hangs before! so i think it's driver/xorg related.
                            to help you: xorg-server is 1.3.0.0-r5 from gentoo stock. and fglrx is 8.5

                            I really hope to NOT bother/annoy you, and to give you a hand to get rid of bugs/problems.

                            Thank's!

                            Comment


                            • I tried the <TexturedXrender "off"> with the 8.5 drivers.... but the artifacts in the icons didn't go away.
                              I reverted, again, to release 8.4.

                              I'm really curious about what could ever cause that visual corruption.........

                              Comment


                              • I installed brand new Debian/lenny amd64. Updated the kernel package to 2.6.24-1, because there was no headers for 2.6.22 (some kbuild depends missing).

                                When I start the X with fglrx driver, system hangs. Blank/black screen. No ping from outside.
                                uname -a
                                Code:
                                Linux korpus 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 GNU/Linux
                                xorg.conf (the buggy one, done by aticonfig --initial)
                                Code:
                                Section "ServerLayout"
                                        Identifier     "aticonfig-Layout[all]"
                                        Screen      0  "aticonfig-Screen[0]" 0 0
                                EndSection
                                
                                Section "Files"
                                EndSection
                                
                                Section "Module"
                                EndSection
                                
                                Section "InputDevice"
                                        Identifier  "Generic Keyboard"
                                        Driver      "kbd"
                                        Option      "XkbRules" "xorg"
                                        Option      "XkbModel" "pc104"
                                        Option      "XkbLayout" "us"
                                EndSection
                                
                                Section "InputDevice"
                                        Identifier  "Configured Mouse"
                                        Driver      "mouse"
                                EndSection
                                
                                Section "Monitor"
                                        Identifier   "Configured Monitor"
                                EndSection
                                
                                Section "Monitor"
                                        Identifier   "aticonfig-Monitor[0]"
                                        Option      "VendorName" "ATI Proprietary Driver"
                                        Option      "ModelName" "Generic Autodetecting Monitor"
                                        Option      "DPMS" "true"
                                EndSection
                                
                                Section "Device"
                                        Identifier  "Configured Video Device"
                                EndSection
                                
                                Section "Device"
                                        Identifier  "aticonfig-Device[0]"
                                        Driver      "fglrx"
                                EndSection
                                
                                Section "Screen"
                                        Identifier "Default Screen"
                                        Monitor    "Configured Monitor"
                                EndSection
                                
                                Section "Screen"
                                        Identifier "aticonfig-Screen[0]"
                                        Device     "aticonfig-Device[0]"
                                        Monitor    "aticonfig-Monitor[0]"
                                        DefaultDepth     24
                                        SubSection "Display"
                                                Viewport   0 0
                                                Depth     24
                                        EndSubSection
                                EndSection
                                Xorg.0.log.old
                                Code:
                                //Too long and cannot post it :(
                                I'm currently using radeon driver to write this post.
                                Any help is appreciated..

                                Specs:
                                CPU: Intel E6750
                                MB: Asus P5K (1006 BIOS version) (P35 Chipset + ICH9)
                                VC: Sapphire 2600 XT 256MB GDDR3

                                Thanks in advance.

                                Comment

                                Working...
                                X