flyingfishfinger Posted December 21, 2016 Author Share Posted December 21, 2016 No, 1400 x 1050 Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted December 21, 2016 Moderators Share Posted December 21, 2016 What did you set for DVMT? Try different value like 0x4 if you have 0x3 Link to comment Share on other sites More sharing options...
flyingfishfinger Posted December 21, 2016 Author Share Posted December 21, 2016 Changing to 0x4 gives me a pretty immediate KP, see attached. CPU-based KP?. And yes, I had 0x3 before. Also, not sure if this is relevant but I've found that the Clover theme which shows up at boot seems to change randomly.Sometimes it's the metal grey Latitude background, but mostly it's the blurry Yosemite background. So far I haven't found a deterministic pattern of when either shows up, but I'm mentioning it here because setting the DVMT to 0x4 seems to have made the Latitude theme show up again, whereas for most previous boot attempts I got the Yosemite one. R Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted December 21, 2016 Administrators Share Posted December 21, 2016 is there more then 1 EFI partition at the moment? Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted December 21, 2016 Moderators Share Posted December 21, 2016 Since changing the DVMT, the DSDT/SSDT have to be updated too. Try booting without them with ig-platform-id set to 0x16260006. If this works, then we could extract new DSDT/SSDT and then repatch them. The theme changing is due to your Config file not having the theme set. So it's random. Enter Clover or what ever theme you want and it'll boot to that every time. Link to comment Share on other sites More sharing options...
flyingfishfinger Posted December 21, 2016 Author Share Posted December 21, 2016 No, but at one point I think I did accidentally install Clover without the "install to ESP" box checked. That gave me an EFI folder at the root of the install, which I deleted. I just looked again, and there currently is an nvram.plist file at the root but otherwise nothing out of the ordinary. If I did accidentally install Clover to the root of the drive earlier, is there a way of undoing that, short of reinstalling the OS if deleting the folder didn't do it? Jake: I have never been able to boot to Desktop if I did not use VESA mode, regardless of platform-id or DVMT setting. You're suggesting sticking with 0x3, 16260002 and then what, temporarily emptying the "patched" folder, or what's the quickest way of booting without DSDT? R Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted December 21, 2016 Moderators Share Posted December 21, 2016 Just delete the folder in the root. Make sure you don't have virtual drive, run diskutil cs revert /dev/disk# if you do. Then reinstall Clover with UEFI settings. Link to comment Share on other sites More sharing options...
flyingfishfinger Posted December 21, 2016 Author Share Posted December 21, 2016 That's for the extra EFI folder. Best way to boot "without" current DSDT? Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted December 21, 2016 Administrators Share Posted December 21, 2016 at clover boot screen go to option acpi and change DSDT.aml to BIOS.aml Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted December 21, 2016 Moderators Share Posted December 21, 2016 Either remove it from Patched folder and change Config.plist to disable DropOEM under SSDT or during boot in Clover Option. Under ACPI patching, rename the DSDT.aml to Bios.aml, and under Tables Dropping, uncheck Drop all OEM SSDT and deselect all the SSDT-x.aml Link to comment Share on other sites More sharing options...
Recommended Posts