Difference between pages "Package:NVIDIA Linux Display Drivers" and "Package:AMD Catalyst Video Drivers"

(Difference between pages)
 
 
Line 1: Line 1:
 
{{Ebuild
 
{{Ebuild
|Summary=NVIDIA accelerated graphics driver
+
|Summary=Accelerated ATI/AMD binary drivers for Radeon HD 5000 and newer chipsets.
|CatPkg=x11-drivers/nvidia-drivers
+
|CatPkg=x11-drivers/ati-drivers
|Maintainer=Ricardo Bastos
+
|Maintainer=Drobbins
 +
|Homepage=
 
|Repository=Funtoo Overlay
 
|Repository=Funtoo Overlay
 
|Overlay=Funtoo
 
|Overlay=Funtoo
 
}}
 
}}
== Introduction ==
 
  
NVidia have proprietary graphics drivers for Linux under binary blob. The alternative open source driver is nouveau.
+
{{Important|Version 14.12-r3 and above now include ATI GLESv2 and EGL libraries, which should improve stabilty with GNOME.}}
 +
 
 +
<tt>x11-drivers/ati-drivers</tt> (often referred to as "<tt>fglrx</tt>", the name of its kernel module) is the proprietary, accelerated driver for AMD (ATI) graphics cards.  
  
 
=== Preparing to Install ===
 
=== Preparing to Install ===
  
==== Hardware compatibility and driver versions ====  
+
==== Default Kernel ====
  
Currently there are five meta versions of nVidia Linux drivers each of which supports a specific group of GPUs. To check the type of driver that is related to your video card, check the link on this page of the official nVidia:
+
If you are using the default kernel -- one like debian-sources that was built automatically, then you'll want to blacklist a few modules to prevent them from loading and interfering with the AMD Catalyst module. To avoid having the open source Radeon drivers automatically load and ruin your day, create a blacklist file as follows:
  
[www.nvidia.com/object/IO_32667.html]
+
{{file|name=/etc/modprobe.d/radeon.conf|desc=Prevent open source DRM and radeon drivers from loading|body=
 +
blacklist radeon
 +
blacklist drm
 +
}}
  
If you have identified as your driver version 337.25, for example, you need the mask(s) driver(s) latest(s) to which you want to install.
+
==== Custom Kernel ====
  
<console>
+
If you are building a custom kernel, rather than blacklisting modules as above, you can simply ensure that the Direct Rendering Manager and in-kernel Radeon drivers are not enabled. If you do build them as modules, you will need to blacklist them as above. Also ensure that the following kernel options are enabled.
###i## echo “>x11-drivers/nvidia-drivers-340” >> /etc/portage/package.mask
+
</console>
+
 
+
==== The required kernel options ====
+
  
 
{{kernelop|desc=
 
{{kernelop|desc=
 
[*] Enable loadable module support
 
[*] Enable loadable module support
 +
Processor type and features --->
 +
      [*] MTRR (Memory Type Range Register) support
 +
Bus options (PCI etc.) --->
 +
      [*] PCI Express Port Bus Support
 +
      [*] Message Signaled Interrupts (MSI and MSI-X)
 +
Device Drivers --->
 +
      Graphics support --->
 +
            < > Direct Rendering Manager (xFree86 4.1.0 and higher DRI support) --->
 
}}
 
}}
  
 +
{{note|If you need support for AGP cards, enable the following kernel options:}}
 
{{kernelop|desc=
 
{{kernelop|desc=
[*] MTRR (Memory Type Range Register) support
+
Device Drivers --->
 +
      Graphics support --->
 +
            <*> /dev/agpgart (AGP Support) --->
 +
                  Select an appropriate AGP driver:
 +
                  <*> AMD Opteron/Athlon64 on-CPU GART support
 
}}
 
}}
  
To we made a successful compilation of the legacy nVidia driver, we set before the removal of the native framebuffer drivers into the kernel in order to avoid conflicts for x86 and AMD64 processors, in this case.
+
=== Editing make.conf ===
  
{{kernelop|desc=
+
Add the following to your <code>/etc/make.conf</code>:
Device Drivers >
+
<console>
  Graphics support >
+
# ##i##nano /etc/make.conf
    <*> Support for frame buffer devices >
+
VIDEO_CARDS="fglrx"
      <> nVidia Framebuffer Support
+
</console>
      <> nVidia Riva support
+
}}
+
  
{{fancytip| An alternative is to [[uvesafb| uvesafb]] framebuffer, which can be installed in parallel with nvidia-drivers }}
+
=== Enabling AMD Catalyst Control Center ===
  
