Ubuntu Intel G33 Driver
LINK ->>> https://cinurl.com/2t7CaO
Most Linux-based* distributions already include Intel® Graphics Drivers. These drivers are provided and maintained by the Linux* distribution vendors and not by Intel, we recommend contacting the Linux* Operating System Vendors.
Open a terminal window by pressing Ctrl+Alt+T. Now, to install the latest drivers, add the graphics package repository by executing the following commands, it will install gpg-agent and get and will install the public key required to verify the integrity of the package.
Intel® open source 3D Graphics Drivers for Linux* are the industry-leading drivers for Linux* distributions for all Intel® graphics platforms shipped over the last decade. Because these drivers are integrated into all popular Linux distributions, you can trust that your Linux system will deliver stunning, high quality graphics without needing additional hardware or extra driver software. Whether you are running the latest Android games on an Intel®-based Chromebook with Google Play Store, or a sophisticated 3D modeling application on a system with the Intel® Xeon® processor, Intel's graphics drivers put beautiful 3D graphics at your fingertips.
Today I am proud to announce that Intel is among a select group of graphics platform suppliers with drivers certified for the most advanced versions of all three open industry-defined 3D graphics APIs on Linux*: OpenGL* 4.5, OpenGL ES* 3.2 and Vulkan* 1.0.
Most users and organizations will find no need to do anything other than use the built-in drivers included with their OS. But we also know that some advanced users might want to experiment with the source code comprising the full graphics stack to test individual components in a custom software stack. Developers who would like to join the developer communities supporting the various components (including Mesa, Linux kernel, display server, etc.) can download the source code for the in-development versions of all the components. The user space portion of our 3D driver includes the implementation of all three 3D APIs specified by the Khronos* industry consortium: OpenGL*, OpenGL ES*, and Vulkan*. To learn more, check out our Community, Support, and News and Blogs pages.
The Intel graphics driver in X.Org intends to support all intel chipsets from the i810 and upwards. Please note that this driver does not support the GMA 500, found in various Atom-based designs.
Please note that TV out support is usually provided by third-party encoder chips, which typically require separate drivers. Some of these drivers have not yet been written or included in the intel driver, thus while everything else may work fine, TV out may not be supported depending on the encoder chip paired with your graphics chip.
Installing new Mesa graphics drivers may also need a newer Linux kernel. It will be a good idea to enable HWE kernel on Ubuntu to reduce the chances of conflict with the kernel. HWE Kernel gives you the latest stable kernel used by Ubuntu on an older LTS release.
Since the nightmare crash between Xorg and Intel graphic card on Ubuntu Jaunty, now you have a good news. You can update your Intel driver to the latest update to this great hardware acceleration for playing h.264 video. Or in other words we now have Hardware acceleration for HD content with our Intel video cards. And as the new video standard on the HTML 5, h.264 video format will be used.
Thanks for the guide. You might want to add instructions on how to revert the changes and downgrade back to the default Intel drivers should the latest intel drivers result in system instability ( which I experienced alot when i tried it) The user would need to install a package called ppa-purge
I'm wondering how to fix this =/ (Another computer, also running Ubuntu 10.04, never had any problems with the internet and connects just fine to the network and to the internet. I didn't change the driver on that computer.)
then open synaptics and search2.6.37-graphics2+12.26~maverickthen reboot and start whit this kernel and my problem with incompatibility of compiz and intel graphics end and my system works excellent and without freezes.
Hi Ivan, I need help with this please. I have Ubuntu 12.04 now and the video card I have is Intel G33 x86/MMX/SSE2. Would this tutorial still work if I try it on my pc? I can't find anything on the internet and the intel website says I have to go to this other website to update the drivers, but there is no guide on how to do it I'm clueless now. What should I do?Please help. Thanks in advance.
Google Chrome 88 (and newer) has made hardware accelerated video decoding available on Linux, but it's not enabled by default. Google Chrome is not the only Chromium-based web browser to support hardware acceleration on Linux though. This article explains how to enable hardware-accelerated video decoding in Google Chrome, Brave, Vivaldi and Opera web browsers running on Debian, Ubuntu, Pop!_OS or Linux Mint (Xorg only).Using hardware-accelerated video decode in your web browser should result in using less CPU usage (and thus, less battery draining) when playing online videos.It's worth noting that Chromium web browser had patches that allowed making hardware accelerated video decoding available on Linux for some time, and some Linux distributions packaged it using those patches. So Chromium users have had hardware acceleration on Linux for some time, depending on their Linux distribution or if they installed the patched Chromium in some other way. E.g. on Ubuntu / Linux Mint there's a PPA with VA-API patched Chromium builds. Thus, these instructions may also work for Chromium browser, depending on how it's built.I'd also like to add that these instructions to enable hardware accelerated video decoding also work on other Linux distributions, and not just Debian / Ubuntu-based Linux distributions, however, the driver names are different.I tested these instructions using Ubuntu 20.10 desktop with Nvidia graphics, and the web browsers listed below installed using their original Ubuntu packaging (using a DEB package). Also tested using a laptop with Intel graphics (10th gen) on Ubuntu 20.04 and 20.10. I don't own a device with AMD graphics to test this.In my test, I was able to get hardware-accelerated video decode to work on Linux using:Google Chrome stable 88Brave stable 1.19Vivaldi snapshot 3.6 / [Edit] The latest Vivaldi stable 3.6 also worksOpera Beta 74if(typeof ez_ad_units!='undefined'){ez_ad_units.push([[300,250],'linuxuprising_com-medrectangle-4','ezslot_1',115,'0','0'])};__ez_fad_position('div-gpt-ad-linuxuprising_com-medrectangle-4-0');Obviously, it should continue to work with versions newer than these (so Google Chrome 89, Brave 1.20, etc.).For me, hardware-accelerated video decode didn't work using:Vivaldi stable 3.5. Vivaldi stable is now version 36, and that does have working hardware-accelerated video decodingOpera stable 73Microsoft Edge - there's not even a chrome://flags/#enable-accelerated-video-decode flag (to enable hardware-accelerated video decode).You can use VA-API on XWayland, using the --use-gl=egl command line flag, but I did not try it. Starting with Google Chrome 91 (and other browsers based on Chromium 91), you'll also need to append the --enable-features=VaapiVideoDecoder and --disable-features=UseChromeOSDirectVideoDecoder flags.[[Edit]] I've tried using the instructions below, and then launch the browser with the --use-gl=egl and --disable-features=UseChromeOSDirectVideoDecoder flags on Wayland, on a laptop with Intel graphics, and hardware-accelerated video playback works. However, the videos stutter on this laptop with these settings. So in this case I prefer Firefox with hardware-accelerated video playback (on which, using Wayland and Firefox on the same laptop, video playback is fluid, but the CPU usage is greater than using a Chromium-based browser).
Things you need to enable hardware-accelerated video decode in the web browsers I mentioned above (so Google Chrome 88+, Brave 1.19+, Vivaldi 3.6+ and Opera 74+):1. Enable the following web browser flags:For browsers based on Google Chrome 90 and older:Override software rendering list: chrome://flags/#ignore-gpu-blocklistHardware-accelerated video decode: chrome://flags/#enable-accelerated-video-decodeFor browsers based on Google Chrome 91 and newer (there's no hardware-accelerated video decode any more, but we'll need to use a new command line flag - see step 4):Override software rendering list: chrome://flags/#ignore-gpu-blocklist2. Install the VA-API driver to be able to decode media (source), as well as libva-drm2 and libva-x11-2 (these 2 are probably already installed, but just in case; I added these 2 in a later edit, after I noticed hardware acceleration was not working without them, and as soon as I installed vainfo, which has these 2 packages as dependencies, it would start working):For Intel Gen 7 and earlier hardware:sudo apt install i965-va-driver-shaders libva-drm2 libva-x11-2For Intel Gen 8+ hardware:sudo apt install intel-media-va-driver-non-free libva-drm2 libva-x11-2For Nouveau and AMD drivers (I couldn't get any browser to use hardware acceleration with the Nouveau drivers, maybe you have better luck): sudo apt install mesa-va-drivers libva-drm2 libva-x11-2if(typeof ez_ad_units!='undefined'){ez_ad_units.push([[300,250],'linuxuprising_com-box-4','ezslot_6',113,'0','0'])};__ez_fad_position('div-gpt-ad-linuxuprising_com-box-4-0');For proprietary Nvidia drivers - you can install them from the repositories or by using the Proprietary GPU Drivers PPA (e.g. launch the Additional Drivers dialog on Ubuntu and install it from there). If you're using proprietary Nvidia drivers, you'll also need a patched vdpau-va-driver ([[edit]] this patch no longer supports VP9, even if your graphics support it, so you must use the h264ify extension in all cases - see below). You can get it from here (you'll also need libvdpau1 from here as it's a dependency for vdpau-va-driver) for Debian / Ubuntu / Linux Mint / Pop!_OS, etc. The Ubuntu 20.04 package from there also works on Ubuntu 20.10 and newer. If you want to see the patches used by this package, download the .debian.tar.gz archive (from the same link as above) and look inside the "patches" folder. In case these DEBs don't work on Debian (I did not try it), use the these links for vdpau-va-driver (orig.tar.gz | debian.tar.xz) and libvdpau (orig.tar.gz | debian.tar.xz) to download the .orig.tar.gz and .debian.tar.xz archives, and build the DEB package on your system. Also install libva-drm2 and libva-x11-2: sudo apt install libva-drm2 libva-x11-2Why the non-free versions of the intel-media-va-driver and i965-va-driver? In theory this should work with the free version (?), but in my test on a laptop with Intel Gen 10, hardware-accelerated video decoding only worked with the intel-media-va-driver-non-free driver, and not intel-media-va-driver (I'm not sure about the i965 driver, but I assumed it might be similar). There's also someone else here, saying this got it working for them.3. Only needed for graphics card that don't support VP9 hardware video decoding: install the h264ify browser extension.If your graphics card doesn't support VP9 hardware video decoding, install the h264ify browser extension (or enhanced-h264ify - some users say this works for them while the original extension doesn't; for me it's the other way around) and make sure it's enabled for VP9.[[Edit]] Nvidia users: the patched vdpau-va-driver mentioned above no longer hardware accelerates VP9 in Chromium-based browser. So you must use the h264ify extension and avoid VP9 in order to get hardware-accelerated video decode.If you still don't see MojoVideoDecoder in the chrome://media-internals tab (see below in the section for how to check if hardware-accelerated video decoding is enabled and actually used by the browser), try to restart the web browser after installing this extension. I've seen cases where this was needed, and some in which it wasn't required.4. Launch the web browser using the --use-gl=desktop and flag to enable VA-API hardware acceleration. [Edit] With browsers based on Chromium 91 and newer, you'll also need to launch it with the --enable-features=VaapiVideoDecoder flag. [[Another edit]] Now it seems for most, also adding the --disable-features=UseChromeOSDirectVideoDecoder flag is also needed.To be able to use VA-API for video decoding you'll need to launch the web browser, be it Chromium, Google Chrome, Brave, Opera or Vivaldi, using the following command line flags: --use-gl=desktop, --enable-features=VaapiVideoDecoder and --disable-features=UseChromeOSDirectVideoDecoder. E.g. to launch Google Chrome using these flags:google-chrome-stable --use-gl=desktop --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoderLaunch Brave using this:brave-browser --use-gl=desktop --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoderAnd so on. To make this change permanent, copy the browser .desktop file from /usr/share/applications to ~/.local/share/applications (if this folder doesn't exist, create it). By copying the file here, we're making sure it won't be overwritten by an update. Then, open the .desktop file (e.g. brave-browser.desktop, brave-browser-beta.desktop, google-chrome.desktop, etc.) from this ~/.local/share/applications location, with a text editor. In this file, search for the line starting with Exec=, and change the executable to include --use-gl=desktop --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder. E.g. for Brave: Exec=/usr/bin/brave-browser-stable --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder, or for Google Chrome: Exec=/usr/bin/google-chrome-stable --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder %UImportant note: If you see a completely white video image when launching the browser with --use-gl=desktop, check chrome://flags and make sure that Vulkan is not enabled there. Having Vulkan enabled and launching the browser using the --use-gl=desktop option will cause this to happen.Another note, this time for Opera users: if after using the h264ify extension, you can no longer play videos on YouTube and other such websites, see the solutions from here to enable h264 support in Opera (note that if the web browser you're using is Opera Beta, the folder must be /opera-beta).That's it. 2b1af7f3a8