Fan Sensors Not Showing (SSDT + FakeSMC)

[KNNSpeed]

Hi,

I'm trying to make the tachometer work with FakeSMC + SSDT on my Dell XPS 15 9560. I'm not sure what else I can try to do. :/

What I think I've done correctly:
Fixed Mutex with nonzero synclevel (do I really need this?)
Matched SSDT-FANS to what ACPISensors is looking for
Created SMCD device
Utilized the correct fan query code (from DptfTabl; specifically GEN1 and SEN4 are the fans)
Dropped the PTID table (PtidDevc)

Any help would be greatly appreciated. It looks like HWMonitor just isn't adding the stuff in the SSDT (SSDT-FANS), but a double-check of my work would also be much valued.

Note: ACPI folder contains the vanilla DSDT/SSDTs.

 

[RehabMan]

Hi,

I'm trying to make the tachometer work with FakeSMC + SSDT on my Dell XPS 15 9560. I'm not sure what else I can try to do. :/

What I think I've done correctly:
Fixed Mutex with nonzero synclevel (do I really need this?)
Matched SSDT-FANS to what ACPISensors is looking for
Created SMCD device
Utilized the correct fan query code (from DptfTabl; specifically GEN1 and SEN4 are the fans)
Dropped the PTID table (PtidDevc)

Any help would be greatly appreciated. It looks like HWMonitor just isn't adding the stuff in the SSDT (SSDT-FANS), but a double-check of my work would also be much valued.

Note: ACPI folder contains the vanilla DSDT/SSDTs.

You can't just use random strings like "Fan1", "Fan2".
The names you use there must match something that HwMonitor recognizes.
Look at the ProBook example and you'll see it uses "System Fan" (also note difference in _HID).

 

[KNNSpeed]

Changed them. Still nothing.

EDIT: Proper set of problem report files.

 

[RehabMan]

Changed them. Still nothing.

EDIT: Proper set of problem report files.

Use ACPIDebug.kext to determine if your FANx methods are running and if they are returning what you expect.
Also, you might want to disable the ACPISensors attaching to THM (thermal-zone match).

 

[KNNSpeed]

The FAN methods aren't running--I put a dummy return value and that's not even showing up. Even after disabling ACPISensors attaching to THM (in the ACPISensors .plist I made thermal-zone -> ithermal-zone).

(ACPISensors does still attach with _CID, "[compatible ID here]" as opposed to _HID)

 

[RehabMan]

The FAN methods aren't running--I put a dummy return value and that's not even showing up. Even after disabling ACPISensors attaching to THM (in the ACPISensors .plist I made thermal-zone -> ithermal-zone).

(ACPISensors does still attach with _CID, "[compatible ID here]" as opposed to _HID)

Have fun debugging ACPISensors and HwMonitor.app code...

 

[KNNSpeed]

Fixed.

<key>FNum</key>
                    <array>
                        <string>ui8</string>
                        <data>
                        Ag==
                        </data>

Changed from:

<key>FNum</key>
                    <array>
                        <string>ui8</string>
                        <data>
                        AA==
                        </data>

in FakeSMC info.plist.

Now it works.

 

[RehabMan]

Fixed.

<key>FNum</key>
                    <array>
                        <string>ui8</string>
                        <data>
                        Ag==
                        </data>

Changed from:

<key>FNum</key>
                    <array>
                        <string>ui8</string>
                        <data>
                        AA==
                        </data>

in FakeSMC info.plist.

Now it works.

FNum should be updated automatically as fans (tachometers) are added...

 

[KNNSpeed]

Guess it wasn't. This would be the second time now on my system that FakeSMC hasn't seemed to always automatically do what it's supposed to do--and I'd wager it's not just me.

Also arbitrary fan names DO work.

EDIT: Mutex Non-zero synclevel patches not needed, as well.

 

[RehabMan]

Guess it wasn't. This would be the second time now on my system that FakeSMC hasn't seemed to always automatically do what it's supposed to do--and I'd wager it's not just me.

You should probably debug through it to discover the real problem..

Also arbitrary fan names DO work.

If so, it is a recent change... or those names are in the kext/app.