So proud. Got Slack 3.5 installed, fumbled through getting lpr working, ppp
going, got X looking good, and even compiled and got kde cruisin'. Many thanks
to this list, and a big tip 'o the hat to Ishak, a very patient and considerate
guy.
Now a big booger. Compiling a custom kernel. Maybe I shouldn't have even tried,
since sbpcd.i included with Slackware was cruisin' good, just hated the sbpcd
probe.
Starting with general questions, why:
1) Do I get so many "warning: control reaches end of non-void function" errors
during compile?
2) Do I get "unresolved symbol(s) /lib/modules/2.0.32/(stuff I never chose in
config)?
3) Do I get messages indicating I can't load a vfs or iso9660 fs when they were
compiled in as modules?
Guesses: I saw in a previous post that compile warnings aren't necessarily a
bad thing, so maybe I should just ignore 1). I read in a previous post that you
can just delete the weird modules. Didn't work. I got more weird modules. Even
when I reloaded ( and yes, lilo'd) the original sbpcd.i So there must be a
script or something telling the boot process to load non-existent modules,
created at kernel config, and left in after another config. The fact that I
can't load filesystems loaded as modules leads me to believe that I'm screwin'
up big time when I do the module thing. My sequence:
(cd /usr/include;rm -rf asm linux scsi; ln -s /usr/src/linux/include/* from
kernel README)
cd /usr/src/linux
make mrproper
make menuconfig (make config last time)
make dep
make clean
make zImage
make modules
make modules_install
cp zImage /root
mv zImage vmlinuz
lilo
I was backing up the old kernel, but screw it. I now just boot from my backup
floppy, run setup and reinstall sbpcd.i from the slack cd, run lilo, and have a
functioning system, albeit with the unresolved symbol crap on boot.
Thunderstorm here ready to fry my modem. Gotta go. Thoughts appreciated.
Regards,
Kevin
