Contribute
Register

[solved] UHD 630 either not booting or no acceleration on Dell XPS 15 9570 4K

Status
Not open for further replies.
Nope, do you have CoreDisplayFixup?

Did you try to implement the brightness on your laptop?

I mean SSDT-PNLF.aml, AppleBacklightInjector.kext and binary patches for AppleBacklight.kext.

If so, did you have this issue that brightness stays at the lowest level during boot and becomes normal after about 3 or 5 minutes?
 
Did you try to implement the brightness on your laptop?

I mean SSDT-PNLF.aml, AppleBacklightInjector.kext and binary patches for AppleBacklight.kext.

If so, did you have this issue that brightness stays at the lowest level during boot and becomes normal after about 3 or 5 minutes?

I have a similar situation, but I don't use any backlit patches, I don't know how to solve them.
It takes about 2 minutes to return to normal. This time is probably the time of sleep, that is, wake up again after sleep.
 
Did you try to implement the brightness on your laptop?

I mean SSDT-PNLF.aml, AppleBacklightInjector.kext and binary patches for AppleBacklight.kext.

If so, did you have this issue that brightness stays at the lowest level during boot and becomes normal after about 3 or 5 minutes?

I am in the same situation.
The brightness is at lowest value during boot and for some minutes after boot. After that I have full control of the brightness both through the slider in System Preferences and through the brightness keys.
One thing I have noticed though is that when changing brightness through the keys the transition between two brightness levels isn’t smooth.
 
If so, did you have this issue that brightness stays at the lowest level during boot and becomes normal after about 3 or 5 minutes?
I do have that, I'm not sure how to fix it.
Also, the max brightness after the 5 minutes is ~30% in Windows, any clue there?

Would you like to share your Clover folder?
All of my kexts are in /L/E, sorry :(
 
Right, I haven't posted my latest config :)
I'll get to that after work. Check back in 5 hours, it'll be there.

Edit: attached!

I fear I have had no luck ([IGPU] Graphics driver failed to load: could not register with Framebuffer driver !) with your config.plist.

I’m more and more convinced that the issue is due to the Intel ME supposedly being disabled on my motherboard (I know of no way the verify this). Since however the nVidia GPU is defective Dell will replace the motherboard. I’ll opt for a normally configured motherboard this time and will try again when the motherboard is replaced (which might take some time since it’s backordered). Would you in the meantime be willing to provide a list of all the kext’s you have added for compatibility reasons both on the main OS partition as well as a dump of your EFI partition in it’s current state (minus the serial number you have configured of course) so that I can rule out some things ? Again, any help is much appreciated.
 
Last edited:
I fear I have had no luck ([IGPU] Graphics driver failed to load: could not register with Framebuffer driver !) with your config.plist.

I’m more and more convinced that the issue is due to the Intel ME supposedly being disabled on my motherboard (I know of no way the verify this). Since however the nVidia GPU is defective Dell will replace the motherboard. I’ll opt for a normally configured motherboard this time and will try again when the motherboard is replaced (which might take some time since it’s backordered). Would you in the meantime be willing to provide a list of all the kext’s you have added for compatibility reasons both on the main OS partition as well as a dump of your EFI partition in it’s current state (minus the serial number you have configured of course) so that I can rule out some things ? Again, any help is much appreciated.
No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the gen_debug.sh tool mentioned in the FAQ, that way it is less likely you'll omit something.
 
No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the gen_debug.sh tool mentioned in the FAQ, that way it is less likely you'll omit something.

I've had some issues with the build-in PM981 SSD which I've ordered a compatible replacement for. For now the NVME drive is disabled in the BIOS. I'm booting clover from a USB stick and have installed Mojave on an USD attached SSD. As as result I've manually added the Clover folder. For my main intend is to get GPU acceleration working and continue from there.

Thanks !
 

Attachments

  • debug_22507.zip
    4.7 MB · Views: 76
I've had some issues with the build-in PM981 SSD which I've ordered a compatible replacement for. For now the NVME drive is disabled in the BIOS. I'm booting clover from a USB stick and have installed Mojave on an USD attached SSD. As as result I've manually added the Clover folder. For my main intend is to get GPU acceleration working and continue from there.

Thanks !

Looking at your ioreg, you are injecting ig-platform-id = 0xe9b00000.
It is probably because too many zeros at the end of your setting for Graphics/ig-platform-id.
You have 0x3E9B00000, but probably meant 0x3e9b0000.

Your ioreg proves that IMEI is not disabled.
Your Clover bootlog also shows active IMEI:
Code:
0:105  0:000  === [ GetDevices ] ========================================
...
0:105  0:000  PCI (00|00:16.00) : 8086 A360 class=078000
 
Looking at your ioreg, you are injecting ig-platform-id = 0xe9b00000.
It is probably because too many zeros at the end of your setting for Graphics/ig-platform-id.
You have 0x3E9B00000, but probably meant 0x3e9b0000.

Your ioreg proves that IMEI is not disabled.
Your Clover bootlog also shows active IMEI:
Code:
0:105  0:000  === [ GetDevices ] ========================================
...
0:105  0:000  PCI (00|00:16.00) : 8086 A360 class=078000

It's good to know that the cause of this issue should be solvable then. Thanks for that.

The extra 0 was the result of me quickly cleaning up additional several attempts to work out the situation shortly before making the dump. I've corrected it, booted with it and the same result. A fresh debug dump is attached.

For what it’s worth, I never was able to load up AppleIntelCFLFramebuffer.kext even when using 0x12345678 as ig-platform-id and thus it’s never patched as it never enters the kernel cache when running `sudo kextcache -i /’ (if I understand correctly).
 

Attachments

  • 26473.zip
    4.7 MB · Views: 87
Last edited:
Status
Not open for further replies.
Back
Top