Jump to content

Winbond/Nuvoton monitor


Slice
 Share

170 posts in this topic

Recommended Posts

  1. How do I hide my serial number and other private info when I do an IO dump?
  2. I modified the default plist but get no fan speeds.  Should I create another node based on your board?
  3. If I do that, how do I get the board name it uses to match on boot?
  4. Is there a way to reload the kext while rebooting?
  5. HWMonitor seems to crash after a short period.  When this happens the machine will sleep.
  6. If its an NTC6796D, how come it did not work before, I thought I saw the definition in there? 

 

Thanks again!

Edited by Modmike
Link to comment
Share on other sites

3 hours ago, vector sigma said:

@unixb0y, @Modmike or anyone interested in, try this new test kext:

Nuvoton6XXXX.kext.zip

 

use only with this: FakeSMC.kext.zip

 

optional: IntelCPUMonitor.kext.zip

 

 

please use only with the FakeSMC.kext attached otherwise will not load. IntelCPUMonitor.kext has small changes, but it also require this FakeSMC to work and is only for my testing purpose since Nuvoton6XXXX.kext is not just as W836x.kext.

WARNING: to do this test remove any other FakeSMC.kext's plugins otherwise an easy kp will appear during the boot. Recommended to use clover in a USB stick to boot with these kexts inject by him. 

NEW:

Nuvoton6XXXX.kext dump all the registers in the ioreg, so don't esitate to post it.

 

Mille grazie!!! Works perfectly with ASUS PRIME Z370-A !

I just copied my config over to the Nuvoton..... plist file. Wondering though why only 2 fans have values (all 4 are shown since I have FANINLIMIT = 4).

Link to comment
Share on other sites

It just died.  Worked for a while and then HWMonitor would crash.  I erased the files in /other and copied over fresh downloads, same problem 2 fans at 0.

 

I remember reading something about the sensors needing to be toggled on or they would stay off.  Read so much stuff not sure where I saw it or if it even applies.

 

i ran every option on Mac optimizer from this site and still a no go.

 

Thanks!

Edited by Modmike
Link to comment
Share on other sites

13 hours ago, Modmike said:

It just died.  Worked for a while and then HWMonitor would crash

That has no sense, and what is HWMonitor?? You mean HWMonitorSMC2.app latest version?

 

13 hours ago, Modmike said:

I erased the files in /other and copied over fresh downloads, same problem 2 fans at 0.

Have you created a custom configuration or anyway set the FANINLIMIT entry to a grater value??

 

13 hours ago, Modmike said:

i ran every option on Mac optimizer from this site and still a no go.

Sorry but I don't even know what is 'Mac optimizer'

 

16 hours ago, Modmike said:
  1. How do I hide my serial number and other private info when I do an IO dump?
  2. I modified the default plist but get no fan speeds.  Should I create another node based on your board?
  3. If I do that, how do I get the board name it uses to match on boot?
  4. Is there a way to reload the kext while rebooting?
  5. HWMonitor seems to crash after a short period.  When this happens the machine will sleep.
  6. If its an NTC6796D, how come it did not work before, I thought I saw the definition in there? 

 

Thanks again!

  1. booting with a different serial number?
  2. already told you where
  3. yes
  4. doing that automatically
  5. try latest
  6. don't tell this to me, mine was the first attempt
Link to comment
Share on other sites

25 minutes ago, vector sigma said:

That has no sense, and what is HWMonitor?? You mean HWMonitorSMC2.app latest version?

 

Have you created a custom configuration or anyway set the FANINLIMIT entry to a grater value??

 

Sorry but I don't even know what is 'Mac optimizer'

 

  1. booting with a different serial number?
  2. already told you where
  3. yes
  4. doing that automatically
  5. try latest
  6. don't tell this to me, mine was the first attempt

 

  • Yes HWMOnitorSMC2
  • Yes I did increase the value to 3 but have since erased everything and reinstalled
  • Mac Optimizer is a utility on Insanely Mac that automatically cleans kext caches, NVRAM, fixes permissions, etc.
  • Will provide IOregDump as soon as I get back 
  • How do I identify the board name used by kext to identify board correctly?  It's an Asus Z390-I but I am sure that is not the name it will match to.  Goes to default config now.
  • I erased ALL files and reinstalled everything, still doesn't work.  Could 
  • Could SMCHelper-64.efi be an issue?
  • When I edit the plist, only Xcode gives me access to the IOKitPErsonalities, is this normal?
