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.
I'm trying to recompile my kernel. How can I get the source code for the kernel?. Can I just download it from www.kernel.org or do I need a special source package for debian?
Not quite. Debian has special patches applied to the kernel, not exactly sure whatfor. So using a vanilla kernel from the kernel.org guys might not work on your system. So, use the Debian kernel sources if you want to re-compile against your Debian kernel.
I've used a number of vanilla kernel sources from kernel.org on my Debian machine without a problem. It may help that I'm using this page as my guide to recompilation; I couldn't say. See section 7.1.1 for "the Debian Way".
just copy the .config from your /boot and then do makemenuconfig .config you and you'll be fine
Hold your horses! If you use .config from an older version you must run make oldconfig. And even this is does not guarantee anything. Best way to do it is to configure your kernel from scratch. Yes, it will take long. Yes, it involves lots of reading. But in the end you will be awarded with stable and fast OS.
Does this look familiar? Either use "touch" to create the file in your kernel source include/linux directory, or just delete the line from ah_osdep.c. You could also switch to madwifi-ng. I don't think that version has the dependency.
Code:
/data/madwifi/madwifi-0.9.2/ath/../hal/linux/ah_osdep.c:44:26: error: linux/config.h: No such file or directory
"Hold your horses! If you use .config from an older version you must run make oldconfig."
"MUST"? I think not. I've switched from 2.4 through several versions of 2.6 up to, now, 2.6.19.1. I've tried running make oldconfig a few times, but there's always so much noise to deal with that I just stop it and run make menuconfig to deal with it. That's not to say that make oldconfig isn't a good idea though, as you will be presented with all the new options and can delete them on the fly. I just found it overwhelming at first, as I was being asked a bunch of questions and didn't have a clue whether I wanted the new stuff or not.
"Hold your horses! If you use .config from an older version you must run make oldconfig."
"MUST"? I think not. I've switched from 2.4 through several versions of 2.6 up to, now, 2.6.19.1. I've tried running make oldconfig a few times, but there's always so much noise to deal with that I just stop it and run make menuconfig to deal with it. That's not to say that make oldconfig isn't a good idea though, as you will be presented with all the new options and can delete them on the fly. I just found it overwhelming at first, as I was being asked a bunch of questions and didn't have a clue whether I wanted the new stuff or not.
What a childish approach. Here you described how not to build a kernel. You do not know what you built in and what not. You get a bloated kernel. Your kernel will contain lots of unnecessary drivers which possibly conflict with each other. Something you actually may want is not compiled in because you even do not know it exists.
What i wrote in my previous post comes from kernel developers. Now you probably say developers don't know a thing about it?
"What i wrote in my previous post comes from kernel developers. Now you probably say developers don't know a thing about it?"
I'm sure they know a lot about it. But, name-dropping doesn't infer any god-like abilities on yourself. There is a lot to say about JUST DOING things in this world. Yes, it may be childish, as compared to taking a university course first. But, you know what: you do actually manage to get things done, and you learn the consequences of doing it the wrong way in the process. At this point, I don't think there's much left I could get rid of in my kernel. Perhaps, but it's not due to lack of trying - or from not running "make oldconfig" and getting an output that I simply wasn't prepared to deal with because I was in the early learning stage.
I love elitists of all stripes. But, they do usually need a bit of ketchup to go down smoothly.
Yes, you can drive around a blind corner 60 mph every day and say: dude, you are stupid if you slow down here, see, nothing has happened to me. You can compile your kernels how you want, sure. OP here may be not that scruffy though.
Running "make oldconfig" will pickup any changed features in the new kernel. You can go back and make further changes if you want, but normally you already did that configuring your last kernel version.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.