Contribute
Register
Status
Not open for further replies.
Your laptop is equipped with an Intel Core i7-8550U which is a Kaby Lake R processor, so you should use the AppleIntelKBLGraphicsFramebuffer driver.

I checked your panic logs, and it turned out that you were using the frame buffer driver for Skylake at some day and the one for Kaby Lake at the other day.

Make sure that you do not spoof as a Skylake/Coffee Lake card and inject a proper ig-platform-id for the Kaby Lake framebuffer driver.

And make sure that your Kaby Lake framebuffer driver is the stock one (I.e. not modified).

Once you finished the above steps, report what happens to the internal screen and attach the latest debug files, so that I could check whether your issue is the same as the one I have experienced on my laptop and make appropriate patches for the KBL framebuffer driver.
Hi, I haven't had time recently to had time to reinstall, but now I have been using a SKL spoof after reading on common problems on 10.14(KBL not stable on 10.14). After trying to spoof, I've been getting a panic, and the report is attached below along with the config.plist for the SKL spoof. The report shows a similar divide-by-zero error at a similar kernel trap. It would be nice if you could help. Let me know if I need more problem reporting files.
Thanks in advance!
Code:
Anonymous UUID:       32D775A3-4530-C08B-ED40-C13EF4764E33

Tue Nov 27 10:17:58 2018

*** Panic Report ***
panic(cpu 4 caller 0xffffff801d8d84dd): Kernel trap at 0xffffff7fa0d189f4, type 0=divide error, registers:
CR0: 0x0000000080010033, CR2: 0x00007fff7357c39e, CR3: 0x000000044de0e05f, CR4: 0x00000000003626e0
RAX: 0x0117a11540000000, RBX: 0xffffff820e8a3648, RCX: 0xffffff820e8a3648, RDX: 0x0000000000000000
RSP: 0xffffff820e8a3630, RBP: 0xffffff820e8a3630, RSI: 0x0000000000000000, RDI: 0x00000000174d6c70
R8:  0x0000000000000018, R9:  0x0000000009a7ec80, R10: 0xffffff81ed57c510, R11: 0x0000000000000000
R12: 0xffffff8054330b80, R13: 0xffffff81ce423000, R14: 0xffffff81cd581000, R15: 0xffffff80511cb700
RFL: 0x0000000000010246, RIP: 0xffffff7fa0d189f4, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00007fff7357c39e, Error code: 0x0000000000000000, Fault CPU: 0x4, PL: 0, VF: 0

