SOLVED: Building a streamlined kernel via modprobed-db

Question

Hi
I was trying to use the modprobed_db daemon (activated by systemd) to collect all used modules on my hardware in order to build a more streamlined kernel.
Here is the wiki:
https://wiki.archlinux.org/index.php/Modprobed-db
I modified the arch linux PKGBUILD of the kernel by adding these two lines:
sudo /usr/bin/modprobed-db recall
make localmodconfig
Unfortunately the modprobed service doesn't catch the loop module, although I'm using it.
I then tried to simply add some modules in ~/.config/modprobed.db, but this resulted in the error "loop: module not found", when I tried to build the kernel via makepkg.
What is the right way to manually add modules to the modprobed database?
thanks
gen2arch
Last edited by gen2arch (2015-05-02 08:50:17)

Answer 1

I made a huge mistake that was the reason for the abovementioned error:
I tried to manually add modules into the modeprobed.db and then do a "recall"  during makepkg while being already in a module-wise restricted environment of a previous custom kernel build!
It is clear that the "recall" mechanism during the build cannot work, when the booted kernel/the running system doesn't contain the searched for modules. One has to manually add and recall modules for a custom build from within a fully fledged arch linux generic kernel where everything is at disposition and can in fact be modprobed!
sorry for the inconvenience.
gen2arch