On Sat, Feb 04, 2012 at 01:40:22PM +0200, Ville Valkonen wrote: > Hello, > > I bought a Jetway_JNC9KDL-2700 mini-itx motherboard that has a Intel NM10 > chipset and a Intel Cedar Trail 2700 (Dual Atom D2700 2x2.13Ghz) processor > (see [1], [2]). > > At the very first I tried to boot with the amd64 arch, though it failed > immediately at the beginning of the boot process (if I recall and conducted > right, it was because of the lacking processor support). Then, I fetched the > i386 snapshot from 31.1.2012 and booted. I was able to complete installation > now. On the next boot it got a bit further as compared on amd64 arch, though > it > froze on the acpiec line(see [3]). Power off/power on and 'boot -c && disable > acpiec && quit' helped for the freeze. > > The motherboard has a wireless ethernet device in the PCI-bus and the card > should work flawlessly (have used it in the earlier obsd versions). I also > tried with other pci-device, though it gave "watchdog timeout" errors. Reading > the manual page of acpiec and rapid googling of 'acpi embedded controller' did > not reveal whether it has something to do with the PCI-bus. Now, I am curious, > for what acpiec affects? > > SUMMARY > AFAIK CPU and ACPI aren't fully supported (see [3], [4]): > > Relevant lines from dmesg.boot: > OpenBSD 5.1-beta (RAMDISK_CD) #75: Sat Jan 21 00:57:12 MST 2012 > boot -c && disable apciec; quit > cpu0: unknown i686 model 0x36, can't get bus clock (0xc4081400) > cpu1: unknown i686 model 0x36, can't get bus clock (0xc4081400) > cpu2: unknown i686 model 0x36, can't get bus clock (0xc4381400) > cpu3: unknown i686 model 0x36, can't get bus clock (0xc4381400)
This is only used for estimating low/high as a speedstep fallback. The problem you alude to earlier seems to be that the processor doesn't advertise long mode in the amd64 case. See ie http://www.astaro.org/astaro-gateway-products/hardware-installation-up2date-licensing/40935-64-bit-installation.html http://www.mini-itx.com/store/?c=47 "64-bit OS Support: Currently EMT64 is *not* enabled on these boards. We expect Jetway to release a BIOS update when 64-bit drivers become available from Intel" Intel only documents the MSRs for the first generation of Atoms, perhaps this one is the same. You don't have EST in cpuid flags though so there is no way for you to test that this does anything at the moment... Index: sys/arch/i386/i386/machdep.c =================================================================== RCS file: /cvs/src/sys/arch/i386/i386/machdep.c,v retrieving revision 1.506 diff -u -p -r1.506 machdep.c --- sys/arch/i386/i386/machdep.c 2 Nov 2011 23:53:44 -0000 1.506 +++ sys/arch/i386/i386/machdep.c 4 Feb 2012 13:37:48 -0000 @@ -2075,6 +2075,8 @@ p3_get_bus_clock(struct cpu_info *ci) } break; case 0x1c: /* Atom */ + case 0x26: /* Atom Z6xx */ + case 0x36: /* Atom [DN]2xxx */ msr = rdmsr(MSR_FSB_FREQ); bus = (msr >> 0) & 0x7; switch (bus) { @@ -2131,6 +2133,7 @@ p3_get_bus_clock(struct cpu_info *ci) break; case 0x2a: /* Core i5/i7 2nd Generation */ case 0x2d: /* Xeon E5 */ + case 0x2f: /* Xeon E7 */ /* BUS100 */ break; case 0x1d: /* Xeon MP 7400 */ Index: sys/arch/amd64/amd64/est.c =================================================================== RCS file: /cvs/src/sys/arch/amd64/amd64/est.c,v retrieving revision 1.25 diff -u -p -r1.25 est.c --- sys/arch/amd64/amd64/est.c 19 Apr 2011 22:14:54 -0000 1.25 +++ sys/arch/amd64/amd64/est.c 4 Feb 2012 13:37:48 -0000 @@ -198,6 +198,8 @@ p3_get_bus_clock(struct cpu_info *ci) } break; case 0x1c: /* Atom */ + case 0x26: /* Atom Z6xx */ + case 0x36: /* Atom [DN]2xxx */ msr = rdmsr(MSR_FSB_FREQ); bus = (msr >> 0) & 0x7; switch (bus) { @@ -228,6 +230,7 @@ p3_get_bus_clock(struct cpu_info *ci) break; case 0x2a: /* Core i5/i7 2nd Generation */ case 0x2d: /* Xeon E5 */ + case 0x2f: /* Xeon E7 */ /* BUS100 */ break; case 0x1d: /* Xeon MP 7400 */
