Big Sur Final Version Wi-Fi driver problem

[joshcook21]

Hi,
Firstly, thanks so much for your patcher.

The first time I tried it on my late 2012 iMac with the Big Sur Beta, it worked fine. On the day that macOS Big Sur came out, I tried the Wi-Fi patcher on that. It said that there was Wi-Fi and showed the networks, but when I opened Safari and searched something, it got stuck and wouldn't load (Wi-Fi problem not Mac). I tried adding my Apple ID and it kept producing 'Couldn't connect to server' error. The App store wouldn't load. With some persuading and turning Wi-Fi on and off, it connected for 10 minutes but wouldn't connect again.

Thanks

[barrykn]

Please uninstall your 3rd party antivirus. (Every single report I've received of this throughout Big Sur's development cycle has involved 3rd party antivirus, like AVG or Kaspersky or Norton or whatever. It's ALWAYS a bad idea to run 3rd party antivirus on a brand new macOS release.)

[barrykn]

(Or if I misdiagnosed this and there is no 3rd party antivirus involved, please let me know and I'll offer some more troubleshooting suggestions.)

[joshcook21]

Thanks for your reply. I have never installed a third-party antivirus on my Mac.
Any idea of what else it could be? I still run Catalina and it works fine so not a physical problem.

Thanks

[joshcook21]

I might also add that it comes up with lots of errors when I run the command, but says in the end that it successfully installed.

[barrykn]

The first time I tried it on my late 2012 iMac with the Big Sur Beta, it worked fine.

I'd like to know the answer to at least one of the following questions, if possible:

1. (Roughly) when was this?
2. What version of the patcher did you use?
3. Which Big Sur beta did you install?

This will help me figure out what might have changed between when it worked and when it stopped working.

(The reason I thought you might be running 3rd-party antivirus is that, since the new WiFi patch in Big Sur Micropatcher v0.2.1 on September 26, reports of WiFi problems this severe that did not involve antivirus and didn't have some other obvious unique element have pretty much dried up.)

I was going to make some excuses about the error messages, but now that I think about it, I might be able to do something about this in a future patcher release. (If the error messages were anything important or relevant, then WiFi should have been completely nonfunctional -- no networks showing up and absolutely no connectivity whatsoever.)

[joshcook21]

It was in early October sometime. Itmustve been beta 7 or 8, can't quite remember. Patcher was 5.0 or 5.1,which ever one was released in early October.

I will screenshot the errors for you tomorrow.
Thanks

[barrykn]

Probably beta 9, probably patcher v0.3.1-v0.3.3.

None of the patcher changes since then should cause any new WiFi problems.

Wait for the upcoming v0.5.2 patcher release (within the next several hours probably), then try again with that release before sending any error screenshots. It has some important bug fixes for patch-kexts.sh, including a bug fix that improves error handling.

[joshcook21]

Okay, thanks for all your help!

[barrykn]

(actually, I think I'll file a new issue to document this, instead of renaming this issue)

[barrykn]

I was going to close this as a duplicate of issue #110, but that only relates to the WiFi problem, not the patch-kexts errors, so I'll keep this issue open separately for now.