Contribute
Register

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

Status
Not open for further replies.
It appears there was no effect. I had to enable the 32MB framebuffer patch or else the system KPs at the gIOLockState 3 spot. I wonder if 32mb is just way too small for 4K and I need to mess with the values a little, and also how they got things working on the 9560...

Anyways, I've attached PR files.


Just a note that I had actually read right over this, so while the data is still there and correct, I eventually set Graphics>EDID>Inject to false. I then tried after setting AAPL00,override-no-connect with no effect, and the same thing happening.

Next step: research how to set larger DVMT-prealloc.
 
research how to set larger DVMT-prealloc
I don't see a way to change it to 128MB without modding the BIOS, which:
1. Seems to have no public methods because nobody wants to share their secrets...?
2. I'm not sure is possible with the XPS

That is, unless you mean to 64mb, in which it already is (as confirmed by the BIOS information page and AmiSetupWriter)?
 
I don't see a way to change it to 128MB without modding the BIOS, which:
1. Seems to have no public methods because nobody wants to share their secrets...?
2. I'm not sure is possible with the XPS

That is, unless you mean to 64mb, in which it already is (as confirmed by the BIOS information page and AmiSetupWriter)?

You said that unless you patch for 32mb, you have KP? Which implies the current setting is 32mb...
 
You said that unless you patch for 32mb, you have KP? Which implies the current setting is 32mb...
Basically, yet everything points to DVMT-prealloc being 64mb.
 
BIOS report, BIOS Setup variable writing tool + extracted IFR...

So everything except the assert coming from the graphics kexts...
 
So everything except the assert coming from the graphics kexts...
Should assert show up in the stack trace? I'll check it later either way.
 
Sometimes.
I took a look in IDA and it seems to be crashing at this line:
upload_2018-10-2_19-5-14.png


upload_2018-10-2_19-5-51.png


Division by zero...? What's "[IGFB][ERROR ] fActiveNumberOfLanes = %d, linkSymbolClock = %llu.. One of them is 0 for FB%x - will lead to DivideByZero panic. PixelClock = %llu!!!!!\n"...? v11 is the register r13, so it appears to definitely be division by 0.
 
Status
Not open for further replies.
Back
Top