Hello Everyone,

I am still using 12.1 and don't really see a need to upgrade at this point. But, back in November last year I downloaded and installed the 2.6.27.rc9 kernel because it had native support for my wireless and I could stop using ndiswrapper. So, I compiled this kernel from source (got it straight from kernel.org). Somehow, during the compile, I must have included the modules from 2.6.24 because I get some errors about modules from the boot messages. I have always just ignored them because they had no effect on the running of the OS. In fact, everything seems to run just fine from this older kernel (which isn't even a final release kernel), that I have just continued to use it right along.

However, now I am noticing just a little higher temperatures with this laptop, so I checked to make sure I had CPU freq running and I didn't. So, in trying to start it I find that I do not have any of the necessary modules (powernow-k8, cpu-freq-ondemand, etc.) as modprobing them delivers an error that they don't exist.

Everything is running so well, I would really rather not recompile if I don't have to, so I was wondering if it is possible to get these modules installed into this kernel without recompiling.

Thanks for any replies.

Bob

OK, this one obviously can't be answered. So, I would like to ask if anyone knows or has tried the 12.2 kernel (2.6.27.7) with 12.1. What I am trying to do is repair my install without reinstalling.

Thanks
Bob

Well, I installed the 2.6.27.7 kernel and it boots fine, but the /lib/modules directory for this kernel is non-existent. I always follow Alen Bob's directions for building a kernel, and according to the instructions, make install copies all the modules for this kernel that directory. I did it twice and they still never showed up in /lib/modules. The mouse freezes immediately when reaching the desktop, I am assuming becuase of this.

dmesg shows the error: FAILED TO OPEN /lib/modules/2.6.27.7-smp: no such directory

Anyone have any ideas where I have erred?

Thanks

Bob

Did you try "make modules_install" ?

Thanks....you made me go back and study what I was entering and I was omitting the "_" between modules and install. That cured it. But it is strange, I am still getting the boot message that says using modules from 2.6.24, when I waded througth the swamp of choices in the configuration steps. But it really doesn't matter because I now have cpufreq working.

Whew!! what a trip just to get this working again. This kernel boots a little faster that the .27-rc9 I was using, but only minimal. Everything else seems about the same. But I have answered my own question: the 12.2 kernel works just fine with 12.1. I guess it is just the packages which are slightly newer that is the only difference between the two versions (at least on my install.)

Thanks for your help.



Bob

EDIT: How is that fglrx (the ATI driver) still works with this new kernel without running the setup again? I just booted into it and it is working. I thought I would have to build it again to get it to work with a new kernel. Never seen this before.

You're welcome
Normally you can compile newer kernels in Slackware compiling them from source, but always keep the original version as well so that you can fall back and test things if something stops working later on.

I was wondering... You said that during boot it still tells you it is using modules from 2.6.24 ...
Isn't it telling about /etc/rc.d/rc.modules-2.6.xxxxx ?
This might be a problem with the symbolic link /etc/rc.d/rc.modules -> /etc/rc.d/rc.modules-2.6.xxxxx

Hello, yes you are correct..that link is to 2.6.24. That may have been my problem all along, just didn't know it. How would I edit that file to direct it to 2.6.27? Would simply renaming it work?

Now that I look, there is no rc.modules for 2.6.27.7 at all.

If you don't have a more recent version, you can use the 2.6.24 file. I checked here and there were no changes between the 2.6.27.7 & 2.6.29.2 versions (I do not have a 2.6.24 version at hand now...).

To change the link:
Just check the correct version numbers for the kernels...

There will be no practical effect, it just will stop saying that it is loading the modules for 2.6.24

Once again, that worked great. The error message is gone. And you were right, there was no appreciable change, but it is nice to have a clean boot. I don't do any heavy duty work with Slack, so I am content with 12.1 and this kernel. All is well!

Thanks again
Bob