So after trying out chrubuntu and arch-linux on my arm based chromebook I decided to try out gentoo. I already had my partitions setup so I didn’t have to worry about that. You can check out my previous setups here:

Prepare for the Gentoo Install

So I rebooted into ChromeOS and opened up the Crosh Shell. The partitions get automatically mounted on boot:

localhost ~ # mount | grep 'SD Card'
/dev/mmcblk1p12 on /media/removable/SD Card type vfat (rw,nosuid,nodev,noexec,relatime,dirsync,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,flush,errors=remount-ro)
/dev/mmcblk1p2 on /media/removable/SD Card 1 type ext2 (rw,nosuid,nodev,noexec,relatime,dirsync)
/dev/mmcblk1p3 on /media/removable/SD Card 2 type ext4 (rw,nosuid,nodev,noexec,relatime,dirsync,data=ordered)

So /media/removable/SD Card 2 is where my root partitions is. First I removed everything from there:

localhost ~ # cd /media/removable/SD\ Card\ 2
localhost SD Card 2 # rm -rf *

Depending on your SD card the above might take a while. Now that I have a clean root partition let’s get the stage3 tar from gentoo:

localhost SD Card 2 # wget

That was the latest at the time, you could run the following at any time to get the latest:

wget -O -$(wget -O - 2>/dev/zero | tail -n1)

After you have the stage3 tar then extract it:

localhost SD Card 2 # tar xjf stage3-armv7a_hardfp-20141023.tar.bz2 

After that you will have the necessary directories:

localhost SD Card 2 # ls 
bin boot dev etc home lib media mnt opt proc root run sbin stage3-armv7a_hardfp-20141023.tar.bz2 sys tmp usr var

Now let’s get the portage files:

localhost SD Card 2 # wget 

Now let’s extract it and put under the usr directory within the root partition:

localhost SD Card 2 # tar xjf portage-latest.tar.bz2 -C usr/

Now let’s prepare to chroot into our rootfs:

localhost ~# mount /dev/mmcblk1p2 /media/removable/SD\ Card\ 2/boot/
localhost ~ # mount -t proc proc /media/removable/SD\ Card\ 2/proc 
localhost ~ # mount --rbind /dev /media/removable/SD\ Card\ 2/dev 
localhost ~ # mount --rbind /sys /media/removable/SD\ Card\ 2/sys 
localhost ~ # cp -L /etc/resolv.conf /media/removable/SD\ Card\ 2/etc/.

We have to do one more extra thing from ChromeOS and that’s enable exec on the mounted root partition (this is so we can chroot):

localhost ~ # mount /dev/mmcblk1p3 -o remount,exec

Now to go inside the gentoo chroot:

localhost ~ # chroot /media/removable/SD\ Card\ 2
localhost / #

Prepare for the Kernel Compile

First let’s set the timezone:

localhost ~ # cp /usr/share/zoneinfo/America/Denver /etc/localtime 
localhost ~ # echo "America/Denver" > /etc/timezone

As I was checking the profile I realized for some reason the PORTAGE_CONFIGROOT was set as the following:

localhost ~ # env | grep -i roo

So I unset it.

localhost ~ # unset PORTAGE_CONFIGROOT

and after that I saw that my profile is configured appropriately:

localhost ~ # eselect profile show
Current /etc/portage/make.profile symlink:

Just for reference here is a list of available profiles:

