Hi Ray,
Im sorry i had a typo error on my previous mail.. you're right, it's an
ethernet card, not sound card.. Also, regarding the compilation, you're
right, i compiled a new kernel with SMP support as described in the
smp-howto, which said i'll have to do "make modules; make modules_install".
It's a 2.2.12 kernel. But how do i extend the version number? Is it by
selecting "set version info on all symbols..." during make config? if it is,
i think i enabled it (but then i must have missed it).
Also, i have other questions:
1. is there a way i can make smp support during a fresh install of redhat
6.1?
2. if not, i see an image with an smp extension under /boot.. is this
something i can readily use to have smp support?
Thanks a lot. Really im starting to feel the difficulties of administering
remote machines (with no tech support onsite).
Mary Christie
----- Original Message -----
From: Ray Olszewski <[EMAIL PROTECTED]>
To: Mary Christie Generalao <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Saturday, June 03, 2000 10:30 PM
Subject: Re: unresolved symbols
> I don't know what a "tulip sound card" is ... the tulip.o module I know
> about is for an Ethernet card ... but unresolved symbols generally
indicates
> one of two things:
>
> 1. The module depends on something that is not installed in the
> kernel (or loaded as a module); an example familiar to
> many is that the ne.o module depends on 8390.o . A
> proper modules.dep file (created with "depmod") catches
> these if you are using "modprobe". If you are using
> "insmod", you have to catch them by hand.
>
> 2. The module was compiled for a different kernel version than
> the one you are trying to load it with.
>
> From your prior messages, I'd bet that the second is your problem. It
> sounded like you compiled a new (for example) 2.2.13 kernel on a system
that
> had an old 2.2.13 kernel, and you did not extend the version number to
> distinguish them. As a result, when you did "make modules_install", you
> overwrote the old kernel's modules with the new ones. (Unless you
previously
> did something like "mv /lib/modules/2.2.13 /lib/modules/2.2.13-old", thus
> making the modules backup that the standard kernel-compile README file
> recommends; then you have them safely tucked aside and you can put them
back
> quite easily.)
>
> If you and the machine are not co-located, this is tough to fix. You need
to
> reload the kernel-image file for your default kernel or compile a new
kernel
> that works. You might have a config file for your default kernel in /boot;
> some distributions include one with the image, but others don't.
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
