Contribute
Register

[Guide] Intel NUC7/NUC8 using Clover UEFI (NUC7i7Bxx,NUC8i7Bxx,etc)

Feartech said:
your USBPorts.kext is incorrect if you have an internal Wifi card installed, would expect to see a HS port set to 255

also, normally, would only see one of these enabled:
Code: 
<dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcm4360_Injector.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>

what make model and wifi card do you have?
Click to expand...
Just a heads up AirportBrcmFixup.kext is enabled, it's the last kext called out in the config.plist. As far as the internal Bluetooth/Wifi card and the USBPorts.kext the card works fine as is and the device sleeps/ wakes properly. There are quite a few users that have taken advantage of the EFI he uploaded, it's the same one I created and have on page 89 as I mentioned before.
It's one of those Hackintosh things, what works for me and at least three other users fails to load for him. It worked in Monterey but not Ventura, I advised disabling all Airport kexts but no luck.
 
Leesureone said:
Just a heads up AirportBrcmFixup.kext is enabled, it's the last kext called out in the config.plist. As far as the internal Bluetooth/Wifi card and the USBPorts.kext the card works fine as is and the device sleeps/ wakes properly. There are quite a few users that have taken advantage of the EFI he uploaded, it's the same one I created and have on page 89 as I mentioned before.
It's one of those Hackintosh things, what works for me and at least three other users fails to load for him. It worked in Monterey but not Ventura, I advised disabling all Airport kexts but no luck.
Click to expand...
was wondering why there is AirportBrcmFixup.kext (for broadcom wifi cards?) was also installed
 
Leesureone said:
Just a heads up AirportBrcmFixup.kext is enabled, it's the last kext called out in the config.plist. As far as the internal Bluetooth/Wifi card and the USBPorts.kext the card works fine as is and the device sleeps/ wakes properly. There are quite a few users that have taken advantage of the EFI he uploaded, it's the same one I created and have on page 89 as I mentioned before.
It's one of those Hackintosh things, what works for me and at least three other users fails to load for him. It worked in Monterey but not Ventura, I advised disabling all Airport kexts but no luck.
Click to expand...
Yes, i was on Monterey till last update and everything goes well. Issue occurred once i upgraded to Ventura!
 
iSalalah said:
Yes, i was on Monterey till last update and everything goes well. Issue occurred once i upgraded to Ventura!
Click to expand...
you have the issues I mentioned above that needs addressing
 
Feartech said:
your USBPorts.kext is incorrect if you have an internal Wifi card installed, would expect to see a HS port set to 255

also, normally, would only see one of these enabled:
Code: 
<dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcm4360_Injector.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>

what make model and wifi card do you have?
Click to expand...
i find hard to fix this as you suggested, could you please make it more easy for me :)
 
iSalalah said:
i find hard to fix this as you suggested, could you please make it more easy for me :)
Click to expand...
you need to remove the wifi kext you are not using, AirportBrcmFixup.kext

and you need to either edit the info.plist in your USBPorts.kext and change whichever HS port your wifi card is on to 255 or check over the usb guide:
www.tonymacx86.com

The New Beginner's Guide to USB Port Configuration

Important Update: June 2023 From Big Sur 11.3 on the built-in OpenCore XhciPortLimit quirk no-longer worked as described. This became a known "bug", though in reality it was Apple changing their internal code, making a simple "peek and poke" to keep it operating, a difficult task. However, with...
www.tonymacx86.com www.tonymacx86.com
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top