how to clean kernel & rest in order to use the config for a custom kernel
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
how to clean kernel & rest in order to use the config for a custom kernel
Hi,
I will try to be clear ... but even for me is not so clear ...
I want to "clean" & "set" all the options (module & so) for the actual kernel (3.2.0.3) in order to use the .config for a custom kernel (3.6.3) which is appropriate for Ivy Bridge hardware.
E.g.
The wlan card is recognized grace of a microcode loaded on install and a strange cascade loading
lsmod
iwlwifi 170823 0
mac80211 192768 1 iwlwifi
cfg80211 137140 2 mac80211,iwlwifi
Find and copy the .config file from the old kernel into the directory of the new kernel. Issue the following command (copy/paste!):
Code:
make rmproper && make oldconfig && make clean && make && make install && make modules && make modules_install && mkinitramfs -o /boot/initrd.img-3.6.3 3.6.3 && update-grub
The long line of code does everything you need, including compiling the kernel, making an initrd image to boot from and updating your Grub2 config. Mind that at one point, it'll ask you to choose for new(-ish) configuration-options that aren't in the old .config file. Just press enter until done, it'll automagically accept the (sensible) default values.
the (this) code perhaps I will be able to find it ... BUT
I don't know how to load the useful modules
and
to blacklist the wrong (not only this in fact)
AND
TO PUT ALL OF THIS IN "CURRENT CONFIG" IN ORDER TO BE REUSED BY THE NEW COMPILE
my modules & modules.conf are empty.
I gives one example
=> iwlagn load iwlwifi in order to load microcode firmware: iwlwifi-2030-6.ucode
how freeze this in config? eventually how put directly - iwlagn load microcode - in modules, in modules.conf in initrd and initramfs
AND THIS FOR ALL THE CURRENT SETTINGS IN ORDER TO NO MORE SEARCH AFTER NOUVEAU, ATI and s.o.
HOW? ONLY FOR THE MODULES you have something like (from google arch, wiki.debian, ubuntu ...)
------------
to update modules.conf must use update-modules
=> NO IS Obsolete, must use module-init-tools, module-init-tools-udeb
=> No IS Obsolete, will be / have kmod
apt-get install kmod
Reading package lists... Done
Building dependency tree
Reading state information... Done
kmod is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
man kmod
No manual entry for kmod
See 'man 7 undocumented' for help when manual pages are not available.
I don't understand HOW.
Normally, I must to load ONLY the useful modules and to blacklist the rest (HOW?).
After, to appropriate use the udev, udeb and s.o. (HOW?)
Thanks for the last code (I have used somehting close)
But could you PLEASE help me in this mess?
No need to shout (using capital letters is considered shouting!)...
You're making things way too difficult for your knowledge level. First, tell us why you want what you (appear) to request, because the stuff you mention is really sophisticated stuff aimed for the kernel dev's rather then regular users. Point is, the kernel is smart, very smart: it won't load modules it wouldn't need. But when you change hardware (it's not a matter of if but when!) you wouldn't want to compile the entire kernel again, with the risk you can't because you're missing essential drivers, so it's wise to have a fair number of modules ready and waiting, in case you need them. If you're after firmware drivers et all, install the appropriate package(s) from the non-free repository.
Compile a basic, stock kernel first and learn from it. Then repeat, to learn more. Then tweak the config file via the available GUI's (make menuconfig, make xconfig, assuming you have the required dependencies installed). Just copy/paste the commandline I gave you before, it does the job for you.
my new laptop is an Ivy Bridge (MSI Clone)
with difficulties I forced on testing install to recognize the wifi
the wlan (Atheros E2200) are not, they are many problems (freeze ...) and I understood from the bugs report - some of them are solved in the new 3.6 kernel
I have done a custom kernel 3.6.0-rc1 and is more stable but other pb still remains
What I want to know from the experts:
- I must to configure the current install for the current debian supported kernel (3.2.0-3) and that means ... modules ... init ...
after / or
- I try the new released kernel and I compile until I obtain something good ...
for myself the actual doc is a mess because I can't understood ...
e.g.
the explanation for the intel microcode was:
- is loaded by kernel - module iwlagn => after iwlwifi ... and it must to be like that (conf. intel doc's)
in 3.2 kernel iwlagn are loaded and modinfo iwlagn | grep firmware return firmware
but in 3.6 iwlagn are no more loaded and iwlwifi return firmware
they are also the stuff for usb 3.0 and so
how can clean the 3.2 kernel, config & install?
how can re-use the config for the new one?
thanks at for your amiability
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.