can we get back the apple logo on boot?

arsradu · February 10, 2015

Friend saw you use NVIDIA GPU, I do not know how theirs activation method.

But I did so:

DSDT:

null

Config.plist Clover:

null

In Clover option "VídeoPorts". I do not know applies to nvidia cards.

My video card has only three connectors:

Portas da placa ASUS Radeon HD7750-1GD5-V2.png

Thanks, man. I don't know if this is going to work, but I'm willing to try.

Where is that section that you edited? Where in the DSDT? Cause I can't find it. It would have been nice to keep the left panel from MaciASL visible (I suppose that's what you used to edit that DSDT) so I can see where you are into those folders.

Also, how do you save changes into a new file? I got my default DSDT on my Desktop for easy editing. So now I still don't know where to edit/what to change and how to save those changes.

JorgeMax · February 10, 2015

Thanks, man. I don't know if this is going to work, but I'm willing to try.

Where is that section that you edited? Where in the DSDT? Cause I can't find it. It would have been nice to keep the left panel from MaciASL visible (I suppose that's what you used to edit that DSDT) so I can see where you are into those folders.

Also, how do you save changes into a new file? I got my default DSDT on my Desktop for easy editing. So now I still don't know where to edit/what to change and how to save those changes.

Friend. I do not quite understand how one patch DSDT of "zero". To find the "address" of the video card in DSDT, you will have to use the "IORegistryExplorer" program.

This is the "local" from my plate in "Ioreg":

DSDT:

But if you do not know how to edit in your DSDT, I suggest you ask for the "Mirone" help you, I do not understand and patch DSDT one of "zero".

Open progrma "IORegistryExplorer", click "File / Save a Copy As ..." creates a folder name the it and save the "Ioreg" and your DSDT in, click the right mouse button on top folder and "compress" it. send here (site)

arsradu · February 10, 2015

Friend. I do not quite understand how one patch DSDT of "zero". To find the "address" of the video card in DSDT, you will have to use the "IORegistryExplorer" program.

This is the "local" from my plate in "Ioreg":

null

DSDT:

null

But if you do not know how to edit in your DSDT, I suggest you ask for the "Mirone" help you, I do not understand and patch DSDT one of "zero".

Open progrma "IORegistryExplorer", click "File / Save a Copy As ..." creates a folder name the it and save the "Ioreg" and your DSDT in, click the right mouse button on top folder and "compress" it. send here (site)

Thanks man. I'll give a try tonight.

arsradu · February 10, 2015

Friend. I do not quite understand how one patch DSDT of "zero". To find the "address" of the video card in DSDT, you will have to use the "IORegistryExplorer" program.

This is the "local" from my plate in "Ioreg":

null

DSDT:

null

But if you do not know how to edit in your DSDT, I suggest you ask for the "Mirone" help you, I do not understand and patch DSDT one of "zero".

Open progrma "IORegistryExplorer", click "File / Save a Copy As ..." creates a folder name the it and save the "Ioreg" and your DSDT in, click the right mouse button on top folder and "compress" it. send here (site)

Here is my path.

And..I couldn't find anything similar to that into DSDT (attached).

DSDT.aml.zip

Mirone · February 10, 2015

arsradu,

advice, renames GFX0 to GFX1.

arsradu · February 10, 2015

arsradu,

advice, renames GFX0 to GFX1.

Ok. Could you please tell me where should I rename this? And how? I need a step by step description so that I can understand where are all these accessible and how to edit them. This is all very confusing to me.

Mirone · February 10, 2015

send me you ioreg+config.plist+dsdt

arsradu · February 10, 2015

send me you ioreg+config.plist+dsdt

I would really appreciate it if you could teach me how to do it so I can do it myself. Can't be that hard. Otherwise I will never learn.

clver16 · May 12, 2015