localhost ~ # eselect profile list
Available profile symlink targets:
[1] default/linux/arm/13.0
[2] default/linux/arm/13.0/desktop
[3] default/linux/arm/13.0/desktop/gnome
[4] default/linux/arm/13.0/desktop/gnome/systemd
[5] default/linux/arm/13.0/desktop/kde
[6] default/linux/arm/13.0/desktop/kde/systemd
[7] default/linux/arm/13.0/developer
[8] default/linux/arm/13.0/armv4
[9] default/linux/arm/13.0/armv4/desktop
[10] default/linux/arm/13.0/armv4/desktop/gnome
[11] default/linux/arm/13.0/armv4/desktop/kde
[12] default/linux/arm/13.0/armv4/developer
[13] default/linux/arm/13.0/armv4t
[14] default/linux/arm/13.0/armv4t/desktop
[15] default/linux/arm/13.0/armv4t/desktop/gnome
[16] default/linux/arm/13.0/armv4t/desktop/kde
[17] default/linux/arm/13.0/armv4t/developer
[18] default/linux/arm/13.0/armv5te
[19] default/linux/arm/13.0/armv5te/desktop
[20] default/linux/arm/13.0/armv5te/desktop/gnome
[21] default/linux/arm/13.0/armv5te/desktop/kde
[22] default/linux/arm/13.0/armv5te/developer
[23] default/linux/arm/13.0/armv6j
[24] default/linux/arm/13.0/armv6j/desktop
[25] default/linux/arm/13.0/armv6j/desktop/gnome
[26] default/linux/arm/13.0/armv6j/desktop/kde
[27] default/linux/arm/13.0/armv6j/developer
[28] default/linux/arm/13.0/armv7a *
[29] default/linux/arm/13.0/armv7a/desktop
[30] default/linux/arm/13.0/armv7a/desktop/gnome
[31] default/linux/arm/13.0/armv7a/desktop/kde
[32] default/linux/arm/13.0/armv7a/developer
[33] hardened/linux/arm/armv7a
[34] hardened/linux/arm/armv6j
[35] hardened/linux/musl/arm/armv7a
[36] default/linux/uclibc/arm/armv7a
[37] hardened/linux/uclibc/arm/armv7a

Before doing anything with emerge let’s set the default USE flags, in the past here is what I ended up with:

USE="pulseaudio X -ipv6 bindist nvidia alsa \
bluetooth dbus lm_sensors jpeg lock session udev \
startup-notification truetype -gnome libnotify bash-completion"
INPUT_DEVICES="evdev synaptics"

So let’s grab vim (cause I can’t edit files in any other way :) ):

localhost ~ # emerge -av vim

After installing vim I added the above into /etc/portage/make.conf.

I built the chromeos kernel previously as descibed here and I noticed there is an overlay for the chromiumos kernel. So I decided to install layman and add that overlay (similar approach as this). Before we install the layman tools let’s check out the available USE flags for that package (to get equery we need to install gentoolkit, so first install it with emerge -av gentoolkit):

localhost ~ # equery u layman
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for app-portage/layman-2.0.0-r3:
 U I
 - - bazaar                   : Support dev-vcs/bzr based overlays
 - - cvs                      : Support dev-vcs/cvs based overlays
 + + git                      : Support dev-vcs/git based overlays
 - - mercurial                : Support dev-vcs/mercurial based overlays
 + + python_targets_python2_7 : Build with Python 2.7
 + - subversion               : Support dev-vcs/subversion based overlays
 - - test                     : Workaround to pull in packages needed to run
                                with FEATURES=test. Portage-2.1.2 handles this
                                internally, so don't set it in
                                make.conf/package.use anymore

I wanted layman to support subversion and git repos, so I created the following package.use for layman:

localhost ~ # mkdir /etc/portage/package.use
localhost ~ # cat /etc/portage/package.use/layman 
app-portage/layman subversion git

It took about an hour to build all the dependencies:

localhost ~ # time emerge -av layman
real 62m9.751s
user 29m8.785s
sys 9m19.120s

Then I added the following to /etc/portage/make.conf (so emerge can install packages from the overlays)

source /var/lib/layman/make.conf

Then run the following to list the available overlays and to cache them:

localhost ~ # layman -L

You will see our overlay in the list:

