linux-kernel - kernel config for AMD Athlon 64 X2 4200+ Manchester

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <bb078b9bc5a6138dc7ac78609713efdd@prager.ws>
Date:	Thu, 3 Jan 2008 09:05:28 -0700
From:	Bernd Prager <bernd@...ger.ws>
To:	linux-kernel@...r.kernel.org
Subject: kernel config for AMD Athlon 64 X2 4200+ Manchester

Hi all,

I am running kernel 2.6.23.12 and compiled with SMP on.
Unfortunately the kernel doesn't recognize my dual core processor:

$ dmesg | grep -i cpu
CPU has 2 num_cores
Processor #0 (Bootup-CPU)
SMP: Allowing 1 CPUs, 0 hotplug CPUs
PERCPU: Allocating 34344 bytes of per cpu data
Initializing CPU#0
CPU 0: aperture @ 610000000 size 32 MB
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 0/0 -> Node 0
Brought up 1 CPUs

$  cat /proc/cpuinfo 
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 43
model name      : AMD Hammer Family processor - Model Unknown
stepping        : 1
cpu MHz         : 2211.347
cache size      : 512 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm
3dnowext 3dnow up rep_good pni lahf_lm
bogomips        : 4425.39
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp


Any ideas how I can configure the kernel to fix that?

Thanks for any help,
-- Bernd Prager


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/