Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. |
| 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
10-03-2006, 04:29 PM
|
#1
|
|
Member
Registered: Dec 2003
Location: Russia/Iceland
Distribution: Ubuntu 6, NetBSD 3.1, Cygwin
Posts: 39
Rep:
|
Probing hardware tool for kernel config
Is there a universal tool for probing hardware and determing which features can be safely removed from the .config file used in kernel building? Today I removed a lot of features that seemed to me unused using the menu xconfig command, but the new kernel didn't boot. So I've found myself choosing between 2 evils - there's dozens and hundreds drivers I wouldn't need (telephony, amateur radio, video cards I don't have etc etc etc) but I don't know exactly about many of these features whether they're relevant for my hardware or not, whether I should them remove. The standard device probing program on my Ubuntu 6 doesn't help much. So at the moment I'm compiling a new kernel with all this load of stuff set by default, but it sucks a bit that I'm forced to using drivers I might not need at all. Doesn't anyone know any kind of a tool that could resolve this problem?
|
|
|
|
10-03-2006, 04:48 PM
|
#2
|
|
Senior Member
Registered: Nov 2004
Distribution: Debian, Ubuntu, LinuxMint, Slackware, SysrescueCD
Posts: 1,566
Rep: 
|
If these extra drivers are compiled as kernel modules, as most (just about all) of them are usually by default, then there's really no problem. The only downside is a little extra disk space storing them and a little longer compile time when you redo your kernel. Your system will not run slower, or use more memory, because of a few unused modules laying around. You will use a bit more disk space to store them, but it's usually insignificant in the grand scheme of things. You can get rid of the things you OBVIOUSLY won't be needing when you compile the kernel, but if it's not 100% obvious then I'd say just let it compile (as a module). Your CPU needs to work up a good sweat every now and then anyway! (To keep the thermal paste conducting well  )
|
|
|
|
10-03-2006, 04:57 PM
|
#3
|
|
Guru
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,697
Rep:
|
No tool I know of. The Docs within the kernel source explain what many of the modules that can be built will work with. Easiest way if unsure then make as module. Like haertig says it will take up more space but will not impact on performance because if not needed then it is not loaded.
Brian1
|
|
|
|
10-03-2006, 05:12 PM
|
#4
|
|
LQ Veteran
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,756
|
It won't configure your kernel for you, but lshw is a good tool for finding out what you've got lurking under the hood. The GUI version (gtk-lshw) organizes things nicely.
|
|
|
|
10-04-2006, 05:12 AM
|
#5
|
|
Member
Registered: Dec 2003
Location: Russia/Iceland
Distribution: Ubuntu 6, NetBSD 3.1, Cygwin
Posts: 39
Original Poster
Rep:
|
Thank you Hangdog42!!! This is tool is practically what I needed!!!
Yes, you are right, guys, about compiling things as modules, but you always want your system to be perfect and kernel being compiled some ten minutes shorter...
|
|
|
|
02-13-2007, 11:01 PM
|
#6
|
|
LQ Newbie
Registered: Feb 2007
Posts: 8
Rep:
|
Stick with your drivers like the amateur radio, you don't know when you'll be needing them.
______________________
Amateur Radio Catalogs - Download Radio Catalogs and Radio Brochures for Free
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 09:53 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|