I've just gotten my new version of Linux. Slackware (the 4 disk set). I
have kernel ver. 2.0.0.
The error is on booting, just after the kernal checks /proc and prior to
checking lp I get several errors of the following type:
*** Unresolved symbols in module /lib/modules/2.0.0/cdrom/sbpcd.o
and several others in the /cdrom dir and other dirs. As I'm compiling the
new kernel there are no error messages, not even a warning. I have checked
that /usr/src/linux/include/linux is linked to /usr/include/linux and
/usr/src/linux/include/asm-i386 is linked to /usr/include/asm. Prior to
compiling I do a 'make mrproper', 'make config', and 'make dep'. The I do a
'make zImage', ren the old vmlinuz to something, copy the new image to root,
do a 'lilo -C /etc/lilo.conf' and reboot. The worst part of all to me is
that the unresolved symbols are in modules that I don't even want. When I
do a make config I answer 'y' to the question about including support for
cdu31a cdrom drive non of the others. I specificly do not include any scsi
support and on boot up I get errors in scsi modules.
Once the system is up it appears to work fine but the errors irratate me on
boot up. I've done this with every version I have to include support for my
cdrom and sound-blaster. I've have never gotten such errors.
Also is there a way to trap the errors? dmesg does not show them and they
scroll by to fast to read all of them.
Any help would be greatly appreciated.
Thomas L. Gossard