Recent content by Phlogi

I finally was able to fix my freeze issues by (one or more of): - unplugging all other SSD's and drives - Change the cable - Use SATA0 for the mac OS disk - Apply the ICH10 fix from https://www.tonymacx86.com/threads/random-freeze-hdd-led-on.238412/#post-1660503 - Update clover, lilu kexts...

[Guide] Install 10.11 beta on HP EliteBook/ProBook/others with Clover UEFI Nothing about the brcmpatch in the system.log, here is ioreg:

[Guide] Install 10.11 beta on HP EliteBook/ProBook/others with Clover UEFI Let me double check the patch then. Regarding bluetooth: I wrote (as an edit) that after using the two kexts in the clover folder, it's still not working. I can't find the BT hardware.

[Guide] Install 10.11 beta on HP EliteBook/ProBook/others with Clover UEFI True, but it's a different string I think. Any word on the BT?

[Guide] Install 10.11 beta on HP EliteBook/ProBook/others with Clover UEFI Alright thanks - by the way, this patch worked for enabling 5GHz: sudo perl -pi -e 's|\x01\x58\x54|\x01\x58\x58|g'...

HP Probook Installer Clover Edition I just replaced the WiFi + BT module on my HP 450 G2 and WiFi works fine. However I don't see any BT hardware device. Anything I need to do in order to get it working. The module is a BCM94352HMB and I do have the attached BrcmBluetoothInjector.kext in the...

Alright, so this means the suggested fixes didn't work. Not a problem for me, the Yosemite S theme looks fine and I can UEFI boot very quickly.

There you go:

How did you get that HP HD Webcam fixed? Is it another device? My webcam in the HP laptop looks the same as your vendor specific device and I'm wondering whether you got it working?

True, but didn't work either.

I did fix the issues first and then edited it, compiled it again and saved as .aml.

I tried both by editing the DSDT.aml (in CLOVER/ACPI/patched) with MaciASL, but no luck yet. I guess we'd need to debug that - it's not a major issue actually, but I might be willing to try.

Disabling fast boot does _not_ solve the issue.

Yes exactly, both workarounds do not cause the garbled screen. Here is a screenshot: Another workaround is going to standby and wake-up 8-) /edit: Actually a simple screen-off / on fixes it as well...

Well I guess you're right :) There you go: