According to Kevin Hayes: While burning my CPU.
>
> 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?
Normaly a warning is not reealy anything to worry about, however if you have
large amounts of them, then something is wrong, "possably" the cause is that
you have slackware 3.5 which i have been led to belive uses egcs as its
compiler, egcs is not suited to make 2.0.3x kernels.
As to weahter slackware 3.5 has actualy got egcs as its default compiler i
cannot comment as i dont have slackware 3.5 installed here. Maybe someone
can confirm just which compiler slackware 3.5 actualy has, also is there
any option on having gcc instaed of egcs, or generaly, any information
concerning which compiler is installed with slackware 3.5.
>
> 2) Do I get "unresolved symbol(s) /lib/modules/2.0.32/(stuff I never chose in
> config)?
Because they are left there from 1) a previous compile, 2) they are left
there from the origanal install of the system. It would seem that the
easiest way out of the problem is to move all the modules to a backup
directory before making and installing new modules.
>
> 3) Do I get messages indicating I can't load a vfs or iso9660 fs when they were
> compiled in as modules?
There are many reasons, if you had included the error messages generated
when you try to load modules, then it would have made it very easy to point
you in the right direction, now all one can do is guess.
1) Kerneld is not running,
2) You are using "insmod" to load iso9660 which will result in;
Cannot open /lib/modules/misc/iso9660.o which is correct, the module is
called "isofs.o", however "modprobe iso9660" will do it.
3) No 'depmod -a' has been run, (unlikly as you have "unresolved symbols"
message's at boottime)
4) Too many more possablitiys to name here.
>
> 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
Now just "what do you mean by that" If you remove a file with 'rm filename'
then the file is "gone", so how can you get more "wierd modules" when you
remove a module.??
> 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:
Huum, your explanation of what you are doing leads me to belive that you
have totaly misunderstood all the basic's of starting/compiling and
installing a new kernel and its modules.
I suggest you read /usr/src/linux/README, is not all that big a file to
read, it will explane just what is needed to be done to make a custom kernel
and "HOWTO" install it.
A small tip from me, while doing 'make config' you see a kernel option which
you dont have any clue as to what it is, do i need it? whats it for?, an
example would be;
Kernel math emulation (CONFIG_MATH_EMULATION) [N/y/?]
Above you have 3 things to chose from, N which is de default, just hitting
enter will say "No" to the option, "y" speaks for itself and finaly the "?"
hitting "?" will show a help page, which is the relavant page taken from
/usr/src/linux/Documentaion/Configure.help.
It will tell you what its for, what enviroments use it, and a gerneral need
it or not advice, like "Its safe to say "N" here.
I see so many messages here about "how do i know what a kernel option is
for" well thats the answer.
>
> (cd /usr/include;rm -rf asm linux scsi; ln -s /usr/src/linux/include/* from
> kernel README)
Yes, and also it says use 'ln -s' to make the nessacary links to the kernel
source afterwards as well, i trust you did do it otherwise you would have
had more compile problems.
> 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
Its cp /usr/src/linux/arch/i386/boot/zImage to which ever directory is
defined in /etc/lilo.conf
> mv zImage vmlinuz
That depends on what is defined in /etc/lilo.conf.
> 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.
Once again you seem to have misunderstood, a module is called (take sbpcd)
for an example, sbpcd.o not spbcd.i you are mixing up the "bootdisk" spdcd.i
which is for "installing slackware" from a spdcd.
This is possably one answer to you question on not being able to load
modules..
What you seem to have done is got your system going installed and configured
things like X, PPP, printing etc, which causes so much trouble for some,
but the easy thing like making a kernel and installing it, seems to cause
you so many problems, i rather think you are overlooking the most important
issue's which are discussed in /usr/src/linux/README, after all you did say
you have read it.
If your problem persists then send me a personal note, i will try to walk
you thro' the nessacary things.
>
> Thunderstorm here ready to fry my modem. Gotta go. Thoughts appreciated.
Look at it this way,
'They say' Lightning never strikes the same place twice.
So if you get hit, put your "new" modem in exactly the same place.
>
> Regards,
>
> Kevin
>
--
Regards Richard.
[EMAIL PROTECTED]
