Difference between pages "Make.conf" and "Uvesafb"

From Funtoo
(Difference between pages)
Jump to: navigation, search
m (add sauce, needs much more sauce)
 
m (Bootloader configuration)
 
Line 1: Line 1:
== What is the make.conf file? What is its purpose? ==
+
== ''How to'' : Framebuffer: Userspace VESA VGA graphics support ==
Make.conf is portage's and Funtoo's main configuration file. It contains many variables that define how a package will installed in a Funtoo system. You can customize portage internal variables, such as, portage tree location, sources tarball location, overlays, to name a few. You can customize hardware specs, such as TMPFS, disk limits, GCC compilation flags to achieve best performance, etc. A great deal of this customization is done through the make.conf file. This page will attempt to explain the uses of the make.conf file, different variables that can be added to it, and their uses.  
+
Uvesafb is an improved framebuffer driver for Linux systems with some enhancements compared to vesa. Uvesafb can allow you to get a full-resolution console, even if you have installed a graphics driver that does not support full-resolution consoles. Examples of drivers like these: [[Package:AMD_Catalyst_Video_Drivers| ati-drivers]] and NVidia-drivers.
  
== Where does this file reside? ==
+
== Kernel configuration ==
The <tt>make.conf</tt> file is found at <tt>/etc/portage/make.conf</tt> and <tt>/etc/make.conf</tt> though <tt>/etc/make.conf</tt> is its deprecated location.
+
Before we emerge the required packages for uvesafb functionality, we have to configure the kernel properly.
 +
{{Kernelop|title= |desc=
 +
Device Drivers --->
 +
    <*> Connector - unified userspace <-> kernelspace linker  --->
  
to edit:
+
    Graphics support --->
 +
        Frame buffer devices --->
 +
        [*] Support for frame buffer devices  --->
 +
            [*] Enable firmware EDID
 +
            <*> Userspace VESA VGA graphics support
 +
}}
 +
 
 +
{{fancynote| Build the kernel (<tt>make</tt>), do not install the kernel and modules (<tt> make install modules_install</tt>). You can choose uvesafb as a module, unlike vesa.}}
 +
 
 +
== Install required packages ==
 +
 
 +
Emerge {{Package|dev-libs/klibc}}. Klibc has to be compiled against a kernel that includes uvesafb support. This only has to be done once:
 
<console>
 
<console>
###i## nano /etc/portage/make.conf
+
###i## emerge klibc
 +
</console>
 +
{{Package|sys-apps/v86d}} is the userspace helper that runs x86 code in emulated environment. Uvesafb will not work without v86d. Emerge <code>v86d</code>:
 +
<console>
 +
###i## emerge v86d
 
</console>
 
</console>
  
== Variables ==
+
== Back to kernel configuration ==
 +
