Slice Posted January 11, 2016 Author Share Posted January 11, 2016 Well, nothing changed. I think i will wait for debug version of kext. So we can find out what the problem is. Thank you for your attention and quick response. This is the debug version. Please delete the similar kext from SLE, from LE, from EFI folder or from Chameleon Extra folder, delete kernelcache and reboot. Check with System Profiler that the kext is not present. Then do the follow command from terminal sudo chown -R root:wheel ~/Downloads/W836x.kext sudo kextutil -v ~/Downloads/W836x.kext and show me output. If you are using ElCapitan be sure that SIP is disabled. W836x.kext-debug.zip 1 Link to comment Share on other sites More sharing options...
Multisaft Posted January 11, 2016 Share Posted January 11, 2016 He forgot to make a choice: - Intel or AMD processor - nVidia or ATI card - ITE, Winbond or Fintek LPC chip As well you may use ACPI monitoring if you want. About download link see my signature. ok, when I understand you correct - as I know that you are sparse with your words and that I need to figure it out by myself by thinking about it - you recommend your rev21 version with intel, nvidia checkmark, lpc chip dunno for my asus p6t-se board and acpi monitoring even dont know. Link to comment Share on other sites More sharing options...
Slice Posted January 11, 2016 Author Share Posted January 11, 2016 ASUS -> Winbond Link to comment Share on other sites More sharing options...
Multisaft Posted January 11, 2016 Share Posted January 11, 2016 ASUS -> Winbond ok thats what it looks like now: i'm happy with this type of information, thanks slice!!! Link to comment Share on other sites More sharing options...
nomadturk Posted January 29, 2016 Share Posted January 29, 2016 This is the debug version. Please delete the similar kext from SLE, from LE, from EFI folder or from Chameleon Extra folder, delete kernelcache and reboot. Check with System Profiler that the kext is not present. Then do the follow command from terminal sudo chown -R root:wheel ~/Downloads/W836x.kext sudo kextutil -v ~/Downloads/W836x.kext and show me output. If you are using ElCapitan be sure that SIP is disabled. W836x.kext-debug.zip I installed kext and this is result: Last login: Fri Jan 29 01:18:08 on console SKYNET:~ skynet$ sudo chown -R root:wheel ~/Downloads/W836x.kext Password: SKYNET:~ skynet$ sudo kextutil -v ~/Downloads/W836x.kext Defaulting to kernel file '/System/Library/Kernels/kernel' Cache file /System/Library/Caches/com.apple.kext.caches/Directories/Library/Extensions/KextIdentifiers.plist.gz is out of date; not using. Diagnostics for /Users/skynet/Downloads/W836x.kext: Code Signing Failure: not code signed /Users/skynet/Downloads/W836x.kext appears to be loadable (not including linkage for on-disk libraries). kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Users/skynet/Downloads/W836x.kext" kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Library/Extensions/FakeSMC.kext" kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Users/skynet/Downloads/W836x.kext" Loading /Users/skynet/Downloads/W836x.kext. /Users/skynet/Downloads/W836x.kext successfully loaded (or already loaded). SKYNET:~ skynet$ Link to comment Share on other sites More sharing options...
Slice Posted January 29, 2016 Author Share Posted January 29, 2016 OK, see system.log. There must be more messages about the kext. It is debug version! Link to comment Share on other sites More sharing options...
nomadturk Posted January 29, 2016 Share Posted January 29, 2016 OK, see system.log. There must be more messages about the kext. It is debug version! 29/01/16 12:56:28.982 sudo[2403]: skynet : TTY=ttys000 ; PWD=/Users/skynet ; USER=root ; COMMAND=/usr/sbin/chown -R root:wheel /Users/skynet/Downloads/W836x.kext 29/01/16 12:56:35.074 sudo[2405]: skynet : TTY=ttys000 ; PWD=/Users/skynet ; USER=root ; COMMAND=/usr/bin/kextutil -v /Users/skynet/Downloads/W836x.kext 29/01/16 12:56:35.000 kernel[0]: Dependency org.netkas.FakeSMC of kext org.mozodojo.W836x failed to load. 29/01/16 12:56:35.000 kernel[0]: Kext org.mozodojo.W836x failed to load (0xdc008015). 29/01/16 12:56:35.000 kernel[0]: Failed to load kext org.mozodojo.W836x (error 0xdc008015). 29/01/16 12:57:19.926 com.apple.kextd[45]: kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Library/Extensions/W836x.kext" 29/01/16 12:57:19.978 com.apple.kextd[45]: kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Library/Extensions/W836x.kext" 29/01/16 12:57:19.000 kernel[0]: Dependency org.netkas.FakeSMC of kext org.mozodojo.W836x failed to load. 29/01/16 12:57:19.000 kernel[0]: Kext org.mozodojo.W836x failed to load (0xdc008015). 29/01/16 12:57:19.000 kernel[0]: Failed to load kext org.mozodojo.W836x (error 0xdc008015). 29/01/16 12:57:19.985 com.apple.kextd[45]: Failed to load W836x.kext - (libkern/kext) dependency load failed. 29/01/16 12:57:19.986 com.apple.kextd[45]: Load org.mozodojo.W836x failed; removing personalities from kernel. 29/01/16 12:57:20.025 com.apple.kextcache[2433]: kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext W836x.kext 29/01/16 12:57:46.417 sudo[2435]: skynet : TTY=ttys000 ; PWD=/Users/skynet ; USER=root ; COMMAND=/usr/sbin/chown -R root:wheel /Library/Extensions/W836x.kext 29/01/16 12:57:57.521 sudo[2437]: skynet : TTY=ttys000 ; PWD=/Users/skynet ; USER=root ; COMMAND=/usr/bin/kextutil -v /Library/Extensions/W836x.kext 29/01/16 12:57:57.000 kernel[0]: Dependency org.netkas.FakeSMC of kext org.mozodojo.W836x failed to load. 29/01/16 12:57:57.000 kernel[0]: Kext org.mozodojo.W836x failed to load (0xdc008015). 29/01/16 12:57:57.000 kernel[0]: Failed to load kext org.mozodojo.W836x (error 0xdc008015). 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:01.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:02.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:02.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:02.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:02.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:02.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:02.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:02.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:02.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:02.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:02.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:03.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:03.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:03.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:03.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:03.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:03.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:03.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:04.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:04.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:04.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:04.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:04.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:04.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:04.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:04.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:04.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:07.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:07.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:07.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:07.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:08.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:08.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:08.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:08.000 kernel[0]: W836x: [Debug] freeing... 29/01/16 12:59:08.000 kernel[0]: W836x: [Debug] initialising... 29/01/16 12:59:08.000 kernel[0]: W836x: [Debug] probing... 29/01/16 12:59:08.000 kernel[0]: W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 29/01/16 12:59:08.000 kernel[0]: W836x: [Debug] freeing... Link to comment Share on other sites More sharing options...
Slice Posted January 31, 2016 Author Share Posted January 31, 2016 This is what I wanted to see W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 Wait please I found more information about this chip. 1 Link to comment Share on other sites More sharing options...
nomadturk Posted January 31, 2016 Share Posted January 31, 2016 This is what I wanted to see W836x: [Debug] found unsupported chip ID=0xd1 REVISION=0x21 Wait please I found more information about this chip. Thank You! Link to comment Share on other sites More sharing options...
Slice Posted February 1, 2016 Author Share Posted February 1, 2016 @nomadturk Can you open computer case and look on motherboard to see what is the chip? It should look something like "NCT6779D" but with other digits. We have to find a specification for it. Link to comment Share on other sites More sharing options...
nomadturk Posted February 1, 2016 Share Posted February 1, 2016 I couldn't look because they are under protective cover. But i found these picture from internet about Z170 deluxe controller chipset: Link to comment Share on other sites More sharing options...
Slice Posted February 1, 2016 Author Share Posted February 1, 2016 OK, I think this kext should work. Waiting for your test. W836x.kext.zip Link to comment Share on other sites More sharing options...
nomadturk Posted February 1, 2016 Share Posted February 1, 2016 Now Hwmonitor can read CPU Heatsink, motherboard temp and Voltages. But not the fan: And the System log result: 01/02/16 16:41:49.196 com.apple.kextd[45]: kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Library/Extensions/W836x.kext" 01/02/16 16:41:49.306 com.apple.kextd[45]: kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Library/Extensions/W836x.kext" 01/02/16 16:41:49.379 com.apple.kextd[45]: kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Library/Extensions/W836x.kext" 01/02/16 16:41:49.430 com.apple.kextd[45]: kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Library/Extensions/W836x.kext" 01/02/16 16:41:49.000 kernel[0]: W836x: found NCT6793D 01/02/16 16:41:49.000 kernel[0]: W836x: mother vendor=ASUSTeK COMPUTER INC. product=Z170-DELUXE 01/02/16 16:41:49.000 kernel[0]: W836x: [Warning] set default configuration Link to comment Share on other sites More sharing options...
Slice Posted February 1, 2016 Author Share Posted February 1, 2016 Because it is default configuration. Look other ASUS configs and create your own to be more or less like real. Link to comment Share on other sites More sharing options...
nomadturk Posted February 12, 2016 Share Posted February 12, 2016 Because it is default configuration. Look other ASUS configs and create your own to be more or less like real. Hi Slice I added Asus Z170 into W836x.kext / Info.plist. But I don't know i've successfuly edited. It seems Asus info recognized: 12/02/16 14:55:44.000 kernel[0]: W836x: found NCT6793D 12/02/16 14:55:44.000 kernel[0]: W836x: mother vendor=ASUSTeK COMPUTER INC. product=Z170-DELUXE However the HWmonitor doesn't show Fan info: If you want to control the info.plist: https://db.tt/WdStf771 Link to comment Share on other sites More sharing options...
Slice Posted February 24, 2016 Author Share Posted February 24, 2016 Hi Slice I added Asus Z170 into W836x.kext / Info.plist. But I don't know i've successfuly edited. It seems Asus info recognized: 12/02/16 14:55:44.000 kernel[0]: W836x: found NCT6793D 12/02/16 14:55:44.000 kernel[0]: W836x: mother vendor=ASUSTeK COMPUTER INC. product=Z170-DELUXE However the HWmonitor doesn't show Fan info: If you want to control the info.plist: https://db.tt/WdStf771 See your info.plist FANINLIMIT = 0 This is a number of fans to look in monitor. If you want 5 fans then you must set FANINLIMIT = 5 Enjoy! Link to comment Share on other sites More sharing options...
nomadturk Posted February 24, 2016 Share Posted February 24, 2016 See your info.plist FANINLIMIT = 0 This is a number of fans to look in monitor. If you want 5 fans then you must set FANINLIMIT = 5 Enjoy! Thank you for your help Slice. Now the fans appears in Hwmonitor. But without any rpm value. Link to comment Share on other sites More sharing options...
Jingu Posted October 2, 2017 Share Posted October 2, 2017 I have the Skylake Asus H170I-PLUS desktop. Unfortunately, my dsdt doesn't have an embedded controller, or a method TACH for the fan speed. My SuperIO chip is the Nuvoton NCT6793D. I tried the latest revision 51 of HWSensor3, FakeSMC.kext, ACPIMonitor.kext, IntelCPUMonitor.kext, and W836x.kext. But, I get 0 rpm for the CPU Fan speed. I'm trying to get the fan rpm, but either my dsdt is missing the proper code for the fan speed, or the W836x.kext doesn't support my Nuvoton NCT6793D. DSDT.dsl.txt Link to comment Share on other sites More sharing options...
ccozmo Posted November 27, 2017 Share Posted November 27, 2017 Although my AIDA64 shows the LM78 chip, this article on tweaktown says it is using the nuvoTon NCT6796D https://www.tweaktown.com/reviews/8256/asus-prime-x299-deluxe-motherboard-review/index4.html What is the latest kext for NuvoTon NCT6796D ? I tried the one in the Release 350 but it didn't seem to work Thanks ! Link to comment Share on other sites More sharing options...
Slice Posted November 27, 2017 Author Share Posted November 27, 2017 Although my AIDA64 shows the LM78 chip, this article on tweaktown says it is using the nuvoTon NCT6796D https://www.tweaktown.com/reviews/8256/asus-prime-x299-deluxe-motherboard-review/index4.html What is the latest kext for NuvoTon NCT6796D ? I tried the one in the Release 350 but it didn't seem to work Thanks ! Look, please, your system log for this line DebugLog("found unsupported chip ID=0x%x REVISION=0x%x", id, revision); I want to see the values. Link to comment Share on other sites More sharing options...
ccozmo Posted November 27, 2017 Share Posted November 27, 2017 Look, please, your system log for this line DebugLog("found unsupported chip ID=0x%x REVISION=0x%x", id, revision); I want to see the values. I tried the following command to search the log log show --style syslog | fgrep "found unsupported chip" Am I looking in the right place ? Link to comment Share on other sites More sharing options...
Slice Posted November 27, 2017 Author Share Posted November 27, 2017 I tried the following command to search the log log show --style syslog | fgrep "found unsupported chip" Am I looking in the right place ? Wait please I'll give your debug version. Link to comment Share on other sites More sharing options...
Slice Posted November 27, 2017 Author Share Posted November 27, 2017 I tried the following command to search the log log show --style syslog | fgrep "found unsupported chip" Am I looking in the right place ? test, please. See verbose boot for the line or sudo dmesg | grep unsupported or syslog... Link to comment Share on other sites More sharing options...
ccozmo Posted November 27, 2017 Share Posted November 27, 2017 test, please. See verbose boot for the line or sudo dmesg | grep unsupported or syslog... W836x.kext.zip Thank you Slice - ur amazing and so helpful ! Here is the output loginwindow is not entitledloginwindow is not entitledloginwindow is not entitledRzDeviceEngine is not entitledRzDeviceEngine is not entitledRzUpdater is not entitledRzUpdater is not entitledW836x: [Warning] found unsupported chip ID=0xd4 REVISION=0x23 W836x: [Warning] found unsupported chip ID=0xd4 REVISION=0x23 loginwindow is not entitledloginwindow is not entitledRzDeviceEngine is not entitledRzDeviceEngine is not entitledRzUpdater is not entitledRzUpdater is not entitledloginwindow is not entitledW836x: [Warning] found unsupported chip ID=0xd4 REVISION=0x23 W836x: [Warning] found unsupported chip ID=0xd4 REVISION=0x23 Thanks !! Link to comment Share on other sites More sharing options...
Slice Posted November 27, 2017 Author Share Posted November 27, 2017 OK, Now I added your ID. The kext should work 1 Link to comment Share on other sites More sharing options...
Recommended Posts