Jump to content
30960 posts in this topic

Recommended Posts

 

Maaan, that's like rocket science for most of the users. :)) It's good that you CAN do that, in case you can't get your hands on one already made from the manufacturer. But man, I don't know, I wouldn't go into that on my own. :)) Also, is this only for ATI/Radeon cards?

Maaan, that's like rocket science for most of the users. :)) It's good that you CAN do that, in case you can't get your hands on one already made from the manufacturer. But man, I don't know, I wouldn't go into that on my own. :)) Also, is this only for ATI/Radeon cards?

Sorry if it's off topic but it's related to the recent posts :)

 

Take a look at this thread: http://www.insanelymac.com/forum/topic/299614-asus-eah6450-video-bios-uefi-gop-upgrade-and-gop-uefi-binary-in-efi-for-many-ati-cards/page-1?hl=+uefi%20+maker

 

They published an app for making a UEFI vBIOS from the original BIOS and it's for AMD GPUs if anyone is interested.

 

I tested it on my AMD 5770 GPU and it didn't brick my GPU but use it at your own RISK!!! :rofl:

  • Like 1

Slice, see this please:

 

1:175  0:000  === [ GetAcpiTablesList ] =================================

1:175  0:000  Get Acpi Tables List from RSDT:
1:175  0:000   - [00]: FACP  A M I len=132
1:175  0:000   - [01]: APIC  A M I len=114
1:175  0:000   - [02]: MCFG  A M I len=60
1:175  0:000   - [03]: HPET  A M I len=56
1:175  0:000   - [04]: SSDT  SataTabl len=877
1:175  0:000   - [05]: SSDT  Cpu0Ist len=2408
1:175  0:000   - [06]: SSDT  CpuPm len=2706
1:175  0:000   - [07]: BGRT  A M I len=56
1:175  0:000  Calibrated TSC Frequency = 2986994163 = 2986MHz
 
My vbios is not a UEFI, right? My video card have the first version of bios and on the Gigabyte´s site exists 3 newer versions. Is it possible update vbios on Mac Sierra? and with this update is possible to get UEFI for this card?

 

Slice, see this please:

 

1:175  0:000  === [ GetAcpiTablesList ] =================================

1:175  0:000  Get Acpi Tables List from RSDT:
1:175  0:000   - [00]: FACP  A M I len=132
1:175  0:000   - [01]: APIC  A M I len=114
1:175  0:000   - [02]: MCFG  A M I len=60
1:175  0:000   - [03]: HPET  A M I len=56
1:175  0:000   - [04]: SSDT  SataTabl len=877
1:175  0:000   - [05]: SSDT  Cpu0Ist len=2408
1:175  0:000   - [06]: SSDT  CpuPm len=2706
1:175  0:000   - [07]: BGRT  A M I len=56
1:175  0:000  Calibrated TSC Frequency = 2986994163 = 2986MHz
 
My vbios is not a UEFI, right? My video card have the first version of bios and on the Gigabyte´s site exists 3 newer versions. Is it possible update vbios on Mac Sierra? and with this update is possible to get UEFI for this card?

 

May be. 

     Asus EAH6450 Video BIOS UEFI GOP Upgrade (And GOP UEFI binary in .efi for many ATI cards)    

But what did you expected to have? 

I propose nothing.

  • Like 1

Maaan, that's like rocket science for most of the users. :)) It's good that you CAN do that, in case you can't get your hands on one already made from the manufacturer. But man, I don't know, I wouldn't go into that on my own. :)) Also, is this only for ATI/Radeon cards?

Just use GOPupd: http://www.win-raid.com/t892f16-AMD-and-Nvidia-GOP-update-No-requests-DIY.html

I've used it on many GPUs, never had problems with it.

 

Slice, see this please:

 

1:175  0:000  === [ GetAcpiTablesList ] =================================

1:175  0:000  Get Acpi Tables List from RSDT:
1:175  0:000   - [00]: FACP  A M I len=132
1:175  0:000   - [01]: APIC  A M I len=114
1:175  0:000   - [02]: MCFG  A M I len=60
1:175  0:000   - [03]: HPET  A M I len=56
1:175  0:000   - [04]: SSDT  SataTabl len=877
1:175  0:000   - [05]: SSDT  Cpu0Ist len=2408
1:175  0:000   - [06]: SSDT  CpuPm len=2706
1:175  0:000   - [07]: BGRT  A M I len=56
1:175  0:000  Calibrated TSC Frequency = 2986994163 = 2986MHz
 