Edited by Modmike
Link to comment
Share on other sites

 

8 minutes ago, Modmike said:

How do I identify the board name used by kext to identify board correctly?  It's an Asus Z390-I but I am sure that is not the name it will match to.  Goes to default config now.

Bro', what to say I asked for a ioreg dump also for this purpose. Anyway I'll port my modifications to W836x.kext and send the source to Slice, so all we doing here is it just a test.

Link to comment
Share on other sites

1 hour ago, vector sigma said:

 

Bro', what to say I asked for a ioreg dump also for this purpose. Anyway I'll port my modifications to W836x.kext and send the source to Slice, so all we doing here is it just a test.

 

Here is my iMac.ioreg  Still can't get it to work.  Is there anywhere that a config or some such could have been saved and I need to erase it?

Link to comment
Share on other sites

5 minutes ago, Modmike said:

 

Here is my iMac.ioreg  Still can't get it to work.  Is there anywhere that a config or some such could have been saved and I need to erase it?

this is the registers dump:

      00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

0000  03 ff 03 ff 00 ff ff ff ff ff ff ff ff ff ff ff
0010  03 7f 03 99 03 ff 03 ff 40 ff ff ff ff ff ff ff
0020  ff ff ff ff ff ff ff 28 03 ff ff da 00 00 00 00
0030  00 00 00 00 00 00 00 00 00 50 4b ff ff ff ff ff
0040  03 2e 07 ff ff 00 3f ff 2d ff ff 10 08 55 00 a3
0050  15 ff ff ff ff ff ff ff c1 ff ff ff ff 01 00 01
0060  a0 00 ff ff ff 01 00 ff ff ff ff ff ff ff ff ff
0070  00 0a 00 25 80 25 80 80 00 80 00 25 80 80 00 ff
00f0  00 00 00 00 00 00 00 ff 1c 00 1c 1b ff ff ff ff
0100  1c 00 40 00 00 01 01 3c 00 ff ff ff 00 ff ff ff
0110  ff 19 23 2d 37 ff ff 8c aa c8 e6 32 00 01 01 00
0120  ff 00 64 64 64 ff ff ff ff ff ff ff ff ff ff ff
0130  ff 00 ff ff 00 64 01 ff 02 ff ff ff ff ff ff 00
0140  ff ff ff ff ff 00 00 ff ff ff ff ff ff ff 01 ff
0150  20 80 00 4b 00 50 00 ff ff ff ff ff ff ff ff ff
0200  1c 32 40 00 00 01 01 3c 00 ff 00 ff 00 ff ff ff
0210  ff 28 32 3c 46 ff ff 8c aa c8 e6 3c 00 02 02 00
0220  ff 00 64 64 64 ff ff ff ff ff ff ff ff ff ff ff
0230  ff 00 ff ff 00 64 01 ff 02 01 00 00 00 00 00 00
0240  ff ff ff ff ff 00 00 ff ff ff ff ff ff ff 02 ff
0250  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0260  ff ff ff ff ff ff 00 00 00 ff ff ff ff ff ff ff
0300  03 00 00 0a 0a 01 01 3c 00 7f ff 00 00 ff ff ff
0320  ff 19 23 2d 37 ff ff 8c aa c8 e6 ff ff ff ff ff
0330  ff 00 ff ff 00 64 01 ff 00 ff ff ff ff ff ff 00
0340  ff ff ff ff ff 00 00 ff ff ff ff ff ff ff 03 ff
0360  ff ff ff ff ff ff 11 00 00 7f ff ff ff ff ff ff
0400  00 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff
0410  ff ff ff ff ff ff ff ff ff 00 00 ff ff ff ff ff
0420  ff ff ff 96 64 96 64 e1 96 00 ff ff ff ff ff ff
0440  ff 30 00 00 ff 00 ff ff ff ff 00 00 00 00 04 ff
0450  03 fb ff ff 00 00 00 ff ff 0e 13 23 09 00 ff ff
0460  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0480  94 7e d4 d2 7d 18 00 d4 c9 42 55 53 84 1c 9a 5d
0490  28 20 80 07 08 0e 5c 30 80 25 25 80 80 25 13 80
04b0  ff 1f ff 1f ff 1f ff 1f 13 15 ff 1f 00 00 00 00
04c0  00 00 00 00 00 00 00 00 08 62 00 00 ff 1f 00 00
04f0  2c c0 00 00 25 00 f9 00 50 00 51 00 00 00 00 ff
0500  ff ff 00 ff ff ff 00 ff bf ff ff ff ff 00 00 ff
0550  d4 c9 00 ff 00 00 00 00 00 00 00 00 00 00 00 00
0560  00 00 00 00 00 00 ff ff ff ff ff ff ff ff ff ff
0600  00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff ff
0610  00 00 00 00 00 00 00 ff 1f ff ff ff ff ff ff ff
0620  ff 01 02 00 00 ff ff ff ff ff ff ff ff ff ff 1f
0630  ff 1f ff 1f ff 1f ff 1f 13 15 ff 1f ff 1f ff 1f
0640  ff 1f ff 1f 02 02 02 02 02 02 ff 1f ff 1f 06 02
0650  7f 7f 7f 7f 00 00 00 00 00 00 00 00 00 00 08 62
0660  00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0670  80 00 07 00 08 80 0e 00 5c 80 2c 80 ff ff ff ff
0700  ff 85 02 10 00 30 05 05 a1 64 00 00 09 05 00 00
0710  00 00 00 00 00 00 00 f2 32 f8 80 f8 80 f8 80 01
0720  2c 03 07 00 00 00 94 b1 00 94 40 00 00 00 00 40
0730  ee 00 00 00 00 00 00 00 00 00 00 0e 0a 00 00 00
0800  03 00 00 0a 0a 01 01 3c 00 99 ff 00 00 ff ff ff
0820  ff 19 23 2d 37 ff ff 8c aa c8 e6 ff ff ff ff ff
0830  ff 00 ff ff 00 64 01 ff 00 ff ff ff ff ff ff 00
0840  ff ff ff ff ff ff ff ff ff ff ff ff ff ff 08 ff
0900  1c 00 40 00 00 01 01 3c 00 ff ff ff 00 ff ff ff
0920  ff 28 28 2d 46 ff ff ff ff ff ff ff ff ff ff ff
0930  ff 00 ff ff 00 4b 01 ff 02 ff ff ff ff ff ff 00
0940  ff ff ff ff ff ff ff ff ff ff ff ff ff ff 09 ff
0960  ff ff ff ff ff ff 00 00 00 ff ff ff ff ff ff ff
0a00  03 00 00 0a 0a 01 01 3c 00 ff ff 00 00 ff ff ff
0a10  ff 19 23 2d 37 ff ff 8c aa c8 e6 3c 00 03 03 00
0a20  ff 19 23 2d 37 ff ff 8c aa c8 e6 ff ff ff ff ff
0a30  ff 00 ff ff 00 64 01 ff 00 ff ff ff ff ff ff 00
0a40  ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0a ff
0a50  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a60  ff ff ff ff ff ff 11 00 00 ff ff ff ff ff ff ff
0a70  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0b00  03 00 00 0a 0a 01 01 3c 00 ff ff 00 00 ff ff ff
0b10  ff 19 23 2d 37 ff ff 8c aa c8 e6 3c 00 03 03 00
0b20  ff 19 23 2d 37 ff ff 8c aa c8 e6 ff ff ff ff ff
0b30  ff 00 ff ff 00 64 01 ff 00 ff ff ff ff ff ff 00
0b50  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0b60  ff ff ff ff ff ff 11 00 00 ff ff ff ff ff ff ff
0b70  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c00  ff 10 00 00 1f 3f 1f 00 00 00 00 00 00 00 7f 7f
0c10  7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 50 50 50 50 50 62
0c20  4b 4b 4b 4b 4b 5f 03 04 05 06 07 10 00 00 00 00
0c30  00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a 00
0c50  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c60  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c70  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d00  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d10  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d20  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d30  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d50  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d60  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0e00  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0e10  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0e20  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0e30  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0f00  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0f10  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0f20  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0f30  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
8040  03 00 00 ff ff 00 3f ff 2d ff ff 10 08 55 80 5c
80f0  00 00 00 00 00 00 00 ff 1c 00 1c 1b ff ff ff ff

