As far as I know some drivers do not work as modules with SMP option enabled. I am working on kernel 2.0.36 and I do not know if this belongs to kernel 2.2.5, too - maybe I am completely wrong.
Seems (and I am telling you) that you have to hardwire the drivers. By the way, where is the problem to hardwire them?

Dietmar

Borries Demeler wrote:

Greetings,

I am stumped: I compiled a kernel (2.2.5, single processor mode) with a
bunch of modules in it, boot the new kernel, run "depmod -a" during boot,
it finds all modules and starts just fine.

Now I recompile the kernel, exactly the same setup, same modules,
everything identical, except: this time it is an SMP kernel, and
under "Processor type and features" I turn on MTRR support and
SMP support (I got a dual PII450). I recompile the modules, reinstall
the modules (same ones) and reboot. This time "depmode -a" generates
tons of unresolved symbols for the modules, needless to say, they don't
load and of course, they don't work.

Well, almost. Some of the modules don't generate error messages and
do load. What is going on here? I read modules.txt and smp.txt, but
no mention of this problem.

I get the same error regardless of wether I compile/install the SMP
modules (rm /lib/modules/2.2.5; make modules; make modules_install),
or if I use the modules compiled with the single CPU setup.

Anybody has got a clue? Please let me know... And please don't tell
me to hardcode the modules into the kernel, I already know that works.

Thanks in advance!

-Borries
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]

 
-- 
We all have lack of knowledge... 

Dietmar Stein, Systemadministrator UNIX/Linux
[EMAIL PROTECTED], [EMAIL PROTECTED]
 

Reply via email to