Difference between pages "Building a Kernel from Source" and "Package:Pianobar"

From Funtoo
(Difference between pages)
Jump to: navigation, search
(Configuring the kernel)
 
 
Line 1: Line 1:
Setting up a proper kernel yourself - lean, mean and tailored to your hardware,  is the challenge by which a linux user can graduate to becoming a Funtoo knight ;-)
+
{{Ebuild
 
+
|Summary=Pianobar is a console client for the personalized web radio Pandora.
Even though many of us are using enterprise-ready kernels in datacenters, there is almost nobody who hasn't at least considered building a kernel for his laptop / PC.
+
|CatPkg=media-sound/pianobar
We are showing here how an intermediate Linux user can use an alternative to the standard beginners "genkernel" approach,  to compile a custom kernel,  in a relatively speedy and easy set up.
+
|Maintainer=
 
+
|Homepage=https://github.com/PromyLOPh/pianobar
== Minimum Requirements ==
+
}}
* '''Understand the command line'''
+
To install Pianobar, emerge it:
* '''Know where the kernel files are located'''
+
 
+
== Assumptions ==
+
You start from an installed Funtoo system on the disk, or at least, you are on stage3 in a chrooted environment from a live cd, following somehow the Funto [[Installation (Tutorial)|Installation Tutorial]].
+
 
+
== Less advanced version ==
+
=== Emerging the kernel sources ===
+
To begin, we have to figure out which kernel sources we will use. If you are unsure about which sources are available and what their benefits and drawbacks are, check out the [[Funtoo_Linux_Kernels| Kernels]] page.
+
 
+
After you have made a decsion as to which kernel you want to install, emerge it:
+
 
<console>
 
<console>
###i## emerge vanilla-sources
+
###i## emerge pianobar
 
</console>
 
</console>
Portage will now go about installing the sources to ''/usr/src''. It will also symlink the kernel-version directory to a directory called ''linux''.
 
  
=== Configuring the kernel ===
+
== Pianobar configuration ==
Now that the kernel sources are on your system, you should configure them. To do this, change your directory to ''/usr/src/linux''
+
=== Easy login ===
<console>
+
After you have emerged Pianobar, you can run it with <code>pianobar</code>. If you dislike typing your username and password every time that you run pianobar, create the file <code>~/.config/pianobar/config</code> and add the following lines to it:
###i## cd /usr/src/linux
+
{{file|name= ~/.config/pianobar/config|desc= |body=
</console>
+
password = YOURPASSWORD
As we are now in the kernel sources directory, we can run a script that allows us to modify them. Run:
+
user = user@email.com
<console>
+
}}
###i## make menuconfig
+
</console>
+
While you edit the sources, keep the following in mind:
+
* To build something into your kernel, press y when you have it selected.
+
* To exclude something from your kernel, press n when you have it selected.
+
* To build something as a module, press m.
+
  