and this is the mobo model:

ROG STRIX Z390-I GAMING

Use that to create a custom configuragion under ASUS, and your custom configuration will be detected... easy.

 

P.S. the kext appear to be working well as all the registers are present :). Now I have to go, I'll do something in the weekend.

Link to comment
Share on other sites

I created a ROG STRIX Z390-I GAMING node, modified the labels and had to change the FANINLIMIT to 5 to see the pump RPM.  

 

896725129_ScreenShot2019-04-02at9_26_32PM.png.226ecfe6fb7d30684922c9dc5a67d261.png

 

I only have 1 pump and the fans are on a single speed hub.  Everything shows up in HWMonitor SMC2 as laid out and it no longer crashes.  

 

1963313266_ScreenShot2019-04-02at9_29_37PM.png.7b55bd43aff33bab2c6ae552c9987c96.png

 

 

Config question:

  1. What are the VIN1 to VIN8 entries in the plist for, core readings?
  2. Do I need to put the fans to 7 and add FANIN5 and FANIN6 to access the onboard temperature probe connector?
  3. How do I remove a category, like Battery from HWMonitorSMC2
  4. Is there a way to customize the labels in HWMonitorSMC2?
  5. What is the fan slider size for? Tuning RPM?  What if you have different size fans?
  6. Is there a config Guide for HWMonitorSMC2 you can point me to?
  7. The IGPU seems like it's not working.  Are these readings ok?

 