Hi Guys ^^, for me the initialization doesnt have the logo but it has the progress bar. But the boot part shows the apple logo with progress bar, i am at imac 13,2 smbios and using clover, and in my config plist custom logo is set to no. and my specs are, i7 3770, p8z77 v pro thunderbolt, geforce gtx 750 ti, btw before when csm was enabled, the bootscreen was stretched but when i disabled csm in bios, i get native res. My only problem is the apple logo not showing on the second boot part or the so called initialization part, before that i get a blank screen for a second after the boot part^^ help^^

Allan · May 12, 2015

Use this in your config.plist:

<dict>
    <key>Comment</key>
    <string>Bootloader Graphics - Second Stage Patch</string>
    <key>Find</key>
    <data>QYjE6xE=</data>
    <key>Name</key>
    <string>IOGraphicsFamily</string>
    <key>Replace</key>
    <data>QYjE6zE=</data>
</dict>

Credits: @pokenguyen

Edited May 13, 2015 by Allan
Credits

artur_pt · May 12, 2015

hello

sorry allan but u should give the right person the credits.. is from there .. the solution

#331

good hack

clver16 · May 12, 2015

Use this in your config.plist:

<dict>
    <key>Comment</key>
    <string>Bootloader Graphics - Second Stage Patch</string>
    <key>Find</key>
    <data>QYjE6xE=</data>
    <key>Name</key>
    <string>IOGraphicsFamily</string>
    <key>Replace</key>
    <data>QYjE6zE=</data>
</dict>

Credits:@the-darkvoid

Sir Good day the patch didn't work sir artur told me that those patches are for intelhd only is there a way for nvidia cards? thanks^^

Allan · May 13, 2015

hello

sorry allan but u should give the right person the credits.. is from there .. the solution

#331

good hack

Oh nice! Thanks @Artur-pt

Post edited.

JahStories · May 13, 2015

ehi guys,

The patch needs nvinjection to show the logo, but i've noticed that doing so, dual screen (hdmi & dvi) doesn't work anymore, only dvi works.

So i switched back, disabling nvinjection and now i've a fully working dual screen setup, but the apple logo is gone again.

bojan · May 18, 2015

Hi,

Is there anyone who can help me edit my DSDt.aaml file in order to get fully working boot on Yosemite 10.10.3. ?

My PC specification:

Z77-DS3H, i5 3570k and MSI GTX 760 Twin Frozr.

I tried to edit it myself but all that I did was edit GFX0 to GFX1. I applied all the fixes to clover plist.config which were mentioned here but nothing changed. IOFBNeedsRefresh command still shows YES for all the ports. Everything is ok with the first boot stage, but the second one is just a black screen with a pointer followed by a third stage with a loading bar in the middle.

I uploaded the ioreg, DSDT.aml, and config.plist.

https://www.dropbox.com/sh/lao6n3q580pkdiw/AADNM2xV8Cplt-2SFFat1Q7va?dl=0

Please, guys.... I am desperate

arsradu · September 5, 2015

You never have (boot-display) if you never set it.

I've no idea why your nvidia ioreg port values just simple like that.. Is that bad/damaged gpu card, or disabled nv drivers?

I dont know this is this the right place to discuss it here, or rebump old topic here. Just before you go make sure you already done backup your clean (working) clover config since it inject properties to registry and can be end with bad results.

