Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

apianti
apianti
Posted
Posted

Nah, you are mistaking the backup as an option to restore a broken or misconfigured installation without another boot mechanism. If you break booting clover you can only fix it by booting something else. There is no where else to really save backups, the ESP doesn't make sense because it may not have a reasonable amount of space for doing so. So, there are two options, and you always need a usb, either keep a working copy of clover (with the EFI shell) on a usb to use the EFI shell to restore or modify, or always test first on a usb. Also you can use a different operating system. Like I often mess up some code and clover will segfault or something, so I just boot directly into windows or linux from the firmware and fix it.

  • Like 1
Badruzeus
Badruzeus
Posted
Posted
4 minutes ago, apianti said:

Nah, you are mistaking the backup as an option to restore a broken or misconfigured installation without another boot mechanism. If you break booting clover you can only fix it by booting something else. There is no where else to really save backups, the ESP doesn't make sense because it may not have a reasonable amount of space for doing so. So, there are two options, and you always need a usb, either keep a working copy of clover (with the EFI shell) on a usb to use the EFI shell to restore or modify, or always test first on a usb. Also you can use a different operating system. Like I often mess up some code and clover will segfault or something, so I just boot directly into windows or linux from the firmware and fix it.

Thanks God, my AMI Aptio has `Launch EFI Shell from FS` option. Anyway, how to boot into *.iso that is placed on specific volume (if it' s possible)?

Andres ZeroCross
Andres ZeroCross
Posted
Posted
2 hours ago, arsradu said:

Hi guys,

 

Whoever thought of making an EFI backup on the target disk was an absolute genius! That was a brilliant idea.

 

Now, I'm thinking of the following scenario:

Let's say you updated to the latest version of Clover and...for some reason, you can't boot anymore. And you don't have a USB drive with another version of Clover.

You still have access to the Clover UI, but you don't have access to the drivers folder for example (maybe that would be another useful feature), assuming you know that's where the issue resides. But regardless, you know you have a working backup on your target disk. So you can attempt to restore one of the previous versions.

 

Unfortunately...there is no easy way to do that. Or maybe there is and I'm making a total fool of myself writing this. :)) I mean, I guess you could boot in single-user mode and try to copy the content of your backup folder over the current one. Now, one thing I don't know...is whether or not, when you do this, it replaces everything...or adds to the current content. Cause that might cause more issues than it solves... Also, I don't know how many people know how to do this from command line in the first place.

 

So, the idea here is: would it be possible to have a feature to restore a backup of Clover (from the target partition) using the Clover UI itself (assuming you can boot into the UI of course)?

 

I mean, I'm thinking something like this:

  1. scan the target disk for available backups
  2. display the results
  3. let the user choose the one he thinks might be the most reliable one
  4. load that one and replace the current installation with that new/old one.

 

It's just an idea, but also an open discussion. And I would love to know your opinion on it. :) 

 

Alternatively...can we maybe just allow the user to select a backup to boot only that specific time? He can fix his current EFI installation once he gets back into the OS, I guess. Something similar to what we have right now for loading a backup config (another really useful feature). Only in this case, we're not loading only the config from EFI/Clover/Config, but loading the entire folder from EFI-Backups.

 

Maybe I'm missing something here and this idea won't work. Or at least in its current form. Nonetheless, I'd love to know your opinion.

 

Thanks guys!

 

Aaand keep up the good work. :)


Just boot to windows, mount EFI partition and modify the EFI/CLOVER files

  • Like 1
arsradu
arsradu
Posted
Posted (edited)
40 minutes ago, apianti said:

Nah, you are mistaking the backup as an option to restore a broken or misconfigured installation without another boot mechanism. If you break booting clover you can only fix it by booting something else. There is no where else to really save backups, the ESP doesn't make sense because it may not have a reasonable amount of space for doing so. So, there are two options, and you always need a usb, either keep a working copy of clover (with the EFI shell) on a usb to use the EFI shell to restore or modify, or always test first on a usb. Also you can use a different operating system. Like I often mess up some code and clover will segfault or something, so I just boot directly into windows or linux from the firmware and fix it.

 

Yeah, well, in this case, that backup doesn't really help. Because, if you can boot from another OS, you can fix your main EFI this way. Same for booting from an USB drive. The idea was for that backup to help you boot (or restore those files back into the EFI partition so you can boot like that) in case there is no other way of getting back into the system.

 

Thing is, I had a very weird issue after installing Clover 4896. Not sure what happened there.... Probably something didn't get properly installed...or sources got messed up. Anyway, problem was I couldn't boot at all. And I didn't have an USB drive with Clover on it at the time... I had a USB drive, just not with Clover. So in the end I just put Clover on that USB from another machine, and was able to boot back into the OS.

 