Backtrace (CPU 4), Frame : Return Address
0xffffff820e8a3100 : 0xffffff801d7aca9d
0xffffff820e8a3150 : 0xffffff801d8e6893
0xffffff820e8a3190 : 0xffffff801d8d82ba
0xffffff820e8a3200 : 0xffffff801d759ca0
0xffffff820e8a3220 : 0xffffff801d7ac4b7
0xffffff820e8a3340 : 0xffffff801d7ac303
0xffffff820e8a33b0 : 0xffffff801d8d84dd
0xffffff820e8a3520 : 0xffffff801d759ca0
0xffffff820e8a3540 : 0xffffff7fa0d189f4
0xffffff820e8a3630 : 0xffffff7fa0d168f6
0xffffff820e8a39a0 : 0xffffff7fa0cf10fa
0xffffff820e8a3a00 : 0xffffff7f9f19e726
0xffffff820e8a3a40 : 0xffffff7f9f19e5db
0xffffff820e8a3a90 : 0xffffff801de850a8
0xffffff820e8a3ae0 : 0xffffff7f9f1a4bb7
0xffffff820e8a3b30 : 0xffffff801de8e52f
0xffffff820e8a3c70 : 0xffffff801d892ef4
0xffffff820e8a3d80 : 0xffffff801d7b218d
0xffffff820e8a3dd0 : 0xffffff801d78cb45
0xffffff820e8a3e50 : 0xffffff801d7a14fe
0xffffff820e8a3ef0 : 0xffffff801d8bfa0b
0xffffff820e8a3fa0 : 0xffffff801d75a486
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(530.12)[9D1E5FA7-267E-397E-9C91-1751221A05CF]@0xffffff7f9f182000->0xffffff7f9f1ccfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[7DE930EC-AB73-3F5A-9D38-94D5EE90D197]@0xffffff7f9e095000
         com.apple.driver.AppleIntelSKLGraphicsFramebuffer(12.0.2)[ED111957-D1C9-3968-B529-14C169701B9A]@0xffffff7fa0cd9000->0xffffff7fa0eccfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[7DE930EC-AB73-3F5A-9D38-94D5EE90D197]@0xffffff7f9e095000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[DC1D9290-BFFC-309B-8529-CCB7AB322B1C]@0xffffff7f9e70b000
            dependency: com.apple.iokit.IOAcceleratorFamily2(400.27)[5BC3E111-E908-36E8-9AFB-A39BD0D561D5]@0xffffff7f9ff0a000
            dependency: com.apple.iokit.IOReportFamily(47)[6A9FF3E1-E644-3F33-8A44-8B51C44AA67C]@0xffffff7f9f4f7000
            dependency: com.apple.AppleGraphicsDeviceControl(3.25.6)[53E6D711-F2EF-35EE-8974-7BDCE4281C83]@0xffffff7f9f481000
            dependency: com.apple.iokit.IOGraphicsFamily(530.12)[9D1E5FA7-267E-397E-9C91-1751221A05CF]@0xffffff7f9f182000

BSD process name corresponding to current thread: WindowServer
Boot args: dart=0 -disablegfxfirmware -cdfon -igfxnohdmi -wegnoegpu lilucpu=8

Mac OS version:
18B75

Kernel version:
Darwin Kernel Version 18.2.0: Fri Oct  5 19:41:49 PDT 2018; root:xnu-4903.221.2~2/RELEASE_X86_64
Kernel UUID: 5D53F7E4-472A-369D-97D8-4DD877A4BDFF
Kernel slide:     0x000000001d400000
Kernel text base: 0xffffff801d600000
__HIB  text base: 0xffffff801d500000
System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

System uptime in nanoseconds: 8912251859
last loaded kext at 8801425487: com.apple.fileutil    1 (addr 0xffffff7f9f21c000, size 110592)
last unloaded kext at 1127015009: as.lvs1974.HibernationFixup    1.2.0 (addr 0xffffff7fa0bf9000, size 16384)
loaded kexts:
(none)

EOF
Model: MacBookPro14,1, BootROM 184.0.0.0.0, 4 processors, Intel Core i7, 1.99 GHz, 16 GB, SMC 2.43f6
Graphics: Intel UHD Graphics 620, Intel UHD Graphics 620, Built-In, 22 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 2133 MHz, Micron, -
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 2133 MHz, Micron, -
Network Service: Ethernet, Ethernet, en0
USB Device: USB 3.0 Bus
USB Device: HD Camera
USB Device: Bluetooth HCI
USB Device: Edimax Wi-Fi N150 Bluetooth4.0 USB Adapter
Thunderbolt Bus:
 

Attachments

  • skl-config.plist
    10.4 KB · Views: 260
Last edited:
Hi, I haven't had time recently to had time to reinstall, but now I have been using a SKL spoof after reading on common problems on 10.14(KBL not stable on 10.14). After trying to spoof, I've been getting a panic, and the report is attached below along with the config.plist for the SKL spoof. The report shows a similar divide-by-zero error at a similar kernel trap. It would be nice if you could help. Let me know if I need more problem reporting files.
Thanks in advance!
Code:
Anonymous UUID:       32D775A3-4530-C08B-ED40-C13EF4764E33

Tue Nov 27 10:17:58 2018

