You are not logged in.

#1 2011-01-02 03:27:13

Telkkar
Member
From: United States
Registered: 2010-12-26
Posts: 38

[SOLVED] Testing kernel compile

Hey all,

I compiled kernel26-git from the AUR today. I spent three or so hours reading through the config to handpick options, etc. I compiled, everything went fine. I booted, and bam -- works perfectly!

... too perfectly. Everything works as it should, or rather, works as it did under kernel26 in core. uname -r gives me what I would expect -- 2.6.37-rc8-<continued>. I unchecked enough options to make Linus smite me with a banhammer the size of Finland and say "Leaveth mine kernel alone! Begone!"

So my question is -- how can I test that my config was actually followed instead of the config for the kernel in core? I'm trying to make a lean kernel for my MPB -- just for fun. smile (there's also an issue with kworker that is eating my battery alive, but I've looked all over the place and no one else has it, or hasn't said so)

Last edited by Telkkar (2011-01-02 04:17:04)

Offline

#2 2011-01-02 03:43:46

bangkok_manouel
Member
From: indicates a starting point
Registered: 2005-02-07
Posts: 1,556

Re: [SOLVED] Testing kernel compile

zcat /proc/config.gz > running_kernel_config
then diff this config with arch's one.

/edit: support for /proc/config.gz has to be built in kernel, hope you did that tongue
otherwise, your config is still in your build dir if you didnt clean it, it's the .config file

Last edited by bangkok_manouel (2011-01-02 03:45:27)

Offline

#3 2011-01-02 03:53:45

Telkkar
Member
From: United States
Registered: 2010-12-26
Posts: 38

Re: [SOLVED] Testing kernel compile

Thanks for the quick reply!

The two config files are very different. For my -git kernel, I have a TON of options that are "not set." Something makes me think that when the options are "not set," the kernel is compiled with those options as modules if possible -- I saw a LOT of [M] on options that I know I disabled when I compiled.

Haha, yeah, I made sure to build in support for config.gz. Thats one thing I DID make sure to do.

Offline

#4 2011-01-02 04:07:21

bangkok_manouel
Member
From: indicates a starting point
Registered: 2005-02-07
Posts: 1,556

Re: [SOLVED] Testing kernel compile

not set means it's not built at all.
m means built as module.
y means built in kernel

Offline

#5 2011-01-02 04:16:50

Telkkar
Member
From: United States
Registered: 2010-12-26
Posts: 38

Re: [SOLVED] Testing kernel compile

Hmm... wonder why I saw so many [M]'s when I was compiling. Interesting...

Thanks for your help! Glad to know that everything's working as it should.

Offline

#6 2011-01-02 04:21:10

bangkok_manouel
Member
From: indicates a starting point
Registered: 2005-02-07
Posts: 1,556

Re: [SOLVED] Testing kernel compile

use the zcat solution i first posted then you'll know for sure if everything is right.

Offline

#7 2011-01-02 05:27:19

Telkkar
Member
From: United States
Registered: 2010-12-26
Posts: 38

Re: [SOLVED] Testing kernel compile

I'll recheck to make sure what I labeled not to build -- did not build. Thank you again.

Offline

Board footer

Powered by FluxBB