My vbios is not a UEFI, right? My video card have the first version of bios and on the Gigabyte´s site exists 3 newer versions. Is it possible update vbios on Mac Sierra? and with this update is possible to get UEFI for this card?

 

The VFCT ACPI table is only found when the AMD GOP driver is loaded. NVIDIA GPUs do not create such an ACPI table.

  • Like 2

Just use GOPupd: http://www.win-raid.com/t892f16-AMD-and-Nvidia-GOP-update-No-requests-DIY.html

I've used it on many GPUs, never had problems with it.

The VFCT ACPI table is only found when the AMD GOP driver is loaded. NVIDIA GPUs do not create such an ACPI table.

Oh TheRacerMaster! Thats the point! Im searching for UEFI for my GTX 750 Ti. What I need to do?

The link is broken. Thanks.

Thanks Slice, but is for my GTX 750 Ti. What im looking for is to boot with boot rom priority = efi rom.

@Wppley2 Better contact your video card vendor and ask him for UEFI upgrade for your card. That's what I did in order to upgrade mine EVGA GTX 650 SC.

Hey Philip Petev! Thank you for the response! I'm reading in Win Raid and discover one bug of my mobo bios with PCI Rom priority. Is a bug with various Asus mobos.

  • Like 1

Oh TheRacerMaster! Thats the point! Im searching for UEFI for my GTX 750 Ti. What I need to do?

The link is broken. Thanks.

Thanks Slice, but is for my GTX 750 Ti. What im looking for is to boot with boot rom priority = efi rom.

Hmm, seems like some referral check? Just search for GOPupd on Win-Raid.

  • Like 1

Hi

 

I want to try different config.plist on my hack under EFI/Clover with same kexts. For example, config-1.plist with Imac13,2 SMBIOS and config-2.plist for macpro6,1 SMBIOS. When I select config-2.plist in Clover/Options, I've kernel panic and empty boot args.

 

However, config-2.plist is fully functional on my external drive

 

Any ideas?

Hi

 

I want to try different config.plist on my hack under EFI/Clover with same kexts. For example, config-1.plist with Imac13,2 SMBIOS and config-2.plist for macpro6,1 SMBIOS. When I select config-2.plist in Clover/Options, I've kernel panic and empty boot args.

 

However, config-2.plist is fully functional on my external drive

 

Any ideas?

Set Boot->Debug=YES and catch the moment of panic.

  • Like 1

is there a possibility to have "Save clover options as default" from GUI? like when changing bios features but for clover GUI. so we can make permanent changes from Clover boot GUI. it already saves other tables and dumps.

Not new question again. This was discussed several years.

This is very hard to do because config.plist is not complete set of settings. CloverConfigurator is wrong because it forced users to make full config. No, don't do this!

In most cases config must be very reduced. Clover will calculate most values depending on current hardware state.

And then there is a problem for Clover programmers where to catch all settings.

They came from config.plist.

User can change the config and then values will be changed.

User can enter GUI and change setting here.

Some settings will be calculated, some recalculated.

Some setting are stored in gSetting, some in GlobalConfig, some in internal arrays (patches for example), some in nvram.plist which will be updated next time.

This inconvenience appears because of history of Clover development. As is.

 

Did you know an appointment of utility clover-genconfig? 

When you can't boot you enter GUI and change something. After this change you are trying to boot and after some attempts the victory!

You enter the system! At this point you may start clover-genconfig and got almost all setting that you changed last time booting.

You can copy them into your config.plist finally.

@Slice

 

Screen catches attached : below

 

I don't understand: config-2.plist work alone on USB disk and don't work on HDD. How to use Clover/options/Config?

 

Thanks

Looks like you missed something. Take into account that Kernel and Kext patches will not replaced in config.plist changes.

  • Like 2

Screen catches attached : below

 

I don't understand: config-2.plist work alone on USB disk and don't work on HDD. How to use Clover/options/Config?

 

Thanks

The same thing happened to me you I edited my BIOS and enabled all the CPU power management configurations.

  • Like 1

You can use Darwin Dumper to extract the EDID. One of the best tools I've ever used.

 

For as far as I know, Clover already detects and injects EDID by default. I could be wrong though...

 

But anyway, you do have the option to use your own, if you so desire. And Darwin Dumper is, in my opinion, the easiest way to get it on MacOS.

 

By the way, if the card in your signature is the one you want to use for this case, there might be another way to do it:

 