*** Panic Report ***
panic(cpu 4 caller 0xffffff801d8d84dd): Kernel trap at 0xffffff7fa0d189f4, type 0=divide error, registers:
CR0: 0x0000000080010033, CR2: 0x00007fff7357c39e, CR3: 0x000000044de0e05f, CR4: 0x00000000003626e0
RAX: 0x0117a11540000000, RBX: 0xffffff820e8a3648, RCX: 0xffffff820e8a3648, RDX: 0x0000000000000000
RSP: 0xffffff820e8a3630, RBP: 0xffffff820e8a3630, RSI: 0x0000000000000000, RDI: 0x00000000174d6c70
R8:  0x0000000000000018, R9:  0x0000000009a7ec80, R10: 0xffffff81ed57c510, R11: 0x0000000000000000
R12: 0xffffff8054330b80, R13: 0xffffff81ce423000, R14: 0xffffff81cd581000, R15: 0xffffff80511cb700
RFL: 0x0000000000010246, RIP: 0xffffff7fa0d189f4, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00007fff7357c39e, Error code: 0x0000000000000000, Fault CPU: 0x4, PL: 0, VF: 0

Backtrace (CPU 4), Frame : Return Address
0xffffff820e8a3100 : 0xffffff801d7aca9d
0xffffff820e8a3150 : 0xffffff801d8e6893
0xffffff820e8a3190 : 0xffffff801d8d82ba
0xffffff820e8a3200 : 0xffffff801d759ca0
0xffffff820e8a3220 : 0xffffff801d7ac4b7
0xffffff820e8a3340 : 0xffffff801d7ac303
0xffffff820e8a33b0 : 0xffffff801d8d84dd
0xffffff820e8a3520 : 0xffffff801d759ca0
0xffffff820e8a3540 : 0xffffff7fa0d189f4
0xffffff820e8a3630 : 0xffffff7fa0d168f6
0xffffff820e8a39a0 : 0xffffff7fa0cf10fa
0xffffff820e8a3a00 : 0xffffff7f9f19e726
0xffffff820e8a3a40 : 0xffffff7f9f19e5db
0xffffff820e8a3a90 : 0xffffff801de850a8
0xffffff820e8a3ae0 : 0xffffff7f9f1a4bb7
0xffffff820e8a3b30 : 0xffffff801de8e52f
0xffffff820e8a3c70 : 0xffffff801d892ef4
0xffffff820e8a3d80 : 0xffffff801d7b218d
0xffffff820e8a3dd0 : 0xffffff801d78cb45
0xffffff820e8a3e50 : 0xffffff801d7a14fe
0xffffff820e8a3ef0 : 0xffffff801d8bfa0b
0xffffff820e8a3fa0 : 0xffffff801d75a486
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(530.12)[9D1E5FA7-267E-397E-9C91-1751221A05CF]@0xffffff7f9f182000->0xffffff7f9f1ccfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[7DE930EC-AB73-3F5A-9D38-94D5EE90D197]@0xffffff7f9e095000
         com.apple.driver.AppleIntelSKLGraphicsFramebuffer(12.0.2)[ED111957-D1C9-3968-B529-14C169701B9A]@0xffffff7fa0cd9000->0xffffff7fa0eccfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[7DE930EC-AB73-3F5A-9D38-94D5EE90D197]@0xffffff7f9e095000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[DC1D9290-BFFC-309B-8529-CCB7AB322B1C]@0xffffff7f9e70b000
            dependency: com.apple.iokit.IOAcceleratorFamily2(400.27)[5BC3E111-E908-36E8-9AFB-A39BD0D561D5]@0xffffff7f9ff0a000
            dependency: com.apple.iokit.IOReportFamily(47)[6A9FF3E1-E644-3F33-8A44-8B51C44AA67C]@0xffffff7f9f4f7000
            dependency: com.apple.AppleGraphicsDeviceControl(3.25.6)[53E6D711-F2EF-35EE-8974-7BDCE4281C83]@0xffffff7f9f481000
            dependency: com.apple.iokit.IOGraphicsFamily(530.12)[9D1E5FA7-267E-397E-9C91-1751221A05CF]@0xffffff7f9f182000

BSD process name corresponding to current thread: WindowServer
Boot args: dart=0 -disablegfxfirmware -cdfon -igfxnohdmi -wegnoegpu lilucpu=8

Mac OS version:
18B75

Kernel version:
Darwin Kernel Version 18.2.0: Fri Oct  5 19:41:49 PDT 2018; root:xnu-4903.221.2~2/RELEASE_X86_64
Kernel UUID: 5D53F7E4-472A-369D-97D8-4DD877A4BDFF
Kernel slide:     0x000000001d400000
Kernel text base: 0xffffff801d600000
__HIB  text base: 0xffffff801d500000
System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

System uptime in nanoseconds: 8912251859
last loaded kext at 8801425487: com.apple.fileutil    1 (addr 0xffffff7f9f21c000, size 110592)
last unloaded kext at 1127015009: as.lvs1974.HibernationFixup    1.2.0 (addr 0xffffff7fa0bf9000, size 16384)
loaded kexts:
(none)

EOF
Model: MacBookPro14,1, BootROM 184.0.0.0.0, 4 processors, Intel Core i7, 1.99 GHz, 16 GB, SMC 2.43f6
Graphics: Intel UHD Graphics 620, Intel UHD Graphics 620, Built-In, 22 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 2133 MHz, Micron, -
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 2133 MHz, Micron, -
Network Service: Ethernet, Ethernet, en0
USB Device: USB 3.0 Bus
USB Device: HD Camera
USB Device: Bluetooth HCI
USB Device: Edimax Wi-Fi N150 Bluetooth4.0 USB Adapter
Thunderbolt Bus:

Why do you have a CFL related kext patch in KextsToPatch when you're actually using the SKL kexts?
 
Why do you have a CFL related kext patch in KextsToPatch when you're actually using the SKL kexts?
Hi, hope you are having a wonderful start to the new year.
So far, the internal screen still won't light up when booting with native KBL graphics properties. I can connect to an external display but can only get resolutions up to 1080P. Attached is the debug file for the KBL boot up. The boot up process starts with the internal display, but after it reaches iocounsleusers, the display's backlight brightens as the texts/apple logo disappears. Then the external display lights up. If not connected with external display, system will stay in verbose.

In order to get the internal display to work at all, I have to boot with CFL spoof, the internal display lights up, and the system boots properly, but brightness controls are present but useless: always stuck on maximum brightness. There is native HiDPI. After I wake the computer from sleep, there is a glitch on the display.
1547628820388.png
 

Attachments

  • debug_21463.zip
    3.4 MB · Views: 184
Why do you have a CFL related kext patch in KextsToPatch when you're actually using the SKL kexts?
Hi @RehabMan, glad to see that you're back! Hopefully everything is well for you. :)

Anyways, I was hoping that you can take a more serious look into this issue.

Please take a look at #23, the problem remains. The PR files attached on #23 is for KBL boot up using external monitor, and is still relevant. Basically KBL graphics can be accelerated but the screen refuses to light up while external displays work. Internal screen is black, but hackintool's EDID page recognizes that the internal display is attached while the system only recognizes the external display.

