Jump to content
3338 posts in this topic

Recommended Posts

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
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.

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.

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
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

8 minutes ago, ichelash said:

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

Sure here it is:

You're just gonna need to regenerate the SMBIOS info and use your own USBMap and settings.

 

Z170A Intel HD530 Ventura EFI.zip

 

So far so good:

image.png

  • Like 4
  • Thanks 1
15 minutes ago, Cyberdevs said:

Sure here it is:

You're just gonna need to regenerate the SMBIOS info and use your own USBMap and settings.

 

Z170A Intel HD530 Ventura EFI.zip 5.97 MB · 3 downloads

 

So far so good:

image.png

Thanks, I’m positive test 79 will be a success

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
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
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.

On 6/12/2022 at 5:29 PM, Dragster27 said:

 

I had the exact same issue... it turned out to be a few quirks I had set the wrong way in my config.plist...I've fixed it and got it working now.. Do the following:

 

1. Update all necessary kexts and OpenCore to latest version from https://dortania.github.io/builds/

2.   Backup your config.plist

3. Open your config.plist with OpenCore Configurator and use the config checker from the tools menu to check your configuration for your specific platform.

3. Make the recommended changes to you config plist and save, pay special attention in the suggested changes for the quirks.

4. Save your updated configuration and reboot.

5. If you are upgrading from an existing Monterey install, boot into Monterey and run the upgrade process again, if you're installing from USB boot with it and you should be good.

 

This worked for me to solve the issue.

 

Good luck,

Dragster.

 

 

@Dragster Thank you !  I followed all the steps including adding some Security Quirks ,OC checker suggested . Except for running the upgrade process again . Will try the USB install next. But so far no luck :(

 

 

Edited by rubenpp
change addressing
On 6/12/2022 at 11:31 PM, eSaF said:

Unfortunately until you sort out the correct files and kexts your system actually needs, there is not much anyone can do to help. I don't believe you need all those there, I suggest you find an already constructed and running Monterey/or other OS X  installed EFI Folder with near enough specs as your rig and we can work from there.

With your current setup can you boot any OS X version i.e Monterey or Big Sur and reach the Desktop? Which I think is highly unlikely judging by your files. Meanwhile I will look around and see if I can find a working EFI Folder for you.

@eSaF Appreciate all the help !  My current build  has been running  Monterey with the EFI I provided  , and has been OK even with all the beta releases until Ventura. Again thank you ! 

  • Like 1
11 hours ago, 5T33Z0 said:

 

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.

 

It is true that macOS 13's dyld shared cache no longer ships a non-AVX2 variant for the Intel side with the discontinuation of the famous 'Trash can" MacPro6,1 however if legacy x86 systems are able to successfully “run” macOS 13 via a post-install img from Apple Silicon (non x86), that means support for those x86 instruction set (non-AVX2) is clearly present (in dyld shared cache); thanks to Rosetta, which again is Apple’s planned offering (as part of their transition to Apple Silicon) to also help provide app developers using these ARM-based machines enough buffer period that would allow for a smooth transition of their apps to Apple Silicon as well while maintaining the necessary support for their x86 variant of the app to be able to run in parallel (via x86 instruction set present in Rosetta's dyld shared cache)

 

Basically, if Rosetta didn't exist OR had been updated to only support AVX2 instructions, none of these legacy systems would have seen macOS 13.

Edited by aben
3 hours ago, rubenpp said:

 

 

@Dragster Thank you !  I followed all the steps including adding some Security Quirks ,OC checker suggested . Except for running the upgrade process again . Will try the USB install next. But so far no luck :(

 

 

@Rubenpp No problem. try the install running the upgrade process again after doing the changes, otherwise it might not work. You can also try the installation via USB. 

 

Good luck,

Cheers.

D.

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