1531646900_ScreenShot2019-04-02at9_33_14PM.png.8741406b5388227a333031b6da4b415a.png

 

 

Compiling:

I compiled the latest version of HWMonitorSMC2 using Xcode and that went fine. I also built FakeSMC, W386x, and IntelCPUMonitor but had a few issues:

  1. I got the error "unable to find sdk 'macosx10.11'".  and had to change all the base SDKs to macOS to build. Is that ok?
  2.  Everything ran but I had the 16366 fan rpm issue with my built versions.  Is that because you didn't finish making changes? 

 

It's basically perfect all I need is to learn how to configure it.  You just made the whole Z370 and Z390 community very happy!

 

Thank you very much! 

 

 

Edited by Modmike
  • Like 1
Link to comment
Share on other sites

On 4/2/2019 at 2:41 AM, unixb0y said:

 

Mille grazie!!! Works perfectly with ASUS PRIME Z370-A !

I just copied my config over to the Nuvoton..... plist file. Wondering though why only 2 fans have values (all 4 are shown since I have FANINLIMIT = 4).

 

Also, as soon as I add the IntelCPUMonitor.kext, all fans go back to 16k RPM.

@vector sigma

Link to comment
Share on other sites

2 hours ago, unixb0y said:

 

Also, as soon as I add the IntelCPUMonitor.kext, all fans go back to 16k RPM.

@vector sigma

 

I had the same issue and I think it has to do with sensor order.  In my case, I had to set it to 5 to get my AIO pump reading. I assume it’s because I have fan, fan, temp probe, pump, etc.

 

My fans are connected to a manual hub and I can't monitor the speed.  To hide all entries but Pump, I erased the text in every fan entry and put “Pump” in the 5th FANIN4.  See my post above.

 

I think you can have up to 7 fans but your board may use them for different things.

 

