[pre-release] macOS Ventura

[ichelash]

1 minute ago, Cyberdevs said:

For the installation you need to remove the DeviceProperties once you have installed Ventura you can use the iGPU settings.

Alright..on it

[maly70]

Hello Mates,

I installed Ventura b 1 a Gigabyte z490 Pro, gpu 10400, then installed same os into Gigabyte z590 Vision G and Gigabyte Z590 Elite AX with Nvidia 710 all works fine except vision G and Elite Ax no full acceleration(because of Nvidia card). 

Cyberdevs, you are the best I saw that helps from his heart, keep it up

7 minutes ago, Cyberdevs said:

For the installation you need to remove the DeviceProperties once you have installed Ventura you can use the iGPU settings.

You are the best Cyberdevs, keep it up

[ichelash]

5 minutes ago, maly70 said:

Hello Mates,

I installed Ventura b 1 a Gigabyte z490 Pro, gpu 10400, then installed same os into Gigabyte z590 Vision G and Gigabyte Z590 Elite AX with Nvidia 710 all works fine except vision G and Elite Ax no full acceleration(because of Nvidia card). 

Cyberdevs, you are the best I saw that helps from his heart, keep it up

You are the best Cyberdevs, keep it up

The fellas  around this forum are the best ever. Mad respect to everyone helping around here.

[Cyberdevs]

6 minutes ago, maly70 said:

no full acceleration(because of Nvidia card).

you can plug your display to the mainborad's display output instead of the nVidia GPU while if the iGPU is supported you can also disable the nVidia like shown in the picture:

[SchlachtbankHS]

14 hours ago, anerik70 said:

XFX Radeon RX570 8GB is the problem!  

 

I did this:

1. Boot with the EFI I use for Monterrey. Run de installer from macOS Monterrey (I created a partition for ventura).

2. System reboot (change to ventura EFI what I send you in the last reply) and continue the installer. When the partition name change and recovery macOS 13 appears, reboot again with the Monterrey's EFI and enter to recovery macOS 12.

3. Change the os.dmg as the MacRumors guide explain.

4. Reboot with the ventura EFI and let the installer finish (it finish in black screen when config window should appears. It is because your rx570). At this point ventura is installed but no graphics usable.

5. Change my rx470 for a non Polaris card and boot ventura (there is video And the config windows appears).

6. Finish the config.

I tried with another gpu (gt760) but got stuck at the same point. I double checked my EFI with yours and it’s the same

[maly70]

37 minutes ago, Cyberdevs said:

you can plug your display to the mainborad's display output instead of the nVidia GPU while if the iGPU is supported you can also disable the nVidia like shown in the picture:

Dear Cyberdevs, I installed Ventura into z490 with igpu 10400 and working great, still waiting for Nvidia patch  

Thank you 

[MaLd0n]

11 hours ago, surenmunoo said:

Hi I just tried it and it boots but I don't have wifi, bluetooth and use of the 10G Network Port. Alsomy Thunderbolt bolts don't show in Hackintool. 

Don't use it. This file is from my mobo.

U need edit ur. Is personal thing not generic.  

[MifJpnAlphaPlus]

Hello everyone.

Everyone posted a lot, so I was able to boot well. (Thank you very much)

 

There are three things that don't work. I made almost all nightly builds, but is it still not working?

(i9 10900F, RX-570, Asus Tuf Gaming 570 pro)

1, ALC1200 does not work.

2, I don't feel that WEG is moving. (Pikera etc. will be ignored and purple lines will be displayed in the middle of startup)

3, BCM20702 USB Dongle doesn't work on the same kext as Monterey.

I'm looking forward to Ventura working well in the future.

Please let me know if you have any information.

Thank you.

OC.zip

[D3v1L]

4 hours ago, 5T33Z0 said:

Hmmm, then I guess this is a property provided by Whatevergreen. Thanks for testing

 

nothing to do... with fb_name and WEG, black screen and "no signal" on monitor

[Cyberdevs]

@MifJpnAlphaPlus

Try this, test it on a USB disc first and if it works you can replace your own efi.

For the audio it's better to use the DeviceProperties rather than injecting it via nvram.

OC.zip

[FirstCustomac]

Anyone able to inject Orinoco framebuffer? Or has it been removed from macOS Ventura? 

[Stefanalmare]

3 minutes ago, FirstTimeCustomac said:

Anyone able to inject Orinoco framebuffer? Or has it been removed from macOS Ventura? 

Hhehehheheheh! I'm in the same situation. No way to make RX 570 working in Ventura. Any hint?

[Cyberdevs]

12 minutes ago, FirstTimeCustomac said:

Anyone able to inject Orinoco framebuffer? Or has it been removed from macOS Ventura? 

No it's still there:

 

These Device ID are available in AMD9500Controller.kext:

Spoiler

0x67E01002 0x67E31002 0x67E81002 0x67EB1002 0x67EF1002 0x67FF1002 0x67E11002 0x67E71002 0x67E91002 0x67C01002 0x67C11002 0x67C21002 0x67C41002 0x67C71002 0x67DF1002 0x67D01002 0x67C81002 0x67C91002 0x67CA1002 0x67CC1002 0x67CF1002

 

[FirstCustomac]

32 minutes ago, Stefanalmare said:

Hhehehheheheh! I'm in the same situation. No way to make RX 570 working in Ventura. Any hint?

I do have RX 580 that just works. Initially, it was showing all purple line on top and displayport did not work(Only HDMI worked) before reaching the desktop but after adding -lilubetaall all worked out except Orinoco FB being injected.

 

23 minutes ago, Cyberdevs said:

No it's still there

Thank you for confirming that

 

This is what I have

 

I've tried

- SSDT method,

- Changing part# in vBIOS to Mac Edition's part# which worked in previous macOS versions.

- @name, string (DeviceProperty)

- fb_name, string (DeviceProperty)

 

None of these seem to inject Orinoco FrameBuffer.  Any suggestions?

Edited June 18, 2022 by FirstTimeCustomac

[Cyberdevs]

@FirstTimeCustomac

My RX580's ports were ok in Ventura and I just use WEG I have one display connected to DP and one to HDMI and both work just fine, I can't talk about the 570 tho because I don't have access to any 570 GPU so I just can't comment on that but since 2017 27' iMacs come either with RX 570 or 580 there shouldn't be any issues in that regard and as far as I remember there are no purple lines during the boot stages on my displays.

[Guest 5T33Z0]

@MifJpnAlphaPlus You don't have the latest Kexts and OpenCore is outdated as well:

 

 

Edited June 18, 2022 by 5T33Z0

[Cyberdevs]

@5T33Z0

 I updated his EFI folder oc and kexts. He should be ok using the folder I posted.

[FirstCustomac]

12 minutes ago, Cyberdevs said:

@FirstTimeCustomac

My RX580's ports were ok in Ventura and I just use WEG I have one display connected to DP and one to HDMI and both work just fine, I can't talk about the 570 tho because I don't have access to any 570 GPU so I just can't comment on that but since 2017 27' iMacs come either with RX 570 or 580 there shouldn't be any issues in that regard and as far as I remember there are no purple lines during the boot stages on my displays.

In regards to purple lines and DP ports not working but resolved after adding -lilubetaall boot flag, was to answer @Stefanalmare's question.  But yes RX 580 is what I am working with and I just can't seem to inject Orinoco Framebuffer. 

[Stefanalmare]

31 minutes ago, 5T33Z0 said:

@MifJpnAlphaPlus You don't have the latest Kexts and OpenCore is outdated as well:

 

 

I just can't make OCAT to use DEV kext. How can I resolve this?

[bestal]

is there any progress for ventura ivy bridge?

 

Edited June 18, 2022 by ruslan61

[Stefanalmare]

4 minutes ago, Stefanalmare said:

I just can't make OCAT to use DEV kext. How can I resolve this?

OK, I've got it.

[Stefanalmare]

2 hours ago, Cyberdevs said:

No it's still there:

 

These Device ID are available in AMD9500Controller.kext:

  Hide contents

0x67E01002 0x67E31002 0x67E81002 0x67EB1002 0x67EF1002 0x67FF1002 0x67E11002 0x67E71002 0x67E91002 0x67C01002 0x67C11002 0x67C21002 0x67C41002 0x67C71002 0x67DF1002 0x67D01002 0x67C81002 0x67C91002 0x67CA1002 0x67CC1002 0x67CF1002

 

Mine is 0x67DF1002 and it should work. But no avail until now. Only black screen no matter the port I use. It worked like it suppose to on all macos's I used.

[mav96]

I give up with the HDMI. I patched successfully intel hd 630 KBL FB (device-id = <1B590000>). I got H264 and HVEC support. However, the HDMI is completely dysfunctional.

 

I tried patching the connections - the ports, bus id, alldata. Tried other framebuffers, all boot args I could find helpful in the WEG manual and still no functioning HDMI. It simply does not even register that something is plugged in. IORegister also does not show anything (on Monterey it registers the external monitor as AppleDisplay). And in Hackintool the Framebuffer I mostly try to make work (<00001B59>) has exactly the same connectors as the ones I have on Monterey (where the HDMI is working). The one on the screenshot is the one that gets in red (external signal) on Monterey when I connect external display. On Ventura nothing happens at all, as if nothing is being plugged in, which means that somehow it does not even know that an HDMI port exists.

 

 

If you have any suggestions what else I might try, I would be eternally grateful

 

P.S. From what I read in the WEG code, it is most probably related to computeLaneCount failure of the Lilu Pather, but I have no clue how I can fix it.

 

Edited June 18, 2022 by mav96

[Cyberdevs]

15 minutes ago, Stefanalmare said:

Mine is 0x67DF1002 and it should work. But no avail until now. Only black screen no matter the port I use. It worked like it suppose to on all macos's I used.

What is the brand for your GPU? Some GPUs are problematic as you might already know but since it's working in Monterey maybe it's just a misconfiguration in the config.plist or something that you over looked somehow?

[PoMpIs]

Guys, many times when I start Ventura, the computer shuts down before reaching the desktop, giving the following kernel panic

{"bug_type":"210","timestamp":"2022-06-18 19:40:08.00 +0200","os_version":"macOS 13.0 (22A5266r)","roots_installed":0,"incident_id":"2D76588D-3DA6-4C04-80DA-F0AB97E42773"}
{"macOSProcessedStackshotData":"bm8gb24gZGlzayBwYW5pYyBzdGFja3Nob3QgZm91bmQgaW4gY29yZWZpbGU=","macOSPanicString":"panic(cpu 2 caller 0xffffff7fa81862a8): \"[3:0:0][PPLIB] Failed to send PPLIB IRI to Accelerator.\n\" @AmdRadeonController.cpp:2001\nPanicked task 0xffffff8baf3035b8: 10 threads: pid 168: WindowServer\nBacktrace (CPU 2), panicked thread: 0xffffff907aff0a70, Frame : Return Address\n0xffffffab5165b500 : 0xffffff801b1323dd \n0xffffffab5165b550 : 0xffffff801b29ab56 \n0xffffffab5165b590 : 0xffffff801b289df0 \n0xffffffab5165b5e0 : 0xffffff801b0cd951 \n0xffffffab5165b600 : 0xffffff801b1326bd \n0xffffffab5165b6f0 : 0xffffff801b131d69 \n0xffffffab5165b750 : 0xffffff801b91613b \n0xffffffab5165b840 : 0xffffff7fa81862a8 \n0xffffffab5165b950 : 0xffffff7fa8147fc9 \n0xffffffab5165b990 : 0xffffff7fa8185146 \n0xffffffab5165b9e0 : 0xffffff7fa814c870 \n0xffffffab5165ba40 : 0xffffff7fb0fcacf9 \n0xffffffab5165bad0 : 0xffffff7fa814c7fc \n0xffffffab5165baf0 : 0xffffff7fb0fc0f0e \n0xffffffab5165bb80 : 0xffffff801b8177dc \n0xffffffab5165bbe0 : 0xffffff801b887dd7 \n0xffffffab5165bc50 : 0xffffff801b241257 \n0xffffffab5165bca0 : 0xffffff801b10a806 \n0xffffffab5165bd50 : 0xffffff801b123218 \n0xffffffab5165bdc0 : 0xffffff801b12393a \n0xffffffab5165bef0 : 0xffffff801b26cd4a \n0xffffffab5165bfa0 : 0xffffff801b0cddb6 \n      Kernel Extensions in backtrace:\n         com.apple.iokit.IOGraphicsFamily(597.0)[1418696D-9CF9-3249-B6B4-CA695BF037F6]@0xffffff7fb0fb0000->0xffffff7fb0fdefff\n            dependency: com.apple.iokit.IOPCIFamily(2.9)[98643CEB-CCC7-3DA8-B1DE-0C82D4D28F2B]@0xffffff801dbfc000->0xffffff801dc2afff\n         com.apple.kext.AMDRadeonX6000Framebuffer(4.0.9)[97BFB693-7A25-3C1D-A3B4-B33F335DA4F1]@0xffffff7fa8137000->0xffffff7fa83c0fff\n            dependency: com.apple.AppleGraphicsDeviceControl(7.1.14)[B3BE5F58-0040-3606-907A-FFE6385C38C1]@0xffffff7faff0a000->0xffffff7faff0dfff\n            dependency: com.apple.iokit.IOACPIFamily(1.4)[62C52EB0-4D0B-3A00-B4B0-A1841EA15AB4]@0xffffff801d78c000->0xffffff801d78dfff\n            dependency: com.apple.iokit.IOGraphicsFamily(597)[1418696D-9CF9-3249-B6B4-CA695BF037F6]@0xffffff7fb0fb0000->0xffffff7fb0fdefff\n            dependency: com.apple.iokit.IOPCIFamily(2.9)[98643CEB-CCC7-3DA8-B1DE-0C82D4D28F2B]@0xffffff801dbfc000->0xffffff801dc2afff\n\nProcess name corresponding to current thread (0xffffff907aff0a70): WindowServer\nBoot args: -v agdpmod=pikera unfairgva=1\n\nMac OS version:\n22A5266r\n\nKernel version:\nDarwin Kernel Version 22.0.0: Tue May 24 20:31:35 PDT 2022; root:xnu-8792.0.50.111.3~5\/RELEASE_X86_64\nKernel UUID: 198748B0-2858-345A-957A-45C9ACB4C2F2\nroots installed: 0\nKernelCache slide: 0x000000001ae00000\nKernelCache base:  0xffffff801b000000\nKernel slide:      0x000000001ae10000\nKernel text base:  0xffffff801b010000\n__HIB  text base: 0xffffff801af00000\nSystem model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)\nSystem shutdown begun: NO\nPanic diags file available: YES (0x0)\nHibernation exit count: 0\n\nSystem uptime in nanoseconds: 18527074634\nLast Sleep:           absolute           base_tsc          base_nano\n  Uptime  : 0x00000004504cba96\n  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000\n  Wake    : 0x0000000000000000 0x0000000e78fe33ed 0x0000000000000000\nCompressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space\nZone info:\n  Zone map: 0xffffff80795cc000 - 0xffffffa0795cc000\n  . PGZ   : 0xffffff80795cc000 - 0xffffff807d5cd000\n  . VM    : 0xffffff807d5cd000 - 0xffffff8549900000\n  . RO    : 0xffffff8549900000 - 0xffffff86e2f66000\n  . GEN0  : 0xffffff86e2f66000 - 0xffffff8baf299000\n  . GEN1  : 0xffffff8baf299000 - 0xffffff907b5cc000\n  . GEN2  : 0xffffff907b5cc000 - 0xffffff95478ff000\n  . GEN3  : 0xffffff95478ff000 - 0xffffff9a13c32000\n  . DATA  : 0xffffff9a13c32000 - 0xffffffa0795cc000\n  Metadata: 0xffffffcb92096000 - 0xffffffcbb2096000\n  Bitmaps : 0xffffffcbb2096000 - 0xffffffcbbe096000\n\n\n\n"}

And it only happens with RX6600, with RX6650XT it always goes well... does anyone understand that Panic?

 

 

Edited June 18, 2022 by PoMpIs