You are not logged in.
Hello,
I have a kernel config file seved to ~/config which only has 19 modules (and could be further optimized), but I'm having trouble using it.
What I have done:
Used ABS to get the latest linux sources from testing
Copied /var/abs/testing/linux to ~/Install/linux
cd ~/Install/linux
makepkg -o
cp ~/config ./.config
cp .config config
cp .config config.x86_64
makepkg -ei --pkg linux
The weird part, at least to me, is that I saw a lot more then 19 modules during compilation. Is this expected for some reason or have I messed something up?
Last edited by bstaletic (2015-02-16 13:19:59)
Offline
The weird part, at least to me, is that I saw a lot more then 19 modules during compilation. Is this expected for some reason or have I messed something up?
Your build method seems ok to me. Can't really say anything about the .config, but kernel modules can have dependencies too. For example, if you choose to build ext4 as a module, it selects at least jdb2 and crc16 modules to be built as well.
Offline
I now about the dependancies, but it shouldn't matter if I'm counting modules in config file using grep and wc.
Offline
true..
did you just 'see' too many modules during compilation, or is there actually more than 19 modules built/installed?
if you mean the lines that look like this:
CC [M] fs/jbd2/transaction.o
CC [M] fs/jbd2/commit.o
CC [M] fs/jbd2/recovery.othen that's just a compiler output, not a list of individual modules.
Offline
Recommend you try modprobed-db
AUR: https://aur.archlinux.org/packages/modprobed-db
wiki: https://wiki.archlinux.org/index.php/Modprobed-db
Offline
ooo,
I saw lines similar to those in your post, so I should relax, thank you for the info.
grasky,
The tool is great, and I used it to gather the data, but later wanted to minimize the kernel further.
EDIT: There's also the fact I was somewhat tired while play with the kernel, and my brain started playing tricks on me (i.e. I started making dumb mistakes).
Last edited by bstaletic (2015-02-15 19:08:23)
Offline
The tool is great, and I used it to gather the data, but later wanted to minimize the kernel further.
The real magic is `make localmodconfig` but I don't think you can or should strip it back beyond what it does...
Offline
I'm currently running arch on a kernel generated with localmodconfig and modprobed-db. A close inspection of kernel config reveals some wifi, touchpad, joystick etc drivers which I never used. It should totally be possible to get rid of those. Also adding support for some things I initially removed.
If I s/=m/=y/g the config and compile it that way, kernel is not bootable, why is that?
Offline