Jump to content
arsradu

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

391 posts in this topic

Recommended Posts

Because I can't stop messing with stuff...

 

When I extracted the device properties earlier, my graphics was being injected via SSDT. Although I hadn't set it in the SSDT, when I extracted the properties both ports had a display-cfg value (0x00030103 for port 0 and 0x0100ffff for port 1).

 

When I removed the display-cfg values a little while ago from my device properties and injected the resulting hex string I got a brief flash going from first to second stage. Checking the IOReg both values were ffffffff.

 

So maybe the key to having no flash between stages (for nVidia anyway) is to have display-cfg set?

Share this post


Link to post
Share on other sites
Advertisement

Because I can't stop messing with stuff...

 

When I extracted the device properties earlier, my graphics was being injected via SSDT. Although I hadn't set it in the SSDT, when I extracted the properties both ports had a display-cfg value (0x00030103 for port 0 and 0x0100ffff for port 1).

 

When I removed the display-cfg values a little while ago from my device properties and injected the resulting hex string I got a brief flash going from first to second stage. Checking the IOReg both values were ffffffff.

 

So maybe the key to having no flash between stages (for nVidia anyway) is to have display-cfg set?

 

It's itching, huh? :P

 

How can one know which value should be added for display-cfg? Ok, it's 0x00030103 for port 0 and 0x0100ffff for port 1. But what about other posts? I'll try the one for port 1 and come back with updates.

 

Update: it doesn't seem to affect that gap in any way. At least in my case. Are you using stock or proprietary Nvidia drivers? 

 

arsradu,

you were right I was mistaken for a Real Mac

where it is possible to notice the mouse cursor in the upper left corner

look at this video.

the flash reason is because of course I am

almost 100% sure of that.

Interesting... :)

 

Ok, I didn't get this:

 

the flash reason is because of course I am

almost 100% sure of that.

 

Uhm....what? :)) And can it really be the cause for that gap between the two stages? Also, isn't that a MacBOOK? Meaning a laptop? I thought we were talking about desktop graphics here. :P

 

 

270X

Ok. Added as 270X. Thank you.

Still, could you please, add a bit more about what exactly did you do to get it to work on your card? And can this be achieved without DSDT editing? I'm thinking about Clover DSDT patches only.

4096 MB (4 GB)  0x100000000 not working VBIOS. It show 0MB in About This Mac

As Mirone said, this is most likely only cosmetic.

 

However the value should be correct... But maybe I missed something.

 

Guys, can anyone confirm the VRAM hex values from the first post? They look ok to me. But I would like a second opinion on that.

Share this post


Link to post
Share on other sites

Uhm....what? :)) And can it really be the cause for that gap between the two stages? Also, isn't that a MacBOOK? Meaning a laptop? I thought we were talking about desktop graphics here. :P

 

 

the above video posted by cecekPawon
It shows a boot equal to a macbook.

Share this post


Link to post
Share on other sites

@arsradu: I'm using the stock El Capitan kexts.

 

I'm not sure whether those display-cfg values were injected by Clover or OS X (as I said, I didn't define them in the SSDT). They were extracted by IOReg when creating the device properties xml file. I just noticed that removing them caused a brief flash which wasn't there before.

Share this post


Link to post
Share on other sites

 

the above video posted by cecekPawon
It shows a boot equal to a macbook.

 

Oh, I see now.

 

There is still a gap there. But..yes, the cursor is present on the second stage boot.

@arsradu: I'm using the stock El Capitan kexts.

 

I'm not sure whether those display-cfg values were injected by Clover or OS X (as I said, I didn't define them in the SSDT). They were extracted by IOReg when creating the device properties xml file. I just noticed that removing them caused a brief flash which wasn't there before.

 

I didn't define anything in either Clover, or SSDT.... At least not manually. But I'll take a look at my IOreg tonight and see if the values I get (if I get any such values) are different in comparison to what you got. Anyway, so far, it doesn't seem to affect that gap in any way.

Share this post


Link to post
Share on other sites

in iMac late 2014:

That's a beautiful machine. Still, that display, from that angle... :)) Not the best example. I'm sure it probably looks better in person. But still. :))

 

Anyway, so this one is gap-less. And it's a "desktop". Then what the hell is the cause for that gap?

Share this post


Link to post
Share on other sites

have you tried clover devices arbitrary inject with new rehabman fix? sample here ..

I'm not sure the question was for me... Probably not. :))

 

Anyway, I did see that before. However I just noticed a little bug in that example (of course, it's just an example, and Slice also mentions it's not perfect). But I'm not sure if I got the implementation correctly.

 

So, under Devices, we add a new Array called Arbitrary

<key>Arbitrary</key>     
<array>     
</array>

In which we add this?

<dict>                
<key>PciAddr</key>                
<string>01:00.00</string>                
<key>Comment</key>                
<string>Nvidia Geforce card in PCIe slot</string>                
<key>CustomProperties</key>                
<array>                    
<dict>                        
<key>Key</key>                        
<string>model</string>                        
<key>Value</key>                        
<string>Gigabyte GeForce 7300 LE</string>                    
</dict>                    
<dict>                        
<key>Key</key>                        
<string>AAPL,boot-device</string> //I suppose this should become @1,APPL,boot-display. Right?                        
<key>Value</key>                        
<data>AQAAAA==</data> // I never knew where did this "data" come from. I know it's Base64. But Base64 of what? Can we add a string here? Like <string>0x00000001</string> ?                    
</dict>                
</array>            
</dict>

Share this post


Link to post
Share on other sites

@arsradu: I'm using the stock El Capitan kexts.

 

I'm not sure whether those display-cfg values were injected by Clover or OS X (as I said, I didn't define them in the SSDT). They were extracted by IOReg when creating the device properties xml file. I just noticed that removing them caused a brief flash which wasn't there before.

 

Display-cfg value in IOreg (without injecting/specifying anything) is ffffffff, as you said. However, using the value you mentioned above for port @1 (0x0100ffff), I had the same behavior as without it (flashing between the two stages). Maybe there are different values for different cards and not just for different ports? Just saying.

Share this post


Link to post
Share on other sites

Maybe try 0x00030103. IIRC 0x0100ffff was on my unused port. When I googled both values I found references to them which suggests they may be somewhat generic.

 

Wanna hear something funny? The injected value in Clover doesn't actually get injected (IOreg still says FFFFFFFF). Result? Well, same issue, of course.

Share this post


Link to post
Share on other sites

Out of curiosity I checked my macbook pro to see if there was any reason why it didn't have the flash and why my hackintosh does.  Only thing I could find different was this key under iGPU.  Not sure if this is it or if setting display-cfg will do it.  If I knew what to set display-cfg to I would try it, but haven't quite figured that out.

        <key>StartupDisplay</key>
        <data>
        R04CAAAAAAAACgAAQAYAACD8ABAAAAAAAAoAAEAGAACgAAAAAAAAAAAAAAAu
        AAAAAAAAAAAAAAAwAAAAIAAAAAMAAAAGAAAAAAAAAAAAAAAAAAABAAAAAAAA
        AACtCw3wAQAAAAAAAAAACgAAQAYAACD8ABAAAAAAAAoAAEAGAACgAAAAAAAA
        AAAAAAAuAAAAAAAAAAAAAAAwAAAAIAAAAAMAAAAGAAAAAAAAAAAAAAA=
        </data>

Share this post


Link to post
Share on other sites
Wanna hear something funny? The injected value in Clover doesn't actually get injected (IOreg still says FFFFFFFF). Result? Well, same issue, of course.

 

I'm injecting the values as part of the device properties, not via Clover. Here's how my device properties look:

 

 

 

<?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(0x2,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>@0,AAPL,boot-display</key>
<string>0x00000001</string>
<key>@0,compatible</key>
<string>NVDA,NVMac</string>
<key>@0,connector-type</key>
<string>0x00000800</string>
<key>@0,device_type</key>
<string>display</string>
<key>@0,display-cfg</key>
<string>0x00030103</string>
<key>@0,name</key>
<string>NVDA,Display-A</string>
<key>@1,compatible</key>
<string>NVDA,NVMac</string>
<key>@1,connector-type</key>
<string>0x00000800</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,display-cfg</key>
<string>0x0100ffff</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>
<key>NVCAP</key>
<data>
BAAAAAAAAwAIAAAAAAAABwAAAAA=
</data>
<key>VRAM,totalsize</key>
<string>0x40000000</string>
<key>device_type</key>
<string>NVDA,Parent</string>
<key>model</key>
<string>NVIDIA GeForce 210</string>
<key>rom-revision</key>
<string>70.18.5F.00.06</string>
</dict>
</dict>
</plist>
 

 

 

 

The NVCAP value is extracted from my card BIOS with NVCAP Maker. It's not the generic one that Clover etc uses.

Share this post


Link to post
Share on other sites

I'm injecting the values as part of the device properties, not via Clover. Here's how my device properties look:

 

 

 

<?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(0x2,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>@0,AAPL,boot-display</key>
<string>0x00000001</string>
<key>@0,compatible</key>
<string>NVDA,NVMac</string>
<key>@0,connector-type</key>
<string>0x00000800</string>
<key>@0,device_type</key>
<string>display</string>
<key>@0,display-cfg</key>
<string>0x00030103</string>
<key>@0,name</key>
<string>NVDA,Display-A</string>
<key>@1,compatible</key>
<string>NVDA,NVMac</string>
<key>@1,connector-type</key>
<string>0x00000800</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,display-cfg</key>
<string>0x0100ffff</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>
<key>NVCAP</key>
<data>
BAAAAAAAAwAIAAAAAAAABwAAAAA=
</data>
<key>VRAM,totalsize</key>
<string>0x40000000</string>
<key>device_type</key>
<string>NVDA,Parent</string>
<key>model</key>
<string>NVIDIA GeForce 210</string>
<key>rom-revision</key>
<string>70.18.5F.00.06</string>
</dict>
</dict>
</plist>
 

 

 

The NVCAP value is extracted from my card BIOS with NVCAP Maker. It's not the generic one that Clover etc uses.

 

 

Cool! Thank you. I'll give that a try in a little while.

 

What exactly does that NVCAP value do? What's it for?

 

Also, I suppose the data you injected is Base64 encode for something like this: 0400000000002100000000000000000700000000 ?

Share this post


Link to post
Share on other sites

Yeah it was plain text when I pasted it into PlistEdit. But it shows up as Base64 when I read it out in TextEdit for pasting here.

 

As far as I know NVCAP is for setting up the video ports. I'm not sure if it has any effect but I've always tended to use my card's value when injecting.

Share this post


Link to post
Share on other sites

Yeah it was plain text when I pasted it into PlistEdit. But it shows up as Base64 when I read it out in TextEdit for pasting here.

 

As far as I know NVCAP is for setting up the video ports. I'm not sure if it has any effect but I've always tended to use my card's value when injecting.

 

Ok, cause I tried encoding that string with an online Base64 encoder (I hope it's the same thing...) and it resulted in something like this: MDQwMDAwMDAwMDAwMjEwMDAwMDAwMDAwMDAwMDAwMDcwMDAwMDAwMA==

 

Pretty creepy looking, if you ask me. :)) Anyway, I added 0x00030103 to my port nr 1, since that's the one that I'm using.

And, if you want, you can take a look at my xml output below.

 

I didn't add connector-type data since I have no such thing in IOreg, and no idea where did you get those from. :))

 

 

 

	<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
	<dict>
		<!-- Primary display -->
		<key>@1,AAPL,boot-display</key>
		<string>0x00000001</string>
		
		<!-- Port: DVI-D -->
		<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>
		<key>@1,display-cfg</key>
			<string>0x00030103</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>NVCAP</key>
			<data>MDQwMDAwMDAwMDAwMjEwMDAwMDAwMDAwMDAwMDAwMDcwMDAwMDAwMA==</data>
		<key>VRAM,totalsize</key>
			<string>0x80000000</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.04</string>
		<!-- end: regular values -->
	</dict>

 

 

 

Anyway, if that looks ok, it didn't make any difference to the actual gap... It's still there. However, adding display-cfg this way DID make a difference in the IOreg output. It does now read that value (0x00030103), assuming it's the correct one, for port @1.

Share this post


Link to post
Share on other sites

I think the connector data is supposed to help define whether the port is DVI/VGA etc. Although you'll see that in most DSDT fixes it's set as 0x00000800 for each port. There's a lot of stuff like that in nVidia injection that seems to be technically "wrong" but somehow makes little to no difference for my desktop cards at least. Same with NVCAP. But my needs are simple so as long as I have working DVI I'm happy.

 

There must be more to getting no flash then. It was worth a try anyway.

Share this post


Link to post
Share on other sites

I think the connector data is supposed to help define whether the port is DVI/VGA etc. Although you'll see that in most DSDT fixes it's set as 0x00000800 for each port. There's a lot of stuff like that in nVidia injection that seems to be technically "wrong" but somehow makes little to no difference for my desktop cards at least. Same with NVCAP. But my needs are simple so as long as I have working DVI I'm happy.

 

There must be more to getting no flash then. It was worth a try anyway.

 

And I thank you very much for that! :)

 

