Alan Sojan Posted June 14 Share Posted June 14 (edited) 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 EFI.zip Edited June 15 by Alan Sojan 1 Quote Link to comment Share on other sites More sharing options...
eSaF Posted June 14 Share Posted June 14 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. 1 Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted June 15 Author Share Posted June 15 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. Yes, I installed macOS on an external hard disk. I'm going to connect it internally a bit later 1 Quote Link to comment Share on other sites More sharing options...
ichelash Posted June 15 Share Posted June 15 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 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 Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted June 15 Author Share Posted June 15 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 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) Quote Link to comment Share on other sites More sharing options...
ichelash Posted June 15 Share Posted June 15 (edited) 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 June 15 by ichelash 1 Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted June 15 Author Share Posted June 15 2 minutes ago, ichelash said: Which connector? HDMI or DP HDMI Quote Link to comment Share on other sites More sharing options...
ichelash Posted June 15 Share Posted June 15 3 minutes ago, Alan Sojan said: HDMI Add this to boot-arg on your config plist igfxonln=1 1 Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted June 15 Author Share Posted June 15 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. Quote Link to comment Share on other sites More sharing options...
ichelash Posted June 15 Share Posted June 15 23 minutes ago, Alan Sojan said: I tried these boot-args and then just igfxonln=1 on its own. Both still result in turning my monitor off after boot. Did reset nvram? Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted June 15 Author Share Posted June 15 (edited) 13 minutes ago, ichelash said: Did reset nvram? Yes, every time i made sure to do this. Edited June 15 by Alan Sojan Quote Link to comment Share on other sites More sharing options...
ichelash Posted June 15 Share Posted June 15 39 minutes ago, Alan Sojan said: Yes, every time i made sure to do this. What's your reason of using iMac20,1 smbios? Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted June 15 Author Share Posted June 15 2 hours ago, ichelash said: What's your reason of using iMac20,1 smbios? It was to upgrade to macOS Ventura. Now I have changed it Quote Link to comment Share on other sites More sharing options...
ichelash Posted June 15 Share Posted June 15 1 hour ago, Alan Sojan said: It was to upgrade to macOS Ventura. Now I have changed it Even so, Ventura Suitable Smbios is for Skylake is iMac18,1/2, and for Sonoma iMac19,1/2..anyways hope that iMac20,1 works for you. 1 Quote Link to comment Share on other sites More sharing options...
PoMpIs Posted June 15 Share Posted June 15 @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 😴 Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted June 15 Author Share Posted June 15 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! 1 Quote Link to comment Share on other sites More sharing options...
PoMpIs Posted June 15 Share Posted June 15 21 minutes ago, Alan Sojan said: Hi, I'm hoping it works. Thank you! 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 1 Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted June 16 Author Share Posted June 16 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! Quote Link to comment Share on other sites More sharing options...
cankiulascmnfye Posted June 16 Share Posted June 16 @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 1 Quote Link to comment Share on other sites More sharing options...
deeveedee Posted June 17 Share Posted June 17 (edited) 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 June 17 by deeveedee 1 Quote Link to comment Share on other sites More sharing options...
cankiulascmnfye Posted June 17 Share Posted June 17 I think installing the Skylake drivers with OCLP and using a device-id to spoof as HD 530 should do the trick. 1 Quote Link to comment Share on other sites More sharing options...
deeveedee Posted June 17 Share Posted June 17 (edited) @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 June 17 by deeveedee 2 Quote Link to comment Share on other sites More sharing options...
Terminator2023 Posted July 26 Share Posted July 26 Hey, maybe you still have efi for the asrock h110m board I have the same problem for a few days I can't put the graphics on my feet Quote Link to comment Share on other sites More sharing options...
Terminator2023 Posted July 26 Share Posted July 26 I only have an i3 6100t processor Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.