Contribute
Register

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

Since we lack a T2 chip, in order to use Sidecar you must use a iMac SMBIOS (not iMacPro) with the IGPU configured as headless so that sidecar can use Intel Quicksync to compress and decompress the Sidecar image information.

If it still does not work you could try installing the FeatureUnlock kext :-


Cheers
Jay
I tried that but the iPad screen still shows black. Tried in Monterey as well and still get Black screen
 

Attachments

  • Screen Shot 2022-04-18 at 10.28.14.png
    Screen Shot 2022-04-18 at 10.28.14.png
    321.1 KB · Views: 31
  • Screen Shot 2022-04-18 at 10.28.28.png
    Screen Shot 2022-04-18 at 10.28.28.png
    276 KB · Views: 31
  • Screen Shot 2022-04-18 at 10.28.54.png
    Screen Shot 2022-04-18 at 10.28.54.png
    247.2 KB · Views: 35
  • Screen Shot 2022-04-18 at 10.29.16.png
    Screen Shot 2022-04-18 at 10.29.16.png
    274.1 KB · Views: 33
  • Screen Shot 2022-04-18 at 10.30.35.png
    Screen Shot 2022-04-18 at 10.30.35.png
    491.8 KB · Views: 30
Last edited:
Thanks for that! Because I use Rocket Lake, I cannot use headless mode IGPU but I will try that FeatureUnlock Kext.

I tried that but the iPad screen still shows black. Tried in Monterey as well and still get Black screen

@suren6791,

Unfortunately without a working IGPU that supports Intel QuickSync there is no way to get SideCar working, as previously stated Sidecar must use either T2 or IGPU. The FeatureUnlock kext only enables the option within MacOS, it still needs a working IGPU/QuickSync to work.

Cheers
Jay
 
@suren6791,

Unfortunately without a working IGPU that supports Intel QuickSync there is no way to get SideCar working, as previously stated Sidecar must use either T2 or IGPU. The FeatureUnlock kext only enables the option within MacOS, it still needs a working IGPU/QuickSync to work.

Cheers
Jay
Thank you. I might just go back to the 10700K as Rocket Lake does not offer much, anyway.
 
** OpenCore 0.8.0 Released **


To upgrade to OpenCore 0.8.0 please follow the HackinDROM instructions located here:
However, do not use OpenCore Configurator 2.59.0.0 because it is not compatible with the release version of OpenCore 0.8.0. After performing the upgrade with HackinDROM, no further changes or edits are needed.

Always keep a backup copy of previous OpenCore EFI folder in the EFI partition of a USB flash disk (for emergency boot).
 
I have rigorously cycled through all alcid channels for onboard Z490 Vision D Intel i220-VB audio. For some reason with Intel i9-10900k IGPU and dGPU 6900 xt it only accepts on my setup alcid = 28 which lists/enables all the appropriate sound board devices. I have to manually after each boot and login on menu bar choose internal speaker and manually choose in system settings internal speakers because by changing in menu bar it does not switch in system setting preferences for some odd reason. I will try this idea and report back soon with an answer.



My build is as follows using:
- enabled VT in system BIOS for FaceTime and Windows dual boot support

- enabled internal graphics in system BIOS for FaceTime to work with video for other person. (Using auto will not allow to see video on FaceTime from other person but boot time is normal. when enabling internal iGPU with dGPU as primary PCIe slot 1 boot suffers major heavy delay before login enough to the point where I can grab a meal and run a marathon.)

- running BIOS F21 on Z490 Vision D
- HDMI plugged in to motherboard to lg 4k and display port in on lg 4k monitor
- OpenCore 0.7.9
- macOS 12.3.1
- WD SN750 1 TB (macOS lives on this drive)
- Intel i9-10900k
- Z490 Vision D
- dGPU = factory AMD Radeon 6900 xt
- IGPU (currently using a custom IGPU headless, IGPU intel UHD 630 + dGPU 6900xt boots very slow try my EFI)

@CaseySJ any thoughts or solutions ? I still can't get my head around this and it seems such a simple task to solve ?
 
@CaseySJ any thoughts or solutions ? I still can't get my head around this and it seems such a simple task to solve ?
Can you please describe the problem again? Using 'lists' will make it much easier for me to read:

Screen Shot 2022-04-19 at 4.40.01 PM.png
 
@CaseySJ any thoughts or solutions ? I still can't get my head around this and it seems such a simple task to solve ?
Delete your alcid=28 value in config.plist NVRAM boot-args and add it to your device properties for the Realtek ALC as:

key: layout-id
value:28
type:NUMBER
 
Just upgraded to OC 0.8.0 from 0.7.4 and I've started seeing the following debug msg showing up on the Gigabyte flash screen prior to loading of the OC picker:

"OCS: No schema for SerialInit at 6 index, context <Debug> !"

I have not yet identified any problems associated with this error msg. The OC picker loads fine and I can boot into Monterey 12.3.1 (along with Windows 10 and Ubuntu) without any problems. Just wondering if anyone had any ideas? A google search produced virtually no useful info. Could this have something to do with the custom serial device quirk that was added to OC 0.8.0? BTW, I updated OC using HackinDROM and have not made any changes in config.plist. I can generate a debug log or provide additional files if anyone is interested in exploring further. Again, this error does not appear to be causing me any problems that I can yet identify.
 
Just upgraded to OC 0.8.0 from 0.7.4 and I've started seeing the following debug msg showing up on the Gigabyte flash screen prior to loading of the OC picker:

"OCS: No schema for SerialInit at 6 index, context <Debug> !"

I have not yet identified any problems associated with this error msg. The OC picker loads fine and I can boot into Monterey 12.3.1 (along with Windows 10 and Ubuntu) without any problems. Just wondering if anyone had any ideas? A google search produced virtually no useful info. Could this have something to do with the custom serial device quirk that was added to OC 0.8.0? BTW, I updated OC using HackinDROM and have not made any changes in config.plist. I can generate a debug log or provide additional files if anyone is interested in exploring further. Again, this error does not appear to be causing me any problems that I can yet identify.
you need to remove SerialInit section in your config.plist
 
Just upgraded to OC 0.8.0 from 0.7.4 and I've started seeing the following debug msg showing up on the Gigabyte flash screen prior to loading of the OC picker:

"OCS: No schema for SerialInit at 6 index, context <Debug> !"

I have not yet identified any problems associated with this error msg. The OC picker loads fine and I can boot into Monterey 12.3.1 (along with Windows 10 and Ubuntu) without any problems. Just wondering if anyone had any ideas? A google search produced virtually no useful info. Could this have something to do with the custom serial device quirk that was added to OC 0.8.0? BTW, I updated OC using HackinDROM and have not made any changes in config.plist. I can generate a debug log or provide additional files if anyone is interested in exploring further. Again, this error does not appear to be causing me any problems that I can yet identify.
Now that OpenCore Configurator (OCC) 2.26.0.0 has been released, please try the following:
  • Run OCC and let it upgrade itself to 2.26.0.0
  • Set OCC preferences to "0.8.0 Release Version" so that the title bar shows 0.8.0 Release Configuration
  • Now open your config.plist in OCC, click each of the sections on the left side (ACPI, Booter, DeviceProperties, etc.), but make no changes, then press CMD-S to save the file
  • Reboot and see if the "OCS Schema" warning goes away
 
Back
Top