localhost ~ # layman -L | grep spike
* spike          [Git       ] (

Now let’s add our overlay

localhost ~ # layman -a spike

* Adding overlay,...
* Running Git... # ( cd /var/lib/layman  && /usr/bin/git clone /var/lib/layman/spike )
Cloning into '/var/lib/layman/spike'...
remote: Counting objects: 11045, done.
remote: Total 11045 (delta 0), reused 0 (delta 0), pack-reused 11045
Receiving objects: 100% (11045/11045), 3.90 MiB | 304.00 KiB/s, done.
Resolving deltas: 100% (4945/4945), done.
Checking connectivity... done.
 * Running Git... # ( cd /var/lib/layman/spike  && /usr/bin/git config "layman" )
 * Running Git... # ( cd /var/lib/layman/spike  && /usr/bin/git config "layman@localhost" )
 * Successfully added overlay(s) spike.

After that we should see the desired packages:

localhost ~ # emerge -s chromeos-sources
*  sys-kernel/chromeos-sources [ Masked ]
      Latest version available: 9999
      Latest version installed: [ Not Installed ]
      Size of files: 0 KiB
      Description:   Linux kernel source for the Samsung Chromebook
      License:       GPL-2 !deblob? ( freedist )

[ Applications found : 1 ]

Before we compile the kernel let’s get the mkimage binary installed as well

localhost ~ # emerge -av u-boot-tools

and for the kernel source install

localhost ~ # emerge -av chromeos-sources

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    *] sys-kernel/chromeos-sources-9999:9999::spike  USE="-build -deblob -symlink" 0 KiB

Total: 1 package (1 new), Size of downloads: 0 KiB

Would you like to merge these packages? [Yes/No] y

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-kernel/chromeos-sources-9999::spike
>>> Preparing to unpack ...
>>> Unpacking source...
fatal: repository 'git' does not exist
fatal: repository 'clone' does not exist
Cloning into bare repository '/usr/portage/distfiles/egit-src/kernel'...
remote: Sending approximately 1.05 GiB ...
remote: Counting objects: 237538, done
remote: Finding sources: 100% (31453/31453)  
remote: Total 4173841 (delta 3451254), reused 4173436 (delta 3451254)
Receiving objects: 100% (4173841/4173841), 1.08 GiB | 230.00 KiB/s, done.
Resolving deltas: 100% (3451824/3451824), done.
Checking connectivity... done.
GIT NEW clone -->
   at the commit:            8a084bb91a783e55f146f19940b33af18aeab538
   branch:                   chromeos-3.4
   storage directory:        "/usr/portage/distfiles/egit-src/kernel"
   checkout type:            bare repository
Cloning into '/var/tmp/portage/sys-kernel/chromeos-sources-9999/work/linux-3.4.0-chromeos'...
Checking out files: 100% (39093/39093), done.
Branch branch-chromeos-3.4 set up to track remote branch chromeos-3.4 from origin.
Switched to a new branch 'branch-chromeos-3.4'
>>> Unpacked to /var/tmp/portage/sys-kernel/chromeos-sources-9999/work/linux-3.4.0-chromeos
>>> Source unpacked in /var/tmp/portage/sys-kernel/chromeos-sources-9999/work
>>> Preparing source in /var/tmp/portage/sys-kernel/chromeos-sources-9999/work/linux-3.4.0-chromeos ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-kernel/chromeos-sources-9999/work/linux-3.4.0-chromeos ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sys-kernel/chromeos-sources-9999/work/linux-3.4.0-chromeos ...
>>> Source compiled.
>>> Test phase [not enabled]: sys-kernel/chromeos-sources-9999

>>> Install chromeos-sources-9999 into /var/tmp/portage/sys-kernel/chromeos-sources-9999/image/ category sys-kernel
>>> Copying sources ...
>>> Completed installing chromeos-sources-9999 into /var/tmp/portage/sys-kernel/chromeos-sources-9999/image/

>>> Installing (1 of 1) sys-kernel/chromeos-sources-9999::spike
 * checking 39117 files for package collisions
1000 files checked ...
39000 files checked ...
>>> Merging sys-kernel/chromeos-sources-9999 to /
--- /usr/
--- /usr/src/
>>> /usr/src/linux-3.4.0-chromeos/
>>> /usr/src/linux-3.4.0-chromeos/fs/adfs/map.c
 * if you want to get the default kernel config just run:
 * ./chromeos/scripts/prepareconfig chromeos-exynos5
>>> sys-kernel/chromeos-sources-9999 merged.

