Jump to content
231 posts in this topic

Recommended Posts

43 minutes ago, Hervé said:

Confirmed. No need to replace boot.efi with 10.15.3's. 

  • Like 1
16 hours ago, Hervé said:

@Donw35, please follow the links I posted!

 

Variable works for Clover too; I tested it successfully. You just need to ensure NVRAM works properly (install EMUVariableUEFI.efi module + RC scripts on Catalina boot volume if NVRAM does not work natively as is often the case on old C2D/C2Q platforms such as my Vostro200).

 

1) I reverted to 10.15.4's boot.efi

2) I set the variable in NVRAM with the following Terminal command:


sudo nvram wake-failure=%00%00%00%00%00

3) I rebooted so that the variable would be fully taken into account (and, of course, experienced a last CMOS reset)

 

Afterwards, no more CMOS reset when rebooting from 10.15.4! :thumbsup_anim:

 

 

how about CMOSResetFix(just example name) option in config? just true or false

if check it, always keep wake-failure in nvram.

Edited by Sherlocks
  • Like 1
17 hours ago, Hervé said:

@Donw35, please follow the links I posted!

 

Variable works for Clover too; I tested it successfully. You just need to ensure NVRAM works properly (install EMUVariableUEFI.efi module + RC scripts on Catalina boot volume if NVRAM does not work natively as is often the case on old C2D/C2Q platforms such as my Vostro200).

 

1) I reverted to 10.15.4's boot.efi

2) I set the variable in NVRAM with the following Terminal command:


sudo nvram wake-failure=%00%00%00%00%00

3) I rebooted so that the variable would be fully taken into account (and, of course, experienced a last CMOS reset)

 

Afterwards, no more CMOS reset when rebooting from 10.15.4! :thumbsup_anim:

 

Thanks for such a great finding which fixed CMOS reset issue in both Clover and OpenCore bootloaders now !

sudo nvram wake-failure=%00%00%00%00%00

works on my HackPro5,1 running Catalina 10.15.4 with the 10.15.4 boot.efi.

 

 

Nice work everyone.

 

I am running Clover (Legacy) r5112 with the following Clover BIOS drivers:

  • ApfsDriverLoader.efi
  • FSInject.efi
Edited by tonyx86
  • Like 1
46 minutes ago, valam said:

How to download boot.efi.zip 10.15.3?
link does not work

https://support.apple.com/kb/DL2029?locale=en_GB

https://support.apple.com/kb/DL2030?locale=en_GB

boot.efi 10.15.3.zip

Edited by Rocky12
  • Like 1

Has anyone had such a thing.
Maybe someone knows how to solve the problem?

 

There are no errors in the 10.14.6 and 10.15.3 systems.
So why do I have this problem in 10.15.4.

 

What do you think about it?


Certainly there is a further error:

00:000 00:000 AAPL: [EB|#LOG:INIT] 2020-04-24T21:41:32
00:002 00:002 AAPL: [EB|#VERSION] boot.efi 422.100.16~12 (Official), built 2020-02-29T00:57:17-0800
.........

Edited by topolino1
1 hour ago, pointlessone said:

 

I had the same issue with OC 0.5.7 when I followed Desktop Guide. Switching RebuildAppleMemoryMap off helped me get past this.

 

@pointlessone you are great. thank you.

 

After the change, the first start was ok.
Now I have it again. What to do with this?

Edited by topolino1
4 hours ago, Hervé said:

In case this eluded you, this info is new data displayed when booting in in verbose mode; everybody gets this displayed; it comes from 10.15.4's new boot.efi; it's not indicative of a problem at all and does not in any way prevent 10.15.4 to boot and operate.

 

Or are you getting stuck at the end of that screen? Because it's all but clear...

Hi @Hervé.

Why does the computer stop displaying this information?

 

So you think that this entry is correct and do not worry about anything?

 

Thank you for your help and your time.

 

6 hours ago, Matgen84 said:

 

Do you stuck at EXITBS:START? :(

Such a problem pops up. The computer starts up.
It seems to me that there should be no such information.
With the 10.15.3 system, I didn't have this information.

 

Do you know how to solve it? What is this about?

38 minutes ago, topolino1 said:

Such a problem pops up. The computer starts up.
It seems to me that there should be no such information.
With the 10.15.3 system, I didn't have this information.

 

Do you know how to solve it? What is this about?

 

I have exactly the same thing, but I boot normally on Catalina. These lines don't come from macOS: VirtualSMC, OpenRuntime, OpenCore ... I don't know. I have no solution.

Edited by Matgen84
4 hours ago, Matgen84 said:

 

I have exactly the same thing, but I boot normally on Catalina. These lines don't come from macOS: VirtualSMC, OpenRuntime, OpenCore ... I don't know. I have no solution.

 

I think this is Catalina's reaction to wrong Bios or OC settings.
You have disabled in the bios:
AppleCpuPmCfgLock?
AppleXcpmCfgLock?

 

I have already tested almost everything. I give up:(

 

What is your version of the system?

×
×
  • Create New...