There are some issues to fix, before we go on. First, we don’t have framebuffer and a lousy resolution at the moment; second, the dhcp does not work at startup (there is an error message about no dhcp client being installed, although dhcpcd is there); finally, I think it’s better to rebuild the whole toolchain before we go on.
First, I created a file /etc/portage/package.use:
sys-libs/glibc userlocales
mail-mta/ssmtp mailwrapper
Especially the first one is important in order do downsize glibc compliation / installation time.
Now, I found a post on the Gentoo forums on the dhcp-stuff; it says to re-emerge baselayout. As I am going to re-emerge my whole system anyway, baselayout should be included.
So, first sync the tree and then emerge system; however, as I already configured X into my USE flags, it want’s to emerge the X server already, for which I don’t have time at the moment. So, I issue
USE="-X" emerge -auD --newuse system
which gives a list of 76 packages to merge – what I do of course (and note that baselayout is one of them). This takes a looooooong while… but noticeable shorter than on the old box – the difference between a Core2Duo and a Pentium 4…
We have to update the /etc/conf.d/clock file, it now looks like this:
CLOCK="local"
TIMEZONE="Europe/Zurich"
CLOCK_OPTS=""
Just to be sure that everything is ok, I run a revdep-rebuild after that (to do so, I need to emerge gentoolkit first). Nothing has to be done, so I reboot – horray! dhcp is now working.
Next thing to do is emerge some important stuff:
Now, we can set the EDITOR variable in /etc/rc.conf to /usr/bin/vim (finally!)
For sudo to work, we use visudo (as root) and uncomment the lines
Defaults editor=/usr/bin/vim, !env_editor
%wheel ALL=(ALL) ALL
Next thing is to configure fbsplash; there is a nice wiki article (on which I contributed at some time in the past…) on that which we follow step by step. (The only deviation is that we set VESA default mode to 1280×1024@60; also, I selected the Gentoo theme, not the livecd theme)
The lines for Gentoo in my grub.conf look now like this:
title=Gentoo Linux (Kernel 2.6.19-r5)
root (hd0,5)
kernel /boot/vmlinuz-2.6.19-gentoo-r5 root=/dev/sda6 video=vesafb:ywrap,mttr,1280x1024@60 splash=verbose,theme:gentoo CONSOLE="/dev/tty1 quiet
initrd (hd0,5)/boot/fbsplash-gentoo.1280x1024
Finally, we tweak the file /etc/conf.d/rc and change the following line:
RC_PARALLEL_STARTUP="yes"
Finally, another reboot: apart from the atl1 module, which again failed to load, everything ok and a nice gentoo theme is in place. After using modules-update force and reinstalling atl1, everything works again.
OK – we are now almost ready for installing X and KDE. But first, we do everything needed to have the system correctly up and running. This includes:
Writing /etc/env.d/02locale:
LANG="de_CH.UTF-8"
Also, we change the file /etc/man.conf, we alter the NROFF line:
NROFF /usr/bin/nforr -mandoc -c
(This is for full UTF-8 support, as described in this handbook doc)
We then enable GPM, as described in this handbook entry (we also make all the suggested changes to /etc/conf.d/gpm).
We now turn our attention to power management; we emerge acpid, cpufrequtils and cpufreqd. Latter fails, as some dependency (lm_sensors) need specific kernel options to be set; so we recompile the kernel again with these options added:
Device Drivers -->
I2C support -->
<*> I2C support
I2C Hardware Bus support -->
Intel 82801 (ICH)
Hardware Monitoring support -->
<*> Hardware Monitoring support
Windownd W83627EHF
(This post helped a lot!)
Then, we recompile the kernel, add the modules i2c-i801 and w83627ehf to /etc/modules.autoload.d/kernel-2.6 and reboot (as specified in the post, the W83627 module does not load correctly – so I remove it again from the autoload-file).
Finally, we now emerge cpufreqd, and configure it as given in the handbook entry.
We can add this to the default runlevel, but there is a wiki-page on CPU Frequency Scaling as well. I can’t start /etc/init.d/cpufrequtils, there is an error:
Beim Einstellen ist ein Fehler aufgetreten. Typische Fehlerquellen sind:
- nicht ausreichende Rechte (Administrator)
- der Regler ist nicht verfügbar bzw. nicht geladen
- die angegebene Taktik ist inkorrekt
- eine spezifische Frequenz wurde angegeben, aber der Regler 'userspace'
kann entweder hardwarebedingt nicht genutzt werden oder ist nicht geladen.
I will investigate later on this.
TO-DO before X:
Now, what is missing for next time is some stuff on harddisk monitoring (wiki entry on SMART and on hddtemp , also we have to add some entry in /etc/fstab for the cdrom. I want my multicard-reader to be working; also, I have to configure ALSA…. still something to do for next time!