I also don't need much. And since my current monitor doesn't have DVI, I had to stick to VGA for now. :( Oh well. I hope it won't be for much longer. Anyway, I don't really mind that flashing. I came a long way from the way it used to look. So I'm pretty happy with what I've got right now. Of course, if it can get better, I would love to try it. But I'm just saying, I don't mind it that much.

 

Again, big thanks for sharing your thoughts over here.

Share this post


Link to post
Share on other sites

I have this problem since Yosemite

 

https://www.youtube.com/watch?v=CUPcUl5upP0

 

I'm using Asus z97 Pro Gamer, Asus GTX strix 970 with GOP UEFI supported and dell P2715Q.

 

After try disable CSM in bios, I get 4k at clover bootloader. But problem still remain, the loading bar at left bottom left. Try to use your patch but can't pass step 2.

Here are result after run script in step 2:

<?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(0x14,0x0)</key>
	<dict>
		<key>AAPL,clock-id</key>
		<string>0x00</string>
		<key>AAPL,current-available</key>
		<string>0x04b0</string>
		<key>AAPL,current-extra</key>
		<string>0x02bc</string>
		<key>AAPL,current-in-sleep</key>
		<string>0x03e8</string>
		<key>built-in</key>
		<string>0x00</string>
		<key>device_type</key>
		<string>0x49434858</string>
	</dict>
	<key>PciRoot(0x0)/Pci(0x19,0x0)</key>
	<dict>
		<key>built-in</key>
		<string>0x01</string>
		<key>device_type</key>
		<data>
		RXRoZXJuZXQA
		</data>
	</dict>
	<key>PciRoot(0x0)/Pci(0x1a,0x0)</key>
	<dict>
		<key>AAPL,clock-id</key>
		<string>0x01</string>
		<key>AAPL,current-available</key>
		<string>0x04b0</string>
		<key>AAPL,current-extra</key>
		<string>0x02bc</string>
		<key>AAPL,current-in-sleep</key>
		<string>0x03e8</string>
		<key>built-in</key>
		<string>0x00</string>
		<key>device_type</key>
		<string>0x49434845</string>
	</dict>
	<key>PciRoot(0x0)/Pci(0x1b,0x0)</key>
	<dict>
		<key>MaximumBootBeepVolume</key>
		<string>0x00</string>
		<key>PinConfigurations</key>
		<string>0x00</string>
		<key>layout-id</key>
		<string>0x00000001</string>
	</dict>
	<key>PciRoot(0x0)/Pci(0x1d,0x0)</key>
	<dict>
		<key>AAPL,clock-id</key>
		<string>0x02</string>
		<key>AAPL,current-available</key>
		<string>0x04b0</string>
		<key>AAPL,current-extra</key>
		<string>0x02bc</string>
		<key>AAPL,current-in-sleep</key>
		<string>0x03e8</string>
		<key>built-in</key>
		<string>0x00</string>
		<key>device_type</key>
		<string>0x49434845</string>
	</dict>
</dict>
</plist>

I couldn't find any where to setup VRAM...

Share this post


Link to post
Share on other sites

I have this problem since Yosemite

 

https://www.youtube.com/watch?v=CUPcUl5upP0

 

I'm using Asus z97 Pro Gamer, Asus GTX strix 970 with GOP UEFI supported and dell P2715Q.

 

After try disable CSM in bios, I get 4k at clover bootloader. But problem still remain, the loading bar at left bottom left. Try to use your patch but can't pass step 2.

Here are result after run script in step 2:

<?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(0x14,0x0)</key>
	<dict>
		<key>AAPL,clock-id</key>
		<string>0x00</string>
		<key>AAPL,current-available</key>
		<string>0x04b0</string>
		<key>AAPL,current-extra</key>
		<string>0x02bc</string>
		<key>AAPL,current-in-sleep</key>
		<string>0x03e8</string>
		<key>built-in</key>
		<string>0x00</string>
		<key>device_type</key>
		<string>0x49434858</string>
	</dict>
	<key>PciRoot(0x0)/Pci(0x19,0x0)</key>
	<dict>
		<key>built-in</key>
		<string>0x01</string>
		<key>device_type</key>
		<data>
		RXRoZXJuZXQA
		</data>
	</dict>
	<key>PciRoot(0x0)/Pci(0x1a,0x0)</key>
	<dict>
		<key>AAPL,clock-id</key>
		<string>0x01</string>
		<key>AAPL,current-available</key>
		<string>0x04b0</string>
		<key>AAPL,current-extra</key>
		<string>0x02bc</string>
		<key>AAPL,current-in-sleep</key>
		<string>0x03e8</string>
		<key>built-in</key>
		<string>0x00</string>
		<key>device_type</key>
		<string>0x49434845</string>
	</dict>
	<key>PciRoot(0x0)/Pci(0x1b,0x0)</key>
	<dict>
		<key>MaximumBootBeepVolume</key>
		<string>0x00</string>
		<key>PinConfigurations</key>
		<string>0x00</string>
		<key>layout-id</key>
		<string>0x00000001</string>
	</dict>
	<key>PciRoot(0x0)/Pci(0x1d,0x0)</key>
	<dict>
		<key>AAPL,clock-id</key>
		<string>0x02</string>
		<key>AAPL,current-available</key>
		<string>0x04b0</string>
		<key>AAPL,current-extra</key>
		<string>0x02bc</string>
		<key>AAPL,current-in-sleep</key>
		<string>0x03e8</string>
		<key>built-in</key>
		<string>0x00</string>
		<key>device_type</key>
		<string>0x49434845</string>
	</dict>
</dict>
</plist>

I couldn't find any where to setup VRAM...

 

Ok, why can't you pass step 2? I don't get it. This is the untouched xml. Now you have to edit it for your needs. When you will start editing it, and ADDING all the information you need, you will find the place to add your VRAM value, as well.

By the way, the selected part in the screenshot is not for design. :P That's the part that you need to add and change, according to your card and port.

 

Also, if you want me to take a look at this issue, I will need your IOreg (config.plist would be nice too). To see which port are you using and apply the patch accordingly.

Share this post


Link to post
Share on other sites

Thank you, I was able to center the loading bar. But the apple logo is missing. I have tried with patch vbios and inject edid in clover config. When I try with my custom Edid (extracted from windows), I lost clover GUI, It's auto boot into mac disk (I give it 5 second countdown to select os), so I got only stage 2.

Share this post


Link to post
Share on other sites

Thank you, I was able to center the loading bar. But the apple logo is missing. I have tried with patch vbios and inject edid in clover config. When I try with my custom Edid (extracted from windows), I lost clover guide, It's auto boot into mac disk (I give it 5 second countdown to select os), so I got only stage 2.

 

Try enabling CSM in Bios. Then Patch VBios. I don't think you need to Inject EDID or use your custom one (should be the same either way). Try without it first. I have no issues without adding/injecting EDID. Works just fine with or without it.

 

Anyway, don't use both Clover Inject EDID and a custom EDID. Use only one of them. Or, for testing, try without any EDID whatsoever. See if it makes any difference.

 

I'm assuming you mean Clover GUI, not guide. :) And you shouldn't lose first stage boot logo for that. In your video, I can see first stage boot just fine. You can try posting your config. Maybe something is wrong in there.

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.

Announcements

  • Similar Content

    • By gekko.be
      I have an old Hackintosh that I have brought back to life. An ASUS P5KPLAM-SE mobo, Intel Core 2 Quad, with a Sapphire HD 5670 1GB graphics card. It used to work just fine on High Sierra 10.13.3 (I think it was .3) However I only used the DVI port. Updated to 10.13.6 and with AMD kexts rollback to the previous versions I got everything o wrk just fine: boot, HDMI video, HDMI audio etc etc. The only problem I face is that my USB keyboard and mouse freeze/hang seemingly very random... I can not seem to get it right. Unplugging and replugging the USB device makes it work again, sometimes for a few seconds sometimes for an hour ... No idea what's wrong... Have tried tons of options in clover, USBInjectall.kext with port limit patch, whatever I could find... Would there be anyone out there who would have an idea of what could be the problem?
    • By macinsane
      *This guide is deprecated and will not be maintained anymore*

      Update: Now running Mojave! Thanks to mojave2core! Yeah   Still using C2D in 2019!
      Inserted a nice and cheap GT710 that is not relying on nVidias Webdrivers and runs OOB under Mojave.
       
      Nice, seeing High Sierra running on this old but capable system! It rocks with a new ASUS GT1030
       
      Config:
      Gigabyte EP43-DS3L
      Core2Quad Q9300
      6 GB DDR2 RAM
      Asus GT1030 2GB
      Sandisk SSD 128GB
      TP-Link AC1200 Wifi USB
      Inateck KT4006 USB 3.0 PCIe (No boot)
       
      SMBIOS: iMac14,1
      Clover: 4297  4360
       
      A good deal of DSDT editing was necessary to get this machine to boot High Sierra but finally it works flawlessly, even sleep and wake!
      You NEED to have the DSDT put in place for installation because otherwise macOS doesn't recognize the SATA ports.
      There are a few important BIOS settings: SATA hast to be set to AHCI and "native" and HPET has to be run "64-bit", I'd recommend to disable IDE and the serial and parallel port.
      For the GT1030 nVidia Webdrivers are needed, have to boot with nv_disable=1 until you have them installed.
      You have to install Clover in legacy mode because this old fella does not support UEFI.
       
      Only downside: The so often recommended Inateck USB-card isn't recognized by BIOS, so you cannot boot from it. It works perfectly within macOS though, have the ac-Wifi connected to it.
      config.plist.zip
      DSDT.aml.zip
    • By eLDeus
      Hello, can't figure out why there's no Line-In input option with VoodooHDA, but I definetly have it in my built-in audio card on the motherboard.
      Thanks!
    • By Rajan Pandit
      Hai, I have i5 2500k with 8GB Ram, GA-Z86 AP-D3 Rev. 1 (F3 Bios) with Samsung EVO SSD... 
      I Installed High Sierra 10.13.6, I use ##### to activate boot... everything is fine..
      but sometime my system Freeze..... and sometimes screen freeze but mouse worked
      means system is running.. mouse is also moving.. but Screen got freeze...
      please help me to resolve.. I really frustrated now. I install many times...
      but same problem... There is no graphic card in my system...
       
      please help me.. I am attaching my clover folder.. please help
      CLOVER.zip
    • By fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

      Pre-Requisites
      8GB or larger USB drive.  Edit: Recommend 16GB or larger for macOS Catalina 10.16 Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
      1)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)

      to a folder named "SharedSupport" on your Windows NTFS drive.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

      2)  Rename InstallESDDmg.pkg to InstallESD.dmg
      3)  Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
      Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
      Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
      1.  Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
      2.  Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
      3.  Restore 4.hfs to USB second partition with BDU --->  2nd partition becomes bootable "OS X Base System"
      Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
      Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed.  Don't forget to apply the changes at the end...
      Transmac to Copy "SharedSupport" folder to OS X Base System
      1.  Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder.  Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
      2.  In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
       
      Clover Settings
      Clover configuration is required now.  The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, the hackintosh-vanilla-desktop-guide has some good explanations on the various settings available and also offers sample configuration files based on CPU type.  Also, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
      The location of the important configuration files for Clover are summarized below
      config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware).  In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine.  Reboot the system to the USB installer to install High Sierra ...
      What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
      Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app.  In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
      -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/  
      ...then start installation with the startosinstall utility...
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app  
      The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
      cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.6_18G103
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility....
       
      eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD  
      This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system.
       
      Updated Download Links for macOS Catalina 10.15.6_19G73
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
      InstallInfo.plist_edited_10.14.6.zip
      InstallInfo.plist_edited_10.15.6.zip
×