The following article provides information about Hybrid Graphics on a Dell PC using the Ubuntu operating system.
This article is going to go over the differences between Discrete Graphics and Video Card Graphics and what Proprietary Drivers and Open Source Drivers means for your Video output. This article deals with Dell PCs using the Ubuntu operating system and the common videos issues you are likely to experience over time. This article is as much a reference guide as it is a troubleshooting guide.
Please remember that Dell supports the Hardware that ships with the unit and the reinstall or recovery of the Operating system that came with the unit. I hope you find the following information useful.
Most Notebook and AIO (All in One) systems have the capability of having two GPUs. The first is the integrated GPU and is usually part of the CPU and the other is called the discrete GPU. The discrete GPU is an optional extra and is always more powerful than the integrated GPU. If your system has a hardware mux it will be able to switch between GPUs.
While add-on Video cards are technically a second GPU added to the Integrated GPU, they are not usually included in Hybrid Graphics. Most Desktop BIOS settings means that when a Video card is plugged in, it automatically takes the place of the Integrated GPU which is no longer used.
This is another term for Binary drivers, which are closed source drivers provided by the hardware manufacturers of the secondary GPU. Some hardware devices may require this kind of driver in order to function fully and properly. Unfortunately there is no way for developers to affect this type of driver and work on any bugs found with it.
Open source drivers have been created by the Linux community to function with certain GPUs. They are most commonly used with GPUs where the manufacturer doesn't supply Linux versions and there is no proprietary driver available. The benefits of open source is that they are community supported and bugs tend to be fixed on an ongoing basis. The disadvantage is that they won't fully support all the features of every GPU.
The first thing is to correctly identify your Hardware.
You can determine you make and model using the command below in Terminal :
You can get more detailed information by running :
For a list of supported hardware please check out the article below :
There are two ways to install a proprietary driver in Ubuntu :
The first way is through the GUI (Graphical User Interface) Hardware Manager window.
Open Software Center and go to Edit
Select Additional Drivers
It will check what is already installed and download a list of all the other proprietary drivers available and any updates.
You will now be able to enable / disable a driver. If there are multiple versions, please remember it's best to use the most recent one that applies to your hardware. It's usually got the best chance of working and containing the most recent fixes for any issues.
The second way is through the CLI (Command Line Interface)
Open a Terminal Window (CTRL + ALT + T)
The example below shows commands for Nvidia:
There are a number of open source drivers that cover a number of manufacturers.
I've listed some current programmes below :
This is the default driver and supports most cards without acceleration and has a limited set of possible resolutions.
This is the latest open source driver to support the Intel Graphics
This is another AMD Radeon driver which is looking to support 3D and is made up of radeon, r200, r300g, r600g and radeonsi.
This driver is based entirely on information gained through backward engineering for Nvidia devices.
This driver is also based entirely on information gained through backward engineering for Nvidia Tegra devices.
This company supplied open source drivers for all devices older than G550, any that are newer than G550 use a closed source driver.
This supports the S3 Chrome GPU, all other S3 products are closed source.
This driver had support built in for the ARM Mali GPU.
These drivers support the Vivante GC400, GC800 and the GC1000 series.
This supports the Qualcomm Adreno GPU series.
This was an attempt to support the Videocore GPU series, but Broadcom who make the Videocore series release the source code for the IV graphics core as part of the second anniversary of the Broadcom Raspberry Pi.
vga_switcheroo is what allows you to switch between GPUs if your machine has a hardware mux.
To check whether your kernel is compiled with the correct option you can examine the file config-2.6.nn-mm-generic in the /boot directory :
vga_switcheroo mechanism works when the kernel is booted with either the modeset=1 kernel option and/or the nomodeset option being absent. To test if vga_switcheroo is enabled, look for the switch file :
If vga_switcheroo is available, you can switch between GPUs. Be prepared for something to go wrong and the system to lockup as the fact this file is there doesn't gaurantee the machine is supported.
Use this command to turn on the GPU that is currently disconnected, but it doesn't switch the outputs :
This command connects the integrated graphics with the outputs :
This command connects the discrete graphics with the outputs :
This command turns off the graphics card that is currently disconnected :
This command lets you check the current state of the hybrid graphics. There will usually be two lines of output - one should show Pwr and the other shows Off :
Are you experiencing the issue outside of the Ubuntu operating system?
If you are seeing the issue outside the operating system then please go to either this article for an External Screen or this article for an Internal Screen to troubleshoot further.
If you aren't seeing the issue outside the operating system then:
In the Grub bootloader menu - select boot your computer into recovery mode
Choose resume normal boot from the recovery menu (This will attempt a normal boot with failsafe video settings.)
If the normal boot doesn't resolve the issue, then you can go back into recovery mode and select the run in failsafe graphic mode option.
If you still have no video then you may be looking at an operating system reinstall or you can drop to the root shell prompt if you have the experience or a guide to troubleshoot further using Terminal.
Are you experiencing the issue outside of the Ubuntu operating system?
If you are seeing the issue outside the operating system then please go to either this article for an External Screen or this article for an Internal Screen to troubleshoot further.
If you aren't seeing the issue outside the operating system then:
Performance Issues and Video Stability can be helped by disabling the visual effects. (This involves changing to the 2D desktop environment.)
Open Terminal (CTRL + ALT + T) and install compiz settings manager:
On Ubuntu Dash, search for compiz settings manager and open the application and disable/uncheck:
Effects > Animations, Fading Windows, Windows Decoration
If you still have distorted video then you may be looking at an operating system reinstall to resolve.
The default resolution for Ubuntu 14.04 is 640x480 at the low end and 1024x768 at the top.
If you are using the default video GPU and only see the low end of 640x480 then it's recommended that you run Xdiagnose and tick all 3 Debug options, as this has been known to restore the screen to the upper default 1024x768.
To get resolutions above 1024x768 you will need to use the xrandr command in Terminal to add a new mode with the new resolution. (This isn't usually kept past a Reboot.)
If you are an experienced Ubuntu user and are looking to keep the changes past a reboot then you can look to add the xrandr newmode and addmode commands into /etc/gdm/Init/Default just before "initctl ..."
It should look similar to the code below :
If the Fn shortcut keys for adjusting the brightness aren't working or you are looking for more control than they provide, then there are applets you can install that will give you a GUI (Graphical User Interface) window with various display settings. If you are an experienced Ubuntu user there are Terminal commands such as gksu and leafpad that will let you create a file to resolve the Fn shortcuts.
Again for experienced users, adding a Grub parameter may be all you need. You will need gksu and leafpad installed and to be operating as admin with sudo control. You need to replace the existing line GRUB_CMDLINE_LINUX="" with the new line GRUB_CMDLINE_LINUX="acpi_osi=Linux" in the Grub text file and then update it in Terminal. If the brightness keys on the keyboard still don't work, you can replace GRUB_CMDLINE_LINUX="acpi_osi=Linux" with GRUB_CMDLINE_LINUX="acpi_backlight=vendor" and try again. If you still have issues after this, try the next method.
The first step is to install xbacklight if it isn't already on your system. Create a startup application called brightness, by searching for startup applications and clicking Add. Give the new application the command below and reboot the system. If it doesn't work, try the next method.
The first thing to do is open a Terminal window and identify the exact type of card you have and the BusID. (The BusID has five (5) digits 00:00.0 , take a note of it.)
Combine the BusID with the following two commands to dim and increase the brightness on your display. (You will need to experiment to see which settings suit you best.)
In order to make this change survive a reboot you will need gksu and leafpad installed. You need to open the /etc/re.local file in leafpad and add this line setpci -s 00:00.0 F4.B=50 just above the existing line that says exit 0:
If you're still having problems after this, then the next method is a last resort and only intended for those users who are experienced with Ubuntu.
you can even use xrandr to affect the brightness output. (I would recommend you be sure about the hardware of your machine and are confident in whichever guide you find to use, before doing too much in Terminal with the sudo command.)
Does your graphics card fan run at full speed? You can create a script using the following command to run before shutdown :
If you have turned off the unused discrete card and your laptop freezes after suspending and trying to wake, you can make a new file called 11_switcheroo_suspend under /etc/pm/sleep.d and make sure the file is executable :
Depending on which GPU is started on Boot - you may have an issue with it needing the system to be connected to mains power.


Article ID: SLN298475
Last Date Modified: 09/06/2017 04:45 AM
Thank you for your feedback.