Jump to content

Intel HD 530 issue


ichelash
 Share

16 posts in this topic

Recommended Posts

Hello everyone, I hope you all are doing okay.

Alright, so their is something very fishy with my hackintosh graphics, as you may know I have been battling the guys who have installed Ventura dev beta “I’m jealous “. Trying to fix this intel HD 530 on my hackintosh from Big Sur, Monterey & now Ventura beta.

The issue is the monitor going on power safe mode always even if I use the boot-args required to keep it online, my friend @Cyberdevs tested my EFI folder and it’s working great on his rig,  so my question is what’s is wrong with my rig? Someone? Anybody who has been through such issue? .

Last thing when that monitors goes on power safe mode..something seems to be working on the background because, it connects automatically with my phone’s hotspot via usb cable..so I don’t know what could be the problem with my rig, Using DVI to connect to the monitor, it doesn’t have hdmi, others are 2 display ports & vga. 
any idea how I can fix that will be appreciated 

 

ichelash

Link to comment
Share on other sites

The only thing I see here is...Why DVI? I believe that's the underlying issue here. It's actually an older type of video connector and has 5 times less bandwidth than DP or HDMI. To Apple this standard is antique and most certainly obsolete, so issues with this connector on modern macOS versions should be expected. As far as I'm aware, the only connectors that are natively supported within framebuffers in macOS are LVDS, DP and HDMI. 

If I were you trying to run macOS on this machine, this is where I'll start looking into; most likely you'll need a supported monitor. Sadly, It is what it is when it comes to Apple and the standards they support.

  • Thanks 1
Link to comment
Share on other sites

43 minutes ago, aben said:

The only thing I see here is...Why DVI? I believe that's the underlying issue here. It's actually an older type of video connector and has 5 times less bandwidth than DP or HDMI. To Apple this standard is antique and most certainly obsolete, so issues with this connector on modern macOS versions should be expected. As far as I'm aware, the only connectors that are natively supported within framebuffers in macOS are LVDS, DP and HDMI. 

If I were you trying to run macOS on this machine, this is where I'll start looking into; most likely you'll need a supported monitor. Sadly, It is what it is when it comes to Apple and the standards they support.

Thanks @aben I have noticed that, the issue might be the DVI, but I hope display ports might work

Link to comment
Share on other sites

I would expect DVI output to be Ok but it may require framebuffer patching.

Do you have another Hack or Mac from which you could access the Skylake's screen provided screen sharing is enabled of course? This would be to take an IOReg extract.

 

SKL FB 0x19120000 is a mobile layout which defines 3 x output ports:

ID: 19120000, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000110F
TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes)
Model name: Intel HD Graphics SKL CRB
Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[255] busId: 0x00, pipe: 0, type: 0x00000001, flags: 0x00000020 - ConnectorDummy
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP
FF000000 01000000 20000000
01050900 00040000 87010000
02040A00 00040000 87010000
  1. con0 defines a dummy output port
  2. con1 defines a DP output port
  3. con2 defines a DP output port

 

Of course, you cannot use a desktop SKL layout since all four of those are empty/connectionless framebuffers.

You could expect problems if your DVI port registers against con0 but only an IOReg extract would show that. Try to boot in VESA mode to check things out.

 

Can you please post a zipped copy of your EFI folder or at least a subset with config file + ACPI & kexts folder?

If your device properties are exactly as shown above, I invite you to fix the typo... <_< It may actually fix all your graphics problem.

 

HD530 iGPU of Intel i3-6100 carries device id 0x1912; as such, it's entirely useless and unnecessary to inject that as a property; but it does no harm of course.

Link to comment
Share on other sites

@ichelash

  1. OpenCor is outdated
  2. Config Errors
  3. Fix Device Properties
  4. Don't use OpenCore Configurator… it's trash. use OpenCOre Auxiliary Tools instead.
OCS: No schema for EnableForAll at 0 index, context <Quirks>!
OCS: No schema for EnableForAll at 6 index, context <Quirks>!
OCS: No schema for SkipCustomEntryCheck at 11 index, context <Boot>!
OCS: No schema for AllowNvramReset at 0 index, context <Security>!
OCS: No schema for AllowToggleSip at 2 index, context <Security>!
Serialisation returns 5 errors!

ACPI->Add[0]->Comment contains illegal character!
CheckACPI returns 1 error!

Original path: PciRoot(0x0/Pci(0x1c,0x0)/Pci(0x0,0x0)
Path after internal conversion: 
DeviceProperties->Add[0]->DevicePath is borked! Please check the information above!
CheckDeviceProperties returns 1 error!

Completed validating /Users/5t33z0/Downloads/EFI/OC/config.plist in 1 ms. Found 7 issues requiring attention.

 

Edited by 5T33Z0
  • Thanks 1
Link to comment
Share on other sites

@ichelash Nothing wrong with OCC, I use it all the time. And nothing wrong with using OC 0.8.0 for Monterey.

 

In your device property section, you incorrectly have:

  • PciRoot(0x0/Pci(0x1c,0x0)/Pci(0x0,0x0)

when it should be:

  • PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)

You're missing an essential ")" character...

 

In NVRAM section, you're using an incorrect value for SIP: replace 0x0FFF by 0x0FEF or you'll never get macOS updates.

Of course, you'll have to remove the -igfxvesa boot-arg to boot with graphics acceleration.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

9 minutes ago, Hervé said:

@ichelash Nothing wrong with OCC, I use it all the time. And nothing wrong with using OC 0.8.0 for Monterey.

 

In your device property section you incorrectly have:

  • PciRoot(0x0/Pci(0x1c,0x0)/Pci(0x0,0x0)

when it should be:

  • PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)

You're missing an essential ")" character...

 

In NVRAM section, you're using an incorrect value for SIP: replace 0x0FFF by 0FEF or you'll never get macOS updates.

that was for the BCM943602CS that you added on that config you sent me

Link to comment
Share on other sites

2 hours ago, 5T33Z0 said:

@ichelash OCC has no config validation included and can't integrate new Keys into GUI automatically, which causes conflicts. OCAT can. It can also update OpenCore and Kexts.

Have tried that using OCAT, but am guessing is the issue with dvi, have ordered a display cable I'll see how it goes.

Link to comment
Share on other sites

 Share

×
×
  • Create New...