You are not logged in.
Pages: 1
For learning purposes, I would like to build and install a custom kernel WITHOUT using pacman. I want to make + make modules_install and copy the kernel manually in /boot. However, make modules_install would install files in /usr/lib/firmware which already exist on a normal Arch installation and are owned by the linux-firmware package (required by the linux package).
I found this old thread (2009) related to this, but there does not seem to be a clean solution.
There is also no mention of this in the wiki page Kernels/Compilation/Traditional
For those who prefer manually installing their custom kernels, how do you handle firmware files. Do you simply overwrite the files in /usr/lib/firmware? (At first sight, it seems like the firmware files installed by a custom kernel are a subset of those provided by the linux-firmware package, so this might not be a problem.)
Last edited by jpgg (2014-08-20 18:50:33)
Offline
Just remove the linux-firmware package. If it turns out that you need some of the extra files that it provides, just install those manually too.
Offline
Just remove the linux-firmware package.
The linux package depends on linux-firmware and I want to keep the default arch kernel installed. Is it somehow possible to uninstall a package that is required by another?
Last edited by jpgg (2014-08-20 20:12:54)
Offline
It is, but IMO it would be better to create a custom linux-firmware package that no longer conflicts with the files that you want to install manually.
Offline
At first sight, it seems like the firmware files installed by a custom kernel are a subset of those provided by the linux-firmware package, so this might not be a problem.
It isn't.
Offline
Pages: 1