Difference between pages "Hostname" and "Package:AMD Catalyst Video Drivers"

(Difference between pages)
 
 
Line 1: Line 1:
w.i.p
+
{{Ebuild
==Introduction==
+
|Summary=Accelerated ATI/AMD binary drivers for Radeon HD 5000 and newer chipsets.
A hostname is a unique name created to identify a machine on a network. In computer networking, a hostname  is a label that is assigned to a device connected to a computer network and that is used to identify the device in various forms of electronic communication such as the World Wide Web, e-mail or Usenet. Hostnames may be simple names consisting of a single word or phrase, or they may be structured.
+
|CatPkg=x11-drivers/ati-drivers
==Configuration==
+
|Maintainer=Drobbins
In Funtoo Linux <code>/etc/conf.d/hostname</code> is the only configuration file for setting a hostname. In OpenRC framework <code>/etc/conf.d/foo</code> is the configuration file for a corresponding Init script <code>/etc/init.d/foo</code>. With the case of hostname, default value in <code>/etc/conf.d/hostname</code> is set to ''localhost'', means when system boots and OpenRC's <code>/etc/init.d/hostname</code> script started a hostname getting only ''localhost'' name.  How it looks?  In your shell promt this will look in following way, an example for root:
+
|Homepage=
 +
|Repository=Funtoo Overlay
 +
|Overlay=Funtoo
 +
}}
 +
 
 +
{{Important|Version 14.12-r3 and above now include ATI GLESv2 and EGL libraries, which should improve stabilty with GNOME.}}
 +
 
 +
== Introduction ==
 +
 
 +
<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 ==
 +
 
 +
=== Blacklist Radeon and DRM Modules ===
 +
 
 +
To avoid having the open source Radeon drivers automatically load and ruin your day, create a blacklist file as follows:
 +
 
 +
{{file|name=/etc/modprobe.d/radeon.conf|desc=Prevent open source DRM and radeon drivers from loading|body=
 +
blacklist radeon
 +
blacklist drm
 +
}}
 +
 
 +
=== Configuring the kernel ===
 +
 
 +
