- Joined
- Dec 10, 2011
- Messages
- 31
- Motherboard
- Gigabyte Z490 Vision D
- CPU
- i7-10700K
- Graphics
- RX 570
- Mac
-
- Mobile Phone
-
I did that (adding layout-id 0B000000) and removed alcid=11 from the boot args. That worked I'm sure, but today most of my audio devices disappeared (internal speakers, all airplay devices). I rebooted but they didn't come back. I reset NVRAM and I heard the Apple Sound but once booted they were still not there. Right now I've commented out the audio-id in DeviceProperties and put alcid=11 back in boot args and the audio devices are back once again and audio is working. I've also had audio issues on Windows occasionally. Yesterday I was playing a game in Windows 10 with audio and suddenly the audio quit. Not sure why.I think maybe adding the layout-id 0B000000 will fix the audio problem. It did for me and others when upgrading to Monterey.
I can only speak for myself, but the issue was this:On the Vision G:
- I am still trying to understand what the issue is with on-board audio on Vision G. Please try commenting-out the device-id line by changing it to #device-id. Refer to the first screenshot where device-id is set to 709D0000. Placing a hash mark in front of the property name has the effect of deactivating it.
Hello @sbushman18,I think maybe adding the layout-id 0B000000 will fix the audio problem. It did for me and others when upgrading to Monterey.
layout-id
instead of alcid
when the latter has and continues to work in all other systems?Thank you for the sentiment! You're most welcome to contribute towards the site's operating expenses by clicking the "Contribute" button at the very top left of the webpage, just above the TonyMacx86 logo.@CaseySJ - Want to thank you sincerely for all your help getting this machine running, and would like to donate/tip if you have a paypal account or something for that.
As tempting as it might be to join the Society of Mad Scientists (a dubious distinction we reserve for those who flash their Thunderbolt firmware), this is not a society to join unless fate and (mis)fortune deem it necessary!Just picked up an ASUS Aquantia AQ107. I guess it's not plug and play, so what do I need to do to get it to show up in Monterey?
EDIT - Nevermind, found the patch and enabled it so the Aquantia is now working. Getting there!
Now I just need to decide if I need to do the Thunderbolt flash. My Apollo x8 is working with the standard firmware, but I haven't tried much else. Wondering what functionality I'll gain with the flash. I am trying to make this replace my 2018 Mac Mini as my main machine, so I am not too concerned about losing TB3 functionality in Windows.
Thanks for reporting this. Commenting out... But if I removed device-id set to 709D0000, and kept alcid=11 in boot args, audio worked.
...
device-id=709D0000
seems to do the trick. This property was originally added for Catalina users, I believe, because that version of macOS does not support Comet Lake audio device ID.Yes, it's okay to install BIOS F20 on Z490 Vision D.Hi all
is this now safe to upgrae to bios 20 ? on vision D, with monterey
I need this for BAR (ive got alose an RTX3090, dual maco/windows config)
Thnks
yes, I just took the EFI and generated the serial numbers, then the cpu mask and downloaded the last one available and replaced the kext for the mojave operating system. I have not tried to do the same with a newer operating system, my goal was to work with Intel Wi-Fi with Mojave. But I had to use a Broadcom. I also noticed that the wi-fi intel and the adapter in psi-e are not the same as the Intel module installed in the wi-fi slot on the motherboard. I have an adapter board for m2 wi-fi, I inserted Intel AC 8265 into it and it was not recognized when the necessary kexts were entered. I decided that Intel Wi-Fi 6 and Mojave was a bad idea and gave up trying.If you look at the OpenCore 0.7.6 mini-guide in this thread, you’ll find an EFI folder for Intel Wireless. It is preconfigured for on-board Intel WiFi and Bluetooth. Have you tried that one already?
Hi Casey,On the Vision D:
On the Vision G:
- iGPU is enabled properly and is in headless mode as expected.
- iGPU device properties are also present in IOReg.
- iGPU will not appear in System Information --> Graphics/Displays. It should, however, appear in System Information --> PCI. If it does not appear there, please try a cold boot.
- I am still trying to understand what the issue is with on-board audio on Vision G. Please try commenting-out the device-id line by changing it to #device-id. Refer to the first screenshot where device-id is set to 709D0000. Placing a hash mark in front of the property name has the effect of deactivating it.