We recommend that you update to the latest Intel Graphics driver to get full API support. For more information about installing the latest graphics driver on your system, see How to Install an Intel Graphics Driver in Windows 10.
Starting with Gen6 (Sandy Bridge and onwards), Intel GPUs provide performance counters used for exposing internal performance data to drivers. The drivers and hardware registers refer to this infrastructure as the Observation Architecture (internally "OA") [15], but Intel's documentation also more generally refers to this functionality as providing Observability Performance Counters [16] [17].
Intel 965 Opengl 21 Driver
The H.264 decoding support is maintained in a separated g45-h264 branch, which can be used by installing libva-intel-driver-g45-h264AUR package. Note, however, that this support is experimental and its development has been abandoned. Using the VA-API with this driver on a GMA 4500 series GPU will offload the CPU but may not result in as smooth a playback as non-accelerated playback. Tests using mplayer showed that using vaapi to play back an H.264 encoded 1080p video halved the CPU load (compared to the XV overlay) but resulted in very choppy playback, while 720p worked reasonably well [22]. This is echoed by other experiences [23]. Setting the preallocated video ram size higher in BIOS results in much better hardware decoded playback. Even 1080p h264 works well if this is done[24]. Smooth playback (1080p/720p) works also with mpv-gitAUR in combination with ffmpeg-gitAUR and libva-intel-driver-g45-h264AUR. With MPV and the Firefox plugin "Send to MPV player"[25] it is possible to watch hardware accelerated YouTube videos.
In Mesa 20.0, a new OpenGL driver, Iris, is promoted to be the default for Gen8+. Certain applications run faster with it. You may disable it and revert to use the old i965 driver by setting the MESA_LOADER_DRIVER_OVERRIDE=i965 environment variable before starting any OpenGL application. This setting does not affect Vulkan applications.
The intel-driver uses Triple Buffering for vertical synchronization; this allows for full performance and avoids tearing. To turn vertical synchronization off (e.g. for benchmarking) use this .drirc in your home directory:
intel_idle.max_cstate=1 limits the processors sleep states, it prevents the processor from going into deep sleep states. That is absolutely not ideal and does result in higher power use and lower battery life. However, it does solve random hangs on many Intel systems. Use this if you have a Intel Baytrail or a Kaby Lake Refresh chip. Intel "Baytrail" chips are known to randomly hang without this kernel parameter due to a hardware flaw[27].More information about the max_cstate parameter can be found in the kernel documentation and about the cstates in general on a writeup on GitHub.
If you try adding intel_idle.max_cstate=1 i915.enable_dc=0 ahci.mobile_lpm_policy=1 in the hope of fixing frequent hangs and that solves the issue you should later remove one by one to see which of them actually helped you solve the issue. Running with cstates and display power management disabled is not advisable if the actual problem is related to SATA power management and ahci.mobile_lpm_policy=1 is the one that actually solves it.
For some 165Hz monitors, xrandr might not display the 165Hz option, and the fix in #Adding undetected resolutions does not solve this. In this case, see i915-driver-stuck-at-40hz-on-165hz-screen.
Users with newer 12th gen IGP's may see issues where plasma desktop is almost unusable. It appears to be an issue with accelerated items. Running glxgears will report a high frame rate, but the animation will not be updated.A possible solution here is to change the driver under X.
The Iris Gallium3D driver is certainly moving in the right direction and great to see it now in mainline Mesa, which should help the developers in moving the code forward while also opening it up to more users for testing and feedback. Now that it's mainline in Mesa 19.1, assuming it's part of your distribution/PPA/AUR/third-party Mesa package build, it will just be a matter of setting the MESA_LOADER_DRIVER_OVERRIDE=iris environment variable for using this Gallium3D driver in place of the classic i965 driver for Broadwell graphics and newer.
Hopefully the Iris Gallium3D driver will be mature enough by the end of the year when Icelake hardware is shipping that it could become the default driver at least there, but we'll see how quickly the performance optimizations are ironed out in this driver over the months ahead. Stay tuned for more benchmarks on Phoronix.
Besides performance and better driver efficiency, switching over to a Gallium3D driver opens up other new possibilities like supporting the Gallium HUD, leveraging the Gallium Nine state tracker for D3D9 Windows games running under Wine / Steam Play, and other features afforded to the Gallium3D architecture.
Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software. He can be followed via Twitter, LinkedIn, or contacted via MichaelLarabel.com.
Crocus is great for the Intel 965 and above iGPUs, but the new Gallium i915G driver brings OpenGL 2.1 support to the 915GM platforms along with improved performance. (Crocus does not work with the "smaller number" GPUs)
Im having an issue with my Dell Inspiron 1525 laptop computer. I have an intel 965 Express onboard graphics and when I start to play a game, called Medal of Honor : Allied Assault It loads, and then the console spits out an error which I will underline.
May I ask which newer version of the driver you installed? I, along with other Inspiron 1525 users, have been having issues with the last three versions released from Intel. See this thread for details:
The driver Dell is shipping is v15.7.3 (7.14.10.1409), which has OpenGL 1.5 support. Since v15.11.x OpenGL 2.0 is offered, but that's less stable. Due to the bugs sargeras9 posted the latest version working on your chipset is v15.11.0 (7.15.10.1537).
I'm running a laptop running on a Mobile Intel(R) 965 Express Chipset Family - specifically a Intel GM965. The driver is as current as I can find ( 8.15.10.1749 ) Documentation on this chipset tells me that it supports OpenGL up to 1.5, however when I run GPU Caps Viewer it tells me my OpenGL version is 1.1.0, despite having the most up to date drivers.
I must have gone through that list of available drivers a dozen times by now and somehow always downloaded the wrong drivers, this time however I got the correct ones and my chipset is now happilly 1.5 enabled!
I have checked OpenGL version of my GPU via GPU Caps Viewer verifying me up to OpenGL Version 2.1, but Kivy somehow doesn't detect OpenGL 2.1 and defaults to GDI Generic from Microsoft instead. I did some research on internet and found out that best way to resolve this problem is to update your graphical card's driver from your graphical card manufacturer, but this didn't work in my case.
We require NVIDIA driver version 257.21 (June 2010) or newer, see bug 623338. Notice that 257.21 is the commercial version number. This corresponds to the last 5 digits in the technical version number, which for instance is 8.17.12.5721 on Windows 7/Vista.
We require AMD driver version 10.6 (June 2010) or newer on Windows up to 7, see bug 623338. Notice that 10.6 is the commercial version number. The actual check is performed on the technical version number, and we require it to be at least 8.741.0.0.
We require AMD driver version greater than 12.11 beta (November 2012) on Windows 8, see bug 806991. Notice that 12.11 beta is the commercial version number. The actual check is performed on the technical version number, and we require it to be strictly higher than 9.10.8.0.
We block Direct3D 10 features (including Direct2D) on buggy installations where the Intel driver version reported in the Windows Registry is not equal to the version of the driver DLL, igd10umd32.dll/igd10umd64.dll. See bug 590373.
If enabled while Trace is active, this variable specifies that the threaded contextshould be traced for drivers which implement it. By default, the driver thread is traced,which will include any reordering of the command stream from threaded context.
Although this text file is updated by the Mesa developers themselves, it might not contain an exhaustive list of all the drivers features and subtleties. So, for more information, it is advised to look at the source code, or ask the developers on their mailing-list.
The NVK driver has been written almost entirely from scratch using the new official headers from NVIDIA. Mesa translates specifications to vendor-specific graphics hardware drivers. The long-term hope is for NVK to be for NVIDIA hardware what RADV is to AMD hardware.
Beginning with Mesa 20.2 is OpenGL 4.5 support for LLVMpipe, the LLVM-based software rasterizer built as a Gallium3D driver. This succeeded LLVMpipe for years being limited to OpenGL 3.3. While the OpenGL 4.5 support has been enabled for weeks, The Khronos Group has now officially confirmed its implementation.
Intel shared plans early on that they want OpenGL ES 3.0 for Mesa by early 2013 with the next Mesa release. OpenGL ES 3.0 has a lot of new features over the aging OpenGL ES 2.0 specification, which makes it a really worthwhile upgrade. As part of this, Intel has been working on ETC2 texture compression and other functionality for this open-source Linux graphics driver. Ian Romanick of Intel has now shared on the Mesa mailing list that in the coming days he will begin to post the GLES3 patches for review and then merge them into mainline Mesa. 2ff7e9595c
Commentaires