Difference between pages "Package:AMD Catalyst Video Drivers" and "Install/BootLoader"

(Difference between pages)
(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.)
 
(Installing GRUB)
 
Line 1: Line 1:
{{Ebuild
+
<noinclude>
|Summary=Accelerated ATI/AMD binary drivers for Radeon HD 5000 and newer chipsets.
+
{{InstallPart|boot loader configuration}}
|CatPkg=x11-drivers/ati-drivers
+
</noinclude>
|Maintainer=Drobbins
+
=== Installing a Bootloader ===
|Repository=Funtoo Overlay
+
|Overlay=Funtoo
+
}}
+
== 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.  
+
These install instructions show you how to use GRUB to boot using BIOS (old-school) or UEFI (new-school).
  
== Preparing to Install ==
+
==== Old School (BIOS) ====
=== 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) --->
+
}}
+
  
{{fancynote| If you need support for AGP cards, enable the following kernel options:}}
+
If you're using the BIOS to boot, setting up GRUB, the bootloader, is pretty easy.
{{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 ===
+
To use this recommended boot method, first emerge <code>boot-update</code>. This will also cause <code>grub-2</code> to be merged, since it is a dependency of <code>boot-update</code>.
  
Add the following to your <code>/etc/make.conf</code>:
 
 
<console>
 
<console>
# ##i##nano /etc/make.conf
+
(chroot) # ##i##emerge boot-update
VIDEO_CARDS="fglrx"
+
 
</console>
 
</console>
=== Editing package.use ===
 
  
Then, add the following to <code>/etc/portage/package.use</code>:
+
Then, edit <code>/etc/boot.conf</code> and specify "<code>Funtoo Linux genkernel</code>" as the <code>default</code> setting at the top of the file, replacing <code>"Funtoo Linux"</code>.
 +
 
 +
<code>/etc/boot.conf</code> should now look like this:
 +
 
 +
<pre>
 +
boot {
 +
generate grub
 +
default "Funtoo Linux genkernel"
 +
timeout 3
 +
}
 +
 
 +
"Funtoo Linux" {
 +
kernel bzImage[-v]
 +
}
 +
 
 +
"Funtoo Linux genkernel" {
 +
kernel kernel[-v]
 +
initrd initramfs[-v]
 +
params += real_root=auto
 +
}
 +
 
 +
"Funtoo Linux better-initramfs" {
 +
kernel vmlinuz[-v]
 +
initrd /initramfs.cpio.gz
 +
}
 +
</pre>
 +
 
 +
Please read <code>man boot.conf</code> for further details.
 +
 
 +
===== Running grub-install and boot-update =====
 +
 
 +
Finally, we will need to actually install the GRUB boot loader to your disk, and also run <code>boot-update</code> which will generate your boot loader configuration file:
 +
 
 
<console>
 
<console>
###i## nano /etc/portage/package.use
+
(chroot) # ##i##grub-install --no-floppy /dev/sda
x11-drivers/ati-drivers qt4
+
(chroot) # ##i##boot-update
 
</console>
 
</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 ===
+
Now you need to update your boot loader configuration file:
To emerge the drivers, run the following command:
+
 
<console>
 
<console>
###i## emerge -av --changed-use --deep @world
+
(chroot) # ##i##boot-update
 
</console>
 
</console>
 +
You only need to run <code>grub-install</code> when you first install Funtoo Linux, but you need to re-run <code>boot-update</code> every time you modify your <code>/etc/boot.conf</code> file, so your changes are applied on next boot.
  
== Configuring ==
+
==== New School (UEFI) ====
  
Next, set ati-drivers to manage the system's OpenGL implementation:  
+
If you're using UEFI to boot, setting up the boot loader is a bit more complicated for now, but this process will be improving soon. Perform the following steps.
<console>
+
 
###i## eselect opengl set ati
+
===== Emerging GRUB =====
</console>
+
 
 +
You will still use GRUB as a boot loader, but before emerging grub, you will need to enable EFI booting. To do this,
 +
add the following line to <code>/etc/make.conf</code>:
 +
 
 +
<pre>
 +
 
 +
For 64-bit systems:
 +
 
 +
GRUB_PLATFORMS="efi-64"
 +
 
 +
For 32-bit systems, i.e. Intel Atom devices and systems with less than 4GB of RAM:
 +
 
 +
GRUB_PLATFORMS="efi-32"
 +
 
 +
</pre>
 +
 
 +
Then, <code>emerge boot-update</code>. You will notice <code>grub</code> and <code>efibootmgr</code> getting pulled in as dependencies. This is expected and good:
  
Afterwards, run <code>aticonfig</code> to modify the X-server configuration file to work with the ati-drivers:
 
 
<console>
 
<console>
###i## aticonfig --initial
+
(chroot) # ##i##emerge boot-update
 
</console>
 
</console>
  
{{fancytip| If you would like to have a full-resolution framebuffer with ati-drivers, check out [[uvesafb| uvesafb]]}}
+
===== Installing GRUB =====
  
== Troubleshooting ==
+
Now, for the magic of getting everything in place for booting. You should copy your kernel and initramfs (if you have one -- you will if you are following the default install) to <tt>/boot</tt>. GRUB will boot those. But how do we get UEFI to boot GRUB? Well, we need to run the following command (for 32bit simply set it as i386-efi):
=== 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>
# ##i##aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0
+
(chroot) # ##i##grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda
 
</console>
 
</console>
 +
This command will simply install all the stuff to <tt>/boot/EFI</tt> and <tt>/boot/grub</tt> that your system needs to boot. In particular, the <tt>/boot/EFI/grub/grubx64.efi</tt> file will be created. This is the GRUB boot image that UEFI will load and start.
  
You may need to restart your X session.
+
A more detailed explanation of the flags used in the above command:
 +
* <code>--target=x86_64-efi</code>: Tells GRUB that we want to install it in a way that allows it to boot in UEFI
 +
* <code>--efi-directory=/boot</code>: All GRUB UEFI files will be installed in ''/boot''
 +
* <code>--bootloader-id="Funtoo Linux [GRUB]"</code>: This flag is not necessary for GRUB to boot. However, it allows you to change the text of the boot option in the UEFI BIOS. The stuff in the quotes can be set to anything that you would like.
 +
* <code>--recheck</code>: If a device map already exists on the disk or partition that GRUB is being installed on, it will be removed.
 +
* <code>/dev/sda</code>:The device that we are installing GRUB on.
  
=== GNOME 3 windows only refresh when I drag them. ===
+
===== Configuring GRUB =====
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.
+
 
 +
OK, now UEFI has the GRUB image it needs to boot. But we still need to configure GRUB itself so it finds and boots your kernel and initramfs. This is done by performing the following steps. Since boot-update doesn't yet support UEFI, we will use boot-update, but then edit our <code>/boot/grub/grub.cfg</code> to support UEFI booting.  
 +
 
 +
First, you will need to edit <code>/etc/boot.conf</code>. Format this as you would if you were booting without UEFI. If you are not sure how this should look, below is an example of what it could look like if you are booting from an unencrypted ext4 partition:
 +
 
 +
{{file|name=/etc/boot.conf|desc=|body=
 +
boot {
 +
        generate grub
 +
        default "Funtoo Linux"
 +
        timeout 3
 +
}
 +
 
 +
"Funtoo Linux" {
 +
        kernel vmlinuz[-v]
 +
        params += rootfstype=ext4 root=/dev/sda2
 +
}
 +
}}
 +
 
 +
After you have edited your <code>/etc/boot.conf</code> file, run <code>boot-update</code>. You should now have a <code>/boot/grub/grub.cfg</code> file, which you can edit using the following command:
  
=== Compton with backend glx does not work well with ati-drivers ===
 
Try running compton with the following switches:
 
 
<console>
 
<console>
###i## compton --backend glx --vsync none --paint-on-overlay
+
# ##i##nano /boot/grub/grub.cfg
 
</console>
 
</console>
  
[[Category:Video Cards]]
+
 
[[Category:First Steps]]
+
To get your <code>/boot/grub/grub.cfg</code> to support booting with UEFI, make the following changes. Below the existing insmod lines, add the following lines.  Both of these involve adding support for the UEFI framebuffer to GRUB.:
{{EbuildFooter}}
+
 
 +
<pre>
 +
  insmod efi_gop
 +
  insmod efi_uga
 +
</pre>
 +
 
 +
Then, change the <code>set gfxpayload</code> line to read as follows. UEFI does not support text mode, so we will keep video initialized to the current resolution.:
 +
 
 +
<pre>
 +
  set gfxpayload=keep
 +
</pre>
 +
 
 +
You can now save your changes by pressing <code>Control-X</code> and answering <code>y</code> when asked if you want to save the modified buffer. When prompted for a filename, hit Enter to use the existing filename.

Revision as of 07:36, January 1, 2015


Note

This is a template that is used as part of the Installation instructions which covers: boot loader configuration. Templates are being used to allow multiple variant install guides that use most of the same re-usable parts.


Installing a Bootloader

These install instructions show you how to use GRUB to boot using BIOS (old-school) or UEFI (new-school).

Old School (BIOS)

If you're using the BIOS to boot, setting up GRUB, the bootloader, is pretty easy.

To use this recommended boot method, first emerge boot-update. This will also cause grub-2 to be merged, since it is a dependency of boot-update.

(chroot) # emerge boot-update

Then, edit /etc/boot.conf and specify "Funtoo Linux genkernel" as the default setting at the top of the file, replacing "Funtoo Linux".

/etc/boot.conf should now look like this:

boot {
	generate grub
	default "Funtoo Linux genkernel" 
	timeout 3 
}

"Funtoo Linux" {
	kernel bzImage[-v]
}

"Funtoo Linux genkernel" {
	kernel kernel[-v]
	initrd initramfs[-v]
	params += real_root=auto 
} 

"Funtoo Linux better-initramfs" {
	kernel vmlinuz[-v]
	initrd /initramfs.cpio.gz
}

Please read man boot.conf for further details.

Running grub-install and boot-update

Finally, we will need to actually install the GRUB boot loader to your disk, and also run boot-update which will generate your boot loader configuration file:

(chroot) # grub-install --no-floppy /dev/sda
(chroot) # boot-update

Now you need to update your boot loader configuration file:

(chroot) # boot-update

You only need to run grub-install when you first install Funtoo Linux, but you need to re-run boot-update every time you modify your /etc/boot.conf file, so your changes are applied on next boot.

New School (UEFI)

If you're using UEFI to boot, setting up the boot loader is a bit more complicated for now, but this process will be improving soon. Perform the following steps.

Emerging GRUB

You will still use GRUB as a boot loader, but before emerging grub, you will need to enable EFI booting. To do this, add the following line to /etc/make.conf:


For 64-bit systems:

GRUB_PLATFORMS="efi-64"

For 32-bit systems, i.e. Intel Atom devices and systems with less than 4GB of RAM:

GRUB_PLATFORMS="efi-32"

Then, emerge boot-update. You will notice grub and efibootmgr getting pulled in as dependencies. This is expected and good:

(chroot) # emerge boot-update
Installing GRUB

Now, for the magic of getting everything in place for booting. You should copy your kernel and initramfs (if you have one -- you will if you are following the default install) to /boot. GRUB will boot those. But how do we get UEFI to boot GRUB? Well, we need to run the following command (for 32bit simply set it as i386-efi):

(chroot) # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda

This command will simply install all the stuff to /boot/EFI and /boot/grub that your system needs to boot. In particular, the /boot/EFI/grub/grubx64.efi file will be created. This is the GRUB boot image that UEFI will load and start.

A more detailed explanation of the flags used in the above command:

  • --target=x86_64-efi: Tells GRUB that we want to install it in a way that allows it to boot in UEFI
  • --efi-directory=/boot: All GRUB UEFI files will be installed in /boot
  • --bootloader-id="Funtoo Linux [GRUB]": This flag is not necessary for GRUB to boot. However, it allows you to change the text of the boot option in the UEFI BIOS. The stuff in the quotes can be set to anything that you would like.
  • --recheck: If a device map already exists on the disk or partition that GRUB is being installed on, it will be removed.
  • /dev/sda:The device that we are installing GRUB on.
Configuring GRUB

OK, now UEFI has the GRUB image it needs to boot. But we still need to configure GRUB itself so it finds and boots your kernel and initramfs. This is done by performing the following steps. Since boot-update doesn't yet support UEFI, we will use boot-update, but then edit our /boot/grub/grub.cfg to support UEFI booting.

First, you will need to edit /etc/boot.conf. Format this as you would if you were booting without UEFI. If you are not sure how this should look, below is an example of what it could look like if you are booting from an unencrypted ext4 partition:

/etc/boot.conf
boot {
        generate grub
        default "Funtoo Linux"
        timeout 3
}

"Funtoo Linux" {
        kernel vmlinuz[-v]
        params += rootfstype=ext4 root=/dev/sda2
}

After you have edited your /etc/boot.conf file, run boot-update. You should now have a /boot/grub/grub.cfg file, which you can edit using the following command:

# nano /boot/grub/grub.cfg


To get your /boot/grub/grub.cfg to support booting with UEFI, make the following changes. Below the existing insmod lines, add the following lines. Both of these involve adding support for the UEFI framebuffer to GRUB.:

  insmod efi_gop
  insmod efi_uga

Then, change the set gfxpayload line to read as follows. UEFI does not support text mode, so we will keep video initialized to the current resolution.:

  set gfxpayload=keep

You can now save your changes by pressing Control-X and answering y when asked if you want to save the modified buffer. When prompted for a filename, hit Enter to use the existing filename.