But that also gave me this idea...of using those backups, since they're really useful, for cases like these where you might get stuck outside the OS, with no option to boot.

 

I guess I was wrong then. :) Thank you very much for your answer.

5 minutes ago, Andres ZeroCross said:


Just boot to windows, mount EFI partition and modify the EFI/CLOVER files

Yeah...I don't use Windows...anymore. :)) But that's definitely another way to fix this. And it's a good idea.

Edited by arsradu
Andres ZeroCross
Andres ZeroCross
Posted
Posted
4 minutes ago, arsradu said:

 

Yeah, well, in this case, that backup doesn't really help. Because, if you can boot from another OS, you can fix your main EFI this way. Same for booting from an USB drive. The idea was for that backup to help you boot (or restore those files back into the EFI partition so you can boot like that) in case there is no other way of getting back into the system.

 

Thing is, I had a very weird issue after installing Clover 4896. Not sure what happened there.... Probably something didn't get properly installed...or sources got messed up. Anyway, problem was I couldn't boot at all. And I didn't have an USB drive with Clover on it at the time... I had a USB drive, just not with Clover. So in the end I just put Clover on that USB from another machine, and was able to boot back into the OS.

 

But that also gave me this idea...of using those backups, since they're really useful, for cases like these where you might get stuck outside the OS, with no option to boot.

 

I guess I was wrong then. :) Thank you very much for your answer.

Yeah...I don't use Windows...anymore. :)) 


Then you can use Shell to copy folder clover to your internal HDD/SSD

  • Like 1
arsradu
arsradu
Posted
Posted
Just now, Andres ZeroCross said:


Then you can use Shell to copy folder clover to your internal HDD/SSD

 

That you can do. I was just thinking of a more..user friendly option, for people who are not very good at working with Shell. Something from Clover GUI itself. :) 

  • Like 1
Badruzeus
Badruzeus
Posted
Posted
26 minutes ago, arsradu said:

I was just thinking of a more..user friendly option, for people who are not very good at working with Shell. Something from Clover GUI itself. :) 

#IMHO That' s per-user depends, just like some users did partition backup b4 installing newer os then restoring it once error occurred.. but others didn't. I my self, usually > mv CLOVERX64.efi CLOVERX64.efi.bak b4 updating with newer rev.

 

56 minutes ago, arsradu said:

Thing is, I had a very weird issue after installing Clover 4896. Not sure what happened there.... Probably something didn't get properly installed...or sources got messed up. Anyway, problem was I couldn't boot at all.

Currently, no issue here. Booting normal, GUI loaded, kext_inject works as expected, entry scan does well, 10.11.6 / 10.14.x.

r4898-GCC.zip

  • Like 1
arsradu
arsradu
Posted
Posted (edited)
13 minutes ago, Badruzeus said:

#IMHO That' s per-user depends, just like some users did partition backup b4 installing newer os then restoring it once error occurred.. but others didn't. I my self, usually > mv CLOVERX64.efi CLOVERX64.efi.bak b4 updating with newer rev.

 

Currently, no issue here. Booting normal, GUI loaded, kext_inject works as expected, entry scan does well, 10.11.6 / 10.14.x.

r4898-GCC.zip

 

:) I should have also probably mentioned that I also built 4896 again, on a clean environment, and I didn't have any issue anymore. So...not sure what happened there. Now I'm on 4898, as well (thank you very much for sharing this build). Also with no issues. So I really don't know what happened there. I just wish there was a simple way to either revert to previous Clover, from Clover itself, ooor...restore from those backups that we make. After all, that's why they're called backups, right? So you can use them later on. If we can only use them from a booted OS....well, that's good and all, but, it's not gonna help you at all if you can't boot.

 

And using Shell is definitely an option. But...as I said before, not many people know how to use that. So...I thought having something accessible from Clover UI itself to help you fix such issues, might be a good thing.

Edited by arsradu
  • Like 1
Badruzeus
Badruzeus
Posted
Posted (edited)
28 minutes ago, arsradu said:

I just wish there was a simple way to either revert to previous Clover, from Clover itself, ooor...restore from those backups that we make. After all, that's why they're called backups, right? So you can use them later on. If we can only use them from a booted OS....well, that's good and all, but, it's not gonna help you at all if you can't boot.

What I got from Apianti brief explanations, it may be possible but consider about ESP size limitation for saving backup files.