# Get gfxutil, eg from darwindumper here (https://bitbucket.org/blackosx/darwindumper/downloads) cd ~/Desktop && cp ~/Downloads/DarwinDumper_v2.9.8/DarwinDumper.app/Contents/Resources/Tools/gfxutil . # skip this step if you never set devices properties before ioreg -lw0 -p IODeviceTree -n efi -r -x | grep device-properties | sed 's/.*<//;s/>.*//;' > device-properties.hex && ./gfxutil -s -n -i hex -o xml device-properties.hex device-properties.xml # edit / make new device properties xml (3 ports)# value can be <string> or <data> (base64), convert here (https://blog.thrsh.net/osx86.html) <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"><plist version="1.0"><dict>  <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>  <dict>    <!-- Primary display -->    <key>@2,AAPL,boot-display</key>    <string>0x00000001</string>     <!-- Optional: set type as HDMI -->    <key>@2,connector-type</key>    <string>0x00000800</string>     <!-- start: regular values -->    <key>@0,compatible</key>    <string>NVDA,NVMac</string>    <key>@0,device_type</key>    <string>display</string>    <key>@0,name</key>    <string>NVDA,Display-A</string>    <key>@1,compatible</key>    <string>NVDA,NVMac</string>    <key>@1,device_type</key>    <string>display</string>    <key>@1,name</key>    <string>NVDA,Display-B</string>    <key>@2,compatible</key>    <string>NVDA,NVMac</string>    <key>@2,device_type</key>    <string>display</string>    <key>@2,name</key>    <string>NVDA,Display-C</string>    <key>VRAM,totalsize</key>    <string>0x40000000</string>    <key>device_type</key>    <string>NVDA,Parent</string>    <key>model</key>    <string>Nvidia GeForce GTX 650</string>    <key>rom-revision</key>    <string>80.07.35.00.0B</string>    <!-- end: regular values -->  </dict></dict></plist> # add another additional port if you got black screen, eg (4 ports): <key>@3,compatible</key><string>NVDA,NVMac</string><key>@3,device_type</key><string>display</string><key>@3,name</key><string>NVDA,Display-D</string> # and experimental set active port, where x can be: 0 to (total ports - 1) <!-- Primary display --><key>@x,AAPL,boot-display</key><string>0x00000001</string> # with nvdia webdriver even more simple, just add (1/2 properties) below to device properties (with injectnvidia=no) <!-- Primary display --><key>@x,AAPL,boot-display</key><string>0x00000001</string><!-- Optional: set type as HDMI --><key>@x,connector-type</key> # after all done, convert xml to bin, and copy paste to clover properties & set "inject" to ON ./gfxutil -i xml -o hex device-properties.xml device-properties.hex && echo $'---' && cat device-properties.hex && echo $'\n---'

Ok, let's revive this thread a little, since there have been some breakthroughs, thanks to cecekpawon.

Now, before we continue, I just want to let you know that I edited my device-properties.plist to match my case, which is the display being Display-B@1 according to ioreg. In your example you used Display-C@2. Also, I don't have the display connected via DVI or HDMI, but via D-Sub (VGA) since my monitor does not have a digital port. Also, I don't have proprietary Nvidia drivers installed. I'm running on stock OS X drivers. Anyway, this issue occurs with or without Nvidia drivers. So, I think we can safely skip this hypothesis.

Anyway, so what I did so far is this:

1. Created a device-properties.plist and device-properties.hex using Darwin Dumper. Sorry, but I couldn't figure out how to do that directly with gfxutil.

2. I tried using

./gfxutil -f display

to determine my display (which I already knew where it was from the Clover's preboot.log file).

And that showed

DevicePath = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)

But I couldn't make it create a new device-properties.plist. If you know how to do that, please, share.

3. So I edited the plist file created by DarwinDumper (by checking the box for Device Properties)

And here is the result

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>

<dict>

<key>@1,AAPL,boot-display</key>

<key>@0,compatible</key>

<string>NVDA,NVMac</string>

<key>@0,device_type</key>

<string>display</string>

<string>NVDA,Display-A</string>

<key>@1,compatible</key>

<string>NVDA,NVMac</string>

<key>@1,device_type</key>

<string>display</string>

<string>NVDA,Display-B</string>

<key>VRAM,totalsize</key>

<key>device_type</key>

<string>NVDA,Parent</string>

<key>model</key>

<string>MSi GeForce GTX 650</string>

<key>rom-revision</key>

<key>@2,compatible</key>

<string>NVDA,NVMac</string>

<key>@2,device_type</key>

<string>display</string>

<string>NVDA,Display-C</string>

</dict>

I also uploaded the entire device-properties.plist to see what else is in there.

Also, something I really am not sure is correct for my case is this:

<key>VRAM,totalsize</key>    
<string>0x40000000</string> // Is this value correct for me? My video card has 2GB of VRAM.     
<key>device_type</key>    
<string>NVDA,Parent</string>    
<key>model</key>    
<string>MSi GeForce GTX 650</string> // I tweaked this a little to match preboot.log information (Model=MSi GeForce GTX 650)    
<key>rom-revision</key>    
<string>80.07.35.00.0B</string> // How did you get across this information?

Also, I don't know what kind of scripts you're using on your blog, but accessing it with Safari just keeps refreshing the page over and over and over again. Just letting you know.

@cecekpawon, any insight on this? We're relying on your feedback, man.

device-properties.plist.zip

cecekpawon · September 16, 2015

Hello arsradu,

First, your plist contain some unicode chars, which throwed an error:

$ plutil -lint device-properties.plist

Next, edit with propper plist editor / adv text editor + able to showing foreign chars

Assumed this is your current product (or this), with native drivers (no webdriver)

Port 0: DVI-D
Port 1: VGA
Port 2: HDMI

The sample bellow with attached HDMI (Port x=2) cable to monitor, change your "@x,AAPL,boot-display" value.

Also change your BIOS primary display option to Auto / PCIE (if presents).

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
  <dict>
    <!-- Primary display -->
    <key>@2,AAPL,boot-display</key>
    <string>0x00000001</string>

    <!-- Port: DVI -->
    <key>@0,compatible</key>
    <string>NVDA,NVMac</string>
    <key>@0,device_type</key>
    <string>display</string>
    <key>@0,name</key>
    <string>NVDA,Display-A</string>

    <!-- Port: VGA -->
    <key>@1,compatible</key>
    <string>NVDA,NVMac</string>
    <key>@1,device_type</key>
    <string>display</string>
    <key>@1,name</key>
    <string>NVDA,Display-B</string>

    <!-- Port: HDMI -->
    <key>@2,compatible</key>
    <string>NVDA,NVMac</string>
    <key>@2,device_type</key>
    <string>display</string>
    <key>@2,name</key>
    <string>NVDA,Display-C</string>

    <!-- start: regular values -->
    <key>VRAM,totalsize</key>
    <string>0x40000000</string>
    <key>device_type</key>
    <string>NVDA,Parent</string>
    <key>model</key>
    <string>MSi GeForce GTX 650</string>
    <key>rom-revision</key>
    <string>80.07.35.00.0B</string>
    <!-- end: regular values -->
  </dict>

  <key>PciRoot(0x0)/Pci(0x14,0x0)</key>
  <dict>
    <key>AAPL,clock-id</key>
    <data>AA==</data>
    <key>AAPL,current-available</key>
    <data>sAQ=</data>
    <key>AAPL,current-extra</key>
    <data>vAI=</data>
    <key>AAPL,current-in-sleep</key>
    <data>6AM=</data>
    <key>built-in</key>
    <data>AA==</data>
    <key>device_type</key>
    <string>XHCI</string>
  </dict>

  <key>PciRoot(0x0)/Pci(0x1a,0x0)</key>
  <dict>
    <key>AAPL,clock-id</key>
    <data>AQ==</data>
    <key>AAPL,current-available</key>
    <data>sAQ=</data>
    <key>AAPL,current-extra</key>
    <data>vAI=</data>
    <key>AAPL,current-in-sleep</key>
    <data>6AM=</data>
    <key>built-in</key>
    <data>AA==</data>
    <key>device_type</key>
    <string>EHCI</string>
  </dict>

  <key>PciRoot(0x0)/Pci(0x1b,0x0)</key>
  <dict>
    <key>MaximumBootBeepVolume</key>
    <data>AA==</data>
    <key>PinConfigurations</key>
    <data>AA==</data>
    <key>layout-id</key>
    <data>AQAAAA==</data>
  </dict>

  <key>PciRoot(0x0)/Pci(0x1d,0x0)</key>
  <dict>
    <key>AAPL,clock-id</key>
    <data>Ag==</data>
    <key>AAPL,current-available</key>
    <data>sAQ=</data>
    <key>AAPL,current-extra</key>
    <data>vAI=</data>
    <key>AAPL,current-in-sleep</key>
    <data>6AM=</data>
    <key>built-in</key>
    <data>AA==</data>
    <key>device_type</key>
    <string>EHCI</string>
  </dict>

  <key>PciRoot(0x0)/Pci(0x3,0x0)</key>
  <dict>
    <key>MaximumBootBeepVolume</key>
    <data>AA==</data>
    <key>PinConfigurations</key>
    <data>AA==</data>
    <key>layout-id</key>
    <data>AQAAAA==</data>
  </dict>
