Yeah, I meant from the on-board card, if I don't inject the kext that are needed for them, I guess it's more then enough ? Or an exclude is always needed
The onboard Bluetooth will still show up in macOS as a BT device even without kexts, it just won't have any firmware loaded (usually anyway - sometimes rebooting from Windows into macOS can preserve the firmware for a while) and therefore will be non-functional. macOS will show that it has Bluetooth, but it won't find any devices.Yeah, I meant from the on-board card, if I don't inject the kext that are needed for them, I guess it's more then enough ? Or an exclude is always needed
Yes, you can replace the Intel M2 card with a natively supported Broadom. All details are here: https://dortania.github.io/Wireless-Buyers-Guide/mmm, ok, is there an option to go with a native supported Broadcom card for this slot ?
Yes, there is: https://www.tonymacx86.com/threads/gigabyte-x299x-catalina-support.288625/post-2226576mmm, ok, is there an option to go with a native supported Broadcom card for this slot ?
Hi, you're link isn't working anymore...
This card works for me without any problems. Fully compatible replacement.
No need to install any drivers, supporting kexts or SSDTs.
It's a bit dated compared to Intel, but unlike Intel card the motherboard comes with, it just works.
Both BT and WiFi work.
WiFi might not be super fast as reported by Network Utility App, but I don't really care about WiFi, I have 10GbE switch
https://www.amazon.com/gp/product/B083YXS7VF/?tag=tonymacx86com-20
Hi, you're link isn't working anymore...
Hi @TheBloke, the new beta bios fix this bug?The VCCSA issue is different: when the VCCSA voltage setting is changed from Auto, to for example 1.250V, this setting gets ignored whenever a shutdown or sleep/wake is done. It happens after both Windows and macOS shutdown.
After a full shutdown (but not restart), the BIOS setting still says 1.250V (or whatever), but VCCSA is actually running back at 0.9V. This is visible both in the BIOS (VCCSA is one of the values shown in the top right of each BIOS screen), and via any hardware monitoring software like HWInfo in Windows or HWMonitorSMC2 in macOS (there it will show up as 'VIN5').
When the issue occurs, VCCSA will show up as 0.9V instead of the value you set it to. I'm not 100% sure if this means it's actually 0.9V, or whether it's back to Auto.
In order to get it to re-apply, the user must change VCCSA to a different value (eg 1.245V) and then F10 in the BIOS. But it will only stay applied until the next shutdown or sleep/wake.
I used to have a tedious but effective solution for this: every time I did a cold boot, I'd go into the BIOS and flip the value between 1.250V and 1.245V (or vice versa), then F10 and boot normally. But more recently I've started making use of regular sleep and wake, which breaks that workaround because VCCSA also goes back to Auto (or 0.9V) when the system wakes from sleep.
As for the Thunderbolt: I learned that flashing the firmware does not make any improvements in terms of speed and latency. So in my case I decided to keep it original.There's a ton of info on this in CaseySJ's Z490 thread, so that would be the best place to look/ask to find out the finer details of TB firmware flashing.