Thing that I'm not sure just; although Clover has ability to Make a Current rev Backup.. how do we restoring it via Clover if it won't boot once updated, for example? Yeah, for me instead is by pressing StartUp Boot Key to Linux then rolling back. EFI Shell should did the job either (except error with config.plist and having non-functional "Shift" key when editing #LoL).

Edited by Badruzeus
arsradu
arsradu
Posted
Posted (edited)
31 minutes ago, Badruzeus said:

From what I got from Apianti brief explanations, it may be possible but consider about ESP size limitation for saving backup files.

Thing that I'm not sure just; even if Clover has ability to Make a Current rev Backup.. how do we restoring it via Clover if it won't boot once updated, for example? Yeah, for me is by pressing StartUp Boot Key to Linux then rolling back. EFI Shell should did the job either (except error with config.plist and having non-functional "Shift" key when editing #LoL).

 

Well, the backup is already there. :) In /Volumes/YourOSVolume/EFI-Backups. We don't need extra space on the actual EFI partition for that. We just need to get access to those backups from Clover GUI and use them either to boot into the OS, or to restore a selected backup onto the main EFI partition. That's all.

 

So, the thing is Clover already DOES make a revision backup of itself. Just not on the actual EFI partition. :) 

 

Now, the scenario goes like this: you can't boot into the OS (after selecting your drive), but you can still boot into the Clover UI. So it's not all lost. :) 

 

So, to me, it's not a matter of space on the actual EFI partition, since we're not using that for backup in the first place. We already have a backup on the OS side. We just need to do something with it, in case your Clover from the EFI partition can't be used anymore to boot back into the OS (but again, it is good enough to boot into its own UI).

 

That...was kind of the plan... But maybe that's simply not possible.

 

 

Edited by arsradu
  • Like 1
Badruzeus
Badruzeus
Posted
Posted
3 minutes ago, arsradu said:

Well, the backup is already there. :) In /Volumes/YourOSVolume/EFI-Backups. We don't need extra space on the actual EFI partition for that. We just need to get access to those backups from Clover GUI and use them either to boot into the OS, or to rewrite what's on the main EFI partition. That's all.

Oh, I see.. so for "Restore from Backup" only via Clover from HFS+/APFS partition since these FS are read-only on preboot.

arsradu
arsradu
Posted
Posted (edited)
13 minutes ago, Badruzeus said:

Oh, I see.. so for "Restore from Backup" only via Clover from HFS+/APFS partition since these FS are read-only on preboot.

 

Yep. We only need to read from the OS. We don't need to write anything there. The backup is already there. We don't need to make a new one. We just need to use it. And, for as far as I can tell (and I could be wrong here), we only read from the OS either way. Either to use that backup and boot into the OS using that information (assuming that's possible). Ooor...as I said before, to restore one of those backups and put it back onto the EFI partition, so we can boot normally. Either way it's still reading from the OS. So yeah, I would say we probably don't need -rw access for this.

Edited by arsradu
  • Like 2
apianti
apianti
Posted
Posted

If you can enter the GUI then you can fix the problem, either by restoring the backups with the efi shell, then restarting or by changing the configuration directly in the GUI and then fixing the problem. I thought you meant you couldn't get into the GUI. Literally restoring the backup is just copying the folder back, there's no need for a feature in clover when you can type one line into the efi shell..... Or use another OS. It just doesn't make sense.

  • Like 2
arsradu
arsradu
Posted
Posted (edited)

Well... you can type one line if you know what that line is. :)) But it might not be that obvious for regular users. That’s why I thought it would be a good thing to have that in the Clover UI itself.

After all, a lot of things can be done from Shell. Still, we also have a more user-friendly option to achieve the same thing from Clover UI. You could probably even boot directly from Shell. You don’t really need the UI for that. Still, we do have a beautiful Clover UI so we don’t need to do this manually from command line.

Same for this case.

To be honest, I prefer the UI for stuff like this. And probably most regular users do, as well. It happened to me before that, even though I knew the command I needed to write into the terminal by heart, still happened to make mistakes writing it, or pressing Enter sooner than I might have wanted. :)) Which, and I’m sure I don’t need to tell you this, but if you do this and don’t write the complete path in a rm command cause you pressed Enter sooner than you should have, you risk deleting a lot more than you wanted. Potentially resulting in an unbootable system. Now, I know this is copying, not deleting. But still, to me, having this as an option in the UI is not just more user friendly, but also safer and less prone to user mistakes.

Anyway, as I said, it’s only an idea. And I just thought I’d bring it up for discussion in case you guys find it useful. Once again, thank you very much for your feedback. :)

Edited by arsradu
  • Like 1
JadaOnyx
JadaOnyx
Posted
Posted (edited)
On 1/8/2019 at 10:50 PM, Andres ZeroCross said:

 

So i reconfigure my system. Update my CLOVER to r4842 from here https://github.com/Dids/clover-builder/releases . I remove AudioDxe.efi, BootChimeDxe.efi, BootChimeCfg.efi. Then,

1. Boot into Clover GUI and Reset nvram. Press F11 in CLOVER GUI
2. Boot into mac desktop and add AudioDxe.efi to drivers64UEFi and BootChimeCfg.efi to tools and just use sound.wav into Theme folder (BGM_SVG) then reboot to CLOVER GUI (AudioDxe.efi and BootChimeCfg.efi is from here


3. Enter shell and set "bootchimecfg.efi -s 7 -v 100 -t". I use 7 because my lineout is 7
4. Boot into mac then reboot again,, i can hear sound before GUI CLOVER. then i boot to mac desktop.
5. I add BootChimeDxe.efi from GoldFish64 https://github.com/Goldfish64/AudioPkg to drivers64UEFI then i Reboot.

Finally i can hear sound from Theme Sound and sound before loading progress too.

Here the video, sorry for bad english. I attach nvram.txt and preboot.log.

Thanks before

 

 

 

 

Hey but u have a gigabyte mb, why u don't try to flash a modified ROM with a black logo.bmp file in order to get a more vanilla behavior? With a older build of UEFIFlash u can modify the .fd rom image to extract and replace that logo.bmp and with this modified efiflash (patch made by lordkag from win-raid) u can skip the sign checks... but be careful, and remember to disable the intel bios guard before flashing anything.

 

Theres my setup:

 

The only bad thing is the big delay (8-10secs approx) added by AudioDxe. With FastBoot POST enabled is still slow as hell... but im satisfied anyway! \^_^/

I have a Gigabyte Aorus Gaming 3 btw

 

Edited by JadaOnyx
typo mistake xd
Andres ZeroCross
Andres ZeroCross
Posted
Posted
 
 
 
Hey but u have a gigabyte mb, why u don't try to flash a modified ROM with a black logo.bmp file in order to get a more vanilla behavior? With a older build of UEFIFlash u can modify the .fd rom image to extract and replace that logo.bmp and with this modified efiflash (patch made by lording from win-raid) u can skip the sign checks... but be careful, and remember to disable the intel bios guard before flashing anything.
 
Theres my setup:
 
The only bad thing is the big delay (8-10secs approx) added by AudioDxe. With FastBoot POST enabled is still slow as hell... but im satisfied anyway! \^_^/ 
 
I can change the logo of gigabyte the by myself. It's easy to make it happen.

Sent from my Mi Note 2 using Tapatalk

JadaOnyx
JadaOnyx
Posted
Posted
6 minutes ago, Andres ZeroCross said:

I can change the logo of gigabyte the by myself. It's easy to make it happen.

Sent from my Mi Note 2 using Tapatalk
 

Your MB UEFI has a native option to replace ur bios logo? Ive seen this feature in a few mbs... you're lucky a lot! XD

oSxFr33k
oSxFr33k
Posted
Posted (edited)

Couple question and my apologies if this was already asked.  Does the latest version of clover support plugintype for i9-9900K or do I have to supply a SSDT generated file, not even sure if SSDTgen will export a proper file for this processor.

 

Same question for the E5-2697 v2 ivy bridge processor it seems plugintype 1 didn't work, no speed step so I just re-enabled the SSDT to get speed step working again, unless there is another plugin type I need to choose for either one of these processors?

 

Thanks!

 

 

Edited: 

 

Nevermind I found the answer in another thread the i9-9900k is supported with plugintype=yes, no SSDT needed, however the x79 boards with E5 processors does not support plugintype need to use SSDT unless the new clover versions will support the E5 or not?

Edited by oSxFr33k
oSxFr33k
oSxFr33k
Posted
Posted (edited)
On 3/14/2019 at 1:25 AM, Slice said:

Clover supports all processors even if they are engineering samples as far as they declared.

 It may support it but it Clover's PluginType 1 does not support the speed step without providing a SSDTgen for Ivy Brdige E5-2697v2.

 

I have to generate SSDT with  

ssdtPRGen.sh -c 1 -w 3 -turbo 3500.

 

Thats why I asked if maybe there was a unique plugintype provided by Clover for the E5 ivy bridge or some additional settings with PluginType=yes, in order to skip having a SSDT.  Speed step doesn't work with Clover PluginType have to use SSDT.

Edited by oSxFr33k
 Share
Go to topic listing
×
×
  • Create New...