Clover General discussion

[Andres ZeroCross]

57 minutes ago, arsradu said:

 

I'm guessing you have FakeSMC somewhere else....? Cause it seems to be missing from Clover/kexts/Other.

 

So...is it fixed now with this solution?

 

 

I have used VirtualSMC.kext,, you didn't see it

36 minutes ago, ellaosx said:

i have used boot7 to solve my issue similar to yours long time ago

I have tried Boot7 too,, but i thought you have different problem with me. You can reach GUI CLOVER right?? Your error long ago is about when you press enter in boot entry screen.

But mine is different, i CAN'T REACH Clover GUI

[LockDown]

I cant reach gui too with boot6. Boot7 worked for me. It was also an ivy on 6 series asus board. But boards may vary.

[chris1111]

12 minutes ago, Andres ZeroCross said:

I have used VirtualSMC.kext,, you didn't see it

I have tried Boot7 too,, but i thought you have different problem with me. You can reach GUI CLOVER right?? Your error long ago is about when you press enter in boot entry screen.

But mine is different, i CAN'T REACH Clover GUI

Did you have Clover in ESP (Legacy) or Clasic Legacy on root disk ?

[Andres ZeroCross]

Just now, chris1111 said:

Did you have Clover in ESP (Legacy) or Clasic Legacy on root disk ?

CLOVER in ESP

[Andres ZeroCross]

Btw problem is solved, i have post it above, 

Forget legacy,, the graphics problem still can be fixed with UEFI boot + Legacy Option Rom Disable + CSMVideoDxe.efi

[arsradu]

38 minutes ago, Andres ZeroCross said:

I have used VirtualSMC.kext,, you didn't see it

 

Ouuups! You're right. I've totally missed that one.  

 

Glad you managed to fix it!

[Slice]

1 hour ago, Andres ZeroCross said:

Btw problem is solved, i have post it above, 

Forget legacy,, the graphics problem still can be fixed with UEFI boot + Legacy Option Rom Disable + CSMVideoDxe.efi

We have to remember that Legacy Option ROM can cause Red Panic in legacy clover.

[Andres ZeroCross]

3 minutes ago, Slice said:

We have to remember that Legacy Option ROM can cause Red Panic in legacy clover.

I thought every LEgacy boot always use Legacy Option ROM. Because the option can't be disabled in Legacy Mode

Edited July 29, 2019 by Andres ZeroCross

[Sherlocks]

suggest one.

there is EFI-Backup folder in root in catalina beta4.

to remove this folder, we have to 

 

sudo mount -uw /

sudo killall Finder

 

but in dp4, i can't remove backup folder like this

can we change better location of efi-backup folder in catalina?

[chris1111]

1 hour ago, Sherlocks said:

suggest one.

there is EFI-Backup folder in root in catalina beta4.

to remove this folder, we have to 

 

sudo mount -uw /

sudo killall Finder

 

but in dp4, i can't remove backup folder like this

can we change better location of efi-backup folder in catalina?

 

 

Should not put backup file on root for all macOS versions
In my opinion it should be in $HOME or Desktop

 

 

edit******

I just try 

sudo rm -r "${3}"/EFI-Backups

its work 

Edited July 31, 2019 by chris1111
ad working command to remove efi-backups

[Wackymac]

Does any one know what causes the duplicate UEFI boot entries? more specifically why this issue never existed for me prior. ive tried updating/downgrading my bios and that doesnt resolve the issue. Is this something in clover? all ive been able to read is that this is a bios bug... yet it sorta came out of random (after the machine locked up exporting some video) . and no previous bios versions corrected the issue.

 

any help is greatly appreciated i would love to fix this issue.

[Guest ricoc90]

 

3 hours ago, Sherlocks said:

can we change better location of efi-backup folder in catalina?

 

Maybe it's an idea to integrate the option to delete the backup folder in Clover prefpane?

Honestly I don't think there's a better location. The root is quite an easy reachable place in case you need to get access to it through a shell etc

 

Edited July 31, 2019 by ricoc90

[pkdesign]

I have been trying to work on getting a proper slide value for my *memoryfix. Am I suppose to be able to get a text file of my memory map, i.e. memmap > memmap.txt? That command does not work. I can only use memmap and take screen shots.

[MICKHAEL]

3 minutes ago, pkdesign said:

I have been trying to work on getting a proper slide value for my *memoryfix. Am I suppose to be able to get a text file of my memory map, i.e. memmap > memmap.txt? That command does not work. I can only use memmap and take screen shots.

what formula are you using for that? 

[pkdesign]

2 minutes ago, MICKHAEL said:

what formula are you using for that? 

The formula I am using is: (Start Value / 200000) +1

 

