Announcement

Collapse
No announcement yet.

Intel Pushes Out Its 2.12 X.Org Driver To RC State

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

  • Intel Pushes Out Its 2.12 X.Org Driver To RC State

    Phoronix: Intel Pushes Out Its 2.12 X.Org Driver To RC State

    Intel has rolled out their first release candidate for their forthcoming xf86-video-intel 2.12 DDX driver update. The Intel 2.12 X.Org driver, as we have already mentioned twice brings faster 2D performance, among other changes...

    http://www.phoronix.com/vr.php?view=ODMzOA

  • #2
    Looks like we will finally see decent performance with the new GEM/KMS graphics stack!

    Comment


    • #3
      WoW!

      This release is awesome!

      Beside fixing non-center-sampling (ugly artifacts in firefox, java, ...) this release really improves performance.
      Running some benchmarks to measure the performance of a graphic library I wrote show runtime-reductions of about 20-40%

      Took so long to get decent performance with GEM/KMS, great its finally here :-)

      Comment


      • #4
        Not stable for me

        Although I must admit the performance improvement was noticeable at first glance

        Let's hope for a stability improvment too

        Regards

        Comment


        • #5
          Nice work Intel.

          Comment


          • #6
            The most impressive part isn't even mentioned here in the forum. The driver ist for xfree96 according to the article

            Comment


            • #7
              Quoting myself:

              Originally posted by birdie View Post
              Intel driver is a bad joke, what performance improvements they are talking about when some basic functionality causes X server hangs, when OpenGL performance is ... the word "performance" doesn't apply well to Linux Intel GPPU drivers.

              Comment


              • #8
                Intel's driver is a bad joke alright. Just yesterday I was trying to get it to work. It would hang X anytime we started doing something serious with OpenGL. The closest example I could find was something saying downgrade to Mesa 7.5. Which really isn't a solution at this point. I tried upgrading from 2.9 to 2.11, but it made no difference. Ended up using a different computer with a Nvidia card, worked the first time.

                Comment


                • #9
                  Originally posted by birdie View Post
                  Intel driver is a bad joke, what performance improvements they are talking about when some basic functionality causes X server hangs, when OpenGL performance is ... the word "performance" doesn't apply well to Linux Intel GPPU drivers.
                  Well, I haven't experienced stability problems for quite some time now, although right after UXA-switch/KMS was horrible. 2.6/2.7/2.8 were totally broken - 2.9 was the first which worked quite reliable.
                  2.12 is the first release which brings 2D performance to a level where it should have been for quite some time now.

                  Hmm, yes Intel's OpenGL support is horrible, but its enough to run opengl based composition managers. And frankly, if you care about OpenGL performance, don't tell me nobody warned you about intel

                  - Clemens

                  Comment


                  • #10
                    For the past two months I have been experiencing daily freezes. Downgrading did not change anything. It is a real nightmare.

                    Comment


                    • #11
                      Please Intel get rid of this:
                      [drm:i915_wait_request] *ERROR* i915_wait_request returns...
                      I am tired of all those reboots!

                      Comment


                      • #12
                        If it suddenly started and downgrading doesn't help, have you ever considered your hardware to be broken?

                        Originally posted by DebianAroundParis View Post
                        Please Intel get rid of this:
                        [drm:i915_wait_request] *ERROR* i915_wait_request returns...
                        I am tired of all those reboots!

                        That means your GPU is hung. So instead of spreading bad publicity in a forum not read by intel employees, you could do:
                        1. Install kernel 2.6.34 (needed for debugging)
                        2. install intel 2.11.901 + libdrm-??.21
                        3. When a hang occurs, log in via ssh save the GPU-state as well as the last batchbuffer. File a bug at freedesktop's bugzilla, and append those files:

                        After a freeze, can you grab a copy of dmesg, Xorg.log, intel_reg_dump,
                        and /sys/kernel/debug/dri/0/i915_error_state. From my perspective, the
                        last contains the most interesting information (the batchbuffer executing
                        at the time of a gpu hang). If there is nothing in any of those, echo t >
                        /proc/sysrq-trigger and look for the stacktraces in dmesg.
                        I guess they would be more than happy about feedback like this.

                        - Clemens

                        Comment


                        • #13
                          Originally posted by Linuxhippy View Post
                          If it suddenly started and downgrading doesn't help, have you ever considered your hardware to be broken?

                          That means your GPU is hung. So instead of spreading bad publicity in a forum not read by intel employees, you could do:
                          1. Install kernel 2.6.34 (needed for debugging)
                          2. install intel 2.11.901 + libdrm-??.21
                          3. When a hang occurs, log in via ssh save the GPU-state as well as the last batchbuffer. File a bug at freedesktop's bugzilla, and append those files:
                          Nice, now could you get someone to actually look at Intels bugreports?
                          The ones I find when searching for i915_wait_request in bugs.freedesktop.org tells the same story as most of the bugreports I have done about Intel and their graphic stack: If you are lucky you get a reply, if you are lucky you get a reply asking for more information. If you are really lucky you will get more of the same question about three months apart.
                          I have at least two open Intel bugreports currenntly, I am following two others and would have had more if I actually had time to track.
                          The first is about the wrong resolution being set for S-Video out upon boot (should be a with of 640, got 848), filed nine months ago. They provided a patch in the bugreport that set the right resolution at least 2 kernel releases ago, but still 2.6.35-rc4 does not set the correct resolution. Poingting it out in the bug about two months ago, no answear in over four months.
                          The second is about an issue with the resolution being set having the wrong clock for some resolution. The first time I mentioned the problem (but still did not new what coused it nor did I get any help try to figure it out) was in the former bugreport. Since then they manage to break all modes for NTSC-M and PAL here on my i945 S-Video out. Filed a new bug for this over one month ago with all information asked for in their wiki, still no answear. And this is broken out of the box on Fedora13, I only need a LiveUSB of F13 to reproduce, no logging in or fiddeling needed.

                          Beside those I have seen Xv hanging the whole X-server (being tracked on fedora/redhat, there at least some maintainers who help try to figure out stuff). I have also some other issues that I have filed on redhat and waiting for input.

                          Originally posted by Linuxhippy View Post

                          I guess they would be more than happy about feedback like this.

                          - Clemens
                          Yeah, I guess they are. As long as they can ignore it and instead try to optimize the codebase instead of first getting it to work for all their costumers (yes, they are employed by intel, and I have bougth intel hardware, I am a costumer who wish to be able to use Linux on my boxes, not just windows).

                          And yeah, I am a little bit irritated since Fedora13 is broken out of the box on one of my regular laptops (a i855 machine which hangs and have all "shadowed" buttons white and some other graphical artifacts) and on a little computer wich should only be connected to a TV for various things (a box using a i945GM chipset and S-Video, works with UMS, totally broken with KMS).

                          Comment


                          • #14
                            Oh, and yeah. I really hate those 1 minute lock on posts here. Could you at least make it 5 or maybe 10 minutes? Or remove edit completely?

                            Comment


                            • #15
                              Originally posted by Linuxhippy View Post
                              If it suddenly started and downgrading doesn't help, have you ever considered your hardware to be broken?




                              That means your GPU is hung. So instead of spreading bad publicity in a forum not read by intel employees, you could do:
                              1. Install kernel 2.6.34 (needed for debugging)
                              2. install intel 2.11.901 + libdrm-??.21
                              3. When a hang occurs, log in via ssh save the GPU-state as well as the last batchbuffer. File a bug at freedesktop's bugzilla, and append those files:



                              I guess they would be more than happy about feedback like this.

                              - Clemens
                              Weeks ago I did a search and I saw my problem already reported all over the web for months.
                              Lately I noticed that this bug seems to be triggered by a combination of VLC and KDE.

                              Comment

                              Working...
                              X