I will attach the CFL config PR to demonstrate the problem with the brightness and the issue with the computer not being able to display properly after sleep/ lid close.(picture attached in #23) I know that spoofing CFL is not a good idea, but since KBL is not possible yet, is there a way that we can fix the brightness issue? ie, can we do something with LMAX, or could it be like the other asian brands ie. sony etc.?

It would really help if you could take a careful look. I will upload anything you ask for. There is a community waiting for us to perfect this laptop's graphics.

Thanks in advance!

PS. I have a patch in order for the CFL spoofing to work. It is similar to the patch made by @Austere.J for the divide by zero error (the dirty fix one), but they are not quite similar. Is there a way to check what that patch does? I want to try to translate the appleintelcflframebuffer binary file via objdump -disassemble-all but only got assembly out of it. Is there a way to get readable code out from the assembly, so I can analyze the problem?

edit* it also appears that in console there is something changing the brightness automatically even though I attempted to disable the ambient light detector in the DSDT.
Code:
clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2
lux 29.000000, ambient 0.446000, <private>
setting canAdjust from 1 to 1
brightness 0.44600 _ambientOffset = 0.40000 final (to be capped) = 0.84600
PWM value = 3492 speed = 500
changed brightness to 0.846000. <private>
And the "changed brightness to ..." changes accordingly when I place my hand over the sensor... not a coincidence...
 

Attachments

  • debug_14085.zip
    3.7 MB · Views: 176
  • report.txt
    11 KB · Views: 142
Last edited:
Hi @RehabMan, glad to see that you're back! Hopefully everything is well for you. :)

Anyways, I was hoping that you can take a more serious look into this issue.

Please take a look at #23, the problem remains. The PR files attached on #23 is for KBL boot up using external monitor, and is still relevant. Basically KBL graphics can be accelerated but the screen refuses to light up while external displays work. Internal screen is black, but hackintool's EDID page recognizes that the internal display is attached while the system only recognizes the external display.

I will attach the CFL config PR to demonstrate the problem with the brightness and the issue with the computer not being able to display properly after sleep/ lid close.(picture attached in #23) I know that spoofing CFL is not a good idea, but since KBL is not possible yet, is there a way that we can fix the brightness issue? ie, can we do something with LMAX, or could it be like the other asian brands ie. sony etc.?

It would really help if you could take a careful look. I will upload anything you ask for. There is a community waiting for us to perfect this laptop's graphics.

Thanks in advance!

PS. I have a patch in order for the CFL spoofing to work. It is similar to the patch made by @Austere.J for the divide by zero error (the dirty fix one), but they are not quite similar. Is there a way to check what that patch does? I want to try to translate the appleintelcflframebuffer binary file via objdump -disassemble-all but only got assembly out of it. Is there a way to get readable code out from the assembly, so I can analyze the problem?

edit* it also appears that in console there is something changing the brightness automatically even though I attempted to disable the ambient light detector in the DSDT.
Code:
clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2
lux 29.000000, ambient 0.446000, <private>
setting canAdjust from 1 to 1
brightness 0.44600 _ambientOffset = 0.40000 final (to be capped) = 0.84600
PWM value = 3492 speed = 500
changed brightness to 0.846000. <private>
And the "changed brightness to ..." changes accordingly when I place my hand over the sensor... not a coincidence...

Your ioreg clearly shows two ALS:
Screen Shot 2019-02-09 at 10.06.57 AM.png


You should disable/delete the native one (ALSD).
 
Ok, I think I got the screen to work (aka accelerated), but the backlight isn't working, I think I implemented the backlight right, what did I do wrong?
Hi I face the same kind of proble in on Latitude 7285. It's on hd615 with a edp 3k screen. Can you share some information about how you fix the issue? Thanks
 
Can anyone report on, or assist with, getting the internal display on the Dell Latitude 7285 to function with Graphics Acceleration in Mojave? The internal display (3K) will work without Graphics Acceleration in native resolution(2880x1920) [and no other resolution], which makes for tough reading given the very small font. Once the framebuffer patch (thank you, @RehabMan) is applied to fix Graphics Acceleration, the system boots, but the internal display will only show backlight [the screen is black, but backlit---the system successfully boots, but no-show on the internal display], an external monitor will show the Mojave wallpaper, and when you close the laptop screen, the external monitor will show the login screen, and everything will work on the external monitor (including Graphics Acceleration). Debug.zip (thanks, @black.dragon74) is attached. Hopefully someone can help. Thanks. -cangman
 

Attachments

  • debug_14285.zip
    3.6 MB · Views: 61
Status
Not open for further replies.
Back
Top