==== Installation ====
+
Then, add the following to <code>/etc/portage/package.use</code> if you would like to enable support for AMD Catalyst Control Center:
 +
<console>
 +
###i## nano /etc/portage/package.use
 +
x11-drivers/ati-drivers qt4
 +
</console>
  
Upgrade and/or configure VIDEO_CARDS variable "nvidia" in /etc/make.conf. This will serve to while you are installing the Server X, the correct version of nvidia-drivers to be provided for you.
+
{{Note|If you are using a desktop or workstation profile, this USE flag will be enabled by default.}}
  
{{fancynote| Installing to the driver with the option in gtk use flags will make it installed the media-video/nvidia-settings which is a graphical tool for monitoring and various settings for your video card}}
+
=== Emerging the package ===
  
==== Emerging the package ====
+
If you allready have emerged xorg-server, all you need to install the drivers is running the following command:
 +
<console>
 +
###i## emerge -av --changed-use --deep @world
 +
</console>
  
 +
otherwise you may install the drivers with
 
<console>
 
<console>
###i## emerge x11-drivers/nvidia-drives
+
###i## emerge -av x11-drivers/ati-drivers
 
</console>
 
</console>
  
When the installation is complete run '''modprobe''' nvidia module to read kernel memory.
+
Before using the driver, ensure that the "fglrx" module has been loaded -- run {{c|modprobe fglrx}} as root  -- it should return with no error. If the module can't be found, run {{c|depmod -a}} as root -- then the modprobe command should work. If you are switching from the open source Radeon driver, then shutting down your desktop and rebooting your system (be sure to disable xdm) may be required to get the new "fglrx" module to load cleanly.
 +
 
 +
=== Configuring ===
 +
 
 +
Next, set ati-drivers to manage the system's OpenGL and OpenCL implementations.
 +
Doing this is particulary important for desktop environments like GNOME, which use hardware acceleration by default. Not doing this will result in the GNOME display manager not being able to start!
  
 
<console>
 
<console>
###i## lsmod | grep nvidia
+
###i## eselect opengl set ati
 +
###i## eselect opencl set amd
 
</console>
 
</console>
If an update before remove the old module
+
 
 +
Afterwards, run <code>aticonfig</code> to modify the X-server configuration file to work with the ati-drivers:
 
<console>
 
<console>
###i## rmmod nvidia
+
###i## aticonfig --initial
###i## modprobe nvidia
+
 
</console>
 
</console>
  
==== Testing your Video Card ====
+
{{tip|If you would like to have a full-resolution framebuffer with ati-drivers, check out [[uvesafb| uvesafb]]}}
  
To test your video card run the glxinfo program, which is part of the mesa-progs package. This will check if direct rendering is enabled.
+
=== Multi-Head Display ===
<console>
+
$ ##i##glxinfo | grep direct
+
</console>
+
  
== Configuring ==
+
There are a couple of options for setting up a multi-head display. For some systems, all you need to do is plug in your additional monitor, and it will be detected by your desktop environment, and will work.
  
==== Loading at boot ====
+
If your second monitor does not display anything at all, then play around with your X configuration. Try using the following command to generate a new X config:
  
To automate the loading of the module when you boot your system, add '''nvidia''' in /etc/conf.d/modules.
+
{{console|body=
 +
# ##i##aticonfig --initial=dual-head
 +
}}
  
==== Integration with X Server ====
+
You can use the {{c|--screen-layout={left|right|above|below}}} option to specify the relationship of the second screen to the first.
  
When your X server is installed, the existing logo /etc/X11/xorg.conf you can run the nvidia-xconfig which will set in xorg.conf to identify the video card among other possible configurations.
+
For more than two heads, or multiple cards, you can use the following approach to generate an appropriate X config. First, list adapters to see what adapters are available:
  
{{file|name=/etc/X11/xorg.conf|body=
+
{{console|body=
Section "Device"
+
# ##i##aticonfig --list-adapters
    Identifier    "nvidia"
+
    Driver        "nvidia"
+
    VendorName    "NVIDIA Corporation"
+
    BoardName      "[Nome] [Modelo]"
+
EndSection
+
 
}}
 
}}
  
==== Enabling support nVidia ====
+
Now, a variant of one of the following commands to generate an X configuration for your needs:
Include the use flag in '''nvidia''' /etc/portage/make.conf so due to applications that make use of this advantage may withdraw.
+
 
 +
{{console|body=
 +
# ##i##aticonfig --initial --heads=4 --adapter=1
 +
# ##i##aticonfig --adapter=0,2 --initial
 +
# ##i##aticonfig --adapter=all --initial
 +
# ##i##aticonfig --xinerama=on
 +
}}
 +
 
 +
One you have your displays enabled so that your mouse pointer can move to all displays, you still may not be able to drag windows to certain monitors. In this situation, each monitor is probably configured as a separate X screen, and you'll need to use the Catalyst Control Center {{c|amdcccle}} GUI configuration tool to tie them together. The Catalyst Control Center is installed when the {{c|qt4}} USE variable is enabled.
 +
 
 +
Open up a graphical terminal, and become root by typing {{c|su -}} -- your user will need to be in the {{c|wheel}} group to do this:
 +
 
 +
{{console|body=
 +
$ ##i##su -
 +
Password: ##i##*******
 +
# source /etc/profile
 +
# amdcccle
 +
}}
 +
 
 +
[[File:amdcccle.png|class=img-responsive|center]]
 +
Navigate to Display Manager, and choose the option {{c|Multi-display desktop with display(s) X}} for each display. Then, drag and drop the blue displays to arrange them to match how they are arranged in front of you. Click {{c|OK}}. The Catalyst Control Center will tell you that you will need to restart your system for the changes to take effect. Simply log out if you are running {{c|xdm}}, or end your X session, and start it up again. You should now have a fully-functioning multi-head display.
 +
 
 +
=== Troubleshooting ===
 +
==== I am using a HDMI connection, and my monitor's display has a black border around it. ====
 +
Disable overscan as follows:
 +
 
 +
<console>
 +
$ ##i##su -
 +
Password: ##i##*********
 +
# ##i##aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0
 +
</console>
 +
 
 +
You will need to restart your X session for the changes to take effect. If you are using a display manager, logging out and back in again should cause the new settings to be visible.
 +
 
 +
==== The tabs in Google Chrome are becoming garbled/corrupted ====
  
==== Enabling OpenGL / OpenCL ====
+
New versions of Google Chrome use hardware acceleration by default which appears to have rendering issues with AMD's drivers. To work around this, disable hardware acceleration in Google Chrome by going to {{c|Settings}}, {{c|Show advanced settings...}} and then uncheck the {{c|Use hardware acceleration when available (requires Chrome restart)}}. Once Chrome is restarted, the rendering problem should be resolved.
As a requirement, make sure that the Xorg server is not in use during this change. To enable OpenGL and OpenCL.
+
  
 +
==== Compton with backend glx does not work well with ati-drivers ====
 +
Try running compton with the following switches:
 
<console>
 
<console>
###i## eselect opengl set nvidia
+
###i## compton --backend glx --vsync none --paint-on-overlay
###i## eselect opencl set nvidia
+
 
</console>
 
</console>
  

Revision as of 17:42, February 22, 2015

x11-drivers/ati-drivers


Current Maintainer(s):Daniel Robbins
Source Repository:Repository:Funtoo Overlay


Summary: Accelerated ATI/AMD binary drivers for Radeon HD 5000 and newer chipsets.

Use Flags

qt4
Install qt4 dependent optional tools (e.g Catalyst Control Panel)
modules
Build the kernel modules
disable-watermark
Do a potentially dangerous binary search and replace to disable watermark
pax_kernel
Enable pax kernel specific patches
vaapi
Enabled Video Acceleration API

News

Drobbins

Perl Updates

Gentoo has bumped perl from 5.20 to 5.22. Be sure to run perl-cleaner --all after the upgrade.
2015-07-25 by Drobbins
Drobbins

ARM Rebuild

ARM systems will use new stage3's that are not compatible with earlier versions.
2015-06-27 by Drobbins
Drobbins

ABI X86 64 and 32

Funtoo Linux has new 32-bit compatibility libraries inherited from Gentoo. Learn about them here.
2015-06-18 by Drobbins
More...

AMD Catalyst Video Drivers

Tip

We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.


Important

Version 14.12-r3 and above now include ATI GLESv2 and EGL libraries, which should improve stabilty with GNOME.

x11-drivers/ati-drivers (often referred to as "fglrx", the name of its kernel module) is the proprietary, accelerated driver for AMD (ATI) graphics cards.

Preparing to Install

Default Kernel

If you are using the default kernel -- one like debian-sources that was built automatically, then you'll want to blacklist a few modules to prevent them from loading and interfering with the AMD Catalyst module. To avoid having the open source Radeon drivers automatically load and ruin your day, create a blacklist file as follows:

/etc/modprobe.d/radeon.conf - Prevent open source DRM and radeon drivers from loading
blacklist radeon
blacklist drm

Custom Kernel

If you are building a custom kernel, rather than blacklisting modules as above, you can simply ensure that the Direct Rendering Manager and in-kernel Radeon drivers are not enabled. If you do build them as modules, you will need to blacklist them as above. Also ensure that the following kernel options are enabled.


