Jump to content
2,188 posts in this topic

Recommended Posts

  • 4 weeks later...

Hi @Slice and @vector sigma and everyone, hope you are well and safe.

Please for Nuvoton Super I/O chip support on my older MSI Z97i-AC board ITX, what plugin must I use?

I cannot find any plugin to support my Fans, and in the previous iteration of HWSensors 6.26 (by kozlek) there were readings provided.

 

Running HWSensors v3 r241 on Catalina.

Many thanks in advance.

Edited by MacKonsti
Link to comment
Share on other sites

Hi @Alpha22 thanks for pointing this out, I went straight to r241 and inside the ZIP package there was no README.pdf so I missed that one out... So apologies if my question sounded too n00b :D

I saw the W836x.kext of course but I thought it was for Winbond only, not for Nuvoton NCT LPC chips. Thank you again.

 

A short other question: The guide says that for ACPIMonitor.kext "Installing this kext isn't enough to read FANs or Ambient sensors, must be used with custom DSDT edits." I guess this is still valid, yes?

So in today's installations where we almost do no custom DSDT compiling or edits, is this kext of use if we don't have access to ThermalZone data as the kext expects it?

 

Is anyone using ACPIMonitor without custom DSDT edits but with Clover configuration and patches, that could provide me an example? Many thanks.

Link to comment
Share on other sites

17 hours ago, MacKonsti said:

Hi @Alpha22 thanks for pointing this out, I went straight to r241 and inside the ZIP package there was no README.pdf so I missed that one out... So apologies if my question sounded too n00b :D

I saw the W836x.kext of course but I thought it was for Winbond only, not for Nuvoton NCT LPC chips. Thank you again.

 

A short other question: The guide says that for ACPIMonitor.kext "Installing this kext isn't enough to read FANs or Ambient sensors, must be used with custom DSDT edits." I guess this is still valid, yes?

So in today's installations where we almost do no custom DSDT compiling or edits, is this kext of use if we don't have access to ThermalZone data as the kext expects it?

 

Is anyone using ACPIMonitor without custom DSDT edits but with Clover configuration and patches, that could provide me an example? Many thanks.

The kext ACPIMonitor is not for users. It is for developers who knows what to do with DSDT.

[HOWTO] ACPI access for monitoring 

  • Like 2
Link to comment
Share on other sites

  • 7 months later...

Just noticed that I got no fans anymore in HWMonitorSMC2. 

But I also redid my EFI a while back after changing to OpenCore.

 

Do I need a special kext for fan control? I don't remember...

Link to comment
Share on other sites

5 hours ago, unixb0y said:

Just noticed that I got no fans anymore in HWMonitorSMC2. 

But I also redid my EFI a while back after changing to OpenCore.

 

Do I need a special kext for fan control? I don't remember...

There is no dependency on Clover or OpenCore but there is a dependency on FakeSMC or VirtualSMC with plugins.

Link to comment
Share on other sites

18 hours ago, Slice said:

There is no dependency on Clover or OpenCore but there is a dependency on FakeSMC or VirtualSMC with plugins.

 

Yeah, I know, I don't remember if I should use FakeSMC or VirtualSMC? I have VirtualSMC at the moment and no fans.

Link to comment
Share on other sites

4 minutes ago, Slice said:

Click on the link.

I use your link, but I can only get this.
Less at first Because no fan and CPU power are shown
I have added the code but I got very little.
What are your opinions?

Spoiler

582531180_2563-11-1613_17_35.png.ffa543855b5a5370a95120fa8c952c6e.png

 

Link to comment
Share on other sites

But you show me another picture. It is not my HWMonitor.

Then my kexts took OEM name for motherboard from Clover with DataHubDxe.efi. Else you have to edit info.plist Default section.

  • Like 1
Link to comment
Share on other sites

23 minutes ago, Slice said:

But you show me another picture. It is not my HWMonitor.

Then my kexts took OEM name for motherboard from Clover with DataHubDxe.efi. Else you have to edit info.plist Default section.

Can you tell me more details? I still don't understand What should I do?

Link to comment
Share on other sites

6 hours ago, Slice said:

My vote is for FakeSMC which is in my signature.

 

I also need `W836x.kext` right? Hmmm... no sensors showing up. After removing VirtualSMC and replacing with FakeSMC and adding W836.

Edited by unixb0y
Link to comment
Share on other sites

3 hours ago, naiclub said:

Can you tell me more details? I still don't understand What should I do?

Look into ITEIT87x.kext/Contents/Info.plist

You may find here Gigabyte and model Z87... but not same as you.

