View Issue Details

IDProjectCategoryView StatusLast Update
0001295SpeedFanFan controlpublic2009-08-10 15:05
ReporterdiscostuAssigned Toalfredo 
PrioritynormalSeverityminorReproducibilityalways
Status acknowledgedResolutionopen 
PlatformAbit NF7-S v2.0OSWindows XP ProfessionalOS Version2002 SP3
Product Version4.36 
Target VersionFixed in Version 
Summary0001295: Fan control for Asus V9999 no longer works in version 4.36
DescriptionHello Alfredo,

I would like to report a regression in Speedfan v4.36.

Using Speedfan v4.35 (and earlier), I am able to control the fan speed of my Asus V9999 (Geforce 6800) graphics card with an F75375S controller chip. Very nice feature, because the fan is pretty loud at full speed.
Unfortunately with Speedfan v4.36, it is no longer possible to change the V9999 fan speed. If I try to change the speed manually using the spin buttons, the output window displays an error message (unable to write to port $2E).
Steps To Reproduce- Install Speedfan v4.36 on system with Asus V9999
- Change V9999 fan speed using spin button
=> The speed does not change, Speedfan displays error message

Additional InformationAsus V9999 fan control is working in Speedfan v4.35
TagsV9999
Motherboard Model
Video Card ModelAsus V9999 (nVidia GeForce 6800, F75375S at SMBUS $2E)

Relationships

related to 0001341 resolvedalfredo Speedfan may freeze in automatic mode causing 100% CPU usage 
related to 0001337 resolvedalfredo GPU temperature stays at 0 for asus EN8800GT 1GB 

Activities

ul7ra

2009-01-14 17:23

reporter   ~0004360

Last edited: 2009-01-14 17:25

I'm having the same issue. In 4.35, adjusting fan speed of my ASUS V9999 (Geforce 6800) worked perfectly. The latest version I tried (4.37), however, reports the error posted above when trying to change fan speed. Nonetheless, it seems that the fan controller chip (Fintek F75375S) is being recognized correctly.
(I only posted this note in order to show that it might not be a problem of one individual.)

discostu

2009-02-08 17:26

reporter   ~0004398

Hello Alfredo,

for your information, this issue still occurs in SpeedFan 4.37, i.e. the V9999 card is not detected. See this associated issue for more information:
http://www.bugtrack.almico.com/view.php?id=1341

alfredo

2009-02-16 10:10

manager   ~0004473

I'm not sure I fully understood the actual issue here. Please help me.
There are two possible versions:
1) the Fintek chip on the video card IS found by SpeedFan, fan speed controls are on the main window, but when you try to change the fan speed you get an error message;
2) the Fintek chip IS NOT found by SpeedFan.
If the issue is (1) then you're lucky because I just need to figure out how to WRITE to an I2C device. I might add this in 4.38.
If the issue is (2) then things are a little bit more difficult because it seems that, although I'm using official nVidia routines to access the I2C on the video card, on some cards some chips are not found by SpeedFan. Unfortunately the official documentation is not very clear and I had to buy some hardware and perform a lot of testing to figure out how to set parameters.

discostu

2009-02-16 20:13

reporter   ~0004477

Hello Alfredo,

thank you very much for looking into this issue. I greatly appreciate the time and resources you have poured into this wonderful essential windows utility. Being a developer myself, I must say that Speedfan has proved to be far more stable than much of my own code... ;p Not to mention that I wouldn't dare to burn my fingers on anything happening in kernel space.

To answer your question, the actual problem seems to be like described in situation (2): The Fintek chip is not found by Speedfan. I have recently upgraded to Speedfan v4.37. Upon start up, the program displays the following output:

Win9x:NO 64Bit:NO GiveIO:YES SpeedFan:YES
Found nVidia GeForce 6800
Scanning ISA BUS at $0290...
F71882F check found $FF $FF $11 $01 $FF
Winbond W83627HF (ID=$21) found on ISA at $290
SuperIO Chip=Winbond W83627HF
Scanning nForce2 SMBus at $5000...
Scanning nForce2 SMBus at $5100...
Scanning I2CNVidia SMBus at $3D403E3F...
Address $2D appears to be WRITE ONLY...
Address $2E appears to be WRITE ONLY...
Address $48 appears to be WRITE ONLY...
Address $49 appears to be WRITE ONLY...
Address $4C appears to be WRITE ONLY...
Address $50 appears to be WRITE ONLY...
Scanning I2CNVidia SMBus at $3D403637...
Address $2D appears to be WRITE ONLY...
Address $2E appears to be WRITE ONLY...
Address $48 appears to be WRITE ONLY...
Address $49 appears to be WRITE ONLY...
Address $4C appears to be WRITE ONLY...
Address $50 appears to be WRITE ONLY...
Scanning I2CNVidia SMBus at $3D405051...
Address $2D appears to be WRITE ONLY...
Address $2E appears to be WRITE ONLY...
Address $48 appears to be WRITE ONLY...
Address $49 appears to be WRITE ONLY...
Address $4C appears to be WRITE ONLY...
Found ACPI temperature (41.5C)
Loaded 0 events

Note that the log mentions the "F71882F" chip, however the Asus V9999 graphics card actually uses a Fintek F75375S. Older versions of Speedfan (<4.36) detected this chip at offset $3D405051, as seen in a backup configuration file "speedfansens.cfg":
...=F75375S@$2E(onSMBusI2CNVidia@$3D405051)
The above line from the old config file mentions address $2E, but the log output displays:
  Scanning I2CNVidia SMBus at $3D405051...
  ...
  Address $2E appears to be WRITE ONLY...

Regarding the mentioned erratic behavior for v4.36, I think this was probably caused because when I upgraded from v4.35 to v4.36 I left the old (v4.35) configuration files intact; so Speedfan v4.36 used the old configuration files, displayed the associated fan speed UI controls and tried to reach the F75375S chip at the configured address - unsuccessfully.
When I recently upgraded to v4.37, I moved the existing configuration files to a backup folder in order to create a fresh configuration from scratch. Because Speedfan v4.37 apparently does not detect the F75375S chip by itself, the associated V9999 fan speed controls are no longer displayed in the main window.

I am currently using the nVidia GeForce driver version 185.20. In the recent months I have upgraded the graphics driver a couple of times. So it may be possible that the newer nVidia drivers cause this issue. However RivaTuner is able to monitor the F75375S for all the new driver versions, as mentioned in issue http://www.bugtrack.almico.com/view.php?id=1341.

Looking at the long and growing issue list I fully understand that you must prioritize. And eventually this problem will solve itself when I buy some new hardware. So if the NVAPI proves to be the way of the future, then please do take Speedfan there. In any case, keep up the good work!

Best regards,

Zef

ul7ra

2009-02-16 23:13

reporter   ~0004480

Last edited: 2009-02-16 23:22

For me it seems to detect the F75375S correctly. Even reading temperatures, fan speed and the currently set fanspeed (which I currently change by using Atitool) works correctly. It says:

Win9x:NO 64Bit:NO GiveIO:YES SpeedFan:YES
Found nVidia GeForce 6800
Scanning ISA BUS at $0290...
F71882F check found $09 $03 $11 $00 $FF
Winbond W83627THF (ID=$90) found on ISA at $290
SuperIO Chip=Winbond W83627THF
Scanning Intel SMBus at $0400...
LM75 found on SMBus at $48
LM75 found on SMBus at $49
Scanning I2CNVidia SMBus at $3D403E3F...
F75375S found on SMBus at $2E
Scanning I2CNVidia SMBus at $3D403637...
Scanning I2CNVidia SMBus at $3D405051...
SMART Enabled for drive 0
Found ST3300620A (300.1GB)
SMART Enabled for drive 1
Found ST3750640AS (750.2GB)
Loaded 0 events
SMBus msg : 23:11:01.953 Unsuccessful WRITEB $76 to $2E
SMBus msg : 23:11:02.781 Unsuccessful WRITEB $76 to $2E

