andreJPBR Posted October 25, 2015 Share Posted October 25, 2015 Hi arsradu Perfect! Set Clover resolution to 1080p and Also OS X resolution to 1080p. Game over. Thank you very much for the tutorial and support. EVGA GTX 750 ti tested and approved. https://www.dropbox.com/s/ygqxsqh5dwkaeih/Boot_Movie_Sucess.mp4?dl=0 1 Link to comment Share on other sites More sharing options...
Ramalama Posted October 25, 2015 Share Posted October 25, 2015 In my experience, you don't need a custom one. Clover does a good job at injecting the correct EDID for you monitor. But on some monitors, especially on higher resolution ones (over 1080p) some people were saying that they don't have the Apple logo for the second stage boot. Try to set Clover resolution to 1080p and also OS X resolution to 1080p. Just for testing purposes. See if it makes any difference. Also, if your motherboard supports this feature and if you don't have any MBR-booted drives (legacy drives), you can try to turn OFF CSM in your UEFI Bios. See if that works for you. Exactly, have a little bit other configuration, 2560x1440 on 13inch screen... What i can say, if i set clover to 1280x720 and OS X to 1280x720 = perfect logo + perfect loading bar if i use default 2560x1440 both, i get with "second boot fix" perfect logo + loading bar little bit distored... without the bin patch it is completely distored on 2560x1440... so I'm using hidpi mode, 1600x900 = 3200x1800, but i can't set that resolution to clover because clover can't patch integrated graphics vbios as far i know, since this vbios is inside laptops bios in core_dxe... edid patching won't help here, since a new modeline makes a distored screen on first draw... if you changing resolution and change back, its working... but you won't do that every time after system start :-) So what i can say, use a 16:10 screen for OS X or 16:9 but anything greater 2800+ (2880xxx, 3200xxx...) there is a hole in OS X for 16.9 resolutions from 1920xxxx till 2800xxxx... what i mean with the hole is, distorted boot or not working hiDPI modes on 16:9 screens... Dunno why, but i tested some other systems, everything else is fine :-) Cheers :-) Link to comment Share on other sites More sharing options...
Awesome Donkey Posted November 6, 2015 Share Posted November 6, 2015 Just did this with my 970 on a 1440p DVI-DL screen (along with setting 1440p within Clover) and it works perfectly. The second stage isn't glitched at all - the loading bar is centered and looks perfectly and the Apple logo looks great! Link to comment Share on other sites More sharing options...
arsradu Posted November 6, 2015 Author Share Posted November 6, 2015 Just did this with my 970 on a 1440p DVI-DL screen (along with setting 1440p within Clover) and it works perfectly. The second stage isn't glitched at all - the loading bar is centered and looks perfectly and the Apple logo looks great! Thank you very much for your feedback! And glad to hear that this works for you too. What about the resolution in OS X? Is it set to 1440p, as well? Link to comment Share on other sites More sharing options...
Awesome Donkey Posted November 6, 2015 Share Posted November 6, 2015 Yup, it is. Works fine. 1 Link to comment Share on other sites More sharing options...
arsradu Posted November 6, 2015 Author Share Posted November 6, 2015 Yup, it is. Works fine. Awesome. Is CSM disabled? Link to comment Share on other sites More sharing options...
Awesome Donkey Posted November 6, 2015 Share Posted November 6, 2015 Yes sir! All my OSes are UEFI, so it's disabled. 1 Link to comment Share on other sites More sharing options...
frankiee Posted November 8, 2015 Share Posted November 8, 2015 Dunno if that was mentioned before, but at least for me, the solution was way simpler as described in this guide, so it might be of interest. Really, all I had to do was adding this entry: "@2,AAPL,boot-display", Buffer (One) { 0x00 }, to my GPU Device in my SSDT. The whole entry currently looks like this: (I have a NVIDIA card) Device (_SB.PCI0.NPE3.PXS1) { Name (_ADR, Zero) Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x12) { "AAPL,slot-name", Buffer (0x0B) { "PCI Slot 1" }, "@0,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@1,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@2,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@2,AAPL,boot-display", Buffer (One) { 0x00 }, "@3,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@4,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@5,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }) } } Note that I did not have to add "Load VBIOS" in Clover, and also not "Inject EDID". Actually I was surprised that the solution was so minimalistic. Works in both 10.10 and 10.11. Of course you might need to change the connector from "@2" to something that corresponds on your System. Maybe it even works if you add this entry to all availbale connectors in the SSDT, but I have not tried that. Edit: if you do that, you will have multiple loading bars. So it should be only one entry that matches the connected main display. Just FYI Link to comment Share on other sites More sharing options...
arsradu Posted November 8, 2015 Author Share Posted November 8, 2015 Dunno if that was mentioned before, but at least for me, the solution was way simpler as described in this guide, so it might be of interest. Really, all I had to do was adding this entry: "@2,AAPL,boot-display", Buffer (One) { 0x00 }, to my GPU Device in my SSDT. The whole entry currently looks like this: (I have a NVIDIA card) Device (_SB.PCI0.NPE3.PXS1) { Name (_ADR, Zero) Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x12) { "AAPL,slot-name", Buffer (0x0B) { "PCI Slot 1" }, "@0,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@1,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@2,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@2,AAPL,boot-display", Buffer (One) { 0x00 }, "@3,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@4,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@5,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }) } } Note that I did not have to add "Load VBIOS" in Clover, and also not "Inject EDID". Actually I was surprised that the solution was so minimalistic. Works in both 10.10 and 10.11. Of course you might need to change the connector from "@2" to something that corresponds on your System. Maybe it even works if you add this entry to all availbale connectors in the SSDT, but I have not tried that. I did mention in the initial post (pretty long one, I know, but this is somewhere on the top) that this can also be achieved by using DSDT editing. Actually a few of my friends got it fixed this way. However I do not know how to do it right now (I'm still very much a noob in DSDT editing), so I can't teach others ether. ) Also, you don't have to Inject EDID and Patch VBIOS if you're using an UEFI GOP Vbios (this is also mentioned on the first post ). And even if you're not using a UEFI VBIOS, apparently not all the people need that. I needed it, so I mentioned it for other people to know about it. Thanks for sharing! And also, glad it works for you! Link to comment Share on other sites More sharing options...
frankiee Posted November 8, 2015 Share Posted November 8, 2015 I did mention in the initial post (pretty long one, I know, but this is somewhere on the top) that this can also be achieved by using DSDT editing. Actually a few of my friends got it fixed this way. However I do not know how to do it right now (I'm still very much a noob in DSDT editing), so I can't teach others ether. ) Also, you don't have to Inject EDID and Patch VBIOS if you're using an UEFI GOP Vbios (this is also mentioned on the first post ). And even if you're not using a UEFI VBIOS, apparently not all the people need that. I needed it, so I mentioned it for other people to know about it. Thanks for sharing! And also, glad it works for you! Yeah, sorry if I may have overlooked something And I am absolutely no expert in DSDT editing, so if I can do it, everyone can So you also have some type of SSDT patch for your GPU, right? So apparently, the only thing needed is to add this entry in the _DSM method, using the correct connector adress of course. Link to comment Share on other sites More sharing options...
arsradu Posted November 8, 2015 Author Share Posted November 8, 2015 Yeah, sorry if I may have overlooked something And I am absolutely no expert in DSDT editing, so if I can do it, everyone can So you also have some type of SSDT patch for your GPU, right? So apparently, the only thing needed is to add this entry in the _DSM method, using the correct connector adress of course. I'm not using any kind of patched SSDT/DSDT files. Only Clover patching. I'll try to learn a bit more about it and, maybe I'll add that part as well. I think it would be a nice addition. Link to comment Share on other sites More sharing options...
frankiee Posted November 8, 2015 Share Posted November 8, 2015 Ah, understand. Even if I am not an expert I still try to avoid Clover patches when possible. And there is always something new to learn Link to comment Share on other sites More sharing options...
Mrengles Posted November 9, 2015 Share Posted November 9, 2015 If you would like to avoid having to patch your DSDT ever time your change your monitor setup or default you can use this DSM method, Device (GFX0) { Name (_ADR, Zero) Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x12) { "@0,AAPL,boot-display", Buffer (Zero) {}, "@0,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@1,AAPL,boot-display", Buffer (Zero) {}, "@1,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@2,AAPL,boot-display", Buffer (Zero) {}, "@2,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@3,AAPL,boot-display", Buffer (Zero) {}, "@3,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-2" } }) Link to comment Share on other sites More sharing options...
arsradu Posted November 9, 2015 Author Share Posted November 9, 2015 If you would like to avoid having to patch your DSDT ever time your change your monitor setup or default you can use this DSM method, Device (GFX0) { Name (_ADR, Zero) Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x12) { "@0,AAPL,boot-display", Buffer (Zero) {}, "@0,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@1,AAPL,boot-display", Buffer (Zero) {}, "@1,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@2,AAPL,boot-display", Buffer (Zero) {}, "@2,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@3,AAPL,boot-display", Buffer (Zero) {}, "@3,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-2" } }) So..basically setting the same boot-display property for all ports? Did I get that part right? Link to comment Share on other sites More sharing options...
Ramalama Posted November 9, 2015 Share Posted November 9, 2015 So..basically setting the same boot-display property for all ports? Did I get that part right? @asradu This above seems for me like boot display for every frame buffer... dunno if this is useless or not... But, there must be some registers, which changes, based where your display is connected, just need to read in the Nvidia/Amd Specification sheet... Like Rehab found the BAR1 register in the Intel Graphics specification sheet... (different thing, because BAR1 is for brightness) But theoretically i think its possible... If we find the register it should be very easy to make an ACPI Method for this... PS: i don't have here Nvidia/Amd Graphics, since i have on my laptop only Iris5100... So i can't test... Im Sry... Cheers :-) Link to comment Share on other sites More sharing options...
frankiee Posted November 10, 2015 Share Posted November 10, 2015 This above seems for me like boot display for every frame buffer... dunno if this is useless or not... Imho, it is. When I do this, I get the Apple Logo, but also a second loading bar bottom-left, just like without the patch. Link to comment Share on other sites More sharing options...
couleurs Posted November 10, 2015 Share Posted November 10, 2015 I followed the guide and got my 2nd stage boot screen 95% working but for some reason my monitor still blinks blank before the logo/loading screen finishes? Before it did the same but I didn't have the logo/loading screen properly centred as it just showed the bar on the bottom left hand corner. I'm guessing this is an EDID issue with my monitor? Link to comment Share on other sites More sharing options...
arsradu Posted November 10, 2015 Author Share Posted November 10, 2015 I followed the guide and got my 2nd boot screen 95% working but for some reason my monitor still blinks blank before the logo/loading screen finishes? Before it did the same but I didn't have the logo/loading screen properly centred as it just showed the bar on the bottom left hand corner. Yeah, that's a glitch that most of us have (especially desktop users). Interestingly, even some real iMacs have it too. And no, I'm not sure it has anything to do with the EDID. But I might be wrong. So far, that's the best we can have. When there will be a solution for that as well, I'll post it. Link to comment Share on other sites More sharing options...
couleurs Posted November 10, 2015 Share Posted November 10, 2015 Yeah, that's a glitch that most of us have (especially desktop users). Interestingly, even some real iMacs have it too. And no, I'm not sure it has anything to do with the EDID. But I might be wrong. Ah OK. I thought I was alone. Seems like a weird glitch -- it would be nice to have a fix for it sometime but it's already much better than before. Thanks for the guide! Link to comment Share on other sites More sharing options...
Mrengles Posted November 10, 2015 Share Posted November 10, 2015 So..basically setting the same boot-display property for all ports? Did I get that part right? Yes that's all I did... Makes not difference on my end with multi-monitors or single monitor switched to a different port... I guess OS X thinks the displays are mirrored for the boot process maybe? Link to comment Share on other sites More sharing options...
arsradu Posted November 10, 2015 Author Share Posted November 10, 2015 Yes that's all I did... Makes not difference on my end with multi-monitors or single monitor switched to a different port... I guess OS X thinks the displays are mirrored for the boot process maybe? That is really interesting. I wonder if it works with the device-properties method. Should work..I guess. I just can't test this. ) Link to comment Share on other sites More sharing options...
irog12 Posted November 13, 2015 Share Posted November 13, 2015 Hi I've followed steps 1-4 but the only thing I got from step 5 is the loading bar at the center with no logo. Patch Vbios and Inject EDID made the first stage logo bigger with the loading bar at the center with no logo on the second stage. I've tried with/without CsmVideoDrv.efi but to no avail. My bios, tho UEFI, had no CSM option (it's an H61M). I'm booting in UEFI and I'm not using DSDT/SSDT coz Clover does the good job already. I'm using Manli GeForce 210 on this one. Any ideas? I'm using the VGA port BTW. Please have a look at the file (attached) I edited using @1 as the default. device-properties.xml Link to comment Share on other sites More sharing options...
arsradu Posted November 13, 2015 Author Share Posted November 13, 2015 Hi I've followed steps 1-4 but the only thing I got from step 5 is the loading bar at the center with no logo. Patch Vbios and Inject EDID made the first stage logo bigger with the loading bar at the center with no logo on the second stage. I've tried with/without CsmVideoDrv.efi but to no avail. My bios, tho UEFI, had no CSM option (it's an H61M). I'm booting in UEFI and I'm not using DSDT/SSDT coz Clover does the good job already. I'm using Manli GeForce 210 on this one. Any ideas? I'm using the VGA port BTW. Please have a look at the file (attached) I edited using @1 as the default. 1. What's your display resolution? What's the resolution set in Clover? What's the resolution set in OS X? 2. Did you set a specific display-cfg in Clover config or anywhere else? Does it work without it? Also, something seems a bit off in your xml... Is this the one that you edited or the one generated after reboot, when extracting it again from the system? Also, a screenshot of your IOreg might help in this case. 1 Link to comment Share on other sites More sharing options...
irog12 Posted November 14, 2015 Share Posted November 14, 2015 My display resolution is set to 1600x900 in OS X and in Clover. No I didn't set any display-cfg in Clover. The xml I sent was the edited xml already. What seems to be off in the xml? Here's my ioreg. Thanks Link to comment Share on other sites More sharing options...
arsradu Posted November 14, 2015 Author Share Posted November 14, 2015 My display resolution is set to 1600x900 in OS X and in Clover. No I didn't set any display-cfg in Clover. The xml I sent was the edited xml already. What seems to be off in the xml? Here's my ioreg. Thanks I'm pretty sure hda-gfx is not in the initial tutorial. I'm not sure it's the cause of the issue. Probably not. But let's just do it exactly like it is on the first page for once. So, could you please, try the hex txt in the attachment? Please, make a copy of your current one, just to be safe. And let's see if that makes any difference. Also please, try with and without PatchVbios. hex_txt.txt Link to comment Share on other sites More sharing options...
Recommended Posts