Question...
How how fast has anybody gotten a QX6850 and at what voltage?
Thanks
Printable View
Question...
How how fast has anybody gotten a QX6850 and at what voltage?
Thanks
Hmmm. I think I posted an interim version by mistake. You shouldn't have needed any patches. Sorry.
Clark is correct about the mch fan header. It isn't monitored.
in0 = vMCH
in1 = vCORE
It looks like sensors is scaling them incorrectly though.
I'll have to dig out my notes on the temp and fan mappings. I don't have them with me at work so I'll grab them tonight.
Thanks gtj and clark.
gtj did you intend the scaling to be set up in sensors.conf ? ( actually sensors3.conf -- I'm using sensors version 3.0.1 with libsensors version 3.0.1). If so then we would just need to know how to set it correctly.
I haven't touched it so far.
I have now attached fans to the CPU fan header, the "Rear Fan" header and the "Rear Fan 2" header (called Aux in BIOS). Can't get at the front fan header without dismantling the computer so will leave it for now.
The CPU fan shows up in the sensors display as fan1, RearFan2/Aux shows up as fan 2, but the Rear Fan RPM is missing.
The BIOS also shows zero RPM for the rear fan but it's definitely turning. Is this a known problem?
By the way all speeds and voltages are at default - no overclocking or overvolting.Code:$ sensors
asc7621a-i2c-0-2e
Adapter: SMBus I801 adapter at 2000
in0: +1.21 V (min = +0.00 V, max = +3.31 V)
in1: +1.01 V (min = +0.00 V, max = +2.99 V)
in2: +3.24 V (min = +0.00 V, max = +4.36 V)
in3: +4.99 V (min = +0.00 V, max = +6.61 V)
in4: +11.84 V (min = +0.00 V, max = +15.94 V)
fan1: 1753 RPM (min = 0 RPM)
fan2: 906 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
temp1: -62.0°C (low = -127.0°C, high = +0.0°C) ALARM
(crit = -21.0°C) sensor = diode
temp2: +42.0°C (low = -127.0°C, high = +127.0°C)
(crit = +65.0°C) sensor = thermal diode
temp3: +45.5°C (low = -127.0°C, high = +127.0°C)
(crit = +65.0°C) sensor = transistor
temp4: +41.5°C (low = -127.0°C, high = +127.0°C)
(crit = -128.0°C) sensor = Intel PECI
temp5: -62.0°C sensor = Intel PECI
temp6: -85.0°C sensor = Intel PECI
temp7: +96.0°C sensor = Intel PECI
temp8: +118.0°C sensor = Intel PECI
There should be no scaling in sensors.conf. The driver outputs the correct values for voltage, temp and rpm directly. I'll look at the 3.0.1 version and see what it's doing but now that I think about it, they look actually correct for the Bonetrail and a QX9650, especially when idle. I may have been thinking about the XBX2.
Are you sure you have the rear fan plugged into the correct header on the MB? There are 2 in that general vicinity. The one behind the audio stack is the MCH fan and isn't monitored or controlled. The one behind the mounting hole next to the audio stack is the rear fan header.
Wow,this board is "intresting" to set up to say the least:yepp: .Gun shy to start overclockin:rofl: .
gtj,thanks for memory calculator.
My case is such that I can get close enough to read all the labels on the motherboard so I'm sure about which header is which.
Anyway I investigated a bit more and discovered a curious thing -- I do see an RPM reading for some fans but not others: the RPM sensing seems not to be working for all kinds of fans at low voltage. In particular I have some Noctua fans which are not sensed correctly.
Rear Fan header at 5.55V (CPU idle with case lid off):
Scythe 80mm (DFS802512L from Ninja Mini HS): 1134 RPM
Sharkoon 80mm golf ball: 367 RPM
Noctua NF-R8 80mm: zero RPM reading (but it is spinning)
Rear Fan 2 (Aux): 11.95V
Scythe: 2063 RPM
Sharkoon: 778 RPM
Noctua: 1909 RPM
Has anyone seen this before?
It's not an issue with one particular Noctua fan -- I have several of them and they consistently give an RPM reading with the Aux header but not the Rear Fan header. I won't be changing the Noctua fans though -- they are really nice and quiet :up: .
CPU fan = fan 1, Rearfan2/Aux= fan 2, Rear Fan = fan 4, so I guess the front fan will turn out to be fan 3.
It would be nice to know what all the temp readings are in the sensors output.
Hmmm. The fans all read for me so I'm not sure what's going on.
temp1_input = cpu on-die sensor (NOT the core temps)
temp2_input = motherboard (the asc7621a chip itself)
temp3_input = memory (between the 2 sets of dimm sockets)
The rest are assigned by various peci settings but really are not much use. Use the coretemp driver to get the individual core temps.
Wow, after reading the whole thread at once I'm tired... joking!
I was kinda hoping to find a solution to my problem. It's been 3 weeks since I started assembling my rig, with no other than the here discussed BoneTrail. I had really high hopes for this mobo, and I still do, but I'm stuck. Setup is the BoneTrail of course, C2D E8200, 8800GT and the, as far as I can tell, offender - OCZ Platinum 1333 (10666) 2x1Gb dual channel kit.
So far, not even my monitor has even displayed a thing, no boot, no POST, nothing, only the 3 beeps. I know this is a memory issue. the sticks seem to be fine, the shop I got them from tested them with an Asus board and they're ok. OCZ states that these are 777-20 at 1.8V although SPD on them seems to be 777-20 at 1.5V, probably for safe booting. However, for me it seems to be preventing correct boot, maybe insufficient voltage is applied.
Tried only one stick in the first slot, both sticks, no sticks all with the same result - 3 beeps.
Also tried setting the jumper to diagnostic mode without any luck, also removed the jumper with the same outcome.
Can't think of anything else and I was trying to find an answer here but I'm not sure anyone can help.
I guess I need at least one stick of some other mem that can boot so I can gain access to BIOS, since I couldn't even do that, I don't even know what BIOS version I have!!
GTJ, you are the man!! Any thoughts?
I have seen people with a similar setup, Platinums 1333 and working. I guess maybe it's this particular sample that is more voltage sensitive than others or there's a trick to make it work that I've missed.
Mr Steveo, nice to see you back!! I remember a few years back exchanging posts, back in the times of the good old Coppermine and Mushkin PC150 and i815 was king of the hill. Nice to see you back, like you I've been kinda away for a while...
thanks you guys for any help you can provide and sorry for the already long post.
What does that newest bios change?
Can someone post the way to get into watchdog.So it can be turned off.When i put bios config jumper on 2-3 at start up,it either gives 3 beeps or no post.Put it back to 1-2 and boots into windows fine.
Does setting bios config jumper pins to 2-3 set ram voltages to spd while booting into maintenance mod?If so this maybe the issue.
Unfortunatelly it doesn't work for me.
I've tried diagnostic with either one or two sticks but it's a no go.
Normal mode also with 1, 2 or no sticks is also no good, only 3 beeps.
I don't know what else to do.
I guess SPD on OCZ Platinum is not good for this mobo, maybe voltage is too low but can't enter BIOS to correct that.
I have probably done this 100 times before, but I did it once again. Same result, vCORE is always 1.238 no matter what I do. Has any used Everest and verified that the vCORE does change with a QX6850 and/or a QX9650? I just can't believe that this is a problem with my board, I really think it's a bios problem of some sort. Overall I am pretty disappointed with this board....
jerry
yes, CPU-Z doesn't read Vcore accurately for me either. i have to use Everest or another program to read it. not a big deal - Everest is a must-have anyway.
Thanks Blahung.This board does not play nice with ocz plats.
Manel,keep at it with one stick.It may take several(alot) trys.
Thanks for the temp assignments. I had already tried the coretemp kernel module but the version in Linux kernel 2.6.24 does not recognise the QX9650 CPU. Fortunately support for it has been added to the prerelease version 2.6.25 in the last few days :) !
With a little work I managed to get the new version from 2.6.25 to work in 2.6.24 too. So the sensors output now also shows the 4 core temps:
Code:$ sensors
asc7621a-i2c-1-2e
Adapter: SMBus I801 adapter at 2000
in0: +1.21 V (min = +0.00 V, max = +3.31 V)
in1: +1.01 V (min = +0.00 V, max = +2.99 V)
in2: +3.24 V (min = +0.00 V, max = +4.36 V)
in3: +4.99 V (min = +0.00 V, max = +6.61 V)
in4: +11.84 V (min = +0.00 V, max = +15.94 V)
fan1: 0 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
temp1: -55.2°C (low = -127.0°C, high = +0.0°C)
(crit = -21.0°C) sensor = diode
temp2: +47.0°C (low = -127.0°C, high = +127.0°C)
(crit = +65.0°C) sensor = thermal diode
temp3: +45.0°C (low = -127.0°C, high = +127.0°C)
(crit = +65.0°C) sensor = transistor
temp4: +48.0°C (low = -127.0°C, high = +127.0°C)
(crit = -128.0°C) sensor = Intel PECI
temp5: -56.0°C sensor = Intel PECI
temp6: -85.0°C sensor = Intel PECI
temp7: +96.0°C sensor = Intel PECI
temp8: +118.0°C sensor = Intel PECI
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +41.0°C (high = +76.0°C, crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +37.0°C (high = +76.0°C, crit = +100.0°C)
coretemp-isa-0002
Adapter: ISA adapter
Core 2: +45.0°C (high = +76.0°C, crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
Core 3: +45.0°C (high = +76.0°C, crit = +100.0°C)
You're welcome.
This is pretty weird that both of you are having the same type of problem. I saw your threads over at OCZ Forums as well.
While I have the OC3P1800 sticks the SPD is the same as yours: 7-7-7-20 @476MHz and I boot fine but maybe it's because of the extra headroom I have with the 1800s.
The 1 thing I DON'T have is an E8000 series processor which both of you have. Do either of you have a 6000 series processor to try out?
How about a DMM to see if the vDIMM really is at 1.5v? I can point you to the correct place on the MB to check.
Manel: You're running the 1333s and can't boot at all, right?
Forsaken1: You've got the 1600s and have to juggle to get going, right?
Maybe a combination of the Bonetrail and the 8000 processors is causing the MB to not set the correct timings.
gtj,yes i have a fluke 87 meter.Point me to the correct spot to measure voltage.I do have a E6600 in another setup.Last resort to pull it.
Yes,i have to "juggle" memory.Eventually it work.
Hi gtj
Yes, I can't boot at all. it is a coincidence we both having these problems with E8000, but I can't even say which BIOS version I have since I still couldn't boot.
I'm gonna try the suggestion of populating other slots other than the first, maybe it'll work, although intel states that this slot should always be populated.
I don't have a E6000 processor to test, I thought of it, maybe lower FSB would set lower mem freq and it would boot but unfortunatelly I can't find one to test.
Regarding DMM I do have a couple of Flukes laying around somewhere. Do you measure against a ground spot somewhere or between the other 2 VR pins?
Thanks for your help.
I did´nt see that earlier, changelog of bios 1478:
New Fixes/Features:
- Fixed issue where Intel Desktop Control Center failed to start
with certain processor.
- Updated processor support.
- Fixed language switching and 'Exit discard Changes' could slow
down the responsiveness of BIOS setup page.
- Fixed issue where optical drive and hard drive is not booted in
the order according to Boot Order.
- Added ability to underclock production non-XE processor
multipliers.
- Fixed issue on getting the Max Ratio of the CPU.
- Fixed issue where L2 cache size will not be displayed in BIOS
setup.
- Fixed POST code 5Ah hang with SATA HDDs and PCI Graphics card
in Slot 2.
- Added a workaround of option ROM which has an invalid PCI
Expansion ROM Header.
- Hid AHCI option ROM text when not running in RAID mode.
- Fixed issue causing Watchdog Timer firing to not be detected.
- Fixed blue screen during Vista* UEFI installation.
- Fixed issue where graphics cards that don't support 800x600
mode will not display anything on screen during POST.
- Added PCIe Link Width information for all PCIe Slot in Video
Configuration Setup page.
- Added support for booting El-Torito HDD emulation Memtest86+
with AHCI Option ROM.
- Fixed hard drive detection after cold reboot in AHCI mode.