Clover General discussion

[Funky frank]

So this maybe could be related to the "new" real efi variables thanks to new aptiofix and a limitation of the displayed clover boot entries?

 

The macos updater seems to add new efi boot entries. I also now have a weird one (targeting a physical hdd) named "boot OSX2 thru OSXSSD" (osx2 is another drive with old sierra, and OSXSSD is my real ssd boot drive). The entry is targeting OSXSSD. 

 

Before I could scroll the clover entries to the left, at least I could then select non visible ones.

 

Did you remove that?

Eh guys, I think clover aptiofix and the high sierra installer seriously {censored}ed up my mainboard efi. I cannot change any settings anymore, it will freeze if I try to save change settings. Also macos seems to write lot of stuff into the efi, like new boot entries...   Or is it clover?  How can I remove any EFI component installed to my mainboard bios?

[bronxteck]

I guess follow normal protocol and physically remove as much hardware as you can from the motherboard and see if it still occurs. also test your ram.

[Funky frank]

The bios can reboot now again, I think i was related to EFI boot entries added by clover? or high sierra installer?.  nevertheless still cannot boot from my 1:1 sierra backup, it is a usb3 drive. Why?   clover is loaded from my main drive, but the backup drive is not listed.  

 

What could be the cause for this?

 

In what positions/paths does clover look for a boot file?

[Funky frank]

Oh c'mon guys, clover does not support the High Sierra Updater anymore!

 

After I run it (without apfs), the boot entry of the drive completely disappears in clover. Also no "continue installation entry" or whatever. I do not block any kind of entries, except windows.

 

Can you please fix this?

 

There is a "macOS Install Data" dir on the drive. I linked a shot above.

 

Here is my clover config:

config.plist.zip

[chris1111]

Clover Update macOS works here no issue

[Funky frank]

Ok, I think this is the problem:

 

I boot from my main ssd still after running the updater. If I boot directly from the drive on which I run the updater, clover then will show the installer boot entries. So my feature request to you is:

 

Please make clover capable of showing installer entries from other drives, too.

[Sherlocks]

Aaaaand a third one: I tried to update to High Sierra on my backup drive, it restarted and now there is no boot entry for my backup drive anymore.... Why? Clover is 4392. Update?

 

This is what was added to root dir:

Bildschirmfoto 2018-02-27 um 18.02.48.PNG

 

The kernel in /System/Library/Kernels still is there. So why there is no entry in clover anymore? It was there before I run high Sierra installer (without APFS conversion).

Upload ia.log

 

나의 LG-F800S 의 Tapatalk에서 보냄

[LockDown]

Will this give me the same result?

			<key>Fixes</key>
			<dict>
				<key>FixRegions_10000000</key>
				<true/>
			</dict>

and

			<key>Fixes</key>
			<dict>
				<key>FixHeaders</key>
				<true/>
			</dict>

[levifig]

Using Clover Configurator and trying to disable EFILoginHiDPI by setting it to 0. nvram -p tells me it's set to %00%00%00%00 but I'm still getting the "retina" login screen…

[Kynyo]

At clover boot menu use F11 to reset nvram.

[Funky frank]

Cloud the clover team add all these F-keys functionality into a menu, too?

[Matgen84]

Cloud the clover team add all these F-keys functionality into a menu, too?

Just type F1 and you have F-Keys list 

[Rodion2010]

Using Clover Configurator …

 

Don't do it

 

Will this give me the same result?

			<key>Fixes</key>
			<dict>
				<key>FixRegions_10000000</key>
				<true/>
			</dict>

and

			<key>Fixes</key>
			<dict>
				<key>FixHeaders</key>
				<true/>
			</dict>

No   Read the manual

[LockDown]

Don't do it

No   Read the manual

the 2nd code was taken from official clover package config_sample

[Rodion2010]

the 2nd code was taken from official clover package config_sample

sure. but Regions and Headers are not the same

1st patch is about floating memory addresses, 2nd about not-English symbols in headers

[LockDown]

sure. but Regions and Headers are not the same

1st patch is about floating memory addresses, 2nd about not-English symbols in headers

Oh im sorry. i meant:

			<key>Fixes</key>
			<dict>
				<key>FixRegions_10000000</key>
				<true/>
			</dict>

and

			<key>Fixes</key>
			<dict>
				<key>FixRegions</key>
				<true/>
			</dict> 

will this give me the same result?

[apianti]

Hey, just wanted to let you guys know that I'm just slow and behind on where I wanted to be with v3, I will get something out as soon as feasible. Also I'm having all sorts of trouble with the new color theme, it's very hard for me to read and so I may post less often...

[TheBloke]

Hi guys

Got a bug report:  ATI Connectors Data and ATI Connectors Patch will not accept enough digits to allow me to use the FB connector patch that I need.

EDIT: I realised I need to make a ticket as well, which is here.

Here are examples of the patch strings I want to use:

Data: 000400000403000000010001000000001204030100000000000400000403000000010001000000002205040200000000000400000403000000010001000000001102010300000000000400000403000000010001000000002103020400000000000400000403000000010001000000001000050500000000000400000403000000010001000000002001060600000000

Patch: 000200000402000000010001000000002205050200000000040000001402000000010001000000001000060500000000000400000403000000010001000000001204030100000000000400000403000000010001000000001102010300000000000400000403000000010001000000002103020400000000000400000403000000010001000000002001040600000000

Here's what happens:

1. If I try to copy these into ATI Connectors Data or ATI Connectors Patch in Clover Configurator, it changes it to '0'
2. If I manually edit them into config.plist, Configurator says: "Please fix the following code before saving: integer overflow in <integer> on line 162"
3. If I ignore this and boot with the config.plist, I get an exception and crash when Clover tries to load - printed in huge red text all over the screen

My guess is there's one or two issues here:

• In Sierra/High Sierra, many more digits were added to the required FB data (at least 16 extra digits, maybe more actually)
• I am trying to patch six connectors, which is more than most people.

EDIT: I just tested with a four-connector patch, and that is also not accepted.  So I guess maybe it is the extra digits added by Sierra.  Unless I'm doing something wrong here?

Thanks

Edited March 14, 2018 by TheBloke

[LockDown]

Hi

i have  .nvram.plist (a hidden .nvram.plist WITH a DOT in the beginning). Where did this came from?

Edited March 14, 2018 by ellaosx

[Maniac10]

The dot at the beginning of a file name is a trick that "flags" it as hidden. It was most likely created by Clover's shutdown scripts. Open Console.app and locate /Library/Logs/CloverEFI/rc.shutdown.log for more information.

[apianti]

6 hours ago, TheBloke said:

Hi guys

Got a bug report:  ATI Connectors Data and ATI Connectors Patch will not accept enough digits to allow me to use the FB connector patch that I need.

1. If I try to copy these into ATI Connectors Data or ATI Connectors Patch in Clover Configurator, it changes it to '0'
2. If I manually edit them into config.plist, Configurator says: "Please fix the following code before saving: integer overflow in <integer> on line 162

You used the <integer> tag:

<key>ATIConnectorsData</key>
<integer>000400000403000000010001000000001204030100000000000400000403000000010001000000002205040200000000000400000403000000010001000000001102010300000000000400000403000000010001000000002103020400000000000400000403000000010001000000001000050500000000000400000403000000010001000000002001060600000000</integer>
<key>ATIConnectorsPatch</key>
<integer>000200000402000000010001000000002205050200000000040000001402000000010001000000001000060500000000000400000403000000010001000000001204030100000000000400000403000000010001000000001102010300000000000400000403000000010001000000002103020400000000000400000403000000010001000000002001040600000000</integer>

but it requires the <string> tag:

<key>ATIConnectorsData</key>
<string>000400000403000000010001000000001204030100000000000400000403000000010001000000002205040200000000000400000403000000010001000000001102010300000000000400000403000000010001000000002103020400000000000400000403000000010001000000001000050500000000000400000403000000010001000000002001060600000000</string>
<key>ATIConnectorsPatch</key>
<string>000200000402000000010001000000002205050200000000040000001402000000010001000000001000060500000000000400000403000000010001000000001204030100000000000400000403000000010001000000001102010300000000000400000403000000010001000000002103020400000000000400000403000000010001000000002001040600000000</string>

I have made the same comments on your ticket and closed it.

[TheBloke]

2 hours ago, apianti said:

You used the <integer> tag:

<key>ATIConnectorsData</key>
<integer>000400000403000000010001000000001204030100000000000400000403000000010001000000002205040200000000000400000403000000010001000000001102010300000000000400000403000000010001000000002103020400000000000400000403000000010001000000001000050500000000000400000403000000010001000000002001060600000000</integer>
<key>ATIConnectorsPatch</key>
<integer>000200000402000000010001000000002205050200000000040000001402000000010001000000001000060500000000000400000403000000010001000000001204030100000000000400000403000000010001000000001102010300000000000400000403000000010001000000002103020400000000000400000403000000010001000000002001040600000000</integer>

but it requires the <string> tag:

<key>ATIConnectorsData</key>
<string>000400000403000000010001000000001204030100000000000400000403000000010001000000002205040200000000000400000403000000010001000000001102010300000000000400000403000000010001000000002103020400000000000400000403000000010001000000001000050500000000000400000403000000010001000000002001060600000000</string>
<key>ATIConnectorsPatch</key>
<string>000200000402000000010001000000002205050200000000040000001402000000010001000000001000060500000000000400000403000000010001000000001204030100000000000400000403000000010001000000001102010300000000000400000403000000010001000000002103020400000000000400000403000000010001000000002001040600000000</string>

 

OK thanks @apianti.  The bug is in Clover Configurator then, which always uses integer tags for this field.  I thought Configurator was made by the Clover team but I see now it is not.  I will report this separately to the creators of the Configurator.

[pkdesign]

On 2/21/2018 at 5:21 PM, TheBloke said:

Guys, I want to test the boot flag -nehalem_error_disable

In Clover Configurator, do I add that as typed above: -nehalem_error_disable

Or do I add it as: nehalem_error_disable ?

Looking at the default boot flags provided by Configurator, some are -flag and some are just flag, no - before it. I'd expect a flag to normally have a - so maybe this is just how Configurator is displaying some of them inconsistently.

I'm currently booted with -nehalem_error_disable added as follows:



My guess is that this is the correct way, but I wanted to ask to be sure, as I have no other way of confirming if the flag applied or not (I'm trying it on my X58 system as I've heard it's sometimes required/helpful on systems with SMBIOs 5.1.)

What is the purpose of -nehalem_error_disable?

All I have found is that it disables AppleTyMCEDriver. Is that correct and why would I want to do that?

How are you measuring/viweing your speedsteps?

Edited March 16, 2018 by pkdesign

[TheBloke]

4 hours ago, pkdesign said:

What is the purpose of -nehalem_error_disable?

All I have found is that it disables AppleTyMCEDriver. Is that correct and why would I want to do that?

I read a few (old) posts indicating that this might be necessary on X58 motherboards.  I know AppleTyMCEDriver is related to ECC memory.  The MacPro 5.1 system used X58 with ECC RAM, and I've read discussion of needing to patch AppleTyMCEDriver if you don't use ECC RAM (as I don't).

I've also read discussions of -nehalem_error_disable being needed sometimes, to prevent certain errors.  I can't remember which ones now, but maybe again related to ECC.

I don't think you need the flag.  I added it because I was getting strange crashes and errors post-boot, so I was looking for anything that might be wrong.  I've since resolved my errors/crashes (a bad DIMM), so it wasn't anything to do with adding that flag that fixed it. 

So as far as I can tell, adding -nehalem_error_disable has made zero difference to my system (positive or negative).  In fact I am not even using the flag any more - I removed it a week or so ago when I was adding another flag, and nothing is different that I can see.

Maybe whatever problem the flag solved is no longer an issue in High Sierra.  Or maybe it's something that Clover now fixes automatically.  Or maybe it was never needed at all and was just misinformation.    I wouldn't bother about it at all, unless you have errors related to ECC, which I doubt you do.

Quote

How are you measuring/viweing your speedsteps?

HWMonitor, as bundled with RehabMan's version of kozlek's FakeSMC.

 

EDIT: Another way to see them is iStat Menus (although the info is slightly odd, in that the listed frequencies don't match the listed multipliers on a core-by-core basis, and, at least for me, one of the cores is called 'Core 18'. But the listed multipliers do generally match what HWMonitor is showing):

Spoiler

 

Edited March 16, 2018 by TheBloke

[cecekpawon]

On 3/14/2018 at 1:31 PM, TheBloke said:

OK thanks @apianti.  The bug is in Clover Configurator then, which always uses integer tags for this field.  I thought Configurator was made by the Clover team but I see now it is not.  I will report this separately to the creators of the Configurator.

Seems fixed on 4.60.3.4