[QUOTE=Mark Rose;364463]dmidecode on Linux (and probably BSD) requires root privileges. There is no other easy way to get the information though.[/QUOTE]

On the positive side, I assume most installs of mprime are done by people who have root access to that machine. The determination of the memory structure only has to be done once (or at least only after hardware changes). Or mprime could ask to be granted root privileges on a one time only basis, still assuming mprime is rarely installed by people without root access

[QUOTE=tha;364468]On the positive side, I assume most installs of mprime are done by people who have root access to that machine. The determination of the memory structure only has to be done once (or at least only after hardware changes). Or mprime could ask to be granted root privileges on a one time only basis, still assuming mprime is rarely installed by people without root access[/QUOTE]

All true. Though I run it on 3 machines I have no root access to (with permission).

It might be easier to run an integrated memory benchmark to solve the problem, then auto-tune the number of cores based on that.

I kind of wish mprime would skip the first core when pinning to fewer cores than present. Many interrupts and whatnot are always handled by the first core, so that creates unnecessary contention. I guess I could look at the source code and write a patch ;)

I finally have my 4670k running
:party:

Well, on stock cooler the temps jump to the high 50's within seconds on stock. Good thing I have my hyper 212 svo coming. :smile:

EDIT: Mid 70's now. Still going up.

[QUOTE=kracker;365321]I finally have my 4670k running
:party:

Well, on stock cooler the temps jump to the high 50's within seconds on stock. Good thing I have my hyper 212 svo coming. :smile:

EDIT: Mid 70's now. Still going up.[/QUOTE]

Good luck and Congratz! :grin:

Lol @ stock coolers. Hyper 212 is gonna be a good step up.

Running 4 DC's now. It's in the 80's, doing stress it really throttles... hyper 212 evo coming Monday :smile:

Well, I'm glad I got 2400 memory.

If you weren't getting your cooler really soon I'd suggest trying to crank the voltage down a bit. You might be able to, I don't know. I sure would have been, myself, but I had my H80i by the time I built my i5-3570k system.

Well for fun some memory benchmarks... hf :razz:

Getting to 2400 was [I]way [/I]easier than I thought it would be...

These days the memory speeds aren't all that difficult. My motherboard recognized the settings immediately when I booted for the very first time and I haven't had an issue since. 2400MHz @ 10-12-12-31 like a charm.

2500 MHz @ 11-13-13-35 completely not possible. 2400 MHz @ 10-12-11-31 also completely impossible. Depends on the sticks you got. The TridentX series had 2133, 2400, 2600, 2666, 2800, 3000 and I think briefly a 3200 kit (?) which means each set is individually tested and binned at whatever actually works, which basically means your overclocking yields were < 5% and with a LOT of work to get there.

Nice job, though. Next step is overclocking the CPU which will be more fun.

[QUOTE=TheMawn;365407]
Nice job, though. Next step is overclocking the CPU which will be more fun.[/QUOTE]

Indeed. Fun time tomorrow! :smile:

Meh, I'm confused. What do people use to check Haswell temps? Check difference.