Reconfigure the kernel to include <tt>/usr/share/v86d/initramfs</tt> as an initramfs source file:
 +
{{Kernelop
 +
|title=
 +
|desc=
 +
General Setup--->
 +
    [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support
 +
    (/usr/share/v86d/initramfs)    Initramfs source file(s)
 +
}}
 +
Rebuild the kernel: make and install it, install the modules
  
* CFLAGS="-march=amdfam10 -O2 -pipe"
+
== Bootloader configuration ==
* CXXFLAGS="-march=amdfam10 -O2 -pipe"
+
If you compiled uvesafb into the kernel (not as a module), you can configure its behavior by editing the '<tt>params += </tt>' line in <tt>/etc/boot.conf</tt>. Below, some of the more common switches used with uvesafb are explained.
* INPUT_DEVICES="evdev"
+
* <tt>video=uvesafb:<screen y-res>x<screen x-res>-<color depth></tt>: Tells the kernel that you want to use the uvesafb driver for console output. Also specifies that you will be using uvesafb at a set x-screen resolution, y screen-resolution, and color depth. Set the first part to the size of your screen (in pixels). For example, if I had a 1920x1080 screen and wanted a color depth of 32, I would add the following: <tt>video=uvesafb:1920x1080-32</tt>
* VIDEO_CARDS="vesa nouveau"
+
 
* MAKEOPTS="-j 2"
+
* <tt>mtrr:x</tt>: X represents the number 0 or 3. This option allows you to set up the memory type range registers for uvesafb. Setting x=0 disables mtrr and setting x=3 enables mtrr. x=3 is the default setting for this switch. mtrr:3 is recommended.
* USE="mmx sse"
+
 
* PYTHON_ABIS="2.7 3.3"
+
* <tt>ywrap</tt>: Add support for display panning. Recommended.  
* PYTHON_TARGETS="2.7 3.3"
+
 
* RUBY_TARGETS="ruby21"
+
{{fancytip| For more information regarding these switches, check out http://www.mjmwired.net/kernel/Documentation/fb/uvesafb.txt}}
* ACCEPT_LICENSE="*"
+
 
 +
Now that you have a basic understanding of a few of the different switches, configure your <tt>/etc/boot.conf</tt>:
 +
 
 +
{{file|name=/etc/boot.conf|desc= |body=
 +
boot {
 +
        generate grub
 +
        default "Funtoo Linux: uvesafb"  
 +
        timeout 3
 +
}
 +
  "Funtoo Linux: uvesafb" {
 +
        kernel bzImage[-v]
 +
        params += video=uvesafb:1920x1080-32,mtrr:3,ywrap
 +
}
 +
}}
 +
{{fancynote| Realize that the configuration in the above file will not work on every computer. You must change the resolution (and possibly other switches) to best suite your needs.}}
 +
 
 +
After you have finished editing your <tt>/etc/boot.conf</tt>, run the following:
 +
<console>
 +
###i## boot-update
 +
</console>
 +
finally, reboot your computer so that you can test out uvesafb:
 +
<console>
 +
###i## reboot
 +
</console>
  
[[Category:System]]
+
[[Category:HOWTO]]

Latest revision as of 23:35, 14 September 2014

How to : Framebuffer: Userspace VESA VGA graphics support

Uvesafb is an improved framebuffer driver for Linux systems with some enhancements compared to vesa. Uvesafb can allow you to get a full-resolution console, even if you have installed a graphics driver that does not support full-resolution consoles. Examples of drivers like these: ati-drivers and NVidia-drivers.

Kernel configuration

Before we emerge the required packages for uvesafb functionality, we have to configure the kernel properly.

Device Drivers --->
    <*> Connector - unified userspace <-> kernelspace linker  --->

    Graphics support --->
        Frame buffer devices --->
        [*] Support for frame buffer devices  --->
            [*] Enable firmware EDID
            <*> Userspace VESA VGA graphics support
Note: Build the kernel (make), do not install the kernel and modules ( make install modules_install). You can choose uvesafb as a module, unlike vesa.

Install required packages

Emerge dev-libs/klibc. Klibc has to be compiled against a kernel that includes uvesafb support. This only has to be done once:

# emerge klibc

sys-apps/v86d is the userspace helper that runs x86 code in emulated environment. Uvesafb will not work without v86d. Emerge v86d:

# emerge v86d

Back to kernel configuration

Reconfigure the kernel to include /usr/share/v86d/initramfs as an initramfs source file:

General Setup--->
    [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support
    (/usr/share/v86d/initramfs)    Initramfs source file(s)

Rebuild the kernel: make and install it, install the modules

Bootloader configuration

If you compiled uvesafb into the kernel (not as a module), you can configure its behavior by editing the 'params += ' line in /etc/boot.conf. Below, some of the more common switches used with uvesafb are explained.

  • video=uvesafb:<screen y-res>x<screen x-res>-<color depth>: Tells the kernel that you want to use the uvesafb driver for console output. Also specifies that you will be using uvesafb at a set x-screen resolution, y screen-resolution, and color depth. Set the first part to the size of your screen (in pixels). For example, if I had a 1920x1080 screen and wanted a color depth of 32, I would add the following: video=uvesafb:1920x1080-32
  • mtrr:x: X represents the number 0 or 3. This option allows you to set up the memory type range registers for uvesafb. Setting x=0 disables mtrr and setting x=3 enables mtrr. x=3 is the default setting for this switch. mtrr:3 is recommended.
  • ywrap: Add support for display panning. Recommended.
Tip: For more information regarding these switches, check out http://www.mjmwired.net/kernel/Documentation/fb/uvesafb.txt

Now that you have a basic understanding of a few of the different switches, configure your /etc/boot.conf:

/etc/boot.conf
boot {
        generate grub
        default "Funtoo Linux: uvesafb" 
        timeout 3 
}
  "Funtoo Linux: uvesafb" { 
        kernel bzImage[-v]
        params += video=uvesafb:1920x1080-32,mtrr:3,ywrap
}
Note: Realize that the configuration in the above file will not work on every computer. You must change the resolution (and possibly other switches) to best suite your needs.

After you have finished editing your /etc/boot.conf, run the following:

# boot-update

finally, reboot your computer so that you can test out uvesafb:

# reboot