Okay, here's the deal. I'm trying to get kernel 3.0 installed from source. I can get the kernel built without any issues and can install and boot from it. However, I can't seem to get the modules set up correctly as they are in the stock kernel. The .config files are different between the 2.6 series and 3.0 so it's apparent that I can't just share the configuration file to solve my problems. I can't get it to run the same high resolutions as well as the networking modules. Is there an easy method to get pretty much the same module setup and configuration from the old kernel to the new? I've never had this much issue with a kernel compile before. I'm starting to think it's the 3.0 series being a pain in my butt.

Do modules compile? Do they instal when you say make modules_install? And if yes, where exactly in /lib/modules do they go?

Some of the modules install, and those do load up on the new kernel. The problem is that when it comes time to install modules for 3.0, most of the modules I currently use do not make it for the new kernel. It's quite frustrating. I have tried a go with make oldconfig, and it did a little more of the modules than before, but it still lacked a tremendous amount of what I did have. I'm currently on my 6th attempt to get the kernel to build with all the modules.

A friend sent me a copy of his .config file from a fully successful 3.0 build on slack 13.37, so I am hoping maybe this will show me what I am doing wrong. I'll let you know shortly.

Sounds like you initially tried to build without making oldconfig first. I did that one time, and I had a nasty problem with modules glitching. I also found that the source tree got garbled and making oldconfig later did not fix it at all, and may have made it worse. If you indeed made the 3.0.0 kernel without making oldconfig FIRST, I recommend trashing this source tree and starting over with either one of Pat's or your friend's .configs. In particular, do not use your current .config: it may be garbled as well.

1 members found this post helpful.

Looking at his file, I think you're right. I did made oldconfig after I had already compiled the kernel once without doing so. I wiped it and started clean, compiling now. We will see how this bad boy runs this time. Thanks for the tip. I will report shortly.

Well, half the problem is fixed. I started with a fresh source tree, made oldconfig, now all the display modules and everything installed and worked. So now I have a 3.0 kernel with great looking resolution and great everything else... and NO networking modules installed into /lib/modules/3.0.0..... I specifically setup the .config to have all the required networking modules built.. I have never had this kinda trouble from a kernel and it's irritating the piss outta me.

Without knowing more, it is hard to say what went wrong. Kernel configuration is a black art, and it is possible that you simply cut too much. I am probably a wrong person to ask, as my attempts at kernel config resemble stabbing a ghost in a dark room with a blindfold on. When I experimented with the kernel config, I started with Pat's generic, which pretty much builds everything under the Sun, and then slowly cut away parts I didn't think I need. Whenever I tried to make huge across-the-board cuts I would always end up with a non-working kernel, and I could never tell what exactly made it so. One of my personal mysteries is SCSI: I don't think I have any SCSI, but cutting it made my kernel a non-starter, so I learned to leave it alone.

Perhaps I'll just have the kernel compile EVERYTHING lol.

That's pretty much what I do, perhaps I'm lazy . But hey, it always works!

1 members found this post helpful.

Indeed it is hard to tell whether trimming down the kernel helps a lot or at all. It doesn't appear to be significantly leaner or noticeably faster. And does it really matter to you if it compiles in 100 or 60 or 40 minutes? Either way, it's a background, may be even an overnight task. Pat's generic is the highly modularized version, so it's actually quite lean, though builds for a while. I would start by setting things like PREEMPT and LOCAL_VERSION, you know, things that produce immediate visible results, and going from there in small steps.

3.0 isn't a radical change from 2.6.39, so I just started with the 2.6.39 generic config in 13.37 testing, ran make oldconfig, checked the config with make menuconfig then built it and installed the modules. It works really well.

That said, I missed rtc, so had to rebuild, but hey ho.

I figured I'd update everyone. Yep, I got 3.0 working. I did what you said and did a oldconfig on the generic 2.6.39 and when I ran the config afterwards, I pretty much said yes to all lol. Even with everything compiled into the kernel, this computer has no performance difference at all.