1. UEFI GOP VBIOS (if you don't already have it). Basically the video card's ROM (you can request it on manufacturer's forums, usually). You can check if you already have a "UEFI" ROM using GPU-Z on Windows (I'm not aware of a Mac tool that can do that, but there probably are).

2. Disable Windows CSM (Compatibility Support Module) in BIOS. You don't need it, unless you're planning on putting XP on that machine. Which... I don't know why would anyone want to do, but yeah, for newer versions of Windows, you certainly don't need it.

 

That should bring you full native resolution in preboot.

That's a great tip. I never thought of using Darwin Dumper for that. It did pull up the same EDID I got using other tools, and in fact, whether I choose to inject custom EDID or not, Clover does find the same EDID.

 

But, using Monitor Asset Manager in Windows, I get the same basic EDID but there is more code afterward:

 

From both Darwin Dumper and letting Clover inject:

 

00,FF,FF,FF,FF,FF,FF,00,10,AC,67,D0,53,33,30,30,

05,1A,01,03,80,3C,22,78,EE,44,55,A9,55,4D,9D,26,

0F,50,54,A5,4B,00,B3,00,D1,00,71,4F,A9,40,81,80,

77,80,01,01,01,01,56,5E,00,A0,A0,A0,29,50,30,20,

35,00,55,50,21,00,00,1A,00,00,00,FF,00,48,37,59,

43,43,36,32,33,30,30,33,53,0A,00,00,00,FC,00,44,

45,4C,4C,20,55,32,37,31,35,48,0A,20,00,00,00,FD,

00,38,56,1E,71,1E,00,0A,20,20,20,20,20,20,01,23,

 

Additional lines using MAM:

02,03,22,F1,4F,10,05,04,03,02,07,16,01,14,1F,12,

13,20,21,22,23,09,07,07,83,01,00,00,65,03,0C,00,

10,00,02,3A,80,18,71,38,2D,40,58,2C,25,00,55,50,21,00,00,1E,01,1D,80,18,71,1C,16,20,58,2C,25,00,

55,50,21,00,00,9E,01,1D,00,72,51,D0,1E,20,6E,28,55,00,55,50,21,00,00,1E,8C,0A,D0,8A,20,E0,2D,10,

10,3E,96,00,55,50,21,00,00,18,48,3F,00,CA,80,80,30,40,1A,50,13,00,55,50,21,00,00,1E,00,00,00,94

 

BUT regardless of which I use, I still never get 1920x1080 resolution. (I wouldn’t even dream for 2560x1440!)

 

My mobo is legacy and no UEFI, therefore has no switch for CSM. What I understated, and I may be wrong, is that he EVGA NVIDIA 750ti is UEFI compatible though. Not sure how this helps.

I have the BIOS for my card that I download from TechPowerUp. I have tried renaming it and putting it in the ROM folder but that does nor work either.

Hi everyone,

 

I am having "scan entries" error on clover, due to a raid 0 error.

 

If I disable devices, it boots normally.

 

After a research, I saw several people disabling scanning and enabling root device individually, but I am not being able to do that.

 

Here is my conf.plist:

<key>GUI</key>
	<dict>
		<key>Scan</key>
		<dict>
			<key>Entries</key>
			<false/>
			<key>Legacy</key>
			<false/>
			<key>Tool</key>
			<false/>
		</dict>
		<key>Custom</key>
		<dict>
			<key>Entries</key>
				<dict>
					<key>AddArguments</key>
					<string>root=UUID=A551A28D-2647-3720-B6C1-A0F8F581654C</string>
					<key>Disabled</key>
					<false/>
					<key>FullTitle</key>
					<string>El Macintosh HD</string>
					<key>Hidden</key>
					<false/>
					<key>Ignore</key>
					<false/>
					<key>NoCaches</key>
					<false/>
					<key>Type</key>
					<string>OSX</string>
					<key>Volume</key>
					<string>El Macintosh HD</string>
					<key>VolumeType</key>
					<string>Internal</string>
		</dict>
etc....

I added my boot device with custom entries, but if I plug in my raid he keeps trying to read it and I get stuck on "scan entries" again, even thou I disable it on Scan > Entries.

 

How do I disable all readings from hard discs, so I boot on my os with raid plugged in?

 

Thanks in advance!!

 

 

Edit: The situation just got weirder. I disabled the cache from custom entry and now I can't see any device, but if I put the raid 0 in it does try to read it and I still get stuck. How is this possible??? I disabled everything from scan, I can't even see my boot device, even thou I manually entered it, and clover still tries to read the raid 0.

This is something I have never seen before installing Sierra 10.12.5 or 10.12.6 or even possibly from the newest versions of Clover 41xx. Any suggestions on what to remove or add in clover to clear this ACPI AE Error, seems to be CPU related?

 

I have seen this on older systems and newer ones in my signature so its not singled out to any one piece of hardware.

 

Everything still seems to work correctly CPU/GPU PM sleep/wake/shutdown etc.

post-135888-0-61503400-1501110660_thumb.jpg

That's a great tip. I never thought of using Darwin Dumper for that. It did pull up the same EDID I got using other tools, and in fact, whether I choose to inject custom EDID or not, Clover does find the same EDID.

 

But, using Monitor Asset Manager in Windows, I get the same basic EDID but there is more code afterward:

 

From both Darwin Dumper and letting Clover inject:

 

00,FF,FF,FF,FF,FF,FF,00,10,AC,67,D0,53,33,30,30,

05,1A,01,03,80,3C,22,78,EE,44,55,A9,55,4D,9D,26,

0F,50,54,A5,4B,00,B3,00,D1,00,71,4F,A9,40,81,80,

77,80,01,01,01,01,56,5E,00,A0,A0,A0,29,50,30,20,

35,00,55,50,21,00,00,1A,00,00,00,FF,00,48,37,59,

43,43,36,32,33,30,30,33,53,0A,00,00,00,FC,00,44,

45,4C,4C,20,55,32,37,31,35,48,0A,20,00,00,00,FD,

00,38,56,1E,71,1E,00,0A,20,20,20,20,20,20,01,23,

 

Additional lines using MAM:

02,03,22,F1,4F,10,05,04,03,02,07,16,01,14,1F,12,

13,20,21,22,23,09,07,07,83,01,00,00,65,03,0C,00,

10,00,02,3A,80,18,71,38,2D,40,58,2C,25,00,55,50,21,00,00,1E,01,1D,80,18,71,1C,16,20,58,2C,25,00,

55,50,21,00,00,9E,01,1D,00,72,51,D0,1E,20,6E,28,55,00,55,50,21,00,00,1E,8C,0A,D0,8A,20,E0,2D,10,

10,3E,96,00,55,50,21,00,00,18,48,3F,00,CA,80,80,30,40,1A,50,13,00,55,50,21,00,00,1E,00,00,00,94

 

BUT regardless of which I use, I still never get 1920x1080 resolution. (I wouldn’t even dream for 2560x1440!)

 

My mobo is legacy and no UEFI, therefore has no switch for CSM. What I understated, and I may be wrong, is that he EVGA NVIDIA 750ti is UEFI compatible though. Not sure how this helps.

I have the BIOS for my card that I download from TechPowerUp. I have tried renaming it and putting it in the ROM folder but that does nor work either.

 

The issue might be exactly the motherboard you're using here... I could be wrong though.

 

Anyway, this is what it looks like when you don't have a UEFI VBIOS installed on your GPU.

 

post-1303722-0-18776300-1501236784_thumb.gif

 

And this when you do.

 

post-1303722-0-22217500-1501236781_thumb.png

 

I don't know what the ROM folder is for....never used it, but I'm not sure it's for that... Again, I could be wrong.

 

My suggestions are:

 

1. check if your video card already has a UEFI BIOS installed. The fact that is compatible doesn't mean it's already installed.

2. maybe upgrade your motherboard...? You could find UEFI boards for very cheap nowadays. I'm not saying buy the cheapest one. I'm just saying it's worth investing in a new motherboard.

 

By the way, I also have a 2K monitor and I do have native resolution (2560x1440) in preboot. So...it's up to you. :)

Hi arsradu! There are some app to get this info into macOS?

 

For NVIDIA cards, I'm not sure... I don't think there is any.

 

A few pages back, Slice mentioned something about a specific identifier for ATI cards. And how, based on that information, you can determine if your card has a UEFI VBIOS or not... Now, in our cases, this does not help, since we have Nvidia cards. So no, I don't know another way.

 

By the way, I've got a question for everyone here (it might be only in the latest release of Clover, didn't pay attention to it before, it might be an older change that caused this), but was this always a thing for Clover to make a zip of CLOVERX64.efi inside the CLOVER folder? :))

 

Just curious. Doesn't seem to affect the functionality in anyway. And the update from 4114 to 4128 went without any issues (I'm on r4128 now). Just seemed a bit strange. And I was wondering whether or not it's intended. And if it is, what's the reason for this archive.

 

post-1303722-0-52473400-1501250568_thumb.png

×
×
  • Create New...