</dict>
</plist>

With Clover, you can do a simple test by attaching cable to first port (0: DVI-D) & inject NVIDIA, to check your 2nd boot-stage.

arsradu · September 16, 2015

Hello arsradu,

First, your plist contain some unicode chars, which throwed an error:

$ plutil -lint device-properties.plist

Next, edit with propper plist editor / adv text editor + able to showing foreign chars

Assumed this is your current product (or this), with native drivers (no webdriver)

Port 0: DVI-D
Port 1: VGA
Port 2: HDMI

The sample bellow with attached HDMI (Port x=2) cable to monitor, change your "@x,AAPL,boot-display" value.

Also change your BIOS primary display option to Auto / PCIE (if presents).

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
  <dict>
    <!-- Primary display -->
    <key>@2,AAPL,boot-display</key>
    <string>0x00000001</string>

    <!-- Port: DVI -->
    <key>@0,compatible</key>
    <string>NVDA,NVMac</string>
    <key>@0,device_type</key>
    <string>display</string>
    <key>@0,name</key>
    <string>NVDA,Display-A</string>

    <!-- Port: VGA -->
    <key>@1,compatible</key>
    <string>NVDA,NVMac</string>
    <key>@1,device_type</key>
    <string>display</string>
    <key>@1,name</key>
    <string>NVDA,Display-B</string>

    <!-- Port: HDMI -->
    <key>@2,compatible</key>
    <string>NVDA,NVMac</string>
    <key>@2,device_type</key>
    <string>display</string>
    <key>@2,name</key>
    <string>NVDA,Display-C</string>

    <!-- start: regular values -->
    <key>VRAM,totalsize</key>
    <string>0x40000000</string>
    <key>device_type</key>
    <string>NVDA,Parent</string>
    <key>model</key>
    <string>MSi GeForce GTX 650</string>
    <key>rom-revision</key>
    <string>80.07.35.00.0B</string>
    <!-- end: regular values -->
  </dict>

  <key>PciRoot(0x0)/Pci(0x14,0x0)</key>
  <dict>
    <key>AAPL,clock-id</key>
    <data>AA==</data>
    <key>AAPL,current-available</key>
    <data>sAQ=</data>
    <key>AAPL,current-extra</key>
    <data>vAI=</data>
    <key>AAPL,current-in-sleep</key>
    <data>6AM=</data>
    <key>built-in</key>
    <data>AA==</data>
    <key>device_type</key>
    <string>XHCI</string>
  </dict>

  <key>PciRoot(0x0)/Pci(0x1a,0x0)</key>
  <dict>
    <key>AAPL,clock-id</key>
    <data>AQ==</data>
    <key>AAPL,current-available</key>
    <data>sAQ=</data>
    <key>AAPL,current-extra</key>
    <data>vAI=</data>
    <key>AAPL,current-in-sleep</key>
    <data>6AM=</data>
    <key>built-in</key>
    <data>AA==</data>
    <key>device_type</key>
    <string>EHCI</string>
  </dict>

  <key>PciRoot(0x0)/Pci(0x1b,0x0)</key>
  <dict>
    <key>MaximumBootBeepVolume</key>
    <data>AA==</data>
    <key>PinConfigurations</key>
    <data>AA==</data>
    <key>layout-id</key>
    <data>AQAAAA==</data>
  </dict>

  <key>PciRoot(0x0)/Pci(0x1d,0x0)</key>
  <dict>
    <key>AAPL,clock-id</key>
    <data>Ag==</data>
    <key>AAPL,current-available</key>
    <data>sAQ=</data>
    <key>AAPL,current-extra</key>
    <data>vAI=</data>
    <key>AAPL,current-in-sleep</key>
    <data>6AM=</data>
    <key>built-in</key>
    <data>AA==</data>
    <key>device_type</key>
    <string>EHCI</string>
  </dict>

  <key>PciRoot(0x0)/Pci(0x3,0x0)</key>
  <dict>
    <key>MaximumBootBeepVolume</key>
    <data>AA==</data>
    <key>PinConfigurations</key>
    <data>AA==</data>
    <key>layout-id</key>
    <data>AQAAAA==</data>
  </dict>
