The manual install guide is good to go, but the stage4 install guide is still being worked on.
- Preparing to install
- Preparing the disk
- Installing the Gentoo installation files
- Installing the Gentoo base system
- Configuring the kernel
- Basic system configuration
- Installing system tools
- Configuring the bootloader
- Configuring audio settings
- Setting up a working environment
- First boot into new system
- Installing audio & MIDI programs
- Testing your system
- Final notes
Manual install: installing the gentoo installation files
Before proceeding further, make sure the system time is correct by issuing the "date" command in the terminal. If it's not correct, set it using the date command using the format "MMDDhhmmYYYY". Don't worry about the time zone right now - that will be set later.
Download the Gentoo stage file:
- Open the Midori browser from the task bar.
- Go to https://gentoo.org/downloads/mirrors/.
- Select a mirror and navigate to releases -> amd64 -> autobuilds -> current-stage3-amd64.
- Download stage3-amd64-YYYYMMDD.tar.bz2 to /mnt/gentoo.
A more reliable alternative to a browser download is wget. In your browser, copy the link to the .tar.bz2 stage file and paste it into your terminal after the wget command:
> cd /mnt/gentoo
> wget http://mirrors.rit.edu/gentoo/releases/amd64/autobuilds/current-stage3-amd64/stage3-amd64-20160630.tar.bz2
However you download it, it could take up to 30 minutes over DSL and should finish quickly over cable or FiOS.
Unpack the stage file with:
> tar xvjpf stage3-*.tar.bz2 --xattrs
--xattrs may or may not work, depending on what you booted with. If it doesn't work, just leave it out and don't worry about it.
Add some options to make.conf:
> nano /mnt/gentoo/etc/portage/make.conf
Add this line to /etc/portage/make.conf:
where x is the number of processors or cores in your CPU. You can find this out with:
The first core will be numbered 0, so the number of cores is the last numbered core plus one. Later on, it is possible you may need to reduce MAKEOPTS (such as when compilation segfaults) but this is a good starting point.
Now remove the line for USE (in nano, ctrl-k to delete line) and at the end of make.conf, add the following:
USE="a52 aac aacplus alsa audacious bindist cdda cddb cdio consolekit corefonts dbus dirac dssi dts dv dvd encode equalizer faac ffmpeg fftw flac fluidsynth freesound g3dvl gif gtk gudev hwdb icu id3 id3tag ieee1394 jack jackmidi jpeg ladspa lame libsamplerate lv2 mad matroska midi minizip mp3 mp4 mpeg mpg123 musepack musicbrainz netjack ogg opengl pcre16 png policykit python qt3support qt4 qt5 quicktime realtime rubberband schroedinger shine shout skins sndfile soundtouch svg taglib theora tiff timidity truetype twolame udev usb vamp vcd vorbis wav wavpack X x264 xine xkb xml xvfb xvid xvmc -introspection -pulseaudio -xscreensaver"
Note the following:
- -xscreensaver use flag. Screensavers use up resources and blank your screen at inconvenient times when working with audio. Modern LCD monitors do not suffer from burn in - at most, you might notice transient image persistence, which is not permanent. Instead of using a screensaver, turn your DAW video monitors off when you're not using them.
- ACCEPT_KEYWORDS is "amd64" and not "~amd64". You want a system on a stable arch, even though you're going to make heavy use of package.keywords to set "~amd64" for a lot of audio packages. This should not be confused with advice against mixing ~stable and ~arch. We're not mixing ~stable and ~arch in the base system.
- MAKEOPTS can be adjusted between num_cores-1 and num_cores+1. Start with num_cores+1 and adjust to find out what works best on your system. For this purpose, threaded cores count, so if you have a Core i7 and cpuinfo shows 8 cores, assume 8 cores for MAKEOPTS.
- Set VIDEO_CARDS to your card - "intel" for Intel, and "nv" for Nvidia, for example. Whatever your card, do not enable 3D acceleration. It is not required for audio and may even interfere with efficient audio processing.
- f you have a laptop with a touchpad, add "synaptics" to INPUT_DEVICES, otherwise, "evdev" alone should suffice.
- You should add all of the use flags in the paste instructions above. You can of course customize them any way you see fit, if you know what you are doing.
- The USE flags include both qt4 and qt5. For some reason, this actually resolves certain conflicts. When Portage tells you a package can only use one, put that package in a package.use file with the -qt4 flag.