Similar Content
- By genzaiHello Mieze,
Here are the results of my testing:
First i used an SSDT to inject my i211 and give it the i210 device ID (8086,1533). This appears to be what the driver looks for as it only has an IOPCIPrimaryMatch value in the info plist. after a few tries the SSDT appeared to work and IOJones showed the correct 1533 device ID. The driver did not load however.
Leaving the SSDT in place i then went about creating a FakePCIID kext. I based it off the 'BCM57XX as BCM57765' kext that is packaged with FakePCIID. Once I got this working, i then saw both network controllers. EN0(i219) and EN2(i210) -- not sure where EN1 went but thats probably not relevant.
Both controllers showed as loaded everywhere i checked--
-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.
- Network utility showed both devices and EN#
- DPCImanger showed both devices under its network list
- IOJones seemed to show both fully loaded with a lot of details under each entry
- and there was a new entry for 'Ethernet 2' in System Preferences>Network
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). Furthermore (and very perplexing to me) with I210 'enabled' my i219 controller was also not working. It also showed a red inactive status in network preferences when it should be connected. 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.
Removing the FakePCIID kexts brought my i219 back to life but now i am back to square one.
Thoughts?
Thanks!
g - By felixaaFollowing thread http://www.insanelymac.com/forum/topic/292117-broadcom-bcm57781-how-do-i-patch-the-kext-for-ml-1085/
was imposible find instructions patterns refered by @Mieze using 'Hopper Disassembler' on AppleBCM5701Ethernet.kext(ver: 10.1.2b3)
One user on this post: http://www.hackintoshosx.com/files/file/4270-kextstopatch-clover-broadcom-bcm57781-for-yosemite-1010-1012b3/
claim that is posible patch on-the-fly with Clover but I can´t not find his HEX´s pattern on AppleBCM5701Ethernet binary.
Any light on this? - By tannerI have successfully installed OS X Mavericks onto my Asus Zenbook UX302LA laptop and have almost everything working, except for the following:
Not Working:
Wifi( Intel N 7260, Device Instance Path: PCIVEN_8086&DEV_08B1&SUBSYS_C0708086&REV_6B4&33C43F56&0&00E3)
Two finger scroll
Touchscreen( Unknown driver)
Brightness Controls
Below, I have attached the driver for the N 7260 on Linux, which can possibly be ported to Mac OS X. If the driver cannot be ported, I could add my device ID somehow. If this is all not possible, then I suppose I could use one of my PCIE WIfi cards from another computer.
Thanks.
http://wireless.kernel.org/en/users/Drivers/iwlwifi?action=AttachFile&do=get&target=iwlwifi-7260-ucode-22.15.8.0.tgz
OS X driver for Intel onboard LAN A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers. My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. MultiBeast for Catalina is an all-in-one post-installation tool designed to enable boot from hard drive, and install support for Audio, Network, and Graphics. In addition, it includes System Utilities to rebuild caches and repair permissions and a collection of drivers, bootloaders, boot. The kext that is absolutely required VirtualSMC.kext (or FakeSMC.kext) is as aforementioned essential. This kext is what tells macOS 'Yes this is a real mac', emulating the functionality of the SMC on real Macs (hence the name). Without it, no Hackintosh.
EliteMacx86
Administrator
Staff member
- Joined
- Jul 22, 2018
- Motherboard
- GIGABYTE Z370 AROUS GAMING 3
- CPU
- Intel Core i9 9900K
- Graphics
- 2xAMD RX 580 8GB
- OS X/macOS
- 10.15.x
- Bootloader
- Clover (UEFI)
- Mac
- MacBook Pro
- Mobile Phone
- Android, iOS
So here's a quick guide to fix Keyboard and Mouse when installing. The fix works for USB and PS2 interface. On Laptops, the keyboards are generally PS/2 so you can use this guide if the keyboard isn't working.
Get Device Information
The very first step is to get the device information. The device information is basically a manufacturer name and model no.
You can use Device Manager in Windows to get the information
Download VoodooPS2Controller
The next step is to download the required kext to enable the hardware.
Downloads
Kext For Network For Mac Os X 10.7
Note :- Download the latest version for better support.
Mounting the EFI Partition and placing kext
- Mount your EFI partition of your USB
- Copy VoodooPS2Controller.kext from Release folder downloaded above.
- Navigate to EFI/Clover/kexts/Other and place the both the kexts to this location.
- If the kext is already present in the directory, replace them with a new version
If the Keyboard and Mouse doesn't work follow the steps below.
Fixing USB Ports
If the devices are still not working, there's issue with the USB ports.
To fix the USB ports, follow the guide here: https://www.elitemacx86.com/threads/how-to-create-custom-ssdt-uiac.219/
Make the necessary changes and boot off your system. The devices should work now.
![Kext For Network For Mac Os X Kext For Network For Mac Os X](/uploads/1/3/4/8/134834088/916554582.jpg)
Notes:
Kext Utility Mac
Mac Os X Extensions
- While installing Clover Bootloader, if you've installed 'AppleKeyFeeder-64' this can cause issue with the keyboard functioning. You'll need to remove it to prevent further errors.
- If the PS/2 Keyboard doesn't works, install PS2MouseDxe-64 from Clover Bootloader.