Jump to content

[pre-release] macOS Ventura


3,556 posts in this topic

Recommended Posts

8 minutes ago, ichelash said:

Sadly can’t go past this..monitor’s goes to power safe mode..and that’s it. 

725C316A-718A-4C16-9800-1893A1692441.jpeg

You should set Video in your BIOS: first boot by IGPU without multiple monitor

Or remove GT-710 adaptor which may interfere its booting to HD 530.

Edited by jsl2000
Link to comment
Share on other sites

1 minute ago, jsl2000 said:

You should set Video in your BIOS: IGPU without multiple monitor

Or remove GT-710 adaptor which may interfere its booting to HD 530.

Have removed the GT 710, no peripherals available , just mouse keyboard that’s all 

Link to comment
Share on other sites

19 minutes ago, ichelash said:

Sadly can’t go past this..monitor’s goes to power safe mode..and that’s it. 

I have the same issue on my SkyLake (Intel HD530) rig, after so many tries it will eventually boot into macOS but with no acceleration, system detects the iGPU with full amount of VRAM but it simple doesn't work.

When I remove everything except for AAPL,ig-platform-id and  device-id the error goes away but I still have no acceleration.

  • Like 1
Link to comment
Share on other sites

3 minutes ago, Cyberdevs said:

I have the same issue on my SkyLake (Intel HD530) rig, after so many tries it will eventually boot into macOS but with no acceleration, system detects the iGPU with full amount of VRAM but it simple doesn't work.

When I remove everything except for AAPL,ig-platform-id and  device-id the error goes away but I still have no acceleration.

What seems to be the cause of this issue? Even using the KBL settings it does not want to work.

Link to comment
Share on other sites

Guest 5T33Z0
3 hours ago, aben said:


AFAIK, non-AVX2 instruction set (pre Haswell) do exist in Apple Silicon - in Rosetta (binary translator allowing x86 instructions to be compatible with Apple Silicon). Fortunately, Apple did not update Rosetta to AVX2 (Haswell and above) thus allowing a back door (albeit cumbersome) for macOS 13 to be installed on these legacy Intel systems.

 

From my understanding the x86 variant of Ventura uses AVX2 for the dylyd chache while the M1 versions doesn't, so that's why the swapping trick works. It wouldn't make much sense to use a "middle-man technology" like rosetta to implement AVX2 and use it for caching on M1 because it would be super inefficient.

Link to comment
Share on other sites

1 hour ago, Sygey02 said:

Hi! I removed the extra stuff from Config file, and I confirm you are right , it boots fine without changes I made with new OC version and updated kext.

Thank you for the feedback, so now we can add you to the success list of 'Removal of extra 2 lines of run-efi-updater=no' to the config.plist.

Hopefully @Cyberdevs will see your post and move it to that Thread which will make it easy for others to find.

Edited by eSaF
  • Like 4
  • Thanks 1
Link to comment
Share on other sites

25 minutes ago, ilcondannato said:

Anyone have start Ventura with coffee lake desktop with MacPro7,1 smbios?

No, I have tried and macOS doesn't boot, I don't know why. iMac20,2 and 19,1 are fine.

Link to comment
Share on other sites

I finally got my SkyLake Graphics working on my desktop. I don't know what exactly happened because I've tested the same settings several times to no avail but this time it worked. Maybe because I did a clean install or maybe it was something else. I don't know, but it works :)

Haven't tested the graphics thoroughly but it'll do for now :D

Although there's a glitch when macOS loads, screen will lose signal but after a while it turns back on and sometimes it won't turn back on.

 

@ichelash

CPU: Intel Core i7 6700

iGPU: Intel HD 530

AAPL,ig-platform-id: 00001259

device-id: 12590000

SMBIOS: iMac18,1

image.png

  • Like 5
Link to comment
Share on other sites

8 minutes ago, Cyberdevs said:

I finally got my SkyLake Graphics working on my desktop. I don't know what exactly happened because I've tested the same settings several times to no avail but this time it worked. Maybe because I did a clean install or maybe it was something else. I don't know, but it works :)

Haven't tested the graphics thoroughly but it'll do for now :D

Although there's a glitch when macOS loads, screen will lose signal but after a while it turns back on and sometimes it won't turn back on.

 

@ichelash

CPU: Intel Core i7 6700

iGPU: Intel HD 530

AAPL,ig-platform-id: 00001259

device-id: 12590000

SMBIOS: iMac18,1

image.png

Test 78 was a miss also..please can you send me you EFI @Cyberdevs I try with it on test 79, kindly

Link to comment
Share on other sites

4 minutes ago, Cyberdevs said:

Do you still get the same error?

Hold on..the issue is hackintool detects the Intel HD 530, but it doesn’t go past boot screen, takes like a minute or less, then the monitor goes to power safe mode

Link to comment
Share on other sites

1 hour ago, miliuco said:

No, I have tried and macOS doesn't boot, I don't know why. iMac20,2 and 19,1 are fine.

Tnx anyway...but unfurtunately i need mp71 ...stay with Monterey 4 now 

Link to comment
Share on other sites

4 minutes ago, ichelash said:

Hold on..the issue is hackintool detects the Intel HD 530, but it doesn’t go past boot screen, takes like a minute or less, then the monitor goes to power safe mode

With the EFI folder I posted there's no retrying on my rigs, the boot process is just normal, I did try to update the OC and the kexts but it went straight back to retrying issue.

  • Like 2
Link to comment
Share on other sites

Nice!

Second SkyLake rig and it's not glitching like the first one.

 

CPU: Intel Core i7 6700K

iGPU: Intel HD 530

AAPL,ig-platform-id: 00001259

device-id: 12590000

SMBIOS: iMac18,1

 

 

Screen Shot 2022-06-15 at 1.25.04 PM.png

  • Like 6
Link to comment
Share on other sites

On 6/15/2022 at 11:59 PM, Hervé said:

Of course! KBL layout 0x591B0000 is a mobile framebuffer... 'cannot understand why you went for that.

 

Make sure to:

  1. use the appropriate desktop one
  2. identify the output port (i.e. connector) against which your DP screen registers (using apps such IORegistryExplorer)

 

Recommended KBL desktop framebuffer is 0x59120000:

ID: 59120000, STOLEN: 38 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000110B
TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 115 MB, MAX OVERALL: 116 MB (122171392 bytes)
Model name: Intel HD Graphics KBL CRB
Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz
Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP
[3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP
01050900 00040000 87010000
02040A00 00040000 87010000
03060A00 00040000 87010000

Of course, you'll need the appropriate SMBIOS too.

Thanks for your help and advice.

But I have trued with KBL desktop framebuffer is 0x59120000, but unfortunately always got blank screen.

Changed to KBL mobile framebuffer is 0x591B0000 it can boot to desktop smoothly at Ventura without any errors.

The only issue is unable to enable DP/HDMI audio from HD 530, but ALC-662 is working.

[Solved]

HDMI audio can be enabled now after disabled SkylakeInjector.kext.

On 6/16/2022 at 4:16 AM, ichelash said:

DVI, have remove the Nvidia card from the Computer.

Can you try using KBL desktop framebuffer is 0x59120000 instead of KBL mobile framebuffer is 0x591B0000 ?

Mine need KBL mobile framebuffer is 0x591B0000 to be working.

Screen Shot 2022-06-17 at 7.07.26 AM.png

Edited by jsl2000
Link to comment
Share on other sites

3 minutes ago, jsl2000 said:

Thanks for your help and advice.

But I have trued with KBL desktop framebuffer is 0x59120000, but unfortunately always got blank screen.

Changed to KBL laptop framebuffer is 0x591B0000 it can boot to desktop smoothly at Ventura without any errors.

The only issue is unable to enable DP/HDMI audio from HD 530, but ALC-662 is working.

Can you try using KBL desktop framebuffer is 0x59120000 instead of KBL laptop framebuffer is 0x591B0000 ?

Mine need KBL laptop framebuffer is 0x591B0000 to be working.

Already tried that, but nothing happens..boots up nicely, you choose install Ventura...then after something like 30s ec, monitor goes to power safe mode, and it won't wake again.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...