Contribute
Register
Status
Not open for further replies.
Probably not a good idea, because CFL backlight control is different than KabyLake-R.
Spoof as 0x5916 instead.
Yes, but are you able to tell from the picture above what has been modded for the CFL Framebuffer kext? The computer will not boot with a native CFL framebuffee kext, only with the modded kext which is the one on the right in the picture. If I were to apply a similar patch to the KBL kext then I can use platform ID 5916.
319637-56c97482eb63d47c9c66b3ec6bfabea6.jpg

Edit* I removed the modded kext and replace it with a vanilla one. I am able to boot with the vanilla one with a patch. I attached the newest debug please take a look under the kexttopatch section for the patch. Hopefully you can tell what it does...

Thanks in advance. :)
 

Attachments

  • debug_28386.zip
    2.9 MB · Views: 90
Last edited:
Yes, but are you able to tell from the picture above what has been modded for the CFL Framebuffer kext? The computer will not boot with a native CFL framebuffee kext, only with the modded kext which is the one on the right in the picture. If I were to apply a similar patch to the KBL kext then I can use platform ID 5916.
319637-56c97482eb63d47c9c66b3ec6bfabea6.jpg

Edit* I removed the modded kext and replace it with a vanilla one. I am able to boot with the vanilla one with a patch. I attached the newest debug please take a look under the kexttopatch section for the patch. Hopefully you can tell what it does...

Thanks in advance. :)

Don't use CoffeeLake kexts with KabyLake hardware.
 
Don't use CoffeeLake kexts with KabyLake hardware.
Yes, but can you tell what the patch is for/ what it does, from the picture above? I need to know what it does in order to make a similar patch for KBL.
 
Last edited:
Yes, but can you tell what the patch is for/ what it does, from the picture above? I need to know what it does in order to make a similar patch for KBL.

The image you attached is not even legible.
 
The image you attached is not even legible.
Sorry, can you please take a look now? Again, edited one is on the right, you can also look at the debug file from post #11, it is untouched. The patch is in kexttopatch.
Screen_Shot_2018-11-10_at_12.23.59_AM.png
 
Sorry, can you please take a look now? Again, edited one is on the right, you can also look at the debug file from post #11, it is untouched. The patch is in kexttopatch.View attachment 365152

Sorry, no idea what that patch is for.
Perhaps you should refer back to where you found it.
 
Sorry, no idea what that patch is for.
Perhaps you should refer back to where you found it.
I found it, I think its the divide by zero patch that @Austere.J found for his UHD 630. Is there a way to make a similar patch for UHD 620?
 
I found it, I think its the divide by zero patch that @Austere.J found for his UHD 630. Is there a way to make a similar patch for UHD 620?

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.
 
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.
I've used the KBL platform-ID to boot, it reboots as soon as it hits IOcounsleusers or something like that, similar to your situation before you patched it. Then I used an invalid ID to boot, and here's the debug. The config.plist is the one for KBL, others are for CFL spoof.

Edit*
In other previous configurations of the config (fb properties) such as a different KBL platform, and undefined mem, the computer would boot, and the screen would be stuck on iocounsleusers while the computer boots normally, and I can remote into the laptop. Everything is functioning except the screen... Even touch screen is working, just the screen still stuck on verbose... The config attached is the one that panics.
Thanks in advance!
 

Attachments

  • debug_30559.zip
    2.8 MB · Views: 72
I've used the KBL platform-ID to boot, it reboots as soon as it hits IOcounsleusers or something like that, similar to your situation before you patched it. Then I used an invalid ID to boot, and here's the debug. The config.plist is the one for KBL, others are for CFL spoof.

Edit*
In other previous configurations of the config (fb properties) such as a different KBL platform, and undefined mem, the computer would boot, and the screen would be stuck on iocounsleusers while the computer boots normally, and I can remote into the laptop. Everything is functioning except the screen... Even touch screen is working, just the screen still stuck on verbose... The config attached is the one that panics.
Thanks in advance!

Your setup is a mess (way too many patched system kexts listed in your kextcache output).
Start over with a fresh install:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/
 
Status
Not open for further replies.
Back
Top