2.6.4 kernel
im running suse 9.0, after compileing the 2.6.4 kernel, sound stops working and cannot connect to the internet, can someone walk me threw this process ?
|
You have maybe miss your kernel configuration w/modules :)
Try to recompile your kernel .. |
what the exact steps to compile ,and or build cause i tried to recompile .
|
Try:
make make modules make modules_install |
yes i did that but when i reboot sound stops and internet connection stops working
|
compiling a kernel is not a simple thing. all that we can say is that you didn't do it correctly. go over your options and ensure you have chosen the best options to suit your system. From the way you are asking questions without providing any form of technical background (your sound.... what sound card??) i'd possibly suggest sticking with your current working kernel until you are more expereinced.
|
didnt do what right ?
|
To get your sound card and internet working, you have to make sure you have compile modules required by your sound card and your ethernet card (or modem) into the kernel. It is also possible that you have not configured your system to load the new modules. Type lsmod and see if the modules are loading. What are your hardware specs?
|
Just do make oldconfig in the new kernel directory. It should copy your old kernel config options. For your sound card, video card, etc you may have to recompile them to handle the new kernel requests.
Go to http://www.justlinux.com/nhf/Compili...mpilation.html It will guide you through. |
maybe this is my problem, i do make make modules install make install then when i reboot i loose sound and internet connection
|
sound is usually driven by a module or driver, seen when typing lsmod.
Network is usually also driven by a module, seen by typing lsmod. |
Did you actually configure the kernel before you compiled it? Try "make menu_config" before the "make" step.
|
Quote:
|
Where's the fun in that? ;)
Honestly, stock kernels are fine unless you need to add some obscure hardware support, or you really need a small footprint kernel for some reason. The whole big win of loadable kernel modules is that the kernel no longer has code for hardware and features you don't need. This code stays in modules, and the modules you _do_ need are loaded as needed. This means there is no real big benefit to compiling a custom kernel. I, however, am a masochist, and have compiled 10 custom kernels in the past week, just to learn, and for fun! I remember having to compile custom kernels so my cd-rom that hung off of my soundblaster card would work. Then it took >8 hours on my 486 to compile. Today I'm on my 3rd custom kernel! I'm a kernel compiling FREAK! |
airmikeyy, you need to gives a lot more information such as the steps that you take, what commands did you type, did the commands gave you an error, etc.
hooya27, the problem with a modulize kernel is it creates a security risk. Anybody can compile a module and install it. If they crack your root password, he or she can load the module. The module can be anything for an example a torjan. The reason why a lot admins compile their kernel is it minimize this security risk. |
All times are GMT -5. The time now is 07:28 AM. |