-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Big Sur 11.3.1: Wifi network max speed reduced #189
Comments
Hmm, can you try disabling AirportBrcmFixup in your config.plist? Wondering if only the BCM4360(non-02) variant should use it |
Well, well, well I need to do the test at office as hotspot their are more difficult to connect to and only in 2.4Ghz. Sorry I may have raised a non issue. |
No worries, if you find it to be an OCLP issue then just mention. Will reopen accordingly |
Even though this is closed: I had the same issue. I upgraded the Wifi/Bluetooth Card in my MacBook Pro 10,1 to the same card as mentioned above: (ioreg -r -n ARPT | grep IOName) = pci14e4,43ba (BCM43602 802.11ac Wireless) Running OpenCore Legacy Patcher in standard mode, it enabled the AirportBrcmFixup even though it is not needed. And then I also faced the 400 MBit/s maximum connection speed issue. Setting AirportBrcmFixup to Disabled in the config.plist after building, I am back to the expected 1.300 MBit/s maximum connection speed. Can you possibly introduce a detection that does not enable AirportBrcmFixup, when the above mentioned WiFi Card is detected. I think quite a lot of people have done that upgrade to obtain AC connectivity. Edit: fixed in 0.2.5, respectively in the bundled AirportBrcmFixup. |
On a MacBook Pro 10,1 with upgraded WiFi card the connection speed to a 5ghz network was set at 867Mb on BS 11.3 which is the maximum allowed by the wifi hotspot I connect to.
After upgrading to 11.3.1:
I'm using OLCP 0.1.2 (no additional/specifc config)
my Wifi card (
ioreg -r -n ARPT | grep IOName
) =pci14e4,43ba
(BCM43602 802.11ac Wireless)The text was updated successfully, but these errors were encountered: