Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

I see a noticeable delay loading Clover which happens before InitScreen

 

I have narrowed it down as far as BdsLibConnectAllDriversToAllControllers() called on line #1543 in main.cpp. 

 

I added the following DBG prints before and after the call

DBG("**Calling BdsLibConnectAllDriversToAllControllers()\n");
    BdsLibConnectAllDriversToAllControllers();
DBG("**Return from BdsLibConnectAllDriversToAllControllers()\n");

This shows.

0:333  0:000   VideoBiosLock: Success
0:333  0:000  **Calling BdsLibConnectAllDriversToAllControllers()
0:344  0:010  CsmVideoDriverBindingStart
0:344  0:000  mixed support=40010
0:344  0:000  Controller is [030000]
0:344  0:000  Check for VBE
0:373  0:028   found Detail Timing 1920x1080
0:376  0:002    0 1920x1080 attr=BB - ok, edid+, working, highest, pref=0
0:378  0:002    1 1152x864 attr=BB - ok, edid+, working
0:378  0:000    2 1280x960 attr=BB - ok, edid+, working
0:378  0:000    3 640x480 attr=BB - ok, edid+, 640x480, working
0:378  0:000    4 800x600 attr=BB - ok, edid+, 800x600, working
0:378  0:000    5 1024x768 attr=BB - ok, edid+, 1024x768, working
0:379  0:000    6 1280x1024 attr=BB - ok, edid+, working
0:379  0:000    7 1400x1050 attr=BB - ok, edid-
0:382  0:003  CsmVideo: New mode: 0 1920x1080 - set
0:491  0:108   - SetMode pref 0 (0) = Success
0:491  0:000  CsmVideoCheckForVbe - Success
0:491  0:000  CsmVideoDriverBindingStart end Success
0:491  0:000  CsmVideo: New mode: 4 800x600 - blocking that switch
0:492  0:000  CsmVideo: New mode: 1 1152x864 - blocking that switch
6:605  6:113  **Return from BdsLibConnectAllDriversToAllControllers()
6:605  0:000  LoadDrivers() end
6:605  0:000  === [ InitScreen ] ==============================
6:605  0:000  Console modes reported: 3, available modes:

Has to be something with connecting the video.

Edited by blackosx
Link to comment
Share on other sites

3 hours ago, ellaosx said:

Hi @Slice

what proof can i show you. booting in single mode then do bdmesg will do?

I dont have my Legacy computer at this point, but will be sending logs once im home.

 

To add:

i only have 1 drive for both OS (2 partitions with mavericks & sierra).

I was using 5115 ang both OS worked.

But when i updated clover to 5119, sierra still boots fine, but not mavericks.

Then i saw in verbose that it is not loading 10.9 & Other folder. Reverting back to 5115, maverick works fine

 

Boot->Debug=YES and show debug.log including a failed attempt to boot Mavericks.

Anyway I know Clover boots Mavericks.

 

@blackosx

I know it is related to video but I see no way to speedup the process.

Link to comment
Share on other sites

Thanks @Slice But I can’t be sure 100% sure it’s the video. I’ll try to explore BdsConnect.c a bit more to see if I can get some understanding of what’s happening.

 

EDIT: 

I found Clover Ticket #565 regarding the same problem and as found by the OP, it's down to AudioDxe-64.efi. Without it I now see.

0:733  0:241  **Return from BdsLibConnectAllDriversToAllControllers()
0:733  0:000  LoadDrivers() end
0:733  0:000  === [ InitScreen ] ==============================

:)

 

 

@ellaosx I’ve just booted 10.8.5 with Clover r5119 without issue.

Edited by blackosx
Link to comment
Share on other sites

On 6/18/2020 at 12:32 AM, Slice said:

Boot->Debug=YES and show debug.log including a failed attempt to boot Mavericks.

Anyway I know Clover boots Mavericks.

 

Hi @Slice

 

1. r5115 can boot successfully .

2. r5119 can only boot successfully if i arg it with -f. (without -f , kext wont load in /E/C/K/10.9 & /E/C/K/10.9/Other)

 

The issue started in r5116 using my Legacy Computer found on my signature.

 

Attached is the log of success & failed.

ellaosx_log.zip

 

Edited by ellaosx
Link to comment
Share on other sites

37 minutes ago, Slice said:

Why there are different nvram.plist in these cases?

What do you mean by "Clover 5115" and "Clover 5119"? Different USB sticks with different files?

different nvram because i tried clearing if it was nvram issue, but its not.

Its the same internal hd. I only replace CLOVERX64.efi to test r5115 ànd r5119

Link to comment
Share on other sites

3 hours ago, Slice said:

May be you attempted to start by press SPACE? It was possible with 5115 and prohibited later.

Only ENTER key is allowed.

I have tried:

1.pressing space.

2. pressing enter

3. timeout -1

4. Timeout 0

All the same issue with mavericks. Sierra+ are ok.

 

I have also tried installing mavericks on my C2Duo which is not on my signature, but also failed with the same issue.

This is really weird. Installing/upgrading clover is really a no brainer :(

 

Edited by ellaosx
Link to comment
Share on other sites

2 hours ago, ellaosx said:

How can i go back to a specific revision using buildme?

you can't with buildme, but you can use the terminal:

cd ~/CloverBootLoader (or cd ~/src/Clover) 
git reset --hard a4ac6daf971486b245211410cb5aaa7925a3c2a5

the above sha1 commit is the released 5117 taken from the release page...

 

P.S. I can confirm Mavericks doesn't want to boot. 

  • Thanks 1
Link to comment
Share on other sites

Hi all.

I'm finally over my the project that ate all my time (wasn't a computer one).

 

Before I resume my "Clover string cleaning task" :), I was wondering what happened to the clover website that was explaining the configuration ?

I remember a domain like clover-zetam something. I'm wondering if someone still has the page sources and if we can still bring that back online on the GitHub page system. It's free, pages are BB syntax and can be community maintained.

 

Anyone know something about that ?

 

Edited by Jief_Machak
Link to comment
Share on other sites

Gosh, that was abandoned long ago. The last I saw it was https://sourceforge.net/p/cloverefiboot/wiki/Home/   that was the "official' docs. But I am pretty sure that has been abandoned as well. Hell, it links to the wrong place to download the installer!

 

Hopefully this will get beefed up and made very clear. I think one reason people are so (overly) excited about OpenCore is because it ii SO well documented, including everything that is new an updated in each release.

Edited by pkdesign
Link to comment
Share on other sites

Yes, true, the sourceforge page you gave looks like what I remember.

I always feel that a lot of people lose a lot of time figuring out problems already solved by others, but the solution is buried in a forum thread.

 

I didn't try OpenCore yet, but I heard quite a lot about it. Why the OpenCore developers prefered to restart a new project instead of participating in Clover ? Is it better now ? Does OpenCore already do everything that Clover does ? Should we really keep 2 projects that try to do the same, which divide strength ?

Link to comment
Share on other sites

It seems all the energy is around OC. Nearly all the posts on Reddit are people creating their first hack using it. I almost never see Clover being their first.

 

I've read and read, and no one can definitively explain to me why its better. People claim faster boot times. But seriously, a few seconds...maybe. Then there is the claim that is is upgrade-proof. I personally haven't had a issue updating the OS in years.

 

Clover has been around for 10+ years and has a huge community supporting it. I have tried OC and I don’t see much difference. I am also a big fan of themes, something that OC people hate or deal with a pretty sad excuse of a theme manager (OpenCanopy).

 

I am also not clear of OC interactions with dual booting Windows. Are kext injected or not? I suppose if you are creating only a hack and are happy with that then maybe OC is better? Who knows.

 

Time will tell. I think very clear guides like the Dortania guide for OpenCore would do wonders for Clover.

Link to comment
Share on other sites

Anyway, can we have a Tool like << Load *.efi from FileSystem >> on Clover's GUI?

Me usually with Legacy press Exit (U) then it'll bring me to VBox look alike Firmware and I found this function under "Boot & Maintainance". How if make it bit simpler? Thanks.

Link to comment
Share on other sites

@pkdesign Thanks for the answer.

 

6 hours ago, pkdesign said:

clear guides like the Dortania guide

Having way better documentation is what I have in mind when I asked for the old Clover configuration website.

That's why we need to access to markdown page sources to port it to github.

I hope some people in the community would help with that, even if it's not the funnier part, because my time would be better employed in continuing cleaning the code.

Link to comment
Share on other sites

I think prelinkkernel as some change for BigSur

/System/Library/KernelCollections/BootKernelExtensions.kc.development
/System/Library/KernelCollections/BootKernelExtensions.kc

 

Look at the picture

photo_2020-06-23_09-58-23.thumb.jpg.7b5e4ac9da8f3798e38de51ef0fa11c9.jpg.81912ab3c9c28d72566ac2a13737e10f.jpg

  • Like 1
Link to comment
Share on other sites

1 hour ago, Matgen84 said:

Hi @Slice

 

I don't understand.

 

On a another thread, macOS Big sur is called 11.0 

But in your last commit, you prepare for 10.16.

 

 

1.png

10.16 for Intel

11.0 for ARM

Screenshot 2020-06-23 at 15.05.25.png

  • Thanks 1
Link to comment
Share on other sites

@slice - I had to roll back the last 2 commits to get back to commit "prepare for 10.16" - otherwise I don't get any kext injection on 10.15.5. logs look fine as compared to 5119 that works.  but no kexts are injected.

 

 

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...