1 |
2008/6/3 Drake Donahue <donahue95@×××××××.net>: |
2 |
|
3 |
> |
4 |
> On Tue, 2008-06-03 at 09:01 +0000, Beso wrote: |
5 |
> > hi, |
6 |
> > |
7 |
> > i've got a strange problem with my new notebook pc. i've bought a pc |
8 |
> > with an amd athlon 64 x2 processor with 2 cores, an atheros board and |
9 |
> > an rs690 ati. |
10 |
> > my old pc was a turion 64 with an atheros board and an rs480. now the |
11 |
> > components inside are all about the same so i've just copied the old |
12 |
> > gentoo system into the new pc and tried to recompile the kernel to |
13 |
> > have it tuned for the new processor. so the thing i've done was to |
14 |
> > activate the symetric multiprocessing and set to compiled into the |
15 |
> > kernel of md4, md5, md6 and aes x86_64 chipers for a luks /home |
16 |
> > chipering. |
17 |
> > the problem is that with the old normal config the kernel detects one |
18 |
> > processor and one core and it works, loading the modules, but when |
19 |
> > enabling simetric multiprocessing the kernel detects just one |
20 |
> > processor and one core and then it fails to load modules because of a |
21 |
> > different executable format in the modules. |
22 |
> > |
23 |
> > the strange thing is that opensuse livecd and mandriva live cd |
24 |
> > recognize the double processor (/proc/cpuinfo has 2 lines) and is able |
25 |
> > to step it in the right way. does anyone has a hint on what to control |
26 |
> > in the kernel config to see what's wrong?! |
27 |
> > |
28 |
> > thanks. |
29 |
> > |
30 |
> > -- |
31 |
> > dott. ing. beso |
32 |
> If the attempt to boot does not end in a kernel panic; |
33 |
> use <shift-page up> to get to the top of the console output produced |
34 |
> during boot. If the boot loader has started an SMP kernel, a line |
35 |
> similar to this: "Linux Version 2.6.24-gentoo-r8 (root@livecd) (gcc |
36 |
> version 4.1.1 (gentoo 4.1.1-r3)) #1 SMP Sat May 24 14:06:10 EDT 2008" |
37 |
> should appear. The key word being SMP. No key word, "SMP", means that |
38 |
> "make menuconfig" (or whatever kernel configuration tool you use needs |
39 |
> to be redone. |
40 |
> As far as I know under, Processor type and features,: |
41 |
> [*] Symmetric multi-processing support |
42 |
> Subarchitecture Type (PC-compatible) ---> |
43 |
> Processor family (Opteron/Athlon64/Hammer/K8) ---> |
44 |
> produces an appropriate SMP kernel. |
45 |
> A <shift-page down> should reveal a line like: |
46 |
> CPU has two num_cores |
47 |
> A couple more <shift-page down>: |
48 |
> Initializing CPU#0 |
49 |
> About 3 more <shift-page down>: |
50 |
> Brought up 2 CPU's. |
51 |
> About modules, I'm guessing modules compiled for single cpu have |
52 |
> differences from those compiled for multiple cpu. Also guessing |
53 |
> that /etc/modules/autoload.d and/or udev is trying to load single cpu |
54 |
> module(s) that were not written to adjust to a single cpu kernel. |
55 |
> |
56 |
|
57 |
so grub needs a different line at startup when using multicore?! |
58 |
|
59 |
|
60 |
|
61 |
-- |
62 |
dott. ing. beso |