Difference between pages "F2FS Install Guide" and "Video"

(Difference between pages)
(finished formatting)
 
(Determine Hardware)
 
Line 1: Line 1:
<div class="container"><div class="row"><div class="col-sm-12 col-md-9">
+
Video is set up by setting global variables in [[make.conf]] & portage takes care of the rest.
== Introduction ==
+
These docs assume you have a "PC compatible" computer system with a standard PC BIOS. Many new computers support UEFI for booting, which is a new firmware interface that frequently replaces the older MBR-based BIOS. If you have a system with UEFI, you will want to use this documentation along with the [[UEFI Install Guide]], which will augment these instructions and explain how to get your system to boot. You may need to change your PC BIOS settings to enable or disable UEFI booting. The [[UEFI Install Guide]] has more information on this, and steps on how to determine if your system supports UEFI.
+
  
Installing on F2FS isn't terribly different from installing on XFS or EXT4;; but there are enough factors that warrant a guide of its own
+
== Determine Hardware ==
 +
first determine which video card you have and which driver it requires.
  
 +
<console>###i## lspci -k</console>
  
=== Live CD ===
+
=== Intel ===
 +
gen 1&2:
 +
{{file|name=/etc/portage/make.conf|lang=|desc=set video global variable|body=
 +
VIDEO_CARDS="intel"
 +
}}
 +
gen 3
 +
{{file|name=/etc/portage/make.conf|lang=|desc=set video global variable|body=
 +
VIDEO_CARDS="intel i915"
 +
}}
 +
gen 4+
 +
{{file|name=/etc/portage/make.conf|lang=|desc=set video global variable|body=
 +
VIDEO_CARDS="intel i965"
 +
}}
  
Funtoo doesn't provide an "official" Funtoo Live CD, but there are plenty of good ones out there to choose from. A great choice is the Debian-based [https://grml.org/ GRML] as it contains lots of tools and utilities and supports both 32-bit and 64-bit systems.
+
=== Ati ===
 +
Open source drivers:
 +
{{file|name=/etc/portage/make.conf|lang=|desc=set video global variable|body=
 +
VIDEO_CARDS="radeon"
 +
}}
  
It is also possible to install Funtoo Linux using many other Linux-based live CDs. Generally, any modern bootable Linux live CD or live USB media will work. See [[Requirements|requirements]] for an overview of what the Live Media must provide to allow a problem-free install of Funtoo Linux.
+
Closed source drivers:
 +
{{file|name=/etc/portage/make.conf|lang=|desc=set video global variable|body=
 +
VIDEO_CARDS="fglrx"
 +
}}
  
To begin a Funtoo Linux installation, boot your preferred live media & start a commandline session.
+
==== Hybrid ====
 +
Hybrid intel/ati:
 +
{{file|name=/etc/portage/make.conf|lang=|desc=set video global variable|body=
 +
VIDEO_CARDS="fglrx intel"
 +
}}
  
 +
<console># ##i##aticonfig --initial --input=/etc/X11/xorg.conf</console>
  
 +
=== Nvidia ===
 +
Open source drivers:
 +
{{file|name=/etc/portage/make.conf|lang=|desc=set video global variable|body=
 +
VIDEO_CARDS="nouveau"
 +
}}
 +
Closed source [[Package:NVIDIA_Linux_Display_Drivers | drivers]]:
 +
{{file|name=/etc/portage/make.conf|lang=|desc=set video global variable|body=
 +
VIDEO_CARDS="nvidia"
 +
}}
  
===Starting an SSH session===
 
This is only required if you wish to perform the installation process on a computer other than where you are installing funtoo to
 
<console>
 
service ssh start; passwd; ifconfig
 
</console>
 
This starts SSH, asks for a root password, and then displays the IP address
 
  
 
+
===Other===
===Install required programs===
+
These settings are used by Parallels VM's and presumably others
<console>
+
{{file|name=/etc/portage/make.conf|lang=|desc=set video global variable|body=
apt-get update; apt-get install f2fs-tools elinks
+
VIDEO_CARDS="vesa vga"  
</console>
+
F2FS is not included in current linux kernels, and elinks is used to download the stage3 tarball
+
 
+
 
+
===Partitioning===
+
<console>
+
cfdisk /dev/sda
+
</console>
+
Your partition layout should be similar to
+
 
+
{{TableStart}}
+
<tr class="active"><th>Partition</th>
+
<th>Size</th>
+
<th>MBR Block Device (<code>fdisk</code>)</th>
+
<th>MBR Code</th>
+
</tr><tr>
+
<td><code>/boot</code></td>
+
<td>512 MB</td>
+
<td><code>/dev/sda1</code></td>
+
<td>83</td>
+
</tr><tr>
+
<td>swap</td>
+
<td>1.5 to 2x RAM for low-memory systems and production servers; otherwise 2GB.</td>
+
<td><code>/dev/sda2</code></td>
+
<td>82</td>
+
</tr><tr>
+
<td><code>/</code> (root)</td>
+
<td>minimum of 10GB.  Note: to compile the <code>debian-sources</code> kernel, requires a minimum of 14GB free space in <code>/tmp</code>; consider a minimum of 20GB in this case.</td>
+
<td><code>/dev/sda3</code></td>
+
<td>83</td>
+
</tr><tr>
+
<td><code>/home</code></td>
+
<td>User storage and media. Typically most of the disk.</td>
+
<td><code>/dev/sda4</code> (if created)</td>
+
<td>83</td>
+
</tr><tr>
+
</tr>{{TableEnd}}
+
+
==Formatting==
+
<console>
+
mkfs.ext2 /dev/sda1
+
mkswap /dev/sda2
+
swapon /dev/sda2
+
mkfs.f2fs /dev/sda3
+
mkfs.ext4 /dev/sda4
+
</console>
+
 
+
 
+
===Mounting the new system===
+
<console>
+
mkdir /mnt/funtoo
+
mount -t f2fs /dev/sda3 /mnt/funtoo
+
mkdir /mnt/funtoo/boot
+
mount /dev/sda1 /mnt/funtoo/boot
+
mkdir /mnt/funtoo/home
+
mount -o noatime /dev/sda4 /mnt/funtoo/home
+
</console>
+
 
+
===Downloading the system===
+
<console>
+
cd /mnt/funtoo/
+
elinks build.funtoo.org
+
</console>
+
Navigate to your build, arch, and subarch and save stage3
+
 
+
==Installing stage3==
+
<console>
+
tar xpfv stage3-latest.tar.xz
+
cp /etc/resolv.conf etc
+
</console>
+
 
+
 
+
===chrooting into the new system===
+
<console>
+
mount -t proc none proc
+
mount --rbind /sys sys
+
mount --rbind /dev dev
+
env -i HOME=/root TERM=$TERM; chroot . bash -l
+
export PS1="(chroot) $PS1"
+
</console>
+
 
+
 
+
=== Downloading the Portage tree ===
+
 
+
{{fancynote|For an alternative way to do this, see [[Installing Portage From Snapshot]].}}
+
Now it's time to install a copy of the Portage repository, which contains package scripts (ebuilds) that tell portage how to build and install thousands of different software packages. To create the Portage repository, simply run <code>emerge --sync</code> from within the chroot. This will automatically clone the portage tree from [https://github.com/funtoo/ports-2012 GitHub]:
+
 
+
<console>
+
emerge --sync
+
</console>
+
 
+
{{fancyimportant|1=
+
If you receive the error with initial <code>emerge --sync</code> due to git protocol restrictions, change <code>SYNC</code> variable in <code>/etc/make.conf</code>:
+
<pre>
+
SYNC="https://github.com/funtoo/ports-2012.git"
+
</pre>
+
 
}}
 
}}
  
=== Configuring your system ===
+
== Install ==
As is expected from a Linux distribution, Funtoo Linux has its share of configuration files. The one file you are absolutely required to edit in order to ensure that Funtoo Linux boots successfully is <code>/etc/fstab</code>. The others are optional. Here are a list of files that you should consider editing:
+
once your video cards variable is set in make.conf merge changes into your system
{{TableStart}}
+
<tr class="active"><th>File</th>
+
<th>Do I need to change it?</th>
+
<th>Description</th>
+
</tr><tr  class="danger">
+
<td><code>/etc/fstab</code></td>
+
<td>'''YES - required'''</td>
+
<td>Mount points for all filesystems to be used at boot time. This file must reflect your disk partition setup. We'll guide you through modifying this file below.</td>
+
</tr><tr>
+
<td><code>/etc/localtime</code></td>
+
<td>''Maybe - recommended''</td>
+
<td>Your timezone, which will default to UTC if not set. This should be a symbolic link to something located under /usr/share/zoneinfo (e.g. /usr/share/zoneinfo/America/Montreal) </td>
+
</tr><tr>
+
<td><code>/etc/make.conf</code> (symlink) - also known as:<br/><code>/etc/portage/make.conf</code></td>
+
<td>''Maybe - recommended''</td>
+
<td>Parameters used by gcc (compiler), portage, and make. It's a good idea to set MAKEOPTS. This is covered later in this document.</td>
+
</tr><tr>
+
<td><code>/etc/conf.d/hostname</code></td>
+
<td>''Maybe - recommended''</td>
+
<td>Used to set system hostname. Set the <code>hostname</code> variable to the fully-qualified (with dots, ie. <code>foo.funtoo.org</code>) name if you have one. Otherwise, set to the local system hostname (without dots, ie. <code>foo</code>). Defaults to <code>localhost</code> if not set.</td>
+
</tr><tr>
+
<td><code>/etc/hosts</code></td>
+
<td>''No''</td>
+
<td> You no longer need to manually set the hostname in this file. This file is automatically generated by <code>/etc/init.d/hostname</code>.</td>
+
</tr><tr>
+
<td><code>/etc/conf.d/keymaps</code></td>
+
<td>Optional</td>
+
<td>Keyboard mapping configuration file (for console pseudo-terminals). Set if you have a non-US keyboard. See [[Funtoo Linux Localization]].</td>
+
</tr><tr>
+
<td><code>/etc/conf.d/hwclock</code></td>
+
<td>Optional</td>
+
<td>How the time of the battery-backed hardware clock of the system is interpreted (UTC or local time). Linux uses the battery-backed hardware clock to initialize the system clock when the system is booted.</td>
+
</tr><tr>
+
<td><code>/etc/conf.d/modules</code></td>
+
<td>Optional</td>
+
<td>Kernel modules to load automatically at system startup. Typically not required. See [[Additional Kernel Resources]] for more info.</td>
+
</tr><tr>
+
<td><code>/etc/conf.d/consolefont</code></td>
+
<td>Optional</td>
+
<td>Allows you to specify the default console font. To apply this font, enable the consolefont service by running rc-update add consolefont.</td>
+
</tr><tr>
+
<td><code>profiles</code></td>
+
<td>Optional</td>
+
<td>Some useful portage settings that may help speed up intial configuration.</td>
+
</tr>
+
{{TableEnd}}
+
 
+
If you're installing an English version of Funtoo Linux, you're in luck as most of the configuration files can be used as-is. If you're installing for another locale, don't worry. We will walk you through the necessary configuration steps on the [[Funtoo Linux Localization]] page, and if needed, there's always plenty of friendly, helpful support. (See [[#Community portal|Community]])
+
 
+
Let's go ahead and see what we have to do. Use <code>nano -w <name_of_file></code> to edit files -- the "<code>-w</code>" disables word-wrapping, which is handy when editing configuration files. You can copy and paste from the examples.
+
 
+
{{fancywarning|It's important to edit your <code>/etc/fstab</code> file before you reboot! You will need to modify both the "fs" and "type" columns to match the settings for your partitions and filesystems that you created with <code>gdisk</code> or <code>fdisk</code>. Skipping this step may prevent Funtoo Linux from booting successfully.}}
+
 
+
==== /etc/fstab ====
+
 
+
<code>/etc/fstab</code> is used by the <code>mount</code> command which is ran when your system boots. Statements of this file inform <code>mount</code> about partitions to be mounted and how they are mounted. In order for the system to boot properly, you must edit <code>/etc/fstab</code> and ensure that it reflects the partition configuration you used earlier:
+
 
+
<console>
+
nano -w /etc/fstab
+
</console>
+
<pre>
+
/dev/sda1              /boot          ext2            noauto,noatime  1 2
+
/dev/sda2              none            swap            sw              0 0<br>
+
/dev/sda3              /              f2fs            rw,acl,active_logs=6,background_gc=on,user_xattr          0 1
+
/dev/sda4              /home          ext4            noatime        0 1
+
#/dev/cdrom            /mnt/cdrom      auto            noauto,ro      0 0
+
</pre>
+
==== /etc/localtime ====
+
 
+
<code>/etc/localtime</code> is used to specify the timezone that your machine is in, and defaults to UTC. If you would like your Funtoo Linux system to use local time, you should replace <code>/etc/localtime</code> with a symbolic link to the timezone that you wish to use.
+
 
+
<console>
+
(chroot) # ##i##ln -sf /usr/share/zoneinfo/MST7MDT /etc/localtime
+
</console>
+
 
+
The above sets the timezone to Mountain Standard Time (with daylight savings). Type <code>ls /usr/share/zoneinfo</code> to see what timezones are available. There are also sub-directories containing timezones described by location.
+
 
+
==== /etc/make.conf ====
+
 
+
MAKEOPTS can be used to define how many parallel compilations should occur when you compile a package, which can speed up compilation significantly. A rule of thumb is the number of CPUs (or CPU threads) in your system plus one. If for example you have a dual core processor without [[wikipedia:Hyper-threading|hyper-threading]], then you would set MAKEOPTS to 3:
+
 
+
<pre>
+
MAKEOPTS="-j3"
+
</pre>
+
 
+
If you are unsure about how many processors/threads you have then use nproc to help you.
+
<console>
+
nproc
+
</console>
+
 
+
Set MAKEOPTS to this number plus one:
+
 
+
USE flags define what functionality is enabled when packages are built. It is not recommended to add a lot of them during installation; you should wait until you have a working, bootable system before changing your USE flags. A USE flag prefixed with a minus ("<code>-</code>") sign tells Portage not to use the flag when compiling.  A Funtoo guide to USE flags will be available in the future. For now, you can find out more information about USE flags in the [http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=2&chap=2 Gentoo Handbook].
+
 
+
LINGUAS tells Portage which local language to compile the system and applications in (those who use LINGUAS variable like OpenOffice). It is not usually necessary to set this if you use English. If you want another language such as French (fr) or German (de), set LINGUAS appropriately:
+
 
+
<pre>
+
LINGUAS="fr"
+
</pre>
+
 
+
==== /etc/conf.d/hwclock ====
+
If you dual-boot with Windows, you'll need to edit this file and change the value of '''clock''' from '''UTC''' to '''local''', because Windows will set your hardware clock to local time every time you boot Windows. Otherwise you normally wouldn't need to edit this file.
+
<console>
+
(chroot) # ##i##nano -w /etc/conf.d/hwclock
+
</console>
+
 
+
==== Localization ====
+
 
+
By default, Funtoo Linux is configured with Unicode (UTF-8) enabled, and for the US English locale and keyboard. If you would like to configure your system to use a non-English locale or keyboard, see [[Funtoo Linux Localization]].
+
 
+
 
+
=== Introducing Portage ===
+
 
+
Portage, the Funtoo Linux package manager has a command called <code>emerge</code> which is used to build and install packages from source. It also takes care of installing all of the package's dependencies. You call emerge like this:
+
 
+
When you install a package by specifying its name in the command-line, Portage records its name in the <code>/var/lib/portage/world</code> file. It does so because it assumes that, since you have installed it by name, you want to consider it part of your system and want to keep the package updated in the future. This is a handy feature, since when packages are being added to the <code>world</code> set, we can update our entire system by typing:
+
 
+
<console>
+
emerge --sync
+
emerge -auDN @world
+
</console>
+
 
+
This is the "official" way to update your Funtoo Linux system. Above, we first update our Portage tree using git to grab the latest ebuilds (scripts), and then run an emerge command to update the <code>world</code> set of packages. The options specified tell <code>emerge</code> to:
+
 
+
* '''<code>a</code>''' - show us what will be emerged, and '''ask''' us if we want to proceed
+
* '''<code>u</code>''' - ''update'' the packages we specify -- don't emerge them again if they are already emerged.
+
* '''<code>D</code>''' - Consider the entire dependency tree of packages when looking for updates. In other words, do a '''deep''' update.
+
* '''<code>N</code>''' - Update any packages that have changed ('''new''') USE settings.
+
 
+
You should also consider passing <code>--with-bdeps=y</code> when emerging @world, at least once in a while. This will update build dependencies as well.
+
 
+
Advanced users may be interested in the [[Emerge]] wiki page.
+
 
+
{{fancyimportant|1=
+
Make sure you read any post emerge messages and follow their instructions. This is especially true if you have upgraded perl or python.}}
+
 
+
 
+
=== Configuring and installing the Linux kernel ===
+
 
+
Now it's time to build and install a Linux kernel, which is the heart of any Funtoo Linux system. The kernel is loaded by the boot loader, and interfaces directly with your system's hardware, and allows regular (userspace) programs to run.
+
 
+
A kernel must be configured properly for your system's hardware, so that it supports your hard drives, file systems, network cards, and so on. More experienced Linux users can choose to install kernel sources and configure and install their own kernel. If you don't know how to do this, we provide ebuilds that will automatically build a "univeral" kernel, modules and initramfs for booting your system that supports all hardware. This is an extremely simple way of building a kernel that will get your system booted.
+
 
+
What is our goal? To build a kernel that will recognize all the hardware in your system necessary for booting, so that you will be greeted by a friendly login prompt after installation is complete. These instructions will guide you through the process of installing a kernel the "easy" way -- without requiring user configuration, by using a "universal" kernel.
+
 
+
==== Building the Kernel ====
+
 
+
{{Fancynote|1=
+
See [[Funtoo Linux Kernels]] for a full list of kernels supported in Funtoo Linux. We recommend <code>debian-sources</code> for new users.}}
+
 
+
<console>
+
emerge -av sys-kernel/gentoo-sources sys-kernel/genkernel f2fs-tools<br>
+
cd /usr/src/linux; make menuconfig<br>
+
</console>
+
 
+
F2FS is not included by default; we must specify that we need it
+
{{kernelop|title=foo,bar|desc=
+
Filesystems-->Miscellaneous-->F2FS
+
}}
+
 
+
Save config as 'f2fs.config'
+
 
+
<console>
+
genkernel --kernel-config=f2fs.config all<br>
+
</console>
+
 
+
=== Installing a Bootloader ===
+
 
+
{{fancynote|An alternate boot loader called extlinux can be used instead of GRUB if you desire. See the [[Extlinux|extlinux Guide]] for information on how to do this.}}
+
 
+
==== Installing Grub ====
+
 
+
The boot loader is responsible for loading the kernel from disk when your computer boots. For new installations, GRUB 2 and Funtoo's boot-update tool should be used as a boot loader. GRUB supports both GPT/GUID and legacy MBR partitioning schemes.
+
 
+
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>. (You may need to adjust <code>GRUB_PLATFORMS</code> if you are on a UEFI system. See [[UEFI Install Guide]]).
+
 
+
<console>
+
(chroot)emerge boot-update
+
nano /etc/boot.conf
+
</console>
+
 
+
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]
+
        # params += nomodeset
+
}
+
 
+
"Funtoo Linux genkernel" {
+
# if you use bliss-kernel package
+
# you should change string
+
# kernel kernel[-v]
+
# to
+
# kernel kernel/[-v]/kernel[-v]
+
        kernel kernel[-v]
+
        initrd initramfs[-v]
+
        params += real_root=auto
+
        # params += nomodeset
+
}
+
</pre>
+
 
+
If you use bliss-kernel, your <code>/etc/boot.conf</code> should look like:
+
 
+
<pre>
+
boot {
+
        generate grub
+
        default "Funtoo Linux genkernel"
+
        timeout 3
+
}
+
 
+
"Funtoo Linux" {
+
        kernel bzImage[-v]
+
        # params += nomodeset
+
}
+
 
+
"Funtoo Linux genkernel" {
+
        kernel kernels/[-v]/kernel[-v]
+
        initrd initramfs[-v]
+
        params += real_root=auto
+
        # params += nomodeset
+
}
+
</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>
+
grub-install --no-floppy /dev/sda
+
boot-update
+
</console>
+
 
+
Now you need to update your boot loader configuration file:
+
<console>
+
boot-update
+
</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 your network ===
+
 
+
It's important to ensure that you will be able to connect to your local-area network after you reboot into Funtoo Linux. There are three approaches you can use for configuring your network: NetworkManager, dhcpcd, and the [[Funtoo Linux Networking]] scripts. Here's how to choose which one to use based on the type of network you want to set up.
+
 
+
==== Wi-Fi ====
+
===== Using NetworkManager =====
+
For laptop/mobile systems where you will be using Wi-Fi and connecting to various networks, NetworkManager is strongly recommended. The Funtoo version of NetworkManager is fully functional even from the command-line, so you can use it even without X or without the Network Manager applet. Here are the steps involved in setting up NetworkManager:
+
 
+
<console>
+
emerge linux-firmware
+
emerge networkmanager
+
rc-update add NetworkManager default
+
</console>
+
 
+
Above, we installed linux-firmware which contains a complete collection of available firmware for many hardware devices including Wi-Fi adapters, plus NetworkManager to manage our network connection. Then we added NetworkManager to the <code>default</code> runlevel so it will start when Funtoo Linux boots.
+
 
+
After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:
+
 
+
<console>
+
addwifi -S wpa -K 'wifipassword' mywifinetwork
+
</console>
+
 
+
The <code>addwifi</code> command is used to configure and connect to a WPA/WPA2 Wi-Fi network named <code>mywifinetwork</code> with the password <code>wifipassword</code>. This network configuration entry is stored in <code>/etc/NetworkManager/system-connections</code> so that it will be remembered in the future. You should only need to enter this command once for each Wi-Fi network you connect to.
+
 
+
===== Using wpa_supplicant =====
+
If for some reason you don't want to use a tool such as NetworkManager or <code>wicd</code>, you can use wpa_supplicant for wireless network connections.
+
 
+
First, emerge wpa_supplicant:
+
 
+
<console>
+
emerge -a wpa_supplicant
+
</console>
+
 
+
Now, edit the wpa_supplicant configuration file, located at /etc/wpa_supplicant.conf.
+
The syntax is very easy:
+
<pre>
+
network={
+
ssid="MyWifiName"
+
psk="lol42-wifi"
+
}
+
 
+
network={
+
ssid="Other Network"
+
psk="6d96270004515a0486bb7f76196a72b40c55a47f"
+
}
+
</pre>
+
 
+
You will need to add both <code>wpa_supplicant</code> and <code>dhcpcd</code> to the default runlevel. <code>wpa_supplicant</code> will connect to your access point, and <code>dhcpcd</code> will acquire an IP address via DHCP:
+
 
+
<console>
+
(chroot) # ##i##rc-update add dhcpcd default
+
(chroot) # ##i##rc-update add wpa_supplicant default
+
</console>
+
 
+
==== Desktop (Wired Ethernet) ====
+
 
+
For a home desktop or workstation with wired Ethernet that will use DHCP, the simplest and most effective option to enable network connectivity is to simply add <code>dhcpcd</code> to the default runlevel:
+
 
+
<console>
+
rc-update add dhcpcd default
+
</console>
+
 
+
When you reboot, <code>dhcpcd</code> will run in the background and manage all network interfaces and use DHCP to acquire network addresses from a DHCP server.
+
 
+
==== Server (Static IP) ====
+
 
+
For servers, the [[Funtoo Linux Networking]] scripts are recommended. They are optimized for static configurations and things like virtual ethernet bridging for virtualization setups. See [[Funtoo Linux Networking]] for information on how to use Funtoo Linux's template-based network configuration system.
+
 
+
=== Finishing Steps ===
+
 
+
==== Set your root password ====
+
It's imperative that you set your root password before rebooting so that you can log in.
+
<console>
+
passwd
+
</console>
+
 
+
===Next Steps===
+
 
+
If you are brand new to Funtoo Linux and Gentoo Linux, please check out [[Funtoo Linux First Steps]], which will help get you acquainted with your new system. We also have a category for our [[:Category:Official Documentation|official documentation]], which includes all docs that we officially maintain for installation and operation of Funtoo Linux.
+
  
We also have a number of pages dedicated to setting up your system, which you can find below. If you are interested in adding a page to this list, add it to the "First Steps" MediaWiki category.
+
<console>###i## emerge -avuND world</console>
  
{{#ask: [[Category:First Steps]] | format=ul }}
+
=== Select Driver ===
  
If your system did not boot correctly, see [[Installation Troubleshooting]] for steps you can take to resolve the problem.
+
{{note|change the number of card eselected to match the card of your system}}
 +
<console>###i## eselect opengl list
 +
###i## eselect opengl set 1</console>
  
[[Category:HOWTO]]
+
{{note|some setups can make use of opencl}}
[[Category:Install]]
+
<console>###i##eselect opencl list
[[Category:Official Documentation]]
+
###i##eselect opencl set 1</console>
</div><div class="col-md-3 col-hidden-sm col-hidden-xs"><div id="tocwrap" >
+
__TOC__
+
</div></div></div>
+

Revision as of 19:58, November 3, 2014

Video is set up by setting global variables in make.conf & portage takes care of the rest.

Determine Hardware

first determine which video card you have and which driver it requires.

# lspci -k

Intel

gen 1&2:

/etc/portage/make.conf: set video global variable
VIDEO_CARDS="intel"

gen 3

/etc/portage/make.conf: set video global variable
VIDEO_CARDS="intel i915"

gen 4+

/etc/portage/make.conf: set video global variable
VIDEO_CARDS="intel i965"

Ati

Open source drivers:

/etc/portage/make.conf: set video global variable
VIDEO_CARDS="radeon"

Closed source drivers:

/etc/portage/make.conf: set video global variable
VIDEO_CARDS="fglrx"

Hybrid

Hybrid intel/ati:

/etc/portage/make.conf: set video global variable
VIDEO_CARDS="fglrx intel"
# aticonfig --initial --input=/etc/X11/xorg.conf

Nvidia

Open source drivers:

/etc/portage/make.conf: set video global variable
VIDEO_CARDS="nouveau"

Closed source drivers:

/etc/portage/make.conf: set video global variable
VIDEO_CARDS="nvidia"


Other

These settings are used by Parallels VM's and presumably others

/etc/portage/make.conf: set video global variable
VIDEO_CARDS="vesa vga"

Install

once your video cards variable is set in make.conf merge changes into your system

# emerge -avuND world

Select Driver

Note

change the number of card eselected to match the card of your system

# eselect opengl list
# eselect opengl set 1

Note

some setups can make use of opencl

#eselect opencl list
#eselect opencl set 1