Search results

Expensive, as usual.

For those who haven't updated their laptops to 10.13.2 yet: make sure you have the following kexts in EFI/Clover/kexts/other, before you start the update: - FakeSMC (a must) - Lilu+IntelGraphicsFixup (a must for Skylake+) - other kexts, specific to some models (SATA/Graphics/Fake PCI ID...

Ok, could you tell me where can I look at? Also please, point me to those suggestions to take a look at them too.

My laptop still have problems with closing the lid. The laptop doesn't go to sleep, when I close it, even worse, it doesn't respond at all when I open the lid several minutes later and powering it down the hard way (holding the power button) is the only way. That happens with both 1.17 and the...

So, you suggest to go directly with the fresh install? Interesting, those things start to occur right after installed the ProBooks support (kexts, ACPI, etc) and that's on fresh install.

It seems it was prematurely to talk about "problem solved". The symptoms returned, even after several EC resets / cache rebuilds and it seems there is something about the VoodooPS2Daemon. With the daemon and the "Ignore the trackpad blablabla" option enabled, the keyboard and the pad just stop...

Yeah... I'm always forgetting about that. Several EC resets did the job... I think.

Made a fresh 10.13.1 install on my ProBook 430 G3 (HFS+ install on SSD) today and I'm having problems with keyboard and the pad. It seems the VoodooPS2controller just stops and I lose both the keyboard and the pad. There is no pattern, sometimes it stops when I type the password at the login...

Regarding that "Slow boot with APFS and TRIM" Are all SSDs affected or only some models/vendors/whatever? Is there any pattern for those incompatibilities except the slow boot?

Good to know. Thanks! Then it seems I'm ready. All other _DSM injections from the PJALM patches are already implemented as SSDTs, also several renames in config.plist (EHCx->EH0x, SAT0->SATA, USB 3.0 is "XHC" by design, so no rename is needed). Oh, I've missed one: the _OSI patch. Currently...

Ok, last one: how about patching the following methods: \UXDV \RRIO \_SB.PCI0.GFX0._DOD from NotSerialized to Serialized? Also several Names like CRS1 to CRS4 and their lenght, changed from 0x00 to 0x01 (code value patching)?

So, it's cosmetic patch in order the DSDT to be compiled without errors... How about line 2335? CreateDWordField (BUF0, \_SB.PCI0._Y0F._LEN, MSLN) // _LEN: Length is patched to CreateQWordField (BUF0, \_SB.PCI0._Y0F._LEN, MSLN) // _LEN: Length Should I ignore that too?

I've started to hotpatch the DSDT for my board (H77N-WiFi), using the PJALM patches as a template. I'm having difficulties with one of them. There is a device in the stock DSDT: Device (_SB.PCI0.DOCK) { Name (_HID, "ABCDEFGH") // _HID: Hardware ID Name (_CID, EisaId...

FYI: the internal Broadcom region codes can also be used as well as the ISO-3166 country codes: Keep in mind to be careful wherever you use them. X2 is forbidden in some European countries as well as the FCC territory.

How about the AirportBrcmFixup plugin for Lilu.kext? It has boot flag that sets the country code (brcmfx-country=XX). Maybe that can be used for creating such patch. I would have done it by now, but I have zero knowledge in C++.

May I ask you for your BIOS settings? I'd like to compare them with mine. Thanks in advance!

Of course, you live in US after all. Why whould you need to change the US locale with... US? I don't understand why they have set the US locale by default for generic/unknown wireless cards. Maybe because the FCC locales are the most restrictive ones...

I know, that's why I modified it to match my country (BG). So, this one is actually optional for 10.12.x...

That patch is still needed, especially if you live outside USA and want to use your country's WiFi regulatory.

@RehabMan in your sample ProBook configs the "10.10.2+ 5Ghz US FCC, the-darkvoid" is set with MatchOS only to 10.10.x and 10.11.x. Shouldn't the MatchOS value include 10.12.x too since it's named "10.10.2+"?