Jump to content
23 posts in this topic

Recommended Posts

Hi, I was able to install macOS Ventura with no problems except one, and that is the graphics acceleration. Graphics acceleration was working in macOS Monterey before for me however. I've seen many people talking about spoofing the device id but i'm not sure how to do that.. Could anyone guide me on any possible solution for this mess?  

 

Specs: Dell Inspiron 3650

Intel Core i3-6100

8 GB RAM

image.png

 

EFI.zip

Edited by Alan Sojan
  • Like 1
Link to comment
https://www.insanelymac.com/forum/topic/356961-hackintosh-ventura-intel-hd-530/
Share on other sites

17 minutes ago, eSaF said:

Hi - May I ask if you installed Ventura on a disk that is connected externally i.e 'Hot Plugged' (USB connection)?

The reason I asked, if it is on an internal disk connected in a M.2 Slot or Sata connection, then something is not quite right with the configuration as the disk orange icon depicts an external connection and should be corrected.

All internal disks icons should be this colour (grey) and all external disks should be this colour (orange) as shown here on my machine.

Screenshot 2023-06-15 at 00.55.03.png

Yes, I installed macOS on an external hard disk. I'm going to connect it internally a bit later

13 hours ago, Alan Sojan said:

Hi, I was able to install macOS Ventura with no problems except one, and that is the graphics acceleration. Graphics acceleration was working in macOS Monterey before for me however. I've seen many people talking about spoofing the device id but i'm not sure how to do that.. Could anyone guide me on any possible solution for this mess?  

 

Specs: Dell Inspiron 3650

Intel Core i3-6100

8 GB RAM

image.png

 

EFI.zip 6.7 MB · 0 downloads

On checking this EFI, you still using skylake platform-id 00001219 and device-id 1B190000. You should change those to this (working on my Skylake) platform-id 00001259 and device-id 1B590000. All the best

image.png.f883bb29ead6e952e4b4cb70d8a29954.png

 

755298905_Screenshot2023-06-15at15_05_21.png.55ab4d797b9778156c1adda16406d0e3.png

1 hour ago, ichelash said:

On checking this EFI, you still using skylake platform-id 00001219 and device-id 1B190000. You should change those to this (working on my Skylake) platform-id 00001259 and device-id 1B590000. All the best

image.png.f883bb29ead6e952e4b4cb70d8a29954.png

 

755298905_Screenshot2023-06-15at15_05_21.png.55ab4d797b9778156c1adda16406d0e3.png

Hi, thanks for the reply. I tried this but now my monitor turns off after boot.(macOS still running in background but i cant see screen)

27 minutes ago, Alan Sojan said:

Hi, thanks for the reply. I tried this but now my monitor turns off after boot.(macOS still running in background but i cant see screen)

Which connector? HDMI or DP, my boot-args

igfxagdc=0 igfxonln=1 watchdog=0 -igfxblr  -igfxdump

Edited by ichelash
  • Like 1
30 minutes ago, ichelash said:

Which connector? HDMI or DP, my boot-args

igfxagdc=0 igfxonln=1 watchdog=0 -igfxblr  -igfxdump

I tried these boot-args and then just igfxonln=1 on its own. Both still result in turning my monitor off after boot.

Just now, PoMpIs said:

@Alan Sojan

 

Hello..

 

You spoke to me on youtube 😄. ... Tomorrow I'll upload my EFI to see if it works for you...

 

Now I can't because I'm in bed 😴

Hi, I'm hoping it works. Thank you!

  • Like 1
20 hours ago, PoMpIs said:

 

I had a copy on the NAS 😁.. the one I used to install Sonoma Beta 1... has a random serial, use yours. 

 

https://pompis.duckdns.org/9e9afbff256b

It didn't work sadly. Thank you tho!

 

@Alan Sojan If you rely on the iGPU for driving a display, reinstalling Skylake drivers with OpenCore Legacy Patcher is probably the better solution: https://github.com/5T33Z0/OC-Little-Translated/blob/main/14_OCLP_Wintel/Skylake_Ventura.md#option-2-installing-macos-ventura-with-root-patches

  • Like 1

Just reminding everyone in this thread that we all learned in this thread that the OP's i3-6100 behaves like a P530 (it does not patch the same way as the i5 and i7).

 

EDIT: See here.

 

EDIT2: This thread might help.

Edited by deeveedee
  • Like 1

@cankiulascmnfye I'm never one to say that there is only one way to solve a problem.  This thread solved it without OCLP.  The OP's i3-6100 patches like a P530.

 

It is very possible that OCLP is another option.

 

EDIT: @cankiulascmnfye I was re-reading this thread and see that the OP of that thread did try OCLP.  I can't tell, but it is possible that the OP of that threaded needed the device-id spoof (device-id: <26590000>) in addition to OCLP.

Edited by deeveedee
  • Like 2
  • 1 month later...

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.

×
×
  • Create New...