![]() On 2nd computer, I had bcm4318 ubuntu HTTP request sent, awaiting response Broadcom Diver wont install, please help Nope still not active, even after reboot. The b43, b43legacy, brcmsmac and wl drivers do not support any USB devices. The b43legacy infrastructure is composed of two parts. Back to top Switching between drivers If you card is supported by more than one driver then use the modprobe command to test the drivers. Removing the FakePCIID kexts brought my i219 back to life but now i am back to square one.Below is an alphabetically sorted list of drivers and what they currently can and can't do. Another odd thing is that Network Utility seemed to report activity for the i219 (though not the i210) but there was no way to get the OS to otherwise recognize either controller as connected let alone passing traffic. It also showed a red inactive status in network preferences when it should be connected. Furthermore (and very perplexing to me) with I210 'enabled' my i219 controller was also not working. However despite all this the i211 port would only show as inactive in system preferences and never showed any sign of life when connected to the network (other than physical LEDs blinking). and there was a new entry for 'Ethernet 2' in System Preferences>Network IOJones seemed to show both fully loaded with a lot of details under each entry DPCImanger showed both devices under its network list Network utility showed both devices and EN# ![]() System Profile showed them both under Ethernet devices, with the proper kexts associated (i211, reported as i210 with AppleIntelI210Ethernet loaded, and i219 with intelMausiEthernet loaded. EN0(i219) and EN2(i210) - not sure where EN1 went but thats probably not relevant.īoth controllers showed as loaded everywhere i checked. Once I got this working, i then saw both network controllers. I based it off the 'BCM57XX as BCM57765' kext that is packaged with FakePCIID. Leaving the SSDT in place i then went about creating a FakePCIID kext. after a few tries the SSDT appeared to work and IOJones showed the correct 1533 device ID. This appears to be what the driver looks for as it only has an IOPCIPrimaryMatch value in the info plist. ![]() First i used an SSDT to inject my i211 and give it the i210 device ID (8086,1533). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |