Difference between pages "Package:Awesome (Window Manager)" and "Package:AMD Catalyst Video Drivers"

(Difference between pages)
(Removed == USE Flags ==, as this will be added in on the sidebar by a new update Daniel is working on.)
 
(Removed == USE Flags ==, as this will be added in on the sidebar by a new update Daniel is working on. Changed some tt's to code's.)
 
Line 1: Line 1:
 
{{Ebuild
 
{{Ebuild
|Summary=A dynamic floating and tiling window manager.
+
|Summary=Accelerated ATI/AMD binary drivers for Radeon HD 5000 and newer chipsets.
|CatPkg=x11-wm/awesome
+
|CatPkg=x11-drivers/ati-drivers
|Maintainer=
+
|Maintainer=Drobbins
|Homepage=http://awesome.naquadah.org/
+
|Repository=Funtoo Overlay
 +
|Overlay=Funtoo
 
}}
 
}}
 +
== Introduction ==
  
== About Awesome ==
+
<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.
  
Awesome is a highly configurable window manager distributed under GPL-2 license. It handles both '''tiling and floating''' layouts. You can go into a '''fine-grained customization''' to suit your needs with '''Lua scripting'''. As a window manager, awesome is an ideal choice if you plan to ''get rid of your mouse''.
+
== Preparing to Install ==
 +
=== Configuring the 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) --->
 +
}}
  
=== Vocabulary ===
+
{{fancynote| 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
 +
}}
  
;Screen: A physical monitor plugged into your computer.
+
=== Editing make.conf ===
;Client: A window.
+
;Tag: A tag is something like a workspace or a desktop that you may find in other window managers. However, it is slightly more flexible as you can attach a ''client'' to multiple tags. Moreover, each ''screen'' has its own range of tags.
+
;Layout: A layout is a way to arrange your ''clients'' in the current tag (eg. floating, horizontaly tiled, verticaly tiled, focused client full-screen, ...)
+
;Widget: A widget is a box that can contain text, images or more advanced objects. It enables you to add pieces of information in the status bar (at the top-right of each ''screen'') such as the time, the volume level or your battery load. You can also add widgets in the title bar of a ''client''.
+
  
== Installation ==
+
Add the following to your <code>/etc/make.conf</code>:
 +
<console>
 +
# ##i##nano /etc/make.conf
 +
VIDEO_CARDS="fglrx"
 +
</console>
 +
=== Editing package.use ===
  
Just emerge it:
+
Then, add the following to <code>/etc/portage/package.use</code>:
 +
<console>
 +
###i## nano /etc/portage/package.use
 +
x11-drivers/ati-drivers qt4
 +
</console>
 +
{{fancynote| Feel free to add or remove use flags as you see fit. For example, if you do not want amdcccle support, remove the qt4 use flag.}}
 +
== Installing ==
  
 +
=== Emerging the package ===
 +
To emerge the drivers, run the following command:
 
<console>
 
<console>
###i## emerge -a awesome
+
###i## emerge -av --changed-use --deep @world
 
</console>
 
</console>
  
Then you can add this line to your <code>~/.xinitrc</code>:
+
== Configuring ==
  
{{file|name=~/.xinitrc|body=
+
Next, set ati-drivers to manage the system's OpenGL implementation:
exec ck-launch-session dbus-launch --sh-syntax --exit-with-session awesome
+
<console>
}}
+
###i## eselect opengl set ati
 +
</console>
  
And run <code>xinit</code> to launch awesome. You can also configure a display manager instead, but this is not covered in this document.
+
Afterwards, run <code>aticonfig</code> to modify the X-server configuration file to work with the ati-drivers:
 +
<console>
 +
###i## aticonfig --initial
 +
</console>
  
== Getting Started ==
+
{{fancytip| If you would like to have a full-resolution framebuffer with ati-drivers, check out [[uvesafb| uvesafb]]}}
  
So, you should see a nice awesome background and a top bar which includes your tags on the left (from 1 to 9), the status bar (containing a clock widget) on the right and, on the very left, an icon representing the current layout.
+
== 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:
  
You can switch against tags by typing <code>Mod4 + [1..9]</code> or <code>Mod4 + Left/Right</code>. Where Mod4 is the "Super" key and [1..9] any digit from 1 to 9. Mod4 is the default modifier for awesome key bindings, yet you can configure another one (See [[#Configuration]]).
+
<console>
 +
# ##i##aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0
 +
</console>
  
To run a program, hit <code>Mod4 + r</code>. You will be prompted for a command to run (on the top left corner, next to the tags list). Open some clients (3 or 4) and hit <code>Mod4 + Space</code>. This will switch to the next layout. Go ahead and try available layouts (notice the layout icon on the top right corner). You can also switch to the previous layout by hitting <code>Mod4 + Shift + Space</code>. To understand how each layout is arranged, you might want to add some more clients to the current tag. You can also toggle full screen for the current focused client with <code>Mod4 + f</code>.
+
You may need to restart your X session.
  
Here is some other interesting key bindings:
+
=== GNOME 3 windows only refresh when I drag them. ===
 +
This is a known issue, reported in [http://bugs.funtoo.org/browse/FL-1130 Funtoo Bug 1130]. This issue has been fixed by addressing a bug in cogl -- upgrade to cogl-1.12.2-r2 to fix it.
  
* <code>Mod4 + h/l</code>: Resize clients (this will not work on some layouts)
+
=== Compton with backend glx does not work well with ati-drivers ===
* <code>Mod4 + Ctrl + r</code>: Restart awesome (useful when you want to test the configuration file you just edited)
+
Try running compton with the following switches:
* <code>Mod4 + Shift + q</code>: Quit awesome (note that this will not exit your display manager if ever you have one)
+
<console>
 
+
###i## compton --backend glx --vsync none --paint-on-overlay
There's plenty of other key bindings. We will see them, how to change them and how to create your own in the next section.
+
</console>
 
+
== Configuration ==
+
 
+
Awesome user configuration files are located in <code>~/.config/awesome/</code>. For now, a single file called <code>rc.lua</code> should lie in this directory. It contains the default configuration (including widgets, tags, key bindings, ...). Note that if you don't know Lua, you can still proceed some customization. As far as I'm concerned, I only had to learn Lua basics when I started to create my own widgets.
+
 
+
{{fancynote|The system-wide configuration files are located in <code>/etc/xdg/awesome/</code>.}}
+
 
+
So, the first thing you might want to do is editing the default terminal (run when you hit <code>Mod4 + Return</code>). You can also change the fallback editor, but awesome uses <code>$EDITOR</code> to find your favorite one. This can be done on these lines:
+
{{file|name=~/.config/awesome/rc.lua|lang=lua|body=
+
terminal = "xterm"
+
editor = os.getenv("EDITOR") or "nano"
+
editor_cmd = terminal .. " -e " .. editor
+
}}
+
 
+
For strings, <code>..</code> is the concatenation operator in Lua.
+
 
+
I think the modkey setting is well-documented enough, so next will be the layouts setting:
+
 
+
{{file|name=~/.config/awesome/rc.lua|lang=lua|body=
+
local layouts =
+
{
+
    awful.layouts.suit.floating,
+
    awful.layouts.suit.tile,
+
    awful.layouts.suit.tile.left,
+
    awful.layouts.suit.tile.bottom,
+
    awful.layouts.suit.tile.top,
+
    awful.layouts.suit.fair,
+
    awful.layouts.suit.fair.horizontal,
+
    awful.layouts.suit.spiral,
+
    awful.layouts.suit.spiral.dwindle,
+
    awful.layouts.suit.max,
+
    awful.layouts.suit.max.fullscreen,
+
    awful.layouts.suit.magnifier
+
}
+
}}
+
 
+
These are the default layouts, but you can download some others and create your own. You probably won't do it now, however you might want to change the order. Personally, I don't like to have the floating layout as the default one.
+
 
+
I won't go further about this file, so I would suggest you to go on browsing this file to fetch interesting settings to change. I think one of the most important section you want to check out is "Key bindings". You will see all existing mappings and what they do. As an example, find the following lines at the beginning of the "{{{ Key bindings" section:
+
 
+
{{file|name=~/.config/awesome/rc.lua|lang=lua|body=
+
    awful.key({modkey,          },  "j",
+
        function()
+
            awful.client.focus.byidx( 1)
+
            if client.focus then client.focus:raise() end
+
        end),
+
    awful.key({modkey,          },  "k",
+
        function()
+
            awful.client.focus.byidx(-1)
+
            if client.focus then client.focus:raise() end
+
        end),
+
}}
+
 
+
This enables you to move the focus across the clients in this tag. You may be used to <code>Alt + Tab</code> and <code>Alt + Shift + Tab</code> for that. So why wouldn't you change it to suit what you are used to ?
+
 
+
{{file|name=~/.config/awesome/rc.lua|lang=lua|body=
+
    awful.key({"Mod1", "Shift"  },  "Tab", -- Notice the "Mod1" for Alt key instead of modkey (="Mod4")
+
        function()
+
            awful.client.focus.byidx( 1)
+
            if client.focus then client.focus:raise() end
+
        end),
+
    awful.key({"Mod1", "Shift"  },  "Tab",
+
        function()
+
            awful.client.focus.byidx(-1)
+
            if client.focus then client.focus:raise() end
+
        end),
+
}}
+
  
 +
[[Category:Video Cards]]
 +
[[Category:First Steps]]
 
{{EbuildFooter}}
 
{{EbuildFooter}}

Revision as of 23:20, September 16, 2014

x11-drivers/ati-drivers


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

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

AMD Catalyst Video Drivers

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

Configuring the 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"

Editing package.use

Then, add the following to /etc/portage/package.use:

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

Note

Feel free to add or remove use flags as you see fit. For example, if you do not want amdcccle support, remove the qt4 use flag.

Installing

Emerging the package

To emerge the drivers, run the following command:

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

Configuring

Next, set ati-drivers to manage the system's OpenGL implementation:

# eselect opengl set ati

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

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 may need to restart your X session.

GNOME 3 windows only refresh when I drag them.

This is a known issue, reported in Funtoo Bug 1130. This issue has been fixed by addressing a bug in cogl -- upgrade to cogl-1.12.2-r2 to fix it.

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