Hello !
> > Just updated a Debian box from slink to potato, and also compiled a nice
> > shiny 2.2 kernel (previously used 2.0.34). When I rebooted I got a flood of
> > unresolved symbol errors. I've rerun update-modules, and the same result
I don't know how did you do it but the standard way of compiling a new
kernel : (everything happens in the kernel source directory) make
mrproper, make menuconfig, make clean, make bzImage, make modules, make
modules_install, make install, depmod -a, cp the System.map to /boot (if
install didn't do it). Or, because you use debian you have another option.
make-kpkg. The process is : make mrproper, make menuconfig, make-kpkg
--bzimage --revision=name.number kernel_image
This will create a .deb package for you into the previous directory which
you are in (sorry my english; if you are in /usr/src/kernel-2.2.17 then
the image wil be at /usr/src). Just install the image with dpkg -i
image-name.deb and the dpkg will does everithing for you.
Bye,
Ago
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
