Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

[CaseySJ]

You mean the onboard intel WiFi works in this build? or it will work in MacOS Sonoma?

It works in both, but does not support the vast majority of Continuity features of macOS. It only supports Handoff and Continuity Clipboard.

 

[Sn0wMan]

@statusquo,

Good choices. The Fenvi FV-T919 is not compatible with macOS Sonoma. We can still use on-board Intel WiFi.

How about BCM94360NG?

 

[beelzebozo]

@statusquo,

Good choices. The Fenvi FV-T919 is not compatible with macOS Sonoma. We can still use on-board Intel WiFi.

Is there a kext already?

 

[statusquo]

It works in both, but does not support the vast majority of Continuity features of macOS. It only supports Handoff and Continuity Clipboard.

I guess I'll try the onboard intel WiFi first and see what happens before returning one or both of the Fenvi.

Still waiting for parts. The WD_BLACK 2TB SN850X and 1TB are taking forever to arrive since it was out of stock. The 2TB may arrive this Wednesday as Amazon adjusted the dates a few times. I ended up ordering the extra 1TB from Newegg since Amazon has a longer arrive date for the 1TB. It's still tough to get parts in 2023 so I can't imagine what everyone else had gone through last couple of years.

 

[energy23]

Anyone tried the new F24 BIOS?

 

[Bream]

FYI: Cybersecurity company Eclypsium revealed hidden mechanism in firmware of Gigabyte motherboards

Update to new F24 Bios recommended

Story: WIRED.com / 2023.06.06
Researchers at firmware-focused cybersecurity company Eclypsium revealed today that they’ve discovered a hidden mechanism in the firmware of motherboards sold by the Taiwanese manufacturer Gigabyte, whose components are commonly used in gaming PCs and other high-performance computers. Whenever a computer with the affected Gigabyte motherboard restarts, Eclypsium found, code within the motherboard’s firmware invisibly initiates an updater program that runs on the computer and in turn downloads and executes another piece of software.

While Eclypsium says the hidden code is meant to be an innocuous tool to keep the motherboard’s firmware updated, researchers found that it’s implemented insecurely, potentially allowing the mechanism to be hijacked and used to install malware instead of Gigabyte’s intended program. And because the updater program is triggered from the computer’s firmware, outside its operating system, it’s tough for users to remove or even discover.

“If you have one of these machines, you have to worry about the fact that it’s basically grabbing something from the internet and running it without you being involved, and hasn’t done any of this securely,” says John Loucaides, who leads strategy and research at Eclypsium. “The concept of going underneath the end user and taking over their machine doesn’t sit well with most people.”

In its blog post about the research, Eclypsium lists 271 models of Gigabyte motherboards that researchers say are affected. Loucaides adds that users who want to see which motherboard their computer uses can check by going to “Start” in Windows and then “System Information.”

LINK to story

 

[Stork]

FYI: Cybersecurity company Eclypsium revealed hidden mechanism in firmware of Gigabyte motherboards

Update to new F24 Bios recommended

@CaseySJ, et al, does the F24 BIOS cut out support of Thunderbolt 2/1?

 

[slamjack]

After upgrading to Ventura 13.4 from Monterey 13.4, I start getting strange kernel panic, when Hack is idle for long. It happens from time to time — hack is idle (screen is locked, and turned off), and it wont turn on until hard reboot. Monterey was rock solid.

In system log there are a lot of

"
Jun 15 15:11:43 imac-pro-2 AMPDeviceDiscoveryAgent[881]: Entered:_AMMuxedDeviceDisconnected, mux-device:3130
Jun 15 15:11:43 imac-pro-2 AMPDeviceDiscoveryAgent[881]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:3130
Jun 15 15:11:56 imac-pro-2 AMPDeviceDiscoveryAgent[881]: Entered:_AMMuxedDeviceDisconnected, mux-device:3131
Jun 15 15:11:56 imac-pro-2 AMPDeviceDiscoveryAgent[881]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:3131"

Here is my EFI (OC 0.9.1) and panic report text. I have never any such problem before (4 years of happy hackintoshing)

 

[CaseySJ]

@CaseySJ, et al, does the F24 BIOS cut out support of Thunderbolt 2/1?

Because Gigabyte Z690 Aero G does not have on-board Thunderbolt, it means BIOS does not install new versions of Thunderbolt firmware (NVM xx). Hence, F24 should not have any effect on Thunderbolt behavior...

 

[CaseySJ]

After upgrading to Ventura 13.4 from Monterey 13.4, I start getting strange kernel panic, when Hack is idle for long. It happens from time to time — hack is idle (screen is locked, and turned off), and it wont turn on until hard reboot. Monterey was rock solid.

In system log there are a lot of

"
Jun 15 15:11:43 imac-pro-2 AMPDeviceDiscoveryAgent[881]: Entered:_AMMuxedDeviceDisconnected, mux-device:3130
Jun 15 15:11:43 imac-pro-2 AMPDeviceDiscoveryAgent[881]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:3130
Jun 15 15:11:56 imac-pro-2 AMPDeviceDiscoveryAgent[881]: Entered:_AMMuxedDeviceDisconnected, mux-device:3131
Jun 15 15:11:56 imac-pro-2 AMPDeviceDiscoveryAgent[881]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:3131"

Here is my EFI (OC 0.9.1) and panic report text. I have never any such problem before (4 years of happy hackintoshing)

Perhaps there's a third-party application that's not fully compatible with Ventura?

One option is to perform a clean installation of Ventura and test it for stability without installing third-party applications.