The PSU I have is the one I mentioned in another thread that I don't entirely trust, but still I didn't expect numbers like I'm getting, as I'm about to discuss. I'm not sure how familiar most of you are will Linux, but there's a tool to read diodes similiar to MBM called lm_sensors. Like MBM it can be configured to read different chips of chips and will try to autodetect the chips you have but it can get them wrong. The readings I'm getting off of it are so screwy that either my PSU is completely shot (but the system seems to RUN fine) or the sensors have got to be mislabeled.
Now the fans are okay, they are L1As. But the voltages? Holy crap! Anyone want to take a crack at guessing whether the numbers are mislabeled, wrong, or whether I need to turn off my machine RIGHT NOW before smoke comes out?
I reckon it's common for voltages to be mis-read by software - I get weird values for at least one of the rails on all machines where I run MBM and/or lm_sensors.
For comparison this is the output I get from my 75MIV2-L, XP-M 2400+ and Nexus NX-3000 PSU:
Adapter: ISA adapter
VCore 1: +1.34 V (min = +1.42 V, max = +1.57 V) ALARM
VCore 2: +2.61 V (min = +2.40 V, max = +2.61 V) ALARM
+3.3V: +6.62 V (min = +3.14 V, max = +3.46 V) ALARM
+5V: +5.07 V (min = +4.74 V, max = +5.24 V)
+12V: +11.84 V (min = +11.40 V, max = +12.60 V)
-12V: -19.54 V (min = -12.63 V, max = -11.41 V) ALARM
-5V: -2.12 V (min = -5.24 V, max = -4.76 V) ALARM
Stdby: +5.06 V (min = +4.74 V, max = +5.24 V)
VBat: +2.03 V
fan1: 3125 RPM (min = 0 RPM, div = 8)
fan2: 0 RPM (min = 3013 RPM, div = 8) ALARM
fan3: 0 RPM (min = 3000 RPM, div = 2)
M/B Temp: +35°C (low = +15°C, high = +40°C) sensor = thermistor
CPU Temp: +39°C (low = +15°C, high = +45°C) sensor = thermistor
Temp3: +61°C (low = +15°C, high = +45°C) sensor = thermistor
I _think_ the Temp3 value is that reported by the onchip thermistor - but currently that value is a bit out of whack - it usually tracks the "CPU Temp" to within a few degrees but sometimes it goes nuts - sometimes drops to below room temp, sometimes temps way above the "CPU Temp" like now.
My uptime is at nearly two months now... and the system's been rock.
Also, I'm a little disappointed that the CPU is so hot running at 1.35 VCore, even with stock fan. Think that's an indication I need to reseat the heatsink?
Are these load temps? You can see my load temps above - that's a 2400+ XP-M with a DP-102 with a (temporary) crappy 60mm fan. Before I installed lm_sensors I used a thermocouple at the base of the DP-102 and got results in the same range (+- 5oC or so). I dunno about you but I reckon MY temps OWN for a CPU churning out the equivalent 2.4GHz of lovin F@H goodness.
If you are worried about the seating of your HSF and these are idle temps then try loading the CPU - if temps do go nuts then you probably do have poor HSF contact.
I'm going to dig into the bios when I get home tonight and see what THEY say about the voltages, there should be a place to get that but I can't check them at the moment.
Good idea - they should be accurate. I don't think BIOSes have an idle loop so in the BIOS it's kind like the CPU was pretty well loaded (at least this USED to be the case AFAIK) - so expect slightly higher temps than you see in an unloaded Linux (which has the idle/sleep states).
The other weird thing is that my RAM seems to buzz or hum when it's going through the selfcheck at startup. I've never heard that before, and was just a little weirded out by it. It's fairly loud, and stops as soon as the selfcheck is done. Clues?
I tend to agree with Mati
on this - I've never had these noises because my case doesn't actually have a PC speaker.
btw.. you could also disable the memory check completely if you like - I think I've done this to minimise boot times.