Jump to content

Intel HD 530 Monterey


Alan Sojan
 Share

234 posts in this topic

Recommended Posts

On 5/18/2023 at 8:26 PM, Peckamal said:

Hello, I used the EFI uploaded by the thread founder, everything seems to work for me except for one thing and that is the sound, the system does not even detect the sound card, I have a dell optiplex 7050 i5 6500 Intel HD 530, do you have any advice on how to make the sound work? Thank you

You can Post your EFI Here 

  • Like 1
Link to comment
Share on other sites

2 hours ago, Peckamal said:

Here you have it

I don't know if this will fix the problem you're having but worth a try.

In your config.plist UEFI/Audio/AudioCodec, instead of '1' try '0' (see attached) and as long as your alcid value data is correct I am hoping this will fix the problem.

Also have a look in Hackintool after you make the change to see if any semblance of Audio show up.

Don't forget to clear Nvram on reboot.

Good luck.

Screenshot 2023-05-20 at 20.10.24.png

  • Like 1
Link to comment
Share on other sites

14 minutes ago, eSaF said:

I don't know if this will fix the problem you're having but worth a try.

In your config.plist UEFI/Audio/AudioCodec, instead of '1' try '0' (see attached) and as long as your alcid value data is correct I am hoping this will fix the problem.

Also have a look in Hackintool after you make the change to see if any semblance of Audio show up.

Don't forget to clear Nvram on reboot.

Good luck.

Screenshot 2023-05-20 at 20.10.24.png

Thanks for another tip but it doesn't work

  • Sad 1
Link to comment
Share on other sites

Hello, I have another thing, and that is that today we installed Monterey on a friend's HP ProDesk 600 G2 SFF after several attempts, everything works and the sound works, but the problem is that it has 2xDP and 1x VGA output, but only 1 DP works. Don't you know what should be set or changed in the config so that the last outputs are also sent to the monitor? Thank you very much

IMG_1476.jpeg

Link to comment
Share on other sites

@Peckamal I'm not sure which SMBIOS macModel that you chose for your rig (e.g. macmini8,1), so these are just some observations that might help you:

  • You have chosen AAPL,ig-platform-id 0x19120000.  As indicated here, this framebuffer definition specifies the following port types (see full framebuffer definition below):
    con0: <01000000> dummy port (see port types here) - no physical port
    con1: <00040000> DisplayPort
    con2: <00040000> DisplayPort
  • Your DeviceProperties patches change con1 and con2 port types to <00080000> which is HDMI.  These probably work with DP as well, but may not work with VGA.
  • Your DeviceProperties patch con3 which is not defined in your case.  You can remove your con3 patches
  • Without knowing the mapping of your physical connectors to your logical connectors (con0, con1, con2) and without knowing which physical connector works when connected to your monitor, I'm guessing that the non-working physical connector corresponds to con0 which your AAPL,ig-platform-id defines as "dummy."  If that's the case, you will need to change the definition of con0-type in the same way that you changed the definition of con1 and con2 types.  You may be able to add DeviceProperty framebuffer-con0-type = <00080000> (to be consistent with your other patches) which specify type HDMI even though you are using DP.  Let's start with HDMI for the initial test and if that doesn't work, we'll revisit.  Here's where it gets tricky, logical framebuffer definitions have indices and busids. Your chosen AAPL,ig-platform-id sets the index of con0 as FF (disabling the port).  You will need to change the index of con0.  Since con1 has index 1 and con2 has index 2, you can try setting con0 to index = 3 with the DeviceProperty framebuffer-con0-index = <03000000>.  But in your AAPL,ig-platform-id, con0 has busId 0x00 which may also disable the physical port, so you may need to change con0 busId.  busIds 0x05 and 0x04 are taken, so you can try setting con0 busId = 0x02 with the DeviceProperty framebuffer-con0-busid = <02000000>
  • Each logical connector con0, con1, con2 has flags that affect connector behavior.  Your chosen AAPL,ig-platform-id sets con0 flags <0x00000020> which will probably not produce a working connector.  For consistency with the other flag definitions of con1 and con2, set the flags for con0 to 0x00000187 using DeviceProperty framebuffer-con0-flags = <87010000>
  • Your chosen framebuffer specifies con0 pipe as 0.  This may not work, so try setting framebuffer-con0-pipe = <0b000000>
  • You may find that your displays don't all work simultaneosly and they may not wake up after sleep, so you may need additional device properties.   For now, test this by adding the following boot-args: darkwake=2 igfxonln=1 igfxagdc=0

