slivercr wrote on 2020-06-03, 22:35:

[…]
Show full quote

1. EDIT: "AUX Fan" should be "NB Fan".
2. The changes you mentioned were correctly implemented
3. I can now see the frequencies for the x1950 Pro
4. RAM now shows as Single channel,
5. temperatures have the correct name, although I still don't know what that high temperature is (not reported in BIOS, see attached screenshot)
6. Weirdly enough, as I unplugged the Geforce2 MX the 12 V rail now reports a more credible voltage, in line with what the motherboard's own monitoring software reports.
7. Its an old Samsung TV with VGA input, model UN32C4000PD.
8. I have a couple other boards to test this on which should be more interesting for you.

1. Thank you for checking out the test SIV and I have changed the fan name
2. Good
3. Yes, but the code only used the default values, please rerun the test with the attached SIV32X V5.49 GPUs-06 test SIV.
4. Good
5. I suspect that it's not used on this motherboard so have made it "go away"
6. No, when I added MSI MS-7135 support I adjusted the scaling for VIN0 +12.
   1. May I have a screen shot of what the MSI utility reports.
   2. What locks does MSI utility use? From Menu->Windows->Processes Right/Click on the PID button and select Locks.
   3. Note: I expect the MSI software fails to use the Global\Access_ISABUS.HTP.Method lock so should in general not be used at the same time as SIV, see Menu->Help->Lock Handle to check.
   4. All of SIV + AIDA64 + CPUZ + HWM + … do use this lock so it should be OK to run them all at the same time.
7. SIV should now report Samsung UN32C4000PD
8. I look forward to seeing how SIV does on your other systems, what are they? Assuming they are running >= Windows XP you may as well use SIV32X V5.49 GPUs-06 on them.
9. I should have fixed [Windows] to report AMD Turion 64 ML-42 (Lancaster) [SH-E5] 2.40GHz Socket 754

red-ray wrote on 2020-06-04, 06:41:

[…]
Show full quote

1. Thank you for checking out the test SIV and I have changed the fan name
2. Good
3. Yes, but the code only used the default values, please rerun the test with the attached SIV32X V5.49 GPUs-06 test SIV.
4. Good
5. I suspect that it's not used on this motherboard so have made it "go away"
6. No, when I added MSI MS-7135 support I adjusted the scaling for VIN0 +12.
   1. May I have a screen shot of what the MSI utility reports.
   2. What locks does MSI utility use? From Menu->Windows->Processes Right/Click on the PID button and select Locks.
   3. Note: I expect the MSI software fails to use the Global\Access_ISABUS.HTP.Method lock so should in general not be used at the same time as SIV, see Menu->Help->Lock Handle to check.
   4. All of SIV + AIDA64 + CPUZ + HWM + … do use this lock so it should be OK to run them all at the same time.
7. SIV should now report Samsung UN32C4000PD
8. I look forward to seeing how SIV does on your other systems, what are they? Assuming they are running >= Windows XP you may as well use SIV32X V5.49 GPUs-06 on them.
9. I should have fixed [Windows] to report AMD Turion 64 ML-42 (Lancaster) [SH-E5] 2.40GHz Socket 754

Test of SIV32X V5.49 GPUs-06;

• Weird temperature no longer reported, and fan name changed to "NB Fan"
• Monitor reported by its model number
• GPU still shows default values, picture shows GPUZ info
  The attachment siv.jpg is no longer available
• Also just noticed CPU temperature reported on the left side different than the one reported on the right side
• Pictures of motherboard software and the locks (the "locks" screen seems, to me, indistinguishable from the "handles" screen)
  The attachment coreCenter.jpg is no longer available
  The attachment coreCenterLocks.jpg is no longer available
• Opening Menu->Help->Lock Handle revealed only SIV was using the aforementioned Global\Access_ISABUS.HTP.Method
• The other PC I want to run this program in is a dual P3 system with i840 chipset and RDRAM, but it uses Windows 2k—since OS<WinXP should I still use this version of the program to test?

Thanks!

slivercr wrote on 2020-06-04, 13:44:

[…]
Show full quote

1. GPU still shows default values, picture shows GPUZ infosiv.jpg
2. Also just noticed CPU temperature reported on the left side different than the one reported on the right side
3. The other PC I want to run this program in is a dual P3 system with i840 chipset and RDRAM, but it uses Windows 2k—since OS<WinXP should I still use this version of the program to test?

Thank you for all the testing and all looks OK apart from the GPU.

