Jump to content
8755 posts in this topic

Recommended Posts

Hi guys, for those (few) of you using qemu you may experience issues if you update to qemu 8.0.0 and you passthrough devices to a mac os vm.

From my findings I found the issue is in the new DSDT.

A temporary workaround is to dump the DSDT from the vm in qemu 7.2.1 or older and inject it with opencore in qemu 8.0.0 (I know it's not recommended to inject the full DSDT, but till now it's the only workaround I found).

For reference, I opened an issue in the qemu bugtracker:

https://gitlab.com/qemu-project/qemu/-/issues/1630

  • Like 1

Opencore issue/request for assistance:

 

On my Gigabyte Z590, I prefer to load Windows via the boot menu (F12).  However, with Opencore, it blocks Windows from that Gigabyte F12 menu until I reset NVRAM.  I would prefer that Opencore not affect the F12 Gigabyte boot menu.  Is there anyway to stop Opencore from doing this?  Or limiting it in some way?

 

It becomes very difficult to update Windows as each time I do it, I have to reboot, then run the NVRAM clean utility, reboot again and then Windows will show up in the Gigabyte F12 boot menu utility so that I can boot Windows directly from there.

 

NOTE:  I really don't want to run Windows from Opencore, or it's OpenCanopy menu utility.

 

Is there to accomplish this so that when I want to boot Windows from the Gigabyte F12 boot menu I can?  Thanks in advance.

Edited by meg2014

Any Body Having Problems Installing Try This:-

 

Copy The Installer To Another HDD Using Terminal And Run It From There

e.g sudo cp -R The Installer Name  /Volumes/Your HDD

Had Me Stumped For A While,Tried Everything, Made USB Install, Didn't Work

Then I Ran The Installer From That USB And It Worked 😀

Hope This Helps

@eSaF

Good afternoon my friend. I think the order of the macOS entries has to do with the order they are attached into the motherboard. Are you sure you have had the desired order in the past with the drives plugged as of now?

Installed 13.4 but something's changed with resolution during startup.

Now, during startup the Apple icon and progress bar, are huge size, not native resolution, then it changes to smaller size then arrive to desktop and all previous session window and placement has not been restored, all windows placed at bottom and under lower bottom of screen.

 

Apple changed something with display drivers?

or maybe some OpenCore adjustment can fix this??

 

z490 using built in UHD630 graphics, no dGPU.

 

Had to restore 13.2.1 from backup to avoid this issue for now.

Edited by draylax
  • Sad 1

CSM, I changed without realising, maybe...let's forget about it because it has no effect if its on or off.

Ventura 13.4 screws up resolution on booting, and messes up all window arrangement on desktop, it happened on 13.3 as well and so i went back to 13.2.1, again only iGPU no dGPU. Surprised this hasn't affected others with iGPU only Z490's.

 

I'm not headless, iGPU is driving the display. It's an ITX board, the 1 PCIe Slot has a Lynx AES16e PCIe card for audio.

There's no GPU Tab in Activity monitor and no Intel UHD process.

Config hasn't been changed and it's not been an issue until macOS 13.3, 13.4.

 

 

ah well that answers that about the GPU tab, cool thanks, didn't know about it.

Full command is:

 

defaults write com.apple.ActivityMonitor ShowGPUTab -bool true

So yea, I got the same read outs as your Intel UHD screenshot, model correct and location Built-In.

And yeah Headless, I got same understanding as you, iGPU is just fro processing encoding, dGPU drives display.

So technically i'm not headless, cos I use the iGPU to drive the display because there isn't a discrete gpu.

 

Edited by draylax
  • Like 1
  • Thanks 1
11 hours ago, STLVNUB said:

Can Someone A Bit More Knowledgable Than Me

Please Take A Look At My EFI, It Just Won't Boot 😂

Thanks In Advance

 

EFI.zip 86.61 MB · 2 downloads

 

What is your CPU ?

On 5/19/2023 at 6:56 AM, draylax said:

ah well that answers that about the GPU tab, cool thanks, didn't know about it.

Full command is:

 

defaults write com.apple.ActivityMonitor ShowGPUTab -bool true

So yea, I got the same read outs as your Intel UHD screenshot, model correct and location Built-In.

And yeah Headless, I got same understanding as you, iGPU is just fro processing encoding, dGPU drives display.

So technically i'm not headless, cos I use the iGPU to drive the display because there isn't a discrete gpu.

 

Ah! Super cool!

  • Like 1

I have a solution that may need different NVRAM keys for different versions of macOS (i.e. the keys need to be present in NVRAM for Ventura but not for Monterey and Big Sur).  Is there any way to conditionally "inject" NVRAM keys via OC config.plist based on my OC boot-picker selection?  And Slice is free to tell me to use CLOVER and select my config.plist at boot time :)

If not, is the idea of enabling OC to offer config.plist options at boot time on anyone's radar for development?

Edited by deeveedee
  • Like 2

Not sure if any OC devs still pay attention to this.  I just noticed that ocvalidate (0.9.2) does not detect the presence of both HfsPlus.efi and OpenHfsPlus.efi enabled in config.plist.  If UEFI > Drivers includes both HfsPlus.efi and OpenHfsPlus.efi and both are enabled, ocvalidate does not warn about this condition.

  • Like 1
2 minutes ago, Matgen84 said:

 

Do you try: Boot from USB Installer, select Disk utility and choose Apfs to format the disk.

Opencore doesn't show Install macOS Ventura in the start menu and I can't get to Disk Utility to format it.
Is that the problem?

  • Sad 1
15 hours ago, eSaF said:

You need to read up on how to prepare an OS X installer USB on a Windows machine. I think you are failing on the preparation of the Ventura installer USB. Google will be quite handy here or maybe Youtube.

OK

 

Edited by luky35
×
×
  • Create New...