To test, put 7 in FANLIMIT, add FANIN5 & FANIN6, and enter a name for each one.  When you reboot, you will easily see which ones have readings and edit out what you don’t want in your list.

 

IntelCpuMonitor.kext works for me.  Bear in mind they need to finalize the code so things may not work the same for everyone.

 

 

 

 

Edited by Modmike
Link to comment
Share on other sites

6 hours ago, unixb0y said:

Also, as soon as I add the IntelCPUMonitor.kext, all fans go back to 16k RPM.

Interesting. No really an idea, but I can only suppose that all the threads must wait or be in a queue accessing the same IO space.

Link to comment
Share on other sites

On 4/2/2019 at 9:43 PM, Modmike said:

Config question:

  1. What are the VIN1 to VIN8 entries in the plist for, core readings?
  2. Do I need to put the fans to 7 and add FANIN5 and FANIN6 to access the onboard temperature probe connector?
  3. How do I remove a category, like Battery from HWMonitorSMC2
  4. Is there a way to customize the labels in HWMonitorSMC2?
  5. What is the fan slider size for? Tuning RPM?  What if you have different size fans?
  6. Is there a config Guide for HWMonitorSMC2 you can point me to?
  7. The IGPU seems like it's not working.  Are these readings ok?
  1. voltage register at index 1 to 9 for example. Each motherboard can assign, for the same chip, different sensors. The same chip has always the same ability in all motherboards.. but different motherboards have different soldered capacitors, resistors (and so on) that make the input/output to have different calculations. So the formula to get voltages it is vendor and product specific.
  2. From what I now, and it is really an NTC6796D, it has a max of six fans registers. My code set the max fans number to be never major of this, e.g. even if you set FANINLIMIT = 15.... the max will always be 6. FANIN0 ~ FANIN5 if set, serves only to show a name you decide to give to it and to be shown. It is just the name for the index of the fan register where different mobos can have different fan type (e.g. fan at index 0 i.e. FANIN0 can be the CPU fan...or be something else fan)
  3. it is just doing it automatically. Ensure to not show empty groups in the preferences and anyway there is a checkbox you can deactivate to never show that group of sensors.
  4. No, this depend what you wrote in the kext, otherwise you will see "Fan x speed" if left empty.
  5. It is only the time polling... as should be already written just above.
  6. What the hell, it is self explanatory, just take a look in the preferences. Anyway the app just read SMC keys published by a real SMC device... or in this cases by FakeSMC and its plugins or by polling the drivers you have installed.
  7. Sorry not mine or the app fault. It is just the vanilla driver that publish 0 for this entry in the ioreg. Only apple can fix its own buggy driver(s).

 

OT ..then during the week really not able to do more as lately I have job and jobs to do that makes me boring turning on a pc at home after dinner. Anyway on the next version I'll filter good and bad values to be shown, in a way, for example, that a frequency or a fan rpm of 0 will never show up. 

 

 

Edited by vector sigma
Link to comment
Share on other sites

23 hours ago, Modmike said:

1531646900_ScreenShot2019-04-02at9_33_14PM.png.8741406b5388227a333031b6da4b415a.png

With a discrete GPU active can be normal to see the IGPU using zero resources.... until you have to decode videos using the Intel Quick Sync tech... and see those values becoming greater then 0.

Sorry for the OT as this is not the right Topic :rofl:

Link to comment
Share on other sites

23 hours ago, Modmike said:

I got the error "unable to find sdk 'macosx10.11'".  and had to change all the base SDKs to macOS to build. Is that ok?

probably the new Xcode wants it as "macos10.11" (yes.. another stupid thing by someone in Cupertino), anyway avoid to open the project directly in the Xcode GUI, use make from the command line and it automatically will set 'macos' as the latest available sdk to use...if the 10.11 (preferred) ones isn't available. This also because ensure retro-compatibility with older systems.

Edited by vector sigma
Link to comment
Share on other sites

2 hours ago, vector sigma said:

Interesting. No really an idea, but I can only suppose that all the threads must wait or be in a queue accessing the same IO space.

 

Weird; I actually tried the method that @Modmike recommended and activated all fans (7) (I think my motherboard doesn't have 7 fan headers though :lol:) which seemingly solved the issue. Then, after sitting at the computer for a couple hours, all are on 16k now! So essentially, most probably neither the CPU monitor nor the fan count make any difference but the issue lies somewhere else! :D

Link to comment
Share on other sites

13 hours ago, vector sigma said:

after a wake from sleep for example?

 

Yes, you're right! I just tested it! I have to mention that I also have other issues with sleep mode, but I saw there are dedicated forums for that. Like: When I choose "Sleep" from the Apple menu, it does go to sleep, everything turns off (like LEDs on peripherals etc) and then it turns right back on (sometimes with max fan RPMs, no idea why LOL), shows the lock screen for a while and then goes to sleep and stays there. 

Also, if it goes to sleep "from itself" due to inactivity, it doesn't do that "turning back on" thing.

 

Dave

Link to comment
Share on other sites

16 hours ago, vector sigma said:

probably the new Xcode wants it as "macos10.11" (yes.. another stupid thing by someone in Cupertino), anyway avoid to open the project directly in the Xcode GUI, use make from the command line and it automatically will set 'macos' as the latest available sdk to use...if the 10.11 (preferred) ones isn't available. This also because ensure retro-compatibility with older systems.

I will keep SDK10.11 to have kexts compatible with 10.8-10.13 systems. Else they will be compiled only for 10.14.

Link to comment
Share on other sites

4 hours ago, Slice said:

I will keep SDK10.11 to have kexts compatible with 10.8-10.13 systems. Else they will be compiled only for 10.14.

Yes agreed. But I'm referring that, at least in Xcode 10.2 I have, calling the El Capitan's sdk  as macos10.11  instead of macosx10.11 make a difference.

I.e. in the make file make bin script (called by make) this is written to:

PREFERRED_SDK=macosx10.11

but this only work with older Xcode (the sdk is found without problems) while if you use latest one you have to rename the sdk and set it as explained above. Not a very smart solution by apple.

 

EDIT

using the EC SDK in Xcode 10 + is still allowed and binaries are good.

Edited by vector sigma
Link to comment
Share on other sites

19 hours ago, unixb0y said:

 

Weird; I actually tried the method that @Modmike recommended and activated all fans (7) (I think my motherboard doesn't have 7 fan headers though :lol:)

This is easy to understand, see below:

00 00 00 00 00 00 00 00 08 62 00 00 ff 1f 00 00

each pair of bytes gives you a a value for the fan at index, but if your first connected fan is not at index zero but for example is index 5 (like in the above dump), you have to set a at least FANLIMIT to 5 before start to seeing a working fan.

Even if the Motherboard has few fan connectors doesn't mean that the chip is not able to handle more of it...

Edited by vector sigma
  • Like 1
Link to comment
Share on other sites

21 minutes ago, vector sigma said:

This is easy to understand, see below:


00 00 00 00 00 00 00 00 08 62 00 00 ff 1f 00 00

each pair of bytes gives you a a value for the fan at index, but if your first connected fan is not at index zero but for example is index 5 (like in the above dump), you have to set a at least FANLIMIT to 5 before start to seeing a working fan.

Even if the Motherboard has few fan connectors doesn't mean that the chip is not able to handle more of it...

 

I started at 5 but it didn't work.  Not saying you are wrong, just no idea why.

Link to comment
Share on other sites

33 minutes ago, Modmike said:

 

I started at 5 but it didn't work.  Not saying you are wrong, just no idea why.

probably is wrong. Your chip is actually treat as a nct676d. Slice said nct679bd but I found nothing about it other then this, where the guy is explaining that this is a nct676d, is one of the developers of openhardwaremonitor which all those kexts (koxlek and vit9696 ones as well) are based on.... so your doubt is founded, let see with a different association. 

Edited by vector sigma
typo
Link to comment
Share on other sites

 Share

×
×
  • Create New...