Pandemonium, I was addressing citizenofnowhere, and his issue is almost certainly due to vblank_mode being enabled - but he is using new version of the intel and libdrm code. I don't have access to any Intel hardware in order to test at the moment, so I can't comment any further. If you see a glxgears result that's constrained to your refresh rate (e.g., 60-62fps for a laptop, or a rate corresponding to your display device such as 70, 75, 85), then the problem is vblank_mode (and perhaps the environment variable is broken/ignored in the new driver, so it cannot be overridden). I can't say if the problem applies to you.
>From my understanding of events, we're kind of in a transitional stage with regards to DRI. We had the introduction of DRI2 which was initially supposed to be in the form of TTM, which then got dropped in favour of GEM, and I've been reading some complaints that GEM is too Intel- centric, thus unsuitable for other chipsets. I have no idea what the situation is at the moment, but I honestly don't think the Xorg developers are concerned so much with performance for the legacy DRI code at this time, which is unfortunate for users (but also understandable). Bryce knows a lot more, and he's already explained the situation (re: performance of the 2.4 vs 2.5 driver and absence of the legacy INTEL_BATCH variable). -- INTEL_BATCH=1 not implemented in Intrepid ? https://bugs.launchpad.net/bugs/284082 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