The problem is I am having a hard time understanding which and what values to use. They also keep changing with each method.

 

This is what I doing currently:

At boot with AptioFix I get Error allocating 0x11971 pages at ...

0x11971 calculates to 72049

In my memmap, I calculate the #Pages value (in Type>Available) to find the first that is more than 72049

That is Available > Start B825000

(B82500/200000)+1 = 0x5D or 93

 

Aaaand still no boot.

 

 

[MICKHAEL]

try slide argument 128
anyway, I found another formula)) start*0x100000/0x200000

https://github.com/wmchris/DellXPS15-9550-OSX/blob/master/Additional/slide_calc.md

Edited July 31, 2019 by MICKHAEL

[Matgen84]

18 hours ago, chris1111 said:

 

Should not put backup file on root for all macOS versions
In my opinion it should be in $HOME or Desktop

 

 

edit******

I just try 

sudo rm -r "${3}"/EFI-Backups

its work 

 

Great works. Thanks 

 

EDIT: Other method found in Apple Developer forum:

 

SIP must be disable

Mount drive for read and write (sudo mount -uw /).
Assign rights for read and right ([sudo] chmod - R 775 /your\ folder\).
Delete it ([sudo] rm -rf /your\ folder\).

 

Edited August 1, 2019 by Matgen84

[LockDown]

It should never be on desktop

[vector sigma]

13 hours ago, ellaosx said:

It should never be on desktop

Agreed. Using $HOME/Desktop from with in the package.... the result will be '/var/root/Desktop' i.e. to access the backup you will have to enable the root account and then having just the same problem, i.e. the file system is still read write, but all this with more and more complications.  

 

P.S. Just after installing with Clover's package the file system become read-write... and you can rm what you want, easily.

[joevt]

8 hours ago, vector sigma said:

Agreed. Using $HOME/Desktop from with in the package.... the result will be '/var/root/Desktop' i.e. to access the backup you will have to enable the root account and then having just the same problem, i.e. the file system is still read write, but all this with more and more complications.  

 

Is the Clover installer running as root? So something like $HOME/Documents will also not work? What about the /Users/Shared folder?

 

[Sherlocks]

8 hours ago, vector sigma said:

Agreed. Using $HOME/Desktop from with in the package.... the result will be '/var/root/Desktop' i.e. to access the backup you will have to enable the root account and then having just the same problem, i.e. the file system is still read write, but all this with more and more complications.  

 

P.S. Just after installing with Clover's package the file system become read-write... and you can rm what you want, easily.

 

after update5, can remove backup folder with drag-drop without rm in terminal. just need to enable rw.

 

[pkdesign]

On 7/31/2019 at 1:54 PM, MICKHAEL said:

try slide argument 128
anyway, I found another formula)) start*0x100000/0x200000

https://github.com/wmchris/DellXPS15-9550-OSX/blob/master/Additional/slide_calc.md

Didn’t work. I've given up. Until someone fixes the issue with *memory fixes and Gigabyte boards, I am sticking with the 200free version.

[vector sigma]

On 8/2/2019 at 4:50 AM, joevt said:

Is the Clover installer running as root? So something like $HOME/Documents will also not work? What about the /Users/Shared folder?

 

yep. /User/Shared can only be used in the current OS and not in the target volume, unless a /Users/Shared folder exists (not the case of a pen drive)... then running from different OSes you will have more than one backup.

On 8/2/2019 at 5:19 AM, Sherlocks said:

after update5, can remove backup folder with drag-drop without rm in terminal. just need to enable rw.

That only means that Apple fix Finder.app and now is observing for the filesystem changes.

[joevt]

2 hours ago, vector sigma said:

you will have more than one backup.

Can never have too many backups...

 

But don't you mean there may be more than one backup location as there is only ever one backup per install attempt?

 

In other words, doing an install will do a backup, but the backup could be located in a different location from where previous backups were made if you installed from an OS that is different from the OS that was used during previous installations?

 

[vector sigma]

6 hours ago, joevt said:

But don't you mean there may be more than one backup location as there is only ever one backup per install attempt?

 

In other words, doing an install will do a backup, but the backup could be located in a different location from where previous backups were made if you installed from an OS that is different from the OS that was used during previous installations?

Wanted to say that now the backup is made in the root of the target volume, so a backup always belong to it. Instead, supposing we want to made a backup in $HOME... this is the home of the current OS (can't be otherwise) and running the pkg from another partition you will have a backup in two different places. Additionally you will don't know if your backup is the backup of your internal HD/SSD or your pen drive (in case you want update Clover on a usb stick) and also without temporal logic....  so why the root of the target volume is a perfect place....  

P.S. The package also actually takes care of not making a lot of of backups and only takes latest