1. SIV got further as such as Size @ 00F8 00000000 Type @ 0158 00000000 are now there, so I made some progress. I will try again when the X1650 Pro I got on eBay a few days ago arrives here.
2. The CPU temperature on the left is read from the MCH and is renowned for being questionable on early AMD64 CPUs. If you create TjOff Override as a DWORD of around 25 in HKCU\Software\SIV then SIV will add it's value to the reported value from the hardware.
3. SIV32X will run on W2K, but the tooltips don't work and I can't figure out why so it's better to use SIV32L. SIV has support for the 840 chipset so should do OK, but depending on what the motherboard is I may need to adjust the sensor reporting.

Tested SIV64X on the EVGA Z370 Micro rig in my sig.

12V is missing and it's reporting that the DDR4 voltage is 2.5v instead of 1.35v.

mastergamma12 wrote on 2020-06-04, 23:54:

12V is missing and it's reporting that the DDR4 voltage is 2.5v instead of 1.35v.

Thank you for checking out SIV and it looks like I need to adjust the Fintek F71889A SIO mappings and there is also a Nuvoton NCT7802Y SIO which I needed to add.

The attached SIV64X V5.49 EVGA-06 test SIV should do better, does it? To further improve it I need you to post one screen shot containing both the SIV Menu->Hardware->Sensor Debug panel and the EVGA reporting utility monitoring tab so that I can deduce which SIO input represents what. Please can you also check that the fan names are now correct.

Does the EVGA utility use the Global\Access_ISABUS.HTP.Method + Global\Access_SMBUS.HTP.Method locks? See 6.b. + 6.c. in my earlier post for how I would check.

red-ray wrote on 2020-06-05, 08:28:

Thank you for checking out SIV and it looks like I need to adjust the Fintek F71889A SIO mappings and there is also a Nuvoton NC […]
Show full quote

mastergamma12 wrote on 2020-06-04, 23:54:

12V is missing and it's reporting that the DDR4 voltage is 2.5v instead of 1.35v.

Thank you for checking out SIV and it looks like I need to adjust the Fintek F71889A SIO mappings and there is also a Nuvoton NCT7802Y SIO which I needed to add.

The attached SIV64X V5.49 EVGA-06 test SIV should do better, does it? To further improve it I need you to post one screen shot containing both the SIV Menu->Hardware->Sensor Debug panel and the EVGA reporting utility monitoring tab so that I can deduce which SIO input represents what. Please can you also check that the fan names are now correct.

Does the EVGA utility use the Global\Access_ISABUS.HTP.Method + Global\Access_SMBUS.HTP.Method locks? See 6.b. + 6.c. in my earlier post for how I would check.

Looks a lot better.

mastergamma12 wrote on 2020-06-05, 16:26:

red-ray wrote on 2020-06-05, 08:28:

To further improve it I need you to post one screen shot containing both the SIV Menu->Hardware->Sensor Debug panel and the EVGA reporting utility monitoring tab so that I can deduce which SIO input represents what. Please can you also check that the fan names are now correct.

Does the EVGA utility use the Global\Access_ISABUS.HTP.Method + Global\Access_SMBUS.HTP.Method locks? See 6.b. + 6.c. in my earlier post for how I would check.

Looks a lot better.

Thank you, but what about the fan names and having the EVGA reporting utility monitoring tab in the screen shot?

Looking in the manual I can see what it reports, but the actual values on your system will be different.

slivercr wrote on 2020-06-04, 13:44:

GPU still shows default values, picture shows GPUZ infosiv.jpg

I suspect I have fixed the GPU reporting, please try the attached SIV32X V5.49 R500-06 test SIV and post new save files.

I noticed your posts about your QuForce FX 5800, am wondering what SIV makes of it and if SIV will report it fake GPU on Menu->Machine->GPU Info, what does it report?

Looks like SIO A = VCCIO, SIO C = VCCSA and SIO D = VDDR

No idea on SIO B

Also tested that build on my HTPC rig with a EVGA Z390 FTW as it has the same SuperI/O controller and the vdddr and 12v voltage was wrong like it was on the Z370 Micro before.

mastergamma12 wrote on 2020-06-05, 23:15:

Looks like SIO A = VCCIO, SIO C = VCCSA and SIO D = VDDR VCCST. No idea on SIO B

Thank you for the screen shots and as the raw value for SIO B is 0x03FF I expect it's not used so have removed it for the Z370, on the Z390 it's 1.240 volts and I wonder what it is.

Please try the attached SIV64X V5.49 Z370-06 test SIV on both systems and post a screen shot for the Z390 FTW showing both the SIV and EVGA information so I can confirm it should use the same mappings as the Z370.

Are the all fan names now correct? I can tell they are when a fan is connected, but not the ones reporting 0 RPM.

red-ray wrote on 2020-06-05, 19:50:

slivercr wrote on 2020-06-04, 13:44:

GPU still shows default values, picture shows GPUZ infosiv.jpg

I suspect I have fixed the GPU reporting, please try the attached SIV32X V5.49 R500-06 test SIV and post new save files.
...

Success!

red-ray wrote on 2020-06-05, 19:50:

...
I noticed your posts about your QuForce FX 5800, am wondering what SIV makes of it and if SIV will report it fake GPU on Menu->Machine->GPU Info, what does it report?

This will have to wait quite a while, most of my things are in storage at the moment (relocating across the ocean has downsides). There are a few users that modified their cards, though, so if you ask for help in that thread more people (with interesting systems of their own) may be able to help out.

Thanks for the continued support with SIV, it has quickly become a favorite of mine!

slivercr wrote on 2020-06-06, 14:41:

Success!

Thank you for checking this out as I can now release this code in Beta-06 which I plan to release once the EVGA Z370 + Z390 sensor reporting has been adjusted.

I suspect if you put the X1950 Pro in a >= Windows 7 system SIV will also report the Utilisation % and Frame Buffer Usage as it did for my Sapphire Radeon X1650 Pro, it might also work on Vista.

Z370 Micro

Z390 FTW

Fans should be correct now.

mastergamma12 wrote on 2020-06-06, 17:37:

Z370 Micro + Z390 FTW Fans should be correct now.

Thank you, I feel SIV now does OK on both boards, do you feel I need to make any more adjustments and if so what?

On the Z370 I spotted "[Y]INUSE Wait 812 of 812 ms" when the 812 should be 0. What happens when you select the check box? It should get reset to 0, does it? It being none zero means some software is accessing the SMBus and failing to release the INUSE Wait hardware semaphore which SIV timed out after 812 ms.

red-ray wrote on 2020-06-06, 18:07:

mastergamma12 wrote on 2020-06-06, 17:37:

Z370 Micro + Z390 FTW Fans should be correct now.

Thank you, I feel SIV now does OK on both boards, do you feel I need to make any more adjustments and if so what?

On the Z370 I spotted "[Y]INUSE Wait 812 of 812 ms" when the 812 should be 0. What happens when you select the check box? It should get reset to 0, does it? It being none zero means some software is accessing the SMBus and failing to release the INUSE Wait hardware semaphore which SIV timed out after 812 ms.

Looks good and it does.

mastergamma12 wrote on 2020-06-06, 18:42:

Looks good and it does.

OK I have just uploaded the SIV 5.49 Beta-06s so please use this rather than the test SIVs.

I wonder what has suboptimal INUSE Wait code, given once you reset the timeout it does not return maybe it's the BIOS SPD reading code. BTW Beta-06 should display INUSE Wait 812 of 812 ms in red so it's easier to spot.

So I tried SIV 5.49 Beta-06s on my laptop which is a Dell Insprion 5593 with a 1065g7 and it thinks it's triple channel instead of dual channel.

mastergamma12 wrote on 2020-06-07, 07:25:

So I tried SIV 5.49 Beta-06 on my laptop which is a Dell Insprion 5593 with a 1065g7 and it thinks it's triple channel instead of dual channel.

Thank you for the report and this was rather unexpected as I have a friend who also has a Dell 5593 and SIV reports the channels on that correctly. I wonder if this is down to his having BIOS 1.5.0 12/17/2019 and you having BIOS 1.4.0 12/11/2019.

Either way I suspect I have fixed this in the attached SIV64X V5.49 Dual-07 test SIV, have I?

Did you do anything special to get the RAM running @ 2.66 GHz? On the other system it's only @ 2.13 GHz when the DIMMs are capable of 2.66 GHz.

red-ray wrote on 2020-06-07, 07:59:

Thank you for the report and this was rather unexpected as I have a friend who also has a Dell 5593 and SIV reports the channels […]
Show full quote

mastergamma12 wrote on 2020-06-07, 07:25:

So I tried SIV 5.49 Beta-06 on my laptop which is a Dell Insprion 5593 with a 1065g7 and it thinks it's triple channel instead of dual channel.

Thank you for the report and this was rather unexpected as I have a friend who also has a Dell 5593 and SIV reports the channels on that correctly. I wonder if this is down to his having BIOS 1.5.0 12/17/2019 and you having BIOS 1.4.0 12/11/2019.

Either way I suspect I have fixed this in the attached SIV64X V5.49 Dual-07 test SIV, have I?

Did you do anything special to get the RAM running @ 2.66 GHz? On the other system it's only @ 2.13 GHz when the DIMMs are capable of 2.66 GHz.

Looks good now, as for the 2666mhz ram running at 2666mhz, it was like that when I bought it.