Announcement

Collapse
No announcement yet.

GLAMOR'ized Radeon Driver Shows Hope Over EXA

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

  • #31
    Originally posted by jrch2k8 View Post
    ArchLinux/gentoo

    phenom II 965 / FX6100
    Radeon HD rv710 4350 / HD7700 cape verde
    Kde 4.11.2
    Glamor + XV forced
    kernel 3.11.3/3.12-rc3

    Kwin settings

    render Raster
    Opengl Version 3.1 / 2.0

    i don't have any issues even with this crappy gpu or RadeonSI, so i assume must be an gpu specific issue or distro specific because i cannot reproduce it in any of my radeon machines
    I guess it's radeonsi specific (I can't reproduce it with Intel HD 4000). Hopefully a mesa bug will be easier to track down but unfortunately developers don't seem interested in KDE related bugs

    Edit: what the fuck, HD7700 IS radeonsi! Can you please make a simple test? Open konsole with HD7700 and mesa git, type something (alot of characters) and then delete them. Do you see any lag?
    Last edited by darkbasic; 10-04-2013, 10:36 AM.
    ## VGA ##
    AMD: X1950XTX, HD3870, HD5870
    Intel: GMA45, HD3000 (Core i5 2500K)

    Comment


    • #32
      Meanwhile, I have two Radeon HD 6850s and one Radeon HD 7950 running with open source drivers / glamoregl from the oibaf ppa and there are no bugs/crashes in regards to desktop rendering with Unity, but the RadeonSI support is abysmall in regards to performance in games (supposing you can get them to run in the first place) in comparison to Catalyst. If you are using RadeonSI, it's best to use Catalyst 13.8 Beta, although I haven't tried Catalyst 13.10 because it didn't look very enthusiastic for a release two months after 13.8's massive changes.

      Comment


      • #33
        On the contrary I noticed VERY good performance with games, I got 121 fps in Xonotic 1080p High quality and 102 fps in Openarena 0.8.8 1080p with radeonsi (HD 7950).
        It's a lot considering KDE is completely unusable.
        ## VGA ##
        AMD: X1950XTX, HD3870, HD5870
        Intel: GMA45, HD3000 (Core i5 2500K)

        Comment


        • #34
          Originally posted by darkbasic View Post
          On the contrary I noticed VERY good performance with games, I got 121 fps in Xonotic 1080p High quality and 102 fps in Openarena 0.8.8 1080p with radeonsi (HD 7950).
          It's a lot considering KDE is completely unusable.
          I would be pretty embarassed if I had that much FPS in those two games when I get over 300FPS in a game like TF2 and CSGO in Windows.

          Comment


          • #35
            Originally posted by mmstick View Post
            I would be pretty embarassed if I had that much FPS in those two games when I get over 300FPS in a game like TF2 and CSGO in Windows.
            Hey, did you forget glxgears barely worked just a few months ago?
            ## VGA ##
            AMD: X1950XTX, HD3870, HD5870
            Intel: GMA45, HD3000 (Core i5 2500K)

            Comment


            • #36
              Originally posted by JS987 View Post
              Intel SNA isn't really compared.
              You are forgetting the that sna also heavily targets intel's very powerful simd engine, and not just upto sse2 but, I believe, even up to avx2.
              That results in a pretty big difference even if sna isn't making use of the blt engine, or the 3d pipeline for non-trivial transforms (color space, rotation/stretch, etc).

              Comment


              • #37
                Close, but no cigar

                I tried Glamor again with better results than last time, maybe. Runs ok, but with software rendering "feel". Only visual bug is that the cursor is maybe a 75-100px square dot cloud. But, it's not clear if it's really even running.

                Xorg.0.log shows that glamoregl module loads, but there are no more glamor-related messages after that. Then, exa module loads, followed by a few exa init messages, then R600G prints a "Useful debugging info follows" section, which is not normally there.

                Does this make sense to anyone? Surely they shouldn't both be loading. Do I need to physically configure EXA out of Mesa?

                Any help is much appreciated. It's got to be close!

                Config: Radeon HD 4650 AGP, r600g driver, kernel 3.12-rc3, all built from current Git, on Slackware-current.

                Comment


                • #38
                  Originally posted by pa2708 View Post
                  I tried Glamor again with better results than last time, maybe. Runs ok, but with software rendering "feel". Only visual bug is that the cursor is maybe a 75-100px square dot cloud. But, it's not clear if it's really even running.

                  Xorg.0.log shows that glamoregl module loads, but there are no more glamor-related messages after that. Then, exa module loads, followed by a few exa init messages, then R600G prints a "Useful debugging info follows" section, which is not normally there.

                  Does this make sense to anyone? Surely they shouldn't both be loading. Do I need to physically configure EXA out of Mesa?

                  Any help is much appreciated. It's got to be close!

                  Config: Radeon HD 4650 AGP, r600g driver, kernel 3.12-rc3, all built from current Git, on Slackware-current.
                  If exa initializes then you dont use glamor. You dont need to I had this issue when, even having built and configured everything correctly, exa was used. I dont know exactly the reason for it, but i removed some leftover (from previous compiles) xaa related .so files from the xorg modules directory and then it worked.
                  Also, make sure you build (in this order):

                  -mesa with (these are required): --enable-gbm, --with-egl-platforms=x11,drm. Dont use --enable-xaa.
                  -glamor (xv is optional, but as some applications may require it, it is highly advised) with --enable-glx-tls --enable-xv
                  -xf86-ati

                  As xv support is just got in glamor, i advise using the git versions for the above.

                  Also, make sure you have either an xorg.conf that has both the "module" and "device" sections, or have the glamor.conf in /usr/share/X11/xorg.conf.d/ (or wherever your distro needs it) with the "module" section and xorg.conf with the "device" section. I found that for some reason if i put everything in glamor.conf, after reboot it was missing the "device" section.

                  If it works, you should have something like this:

                  Code:
                  $ cat /var/log/Xorg.0.log | grep -i glamor
                  [    21.900] (II) LoadModule: "glamoregl"
                  [    21.931] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
                  [    22.124] (II) Module glamoregl: vendor="X.Org Foundation"
                  [    22.375] (**) RADEON(0): Option "AccelMethod" "glamor"
                  [    22.375] (II) Loading sub module "glamoregl"
                  [    22.375] (II) LoadModule: "glamoregl"
                  [    22.376] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
                  [    22.376] (II) Module glamoregl: vendor="X.Org Foundation"
                  [    22.376] (II) glamor: OpenGL accelerated X.org driver based.
                  [    23.918] (II) glamor: EGL version 1.4 (DRI2):
                  [    23.964] (II) RADEON(0): glamor detected, initialising EGL layer.
                  [    24.910] (II) RADEON(0): Use GLAMOR acceleration.
                  [    24.910] (II) RADEON(0): Set up textured video (glamor)
                  [    24.910] (II) RADEON(0): [XvMC] Associated with GLAMOR Textured Video.

                  Comment


                  • #39
                    Originally posted by gradinaruvasile View Post
                    If exa initializes then you dont use glamor. You dont need to I had this issue when, even having built and configured everything correctly, exa was used. I dont know exactly the reason for it, but i removed some leftover (from previous compiles) xaa related .so files from the xorg modules directory and then it worked.
                    Also, make sure you build (in this order):
                    Thanks for the hints Grad! The packages and build order were ok. The placement of options between xorg.conf and glamor.conf, though, seems to be really touchy. After a few iterations with that (ending up with everything in xorg.conf, and an empty glamor.conf since I believe one has to be present), glamor now initializes, but there's a segfault in r600_dri.so before the display comes up. Should be able to track that down from the stack dump. One step closer!

                    Comment


                    • #40
                      Originally posted by darkbasic View Post
                      Edit: what the fuck, HD7700 IS radeonsi! Can you please make a simple test? Open konsole with HD7700 and mesa git, type something (alot of characters) and then delete them. Do you see any lag?
                      i did and it works as expected with 0 delay, here those are my setting http://www.imagebam.com/image/ef359c279882336 <-- this is from my radeonsi card with glamoregl with whole graphic stack on git[mesa/libpciaccess/libdrm/pixman/cairo/galmoregl/kmscon/etc] on gentoo

                      update: is the same in my 4850x2,4350 cards which r600g with glamor forced on archlinux
                      Last edited by jrch2k8; 10-05-2013, 09:10 PM.

                      Comment


                      • #41
                        Originally posted by pa2708 View Post
                        Thanks for the hints Grad! The packages and build order were ok. The placement of options between xorg.conf and glamor.conf, though, seems to be really touchy. After a few iterations with that (ending up with everything in xorg.conf, and an empty glamor.conf since I believe one has to be present), glamor now initializes, but there's a segfault in r600_dri.so before the display comes up. Should be able to track that down from the stack dump. One step closer!
                        I had a crashing issue too. In my case i found it was caused by the presence of the /usr/lib/x86_64-linux-gnu/egl/egl_gallium.so library, put there by a system package installed by default (it showed up in the xorg log's segfault message). It seems it had some disagreements with my build of mesa as i didnt build mesa with --enable-egl. Removing the library or building mesa with --enable-egl fixed this issue.

                        Comment


                        • #42
                          The stack dump showed that the crash was happening in sb, the optional shader optimizer. Started X with R600_DEBUG=nosb and everything came up!

                          The X display came up slowly (a couple minutes), and individual windows take some time (10-20 seconds?) to start, but within a given window performance was quite reasonable. Text scrolling in xterm with an antialiased font is the fastest I've ever seen, 3.4 seconds for ls -lR in a directory tree with 27K files/directories.

                          Moving windows around is glass-smooth, except that motion is frozen for around half a second anytime the moved window overlaps another window or the edge of the screen. No visual corruption of any kind.

                          Overall, it's not ready to be enabled permanently (on my rig), but it shows lots of promise. Best of all, it seems to be under active development again. Will give it another shot in a few months or if a major upgrade is made.

                          Comment


                          • #43
                            On the 7560D there isnt much of a speed or visual difference vs exa (it ISNT FASTER though). Or anything for that matter, except the minor bugs i mentioned with transparent tray icons etc. Moving windows, scrolling, opening windows seems to be pretty much the same on xfce 4.10. Also, it seems that is uses less CPU% for mundane tasks like painting ordinary windows, scrolling in Seamonkey etc (this is a highly subjective observation though).

                            Comment


                            • #44
                              Originally posted by pa2708 View Post
                              The stack dump showed that the crash was happening in sb,
                              If its the same one, then it looks like it got squished: https://bugs.freedesktop.org/show_bug.cgi?id=70088

                              Comment


                              • #45
                                Originally posted by oibaf View Post
                                There are some glamor speedups and fixes in the queue, see http://lists.freedesktop.org/archive...ober/date.html
                                BTW, these just get merged: http://cgit.freedesktop.org/xorg/driver/glamor/log/ .

                                I also updated my PPA with them.

                                Comment

                                Working...
                                X