>>> Recording sys-kernel/chromeos-sources in "world" favorites file...
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.

So let’s link that kernel source to /usr/src/linux:

localhost ~ # ln -s /usr/src/linux-3.4.0-chromeos/ /usr/src/linux

Compile the Kernel

So let’s prepare the kernel source (I just followed the same steps as I did before)

localhost ~ # cd /usr/src/linux
localhost linux # ./chromeos/scripts/prepareconfig chromeos-exynos5

Then make sure the config is good:

localhost linux # make oldconfig

I then enabled some extra options in the kernel:

localhost linux # make menuconfig

Here are the options I enabled:


File systems  --->
   Network File Systems  --->
      <M>   NFS client support
      [M]     NFS client support for NFS version 4
      <M>     NFS client support for NFS version 2 (NEW)
      <M>     NFS client support for NFS version 3 (NEW)

File systems --->
    [*] Dnotify support


File systems --->
    <M> Kernel automounter version 4 support (also supports v3)

And here is what I disabled:

Warnings as Errors

Kernel Hacking --->
    [ ] Treat compiler warnings as errors  

Buffer Overflow Detection

Kernel Features --->
  [ ] Enable -fstack-protector buffer overflow detection 

Chromium OS Security

Security Options --->
  < > Chromium OS Security Module

Now let’s build the kernel

localhost linux # time make uImage
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
CALL scripts/
CHK include/generated/compile.h
Kernel: arch/arm/boot/Image is ready
Kernel: arch/arm/boot/zImage is ready
UIMAGE arch/arm/boot/uImage
Image Name: Linux-3.8.11
Created: Sun Feb 1 18:18:07 2015
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3596560 Bytes = 3512.27 kB = 3.43 MB
Load Address: 40008000
Entry Point: 40008000
Image arch/arm/boot/uImage is ready

real 21m42.837s
user 24m30.555s
sys 2m47.515s

Only 21 minutes :) Now let’s build the modules:

localhost linux # time make modules
CC sound/usb/snd-usb-audio.mod.o
LD [M] sound/usb/snd-usb-audio.ko
CC sound/usb/snd-usbmidi-lib.mod.o
LD [M] sound/usb/snd-usbmidi-lib.ko

real 13m43.842s
user 8m47.570s
sys 0m59.675s

Now let’s install the modules

localhost linux # make modules_install

Now let’s create the device tree files:

localhost linux # make dtbs

Now let’s copy the kernel (uImage) and kernel device tree db into place:

localhost linux # cp arch/arm/boot/uImage /boot/vmlinux.uimg
localhost linux # cp arch/arm/boot/dts/exynos5250-snow.dtb /boot/exynos5250-snow.dtb

I configured nv-u-boot to be able to read those file and boot from them (so I didn’t have to sign them or combine them into one file). The setup was covered here.

Prepare Gentoo for boot

Let’s go ahead and create the fstab file:

localhost ~ # cat /etc/fstab 
/dev/mmcblk1p3		/		ext4		noatime		0 1
/dev/mmcblk1p2		/boot		ext2		defaults	1 2
#/dev/SWAP		none		swap		sw		0 0

Let’s setup the networking

localhost ~ # ln -s /etc/init.d/net.lo /etc/init.d/net.mlan0
localhost ~ # echo 'hostname="crbook"' > /etc/conf.d/hostname
localhost ~ # cat /etc/conf.d/net
localhost ~ # rc-update add net.mlan0 default
* service net.mlan0 added to runlevel default

Since I only have a wireless card let’s install wpa_supplicant and dhcp:

localhost ~ # cat /etc/portage/package.use/wpa_supplicant 
net-wireless/wpa_supplicant wps
localhost ~ # time emerge -av wpa_supplicant
real 44m10.542s
user 18m28.330s
sys 7m2.500s
localhost ~ # cat /etc/portage/package.use/dhcp 
net-misc/dhcp -server
localhost ~ # emerge -av dhcp

Now let’s configure the WPA password:

localhost ~ # wpa_passphrase wireless 
# reading passphrase from stdin