Edit somehow this and see changes.

2 hours ago, unixb0y said:

 

I also need `W836x.kext` right? Hmmm... no sensors showing up. After removing VirtualSMC and replacing with FakeSMC and adding W836.

Same for you but W836x.kext

  • Like 1
Link to comment
Share on other sites

20 hours ago, Slice said:

Look into ITEIT87x.kext/Contents/Info.plist

You may find here Gigabyte and model Z87... but not same as you.

Edit somehow this and see changes.

Same for you but W836x.kext

Spoiler

 

I want it like this. I did as you said and it didn't work at all.

Edited by naiclub
Link to comment
Share on other sites

19 minutes ago, Slice said:

I know it works if all correct.

 

So what do I need? Only FakeSMC and W836? W836 is already configured since I found it in an old EFI backup (configured for my motherboard) but no fans.

Link to comment
Share on other sites

 

2 hours ago, Slice said:

Take kernel-log and search any messages from W836.

 

Okay, it tells me it set the default configuration:

 

Spoiler

2020-11-16 16:21:13.511050+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: found NCT6793D
2020-11-16 16:21:13.511163+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: [Warning] no OEMVendor
2020-11-16 16:21:13.511504+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: [Warning] set default configuration
2020-11-16 22:58:24.220712+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: Dump Nuvoton registers:
2020-11-16 22:58:24.230749+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: - 100: ff
2020-11-16 22:58:24.230918+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: - 200: ff
2020-11-16 22:58:24.232286+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: - 300: ff
2020-11-16 22:58:24.240823+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  73: ff
2020-11-16 22:58:24.240994+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  75: ff
2020-11-16 22:58:24.249517+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  77: ff
2020-11-16 22:58:24.301032+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  79: ff
2020-11-16 22:58:24.301204+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  150: ff
2020-11-16 22:58:24.301376+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  670: ff
2020-11-16 22:58:24.333941+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  27: ff
2020-11-16 22:58:24.334903+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  20: ff
2020-11-16 22:58:24.336269+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  21: ff
2020-11-16 22:58:24.339086+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  23: ff
2020-11-16 22:58:24.339821+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  22: ff
2020-11-16 22:58:24.677969+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: found NCT6793D
2020-11-16 22:58:24.685577+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: [Warning] no OEMVendor
2020-11-16 22:58:24.693351+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: [Warning] set default configuration
2020-11-17 11:05:20.226283+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: Dump Nuvoton registers:
2020-11-17 11:05:20.228743+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: - 100: ff
2020-11-17 11:05:20.228915+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: - 200: ff
2020-11-17 11:05:20.229087+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: - 300: ff
2020-11-17 11:05:20.273049+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  73: ff
2020-11-17 11:05:20.273219+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  75: ff
2020-11-17 11:05:20.273562+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  77: ff
2020-11-17 11:05:20.306973+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  79: ff
2020-11-17 11:05:20.307087+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  150: ff
2020-11-17 11:05:20.307263+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  670: ff
2020-11-17 11:05:20.307433+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  27: ff
2020-11-17 11:05:20.308221+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  20: ff
2020-11-17 11:05:20.333295+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  21: ff
2020-11-17 11:05:20.333744+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  23: ff
2020-11-17 11:05:20.335318+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: -  22: ff
2020-11-17 11:05:20.467836+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: found NCT6793D
2020-11-17 11:05:20.483231+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: [Warning] no OEMVendor
2020-11-17 11:05:20.497574+0100 0x73       Default     0x0                  0      0    kernel: (W836x) W836x: [Warning] set default configuration

 

 

But I remember that when I first got it working a long time ago, even with default config, I was seeing some values for the fan RPM even though they were incorrect.

 

 

By the way, FakeSMC itself seems to work, since I also installed IntelCPUMonitor, which does show me good CPU frequency and temperature info for each core in HWMonitorSMC2.

Edited by unixb0y
Link to comment
Share on other sites

OK, now I see what is the problem.

Dump Nuvoton registers reply only FF which means the chip NCT6793D is not responding.

May be your motherboard has other chip? Or it somehow switched off in BIOS?

Link to comment
Share on other sites

13 minutes ago, Slice said:

OK, now I see what is the problem.

Dump Nuvoton registers reply only FF which means the chip NCT6793D is not responding.

May be your motherboard has other chip? Or it somehow switched off in BIOS?

 

Hmmm no the chip name is correct, I'll check the BIOS! What should I be looking for? SuperIO?

Link to comment
Share on other sites

×
×
  • Create New...