Hi Herbert & List, Sounds like there might be a CPU clock programming issue, I'll look into it and fix it asap, should just be a comBIOS update.
Best Regards, Soren Kristensen CEO & Chief Engineer Soekris Engineering, Inc. Herbert J. Skuhra wrote: > On Mon, 12 Nov 2012 13:51:54 +0100 > Mitja Muženič <[email protected]> wrote: > >> So the current situation is: >> OpenBSD 5.1 and earlier - no Enhanced Speedstep control for >> net6501-50 and 6501-70, so they only run at 600MHz. >> OpenBSD 5.2 - Enhanced Speedstep control for net6501-50 and 6501-70, >> but the initial display of the clock frequency after reboot is >> wrong. Blindly setting hw.setperf=100 will make the CPUs run at >> nominal 1000 and 1600MHz respectively. >> OpenBSD 5.3 (to be released) - Enhanced Speedstep control works and >> the initial display is correct - e.g. " hw.cpuspeed=601". Setting >> hw.setperf=100 is still needed to make the CPUs work at their >> nominal speed. >> >> I don't know how it is with other operating systems but it's safe to >> presume that unless your OS actively sets the CPU to the high speed >> state your net6501-50 and net6501-70 units will be severely >> underclocked. net6501-30 runs at fixed 600MHz and has no Enhanced >> Speedstep capability. > > On FreeBSD 9.1-PRERELEASE (i386) changing dev.cpu.0.freq (default: > 600) has no effect; e.g. building a kernel takes approx. 2,5 hours (at > 600 MHz and 1600 MHz). I've also removed "device cpufreq" from my > kernel. > > In comparison to my Atom Netbook (N270 @1.6GHz) my net6501-70 performs > rather slow. :-( > > Is there a patch for FreeBSD? > > I will try OpenBSD-current soon. > _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
