Jump to content
arsradu

[HOW TO] Fix second stage boot logo and loading bar for some dedicated desktop video cards

389 posts in this topic

Recommended Posts

Advertisement

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 :-)

Share this post


Link to post
Share on other sites

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! :D

Share this post


Link to post
Share on other sites

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! :D

 

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?

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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 :P). 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! :D

Share this post


Link to post
Share on other sites

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 :P). 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! :D

 

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.

Share this post


Link to post
Share on other sites

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. :D

 

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.

Share this post


Link to post
Share on other sites

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 ;)

Share this post


Link to post
Share on other sites

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"
                            }
                        })

Share this post


Link to post
Share on other sites

 

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?

Share this post


Link to post
Share on other sites

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 :-)

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

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. :D I wonder if it works with the device-properties method. Should work..I guess. I just can't test this. :))

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

post-942609-0-96357200-1447537139_thumb.png

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By shinho73
      Can someone help me fix reboot issue? Actually it reboots, but sometimes the hackintosh just hangs with screen off. Here is the Extra folder containing org.chameleon.boot.plist. https://drive.google.com/drive/folders/1MX8-DpQk9kaRUfjPcToxf-ElWh-bN6EY?usp=sharing  and the spec of the PC. https://drive.google.com/drive/folders/1NlcUNK5DBzJFxeFeuyt92eRjQqwO5T32?usp=sharing Can someone look at it? I might be doing something wrong. Any help will be greatly appreciated. Thank you. 

    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
    • By fusion71au
      Clover r5051 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r5051 for VMware.zip". Mount Clover-v2.5k-5051-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
×