Configure the kernel as follows. Note that the Direct Rendering Manager is '''not''' enabled. It's possible to have it selected as a kernel module, but should not be built-in to your kernel.
 +
 
 +
{{kernelop|desc=
 +
[*] 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=
 +
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 <code>/etc/make.conf</code>:
 
<console>
 
<console>
localhost ~ # ##i## Hello :)
+
# ##i##nano /etc/make.conf
 +
VIDEO_CARDS="fglrx"
 
</console>
 
</console>
Let's play a bit with a configuration. Open <code>/etc/conf.d/hostname</code> with your favorite editor and set a hostname of your choice.  Below, I will use a real examples  from one of my working test boxes.
+
=== Enabling AMD Catalyst Control Center ===
 +
 
 +
Then, add the following to <code>/etc/portage/package.use</code> if you would like to enable support for AMD Catalyst Control Center:
 
<console>
 
<console>
localhost ~ # ##i## nano /etc/conf.d/hostname
+
###i## nano /etc/portage/package.use
 +
x11-drivers/ati-drivers qt4
 
</console>
 
</console>
Let's set it to hostname="oleg-stable.host.funtoo.org". Save the file and restart  a hostname service:
+
 
 +
{{Note|If you are using a desktop or workstation profile, this USE flag will be enabled by default.}}
 +
 
 +
== Installing ==
 +
 
 +
=== Emerging the package ===
 +
 
 +
If you allready have emerged xorg-server, all you need to install the drivers is running the following command:
 
<console>
 
<console>
localhost ~ # ##i## service hostname restart
+
###i## emerge -av --changed-use --deep @world
 
</console>
 
</console>
Now, let's examine our changes, after a restarting a hostname
+
 
 +
otherwise you may install the drivers with
 
<console>
 
<console>
oleg-stable ~ # ##i## Hello :)
+
###i## emerge -av x11-drivers/ati-drivers
 
</console>
 
</console>
== Diving deeper==
+
 
Notice, that in above output we seeing a shortened hostname and not a FQDN (Fully Qualified Domain Name). Don't be frustrated. This is  how  default bash promt <code>PS1</code> set. To get nice promts, please, consult http://www.ibm.com/developerworks/library/l-tip-prompt/ <-- this one should be on Funtoo wiki :)
+
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.
Another way to test our settings is using a '''hostname''' command. Here we will show only  some of it's features. Let's try to execute '''hostname''' command:
+
 
 +
== Configuring ==
 +
 
 +
Next, set ati-drivers to manage the system's OpenGL and OpenCL implementations:  
 
<console>
 
<console>
oleg-stable ~ # ##i## hostname
+
###i## eselect opengl set ati
oleg-stable.host.funtoo.org
+
###i## eselect opencl set amd
 
</console>
 
</console>
Now we see our fully qualified domain name hostname just how we configured it in <code>/etc/conf.d/hostname</code> in above paragraph. To get a short hostname we need to set '''-s ''' (short) argument to hostname command.
+
 
 +
Afterwards, run <code>aticonfig</code> to modify the X-server configuration file to work with the ati-drivers:
 
<console>
 
<console>
oleg-stable ~ # ##i## hostname -s
+
###i## aticonfig --initial
oleg-stable
+
 
</console>
 
</console>
Good! Hostname offers more then just displaying a system host name but can also set one. Let's try:
+
 
 +
{{tip|If you would like to have a full-resolution framebuffer with ati-drivers, check out [[uvesafb| 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 display does not appear to allow windows to be dragged to it, you'll need to use the Catalyst Control Center {{c|amdcccle}} GUI configuration tool, which is enabled by the {{c|qt4}} USE variable.
 +
 
 +
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 using the following command, as root:
 +
 
 
<console>
 
<console>
oleg-stable ~ # ##i## hostname foo.bar.baz
+
# ##i##aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0
oleg-stable ~ # ##i## hostname
+
foo.bar.baz
+
 
</console>
 
</console>
As you can see, we changed a hostname on-the-fly. This is not recommended way.
 
{{fancywarning|Please, notice that using '''hostname''' command to configure will work temporary for a current session and will be reverted back to a value set in <code>/etc/conf.d/hostname</code> file with next system restart.}}
 
  
Now that we got a brief description of a hostname and basic configuration steps its time to reflect another important case, which is directly related to a Funtoo Linux hostname generation, a hosts.
+
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.
 +
 
 +
=== Compton with backend glx does not work well with ati-drivers ===
 +
Try running compton with the following switches:
 +
<console>
 +
###i## compton --backend glx --vsync none --paint-on-overlay
 +
</console>
  
==Hosts case==
+
[[Category:Video Cards]]
 +
[[Category:First Steps]]
 +
{{EbuildFooter}}

Revision as of 15:27, February 20, 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

IP Space Migration Continues

All Funtoo user containers in the 8.28 IP space will be moving into our new IP space (172.97) over the next few days. If you have DNS set up -- be sure to watch your container and update to the new IP! container.host.funtoo.org DNS will be updated after the move.
2015-08-27 by Drobbins
Drobbins

Funtoo Hosting IP Move

Funtoo user containers with IPs in the 72.18.x.x range will be gradually migrating to new IP addresses this week. If you have DNS entries for your containers, please be aware that your DNS will need to be updated.
2015-08-11 by Drobbins
Drobbins

New ARM Stages

New ARM Stages, built with a new toolchain, are now hitting mirrors. Existing ARM users should re-install using these stages (dated Aug 3, 2015 or later,) rather than upgrade using emerge.
2015-08-06 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.

Introduction

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

Blacklist Radeon and DRM Modules

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

Configuring the kernel

Configure the kernel as follows. Note that the Direct Rendering Manager is not enabled. It's possible to have it selected as a kernel module, but should not be built-in to your kernel.


[*] 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.

Installing

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:

# 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 display does not appear to allow windows to be dragged to it, you'll need to use the Catalyst Control Center amdcccle GUI configuration tool, which is enabled by the qt4 USE variable.

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 using the following command, as root:

# 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.

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