A friend purchased a P35-DS3P mobo with two sticks of 1gb DDR2 RAM, a 3-pin
Coolermaster HSF, and a PCI-E video card to upgrade an older P4 478 system
in an ATX case. The PSU is a 480W Antec Truepower, and when everything is
connected the only response is a quick flicker of the CPU fan--no POST, no
PSU or case fans are spinning up, nothing. OTOH, when the CPU fan connector
(3-pin on the HSF, 4-pin on the mobo) is moved to a case-fan connector on
the mobo, it boots with no problem.
While this was connected, I connected the original Intel HSF (4-pin) to the
mobo's CPU-fan connector and although it still started fine the HSF
connected to the CPU-fan mobo connector (not attached to the CPU) would only
blip on every few seconds, never fully cranking up. I tried the same test
with an old 478 P4 HSF with a 3-pin connector and it would blip once, then
nothing. The 3-pin connector fits only one way with the guide on the mobo,
so I assumed the 3-pin-connector HSF's would work.
At this time it appears to function fine as long as the HSF is connected to
a case-fan connector on the mobo, but these seems make-shift to me. What am
I missing on this 4-pin CPU-fan connenctor issue?
Bob Davis wrote:
> A friend purchased a P35-DS3P mobo with two sticks of 1gb DDR2 RAM, a
> 3-pin Coolermaster HSF, and a PCI-E video card to upgrade an older P4
> 478 system in an ATX case. The PSU is a 480W Antec Truepower, and when
> everything is connected the only response is a quick flicker of the CPU
> fan--no POST, no PSU or case fans are spinning up, nothing. OTOH, when
> the CPU fan connector (3-pin on the HSF, 4-pin on the mobo) is moved to
> a case-fan connector on the mobo, it boots with no problem.
>
> While this was connected, I connected the original Intel HSF (4-pin) to
> the mobo's CPU-fan connector and although it still started fine the HSF
> connected to the CPU-fan mobo connector (not attached to the CPU) would
> only blip on every few seconds, never fully cranking up. I tried the
> same test with an old 478 P4 HSF with a 3-pin connector and it would
> blip once, then nothing. The 3-pin connector fits only one way with the
> guide on the mobo, so I assumed the 3-pin-connector HSF's would work.
>
> At this time it appears to function fine as long as the HSF is connected
> to a case-fan connector on the mobo, but these seems make-shift to me.
> What am I missing on this 4-pin CPU-fan connenctor issue?
>
I don't pretend to understand all the symptoms. It almost suggests
the motherboard has the ability to detect whether a four pin fan is
connected to the four pin header. Like they were sensing whether something
was connected to the PWM pin. Or maybe the 12V pin on the fan header,
has a traditional transistor connected to it for control (two
control methods, one digital, one analog) ? Maybe an analog
transistor for controlling the fan, is not getting fully
switched on (board defect) ?
Since you connected the original Intel four pin fan to the header, and
got some blips, that header may not be completely dead.
A test you can try, is go into the BIOS, while you're using the Intel
4 pin (and the real CPU cooler is connected to the case header), and check
the setting for "Smart Fan Control Method". The motherboard supports
a number of options, with an unclear explanation of what each one
does. I'd [Disable] that setting, since the description says "Forces
fan to run at full speed". That might tell you whether the header had
some basic function. See whether the fans behave properly after that.
(Always shutting down system power, before moving the fan connector - if the
fan connector is offset by one pin by accident, damage could result.)
The motherboard supports QST. The Southbridge has fan interface pins on it,
for driving PWM pins (pulse width modulation - a digital method for analog
control). Using PECI, the chipset can also access the CPU temp. And
implement automatic fan speed control. I believe people have
noticed the "blipping" behavior, most likely having something to do
with the microcontroller inside the chipset not being ready to control
the fan when the board starts up. Perhaps with the [Disable] setting,
you'll get a more traditional and reassuring response ?
The following is quoted from the ICH9 (Southbridge) datasheet:
"Intel Quiet System Technology (Intel QST)
The ICH9 integrates four fan speed sensors (four TACH signals) and 3 fan speed
controllers (three Pulse Width Modulator signals), which enables monitoring and
controlling up to four fans on the system. With the new implementation of the
singlewire Simple Serial Transport (SST) 1.0 bus and Platform Environmental
Control Interface (PECI), the ICH9 provides an easy way to connect to SST-based
thermal sensors and access the processor thermal data. In addition, coupled
with the new sophisticated fan speed control algorithms, Intel QST provides
effective thermal and acoustic management for the platform."
QST is part of a larger subsystem, fully implemented on some Intel "Executive"
motherboards. The P35 only has a fraction of the functions enabled. The Q35 enables
more than fan control. With a Q35 Northbridge, the motherboard can be
controlled remotely, without the main CPU running. The P35 doesn't allow that,
and the only function I'm aware of, is that fan control thing. The full set of
features in Q35 is called AMT, but just try and find documents that fully explain it...
Now, assuming the above tweak makes a difference, would I be happy about this ?
Consider if the BIOS ever gets reset (battery change, or another helpful person
resets the CMOS), then the user may be exposed to the same bad behavior when the
BIOS defaults are restored. So I don't know if I'd want to leave it in that state
(buggered, if the CMOS is reset). Your decision, whether it is worth trying an
RMA, as I'm not sure whether the symptoms are consistent with damage, or are
"normal" for this board.
"Bob Davis" <nospam@nospam.net> wrote in message
news:O4Hrj.47699$m6.37158@newsfe18.lga...
>A friend purchased a P35-DS3P mobo with two sticks of 1gb DDR2 RAM, a 3-pin
>Coolermaster HSF, and a PCI-E video card to upgrade an older P4 478 system
>in an ATX case. The PSU is a 480W Antec Truepower, and when everything is
>connected the only response is a quick flicker of the CPU fan--no POST, no
>PSU or case fans are spinning up, nothing. OTOH, when the CPU fan
>connector (3-pin on the HSF, 4-pin on the mobo) is moved to a case-fan
>connector on the mobo, it boots with no problem.
>
> While this was connected, I connected the original Intel HSF (4-pin) to
> the mobo's CPU-fan connector and although it still started fine the HSF
> connected to the CPU-fan mobo connector (not attached to the CPU) would
> only blip on every few seconds, never fully cranking up. I tried the same
> test with an old 478 P4 HSF with a 3-pin connector and it would blip once,
> then nothing. The 3-pin connector fits only one way with the guide on the
> mobo, so I assumed the 3-pin-connector HSF's would work.
>
> At this time it appears to function fine as long as the HSF is connected
> to a case-fan connector on the mobo, but these seems make-shift to me.
> What am I missing on this 4-pin CPU-fan connenctor issue?
>
I had a similar "problem" with the 4pin fan twitching and not starting on a
GA-P35-DS4 and it is just the bios detects that given the current
temperature the fan need only spin at some low speed which the fan cannot do
and therefore stays stopped. Once the cpu warms up a little (and this only
takes a very short time) the fan will spin normally as the PWM sets it to a
higher speed that it can actually spin at.
HTH
"Paul" <nospam@needed.com> wrote in message news:fons2c$1eg$1@aioe.org...
> I don't pretend to understand all the symptoms. It almost suggests
> the motherboard has the ability to detect whether a four pin fan is
> connected to the four pin header. Like they were sensing whether something
> was connected to the PWM pin. Or maybe the 12V pin on the fan header,
> has a traditional transistor connected to it for control (two
> control methods, one digital, one analog) ? Maybe an analog
> transistor for controlling the fan, is not getting fully
> switched on (board defect) ?
This is the second board, both of which having the same symptoms. At this
point I tend to think it is not two bad boards in a row.
> Since you connected the original Intel four pin fan to the header, and
> got some blips, that header may not be completely dead.
Could PWM have been sensing the CPU is cool and not switching on the fan?
> A test you can try, is go into the BIOS, while you're using the Intel
> 4 pin (and the real CPU cooler is connected to the case header), and check
> the setting for "Smart Fan Control Method".
I retained the Cooler Master HSF and changed the BIOS setting as suggested.
It booted fine and everything worked. Oddly, I changed it back to the
original setting and it still worked perfect. It's as if something awakened
it from the dead. It's installing XP now.
Thanks for all the feedback you provided. I'll pass all this along to the
owner.
Bob Davis wrote:
>
> "Paul" <nospam@needed.com> wrote in message news:fons2c$1eg$1@aioe.org...
>
>> I don't pretend to understand all the symptoms. It almost suggests
>> the motherboard has the ability to detect whether a four pin fan is
>> connected to the four pin header. Like they were sensing whether
>> something
>> was connected to the PWM pin. Or maybe the 12V pin on the fan header,
>> has a traditional transistor connected to it for control (two
>> control methods, one digital, one analog) ? Maybe an analog
>> transistor for controlling the fan, is not getting fully
>> switched on (board defect) ?
>
> This is the second board, both of which having the same symptoms. At
> this point I tend to think it is not two bad boards in a row.
>
>> Since you connected the original Intel four pin fan to the header, and
>> got some blips, that header may not be completely dead.
>
> Could PWM have been sensing the CPU is cool and not switching on the fan?
>
>> A test you can try, is go into the BIOS, while you're using the Intel
>> 4 pin (and the real CPU cooler is connected to the case header), and
>> check
>> the setting for "Smart Fan Control Method".
>
> I retained the Cooler Master HSF and changed the BIOS setting as
> suggested. It booted fine and everything worked. Oddly, I changed it
> back to the original setting and it still worked perfect. It's as if
> something awakened it from the dead. It's installing XP now.
>
> Thanks for all the feedback you provided. I'll pass all this along to
> the owner.
I suppose another possibility, would be something to do with the
CMOS settings. Maybe when you got the board, the CMOS settings
weren't at defaults. It is possible resetting the CMOS, might
have also awakened it.
If anything is strange about the whole thing, it is the decision
to use QST in the first place. I'm not sure, if I was designing
that motherboard, I would have done the same thing. The SuperI/O
chip probably has a duplicate functionality, and could just have
easily been hooked up. (Like previous generations of motherboards.)
Not every motherboard manufacturer has opted for QST. Sticking
with the SuperI/O means it is more likely that programs like
Speedfan could be used, without a lot of changes. And the hardware
monitor section of some SuperI/O chips has an automatic fan speed
control, which more or less gives the same function as QST. It
relies on using the CPU diode in the silicon (analog temp) rather
than reading the digital temp (PECI).
Somewhere along the way, did you update the BIOS ? That could
have played a part as well. Maybe later code did a better
job on the fan.
The erratic behavior of the fan, to me at least, suggests that
the microcontroller is not fully in control or something. Again, if
I was programming the thing, the first thing I'd do is set PWM to
100% (which can be achieved by not pulsing it, and should have
been the hardware default condition). One of the purposes of that,
is to get the fan spinning. So why the microcontroller
code would have immediately programmed it otherwise, is a bit
strange. This is not the only board to report that strange
behavior. (Maybe one of the Intel manufactured boards ? I don't
remember the details now.)
"Paul" <nospam@needed.com> wrote in message news:fooh3a$v5i$1@aioe.org...
> I suppose another possibility, would be something to do with the
> CMOS settings. Maybe when you got the board, the CMOS settings
> weren't at defaults. It is possible resetting the CMOS, might
> have also awakened it.
After connecting the HSF to the system-fan header to get it to POST, I
entered the BIOS and changed the "Smart fan" feature to disabled. I suppose
that save the BIOS might've had some effect, but keep in mind this was the
second mobo, the first having the same problem. After much deliberation we
thought the mobo was bad and returned it, and were dismayed the second had
the same problem.
> Somewhere along the way, did you update the BIOS ? That could
> have played a part as well. Maybe later code did a better
> job on the fan.
At first it had F6 installed, and I updated to F9 later on, much after I had
everything booting properly. Thus, I can't blame the older BIOS version.