You are not logged in.
If I use Arch ABS system with localmodconfig to compile my own kernel, I find that the following modules, which are seen by lsmod using stock kernel, are not there with custom one
snd_compress
snd_pcm_dmaengine
ac97_bus
acpi_callprobably the only relevant one is the last one, but still I would like to understand what the correct procedure is for including such module, as I cannot find it in menuconfig, and moreover pacman gives a couple of errors when I install the custom kernel, although everything seems to work fine when I boot it, except for missing modules.
edit: more precisely, pacman is complaining that sd_mod and usbhid modules are missing, but those are not even there in the standard case.
Should I just ignore pacman error and reinstall acpi_call via pacman after compiling the kernel? as this sounds a bit clumsy, I'd like to know whether there's a better way to handle this.
My main reason for asking this question is that I'm making some tests editing config and applying patches, so localmodconfig is a simple way to cut by 1/5 the compile time.
Last edited by nicolo (2017-10-11 03:44:00)
Offline
Using LMC only works if the needed modules are loaded before you start compiling. Use https://aur.archlinux.org/packages/modprobed-db/ for that. If you have an out-of-tree module like community/acpi_call, you have to edit it to work with your custom kernel and compile it each time you build a kernel (not every time but it's not possible to know if a new kernel will break a module without testing it).
Offline
I see, thanks. Could you please link to some instructions for doing that? Do you know why this does not happen with stock Arch kernel?
Offline
If your kernel does not have a different name and its package name stays as "linux", then you just have to recompile and reinstall that "acpi_call" after you've installed your new kernel.
About changing "acpi_call" to "acpi_call-custom" for a kernel with a new package name like "linux-custom", use the PKGBUILD of "acpi_call-lts" as an example to see what's getting changed to switch from "linux" to "linux-lts". To get something for your "linux-custom" package, it should be basically choosing the "acpi_call-lts" PKGBUILD as a base and then search-and-replace "-lts" to "-custom".
Another thing would be dkms. You could choose the "acpi_call-dkms" package and dkms would manage the recompiling of stuff for you. This "acpi_call-dkms" package is in the AUR.
Last edited by Ropid (2017-04-27 19:48:29)
Offline
Thank you, I will check that out.
Offline