> > Ok, I've got 2.0.18 and just recompiled the kernel with gcc 2.7.2 to add
> > support for some of my hardware. LILO'd and rebooted, and got to the part
> > where the kernel determines module dependencies, and the kernel tells me
> > it can't find a bunch of symbols in various .o files in /lib/modules/2.0.18.
> > I am doing
> > make dep
> > make clean
> > make zImage
> > make modules
> > make modules-install
> > Is this the wrong procedure? I only have a couple things loaded as
> > modules...
> If it makes you feel any better, I'm getting the same thing after
> following the same procedure. I updated to 2.0.26 with the packages from
> ftp.wsc.com (/pub/freeware/linux/...). Everything is fine with the kernel
> supplied with the update, but when I recompile to get rid of all those
> unnecessary device drivers for hardware I don't have, I get dozens of
> "undefined symbol" errors *and* even more insmod errors complaining about
> wrong versions *and* modprobe saying it can't find module block-major-xx.
> If anyone knows what needs to go or be added to get rid of these errors,
> please let us know!
> I've read the modules documentation, but it happily assumes everything
> works and doesn't tell you want might cause any of the errors that many
> people seem to be getting. It must be something so basic we're missing it
> and the doc writers don't consider it obscure enough to document... :)
> I've enabled modules support in the kernel, enabled version numbers
> (although maybe that's the first thing I'll leave out next time), and done
> the make modules; make modules_install.
Ditto here: rebuilt the 2.0.18 kernal, get lots of module dependency
on rebooting. I looked into the directory having the modules, and
that several of the modules that I didn't want were still there. So, I
deleted everything that hadn't been updated when I did the 'make
make modules_install'. When I rebooted, I was then down to one error.
would say what that error was, but I cannot remember! Does the Depmod
on all the modules in the module directory? If so, you may have a
of modules that were compiled in the old kernal, and ones that were
with the new one.