Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AMD graphics driver support for CPUs without AVX2 in Ventura #43

Open
ownway88 opened this issue Oct 28, 2022 · 6 comments
Open

AMD graphics driver support for CPUs without AVX2 in Ventura #43

ownway88 opened this issue Oct 28, 2022 · 6 comments

Comments

@ownway88
Copy link

Hello,

Great work with v19 release!

I see that Opencore Legacy Patcher(OCLP) is patching the AMD Polaris Graphics stack so that the CPUs without AVX2.0 can work in Ventura with graphics acceleration. Will this be possible to be included in KVM-Opencore in the future?

@Medizinmann-MD
Copy link

Medizinmann-MD commented Oct 28, 2022

Well - in theorie - you could actually use OpenCore Legacy Pacher to create a patched installer and use this as a basis for creation of an ISO.

And as I understand it - you may even just need to install the post-install patches from OpenCore legacy patcher!
https://dortania.github.io/OpenCore-Legacy-Patcher/POST-INSTALL.html#applying-post-install-volume-patches

@ownway88
Copy link
Author

OCLP documentation suggested the installation of the post-install patches in safe mode as logging into Ventura directly with AMD cards is not possible.

The problem is that I cannot get into Safemode with KVM-Opencore to apply post-install patches. To get into safe mode, I simply Hold Shift+Enter when selecting Ventura in Boot Picker, I always ran into the prohibit sign with the failure "StartImage failed".

https://dortania.github.io/OpenCore-Legacy-Patcher/VENTURA-DROP.html#current-status

@Medizinmann-MD
Copy link

You could use -x in boot args to boot into safe mode - AFAIK Shift+Enter won't work with QEMU.
acidanthera/bugtracker#1967

@ownway88
Copy link
Author

I saw that thread as well and tried to add -x in boot args, but still got the same failure unfortunately.

@Medizinmann-MD
Copy link

After some research this seems to be a problem with the OVMF/UEFI BIOS for Proxmox - right now it isn't possible to boot in to safe mode with this particular BIOS.

Question is if this BIOS can be patched and if anyone with the capabilities will do it.

@zaidranger
Copy link

Any workaround?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants