Jump to content
30960 posts in this topic

Recommended Posts

@eng_redaesm

1 hour ago, eng_redaesm said:

both boots was unsuccessful,

Yes, you have to tell me because I thought the last commit wasn't working and the previous WAS working. So maybe the mistake is NOT in the last commit but a bit earlier.

Let's find out.

This : https://github.com/jief666/CloverCommits/blob/master/C-20210328085715-dc17de7.efi, should work. It's the same you confirmed working after you helped me find the problem with KernelPM and KPAppleIntelCPUPM.

If it's working, send me the log so I have a working base to compare to and find what have (wrongly) changed.

If it's working, try the next one here https://github.com/jief666/CloverCommits and tell me too.

and with this one : https://github.com/jief666/CloverCommits/blob/master/C-20210328183719-e143fe8.efi

Don't forget to verify in "About Clover" menu that you booted on the right efi. Just to be 100% sure. Because a mistake can send me on the wrong track and lose hours. Thanks.

3 hours ago, Jief_Machak said:

@eng_redaesm

Yes, you have to tell me because I thought the last commit wasn't working and the previous WAS working. So maybe the mistake is NOT in the last commit but a bit earlier.

Let's find out.

This : https://github.com/jief666/CloverCommits/blob/master/C-20210328085715-dc17de7.efi, should work. It's the same you confirmed working after you helped me find the problem with KernelPM and KPAppleIntelCPUPM.

If it's working, send me the log so I have a working base to compare to and find what have (wrongly) changed.

If it's working, try the next one here https://github.com/jief666/CloverCommits and tell me too.

sorry it is my wrong you are right one boot and the other no  here is the logs  

2021-3-29_20-48-21_BOOTX64.EFI.log 2021-3-29_20-53_BOOTX64.EFI.log

5 hours ago, Jief_Machak said:

I think I found it.

@eng_redaesm and @MifJpn Could you try CloverX64-2021-03-30-00-10-04-a5494a8-dirty-jief.zip ?

Have to go for now...

FYI, this build here -^ works for me too... 

commit 773f9bdaf works 

commit a5494a89f is broken

Edited by tluck
2 hours ago, Jief_Machak said:

 

@Jief_Machak Boot fine Preboot and Recovery Partition (Z390 Big Sur 11.3 Beta 5). Thanks

My stupid question: Is the debug.log created when starting the recovery partition ? I only have the starting one on the preboot

2021-3-30_6-10_CloverX64-2021-03-30-06-39-58-a5494a8-dirty-jief.efi.log

  • Like 2
22 minutes ago, kushwavez said:

Debug log must be always created (if you press F2 (if I remember correctly), or configure it from config.plist), even if you boot Windows for example or even if you don't boot anything.


I know that. :) With the same config.plist (debug=true), the debug log is generated automatically when starting the Preboot, not when starting  the recovery partition.

 

15 minutes ago, Jief_Machak said:

Yes, I'd say so.

 

Do you mean that I've to press F2 to generate debug.log when starting the recovery partition? Even with the config.plist configurated (debug=true).

Edited by Matgen84
16 minutes ago, Jief_Machak said:

No. I'll try to reproduce here. Will let you know.

 

New tests: 

  • This time, I start directly the Recovery partition, and the debug.log is generated :) I restart preboot and the debug.log is generated too
  • This time, I start directly the Preboot partition, and the debug.log is generated. I restart Recovery Partition and the debug.log is generated too
     

Strange ^_^ First test, I start preboot, and recovery partition after : only one debug.log 

×
×
  • Create New...