Contribute
Register

<< Solved >> Intel UHD 620 (Dell Inspiron 5584) and no acceleration or black screen

Status
Not open for further replies.
Joined
Jan 1, 2019
Messages
13
Motherboard
Dell Inspiron 5584
CPU
i5-8265U
Graphics
UHD 620
Mac
  1. iMac
I'm trying to get graphic acceleration to work on Intel UHD 620 and so far I'm getting either no acceleration or black screen during start-up of the system.

I'm using Lilu.kext and WhateverGreen.kext

AAPL,ig-platform-id 00001659

if I add to my Clover configuration device-id 16590000 I'm getting black screen. Have tried other values for device-id but either it results in no acceleration or black screen and KP.

I have attached debug info from gen_debug, screen shots from clover configurator and Hackintool
 

Attachments

  • 20190630_202852_resized.jpg
    20190630_202852_resized.jpg
    1.1 MB · Views: 556
  • 20190630_202857_resized.jpg
    20190630_202857_resized.jpg
    962.2 KB · Views: 669
  • 20190630_202902_resized.jpg
    20190630_202902_resized.jpg
    1.3 MB · Views: 507
  • debug_26590.zip
    2.9 MB · Views: 157
Try compiling latest WhateverGreen from source:
The latest commit should fix your problem, I believe.

Don't set a FakeID yourself, nor an ig-platform-id. Let WhateverGreen do that for you.

Make sure DVMT-prealloc is set to 64MB+ in the BIOS, otherwise patch the graphics kexts to allow 32MB (Can be done with WhateverGreen by injecting the required properties)
 
Last edited:
Not sure if it can work for your Whiskey Lake laptop - but spoofing Skylake as per guide has worked for my Kabylake UHD 620:
(see section "Problems with Kaby Lake Graphics" - mind adding lilucpu=8 kernel flag into config.plist /Boot/Arguments)

@ben9923 : idea if WhateverGreen latest commit limited to UHD 620 Whiskey Lake or also applied to UHD 620 kabylake ?
 
Not sure if it can work for your Whiskey Lake laptop - but spoofing Skylake as per guide has worked for my Kabylake UHD 620:
(see section "Problems with Kaby Lake Graphics" - mind adding lilucpu=8 kernel flag into config.plist /Boot/Arguments)

@ben9923 : idea if WhateverGreen latest commit limited to UHD 620 Whiskey Lake or also applied to UHD 620 kabylake ?
The latest commit only applies to the Whiskey Lake device (different device ID).
The Whiskey Lake device is spoofed as a Coffee Lake Iris Plus 655. Until this commit it was spoofed as a Kaby Lake HD620, which wasn't a good fit.

If you mean the Kaby Lake-R UHD 620 (0x5917), it's spoofed as a Kaby Lake HD 620 (0x5916) which is supported by macOS.
It's like that since the initial version of WhateverGreen (which included Intel).

There's no need to spoof a device ID yourself when using WhateverGreen, nor injecting an ig-platform-id. It's all done by WEG. You can override that, but usually it's not necessary.
Are you sure you really need spoofing Skylake? You should have better compatibility and performance with the Kaby Lake HD 620 drivers.
Read the FAQ here, 'General Recommendations' should cover everything you need to properly use WEG:
If you're not using the latest macOS available, I'd update the OS.
(If you're removing some Clover renames like GFX0 -> IGPU make sure your SSDTs match the original names. Shouldn't be necessary to remove those renames tho)

@Lukaszjg WhateverGreen 1.3.0 was released yesterday, it includes that fix.
 
I'm trying to get graphic acceleration to work on Intel UHD 620 and so far I'm getting either no acceleration or black screen during start-up of the system.

I'm using Lilu.kext and WhateverGreen.kext

AAPL,ig-platform-id 00001659

if I add to my Clover configuration device-id 16590000 I'm getting black screen. Have tried other values for device-id but either it results in no acceleration or black screen and KP.

I have attached debug info from gen_debug, screen shots from clover configurator and Hackintool
your device/properties in your config.plist is incomplete. there should be more values. look at screenshot here
you need to patch your DSDT then save the file in the same location replacing the non-patched. I'm not too sure about hd530 as im using uhd620. try using the Hackintool to create the Framebuffer patch. your device/properties should look similar to the attached pics.as I look at yours, device/properties is incomplete for Framebuffer injection
 
The latest commit only applies to the Whiskey Lake device (different device ID).
The Whiskey Lake device is spoofed as a Coffee Lake Iris Plus 655. Until this commit it was spoofed as a Kaby Lake HD620, which wasn't a good fit.

If you mean the Kaby Lake-R UHD 620 (0x5917), it's spoofed as a Kaby Lake HD 620 (0x5916) which is supported by macOS.
It's like that since the initial version of WhateverGreen (which included Intel).
Thanks for the Whiskey Lake explanation !

I had a pink screen issue with 10.14.1 when connecting a HDMI TV - that is why i went with the skylake spoof as per @Sniki guide (changing AAPL, ig-platform-id and device-id to skylake laptop 0x1916000)
 
Thanks for the Whiskey Lake explanation !

I had a pink screen issue with 10.14.1 when connecting a HDMI TV - that is why i went with the skylake spoof as per @Sniki guide (changing AAPL, ig-platform-id and device-id to skylake laptop 0x1916000)
Give the latest 10.14.5 a try, together with updated kexts. Hopefully you'll be able to use the Kaby Lake drivers instead, without such bugs :)
 
Give the latest 10.14.5 a try, together with updated kexts. Hopefully you'll be able to use the Kaby Lake drivers instead, without such bugs :)
Great and appreciate advise, it works, no more pink screen when connected to HDMI TV !

Just noted : need to set ig-platform-id and device-id because no acceleration when letting WEG doing by itself
Changed SMBIOS to 14,2 as suggested by hackintool
 

Attachments

  • WEG settings.png
    WEG settings.png
    68.6 KB · Views: 512
  • sys info.png
    sys info.png
    73.6 KB · Views: 614
Great and appreciate advise, it works, no more pink screen when connected to HDMI TV !

Just noted : need to set ig-platform-id and device-id because no acceleration when letting WEG doing by itself
Changed SMBIOS to 14,2 as suggested by hackintool
I think it's usually better to go with 14,1 (It has just IGPU, no Touch Bar IIRC).

The 0x5916 device-id should already be used by WEG, I guess you can remove this one.
Which ig-platform-id is selected by WEG when not setting your own? I thought 0x59160000 should be used automatically when using the 0x5916 device-id.

Can you attach a troubleshooting archive made without injecting device-id and ig-platform-id? :)
I wonder why it doesn't work without custom setup :think:
 
Can you attach a troubleshooting archive made without injecting device-id and ig-platform-id? :)
I wonder why it doesn't work without custom setup :think:
Hi, here are the PR file when no device-id and ig-platform-id WEG are injected
<09 00 a5 3e> ig-platform-id is automatically setted
 

Attachments

  • debug_25905.zip
    7.5 MB · Views: 217
Status
Not open for further replies.
Back
Top