Kernel Deblobing

From Wikipedia: A binary blob is a closed-source binary-only piece of software without publicly available source code. Since 1996, Linux kernel includes more and more binary blobs, to handle closed-sources devices (without technical documentation which would authorize free firmware development for them). Proprietary software always introduces freedom, security or privacy concerns.

Linux kernel deblobing is the operation which removes binary blobs, to get a completely free kernel. This is done with shell scripts named,   and  , where   represents the kernel revision. Thoses scripts are provided by the Free Software Foundation Latin America, for each kernel revision since 2.6.27. FSFLA provides Linux-libre distribution.

Deblobing kernel obviously means that devices with proprietary firmware only can't be used, like closed-sources Intel Wifi or Nvidia graphics cards. See below how to get a list or removed blob without kernel compilation.

Once deblobed the kernel is compiled as usual.

Deblobing hardened, aufs, ck and rc sources
For:

set the USE flag  in, sources will be automatically deblobed after being emerged.

Deblobing gentoo-sources (or any other sources)
USE flag no more deblobs, this must be manually done.

Emerging Sources
If not done, first accept  licence, needed for gentoo-sources.


 * If the file exists:


 * If the file doesn't exist:

Then emerge gentoo-sources:

… and set symlink to the emerged sources. First get the list of available sources:

… then choose the right ones:

Then change directory to :

Downloading Deblob Scripts
Explore Linux-libre releases and download the emerged kernel revision scripts and signatures. directory is chosen for  sources:

Make the scripts executable by root only:

Verifying Downloaded Scripts
First import the Linux-libre server key:

Then verify the signatures:

Python Version
Deblob scripts use Python 2.7 interpreter, set it at the beginning of the interpreters list. Get the list with:

… then:

Deblob Command
Deblobing can now be started:

During the operation, which may be long, all deblobing information is displayed. After kernel compilation -gnu suffix will be appended to it's name,  in this example.

List of Removed Blobs
To get the list of removed blobs with their kernel symbol names, redirect the deblob command output to a file:

As kernel sources can be re-emerged after being deblobed, this is a convenient way, without kernel compilation, to investigate if targeted hardware should work without binary blobs.

External resources

 * The Binary blob Wikipedia article