I didn't run dmesg | grep cpu in time. This is the actual output:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] ACPI: SSDT 7f6e2000 00655 (v01 PmRef CpuPm 00003000 INTL 20061109)
[ 0.000000] SMP: Allowing 4 CPUs, 2 hotplug CPUs
[ 0.000000] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 14 pages/cpu @f79b9000 s33280 r0 d24064 u57344
[ 0.000000] pcpu-alloc: s33280 r0 d24064 u57344 alloc=14*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Initializing CPU#0
[ 0.000000] CPU 0 irqstacks, hard=f5406000 soft=f5408000
[ 0.000341] Initializing cgroup subsys cpuacct
[ 0.000445] CPU: Physical Processor ID: 0
[ 0.000448] CPU: Processor Core ID: 0
[ 0.000453] mce: CPU supports 5 MCE banks
[ 0.000464] CPU0: Thermal monitoring enabled (TM1)
[ 0.047909] CPU0: Intel(R) Atom(TM) CPU D2500 @ 1.86GHz stepping 01
[ 0.154124] CPU 1 irqstacks, hard=f54d4000 soft=f54d6000
[ 0.154133] smpboot cpu 1: start_ip = 99000
[ 0.164082] Initializing CPU#1
[ 0.261500] Brought up 2 CPUs
[ 1.231616] cpuidle: using governor ladder
[ 1.231620] cpuidle: using governor menu
[ 2.230968] microcode: CPU0 sig=0x30661, pf=0x4, revision=0x106
[ 2.235640] microcode: CPU1 sig=0x30661, pf=0x4, revision=0x106
[ 5.572464] coretemp coretemp.0: Unable to read TjMax from CPU 0
[ 5.572507] coretemp coretemp.0: Unable to read TjMax from CPU 1
So yes, I suppose it detects my CPU.
I do confirm that 'dmesg | grep pstate' outputs nothing though.
Quote:
I am wondering which distribution in which version you are running
|
I'm using CrunchBang 11 "Waldorf". Might be hipster-y, but the newer and more mainstream ones made the screen flicker like crazy and I didn't possess (nor I do now) the skill to fix that. This distro worked out of the box and I was happy with that.