1 |
Beso <givemesugarr@×××××.com> posted |
2 |
d257c3560806030201y23df89fdy1cf12ae0bb3b772a@××××××××××.com, excerpted |
3 |
below, on Tue, 03 Jun 2008 09:01:04 +0000: |
4 |
|
5 |
> the problem is that with the old normal config the kernel detects one |
6 |
> processor and one core and it works, loading the modules, but when |
7 |
> enabling simetric multiprocessing the kernel detects just one processor |
8 |
> and one core and then it fails to load modules because of a different |
9 |
> executable format in the modules. |
10 |
|
11 |
This indicates that the modules and the kernel aren't matched. IOW, you |
12 |
apparently compiled the new kernel but failed to compile the matching |
13 |
modules, so it's trying to use the old ones, which don't match the new |
14 |
kernel, so it won't load them. |
15 |
|
16 |
Even if it's the exact same kernel you compiled, if you change options, |
17 |
particularly something as big as SMP, you'll need to recompile the kernel |
18 |
modules as well. |
19 |
|
20 |
Also note that if you use an initrd/initramfs, you'll need to redo it, |
21 |
loading the new modules as appropriate into it as well as placing them in |
22 |
the normal /lib/modules/<kern-ver>/ dir. I don't run an initramfs/ |
23 |
initrd, so have never learned the technical intricacies thereof, but |
24 |
wherever it's trying to load them from, you don't have the right ones |
25 |
there for it to load. |
26 |
|
27 |
One way or the other, with or without the initrd/initramfs, the kernel is |
28 |
trying to load modules that don't match the kernel, and failing. Correct |
29 |
that, and you will have fixed at least that problem, altho it's possible |
30 |
you'll then have others to fix as well. |
31 |
|
32 |
-- |
33 |
Duncan - List replies preferred. No HTML msgs. |
34 |
"Every nonfree program has a lord, a master -- |
35 |
and if you use the program, he is your master." Richard Stallman |
36 |
|
37 |
-- |
38 |
gentoo-amd64@l.g.o mailing list |