Peter wrote:

> On Sun, 11 Feb 2007 02:31:19 -0800, Hufnus wrote:
>
>> I compiled bzImage and modules using a make menuconfig of
>> my previous homemade and working 2.6.18.5 kernel. Everything
>> works fine except insmod/modprobe. It will not find any of the
>> modules in /lib/modules/2.6.20, it just doesnt seem to know
>> where to look because I can insmod fine if I provide a full
>> path to the .ko and I look out for the module dependencies.
>>
>> Upgraded to the latest module-init-tools-3.2.2 and no effect.
>>
>> The module mapping files in /lib/modules/x.x.xx.xx/ look
>> consistent in size with the 2.6.18.5 ones.
>>
>> Kernel 2.6.18.5 was made with gcc 3.4.5 and the new one with
>> gcc 3.4.6.
>>
>> Where should I look or what can I test to get hints to what is
>> going here...
>>
>> thxs
>> TonyB
>>
>>
>> There are 10 types of people in this world, those that read
>> binary and those who don't!
>>
>
> sounds like you forgot to boot off the new kernel.
>

Maybe. Kernel.org reminds us to start with a new config file each time we
upgrade the kernel. It's a pain, but may solve your problem, if you are
booting the new one. I'd make sure you had the new kernel running:
uname -r will reveal what you are running kernel wise.

If you have the new kernel running...

John.

--
jkherr at power - net dot net (wipe the spaces)