Search results

Yeah sorry about that. Now I have scaled like this, and it works well but everything it’s too big (there says Looks like 1680x945) The option that causes problems with the screen is the one on the right. There says Looks like 1920x1080 With this option the screen looks completely grayed out...

Well I booted without the Framebuffer patch, scaled the display and it worked. I have full QE/CI. Nos it’s scaled to look like 1680x945, the 1920x1080 it’s that causes problem, what could it be? Can it be fixed? Note: I downgraded BIOS and set DVMT to 128MB successfully but it did not change...

Already tried, same thing happens. Don't know what else to try nothing seems to fix it.

I don’t seem able to change it. I extracted this from bios asi per guide: And then change it here: But if I enter again to the grub menu to check if it’s changed this appears: The BIOS is playing me.

There is another option to try before hacking the BIOS? I mean, at least the DVMT is 64MB, unless the 4K display needs more tan that. Maybe I can do something else to try to fix this. Thank you for your time @RehabMan

If this screen appears when booting after changing the Framebuffer values to match 128MB, it means that I have a 64MB DMVT-prealloc? (Because it’s says available 67104768 bytes) Edit: I don’t know how to check correctly my DVMT-prealloc, checked on windows and Linux and both says 128MB, but I...

You mean changing the BIOS or changing the config.plist?

Here are the debug files. I had to make a script so the gen_debug tool would run automatically at start because I cannot see anything with the gray screen (on which if I press keys from the keyboard it does like shown in the video of post #1).

I am probably dumb, doing as in guide and nothing change... 1. I tried every different value of ig-platform-id that I came across with in all the forums (for broadwell) 2. Tried with fake device-id enabled/disabled, got "garbled screen" with valid id. 3. Added framebuffer patch just in case...

No luck doing this, the same thing happens, I get “garbled screen” with valid id

Sorry for the noob question, did you mean this?

This is how the screen looks (.zip video attached). If I press keys like ESC or spacebar the login screen appears and then disappears again into a gey screen. Will do.

I Installed Clover to my SSD as recommended, also checked ioreg files. I boot with ig-platform-id 0x1245678 changed on clover settings, otherwise I cant boot and I get the garbled screen. Thank you in advance

But it’s inside of a function, its that ok?

Hi, i followed the guide but I dont seem able to find the _OFF method on my SSDT files Thanks in advanced

I upload the reporting and clover files, but in this case with the framebuffer activated (the raw .plist from your repository, no changes). Because I think I did not check my DVMT memory properly. Edit: I tried to boot with the clover file attached but with the default if-platform-id...

Well I tried many options for the ig-platform-id none actually seem to do any better, i was getting a garbled screen or not even booting onto macOS. The CSM boot is enabled from BIOS. I'm uploading the reporting files (booted from the usb) and the clover configuration used.

Excellent, now I understand. To fix it what should I have to do?

THANKS, I put an invalid ig-platform-id value (0x12345678) and deleted the framebuffer* entries and I was able to boot into macOS. But if I booted in CSM mode it got me a 23-inch display with 1280X1024 resolution (vram 5MB). Without CSM I got a 61-inch display with 3840x2160 resolution (vram...

I change the integer to 0, I thought it was enough. What else I should do to disable it? (I read the DVMT post but I don’t understand where to turn it off, or exactly what to delete)