The last two lines represent the output when trying to change fan speed or the chip's config. Maybe a faulty offset for writing on the I

alfredo

2009-02-17 02:39

manager   ~0004481

According to ul7ra, the Fintek chip can be found. The "Unsuccessful WRITEB" derives from the fact that I haven't implemented I2C writes.
Tomorrow I will create a beta. If you want to try it, please contact me by email (alfredo [at] almico.com) using an email address not on Gmail, because I will send you a zipped exe.

alfredo

2009-02-19 09:51

manager   ~0004497

Last edited: 2009-02-19 09:52

I received two reports using the latest SpeedFan 4.38 beta 11.3.
One of them detects the Fintek chip. The other one doesn't.
The video card where the Fintek chip is available is:
  Video card is nVidia GeForce 6800
  <ASUS V9999 VGA BIOS Version 5.40.02.15.AS07>
  <Version 5.40.02.15.00>
  <Copyright (C) 1996-2004 NVIDIA Corp.>
  <NVIDIA>
  <NVIDIA Corporation>
  <nv40 Board - p212-0>
  <Chip Rev>


The other video card is:
  Video card is nVidia GeForce 6800
  <ASUS V9999 VGA BIOS Version 5.40.02.15.AS07>
  <Version 5.40.02.15.00>
  <Copyright (C) 1996-2004 NVIDIA Corp.>
  <NVIDIA>
  <NVIDIA Corporation>
  <nv40 Board - p212-0>
  <Chip Rev>

The pc where the Fintek chip is detected uses the following nVidia driver:
  DrvVer=16371 BldChangeListNum=2025132 Branch=R163_60-8748

The other pc uses the following nVidia driver:
  DrvVer=18520 BldChangeListNum=3280500 Branch=r185_00-9901

The pc where the Fintek chip has the following OS:
  Windows NT Multiprocessor Free version 5.1.2600 (Windows XP)

The other pc has the following OS:
  Windows NT Uniprocessor Free version 5.1.2600 (Windows XP)

The only difference I can see is the nVidia driver version. The ultimate test would be to update the driver on the pc where the Fintek chip is detected and see if it still is, but I would do it only if I have a copy of the driver that is known to work.

discostu

2009-02-19 22:09

reporter   ~0004500

Hello Alfredo,

it occurred to me before that the problem may be driver related. The system comparison above also seems to point in this direction. But I'm a bit reluctant to roll back the graphics driver, as the system runs smooth otherwise and I need it frequently.

But also I find it quite strange that the problem only occurs with Speedfan. I retested with both RivaTuner 2.23 and Everest 3.50. Those applications seem not to be affected by the recent 185.20 graphics driver at all, as they are able to display extended V9999 readings, including temperatures.

Could this be explained because these programs do not use NVAPI, as Speedfan does since v4.36?

discostu

2009-02-19 22:46

reporter   ~0004501

Last edited: 2009-02-19 22:49

Hello Alfredo,

I did some more testing. SpeedFan v4.35 detects the F75375S just fine. Here are a couple of lines from the debug.nfo:

19 Feb 09 22:37:37 - Probing LINK <SMBusI2CNVidia@$3D405051> at address $002E...
19 Feb 09 22:37:37 - Probe 0000012 done on LINK <SMBusI2CNVidia@$3D405051> at address $002E...
19 Feb 09 22:37:37 - Probe 0000014 done on LINK <SMBusI2CNVidia@$3D405051> at address $002E...
19 Feb 09 22:37:37 - Probe 0000015 done on LINK <SMBusI2CNVidia@$3D405051> at address $002E...
19 Feb 09 22:37:37 - FOUND F75375S at $002E
19 Feb 09 22:37:37 - Probe 0000016 done on LINK <SMBusI2CNVidia@$3D405051> at address $002E...
19 Feb 09 22:37:37 - Probing ended on LINK <SMBusI2CNVidia@$3D405051> at address $002E...

