Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[UtterDisbelief]

1) Broadcom
2) Please find attached the zipped EFI

Thanks in advance for your help and quick response!

Thank you.

Well, as you already know, you've got 19x USB ports configured. If we ignore that for a moment then I have to guess that the BT connection is HS11 or HS12 ?

Next, I see in config.plist that you currently have the BT kexts disabled. Depending on which Broadcom chipset you have you may need the firmware and patch enabled. However Apple native BCM chips do not. There have been stories that certain older BCM chips have now been deprecated in Ventura.

One test is to just enable BlueToolFixup.kext, and see where that gets you. (Perhaps try on a boot USB stick to avoid damaging your running system etc). You should see the BT device in System Report as "THIRD_PARTY_DONGLE".

I don't know if you still have the original motherboard Intel wirless card in place (AX201), but if you do then ensure the USB port the BT part of it uses is disabled, or this will conflict with the Broadcom one causing connection failure.

 

[MacArthur]

Hello @MacArthur,

OpenCore 2.67.0.0 supports Development Version of OC 0.8.9, which is good enough:
View attachment 564148
Regarding Intel WiFi in Ventura 13.3:

• The latest alpha build on GitHub is 3 weeks old
• Are you using that version?
• Hopefully a new version will be posted soon

I went back to 22E5219e and will wait for Apple to go back to initial wifi management when 13.3 is release or to get an updated AirportItlwm kext.

 

[maeluse]

Thank you.

Well, as you already know, you've got 19x USB ports configured. If we ignore that for a moment then I have to guess that the BT connection is HS11 or HS12 ?

Next, I see in config.plist that you currently have the BT kexts disabled. Depending on which Broadcom chipset you have you may need the firmware and patch enabled. However Apple native BCM chips do not. There have been stories that certain older BCM chips have now been deprecated in Ventura.

One test is to just enable BlueToolFixup.kext, and see where that gets you. (Perhaps try on a boot USB stick to avoid damaging your running system etc). You should see the BT device in System Report as "THIRD_PARTY_DONGLE".

I don't know if you still have the original motherboard Intel wirless card in place (AX201), but if you do then ensure the USB port the BT part of it uses is disabled, or this will conflict with the Broadcom one causing connection failure.

I actually already tried with BlueToolFixup.kext on, but as I mentioned earlier, that did not work out.

What I am wondering is: if that was a firmware/driver issue, would my apple keyboard be recognized after an off/on switch action? because this is how it behaves right now.

Moreover, I also have an additional Bluetooth apple trackpad, and with this one I have absolutely no recognition failure.

So IMHO this issue looks too specific to be fixed with a general Bluetooth patch activation. What do you think? Does this problem speak to some people?

 

[UtterDisbelief]

I actually already tried with BlueToolFixup.kext on, but as I mentioned earlier, that did not work out.

What I am wondering is: if that was a firmware/driver issue, would my apple keyboard be recognized after an off/on switch action? because this is how it behaves right now.

Moreover, I also have an additional Bluetooth apple trackpad, and with this one I have absolutely no recognition failure.

So IMHO this issue looks too specific to be fixed with a general Bluetooth patch activation. What do you think? Does this problem speak to some people?

That's different then ...

If you have no issues with an Apple Trackpad, it sounds more like the keyboard itself is the issue.

Sorry I couldn't help.

 

[maeluse]

The point is I had no issue at all before I updated to Ventura. The truth might be out there...

No problem, I am very glad you tried

 

[CaseySJ]

The point is I had no issue at all before I updated to Ventura. The truth might be out there...

No problem, I am very glad you tried

Have you tried resetting NVRAM and re-pairing the keyboard?

 

[juseon123]

The point is I had no issue at all before I updated to Ventura.

I've had similar problem with my Magic Keyboard/Trackpad from Ventura Beta to 13.2.1. This was somehow linked to DEXT for Intel I225 ethernet for my case. Disabling it by adding e1000=0 fixed it for me. This however is no longer an issue on Ventura 13.3.

 

[emistral]

The command to check for trim issues is (press CTRL-C if the log is long and the command is taking too much time):

log show --last boot | grep "trims took"

This is what it generates on my system:

% log show --last boot | grep "trims took"
...    kernel: (apfs) spaceman_scan_free_blocks:3293: disk5 scan took 1.798960 s, trims took 1.723631 s
...    kernel: (apfs) spaceman_scan_free_blocks:3293: disk3 scan took 2.592847 s, trims took 2.524236 s

We can see:

• One drive took 1.723 seconds
• One drive took 2.524 seconds

Here is the output of the command:
2023-03-01 22:11:07.473909+1100 0x391 Default 0x0 0 0 kernel: (apfs) spaceman_scan_free_blocks:3293: disk3 scan took 10.374706 s, trims took 9.858492 s

2023-03-01 22:11:10.347228+1100 0x8f4 Default 0x0 0 0 kernel: (apfs) spaceman_scan_free_blocks:3293: disk4 scan took 0.409658 s, trims took 0.286817 s

One disk took almost 10s

 

[maeluse]

I've had similar problem with my Magic Keyboard/Trackpad from Ventura Beta to 13.2.1. This was somehow linked to DEXT for Intel I225 ethernet for my case. Disabling it by adding e1000=0 fixed it for me. This however is no longer an issue on Ventura 13.3.

Thank you @CaseySJ and @juseon123 for your inputs! Then, as it is not really a crucial problem for now and as it seems to be fixed in Ventura 13.3, I would patiently wait for the official release of this version.

 

[emistral]

@CaseySJ and others. For those of you guys having a loss of internet connectivity upon waking up (despite the NIC or wifi showing that you are connected), it looks like that I hve fixed the issue by deleting the netowrk profile associated to the adapter/network card used to connect to the internet then recreating one in the settings/preferences->network. It has been almost a week now and no loss of internet connectivity upon wake up or durng use and re-establishment of connectivity after wake up happened within 5s.