seebirds Posted January 24, 2017 Author Share Posted January 24, 2017 Here's my config.plist : https://transfer.sh/JtcpI/config.plist I think the patch is correctly applied. And I have these kexts loaded : kextstat|grep -i brcm 60 0 0xffffff7f81e19000 0x7c1000 0x7c1000 com.apple.driver.AirPort.Brcm4360 (1130.3.1a4) 0FA49381-8C14-3D07-81D0-A0A189812986 <59 58 57 50 12 7 6 5 4 3 1> 104 1 0xffffff7f80e12000 0x6000 0x6000 com.no-one.BrcmFirmwareStore (2.2.7) FA907595-C1CB-3D88-AD98-ADCDA9F29625 <5 4 3> 105 0 0xffffff7f80e18000 0x6000 0x6000 com.no-one.BrcmPatchRAM2 (2.2.7) 76FC3024-9FF8-3607-A616-DF7C550751CB <104 21 5 4 3 1 kextstat|grep -y pciid 47 0 0xffffff7f80c9d000 0x8000 0x8000 org.rehabman.driver.FakePCIID (1.3.4) 63F0A253-C96B-376A-8C0B-FDE91856F7DE <12 7 5 4 3 1> kextstat|grep -i airport 60 0 0xffffff7f81e19000 0x7c1000 0x7c1000 com.apple.driver.AirPort.Brcm4360 (1130.3.1a4) 0FA49381-8C14-3D07-81D0-A0A189812986 <59 58 57 50 12 7 6 5 4 3 1> Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted January 24, 2017 Moderators Share Posted January 24, 2017 @seebirds, You are using an older version of FakePCIID+FakePCIID_Broadcom_WiFi (v1.3.4) and will require the following 3 patches for Sierra. Comment AirPortBrcm4360 - PCI Error 1 Disabled Find QTnEdRs= Name AirPortBrcm4360 Replace QTnEZpA= Comment AirPortBrcm4360 - PCI Error 2 Disabled Find QQ+3zTnBdQw= Name AirPortBrcm4360 Replace QQ+3zTnBZpA= Comment AirPortBrcm4360 - PCI Error 3 Disabled Find g33EBHQG Name AirPortBrcm4360 Replace g33EBGaQ Upgrade to the latest v1.3.6 and you won't need those patches. Link to comment Share on other sites More sharing options...
seebirds Posted January 24, 2017 Author Share Posted January 24, 2017 I upgraded to 1.3.6 (latest release from RehabMan, 2017-01-09 IIRC). Still no wifi I get a KP if I set fake PCI ID for Wifi in Clover, is it normal ? Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted January 24, 2017 Administrators Share Posted January 24, 2017 no its not normal unless you have a conflict some where like DSDTinjection or config's declaring the wrong dev id's. in your log it does mention PCI issue. kernel: (AirPortBrcm4360) No Map PCI register space Link to comment Share on other sites More sharing options...
seebirds Posted January 29, 2017 Author Share Posted January 29, 2017 Finally got wifi o/ Turned out that booting Ubuntu wasn't sufficient to get wifi working (even though my Broadcom card was working great on Ubuntu), you actually need to boot a real Windows (Windows 10 Enterprise in my case). Next step : getting keyboard recognised as ISO. Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted January 30, 2017 Administrators Share Posted January 30, 2017 yes thats what i also used. windows 10 pro to reactivate my wifi. for keyboard there might be an option in the ps2 keyboard kexts plist to set to ISO. Link to comment Share on other sites More sharing options...
Administrators Hervé Posted January 30, 2017 Administrators Share Posted January 30, 2017 https://osxlatitude.com/index.php?/topic/8641-proper-keyboard-layout-recognition-with-voodoops2controller-eg-latitude-e-series/ Link to comment Share on other sites More sharing options...
seebirds Posted January 30, 2017 Author Share Posted January 30, 2017 Thank's Hervé for the link. VoodooPS2 natively recognises my keyboard as ISO, but VoodooPS2 does not support ALPSv7 trackpads. I'm currently using the modified ApplePS2Controller in Jack's bootpack which supports my trackpad but my keyboard gets recognised as ANSI. EDIT/ And… I lost my wifi. Rebooting in Windows doesn't solve the issue. Link to comment Share on other sites More sharing options...
Recommended Posts