and here is the wpa_supplicant config

localhost ~ # cat /etc/wpa_supplicant/wpa_supplicant.conf 
pairwise=CCMP TKIP

Set the root password:

localhost ~ # passwd 
New password: 
Retype new password: 
passwd: password updated successfully

Let’s install syslog-ng in case we need troubleshoot anything:

localhost ~ # time emerge -av syslog-ng
real 6m57.220s
user 3m4.085s
sys 1m11.430s

lastly install the linux-firmware files (this way the wireless card can load)

localhost ~ # emerge -av linux-firmware

At this point your can exit the chroot, unmount every directory from the rootfs, and reboot. You should see openrc start appropriate services and then a prompt will be presented where you can login with the root user.

Post Install Configs

After the reboot you can login and confirm the wireless connected:

crbook ~ # wpa_cli list_networks
Selected interface 'mlan0'
network id / ssid / bssid / flags
0   wireless   any [CURRENT]

Let’s generate the locale:

crbook ~ # grep -vE '^$|^#' /etc/locale.gen
en_US ISO-8859-1
en_US.UTF-8 UTF-8
crbook ~ # locale-gen
 * Generating 2 locales (this might take a while) with 1 jobs
 *  (1/2) Generating en_US.ISO-8859-1 ... [ ok ]
 *  (2/2) Generating en_US.UTF-8 ... [ ok ]
 * Generation complete

Let’s also install the dns utils:

crbook ~ # emerge -av bind-tools

Install PFL

There is a utility called e-file which can tell you which package provides a certain file, it’s part of the pfl package so let’s install that:

crbook ~ # emerge -av pfl

Prior to using we have to build the cache:

crbook ~ # pfl
working on (604 of 607) dev-db/libzdb-3.0
working on (605 of 607) mail-mta/ssmtp-2.64-r2
working on (606 of 607) sys-process/psmisc-22.21-r2
working on (607 of 607) sys-process/procps-3.3.9-r2
writing xml file /tmp/pfltp8OCc.xml ...
uploading xml file /tmp/pfltp8OCc.xml ...
deleting xml file /tmp/pfltp8OCc.xml ...

After that you can run the following:

crbook ~ # e-file sd8797_uapsta.bin
[I] sys-kernel/linux-firmware
    Available Versions: 20130728 20130711 20130530 20130421 99999999 20141009 20140902 20140809 20140603 20131230
    Last Installed Ver: 20140902(Sun 01 Feb 2015 08:55:30 PM MST)
    Description:        Linux firmware files
    Matched Files:      /usr/lib/firmware/mrvl/sd8797_uapsta.bin; /lib/firmware/mrvl/sd8797_uapsta.bin;

There is also an updated version which can tell you which files a remote package owns. To install let’s download the script:

crbook ~ # wget

Then let’s install it under /usr/bin:

crbook ~ # cp /usr/bin/
crbook ~ # ln -s /usr/bin/ /usr/bin/e-file-py
crbook ~ # chmod +x /usr/bin/

It uses the python beautifulsoup module so let’s install that:

crbook ~ # emerge -av beautifulsoup

After that you can do things like this:

crbook ~ # e-file-py -l dev-libs/libgee-0.6.8

Install eix

There is another cool tool called eix which gives a pretty concise view of what versions and USE flags a certain package contains. So let’s install that:

crbook ~ # emerge -av eix

To just create the cache for eix we can run the following:

crbook ~ # eix-update
Reading Portage settings ..
Building database (/var/cache/eix/portage.eix) ..
[0] 'gentoo' /usr/portage/ (cache: metadata-md5-or-flat)
     Reading category 166|166 (100%) Finished             
Applying masks ..
Calculating hash tables ..
Writing database file /var/cache/eix/portage.eix ..
Database contains 18219 packages in 166 categories.

To sync portage and then run eix-update we can run the following:

crbook ~ # eix-sync

This will run the following

emerge --sync

If you want the eix-sync command to update overlays (ie run layman -S), then create the following

crbook ~ # cat /etc/eix-sync.conf

Then the eix-sync command will do this

emerge --sync
laymans -S

I ended up adding the following to crontab (after instaling vixie-cron):

crbook ~ # crontab -l | grep -i eix
00 04 * * * /usr/bin/eix-update -q

After it’s ready you can check versions like this:

crbook ~ # eix libgee
* dev-libs/libgee
     Available versions:  
     (0)    0.6.7 0.6.8
     (0.8)  0.14.0 ~0.16.1(0.8/2)
     Description:         GObject-based interfaces and classes for commonly used data structures

Install hwinfo

Let’s instal hwinfo since lspci doesn’t work. First we need to allow that package to be complied on our platform, that’s done with the package.accept_keywords. So I created the following file:

crbook ~ # cat /etc/portage/package.accept_keywords/hwinfo
sys-apps/hwinfo **

And then install the package

crbook ~ # emerge -av hwinfo

Now we cancheck out a summary of the machine:

crbook ~ # hwinfo --short
  /dev/input/event0    cros-ec-i2c
network interface:
  mlan0                Ethernet network interface
  uap0                 Ethernet network interface
  p2p0                 Ethernet network interface
  lo                   Loopback network interface
  /dev/mmcblk0rpmb     Disk
  /dev/mmcblk0boot0    Disk
  /dev/mmcblk0boot1    Disk
  /dev/mmcblk0         Disk
  /dev/mmcblk1         Disk
  /dev/mmcblk0p1       Partition
  /dev/mmcblk0p2       Partition
  /dev/mmcblk0p3       Partition
  /dev/mmcblk0p4       Partition
  /dev/mmcblk0p5       Partition
  /dev/mmcblk0p6       Partition
  /dev/mmcblk0p7       Partition
  /dev/mmcblk0p8       Partition
  /dev/mmcblk0p9       Partition
  /dev/mmcblk0p10      Partition
  /dev/mmcblk0p11      Partition
  /dev/mmcblk0p12      Partition
  /dev/mmcblk1p1       Partition
  /dev/mmcblk1p2       Partition
  /dev/mmcblk1p3       Partition
  /dev/mmcblk1p12      Partition
                       Linux 3.8.11 ehci_hcd S5P EHCI Host Controller
                       Standard Microsystems Hub
                       Linux 3.8.11 ohci_hcd EXYNOS OHCI Host Controller
                       Linux 3.8.11 xhci-hcd xHCI Host Controller
                       Linux 3.8.11 xhci-hcd xHCI Host Controller
                       Main Memory
                       Generic WebCam SC-03FFM12339N

You can also just get the CPU information:

crbook ~ # hwinfo --cpu
01: None 00.0: 10103 CPU                                        
  [Created at cpu.269]
  Unique ID: rdCR.j8NaKXDZtZ6
  Hardware Class: cpu
  Arch: ARM
  Vendor: "ARM Limited"
  Model: 0.4.0 ""
  Platform: "SAMSUNG EXYNOS5 (Flattened Device Tree)"
  Features: swp,half,thumb,fastmult,vfp,edsp,thumbee,neon,vfpv3,tls,vfpv4,idiva,idivt,
  BogoMips: 199.30
  Config Status: cfg=new, avail=yes, need=no, active=unknown

02: None 01.0: 10103 CPU
  [Created at cpu.269]
  Unique ID: wkFv.j8NaKXDZtZ6
  Hardware Class: cpu
  Arch: ARM
  Vendor: "ARM Limited"
  Model: 0.4.0 ""
  Platform: "SAMSUNG EXYNOS5 (Flattened Device Tree)"
  Features: swp
  BogoMips: 199.30
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Setup Video

The defaults are okay so let’s just emerge Xorg-Server:

crbook ~ # time emerge -av xorg-server
real    98m56.704s
user    134m16.475s
sys 15m27.490s

The main reason it took so long is because it had to compile llvm. If you ever want to find out how long a compile took you can use the genlop utility. First install it:

crbook ~ # emerge -av genlop

and then you can run the following to find out how long a specific package took to compile:

crbook ~ # genlop -t llvm
 * sys-devel/llvm

     Mon Feb  2 05:49:38 2015 >>> sys-devel/llvm-3.5.0
       merge time: 51 minutes and 54 seconds.

If there is an emerge going in the background you can check how it will take to finish (estimating from the last compile time):

crbook ~ # genlop -c

 Currently merging 1 out of 1

 * www-client/chromium-41.0.2272.16

       current merge time: 1 hour, 14 minutes and 44 seconds.
       ETA: 8 hours, 9 minutes and 8 seconds.

For the window manager I use icewm, I ended up installing an older version cause the latest one was causing Focus issues:

crbook ~ # emerge -av =x11-wm/icewm-1.3.8

I then held (masked) the other version by creating the following file:

crbook ~ # cat /etc/portage/package.mask/icewm

This way if a newer version comes out, the emerge world will pick up an update but skip that specific version. And now let’s get the display manager

crbook ~ # time emerge -av lightdm
real    89m53.930s
user    92m24.960s
sys     18m43.525s

To enable the display manager to start on boot we have to enable the following services:

crbook ~ # rc-update add dbus default
 * service dbus added to runlevel default
crbook ~ # rc-update add xdm default
 * service xdm added to runlevel default

and set the following option:

crbook ~ # grep DISPLAY /etc/conf.d/xdm

For the configs I just copied the old configs from my arch linux machine (but the setup was covered here). Here is the jist of it:

mkdir ~/backup
mv /etc/X11/xorg.conf.d/* ~/backup/
cd /etc/X11/xorg.conf.d/
sed -i 's/gb/us/g' 10-keyboard.conf

After a reboot I was able to login and start an icewm-session without issue. I also added the following udev rule to dim the brightness on boot, the default one is the highest one and it’s just a waste of battery:

crbook ~ # cat /etc/udev/rules.d/81-backlight.rules
SUBSYSTEM=="backlight", ACTION=="add", KERNEL=="backlight.10", ATTR{brightness}="1000"

Configure Audio

Let’s install pulseaudio and alsa

crbook ~ # emerge -av pulseaudio

For alsa create the following package.use settings:

crbook ~ # cat /etc/portage/package.use/alsa-plugins
media-plugins/alsa-plugins libsamplerate
crbook ~ # time emerge -av alsa-utils alsa-plugins
real    4m0.621s
user    2m32.865s
sys     0m40.975s

If you want any changes you made in alsamixer to stick during reboot we need to enable the following service:

crbook ~ # rc-update add alsasound boot
 * service alsasound added to runlevel boot

And make sure restore and save options are enabled:

crbook ~ # grep -Ev '^#|^$' /etc/conf.d/alsasound

After that you should see the available sound cards with aplay:

crbook ~ # aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: DAISYI2S [DAISY-I2S], device 0: Playback HiFi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: DAISYI2S [DAISY-I2S], device 1: Capture HiFi-1 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

You can also make sure the UCM profile is appropriately used for the Daisy Sound Card (this ensures the appropriate channels are already um-muted):

crbook ~ # alsaucm listcards
  0: DAISY-I2S
    Daisy internal card
  1: PandaBoard
  2: PandaBoardES
  3: SDP4430
  4: tegraalc5632

Lastly enable alsa to be loaded by pulseaudio:

crbook ~ # grep alsa-sink /etc/pulse/ 
load-module module-alsa-sink

Configure Browser

I ended compiling chromium, first I had to enable all the right options for all the packages:

crbook ~ # cat /etc/portage/package.use/harfbuzz
media-libs/harfbuzz icu
crbook ~ # cat /etc/portage/package.use/zlib
sys-libs/zlib minizip
crbook ~ # cat /etc/portage/package.use/libxml2
dev-libs/libxml2 icu
crbook ~ # cat /etc/portage/package.use/chromium
www-client/chromium -bindist neon
crbook ~ # cat /etc/portage/package.accept_keywords/re2
dev-libs/re2 ~arm
crbook ~ # cat /etc/portage/package.accept_keywords/jsoncpp
dev-libs/jsoncpp ~arm
crbook ~ # cat /etc/portage/package.accept_keywords/chromium
www-client/chromium ~arm

The compile took 9 hours:

crbook ~ # time emerge -av chromium
real    565m29.370s
user    999m18.375s
sys     78m33.000s

To get the flash I ended borrowing the package from arch linux:

crbook ~ # wget

Then I extracted it:

crbook ~ # tar xvzf chromium-pepper-flash-

and the copied it to /usr/lib:

crbook ~ # rsync -avzP usr/lib/. /usr/lib/.

Lastly configured the browser to look for that version:

crbook ~ # cat /etc/chromium/default
# Default settings for chromium. This file is sourced by /bin/bash from
# the chromium launcher.

# Options to pass to chromium.
CHROMIUM_FLAGS=" --ppapi-flash-path=/usr/lib/PepperFlash/ --ppapi-flash-version="

After that flash worked on the chromium browser.

Misc Configs

To enable rc.log (just to see what services fail during boot), I ended up modifying the following:

crbook ~ # $ grep ^rc_log /etc/rc.conf

To enable the power button to actually shutdown the laptop just had to install acpid:

crbook ~ # emerge -av acpid
crbook ~ # service acpid start
crbook ~ # rc-update add acpid default

Ran into an issue with freerdp (it kept trying to use the wrong float abi… the issue is described here). So I just manually compiled it, first got the source:

crbook ~ # git clone
crbook ~ # cd FreeRDP

Here is the command to prepare the source (I included the -DARM_FP_ABI=hard flag):


To install just run the following:

crbook FreeRDP # make install

After compiling keepass it failed to start with the following error:

mini-codegen.c:807, condition `i == sel' not met

I found a couple of bugs on that:

and it’s the same as the freerdp issue, it’s not compiling using the hard float abi. It seems later versions fix the issue. I found an overlay which contained later versions. So first I added the overlay:

crbook ~ # layman -a dotnet

Then create the appropriate packake.accept_keywords:

crbook ~ # cat /etc/portage/package.accept_keywords/mono 
dev-lang/mono ~arm

I found the latest version with eix:

crbook ~ # eix dev-lang/mono
[?] dev-lang/mono
     Available versions:  *2.10.9-r2^t ~*3.0.7 ~*3.2.3 ~*3.2.8 ~*3.10.0[1] ~*3.12.0[1] **9999[1] {debug doc minimal nls pax_kernel xen}
     Installed versions:  3.12.0[1](04:16:58 PM 02/15/2015)(nls -debug -doc -minimal -pax_kernel -xen)
     Description:         Mono runtime and class libraries, a C# compiler/interpreter

* dev-lang/mono-basic
     Available versions:  *2.10^t
     Description:         Visual Basic .NET Runtime and Class Libraries

[1] "dotnet" /var/lib/layman/dotnet

and the installed the latest version:

crbook ~ # emerge -av =dev-lang/mono-3.12.0

This would’ve worked too:

crbook ~ # emerge -av mono

Then after recompiling keepass and it started up without issues:

crbook ~ # emerge -av keepass

Installed the Oracle Embedded Java version, first downloaded it from their site and extracted it:

crbook ~ # tar xzf jdk-8u33-linux-arm-vfp-hflt.tar.gz

Then put it under /usr/local

crbook ~ # mv jdk1.8.0_33/ /usr/local/.

Now let’s create the link to java

crbook ~ # ln -s /usr/local/jdk1.8.0_33/bin/java /usr/local/bin/java

Here is the version:

crbook ~ # java -version
java version "1.8.0_33"
Java(TM) SE Runtime Environment (build 1.8.0_33-b05)
Java HotSpot(TM) Client VM (build 25.33-b05, mixed mode)

I was able to use that version with other application without issues.

I added the following configuration to switch to tty1 if the system is shutting down:

crbook ~ # cat /etc/local.d/00_shutdown.stop
/usr/bin/chvt 1

This way I could see what services are shutting down during a system halt or reboot.

Published by Karim Elatov

16 February 2015