|
|
I just sent you a beta. |
|
|
Report sent. |
|
|
Try to enable Q-Fan, then use SpeedFan to change PWM MODE to SOFTWARE CONTROLLED. Does it work now? |
|
|
Tried this, but I'm afraid changing the speed percentages still doesn't work. I connected a 4-pin fan to the 4-pin CHA1 connector and a 3-pin fan to the 3-pin CHA2 connector on the mobo. Chassis Q-Fan control enabled in BIOS, set to Silent profile. Starting SpeedFan. I haven't ticked the "remember it" box under PWM mode values in Advanced, cause I want to see their behavior. BIOS has set PWM 3 mode to SmartGuardian. I'm setting it to Software controlled. What happens then is that the fans slow down even more. At boot, Fan1/Fan2 ran at about 1500/1600 RPM, and slowed to about 1200/1400 RPM when I set Software controlled. After some testing, it now appears to me that by setting Software controlled, fans run at the cycle which is defined as "minimum duty cycle" under the selected Q-Fan profile in BIOS, something which is supposed to occur only if the MB temperature drops below 20 |
|
|
Just wondering, do you consider this a bug or something not supported? |
|
|
IT87xx chips are supported very well by SpeedFan. What I'm not sure about is if you tried to change fan speeds manually using SpeedFan's main screen controls or if you just waited for SpeedFan to change their speed. |
|
|
I have done most of the testing by changing the speeds manually. I have also adjusted the temperature thresholds to make SpeedFan auto-adjust the speed percentages. Strange, because from what you tell it sounds like this isn't an issue related to SpeedFan. That puzzles me, because it's a quite clean setup. Thank you for your support. Please let me know if you have any bright troubleshooting ideas :-) |
|
|
I'm assuming it is a setup error. Please only use a 3pin-fan directly attached to the motherboard for testing. Where exactly have you attached the fan? Usually on Asus motherboards one of the speed settings controls all CHA_FANs at the same time and applies the same voltage. If I remember correctly, Q-Fan schould be enabled an in normal mode. |
|
|
Ok, now I have a 3-pin fan attached (directly) to the CHA_FAN2 connector. No other fans. The CHA_FAN1 connector has a 4-pin connector. Same results. If I install Asus FanExpert this will control the fan. As for Q-Fan, there is no "normal mode". The selectable profiles are: Disabled, Performance, Optimal, Silent, and Manual. I've tried them all. If I at some point let FanExpert or Q-Fan control the fan, PWM mode values have been altered when I look them up in SpeedFan's Advanced pane. This makes sense, but the strange thing is that setting them to Software controlled will simply slow the fan down and leave it at an RPM rate unaffected by SpeedFan's speed settings, as described a few posts back (0005236). |
|
|
I would also greatly appreciate if anyone with the same motherboard is reading this could confirm if they experience the same problem or not. |
|
2010-05-06 00:24
|
Advanced Pane.png (142,778 bytes) |
|
|
I have this mobo, and the same problem, but I'm using SpeedFan 4.42. When PWM mode is set to either ON/OFF, the fan ramps up, and stays up. Anything I have thought to try doesn't bring the fan speed back down, exect for changing PWM mode to either Software Controlled or SmartGuardian. When either of these is selected, I can't bring the speed up, it seems fixed in both cases. Also, the Silent, Standard, and Turbo modes don't quickly enough bring the fan's speed up, so I can't use those. The manual mode in BIOS doesn't work like it should. It seems to detect what temp the CPU is at during boot, decides which duty cycle that fits in, changes the fan's speed, and then locks it in place. If the CPU's temp changes later while the computer is on, the fan stays the course, it won't speed up or slow down. Asus's AI FanXpert is the only thing I've tried so far that works. I hope this confirmation of the problem helps. |
|
|
Please, upload the output of SEND REPORT (INFO tab). It would be great if you could use SpeedFan 4.43 beta 10. |
|
|
2 reports sent. One for 4.42, one for 4.43 beta 10. |
|
|
This issue is fixed. |
- Anonymous