In summary, add the following DeviceProperties to your config.plist:

  • framebuffer-con0-type = <00080000>
  •  framebuffer-con0-index = <03000000>
  • framebuffer-con0-busid = <02000000>
  • framebuffer-con0-flags = <87010000>
  • framebuffer-con0-pipe = <0b000000>
  • frambuffer-con0-enable = <01000000>

and add the following boot-args to your config.plist

  • darkwake=2 igfxonln=1 igfxagdc=0

 

I'm only relaying to you what I learned while patching my hack (which you know about here).  Patiently read about my HackMini8,1 (starting with the fiirst post) to learn more.

 

0x19120000 Framebuffer definition

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

 

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

3 hours ago, deeveedee said:

@Peckamal I'm not sure which SMBIOS macModel that you chose for your rig (e.g. macmini8,1), so these are just some observations that might help you:

  • You have chosen AAPL,ig-platform-id 0x19120000.  As indicated here, this framebuffer definition specifies the following port types (see full framebuffer definition below):
    con0: <01000000> dummy port (see port types here) - no physical port
    con1: <00040000> DisplayPort
    con2: <00040000> DisplayPort
  • Your DeviceProperties patches change con1 and con2 port types to <00080000> which is HDMI.  These probably work with DP as well, but may not work with VGA.
  • Your DeviceProperties patch con3 which is not defined in your case.  You can remove your con3 patches
  • Without knowing the mapping of your physical connectors to your logical connectors (con0, con1, con2) and without knowing which physical connector works when connected to your monitor, I'm guessing that the non-working physical connector corresponds to con0 which your AAPL,ig-platform-id defines as "dummy."  If that's the case, you will need to change the definition of con0-type in the same way that you changed the definition of con1 and con2 types.  You may be able to add DeviceProperty framebuffer-con0-type = <00080000> (to be consistent with your other patches) which specify type HDMI even though you are using DP.  Let's start with HDMI for the initial test and if that doesn't work, we'll revisit.  Here's where it gets tricky, logical framebuffer definitions have indices and busids. Your chosen AAPL,ig-platform-id sets the index of con0 as FF (disabling the port).  You will need to change the index of con0.  Since con1 has index 1 and con2 has index 2, you can try setting con0 to index = 3 with the DeviceProperty framebuffer-con0-index = <03000000>.  But in your AAPL,ig-platform-id, con0 has busId 0x00 which may also disable the physical port, so you may need to change con0 busId.  busIds 0x05 and 0x04 are taken, so you can try setting con0 busId = 0x02 with the DeviceProperty framebuffer-con0-busid = <02000000>
  • Each logical connector con0, con1, con2 has flags that affect connector behavior.  Your chosen AAPL,ig-platform-id sets con0 flags <0x00000020> which will probably not produce a working connector.  For consistency with the other flag definitions of con1 and con2, set the flags for con0 to 0x00000187 using DeviceProperty framebuffer-con0-flags = <87010000>
  • Your chosen framebuffer specifies con0 pipe as 0.  This may not work, so try setting framebuffer-con0-pipe = <0b000000>
  • You may find that your displays don't all work simultaneosly and they may not wake up after sleep, so you may need additional device properties.   For now, test this by adding the following boot-args: darkwake=2 igfxonln=1 igfxagdc=0

In summary, add the following DeviceProperties to your config.plist:

  • framebuffer-con0-type = <00080000>
  •  framebuffer-con0-index = <03000000>
  • framebuffer-con0-busid = <02000000>
  • framebuffer-con0-flags = <87010000>
  • framebuffer-con0-pipe = <0b000000>
  • frambuffer-con0-enable = <01000000>

and add the following boot-args to your config.plist

  • darkwake=2 igfxonln=1 igfxagdc=0

 

I'm only relaying to you what I learned while patching my hack (which you know about here).  Patiently read about my HackMini8,1 (starting with the fiirst post) to learn more.

 

0x19120000 Framebuffer definition

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

 

Hi, thanks for everything, I'm at work now, I'll try it when I get home, it's set as iMac17,1 Thank you

Link to comment
Share on other sites

9 hours ago, Peckamal said:

Hello, I have another thing, and that is that today we installed Monterey on a friend's HP ProDesk 600 G2 SFF after several attempts, everything works and the sound works, but the problem is that it has 2xDP and 1x VGA output, but only 1 DP works. Don't you know what should be set or changed in the config so that the last outputs are also sent to the monitor? Thank you very much

IMG_1476.jpeg

Just use only one Property like AAPL,ig-platform-id & reset NVRAM 

Screenshot 2023-05-22 at 10.15.59 AM.png

  • Like 2
Link to comment
Share on other sites

3 hours ago, datafeedexpert said:

Just use only one Property like AAPL,ig-platform-id & reset NVRAM 

Screenshot 2023-05-22 at 10.15.59 AM.png

Thank you, I will try it at home from work, if I wanted to install Ventura, can I use the current EFI? or do I have to do something else? Thank you

Link to comment
Share on other sites

@Peckamal , @datafeedexpert 's suggestion to simplify is always good.  I assumed that you had an i3 like the OP and needed to spoof device-id to 0x191b. If you have an i5 or i7, then you shouldn't spoof the device-id and should remove device-id from your DeviceProperties.  If you don't have an i3 (and you do have an i5 or i7), you may want to simply remove device-id from your DeviceProperties, reboot, reset NVRAM and test with Monterey or older macOS.

 

If you are running Ventura, then you need to spoof iGPU as Kabylake as indicated here and demonstrated by @Rocky12 here.

 

EDIT: Keep my overly-complex example in your back pocket just in case the simple solution doesn't work for you.  I have found these HP Minis to behave more like NUCS and laptops than desktops, so the simpler approaches that work with desktops may not work and you'll need to add some extra patches.  Looking forward to seeing your progress.

 

EDIT2: Also see slice's comment here (for Monterey or older).  You can try other frame buffers (other AAPL,ig-platform-ids) that have different connector types already defined.  You can try multiple framebuffers for Ventura, too, but again, you need to spoof a Kabylake iGPU.

 

EDIT3: Sorry to be long-winded, but if you are installing Ventura, you may just want to start testing with Rocky12's solution here.

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

@Peckamal Please post your current EFI.  Also post your G2 Mini's CPU, the macOS version you are testing and a photo showing which physical port is working.

Edited by deeveedee
Link to comment
Share on other sites

Hi

3 minutes ago, deeveedee said:

@Peckamal Please post your current EFI.  Also post your G2 Mini's CPU, the macOS version you are testing and a photo showing which physical port is working.

Hi, i5 6500 my EFI 

EFI.zip

6 minutes ago, deeveedee said:

@Peckamal Please post your current EFI.  Also post your G2 Mini's CPU, the macOS version you are testing and a photo showing which physical port is working.

I'm sorry for the photo 

IMG_1478.jpeg

Link to comment
Share on other sites

@Peckamal Thank you for posting the details.  You initially posted your question in my EliteDesk 800 G4 Mini thread, so I assumed you were asking about a HP 600 Mini.  I should have more carefully read your post earlier in this thread to see that it's an SFF (not a Mini).  What is the chipset in your PC?

 

EDIT: The EFI you posted doesn't have any of the discussed changes to your DeviceProperties.  Also, please tell us what macOS version you are testing.

Edited by deeveedee
  • Like 2
Link to comment
Share on other sites

10 minutes ago, deeveedee said:

@Peckamal Thank you for posting the details.  You initially posted your question in my EliteDesk 800 G4 Mini thread, so I assumed you were asking about a HP 600 Mini.  I should have more carefully read your post earlier in this thread to see that it's an SFF (not a Mini).  What is the chipset in your PC?

 

EDIT: The EFI you posted doesn't have any of the discussed changes to your DeviceProperties.  Also, please tell us what macOS version you are testing.

Sorry, Monterey 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...