Compare this with debug.nfo from latest Speedfan (4.38 beta 11.3):

19 Feb 09 22:42:48 - WARN: won't probe address $2C on <SMBusI2CNVidia@$3D405051>
19 Feb 09 22:42:48 - LINK <SMBusI2CNVidia@$3D405051> at address $002D appears to be unused...
19 Feb 09 22:42:48 - LINK <SMBusI2CNVidia@$3D405051> at address $002E appears to be unused...
19 Feb 09 22:42:48 - WARN: won't probe address $2F on <SMBusI2CNVidia@$3D405051>
...
19 Feb 09 22:42:48 - WARN: won't probe address $4F on <SMBusI2CNVidia@$3D405051>
19 Feb 09 22:42:48 - Probing LINK <SMBusI2CNVidia@$3D405051> at address $0050...
19 Feb 09 22:42:48 - Probe #1 done on LINK <SMBusI2CNVidia@$3D405051> at address $0050...
19 Feb 09 22:42:48 - Probe 0000047 done on LINK <SMBusI2CNVidia@$3D405051> at address $0050...
19 Feb 09 22:42:48 - Probe 0000049 done on LINK <SMBusI2CNVidia@$3D405051> at address $0050...
19 Feb 09 22:42:48 - Probing ended on LINK <SMBusI2CNVidia@$3D405051> at address $0050...
19 Feb 09 22:42:48 - WARN: won't probe address $58 on <SMBusI2CNVidia@$3D405051>
...

Address $2E is not detected ("unused"). Address $50 is probed but nothing is found. SpeedFan v4.35 doesn't probe $50.

Greetings,

Zef

ul7ra

2009-02-20 13:59

reporter   ~0004504

I installed the latest nvidia driver and, indeed, speedfan doesn't detect the Fintek chip anymore.

Here's a short bit from speedfans status textbox:

Win9x:NO 64Bit:NO GiveIO:YES SpeedFan:YES
Found nVidia GeForce 6800
Scanning ISA BUS at $0290...
Winbond W83627THF (ID=$90) found on ISA at $290
SuperIO Chip=Winbond W83627THF
Scanning Intel SMBus at $0400...
LM75 found on SMBus at $48
LM75 found on SMBus at $49
Scanning I2CNVidia SMBus at $3D403E3F...
Address $2D appears to be WRITE ONLY...
Address $2E appears to be WRITE ONLY...
Address $48 appears to be WRITE ONLY...
Address $49 appears to be WRITE ONLY...
Address $4C appears to be WRITE ONLY...
Address $50 appears to be WRITE ONLY...
Scanning I2CNVidia SMBus at $3D403637...
Scanning I2CNVidia SMBus at $3D405051...

I'm now having the exact same problem as discotu in post 4477. Fortunately, I made a driver backup.

sbchen

2009-02-22 02:35

reporter   ~0004517

got a similar problem here with my gigabyte 6800 GT (GV-N68T256DH).

speedfan can just adjust the fan speed when NO nvidia driver is installed

