Search results

So no renames in OC and not SSDT-BATT.aml, just the kext? BTW: I think I just found the issue. One renaming is not working... (BTIX) UPDATE: After fixing the renaming it worked. But I gave your kext a try and removed all the renames and the SSDT-BATT and it worked perfectly. Thanks @BlvckBytes!

Thanks for the reply, but why do you think that renames and SSDT are not needed? As you see in my EFI I already use SMCBatteryManager.kext and the battery is not being detected. I tried the script but all I got is this: Traceback (most recent call last): File "main.py", line 1, in <module>...

Hi guys, I thought I were sure that I did everything right with my SSDT-BATT... But sadly I cannot get the battery to be detected. I switched from an EliteBook 830 G5 to a ProBook 650 G5. Both systems are very similar but as I had to learn the hard way, they are not the same. @BlvckBytes...

I do not get it. I have a notebook with the exact same cpu and iGpu here and it works fine. It has to do something with the bus I guess. It is worth a try...

Hi again, please try this one.

Hey, please give this config a try. Let me know if that helped or not.

Now I have to say sorry for the late reply. Thank you for the links. I bought the adapter and a card (...C2AX) and everything is working flawless now. I have finally a fully working HackBook, thanks to you mate.

So is this a guide or advice of some sort and not you asking for help with an issue?

Have a look at this guide here to understand the bus ID patching with Open Core. https://dortania.github.io/OpenCore-Post-Install/gpu-patching/intel-patching/busid.html#parsing-the-framebuffer

Please post your EFI folder and your origin DSDT.aml here, so we can have a look.

Consider changing the title, as it is solved.

Got it, DisableRTCChecksum did the trick. Now it's all perfect. Thanks to you.

That means, now I have a flawlessly working HackBookPro, just one thing remains... If I reboot after the system was at sleep and woke up, I get an RTC error on boot. I hope I find a way to fix this, because then it is perfect.

@BlvckBytes one off-topic question: I saw your VoodooRMI project on GitHub, is this a thing which is worth trying? I mean ForceTouch emulation sound neat.

I saw this, but I - foolishly - assumed that the whole post was meant. That is why I wrote the explanation in my post. But it's okay. Now I know the exact meaning of this rule. Thanks.

Okay. I will ignore these errors then. Yes I did that, but I did not check all, as I thought - in my naive thinking - that if I check one or two, then the other will have worked, too. What a fool I was... ;-)

Hmm... I do not get why it is against the rules, especially when it is just two sentences... But okay. Thanks for the clarification, I think with a bit investigation I will fully understand that, so thank you very much for sharing and explaining.

Oh and by the way, should I try to fix all the compiling errors of my System DSDT, I mean is that even possible?

Yep, that did the trick! :) Now could you explain to me, what I did wrong? I do not just want it to work, but to understand what my issue was... Was it just the renaming, or was my SSDT-BATT.aml totally wrong? Thank you so much!

Here you go