I wonder if that issue with no Ethernet during internet recovery can be solved by using an adapter with a chip that doesn't require drivers on Mac.
I have 2 that work on M1 Macs without installing anything
* Anker 3x USB + Ethernet with an RTL8153 chip (they don't make the hub anymore, but there's others still using that chip)
* Anker USB-C Ethernet (model A7613) with AX88179A chip
We bought a load of Anker USB-A Ethernet adapters for our new office, and with Big Sur they all stopped working. At the time I think Anker didn't provide the new drivers, and the chipset manufacturer themselves required you to also install an app to enable the adapter. Really not a good experience for our users, and we're slowly trying to get rid of the adapters.
After spending weeks struggling with the nonsense involved in getting Infineon/Cypress/Broadcom hardware working on a custom IoT device thanks to some fun SDIO incompatibilities (and spec violations?) I'm glad to see I'm not the only one fed up with this nonsense.
I really wish these WiFi chips weren't locked up behind layer after layer of NDA and FAE-interaction-required support.
2 comments
[ 1080 ms ] story [ 84.2 ms ] threadI have 2 that work on M1 Macs without installing anything
* Anker 3x USB + Ethernet with an RTL8153 chip (they don't make the hub anymore, but there's others still using that chip)
* Anker USB-C Ethernet (model A7613) with AX88179A chip
We bought a load of Anker USB-A Ethernet adapters for our new office, and with Big Sur they all stopped working. At the time I think Anker didn't provide the new drivers, and the chipset manufacturer themselves required you to also install an app to enable the adapter. Really not a good experience for our users, and we're slowly trying to get rid of the adapters.
I really wish these WiFi chips weren't locked up behind layer after layer of NDA and FAE-interaction-required support.