I have the BCM94352Z card. I have followed the first post exactly (on macOS 10.12.1). The WiFi and BT work. WiFi connects to 5 Ghz networks as well. But I have found that many times, immediately after booting into the system, the WiFi device is not detected (BT always works). If I reboot, it gets detected.
I notice that this always happens after a cold-boot (booting for the first time after the laptop has been off for a while). I just reboot and the next boot always recognises the card.
When the WiFi hardware is not recognised, before rebooting, is there some log I can examine to help debug the issue?
I have the BCM94352Z card. I have followed the first post exactly (on macOS 10.12.1). The WiFi and BT work. WiFi connects to 5 Ghz networks as well. But I have found that many times, immediately after booting into the system, the WiFi device is not detected (BT always works). If I reboot, it gets detected.
I notice that this always happens after a cold-boot (booting for the first time after the laptop has been off for a while). I just reboot and the next boot always recognises the card.
When the WiFi hardware is not recognised, before rebooting, is there some log I can examine to help debug the issue?
Attach EFI/Clover folder as ZIP (press F4 at main Clover screen before collecting). Please eliminate 'themes' directory. Provide only EFI/Clover, not the entire EFI folder.
I have read about it. The ssdtPRGen.sh script is not detecting my Kaby Lake CPU. I have posted an issue on the Github page. https://github.com/Piker-Alpha/ssdtPRGen.sh/issues/308. Once this is resolved, I should be able to implement the native PM.
I don't know what has happened suddenly, but now, every time I boot in to Mac, my WiFi is not detected. The VoodooPS2Controller also seems to have stopped working (both trackpad and keyboard not working). Bluetooth still works, though!
Graphics still work too! I have disabled the "minStolen" kext patch and the Graphics properties in SysInfo still shows 1536 MB. On checking, it looks like my BIOS sets DVMT to 128MB by default.
Battery status works as well.
The IOReg I have attached has been taken in the above state.
I have read about it. The ssdtPRGen.sh script is not detecting my Kaby Lake CPU. I have posted an issue on the Github page. https://github.com/Piker-Alpha/ssdtPRGen.sh/issues/308. Once this is resolved, I should be able to implement the native PM.
You can probably fill in the values manually.
Treat it as Skylake CPU...
I don't know what has happened suddenly, but now, every time I boot in to Mac, my WiFi is not detected. The VoodooPS2Controller also seems to have stopped working (both trackpad and keyboard not working). Bluetooth still works, though!
Did you try an EC reset?
I would work on power management before anything else.
Note: Your ioreg still shows Android File Transfer installed.
It also shows you have work to do on USB configuration (custom SSDT + USBInjectAll.kext).
You might also try without HPET/IRQ patches as they are not always needed.
Also there are some inappropriate changes in your ACPI files. Use diffmerge to review the changes you made, and I think you'll see (eg. disassemble both ACPI/patched and ACPI/origin with iasl -da -dl DSDT.aml SSDT*.aml, then use diffmerge to compare the disassembly).
I tried that, according to your guide. If I pass any parameter (for example, processor model number or frequency), it gives me an invalid argument error:
It also shows you have work to do on USB configuration (custom SSDT + USBInjectAll.kext).
Also there are some inappropriate changes in your ACPI files. Use diffmerge to review the changes you made, and I think you'll see (eg. disassemble both ACPI/patched and ACPI/origin with iasl -da -dl DSDT.aml SSDT*.aml, then use diffmerge to compare the disassembly).
Could you please tell me how you detect such things, so I can detect them myself, in the IORegistryExplorer. Then, I won't have to disturb you for such obvious and mundane things. You also detected that native CPU PM is not done. How did you find that out? I am not averse to reading.
I tried that, according to your guide. If I pass any parameter (for example, processor model number or frequency), it gives me an invalid argument error:
EC reset is not really a "last resort" kind of thing.
Could you please tell me how you detect such things, so I can detect them myself, in the IORegistryExplorer. Then, I won't have to disturb you for such obvious and mundane things. You also detected that native CPU PM is not done. How did you find that out? I am not averse to reading.
I think I figured out why everything stopped working correctly. I completely forgot that I recently updated the BIOS. After this, it looks like the stock, generated DSDT and SSDTs have changed significantly. So, I used the F4 method to get a fresh copy of "origin" DSDT and SSDTs and re-patched all of them. This time, I left out HPET and IRQ, like you said. Now, the Mac is back to normal.
I have also implemented the native CPU PM. It was an issue with the Kaby Lake CFG file in the GitHub repo. I have updated the issue as well.
I have not worked on the USB yet. Looks like it would take a bit of time to read through and follow it.
I think I figured out why everything stopped working correctly. I completely forgot that I recently updated the BIOS. After this, it looks like the stock, generated DSDT and SSDTs have changed significantly. So, I used the F4 method to get a fresh copy of "origin" DSDT and SSDTs and re-patched all of them. This time, I left out HPET and IRQ, like you said. Now, the Mac is back to normal.
I have also implemented the native CPU PM. It was an issue with the Kaby Lake CFG file in the GitHub repo. I have updated the issue as well.
I have not worked on the USB yet. Looks like it would take a bit of time to read through and follow it.
I have attached the relevant files again. Do you still see any inappropriate changes?
With static patching, any BIOS update, hardware update, or BIOS option change makes re-extract/re-patch compulsory.
It is one of the reasons I always hotpatch...
With static patching, any BIOS update, hardware update, or BIOS option change makes re-extract/re-patch compulsory.
It is one of the reasons I always hotpatch...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.