</dict>
</plist>

With Clover, you can do a simple test by attaching cable to first port (0: DVI-D) & inject NVIDIA, to check your 2nd boot-stage.

Well, I guess I did something right, cause now I have the second stage loading bar, centered. Still no logo on top of it though.

The logo is present, no problem, for the first-stage. But, on the second-stage, only the loading bar is displayed. It's an improvement, nonetheless.

So, to sum up, here is what I did:

I extracted the device-properties.hex (and plist, but we're not gonna use that) with DarwinDumper.
I used gfxutil to convert the device-properties.hex to device-properties.xml, so I can edit it.
I edited it, so that it matches my VGA port (Port #1).
I used gfxutil again to convert it back to hex.
I read the hex with HexEdit and exported the output as txt so I can copy-paste it into Clover config.

Unfortunately I can't test with DVI cable cause I don't have one. Also...my monitor doesn't have a DVI-in port. So...I can't really connect via DVI.

Mirone · September 16, 2015

@arsradu,

You must use an EDID editing on your config.plist

and use CsmVideoDxe-64.efi EFI / clover / drivers64UEFI.

In addition to the issues in your DSDT here already mentioned.

my example:

<key>Graphics</key>
	<dict>
		<key>CustomEDID</key>
		<data>
		AP///////wAGECeSHwAjFiMWAQS1PCJ4Im+xp1VMniUMUFS974BxT4HAgQCB
		gJUAqcCzAAEBAjqAGHE4LUBYLEUAVlAhAAAeAAAA/wBDMDJKOTAwWEYyR0MK
		AAAA/QAYSxpRFwAKICAgICAgAAAA/ABUaHVuZGVyYm9sdAogAdYCAyXxTZAf
		BBMFFAMSICEiBxYjCQcHgwEAAOIAD2cDDAAQALgtAR0AclHQHiBuKFUAVlAh
		AAAeAR0AvFLQHiC4KFVAVlAhAAAeAR2AGHEcFiBYLCUAVlAhAACeAR2A0HIc
		FiAQLCWAVlAhAACeAAAAAAAAAAAAAAAAAAAAAAAAuA==
		</data>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
		<key>NvidiaSingle</key>
		<false/>
		<key>PatchVBios</key>
		<true/>
		<key>VideoPorts</key>
		<integer>3</integer>
	</dict>

arsradu · September 16, 2015

@arsradu,

You must use an EDID editing on your config.plist

and use CsmVideoDxe-64.efi EFI / clover / drivers64UEFI.

In addition to the issues in your DSDT here already mentioned.

my example:

<key>Graphics</key>
	<dict>
		<key>CustomEDID</key>
		<data>
		AP///////wAGECeSHwAjFiMWAQS1PCJ4Im+xp1VMniUMUFS974BxT4HAgQCB
		gJUAqcCzAAEBAjqAGHE4LUBYLEUAVlAhAAAeAAAA/wBDMDJKOTAwWEYyR0MK
		AAAA/QAYSxpRFwAKICAgICAgAAAA/ABUaHVuZGVyYm9sdAogAdYCAyXxTZAf
		BBMFFAMSICEiBxYjCQcHgwEAAOIAD2cDDAAQALgtAR0AclHQHiBuKFUAVlAh
		AAAeAR0AvFLQHiC4KFVAVlAhAAAeAR2AGHEcFiBYLCUAVlAhAACeAR2A0HIc
		FiAQLCWAVlAhAACeAAAAAAAAAAAAAAAAAAAAAAAAuA==
		</data>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
		<key>NvidiaSingle</key>
		<false/>
		<key>PatchVBios</key>
		<true/>
		<key>VideoPorts</key>
		<integer>3</integer>
	</dict>

Well, after adding the custom EDID, selecting PatchVBios and adding the number of ports on my video card (are the last ones necessary?), I got something that can be considered pretty close to what I had in mind for a perfect boot.

Have a look at the short video here. Sorry for the poor video quality.

One thing seems different after adding the EDID and making the other changes: the logo and the loading bar seem...a bit bigger. They were a bit smaller before. Maybe something related to the resolution? Any idea how can I change that? It doesn't look like the native resolution.

Mirone · September 16, 2015

This is a perfect boot to hackintosh,

unknown to someone who does not have this

Flash before the second phase (at least in Desktop)

why on laptops is like a real mac without this flash before

the second phase.

regarding the size of the logo and bar, where did you get

the values of its EDID?

cecekpawon · September 17, 2015

Hey, congrats for your (perfect) 2nd boot-stage

Mirones was right, without uEFI support on GPU, CsmVideoDxe driver is needed. And I completly agree, with hackintosh, screen flash before 2nd boot-stage is normal even with "IOFBNeedsRefresh=False" in ioReg as Pike's said. For NVidia (inject=true), adding port value is pretty useless, because it's seem hardcoded (compared to ATI injection), sorry if I'm wrong. PatchVBios is auto mode to find, correct & set highest resolution available / by your config ScreenResolution value. PatchVBiosBytes to manually force patch / overriding resolution. I was lucky to have 1920x1080 and apply patch from projectosx (which now inaccessible) to force 1920x1080 (16:9) -> 1920x1200 (4:3) to avoid streched boot screen. Sample bellow:

<key>Graphics</key>
<dict>
  <key>PatchVBiosBytes</key>
  <array>
    <dict>
      <key>Find</key>
      <data>
      NC0nKJAroL+cj5a5jh8AAAA=
      </data>
      <key>Replace</key>
      <data>
      Ej/v74MBG9ixr6/ZBABBJRI=
      </data>
    </dict>
    <dict>
      <key>Find</key>
      <data>
      QAa6sAQ=
      </data>
      <key>Replace</key>
      <data>
      gAe6sAQ=
      </data>
    </dict>
    <dict>
      <key>Find</key>
      <data>
      KAAZACgYCAgF
      </data>
      <key>Replace</key>
      <data>
      gAewBPBLECYF
      </data>
    </dict>
    <dict>
      <key>Find</key>
      <data>
      gg8DAQAACAQUAAAIFw==
      </data>
      <key>Replace</key>
      <data>
      fQEDfQEIASDAA///IA==
      </data>
    </dict>
  </array>
</dict>

arsradu · September 17, 2015

This is a perfect boot to hackintosh,

unknown to someone who does not have this

Flash before the second phase (at least in Desktop)

why on laptops is like a real mac without this flash before

the second phase.

regarding the size of the logo and bar, where did you get

the values of its EDID?

The EDID was extracted with DarwinDumper. And thanks for the tip.

By the way, Clover seems to have a "Inject EDID" feature built-in. So no need to manually add a custom one.

Hey, congrats for your (perfect) 2nd boot-stage

Mirones was right, without uEFI support on GPU, CsmVideoDxe driver is needed. And I completly agree, with hackintosh, screen flash before 2nd boot-stage is normal even with "IOFBNeedsRefresh=False" in ioReg as Pike's said. For NVidia (inject=true), adding port value is pretty useless, because it's seem hardcoded (compared to ATI injection), sorry if I'm wrong. PatchVBios is auto mode to find, correct & set highest resolution available / by your config ScreenResolution value. PatchVBiosBytes to manually force patch / overriding resolution. I was lucky to have 1920x1080 and apply patch from projectosx (which now inaccessible) to force 1920x1080 (16:9) -> 1920x1200 (4:3) to avoid streched boot screen. Sample bellow:
<key>Graphics</key>
<dict>
  <key>PatchVBiosBytes</key>
  <array>
    <dict>
      <key>Find</key>
      <data>
      NC0nKJAroL+cj5a5jh8AAAA=
      </data>
      <key>Replace</key>
      <data>
      Ej/v74MBG9ixr6/ZBABBJRI=
      </data>
    </dict>
    <dict>
      <key>Find</key>
      <data>
      QAa6sAQ=
      </data>
      <key>Replace</key>
      <data>
      gAe6sAQ=
      </data>
    </dict>
    <dict>
      <key>Find</key>
      <data>
      KAAZACgYCAgF
      </data>
      <key>Replace</key>
      <data>
      gAewBPBLECYF
      </data>
    </dict>
    <dict>
      <key>Find</key>
      <data>
      gg8DAQAACAQUAAAIFw==
      </data>
      <key>Replace</key>
      <data>
      fQEDfQEIASDAA///IA==
      </data>
    </dict>
  </array>
</dict>

Thanks man! I appreciate the help.

Now I realized it's not just the logo and the loading bar. Clover UI is also at the same resolution. And it is specified in its GUI section to use 1440x900 (which is my monitor's native resolution with a 16:9 aspect ratio), but from my experience, even without manually specifying it, it will still display it properly. So I don't think that part makes any difference.

The things changed when I added that EDID though and patched VBios. So somewhere the resolution detection is not right.

In your example, you got 4 patches? Am I correct? And where the hell do you guys get those values from? What is that? Base64? And if yes, which values should I put in there? How would I know what should I be looking for and what to replace?

cecekpawon · September 17, 2015

As I said, just lucky had same resolution & applied existing patch, maybe someone can explain it for you.. Googling (yes, it's base64encode) and found this old thread (originally by Pene in projectosx which now gone). If I can remember, that patch try to replace existing / unused resolution to new desire one. Some guy on this forum, apply the current patches too.

arsradu · September 17, 2015

As I said, just lucky had same resolution & applied existing patch, maybe someone can explain it for you.. Googling (yes, it's base64encode) and found this old thread (originally by Pene in projectosx which now gone). If I can remember, that patch try to replace existing / unused resolution to new desire one. Some guy on this forum, apply the current patches too.

You were lucky indeed. I couldn't find anything for 1440x900. And the threads I read around here are very technical, and really, really confusing. So basically Clover Patch VBios doesn't know my resolution. Did I get this right?

I asked you something above, but I guess you missed that part:

    <key>VRAM,totalsize</key>
    <string>0x40000000</string> //I replaced this with 80000000 since I've got 2GB or RAM. I hope that was ok.
    <key>device_type</key>
    <string>NVDA,Parent</string>
    <key>model</key>
    <string>MSi GeForce GTX 650</string>
    <key>rom-revision</key>
    <string>80.07.35.00.0B</string> // where did you get this value from? I doubt it applies to all Nvidia GTX 650s around the world.

can we get back the apple logo on boot?

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites