Contribute
Register

Black screen Intel HD 530 on Mojave after patching Framebuffer

Status
Not open for further replies.
Joined
Dec 10, 2014
Messages
79
Motherboard
SONY VAIO VPCEA46FG
CPU
i5-480M
Graphics
HD 5470M
Mobile Phone
  1. iOS
Just upgraded from Sierra to Mojave on my Skylake i3 6100 with Intel HD 530 Its a Dell Optiplex 3046 system.

In Sierra, I got full graphics acceleration by this patch, as there was no option to set DVMT from bios in my mobo.


Comment: 0x19160000/etc, 19MB framebuffer 9MB cursor bytes (credit RehabMan) Name: AppleIntelSKLGraphicsFramebuffer Find: 01030303 00002002 00005001 Replace: 01030303 00003001 00009000

But as of now the fly kext patching from clover is no more for Mojave,
I followed the Intel Framebuffer patching guide using Whatever Green and Liu.

Here is my configuration:
Screenshot 2019-01-10 at 4.27.06 PM.png


This is the same patch which did the trick for me in Sierra
But on Mojave, this takes me to a black screen. I doubt something is wrong with the port conf, please help.
Attaching my config.plist.
 

Attachments

  • config-fbpatch copy.plist
    5.9 KB · Views: 303
Instead of using find and replace you could try setting your stolenmem (19mb) and fbmem (9mb) manually, you'll have to convert it from mb to bytes like shown here: #50

Tried this with Whatever green and Lilu in L/E & S/L/E also in Clover/kexts/other but I get a KP.
Screenshot 2019-01-11 at 11.06.27 AM.png


Here is the content of the KP
Fri Jan 11 10:34:54 2019 *** Panic Report *** panic(cpu 1 caller 0xffffff7f94377c25): assertmsg@/Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-12.4.7.1/Common/IONDRV/Intel/SKL/AppleIntelFramebuffer/AppleIntelController.cpp:26588 Backtrace (CPU 1), Frame : Return Address 0xffffff90b4d53aa0 : 0xffffff80129aeafd 0xffffff90b4d53af0 : 0xffffff8012ae85a3 0xffffff90b4d53b30 : 0xffffff8012ad9fca 0xffffff90b4d53ba0 : 0xffffff801295bca0 0xffffff90b4d53bc0 : 0xffffff80129ae517 0xffffff90b4d53ce0 : 0xffffff80129ae363 0xffffff90b4d53d50 : 0xffffff7f94377c25 0xffffff90b4d53db0 : 0xffffff7f94374c0f 0xffffff90b4d53e40 : 0xffffff801302c65b 0xffffff90b4d53e80 : 0xffffff801302c3a1 0xffffff90b4d53f00 : 0xffffff801302b8f7 0xffffff90b4d53f50 : 0xffffff801302d3c6 0xffffff90b4d53fa0 : 0xffffff801295b0ce Kernel Extensions in backtrace: com.apple.driver.AppleIntelSKLGraphicsFramebuffer(12.0.4)[C5248107-B7E9-3EE3-9EB1-D36B98D01FAE]@0xffffff7f9434d000->0xffffff7f94540fff dependency: com.apple.iokit.IOPCIFamily(2.9)[7EA30FDD-A2FB-390F-99DD-42BC19691BB4]@0xffffff7f93295000 dependency: com.apple.iokit.IOACPIFamily(1.4)[99A8A054-9F64-3FB8-BB1D-5973F8AB04A1]@0xffffff7f93310000 dependency: com.apple.iokit.IOAcceleratorFamily2(404.2.2)[FA92A03C-F113-384A-9B1F-B2C52DE7F4D2]@0xffffff7f94298000 dependency: com.apple.iokit.IOReportFamily(47)[75A625B5-0DEB-343A-A723-9D72533F098C]@0xffffff7f93f8d000 dependency: com.apple.AppleGraphicsDeviceControl(3.28.4)[400C2E21-0880-36D7-AC5E-6B9BC885F158]@0xffffff7f93f1f000 dependency: com.apple.iokit.IOGraphicsFamily(530.14)[C5617AC3-A68D-36CE-AC22-7C7C81318961]@0xffffff7f93c06000 BSD process name corresponding to current thread: kernel_task Boot args: -v dart=0 nv_disable=1 Mac OS version: 18C54
 
WEG and Lilu should be in kext/other OR L/E, as S/L/E might get overwritten during updates.

Memory should be added as integers, try the attached config.

I'm a bit confused about your plattform-id. Your old patch was using a 1916 plattform id (which is for Intel 520). Now your using 1912 (which is correct for 530). This could be something to look into if the above config doesn't work.
 

Attachments

  • config_ironman2.plist
    5.9 KB · Views: 280
WEG and Lilu should be in kext/other OR L/E, as S/L/E might get overwritten during updates.

Memory should be added as integers, try the attached config.

I'm a bit confused about your platform-id. Your old patch was using a 1916 platform id (which is for Intel 520). Now your using 1912 (which is correct for 530). This could be something to look into if the above config doesn't work.

For my old patch I was injecting the correct platform id (1912) via Clover inject intel = yes option, Rehab man advised me to use that replace patch. and it worked. Please see this thread.

I tried with the configuration above - now I'm not getting a KP but black screen(i think earlier KP was because the memory values were not integers as you said)

I can see from the verbose that the IGPU gets registered successfully, but then goes to a black screen then display goes to power saving mode. BTW I'm using VGA connection.

Please see the next post for more info on connectors.
 
Last edited:
Here is some more info from the Intel framebuffer patcher - which I ran on the working Intel HD 530 running Sierra with full acceleration.
In there it looks like the active monitor (VGA) is connected to index 3 with bus-id 0x06.
I also tried changing that bus-id type to VGA for Mojave - but it's not working same black screen error.

Screenshots below are from the working Intel HD 530 on the same machine running Sierra.

Screen Shot 2019-01-11 at 11.02.25 AM.png


Screen Shot 2019-01-11 at 11.01.13 AM.png
 
I just realised FB-Patcher advises to spoof the 16190000 Device ID. Maybe try that first before messing around with the connector type.

What I would try after that is setting all ports to VGA and after that disabling all ports you don't need.
 
I just realised FB-Patcher advises to spoof the 16190000 Device ID. Maybe try that first before messing around with the connector type.

What I would try after that is setting all ports to VGA and after that disabling all ports you don't need.
Okay, spoofing device id means changing the device id to 16190000 instead of 12190000 which im using now?
 
In there it looks like the active monitor (VGA) is connected to index 3 with bus-id 0x06.
I also tried changing that bus-id type to VGA for Mojave - but it's not working same black screen error.

Bus ID and connector type not important for VGA port, need AGDP patch on Mojave, even SMBIOS iMac14,2 AGDP config value is set to none, still not work for me, for SKL use ig-platform-id 0x193B0005, all 5/6/7 ports work.
Try below patch should work.

1547209474015.png
 
Status
Not open for further replies.
Back
Top