Things that you may need to include in your kernel:
+
=== Easy login (with encryption) ===
* Wireless/LAN drivers
+
If leaving a plaintext password for your Pandora account somewhere on your filesystem makes you nervous, you can use gpg to decrypt a file that contains your password. Change your configuration to reflect the one below if you would like to encrypt your password:
* Support for your graphics card
+
{{file|name=~/.config/pianobar/config|desc= |body=
* Support for your audio card
+
password_command = gpg --decrypt ~/.passwords/pianobar
* Support for USB devices
+
user = user@email.com
{{fancynote| Many pages on the wiki will tell you the kernel requirements for the application that they are about. Keep your eyes open for the blue background, white text sections of pages. Like on this one: [[uvesafb| uvesafb]]}}
+
 
+
=== Building and installing the kernel sources ===
+
After you finish configuring your kernel sources, you will need to build them. To build your sources, run the following:
+
<console>
+
###i## make
+
</console>
+
{{fancytip| You can add -j<number of processing cores + 1> after make to build the kernel more quickly.}}
+
 
+
When the kernel and its modules finish building, install them:
+
<console>
+
###i## make install modules_install
+
</console>
+
Now that you have installed your kernel and modules, it is a good idea to install an initramfs. If your system has a separate ''/usr'' partition, is encrypted, or uses some other non-standard configuration, it will probably not boot without an initramfs. See [[Building_a_Kernel_from_Source#Initramfs| Initramfs]].
+
 
+
== Advanced version ==
+
=== Getting ready to start ===
+
 
+
{{fancynote| In this case we are building a kernel that is booting root in LVM over encrypted LUKS container.
+
If you don't have this setup, don't worry, you just don't need all the modules, but everything else is similar.}}
+
First, there is the decision which linux kernel sources we need.
+
There are plenty of them in the repositories around, often it is not easy to distinguish between them.
+
 
+
I would always trust my distribution of choice and take what is has to offer - and funtoo has a lot to offer!
+
 
+
I really do recommend (especially if it is your first time) to build a debian-sourced genkernel like described in chapter 5 "Using Debian-Sources with Genkernel" in the [[Funtoo_Linux_Kernels| Funtoo Kernels Tutorial]].
+
 
+
From there you should have a running system booting nicely from your own build (just little bit bloated) kernel. This is more than you can expect from any other ready to go distribution.
+
 
+
{{fancynote| We are using RedHat's dracut in order to build a nice initramfs (containing all the necessary tools and extra drivers our kernel might need to start the system). Although dracut is the way to go, more sophisticated and not as buggy as gentoo's genkernel approach, more and more funtoo geeks start using slashbeast's better-initramfs, which we will cover at the end of this howto! So after having set up a genkernel from debian or gentoo sources we are going to build a kernel with either (or both) dracut or/and better-initramfs. So gentoo sources with genkernel is always my backup if anything is not working correctly on my system. For the slightly more geeky approach with my own initram I am using pf-sources, ck-sources or any other more or less heavily patched sources.}}
+
 
+
Let's go!
+
 
+
=== Kernel Sources ===
+
The source you use on your system is up to you. For a laptop or desktop system, the following are recommended:
+
* '''{{Package|sys-kernel/pf-sources}}'''
+
* '''{{Package|sys-kernel/ck-sources}}'''
+
* '''{{Package|sys-kernel/gentoo-sources}}'''
+
* '''{{Package|sys-kernel/git-sources}}'''
+
* '''{{Package|sys-kernel/sysrescue-std-sources}}'''
+
* '''{{Package|sys-kernel/debian-sources}}'''
+
{{fancynote| If you are unsure of which sources you would like to use, emerge <code>gentoo-sources</code>. That's always a safe bet for a general system. For more information on available kernels, check out: [[Funtoo Linux Kernels]]}}
+
 
+
=== Prerequisites ===
+
 
+
Regardless of the tools you already have installed, it is recommended to follow the steps below, even if you find them to be redundant.
+
First, we edit our <code>/etc/portage/make.conf</code>:
+
 
+
<pre>
+
#These compiler flags are just tweaking (optimazation) and NOT necessary:
+
CFLAGS="-O2 -pipe -march=native -ftracer -fforce-addr"
+
CXXFLAGS="${CFLAGS} -fpermissive -fomit-frame-pointer"
+
KDIR=/usr/src/linux
+
KERNEL="symlink build"
+
USE="$KERNEL ....here are your use flags...."
+
## These modules are available:
+
## DRACUT_MODULES="dracut_modules_biosdevname dracut_modules_btrfs dracut_modules_caps dracut_modules_crypt dracut_modules_crypt-gpg dracut_modules_dmraid dracut_modules_dmsquash-live dracut_modules_gensplash dracut_modules_iscsi dracut_modules_livenet dracut_modules_lvm dracut_modules_mdraid dracut_modules_multipath dracut_modules_nbd dracut_modules_nfs dracut_modules_plymouth dracut_modules_ssh-client dracut_modules_syslog"
+
## We will use these modules for LVM / LUKS:
+
DRACUT_MODULES="crypt lvm plymouth biosdevname dmraid crypt-gpg dmsquash-live ssh-client syslog"
+
</pre>
+
 
+
Next, we set the package keywords by adding the following to <code>/etc/portage/package.use</code>:
+
 
+
<pre>
+
sys-kernel/dracut dm net device-mapper crypt lvm
+
</pre>
+
 
+
{{fancynote| If you don't have lvm over encrypted LUKS you just add the "net" keyword here, or "selinux".}}
+
 
+
 
+
Next, we build our packages:
+
<console>
+
###i## emerge -av app-portage/gentoolkit sys-kernel/pf-sources sys-kernel/dracut sys-boot/plymouth sys-boot/plymouth-openrc-plugin
+
</console>
+
 
+
=== Preparing the kernel ===
+
 
+
We go now to the sources directory and enter the following commands to update the kernel's  .config  file:
+
<console>
+
###i## cd /usr/src/linux/
+
###i## make clean
+
  CLEAN  .
+
  CLEAN  arch/x86/kernel/acpi/realmode
+
  CLEAN  arch/x86/kernel/cpu
+
  CLEAN  arch/x86/kernel
+
  CLEAN  arch/x86/vdso
+
  CLEAN  arch/x86/lib
+
  CLEAN  drivers/gpu/drm/radeon
+
  CLEAN  drivers/net/wan
+
  CLEAN  drivers/scsi/aic7xxx
+
  CLEAN  drivers/tty/vt
+
  CLEAN  drivers/video/logo
+
  CLEAN  firmware
+
  CLEAN  kernel
+
  CLEAN  lib/raid6
+
  CLEAN  lib
+
  CLEAN  security/apparmor
+
  CLEAN  security/selinux
+
  CLEAN  usr
+
  CLEAN  arch/x86/boot/compressed
+
  CLEAN  arch/x86/boot
+
  CLEAN  .tmp_versions
+
  CLEAN  vmlinux System.map .tmp_kallsyms2.S .tmp_kallsyms1.o .tmp_kallsyms2.o .tmp_kallsyms1.S .tmp_vmlinux1 .tmp_vmlinux2 .tmp_System.map
+
###i## zcat /proc/config.gz > /usr/src/linux/.config
+
</console>
+
 
+
Next, we run <tt>make localmodconfig</tt>. You will get some questions which you can answer mostly with either M (compiled as a module) or Y (compiled directly into the kernel). If you are not sure what to choose, press enter, and the default option will be selected.
+
<console>
+
###i## make localmodconfig
+
Enable different security models (SECURITY) [Y/n/?] y
+
Enable the securityfs filesystem (SECURITYFS) [Y/?] y
+
Socket and Networking Security Hooks (SECURITY_NETWORK) [Y/?] y
+
Security hooks for pathname based access control (SECURITY_PATH) [Y/?] y
+
Low address space for LSM to protect from user allocation (LSM_MMAP_MIN_ADDR) [65536] 65536
+
NSA SELinux Support (SECURITY_SELINUX) [Y/n/?] y
+
  NSA SELinux boot parameter (SECURITY_SELINUX_BOOTPARAM) [N/y/?] n
+
  NSA SELinux runtime disable (SECURITY_SELINUX_DISABLE) [N/y/?] n
+
  NSA SELinux Development Support (SECURITY_SELINUX_DEVELOP) [Y/n/?] y
+
  NSA SELinux AVC Statistics (SECURITY_SELINUX_AVC_STATS) [Y/n/?] y
+
  NSA SELinux checkreqprot default value (SECURITY_SELINUX_CHECKREQPROT_VALUE) [1] 1
+
  NSA SELinux maximum supported policy format version (SECURITY_SELINUX_POLICYDB_VERSION_MAX) [Y/n/?] y
+
    NSA SELinux maximum supported policy format version value (SECURITY_SELINUX_POLICYDB_VERSION_MAX_VALUE) [19] 19
+
TOMOYO Linux Support (SECURITY_TOMOYO) [Y/n/?] y
+
  Default maximal count for learning mode (SECURITY_TOMOYO_MAX_ACCEPT_ENTRY) [2048] 2048
+
  Default maximal count for audit log (SECURITY_TOMOYO_MAX_AUDIT_LOG) [1024] 1024
+
  Activate without calling userspace policy loader. (SECURITY_TOMOYO_OMIT_USERSPACE_LOADER) [Y/n/?] y
+
AppArmor support (SECURITY_APPARMOR) [Y/n/?] y
+
  AppArmor boot parameter default value (SECURITY_APPARMOR_BOOTPARAM_VALUE) [1] 1
+
Integrity Measurement Architecture(IMA) (IMA) [Y/n/?] y
+
EVM support (EVM) [N/y/?] (NEW)
+
Default security module
+
  1. SELinux (DEFAULT_SECURITY_SELINUX)
+
  2. TOMOYO (DEFAULT_SECURITY_TOMOYO)
+
  3. AppArmor (DEFAULT_SECURITY_APPARMOR)
+
> 4. Unix Discretionary Access Controls (DEFAULT_SECURITY_DAC)
+
choice[1-4?]: 4
+
warning: (ACPI_HOTPLUG_CPU) selects ACPI_CONTAINER which has unmet direct dependencies (ACPI && EXPERIMENTAL)
+
warning: (MEDIA_TUNER) selects MEDIA_TUNER_TEA5761 which has unmet direct dependencies (MEDIA_SUPPORT && VIDEO_MEDIA && I2C && EXPERIMENTAL)
+
#
+
# configuration written to .config
+
#
+
warning: (GFS2_FS) selects DLM which has unmet direct dependencies (EXPERIMENTAL && INET && SYSFS && CONFIGFS_FS && (IPV6 || IPV6=n))
+
warning: (IMA) selects TCG_TPM which has unmet direct dependencies (HAS_IOMEM && EXPERIMENTAL)
+
warning: (MEDIA_TUNER) selects MEDIA_TUNER_TEA5761 which has unmet direct dependencies (MEDIA_SUPPORT && VIDEO_MEDIA && I2C && EXPERIMENTAL)
+
warning: (ACPI_HOTPLUG_CPU) selects ACPI_CONTAINER which has unmet direct dependencies (ACPI && EXPERIMENTAL)
+
</console>
+
 
+
Now comes the most adventurous part!
+
 
+
=== Building the Kernel ===
+
<console>
+
###i## make -j8  bzImage
+
###i## make -j8 modules
+
###i## make modules_install
+
###i## make install
+
</console>
+
 
+
== Initramfs ==
+
{{fancywarning| Make sure that you have built and installed your kernel sources / modules before building an initramfs.}}
+
=== Initramfs, or not? ===
+
The reason to build a kernel with an initramfs is mostly for interoperability (e.g. live-cd's) and special features like an included busybox, ssh, etc.  But mostly, and that's why we are doing this here now, to have a proper kernel up and running quick'n dirty in a reasonable time without fighting hours and days until a more or less exotic hardware is perfectly run by the kernel.
+
After having a proper basic kernel running with the help of an initramfs, I really recommend you to go a step further and build a true kernel with all features includes without an initramfs. But this could be pain in the butt and very time consuming - so we do it the funtoo way here - at least in the second example when we stick to better-initramfs instead of Red-Hat's ''dracut''.
+
 
+
=== Option two: using better-initramfs ===
+
 
+
Piotr's better-initramfs is another approach to building an initramfs. It is quick, nice and shiny, and is popular among funtoo'ers. The biggest plus is that, once built it is kernel version independent. Follow the instructions below to get better-initramfs up and running.
+
 
+
==== Downloading better-initramfs ====
+
<console>
+
###i## cd /opt
+
###i## git clone git://github.com/slashbeast/better-initramfs.git
+
###i## cd better-initramfs
+
</console>
+
Above, we have moved to the <code>/opt</code> directory, which is often used for '''opt'''ional software on Linux systems. Next, we get a copy of better-initramfs from github.com. Finally, we change to the better-initramfs directory so that we can build it in the next step.
+
 
+
==== Build better-initramfs ====
+
<console>
+
###i## bootstrap/bootstrap-all
+
###i## make prepare image
+
###i## cp output/initramfs.cpio.gz /boot
+
</console>
+
In this step, we first run the ''bootstrap-all'' command to build all of the applications and libraries required for better-initramfs. Then, we make an initramfs image using <code>make prepare image</code>. Lastly, we move the newly created initramfs to <tt>/boot</tt>.
+
 
+
=== Adjust boot.conf ===
+
 
+
Now that we have the initramfs and kernel sources, we can edit <tt>/etc/boot.conf</tt> to tell GRUB about our initramfs and kernel. The configuration below is for a system that is encrypted and uses lvm. If your system is not configured like this, take a look at this page: [https://bitbucket.org/piotrkarbowski/better-initramfs| better-initramfs configuration options].
+
{{file|name=/etc/boot.conf|desc= |body=
+
boot {
+
        generate grub
+
        default "Funtoo Linux"
+
        timeout 3
+
}
+
 
+
"Funtoo Linux" {
+
        kernel vmlinuz[-v]
+
        initrd /initramfs.cpio.gz
+
        params += enc_root=/dev/sda3 lvm luks root=/dev/mapper/vg-root rootfstype=ext4 quiet
+
}
+
 
+
"Funtoo Linux dracut" {
+
        kernel vmlinuz[-v]
+
## this is the dracut generated initrd
+
        initrd initramfs[-v].img
+
        params  = quiet rootfstype=ext4
+
        params += luks enc_root=/dev/sda3
+
        params += lvm root=/dev/mapper/vg-root
+
}
+
 
+
 
+
"Funtoo Linux genkernel" {
+
        kernel kernel-genkernel[-v]
+
        initrd initramfs-genkernel[-v]
+
        params = quiet rootfstype=ext4
+
        params += luks enc_root=/dev/sda3
+
        params += lvm root=/dev/mapper/vg-root
+
}
+
 
}}
 
}}
Okay,... here you go..! :)
 
  
update the <tt>grub.cfg</tt> with boot update, then reboot and see how it works!
+
=== Keybindings ===
 +
To configure keybindings, check out <code>man pianobar</code>. All keybindings can be added to <code>~/.config/pianobar/config</code>. All the keybindings in the man page will begin with the line <code>act_</code>.
  
<console>
+
=== Other configuration options ===
###i## boot-update -v   
+
{| {{table}}
 
+
!Option
boot-update 1.5.2 / Copyright 2009-2011 Funtoo Technologies
+
!Description
 
+
|-
[use option "-l" for license info, "-h" for help]
+
|audio_quality
 
+
|The quality of the audio. Can be set to: high, medium, or low.
* Generating config for grub...
+
|-
 
+
|autostart_station
DEFAULT > Funtoo Linux better-initramfs - vmlinuz-3.2.6-pf
+
|Select a station ID that you would like to play when Pianobar starts.
          Funtoo Linux dracut - vmlinuz-3.2.6-pf
+
|-
          Funtoo Linux genkernel - kernel-genkernel-x86_64-3.2.6-ck
+
|proxy
 
+
|Use a http proxy.
* Completed successfully.
+
|}
###i## reboot
+
</console>
+
 
+
=== Option one: Initrd with dracut ===
+
  
To build the initrd with dracut, we just execute:
+
== Troubleshooting ==
 +
=== Not compiled with threads support ===
 +
If you recieve the following warning message (<code>[aac @ 0x7faccc003cd0] Warning: not compiled with thread support, using thread emulation</code>) while running Pianobar, add threads support to ffmpeg, then rebuild it:
 
<console>
 
<console>
# ##i##dracut -f --fstab --xz /boot/initramfs-3.2.6-pf.img  3.2.6-pf
+
###i## echo "media-video/ffmpeg threads" > /etc/portage/package.use/ffmpeg
 +
###i## emerge ffmpeg
 
</console>
 
</console>
 
+
{{fancynote| As of [https://bugs.funtoo.org/browse/FL-1437 FL-1437], threads support should be enabled on ffmpeg by default.}}
Generally, this should be enough!
+
{{EbuildFooter}}
If you experience booting problems like missing modules / drivers then just boot from the genkernel section and fix the initrd building. You can look into the man page to tweak the command a bit (e.g. --add-drivers "xz dm_crypt" etc...).
+
 
+
Ok let's go on and finish the taks, we are now going to tell grub how to boot off correctly! Edit <tt>/etc/boot.conf</tt>:
+
 
+
<pre>
+
 
+
boot {
+
        generate grub
+
        default "Funtoo Linux dracut"
+
        timeout 3
+
}
+
 
+
"Funtoo Linux genkernel" {
+
        kernel kernel-genkernel[-v]
+
        initrd initramfs-genkernel[-v]
+
        params = quiet rootfstype=ext4
+
        params += luks enc_root=/dev/sda3
+
        params += lvm root=/dev/mapper/vg-root
+
}
+
 
+
"Funtoo Linux dracut" {
+
        kernel vmlinuz[-v]
+
## this is the better-initramfs generated initrd
+
        initrd initramfs[-v].img
+
        params  = quiet rootfstype=ext4
+
        params += luks enc_root=/dev/sda3
+
        params += lvm root=/dev/mapper/vg-root
+
}
+
</pre>
+
 
+
That's it -- almost!
+
 
+
Now write to the <code>grub.cfg</code> with the handy [[Boot-Update]] script:
+
<console>
+
###i## boot-update -v
+
 
+
boot-update 1.5.2 / Copyright 2009-2011 Funtoo Technologies
+
 
+
[use option "-l" for license info, "-h" for help]
+
 
+
* Generating config for grub...
+
 
+
DEFAULT > Funtoo Linux - vmlinuz-3.2.6-pf
+
          Funtoo Linux genkernel - kernel-genkernel-x86_64-3.2.6-pf
+
 
+
* Completed successfully.
+
</console>
+
 
+
Okay,... here you go..! :)
+
 
+
Reboot and see how it works!
+
 
+
 
+
[[Category:HOWTO]]
+
[[Category:Featured]]
+
[[Category:Kernel]]
+

Revision as of 16:00, 5 August 2014

media-sound/pianobar


Source Repository:Gentoo Portage Tree
Homepage

Summary: Pianobar is a console client for the personalized web radio Pandora.


Pianobar

To install Pianobar, emerge it:

# emerge pianobar

Pianobar configuration

Easy login

After you have emerged Pianobar, you can run it with pianobar. If you dislike typing your username and password every time that you run pianobar, create the file ~/.config/pianobar/config and add the following lines to it:

~/.config/pianobar/config
password = YOURPASSWORD
user = user@email.com

Easy login (with encryption)

If leaving a plaintext password for your Pandora account somewhere on your filesystem makes you nervous, you can use gpg to decrypt a file that contains your password. Change your configuration to reflect the one below if you would like to encrypt your password:

~/.config/pianobar/config
password_command = gpg --decrypt ~/.passwords/pianobar
user = user@email.com

Keybindings

To configure keybindings, check out man pianobar. All keybindings can be added to ~/.config/pianobar/config. All the keybindings in the man page will begin with the line act_.

Other configuration options

Option Description
audio_quality The quality of the audio. Can be set to: high, medium, or low.
autostart_station Select a station ID that you would like to play when Pianobar starts.
proxy Use a http proxy.

Troubleshooting

Not compiled with threads support

If you recieve the following warning message ([aac @ 0x7faccc003cd0] Warning: not compiled with thread support, using thread emulation) while running Pianobar, add threads support to ffmpeg, then rebuild it:

# echo "media-video/ffmpeg threads" > /etc/portage/package.use/ffmpeg
# emerge ffmpeg
Note: As of FL-1437, threads support should be enabled on ffmpeg by default.