Export translations

Settings

Group

Language

Format

Export for off-line translation

Export in native format

<languages/>
__TOC__
<div lang="en" dir="ltr" class="mw-content-ltr">
= Overview =
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{note|The mhwd command is still ''under development'', and at present is only able to install drivers for graphics cards connected internally via pci.}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Where installing the full version of Manjaro (i.e. complete with a pre-installed desktop environment, codecs, and software applications), the mhwd command will be automatically run by the GUI and CLI installer to automatically detect your graphics card and install the most appropriate driver for it. '''Whether free or proprietary drivers are installed will depend on your initial choice of using free or nonfree graphics drivers to boot up'''. 
Otherwise, it will be necessary to run the mhwd command manually as part of the post-installation process for the minimalistic '''NET-Edition''' of Manjaro.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''For Beginners, it is recommended to use "Hardware Detection" in [[Manjaro Settings Manager]] to change or install new graphics drivers.'''<br />
For intermediate and advanced users, it is also possible to use the mhwd command to install, re-install, and remove installed graphics drivers at any time, as illustrated below.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
= Automated Identification and Installation =
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This is the recommended method for the detection and installation of graphics drivers. The syntax for the automated installation method is:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo mhwd -a [pci or usb connection] [free or nonfree drivers] 0300}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
A breakdown of the command used for the automated method is as follows:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* '''-a''': Automatically detect and install the appropriate driver
* '''[pci or usb]''': Install the appropriate driver for devices connected internally via pci, or externally via usb (again, mhwd currently only supports pci connections at this stage in its development)
* '''[free or nonfree]''': Install either free drivers (e.g. provided by the Linux community), or nonfree drivers (e.g. provided by hardware manufacturers) 
* '''0300''': Identify that a driver is to be installed for a graphics card (0300 is the ID for graphics cards. As the mhwd command develops, new ids will be used for other hardware devices).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example, the following command would result in the automatic detection and installation of the best available '''proprietary driver''' for a pci-connected graphics card:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo mhwd -a pci nonfree 0300}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Otherwise, the following command would result in the automatic detection and installation of the best available '''free driver''' for a pci-connected graphics card:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo mhwd -a pci free 0300}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
= Manual Identification and Installation =
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Taking a do-it-yourself approach is itself relatively easy and straightforward using the mhwd command. This should be undertaken in two stages:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''1.''' Identify the appropriate driver to be installed, and then
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''2.''' Install the driver
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{tip| Just ensure that you have identified and are indeed about to install the correct driver for your particular graphics card!}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Identifying Available Drivers ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Prior to manually installing a graphics driver, it will be necessary to identify what drivers are available for your system. To list the appropriate drivers available, the basic syntax is:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=mhwd -l [optional: detailed view] [optional: --pci or --usb connection]}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Using this command without the additional options will list basic information for all the available drivers for devices connected to your system. '''All drivers graphics card drivers will have the prefix (video-) in their name'''. The basic information provided for all listed drivers will be:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Name
* Version
* Free or proprietary, and
* PCI or USB connection
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
A more detailed list of installed drivers can be obtained by entering:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=mhwd -l -d}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
A detailed list will provide the following information:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Name
* Version
* PCI or USB connection
* Description
* Priority
* Free or proprietary
* Dependencies
* Conflicts
* Class ID (e.g. '0300' for graphics card drivers), and
* Vendor ID
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
In addition, using the ''--pci'' filter in the following example will list detailed information for only the drivers available for devices (e.g. graphics cards) using an internal PCI connection:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=mhwd -l -d --pci}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Installing a Driver ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To install a driver for a graphics card, the syntax is:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo mhwd -i pci [name of driver]}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
A breakdown of the command used to manually install a driver is as follows:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* '''-i''': Install a driver
* '''[pci]''': Install a driver for a device connected internally via pci (e.g. graphics cards)
* '''[name of driver]''': The name of the driver to be installed
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example, to install the proprietary nvidia graphics card driver, the following command would be used:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo mhwd -i pci video-nvidia}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Force Reinstall a Driver ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{warning|use this command with care!}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To force the re-installation of an existing driver without removing it first, the syntax is:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo mhwd -f -i pci [name of driver]}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example, to force the re-installation of a previously installed nvidia graphics card driver, the following command would be used:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo mhwd -f -i pci video-nvidia}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
= Removing an Installed Driver =
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
On occasion it may be necessary to remove an installed graphics card driver. Similarly to manually installing a graphics card driver, two steps should be undertaken for removal:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''1.''' Identify the installed driver
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''2.''' Remove the identified driver
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
After all, it would be somewhat difficult to remove an installed driver if you don't know what it's called!
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Identifying Installed Drivers ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To identify and list Manjaro's installed drivers - including the graphics driver to be removed, the syntax is:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=mhwd  -li [optional: detailed view] [optional: pci or usb devices only]}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Using this command without the additional options will list the basic information of all the drivers currently installed on your system. '''Once again, all drivers for graphics cards will have the prefix (video-) in their name'''. As with listing drivers available for your system, the ''-d'' option used in the following command will list detailed information:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=mhwd -li -d}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This information may prove useful to determine any otherwise unforeseen consequences or problems upon removing a driver. And again, it is also possible to filter your list of installed drivers by whether they are used on hardware connected via pci or usb. In this instance, a detailed list will be generated only for installed drivers used on hardware with a PCI connection:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=mhwd -li -d --pci}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
One other way of reporting drivers installed andin use is using the {{ic|inxi}} tool.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=inxi -G}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{note|The mhwd profile 'video-linux' corresponds to the latest opensource driver availablefor your hardware.}}
{{note|The mhwd profile 'video-vesa' is a generic fallback driver which should not be used in the vast majority of cases.}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Removing Installed Drivers ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{warning|use this command with care!}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To remove an installed driver, the syntax is:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo mhwd -r [pci or usb] [name of driver]}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example, to remove the installed driver for a nvidia graphics card (connected internally via pci), the following command would be used:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo mhwd -r pci video-nvidia}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
= Checking configuration =
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You can check configuration with:
{{UserCmd|command=sudo mhwd-gpu --check}}
{{UserCmd|command=mhwd-gpu --status}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
And if needed fix issues with:
{{UserCmd|command=sudo mhwd-gpu --setmod}}
{{UserCmd|command=sudo mhwd-gpu --setxorg [PATH]}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Make sure the path to xorg config file is valid.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Note about ati, xorg file and login artifacts or kicad: if you get artifacts upon logging in or if kicad rendering and zooming is slow, try adding [Option "EXAPixmaps" "off"] in the "Device" section of xorg config file. See [https://wiki.archlinux.org/title/ATI#Performance_and/or_artifacts_issues_when_using_EXA here.]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==PRIME GPU offloading==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If your hardware includes more than one GPU card you can make use of PRIME offloading. PRIME is a technology used to manage hybrid graphics found on recent desktops and laptops (Optimus for NVIDIA, AMD Dynamic Switchable Graphics for Radeon). PRIME detects both cards and automatically selects Intel card by default; using the more powerful discrete graphics card, when called, for more demanding applications.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
In Manjaro this will automatically be available for hybrid graphics systems using intel/modesetting for the integrated card and free drivers (AMDGPU or Nouveau) for the dGPU.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may choose to run a program with a specific GPU, prepending the application's command with ''DRI_PRIME=x'', where ''x'' is the card priority number.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example, to run an application using the second card prepend the application command with '''DRI_PRIME=1'''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=DRI_PRIME=1 glxspheres64}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To use the 1st card (usually when the CPU has an embedded GPU, this is used)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=DRI_PRIME=0 glxspheres64}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you want to always run some application with the discrete gpu, you may copy that application's .desktop file to {{ic|~/.local/share/applications/}} and edit the "Exec" property
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=Exec=DRI_PRIME=1 inkscape}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Some applications (usually games like steam) may have an embedded option to specify the command line, where it is preferred to use this way.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example, in Steam, select a game - that you want to run using your discrete Nvidia card - from the Library page of the Steam client, right-click, and select Properties.
Click the SET LAUNCH OPTIONS... button and specify for the command line options followed by the default launch hook %command%.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
DRI_PRIME=1 %command%
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To use the dGPU by default see '''[https://wiki.archlinux.org/index.php/PRIME#Reverse_PRIME Reverse Prime]'''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
= NVIDIA Proprietary (non-free) drivers =
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have a Nvidia card, you have the option to use the proprietary (closed source = non-free) drivers instead of the open source (free) nouveau driver.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For Legacy/older nvidia cards, Manjaro maintains older drivers for compatibility. In these cases the driver name is different, instead of nvidia it is nvidia-390xx or nvidia340xx, whether in nvidia-only or bumblebee mhwd driver configuration.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When you install the non-free driver, mhwd includes a Nvidia utility "Nvidia Settings Utility" that can help you configure several settings. You can find this utility in your GUI Applications Menu or start it from a terminal
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo nvidia-settings}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you are using bumblebee, the nvidia utility needs a special command
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo optirun -b none nvidia-settings -c :8}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Nvidia Optimus==
For Optimus laptops or dual GPU hardware with intel and nvidia GPUs, you have three options to utilize the card driver usage at your preference or your hardware capabilities.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''[[#nvidia-prime|PRIME]] (mhwd default)'''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''[[#Bumblebee|Bumblebee]]'''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When you install Manjaro with the non-free option selected from Grub menu, or when you use automatic driver installation, PRIME or bumblebee is installed by default, depending on support for your GPU, PRIME being preferred. In these cases, the mhwd driver is named "video-hybrid-intel-nvidia-***xx-prime" or "video-hybrid-intel-nvidia-***xx-bumblebee".
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Configure The Resolution/Refresh Rate==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{warning|The method provided does not currently work for the Cinnamon Edition. As soon as a solution is found, then this article will be updated.}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''1.'''  Start nvidia-settings utility
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''2.'''  Change resolution and refresh rate in 'X Server Display Configuration' tab.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''3.'''  Hit the 'Save to X Configuration File' button and save to '''/etc/X11/mhwd.d/nvidia.conf'''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''4.'''  Now start your terminal and enter the following command to complete the process:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo mhwd-gpu --setmod nvidia --setxorg /etc/X11/mhwd.d/nvidia.conf}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Configure X Screen settings (OpenGL Settings, Antialiasing, X Server XVideo)==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''1.'''  Start nvidia-settings utility
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''2.''' Change settings in X Server XVideo Settings, OpenGL and Antialiasing, in the 'X Screen' tab.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''3.''' Click on 'nvidia-settings configuration' tab and click on the 'Save Current Configuration' button.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''4.''' Save the .nvidia-settings-rc to the default location specified ('''/home/[your account name]''')
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''5.''' Edit the .xinitrc file with your preferred text editor. For example, if you use gedit, run this in your terminal:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=gedit ~/.xinitrc}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''6.''' Once opened, add the following line into the configuration file:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=exec nvidia-settings --load-config-only}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Nvidia settings for special cases ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
In case your monitor is not entering powersave mode (DPMS), try adding `Option "HardDPMS" "true"` in your Xorg monitor section. For example:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Section "Monitor"
     # HorizSync source: edid, VertRefresh source: edid
     Identifier     "Monitor0"
     VendorName     "Unknown"
     ModelName      "BenQ ZOWIE XL LCD"
     HorizSync       30.0 - 160.0
     VertRefresh     56.0 - 144.0
     Option         "DPMS"
     Option         "HardDPMS" "true"
   EndSection
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
After forum [https://forum.manjaro.org/t/display-does-not-go-to-powersave/84004/5 issue]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==nvidia-prime==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Manjaro also offers an easy way to use PRIME with proprietary Nvidia drivers.<br>
Simply select and install an 'nvidia-prime' profile through MSM or mhwd (such as ''video-hybrid-intel-nvidia-440xx-prime'') and ensure the package ''nvidia-prime'' is installed.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Then to use the discrete Nvidia card it works the same as [[#PRIME_GPU_offloading|PRIME offloading]] above but uses a different command. Prepend the application command with '''prime-run'''. For example:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=prime-run glxspheres64}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Bumblebee==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Bumblebee configuration is mainly developed to help minimize laptop battery consumption, since Nvidia usually consumes significant power, while Intel cards are more power efficient. So, bumblebee detects both cards and automatically selects Intel card by default and can use the Nvidia for more demanding applications. 
For an application to use the Nvidia card, prepend the application command with optirun or primusrun. For example:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=optirun glxspheres64}}
{{UserCmd|command=primusrun inkscape}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you want to specifically run some application with the nvidia driver, you may edit that application's .desktop file "Exec" property, or run it in terminal like this
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Exec=primusrun chromium
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Some applications (usually games like steam) may have an embedded option to specify the command line, where it is preferred to use this way.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example, in Steam, select a game - that you want to run using your discrete Nvidia card - from the Library page of the Steam client, right-click, and select Properties.
Click the SET LAUNCH OPTIONS... button and specify for the command line options followed by the default launch hook %command%.
  
 primusrun %command%
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[Manjaro Hardware Detection Overview]]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
= Easier way =
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may use a GUI version of mhwd in [[Manjaro Settings Manager#Hardware Detection]]
: With this tool you can:
: - install graphic driver
: - switch graphic driver
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
https://www.youtube.com/watch?v=UAFGukpEIJw
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
= How to check the driver =
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
 {{UserCmd|command=glxinfo &#124; grep OpenGL}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Example output command:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Nvidia driver''' ( proprietary driver )
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmdOutput|command=glxinfo &#124; grep OpenGL|result= OpenGL vendor string: NVIDIA Corporation<br> OpenGL renderer string: GeForce GTX 660/PCIe/SSE2<br> OpenGL core profile version string: 4.3.0 NVIDIA 331.49<br> OpenGL core profile shading language version string: 4.30 NVIDIA via Cg compiler<br> OpenGL core profile context flags: (none)<br> OpenGL core profile profile mask: core profile<br> OpenGL core profile extensions:<br> OpenGL version string: 4.4.0 NVIDIA 331.49<br> OpenGL shading language version string: 4.40 NVIDIA via Cg compiler<br> OpenGL context flags: (none)<br> OpenGL profile mask: (none)<br> OpenGL extensions:}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Nouveau''' , '''Gallium''' from '''Mesa''' ( open source driver )
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmdOutput|command=glxinfo &#124; grep OpenGL|result= OpenGL vendor string: nouveau<br> OpenGL renderer string: Gallium 0.4 on NVE6<br> OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.5<br> OpenGL core profile shading language version string: 1.40<br> OpenGL core profile context flags: (none)<br> OpenGL core profile extensions:<br> OpenGL version string: 3.0 Mesa 9.2.5<br> OpenGL shading language version string: 1.30<br> OpenGL context flags: (none)<br> OpenGL extensions:}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Intel''' driver from '''Mesa''' ( open driver )
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmdOutput|command=glxinfo &#124; grep OpenGL|result= OpenGL vendor string: Intel Open Source Technology Center<br> OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop<br> OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.0.6<br> OpenGL core profile shading language version string: 3.30<br> OpenGL core profile context flags: (none)<br> OpenGL core profile profile mask: core profile<br> OpenGL core profile extensions:<br> OpenGL version string: 3.0 Mesa 11.0.6<br> OpenGL shading language version string: 1.30<br> OpenGL context flags: (none)<br> OpenGL extensions:<br> OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.0.6<br> OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00<br> OpenGL ES profile extensions:}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==== Checking vulkan support ====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
OpenGL is a graphics API specification and it has been superseded by the Vulkan api. To check support for Vulkan applications, you can install vulkan-tools and run 
{{UserCmdOutput|command=vkcube|result=Selected GPU 0: NVIDIA GeForce RTX 3050 Laptop GPU, type: DiscreteGpu}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
With integrated GPU you can select the GPU:
{{UserCmdOutput|command=vkcube --gpu_number 0|result=Selected GPU 0: NVIDIA GeForce RTX 3050 Laptop GPU, type: DiscreteGpu}}
{{UserCmdOutput|command=vkcube --gpu_number 1|result=Selected GPU 1: AMD Radeon Graphics (RADV RENOIR), type: IntegratedGpu
}}$
</div>

[[Category:Contents Page]]