speedfan bootup log with no nvidia driver installed:
Win9x:NO 64Bit:NO GiveIO:YES SpeedFan:YES
I/O properly initialized
Linked ISA BUS at $0290
Linked VIA VT8237 SMBUS at $0400
Found nVidia GeForce 6800 GT
Linked nVidiaI2C0 SMBUS at $3D403E3F
Linked nVidiaI2C1 SMBUS at $3D403637
Linked nVidiaI2C2 SMBUS at $3D405051
Scanning ISA BUS at $0290...
Winbond W83627THF (ID=$90) found on ISA at $290
SuperIO Chip=Winbond W83627THF
Scanning VIA SMBus at $0400...
Scanning I2CNVidia SMBus at $3D403E3F...
Address $2D appears to be WRITE ONLY...
Address $2E appears to be WRITE ONLY...
Address $48 appears to be WRITE ONLY...
Address $49 appears to be WRITE ONLY...
Address $4C appears to be WRITE ONLY...
Scanning I2CNVidia SMBus at $3D403637...
Address $2D appears to be WRITE ONLY...
Address $2E appears to be WRITE ONLY...
Address $48 appears to be WRITE ONLY...
Address $49 appears to be WRITE ONLY...
Address $4C appears to be WRITE ONLY...
Scanning I2CNVidia SMBus at $3D405051...
Winbond W83L785R (ID=$60) found on SMBus at $2D
Address $2E appears to be WRITE ONLY...
Address $48 appears to be WRITE ONLY...
Address $49 appears to be WRITE ONLY...
Address $4C appears to be WRITE ONLY...
Found Maxtor 6L250R0 (251,0GB)
Found SAMSUNG SP1203N (120,1GB)
End of detection
Loaded 0 events

with geforce driver 182.06 (current) it doesn't even detect the card.. it finds the nvidia smbus but does not find any information there:

Win9x:NO 64Bit:NO GiveIO:YES SpeedFan:YES
I/O properly initialized
Linked ISA BUS at $0290
Linked VIA VT8237 SMBUS at $0400
Found nVidia GeForce 6800 GT
Linked nVidiaI2C0 SMBUS at $3D403E3F
Linked nVidiaI2C1 SMBUS at $3D403637
Linked nVidiaI2C2 SMBUS at $3D405051
Scanning ISA BUS at $0290...
Winbond W83627THF (ID=$90) found on ISA at $290
SuperIO Chip=Winbond W83627THF
Scanning VIA SMBus at $0400...
Scanning I2CNVidia SMBus at $3D403E3F...
Address $2D appears to be WRITE ONLY...
Address $2E appears to be WRITE ONLY...
Address $48 appears to be WRITE ONLY...
Address $49 appears to be WRITE ONLY...
Address $4C appears to be WRITE ONLY...
Address $50 appears to be WRITE ONLY...
Scanning I2CNVidia SMBus at $3D403637...
Scanning I2CNVidia SMBus at $3D405051...
Found Maxtor 6L250R0 (251,0GB)
Found SAMSUNG SP1203N (120,1GB)
End of detection
Loaded 0 events

with geforce driver 175.19 (used that for months now) it gives the above mentioned unsuccessful write messages:

Win9x:NO 64Bit:NO GiveIO:YES SpeedFan:YES
I/O properly initialized
Linked ISA BUS at $0290
Linked VIA VT8237 SMBUS at $0400
Found nVidia GeForce 6800 GT
Linked nVidiaI2C0 SMBUS at $3D403E3F
Linked nVidiaI2C1 SMBUS at $3D403637
Linked nVidiaI2C2 SMBUS at $3D405051
Scanning ISA BUS at $0290...
Winbond W83627THF (ID=$90) found on ISA at $290
SuperIO Chip=Winbond W83627THF
Scanning VIA SMBus at $0400...
Scanning I2CNVidia SMBus at $3D403E3F...
Winbond W83L785R (ID=$60) found on SMBus at $2D
SMBus msg : 02:32:49.843 Unsuccessful WRITEB $4E to $2D
SMBus msg : 02:32:49.843 Unsuccessful WRITEB $4E to $2D
SMBus msg : 02:32:49.843 Unsuccessful WRITEB $4E to $2D
SMBus msg : 02:32:49.843 Unsuccessful WRITEB $4E to $2D
Scanning I2CNVidia SMBus at $3D403637...
Scanning I2CNVidia SMBus at $3D405051...
Found Maxtor 6L250R0 (251,0GB)
Found SAMSUNG SP1203N (120,1GB)
End of detection
Loaded 0 events

when I manually try to change the speed I get:
SMBus msg : 02:33:45.718 Unsuccessful WRITEB $81 to $2D
SMBus msg : 02:33:45.718 Unsuccessful WRITEB $81 to $2D
SMBus msg : 02:33:45.718 Unsuccessful WRITEB $81 to $2D
SMBus msg : 02:33:45.718 Unsuccessful WRITEB $81 to $2D
SMBus msg : 02:33:45.828 Unsuccessful WRITEB $81 to $2D
SMBus msg : 02:33:45.828 Unsuccessful WRITEB $81 to $2D

now the funny party:

using the original gigabyte tool, i can select 3 fan-modes with ANY driver... but they are only "fast, faster, fastest" (useless)

alfredo

2009-02-22 10:01

manager   ~0004518

@ul7ra
I do really appreciate your patience. I hope you could revert to the previous driver. Now this tells me that some driver releases hide some devices on the bus.

@sbchen
Could you use the SEND REPORT (INFO tab) facility adding a few notes to each report?
I will work on the "Unsuccessful WRITEB" with SpeedFan 4.39.

DrVerdi

2009-05-19 09:44

reporter   ~0004787

Alfredo
may i ask you, if there will be a solution for the ASUS V9999 cards in a future versions of speedfan?
I am using your really great piece of software for a long time now, but i cannot understand, why the versions 4.35 and older are working fine with this card and the newer versions from 4.36 will not.
In my case with the newest Nvidia driver speedfan is working fine until version 4.35 with higher versions temperature sensor of my card is not recognized.

So i think it is not only a problem of the Nvidia drviver version it is also a problem of speedfan software.
Please can you have a closer look at this issue?

Thank you very much
Franz

Flo

2009-08-10 15:05

reporter   ~0004921

Any news on this issue? I'm also stuck with 4.35 on two systems containing two different V9999 cards (an LE and a GT).

If there's any additional information that could help you track down the problem, please tell us.

Issue History

Date Modified Username Field Change
2008-11-13 23:54 discostu New Issue
2008-11-13 23:54 discostu Status new => assigned
2008-11-13 23:54 discostu Assigned To => alfredo
2008-11-13 23:54 discostu Video Card Model => Asus V9999 (nVidia GeForce 6800, F75375S at SMBUS $2E)
2009-01-14 17:23 ul7ra Note Added: 0004360
2009-01-14 17:24 ul7ra Note Edited: 0004360
2009-01-14 17:25 ul7ra Note Edited: 0004360
2009-01-26 11:22 discostu Tag Attached: V9999
2009-02-08 17:26 discostu Note Added: 0004398
2009-02-16 10:05 alfredo Relationship added related to 0001341
2009-02-16 10:05 alfredo Status assigned => acknowledged
2009-02-16 10:10 alfredo Note Added: 0004473
2009-02-16 10:14 alfredo Relationship added related to 0001337
2009-02-16 20:13 discostu Note Added: 0004477
2009-02-16 23:13 ul7ra Note Added: 0004480
2009-02-16 23:13 ul7ra Note Edited: 0004480
2009-02-16 23:14 ul7ra Note Edited: 0004480
2009-02-16 23:19 ul7ra Note Edited: 0004480
2009-02-16 23:22 ul7ra Note Edited: 0004480
2009-02-17 02:39 alfredo Note Added: 0004481
2009-02-19 09:51 alfredo Note Added: 0004497
2009-02-19 09:52 alfredo Note Edited: 0004497
2009-02-19 22:09 discostu Note Added: 0004500
2009-02-19 22:46 discostu Note Added: 0004501
2009-02-19 22:49 discostu Note Edited: 0004501
2009-02-20 13:59 ul7ra Note Added: 0004504
2009-02-22 02:35 sbchen Note Added: 0004517
2009-02-22 10:01 alfredo Note Added: 0004518
2009-05-19 09:44 DrVerdi Note Added: 0004787
2009-08-10 15:05 Flo Note Added: 0004921