[*] Enable loadable module support
Processor type and features --->
      [*] MTRR (Memory Type Range Register) support
Bus options (PCI etc.) --->
      [*] PCI Express Port Bus Support
      [*] Message Signaled Interrupts (MSI and MSI-X)
Device Drivers --->
      Graphics support --->
            < > Direct Rendering Manager (xFree86 4.1.0 and higher DRI support) --->
Note

If you need support for AGP cards, enable the following kernel options:

Device Drivers --->
      Graphics support --->
            <*> /dev/agpgart (AGP Support) --->
                  Select an appropriate AGP driver:
                  <*> AMD Opteron/Athlon64 on-CPU GART support

Editing make.conf

Add the following to your /etc/make.conf:

# nano /etc/make.conf
VIDEO_CARDS="fglrx"

Enabling AMD Catalyst Control Center

Then, add the following to /etc/portage/package.use if you would like to enable support for AMD Catalyst Control Center:

# nano /etc/portage/package.use
x11-drivers/ati-drivers qt4
Note

If you are using a desktop or workstation profile, this USE flag will be enabled by default.

Emerging the package

If you allready have emerged xorg-server, all you need to install the drivers is running the following command:

# emerge -av --changed-use --deep @world

otherwise you may install the drivers with

# emerge -av x11-drivers/ati-drivers

Before using the driver, ensure that the "fglrx" module has been loaded -- run modprobe fglrx as root -- it should return with no error. If the module can't be found, run depmod -a as root -- then the modprobe command should work. If you are switching from the open source Radeon driver, then shutting down your desktop and rebooting your system (be sure to disable xdm) may be required to get the new "fglrx" module to load cleanly.

Configuring

Next, set ati-drivers to manage the system's OpenGL and OpenCL implementations. Doing this is particulary important for desktop environments like GNOME, which use hardware acceleration by default. Not doing this will result in the GNOME display manager not being able to start!

# eselect opengl set ati
# eselect opencl set amd

Afterwards, run aticonfig to modify the X-server configuration file to work with the ati-drivers:

# aticonfig --initial
Tip

If you would like to have a full-resolution framebuffer with ati-drivers, check out uvesafb

Multi-Head Display

There are a couple of options for setting up a multi-head display. For some systems, all you need to do is plug in your additional monitor, and it will be detected by your desktop environment, and will work.

If your second monitor does not display anything at all, then play around with your X configuration. Try using the following command to generate a new X config:

# aticonfig --initial=dual-head


You can use the right} option to specify the relationship of the second screen to the first.

For more than two heads, or multiple cards, you can use the following approach to generate an appropriate X config. First, list adapters to see what adapters are available:

# aticonfig --list-adapters


Now, a variant of one of the following commands to generate an X configuration for your needs:

# aticonfig --initial --heads=4 --adapter=1 
# aticonfig --adapter=0,2 --initial
# aticonfig --adapter=all --initial
# aticonfig --xinerama=on


One you have your displays enabled so that your mouse pointer can move to all displays, you still may not be able to drag windows to certain monitors. In this situation, each monitor is probably configured as a separate X screen, and you'll need to use the Catalyst Control Center amdcccle GUI configuration tool to tie them together. The Catalyst Control Center is installed when the qt4 USE variable is enabled.

Open up a graphical terminal, and become root by typing su - -- your user will need to be in the wheel group to do this:

$ su -
Password: *******
# source /etc/profile
# amdcccle


Amdcccle.png

Navigate to Display Manager, and choose the option Multi-display desktop with display(s) X for each display. Then, drag and drop the blue displays to arrange them to match how they are arranged in front of you. Click OK. The Catalyst Control Center will tell you that you will need to restart your system for the changes to take effect. Simply log out if you are running xdm, or end your X session, and start it up again. You should now have a fully-functioning multi-head display.

Troubleshooting

I am using a HDMI connection, and my monitor's display has a black border around it.

Disable overscan as follows:

$ su -
Password: *********
# aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0

You will need to restart your X session for the changes to take effect. If you are using a display manager, logging out and back in again should cause the new settings to be visible.

The tabs in Google Chrome are becoming garbled/corrupted

New versions of Google Chrome use hardware acceleration by default which appears to have rendering issues with AMD's drivers. To work around this, disable hardware acceleration in Google Chrome by going to Settings, Show advanced settings... and then uncheck the Use hardware acceleration when available (requires Chrome restart). Once Chrome is restarted, the rendering problem should be resolved.

Compton with backend glx does not work well with ati-drivers

Try running compton with the following switches:

# compton --backend glx --vsync none --paint-on-overlay