[pre-release] macOS Ventura

[Guest ricoc90]

@fernando.c.neves As far as I understand there currently is no way of fixing these graphics as of yet, if ever.
Spoofing as SKL makes no sense, since SKL itself needs to be spoofed in order to work. You might want to keep an eye on the Unsupported thread over at macrumors. 

[anerik70]

57 minutes ago, fernando.c.neves said:

Hi to everyone who update to Ventura, I already has Ventura in my 2 Hackintoshes One 10 generation I5 10400F with Gigabyte B560M-H working everything OOB with a Dongle Bluetooth and AMD Radeon RX 570 4GB with full acceleration.

 

Another Laptop (Skylake) Acer Aspire ES1-572 i5 6200u with Intel HD Graphics 520 with a patch in Opencore 0.8.3 to get acceleration and now runs as metal 3. Appers in system as Intel HD Graphics 620 (spoofed in OpenCore as 1659000 (HD 620) Kabylake). Working everything including SD Card Reader, Bluetooth and WiFi with an BCM94360CD OOB. Running Ventura Beta 4 smooth and perfect (SSD 240GB) Kingston.

 

Now here the issue...

 

I had an MacBook Pro Retina Early 2015, who is unsupported to Ventura 13 (Broadwell). I made an Ventura Pen Drive with OpenCore Legacy Support (OpenCore 0.8.3) and changed the SMBIOS of my MacbookPro12,1 to MacbookPro15,2 (2018), install was perfect, everything working but without acceleration support (Intel Iris Graphics 6100 (Broadwell).

 

I already done everything spoofed 162B0000 to every Skylake and Kabylake IGPU's and nothing works. Than I had an idea of use my AppleIntelBDWGraphics.kext from Monterey 12.5 and the rest of kexts like Framebuffer and bundle's, set csr-active-config to 02080000 (Root disabled) and use command line snapshot Mounter V2 to install these kext's in /S/L/E of Ventura 13 Beta 3. Works with my Intel Iris Graphics, get acceleration but System hangs and never start's keep looping in boot. Then I changed the info.plist of AppleIntelKBLGraphics.kext and add 0x162B8086 (Intel Iris Graphics 6100). The System not load the kext at all (Both files AppleIntelKBLGraphicsFrameBuffer.kext too. There is anyone who get's acceleration with this IGPU?

 

Link to Monterey 12.5 AppleIntelBDWGraphics.kext and FrameBuffer + Bundles

https://drive.google.com/file/d/1UrMJzn7PhmYRR-nONu1DdiWCj5y0oowk/view?usp=sharing

 

I'm losing my fate in get this working.

 

Pictures of my About This Mac and System Info (Graphics and Monitor).

https://drive.google.com/file/d/10jedLfkrsv8t-fkQ4juhxqYafNIlC2yM/view?usp=sharing

https://drive.google.com/file/d/1iH6dFA2-tm0rMdsCtnmwwecy5fIvRYvX/view?usp=sharing

 

More information about kext's policies in Ventura and Metal Support.

 

https://github.com/khronokernel/khronokernel.github.io/blob/legacy-metal/_posts/2022-08-01-2022-LEGACY-METAL.md

 

This Article says that Skylake Metal support is not working, but you can do a Spoof in Intel HD Graphics as an Kabylake device to work this out. My Acer is an Skylake and works everything except for the Intel HD Graphics 520 that.i spoofed to Intel HD Graphics 620 (Kabylake) device-id (16590000) in OpenCore 0.8.3 from OpenCore Legacy Patcher 0.4.9. Now my Skylake iGPU is fully accelerated and show as Metal 3 device (Intel HD Graphics 620).

 

If anyone has a solution for this, please share.

 

Ventura 13 beta 4.

 

config.plist 27.16 kB · 0 downloads

Can you share your ES1-572 EFI?

[fernando.c.neves]

Yes, I already know that no one has ever done it with an Broadwell MacBook Pro, but my idea of use Monterey 12.5 kext and installed in /S/L/E/ works but system do not complete boot and keep looping.

 

Need more work in this idea, it should work.

 

To use Command Line SnapShot Mounter V2, need to download https://download.developer.apple.com/macOS/Kernel_Debug_Kit_13.0_build_22A5295i/Kernel_Debug_Kit_13.0_build_RomeSeed22A5295i.dmg (Ventura Beta 3)

 

Thanks in anyway Ricoc90.

[fernando.c.neves]

Here the link of my EFI - Acer Aspire ES1-572 - OpenCore 0.8.4 - Ventura Beta 4.

 

https://drive.google.com/file/d/1yhoRlD8YdGtrvB6NlpsF3jYesZLbi0p5/view?usp=sharing

Now my Intel HD Graphics 520 (Skylake) shows as Intel UHD Graphics 617 with Metal 3 support.

Using MacBookPro15,2 SMBIOS.

Edited August 3, 2022 by fernando.c.neves

[fernando.c.neves]

I booted with -x arguments and yes I had Hardware acceleration in Ventura 13 Beta 3 with AppleIntelBDWGraphics.kext and AppleIntelBDWGraphicsFramebuffer.kext of Monterey 12.5. Showing in System Info that loaded kext. Intel Iris Plus Graphics 640 1536MB.

 

But without -x keeps looping after enable acceleration in Ventura Beta 3.

 

Edited August 3, 2022 by fernando.c.neves

[fernando.c.neves]

There something to workout in EFI of my MacBook Pro Retina Early 2015 (Intel Iris Graphics 6100) to stop looping boot with AppleIntelBDWGraphics.kext after loading.

 

Here my EFI link.

 

https://drive.google.com/file/d/1UNstmbDAttfJr1hKxuh5VASD8THfRWq5/view?usp=sharing

 

Thanks in advance!!!

[chris1111]

2 hours ago, PoMpIs said:

 

It has something to do with it, because when I delete it, if I don't put the computer to sleep, it doesn't regenerate, and therefore I don't have the problem again.

 

If I put it to sleep, when I wake it up the file is regenerated, but on my computer I don't get high CPU usage caused by "powerd" again until it goes back to sleep automatically and wakes up only a few hours later, And that's when the high CPU usage shows up.

 

I suppose that if you create a script in automator that deletes that file every time it wakes up from sleep, it would work normally... Or execute every time it wakes up from sleep "sudo pmset schedule cancelall" 🤷‍♂️

 

Something will have to be done, that beta 5 will take a few days, and I only have ventura installed on the computer 😀

@PoMpIs

Ive create a temporary fix

PmsetNoSchedule See Read Me

Works good on my HP EliteBook 840G4

 

CPU Usage after sleep

reboot + Login  Password Result this

 

 

Edited July 31, 2022 by chris1111

[D3v1L]

6 hours ago, PoMpIs said:

WTF!!! 😆

 

It's impossible, they come back a while after coming out of sleep..

 

I've been looking and this is the file:

 

HD > Library > Preferences > SystemConfiguration > com.apple.AutoWake.plist

 

 

I have deleted the file and as long as it does not go to sleep it does not create it again, but it is to put it to sleep and wake it up and it already has the same configuration😅

 

I have also tried to edit the file changing the dates to 2030... but when leaving sleep it creates other new entries automatically with the initial date

 

I'm going crazy 🤪

 

 

uhm......how it was? xD

 

 

 

ahahahah LoL xD 

 

mine after wake, all normal but strange things:

 

"the computer is scheduled to go to sleep automatically, if you do nothing it will go to sleep automatically in xx minutes and xx seconds" ... ...if I select "cancel" (Annulla) it will continue normally with normal work (normally)...

(tonight, it wake at 1:59am and it sleep at 2:00am like I schedule...so schedule setup via terminal is working ok)

 

Stay tuned for more Happy Days! (Weezer Buddy Holly from Arnold's docet on windows 95 clip xD LoL )

 

edit:

LoL much older than me xD ahahahahah

 

 

Edited July 31, 2022 by D3v1L

[Slice]

8 hours ago, prcmelo said:

@Slice Thanks for you help!!! But I'm getting the same problem with this CloverX64. All my Kexts are up to date. I'm sending my config.plist and boot log, thank you!!!

log.rtf 89.27 kB · 1 download config.plist 9.19 kB · 1 download

All looks good except:

1. I don't think you should use CsmVideoDxe.efi. It is for old cards not having UEFI BIOS.

2. The quirk EnableSafeModeSlide may cause Panic. Disable the quirk.

[Henties]

9 hours ago, eSaF said:

hopefully these bugs will be ironed out, so meanwhile just take it easy and Lean Back. 

I opt to disagree 😂 and would rephrase as follows:

 

"these bugs will be ironed out, so meanwhile just take it easy and Lean Back."

 

Greetings Henties  

[Henties]

7 hours ago, PoMpIs said:

Something will have to be done, that beta 5 will take a few days, and I only have ventura installed on the computer 😀

Wow, you are sure "living" on a knife's edge.

 

Greetings Henties

[Matgen84]

8 hours ago, SavageAUS said:

I have always been on developer updates.

I let the update happen and it all looks correct.

 

 

Hi @SavageAUS

Ventura Dev Beta 4 and Public Beta 2 have the same number version name : 13.0.22A5311f. 

[miliuco]

8 hours ago, chris1111 said:

@PoMpIs

Ive create a temporary fix

PmsetNoSchedule See Read Me

Works good on my HP EliteBook 840G4...

 

Thank you Chris. 

[PoMpIs]

9 hours ago, chris1111 said:

@PoMpIs

Ive create a temporary fix

PmsetNoSchedule See Read Me

Works good on my HP EliteBook 840G4

 

CPU Usage after sleep

reboot + Login  Password Result this

 

 

 

Thank you very much Chris1111 

 

PS: On the Lenovo 520s that problem still does not occur... I don't understand it

 

 

 

Edited July 31, 2022 by PoMpIs

[chris1111]

48 minutes ago, PoMpIs said:

 

Thank you very much Chris1111 

 

PS: On the Lenovo 520s that problem still does not occur... I don't understand it

 

@PoMpIs @miliuco

You're welcome it's a pleasure

 

[PoMpIs]

Has anyone tested if doing a clean installation of beta 4 stops the problem of high CPU usage by "powerd" from happening??

 

I did it today, and the operation is not like before, now it works like my Lenovo 520s... that is, those events are no longer generated when leaving sleep.

I only have this exactly the same as on the laptop...

 

 

Now I'm going to go out for a while and let it stay in sleep, and when I come back I'll check if it worked well.

[iGPU]

14 hours ago, chris1111 said:

@PoMpIs

Ive create a temporary fix

PmsetNoSchedule See Read Me

Works good on my HP EliteBook 840G4

 

CPU Usage after sleep

reboot + Login  Password Result this

 

 

 

 

Thanks, chris1111!

 

Power management notably better on my Z690 / i9 12900KF / Ventura ß4 (and fans are now quiet!):

 

[Slice]

1 hour ago, PoMpIs said:

Has anyone tested if doing a clean installation of beta 4 stops the problem of high CPU usage by "powerd" from happening??

 

I did it today, and the operation is not like before, now it works like my Lenovo 520s... that is, those events are no longer generated when leaving sleep.

I only have this exactly the same as on the laptop...

 

 

Now I'm going to go out for a while and let it stay in sleep, and when I come back I'll check if it worked well.

I installed beta 4 as an update to beta 3. Anyway I have no high power usage even after wake.

May be because of Clover?

[PoMpIs]

29 minutes ago, Slice said:

I installed beta 4 as an update to beta 3. Anyway I have no high power usage even after wake.

May be because of Clover?

 

Well, it could be, because I came back and it was suspended and when I woke it up, the events were not created with the other installation of Ventura that I have been updating since beta 1

 

This clean install stays the same after waking up from sleep:

 

 

🤷‍♂️

[Alex HQuest]

23 hours ago, Cyberdevs said:

Since when there were issues? I ask because i have installed up to dp 3 and didn't have much issues doin so. 

 

23 hours ago, Slice said:

I also have Ventura on Skylake CPU. 

The problem is Skylake graphics HD530.

 

Odd. I only asked since while the HD630 spoofing seemed to make installation go thru, by about 3/4 of the progress “Install macOS” hangs the machine while doing its wrap up, and the OS is never installed completely. Guess I'll poke around with my config, then - maybe whatever worked in Monterey doesn't play nicely as nicely with Ventura.

 

Device specs in my signature. Thanks, though.

 

 

 

Edited July 31, 2022 by Alex HQuest

[Anto65]

On 7/30/2022 at 1:36 PM, miliuco said:

No, I mean schedule to plan start, sleep... at a certain time, I can't find this feature in System Preferences >> Lock Screen, neither in Energy Saver.

 

However, Ventura Help says about Schedule:

"On your Mac, choose Apple menu > System Preferences, click Energy Saver, and then click Schedule."

 

In previous macOS:

I borrowed the app from Mrey  "System Preferences"  😆
It works perfectly on Ventura 

 

https://drive.google.com/file/d/1yxcaldstMQjF6Z3hMd2hfZvhX3J4B4de/view?usp=sharing  (... because it doesn't come from an identified developer 🙈)

set the stop at 19.25 and the awakening at 19.30 ... it works 

 

Edited July 31, 2022 by antuneddu

[Cyberdevs]

8 minutes ago, Alex HQuest said:

Odd. I only asked since while the HD630 spoofing seemed to make installation go thru, by about 3/4 of the progress “Install macOS” hangs the machine while doing its wrap up, and the OS is never installed completely.

 

Device specs in my signature.

Update your EFI and the kext to their latest, i've had some issues installing the 4th DP which got resolved by updating OC and the kexts to to their latest nightly versions on my KabyLake and AlderLake rigs I haven't tested it on my SkyLake tho.

[Alex HQuest]

4 minutes ago, Cyberdevs said:

Update your EFI and the kext to their latest, i've had some issues installing the 4th DP which got resolved by updating OC and the kexts to to their latest nightly versions on my KabyLake and AlderLake rigs I haven't tested it on my SkyLake tho.

Sorry, I should had stated that. I’ve got all OC code as fresh as of yesterday’s builds.

 

Do I still need that SklAsKbl whatever extension? Or was this included into WEG?

[Cyberdevs]

28 minutes ago, Alex HQuest said:

Sorry, I should had stated that. I’ve got all OC code as fresh as of yesterday’s builds.

 

Do I still need that SklAsKbl whatever extension? Or was this included into WEG?

AFIAK it was included in the WEG all you need to do is to add the correct iGPU info like ig-platform-id (of the closes KabyLake relative to your iGPU) and the device-id for instance for my HD530 (i7 6700K) I used the following settings:

But then again i haven't tested the latest beta so somethings might have changed in the lates beta (which I doubt)

[Slice]

11 minutes ago, Cyberdevs said:

AFIAK it was included in the WEG all you need to do is to add the correct iGPU info like ig-platform-id (of the closes KabyLake relative to your iGPU) and the device-id for instance for my HD530 (i7 6700K) I used the following settings:

But then again i haven't tested the latest beta so somethings might have changed in the lates beta (which I doubt)

I tested without WEG this two keys... Logically it is enough but panic.