What is this?

[lersy]

Hey there buddy,

I came across with your repositories and saw this one. I downloaded and installed kext but IDK if something happens or not.

Here is the screenshoots I can provide for you:

As it is seen above , PCI lists is same before and after kext

Here is the ioregistryexplorer ss:

So what is this kext all about? As you see in my system information page only things shown as not installed are thermal subsystem things does this kext enable it or what ?

What is depend on UUID? UUID which I created through terminal with command "uuidgen" and paste in open core smbios section?

Can you provide some kind of tutorial or guide or something?

Thanks in advance

I also saw your contribution to ssdtless keyboard brightness thing it is awesome even though I dealt a great time to activate it at the beginning it will be helpful for newcomers.

Btw my system specs are:

Dell 7577 laptop - i7-7700hq variant smbios set to macbookpro14,1 for thunderbolt shit

[zhen-zen]

Thank you for your interest. This kext is still WIP, aimed to make use of Intel DPTF framework for performance tuning.

Currently available feature is to switch to modes with UUID under Available Mode.

I haven't updated it further since the battery of my laptop died and everything's throttled significantly. This feature also can't help, so I am still waiting for the replacement.

Also, some ACPI devices might be unavailable if corresponding SSDTs are dropped.

[lersy]

Thanks for your quick reply. Honestly I can say that I don't get its advantages and disadvantages depending on your answer, what I understand is that I should wait for development and someone else to make a guide for it.

I hope that you will get your devices soon for your own sake.

So I will remove the kext for now and be waiting for future updates if they ever come.

Have a nice day or night dude.

[zhen-zen]

Yes, there might be some constraints and I'm not sure if desired APIs present. I only finished the first step which is to parse description from those binaries. And there's still a lot to implement to get it fully functional.

[lersy]

Sadly I have no coding skills at all but I believe that you can achieve it by yourself or maybe there will be some other party to help you out to finish it. I can be a beta tester to provide you logs if you point me to how I can do it that's all I can offer.

[zhen-zen]

Actually there are several components. So far there are INT340Xs, B0D4 (which is also a PCI device). And unfortunately I cannot guarantee the development timeline. The architecture is a bit complex and I'm not sure of the constraints. I'm sorry for letting you down.

[profzei]

@zhen-zen
Hi, I tried your latest revision for my Huawei Matebook X Pro (my repo) and IOReg is now populated with new personalities (as you can see in the attached images...)!
Great work!

IOReg: Thermal Solution

IOReg: Sensor Solution (in Windows10 it is called Intel Dynamic Platform and Thermal Framework Generic Partecipant)

IOReg: VIR# (in Windows10 it is called Intel Dynamic Platform and Thermal Framework Ambient Temperature Sensor Partecipant)

First question: is it "normal", based on the current state of the development of your Kext, what is it reported by IOReg for \_SB.VIR1 and so on?

Since I loaded your Kext, the following 2 ACPI errors appear to me during boot (first they were not present... I had a zero ACPI errors configuration):

2021-09-01 22:59:30.713528+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:
2021-09-01 22:59:30.713533+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:
2021-09-01 22:59:30.713536+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [X3PT]
2021-09-01 22:59:30.713537+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [X3PT]
2021-09-01 22:59:30.713539+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf>  Namespace lookup failure, AE_NOT_FOUND
2021-09-01 22:59:30.713541+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf>  Namespace lookup failure, AE_NOT_FOUND
2021-09-01 22:59:30.713544+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf>  (20160930/psargs-463)
2021-09-01 22:59:30.713546+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf>  (20160930/psargs-463)
2021-09-01 22:59:30.713553+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [_PSV] @0002D #002D:
2021-09-01 22:59:30.713554+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [_PSV] @0002D #002D:
2021-09-01 22:59:30.713558+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> 
2021-09-01 22:59:30.713559+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> 
2021-09-01 22:59:30.713562+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> No Local Variables are initialized for method [_PSV]
2021-09-01 22:59:30.713564+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> No Local Variables are initialized for method [_PSV]
2021-09-01 22:59:30.713566+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> 
2021-09-01 22:59:30.713568+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> 
2021-09-01 22:59:30.713570+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> No Arguments are initialized for method [_PSV]
2021-09-01 22:59:30.713575+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> No Arguments are initialized for method [_PSV]
2021-09-01 22:59:30.713578+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> 
2021-09-01 22:59:30.713579+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> 
2021-09-01 22:59:30.713584+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:
2021-09-01 22:59:30.713585+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:
2021-09-01 22:59:30.713588+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Method parse/execution failed
2021-09-01 22:59:30.713590+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Method parse/execution failed
2021-09-01 22:59:30.713594+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB.PCI0.LPCB.EC0.SEN3._PSV] (Node ffffff9356463d80)
2021-09-01 22:59:30.713595+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB.PCI0.LPCB.EC0.SEN3._PSV] (Node ffffff9356463d80)
2021-09-01 22:59:30.713598+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> , AE_NOT_FOUND
2021-09-01 22:59:30.713599+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> , AE_NOT_FOUND
2021-09-01 22:59:30.713603+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf>  (20160930/psparse-632)
2021-09-01 22:59:30.713605+0200  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf>  (20160930/psparse-632)

Second question: I don't understand what I could do to solve them... do you have any suggestions?
I attach also my original DSDT folder from OpenCoreSysReport:
ACPI.zip

Third question: in ThermalSolution image you could see 5 Available Mode: are they selectable in OpenCore config.plist? If yes, how?

I'm available for making tests with my laptop!

[zhen-zen]

1. INT3409 is virtual sensor according to your SSDT. It doesn't appear on mine so I didn't implement that.
2. The original SSDT indicates that it's looking for S3PT, your ACPI patch elsewhere is applied here. Check \_SB.PCI0.LPCB.EC0.SEN3._PSV in patched ones.
3. You can send desired mode using ioio, i.e. ioio -s ThermalSolution 3A95C389-E4B8-4629-A526-C52C88626BAE true. I don't think it's necessary to read a static value from config. The efficiency might vary.
4. Recent commits add experimental support to S0ix at PEPD, but it does nothing on yours. So you shouldn't notice any difference.

[Edwardwich]

not work for me ?

@zhen-zen

[Edwardwich]

SSDT-7.aml.zip

@zhen-zen

[zhen-zen]

There's no active development here due to lack of documents. What's implemented follows Linux platform drivers and won't alter default behavior.

S0ix support is experimental and available in the trunk. Depends on OEM implementation, features like power LED, fan behavior, open lid to wake, might be available. There's nothing to configure for now and be aware of the thermal status.