From c2e8da3b4520332db00b29014a60223960f2766a Mon Sep 17 00:00:00 2001 From: Cesnia Ramirez Date: Fri, 21 Oct 2016 21:27:02 -0600 Subject: docs/distros: add information about kernel deblobbing in Gentoo. --- docs/distros/index.html | 63 ++++++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 60 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/distros/index.html b/docs/distros/index.html index a0b68374..5967b902 100644 --- a/docs/distros/index.html +++ b/docs/distros/index.html @@ -102,9 +102,66 @@ - configure the ACCEPT_LICENSE string accordingly.

- You also need to deblob your kernel. See: - https://wiki.gentoo.org/wiki/Installation_on_libreboot#Use_a_Kernel_without_blobs -

+ You also need to deblob your kernel: For that you need to add the +deblob useflag in the USE variable at /etc/portage/make.conf see +https://wiki.gentoo.org/wiki/Installation_on_libreboot#Let_portage_remove_the_blobs +, so that when you install the source code of the kernel it is +emerged without the blobs, however this will only work if your +objective is to install the hardened-sources, ck-sources, or the +rt-sources kernel, so if you plan to install any other kernel such as +gentoo-sources (the recommended kernel by the Gentoo Project) or any +other kernel listed at https://wiki.gentoo.org/wiki/Kernel/Overview +you have two options:

+
    +
  1. +

    Creating a local overlay (repository) with a modified copy + of your desired kernel’s ebuild so that the deblob useflag does + work in it (This may not work if you use the kernel git-sources, as + of git-sources unstable, inconsistent, bleeding-edge nature it may + work at some point and in other not, also pf-sources won’t work + with this method as its versioning classification does conflict with + Gentoo’s internal script for controlling the deblobbing proccess, + however if you want to mess with the script it is located inside the + file at /usr/portage/eclass/kernel-2.eclass). For this first create + a local overlay following the steps defined at + https://wiki.gentoo.org/wiki/Overlay/Local_overlay + , next create the directory of your kernel at + /usr/local/portage/sys-kernel/your-kernel-dir, after that copy the + ebuild of your desired kernel from + /usr/portage/sys-kernel/your-kernel-dir/your-kernel.ebuild to + usr/local/portage/sys-kernel/your-kernel-dir/your-kernel.ebuild, + then open it in an editor and add a line with K_DEBLOB_AVAILABLE=”1” + between the variable EAPI and the line inherit kernel-2, and finally + run with root permissions the command ebuild + /usr/local/portage/sys-kernel/your-kernel-dir/your-kernel.ebuild + manifest ; after that if you + had already added deblob to + your useflags you can continue with the kernel installation as you + normally would.

    +
  2. +

    Adding an exception to the licences that are accepted for + your desired kernel so that portage allows installing the source + code of your desired kernel even if it has blobs, and after that + applying the linux-libre deblob scripts by yourself and by doing so + removing the blobs. For this first create a file in + /etc/portage/package.license with the following content + sys-kernel/your-kernel-sources freedist , + next emerge (install) the source code of your kernel with portage, + after that go to /usr/src/linux and download the proper deblob-check + and deblob-version scripts for your kernel version from + http://www.fsfla.org/svn/fsfla/software/linux-libre/releases/tags/, + then make them executable, and finally set the EPYTHON + variable to python2.7 and execute + with root permissions the script deblob-version ; after that continue + with the kernel installation as you normally would. +

    +
+

It is also possible to install +the linux-libre sources following the instructions +at +https://wiki.gentoo.org/wiki/Installation_on_libreboot#Use_linux-libre_sources +however this is not recommended as portage would not be able to +manage it.

Visit the Gentoo website

-- cgit v1.2.3-70-g09d2