Slice Posted November 17, 2020 Author Share Posted November 17, 2020 May be SuperIO. Do you have Windows to check in AIDA64? I should look into datasheet to see if there is something to power on the chip. Link to comment Share on other sites More sharing options...
unixb0y Posted November 17, 2020 Share Posted November 17, 2020 4 minutes ago, Slice said: May be SuperIO. Do you have Windows to check in AIDA64? I should look into datasheet to see if there is something to power on the chip. I will look in the BIOS now. Yeah I have dual boot I can check! Link to comment Share on other sites More sharing options...
unixb0y Posted November 17, 2020 Share Posted November 17, 2020 16 minutes ago, unixb0y said: I will look in the BIOS now. Yeah I have dual boot I can check! I didn't find anything in the BIOS. AIDA64 says that I have Nuvoton NCT6793D. Link to comment Share on other sites More sharing options...
Slice Posted November 17, 2020 Author Share Posted November 17, 2020 22 minutes ago, unixb0y said: I didn't find anything in the BIOS. AIDA64 says that I have Nuvoton NCT6793D. Windows gets fan speed? Link to comment Share on other sites More sharing options...
unixb0y Posted November 17, 2020 Share Posted November 17, 2020 Just now, Slice said: Windows gets fan speed? yes Link to comment Share on other sites More sharing options...
MacNB Posted December 2, 2020 Share Posted December 2, 2020 (edited) On 2/17/2020 at 8:40 PM, vector sigma said: Thanks to had taken the time to ensure fans connectors are right. The file is identical on what it's already on Github.. Hi Vector, I just downloaded v2.6.1 App binary release from GitHub. I noticed that one of my Fan names was incorrect (not the same as the one I had submitted to you in the Z77X-UP5 TH-CF.plist file). I then checked the App's Contents/SharedSupport/LPC/Gigabyte/ITE IT8228F/ folder and the file Z77X-UP5 TH-CF.plist is not included therefore the App is picking up the default.plist file. The plist file is in the sources on GitHub but not built into the binary. Is there something wrong with the build process or are we (users) suppose to add our own plist files manually ? Edited December 2, 2020 by MacNB Link to comment Share on other sites More sharing options...
Slice Posted December 2, 2020 Author Share Posted December 2, 2020 I have to announce new release 242 IntelCPUMonitor supported all new Intel CPUs: CometLake, IceLake and others. RadeonMonitor can monitor GPU temperature for RX570, Vega and RX5600/5700. SMIMonitor can monitor temperatures and FANS on Dell laptops. VoodooBatterySMC can monitor batteries on most all laptops. It supports multibattery comfiguration and is able to see amperage at laptops heavy load. Updated application HWMonitorSMC is compatible with BigSur 10 Link to comment Share on other sites More sharing options...
fryysyd Posted December 3, 2020 Share Posted December 3, 2020 10 hours ago, Slice said: 我必须宣布新版本242 IntelCPUMonitor支持所有新的Intel CPU：CometLake，IceLake等。 RadeonMonitor可以监控RX570，Vega和RX5600 / 5700的GPU温度。 SMIMonitor可以监控Dell笔记本电脑上的温度和FANS。 VoodooBatterySMC可以监视大多数笔记本电脑上的电池。它支持多电池配置，并且能够在笔记本电脑重载时看到安培数。 更新的应用程序HWMonitorSMC与BigSur兼容 Spoiler Wonderful Link to comment Share on other sites More sharing options...
MacKonsti Posted December 4, 2020 Share Posted December 4, 2020 (edited) On 12/2/2020 at 10:14 PM, Slice said: I have to announce new release 242 Thank you from me too, @Slice for your contribution, I feel like this is an anniversary a year later after your previous release! Thanks again for your commitment. What is the minimum MacOS accepted for these kexts? Do we still need to load in Clover the SMCHelper.efi with this release? I ask because the choice was either VirtualSMC.efi for VirtualSMC and plugins or SMCHelper.efi for FakeSMC according to many guides. Thank you again! Stay safe. Edited December 4, 2020 by MacKonsti Link to comment Share on other sites More sharing options...
Slice Posted December 4, 2020 Author Share Posted December 4, 2020 With these plugins you have to use FakeSMC and exclude VirtualSMC. About SMCHelper I will recommend to use it. 3 Link to comment Share on other sites More sharing options...
unixb0y Posted December 9, 2020 Share Posted December 9, 2020 (edited) Hmm something's off with my fan stats. I had it working a long while ago, then it somehow stopped working (HWMonitorSMC 2.x). With the latest Kext files and HWMonitorSMC 1.X (?) I now do get the three fans that I have connected in my system (actually 4 but on 3 fan headers) but all display probably the maximum value in the data type used (14 bit data type? weird But it's exactly 2^14-1 on all fans) : Spoiler I did copy over my W836X config that worked in the past: Spoiler EDIT: I just realized that it doesn't even pick up the "ASUS" config, instead using "Default".. Weird. Might need to post in though. Edited December 9, 2020 by unixb0y Link to comment Share on other sites More sharing options...
Slice Posted December 9, 2020 Author Share Posted December 9, 2020 To pick up ASUS name you have to use DataHubDxe.efi. It has become fashionable to call it unnecessary. Link to comment Share on other sites More sharing options...
unixb0y Posted December 9, 2020 Share Posted December 9, 2020 1 minute ago, Slice said: To pick up ASUS name you have to use DataHubDxe.efi. It has become fashionable to call it unnecessary. Where do I find that efi file and why is it called unnecessary? I don't understand Link to comment Share on other sites More sharing options...
Slice Posted December 9, 2020 Author Share Posted December 9, 2020 Sorry for the sarcasm. It is in Clover release files. 1 Link to comment Share on other sites More sharing options...
unixb0y Posted December 9, 2020 Share Posted December 9, 2020 (edited) I don't use clover though, but I guess it doesn't inherently have anything to do with Clover? edit: https://dortania.github.io/OpenCore-Install-Guide/clover-conversion/clover-efi.html lists it under "Drivers provided/merged into OpenCore and so are no longer needed" Edited December 9, 2020 by unixb0y Link to comment Share on other sites More sharing options...
Slice Posted December 9, 2020 Author Share Posted December 9, 2020 In this case I can't guaranty sensors will see ASUS name. It sent by Clover through DataHub protocol. I may propose you to write your sensors configuration as default one. Link to comment Share on other sites More sharing options...
unixb0y Posted December 9, 2020 Share Posted December 9, 2020 Okay :-) Yeah that would be an idea, to paste it into "default". I did try it, but the readings were still 2^14-1 :/ Link to comment Share on other sites More sharing options...
Slice Posted December 9, 2020 Author Share Posted December 9, 2020 0xFF is not good. It means that the chip is not responding and I don't know why. Link to comment Share on other sites More sharing options...
unixb0y Posted December 9, 2020 Share Posted December 9, 2020 Might SMCSuperIO.kext help? Link to comment Share on other sites More sharing options...
iCanaro Posted December 9, 2020 Share Posted December 9, 2020 @Slice I wondered if the readme could be useful.pdf which is present inside the dmg of the package240, make it available even for the latest release 242 Link to comment Share on other sites More sharing options...
unixb0y Posted December 9, 2020 Share Posted December 9, 2020 3 hours ago, Slice said: 0xFF is not good. It means that the chip is not responding and I don't know why. What could I do to find out possible issues? As mentioned earlier, it worked in the past and in Windows I do get readings. The chip name is also correct. Maybe it's because I disabled Serial port in BIOS lately? But I don't think so Link to comment Share on other sites More sharing options...
unixb0y Posted December 9, 2020 Share Posted December 9, 2020 Today, I updated my OC installation and created a completely new EFI. I chose VirtualSMC and no W836 Kext and now I have sensor readings for my fans I use now: AppleALC.kext IntelMausi.kext Lilu.kext SMCProcessor.kext SMCSuperIO.kext VirtualSMC.kext WhateverGreen.kext And I have all this good stuff. iStats also works with these Kexts! Link to comment Share on other sites More sharing options...
Paksman Posted December 30, 2020 Share Posted December 30, 2020 Maybe this is off topic but I need to ask: is there anyone here successfully using opencore on Big Sur with fakesmc kext? It causes kernel panic with "You shutdown your computer because of a problem ..." message. Tried reading logs but found nothing useful. I need fakesmc with radeon monitor plugin as it's the only way to read temperature from my 5700 gpu. opencore-2020-12-18-192820.txt Link to comment Share on other sites More sharing options...
Slice Posted December 30, 2020 Author Share Posted December 30, 2020 2 hours ago, Paksman said: Maybe this is off topic but I need to ask: is there anyone here successfully using opencore on Big Sur with fakesmc kext? It causes kernel panic with "You shutdown your computer because of a problem ..." message. Tried reading logs but found nothing useful. I need fakesmc with radeon monitor plugin as it's the only way to read temperature from my 5700 gpu. opencore-2020-12-18-192820.txt This is the SMC key MSSD MSSD si8 1 Stores the last known Shut-down cause. STOP_CAUSE_SHUTDOWN_GOOD_CODE 5 STOP_CAUSE_SLEEP_GOOD_CODE 5 STOP_CAUSE_POWERKEY_GOOD_CODE 3 SLEEP_CAUSE_SLEEP_LOWBATT_CODE 2 // Deprecated. Use STOP_CAUSE_LOWBATT SLEEP_CAUSE_SLEEP_OVERTEMP_CODE 1 // Deprecated. Use appropriate STOP_CAUSE_TEMP* STOP_CAUSE_INIT_CODE 0 // Initial code STOP_CAUSE_HEALTHCHECK_CODE -1 // 0xFF STOP_CAUSE_PS_CODE -2 // 0xFE STOP_CAUSE_TEMP_MULTISLEEP_CODE -3 // 0xFD STOP_CAUSE_SENSORFAN_CODE -4 // 0xFC STOP_CAUSE_TEMP_OVERLIMITTO_CODE -30 // 0xE2 STOP_CAUSE_PSWRSMRST_CODE -40 // 0xD8 STOP_CAUSE_UNMAPPED_CODE -50 // 0xCE Deprecated because it should never occur STOP_CAUSE_LOWBATT_CODE -60 // 0xC4 STOP_CAUSE_NINJA_SHUTDOWN_CODE -61 // 0xFF STOP_CAUSE_NINJA_RESTART_CODE -62 // 0xC2 STOP_CAUSE_TEMP_PALM_CODE -70 // 0xBA STOP_CAUSE_TEMP_SODIMM_CODE -71 // 0xB9 STOP_CAUSE_TEMP_HEATPIPE_CODE -72 // 0xB8 STOP_CAUSE_TEMP_BATT_CODE -74 // 0xB6 STOP_CAUSE_ADAPTERTO_CODE -75 // 0xB5 STOP_CAUSE_TEMP_MANUAL_CODE -77 // 0xB3 Not currently used. STOP_CAUSE_CURRENT_ADAPTER_CODE -78 // 0xB2 STOP_CAUSE_CURRENT_BATT_CODE -79 // 0xB1 STOP_CAUSE_TEMP_SKIN_CODE -82 // 0xAE STOP_CAUSE_TEMP_BACKUP_CODE -84 // 0xAC STOP_CAUSE_TEMP_SKIN_BOTHBAD_CODE -83 // 0xAB Will die with M57, M59, M75, M76 STOP_CAUSE_TEMP_CPUPROX_CODE -86 // 0xAA STOP_CAUSE_TEMP_CPU_CODE -95 // 0xA1 STOP_CAUSE_TEMP_PS_CODE -100 // 0x9C STOP_CAUSE_TEMP_LCD_CODE -101 // 0x9B STOP_CAUSE_RSM_POWER_FAIL_CODE -102 // 0x9A STOP_CAUSE_BATT_CUV_CODE -103 // 0x99 STOP_CAUSE_UNKNOWN_CODE -128 // 0x80 for unknown shutdown cause With Clover you will have correct key. With OpenCore you have to exclude MSSD from FakeSMC.info.plist 1 Link to comment Share on other sites More sharing options...
Streets Posted December 30, 2020 Share Posted December 30, 2020 Goodnight. Merry Christmas. Is there any solution for the fans of the Nuvoton NTC5887D-M? Link to comment Share on other sites More sharing options...
Recommended Posts