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!

--
__ __ _ I N C. http://www.sysdev.org
/ __|\\// __|| \ __ __ / tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities
|___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers

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.

--
Peter

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)

On Sun, 11 Feb 2007 11:14:13 -0500
"John K. Herreshoff" <nope@not.here> wrote:

> 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)
>

I did not upgrade a machine I built modules and kernel on
machine 1, the development machine and moved it to a new HD,
chroot to it and lilo'd the device. That means:

copy the modules to /lib/modules/2.6.20
copy System.map to /boot
copy vmlinuz to /
copy lilo.conf to /etc
and form the chroot jail execute lilo.

Done it a million times, since that is my
job. This time, insmod cant find the modules.
I do the procedure with 2.6.18.5 and it works
fine on the same target HD.

TonyB



There are 10 types of people in this world, those that read
binary and those who don't!

--
__ __ _ I N C. http://www.sysdev.org
/ __|\\// __|| \ __ __ / tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities
|___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers

On Sun, 11 Feb 2007 11:14:13 -0500
"John K. Herreshoff" <nope@not.here> wrote:

> 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)
>


What I suspect is that somewhere in the build's .config file,
when you run make menuconfig, the kernel must be told where
to look for the modules: normally, "/lib/modules/$VER".

That I must have been screwed up somehow...

TonyB


There are 10 types of people in this world, those that read
binary and those who don't!

--
__ __ _ I N C. http://www.sysdev.org
/ __|\\// __|| \ __ __ / tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities
|___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers

John K. Herreshoff <nope@not.here> wrote:
>
> 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

It does? I've only read not to use the same .config for a major version
jump, such as from 2.4.x to 2.6.x. Of course, the user must run
"make config/oldconfig/menuconfig/xconfig" to set things up.

- Kurt

On Sun, 11 Feb 2007 11:14:13 -0500, John K. Herreshoff wrote:

> 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

Where is that recommended by Kernel.org? My normal method is to copy the
previous kernel's config over to the new source tree, and then "make
oldconfig". After answering those questions, it's the usual process:
make bzImage
make modules
make modules_install

and then copy some things around and reboot. Been working fine for years
that way, here.

--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".

On Sun, 11 Feb 2007 15:25:54 -0600, Dan C wrote:

> On Sun, 11 Feb 2007 11:14:13 -0500, John K. Herreshoff wrote:
>
>> 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
>
> Where is that recommended by Kernel.org? My normal method is to copy the
> previous kernel's config over to the new source tree, and then "make
> oldconfig". After answering those questions, it's the usual process:


I'll just add a few remarks/complements

That part was simplified this way for 2.6.* :

> make bzImage
> make modules

make

> make modules_install

That part's the same, though I'd recommend to use a normal account :
-------
su danc
cd .../pathtonewkernel
cp /boot/previouskernel-config .config
make oldconfig
[ maxe [menu|x]]config ]
make
su
make modules_install
-------

>
> and then copy some things around and reboot.

Mmm, copy some :
cp arch/yourach/boot/bzimage /boot/newkernintown
cp .config /boot/newkernintown-config
[ cp System.map /boot/newkernintown-System.map ]

remember to build your estranged modules, like, for me,
NVIDIA, loop-aes and ALSA, don't forget to build the initrd if you're
using it and ***Don't forget to include your new kernel in the /etc/lilo.conf ***
I'll suppose you now won't forget to run 'lilo [-v[2]]' ;D)

> Been working fine for years
> that way, here.

Same here, but for a few "saturday night specials" when the lkml went
red hot but nothing to compare with the permanent stress of installing
any Win** for someone who had to *really* use it :-)

(...
besides, the latest QEmu (0.9.0) really worths a try, as far as my
tests seem to show, the new image model .qcow2 allows to store
snapshots of a running system which for my (licensed) winXP means
it'll boot in less than 10 seconds while I'm here typing this
meanwhile listening to some music on the net while waiting my
DVD backup tell me to go to bed ;D)

On Sun, 11 Feb 2007 02:31:19 -0800
Hufnus <tonyb@sysdev.org> 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...

Thanks to all who contributed and tried to help me with my
Linux 2.6.20 Slackware modules problem.

I produce a free embedded slackware distro. It runs on any
compact flash! You can pick it up at my site below, but wait
until v1.3.5 and my 14th release is fully tested ...

The problem was that Linux-2.6.20 was a BIGGG change from
2.6.18 & 2.6.19. The in memory footprint increased and many
new ways of doing things. First, some of the problems with
the modules was tight memory on my Advantech i486 breadboard.
The second, some of my kernel patches had to be adjusted and
I hadnt caught all.

It was a tedious week, but the feeling of getting it all
working in my own embedded i486/pxa255 Slackware distro makes
it all worth it!

Again thanks for your suggestions,
TonyB



--
__ __ _ I N C. http://www.sysdev.org
/ __|\\// __|| \ __ __ / tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities
|___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers

On Feb 11, 9:51 am, Hufnus <t...@sysdev.org> wrote:
> On Sun, 11 Feb 2007 11:14:13 -0500
> "John K. Herreshoff" <n...@not.here> wrote:

<snip>

> I did not upgrade a machine I built modules and kernel on
> machine 1, the development machine and moved it to a new HD,
> chroot to it and lilo'd the device. That means:
>
> copy the modules to /lib/modules/2.6.20
> copy System.map to /boot
> copy vmlinuz to /
> copy lilo.conf to /etc
> and form the chroot jail execute lilo.
>

If I remember correctly, an easier way of accomplishing this is to
specify an alternate directory to install the new files to:

make ROOT=</path-to-new-base-directory> install
make ROOT=</path-to-new-base-directory> modules_install
cp /etc/lilo </path-to-new-base-directory>
lilo -C </path-to-new-base-directory>/etc/lilo.conf -b /dev/<new-boot-
disk>


<snip>