Clover General discussion

[chris1111]

22 hours ago, PG7 said:

Hello good afternoon

 

I have a problem with two PCs to install BigSur autonomo by the pendrive on them! (I never had any problems with Catalina)

let's start here by the first

 

Lenovo Thinkcentre M93p

intel i5-4460s
intel HD4600 + Nvidia GTX760 3go
SSD x2
28Go RAM
Clover r5126

 

system at the moment
1 SSD 240Go = Windows 10 2004
1 SSD 480Go = MacOS Mojave - Catalina - BigSur 20B29 (installed on the SSD by another pc)

 

problem

I can enter the 1 installation phase and start BUT when it reaches 13 minutes it makes the print error posted here!
I also leave a report of the error in the install

 

Thanks

 

Google translate ! 

 

 

 

  Hide contents

 

 

Do you please provide your EFI I will check for you

[PG7]

11 minutes ago, chris1111 said:

Do you please provide your EFI I will check for you

 

 

Merci Chris 

 

voila ici 

 

 

good afternoon Chris

 

this is the Clover I use and for the installation I have to use the SMBIOS iMac 14.4 or 15.1

for normal use I have to use SMBIOS 14.2 MANDATORY because if not with any other SMBIOS I can activate the USB3 ports on this Lenovo M93p

 

I let my DSDT go too but even without it the error is the same and in OpenCore it is exactly the same error

not well from the image or the pendrive because with the same I can install on my other pc without problems

a very identical error also happens with my HP Envy Recline AIO which are the same version of Haswell chipset

 

I have another Lenovo M93 All In One and I can install it without any problem (I can't see what may be at issue, pass on my knowledge)

 

in any case thanks for your help

Edited November 16, 2020 by PG7

[chris1111]

7 minutes ago, PG7 said:

 

 

Merci Chris 

 

voila ici 

 

 

good afternoon Chris

 

this is the Clover I use and for the installation I have to use the SMBIOS iMac 14.4 or 15.1

for normal use I have to use SMBIOS 14.2 MANDATORY because if not with any other SMBIOS I can activate the USB3 ports on this Lenovo M93p

 

I let my DSDT go too but even without it the error is the same and in OpenCore it is exactly the same error

not well from the image or the pendrive because with the same I can install on my other pc without problems

a very identical error also happens with my HP Envy Recline AIO which are the same version of Haswell chipset

 

I have another Lenovo M93 All In One and I can install it without any problem (I can't see what may be at issue, pass on my knowledge)

 

in any case thanks for your help

You can try this ; hope that help?

 

config.plist.zip

SSDT-EC.aml.zip

[PG7]

2 minutes ago, chris1111 said:

You can try this ; hope that help?

 

config.plist.zip

SSDT-EC.aml.zip

 

 

I will test now and give an answer

merci

[PG7]

39 minutes ago, chris1111 said:

You can try this ; hope that help?

 

config.plist.zip

SSDT-EC.aml.zip

 

Chris

 

tested the config and the EC

- the config had to pass the iMac15.1 think it was your mistake the iMac5,1
- the EC I already have in the DSDT in LPCB

 

the error remains the same in the same place!

 

16.02 Historique de Programme d’installation 16-Nov-2020.txt

[naiclub]

Spoiler

I want to make this version very complete.

I am very pleased with Clover 5126. Can boot any version From MountainLion to bigsur

Edited November 16, 2020 by naiclub

[PG7]

I will test another way

 

I launched another test but now in direct update from the system
the error returns equal

Spoiler

 

remember that if you install the system on another machine on the SSD, I can then use it on this machine without any problem

[chris1111]

37 minutes ago, PG7 said:

 

Chris

 

tested the config and the EC

- the config had to pass the iMac15.1 think it was your mistake the iMac5,1
- the EC I already have in the DSDT in LPCB

 

the error remains the same in the same place!

 

16.02 Historique de Programme d’installation 16-Nov-2020.txt

Yes sorry iMac 15.1  error remains the same  another big mystery of Big Sur 11 

[yzq159]

 

XhciPortLimit has been set to YES, but it doesn't seem to work. How can I solve this problem

[jlrycm]

On 11/13/2020 at 11:46 AM, jlrycm said:

Hello @everyone, I installed Big Sur release using a USB pen drive and it went smoothly. The only issue so far is that the USB 3.1 ASmedia controller pcie card is not loaded properly and the USB 3.1 external disk is not recognized as such when connected. Attached are some pictures and my efi folder (excluding themes and doc folders). Any tips will be highly appreciated.

 

Archive Clover.zip

Jorge’s iMac.zip

Hello @Slice @Jief_Machak: by any chance you had the opportunity to see my previous post about my installation of Big Sur, which was successful except for the USB 3.1 gen 2 PCIe card which is loaded properly in Catalina but not in Big Sur. The card uses ASmedia 2142 usb controller which is supposed to be supported natively. I checked with the vendor and they responded that the card is supposed to be supported natively by Big Sur. However, that’s not the case as you can see in the pictures attached to my previous post in which I also attached the efi folder and the ioreg copy.

[Slice]

I may suppose that ACPI name does matter. It shouldn't be PXSX but XHCI or XHC1.

[Deadpool]

21 hours ago, Deadpool said:

Hi @Jief_Machak I had the same exact problem on Big Sur when I have updated all the kexts in “Other” folder to their last commit versions (had no problem with release kexts versions). I had then a no bootable system and installed Catalina with an old usb and now I’m planning to update to Big Sur. Hope it helps!

Hi again @Jief_Machak just to give you an update: I have fresh installed Catalina and selected update to Big Sur pop up message. Once ready, I started the update process and I have the exact same error when from clover screen it should start to update. Same error message. So I’m unable to update from Catalina to Big Sur using last commit version of clover. 

[iCanaro]

5 hours ago, jlrycm said:

Hello @everyone, I installed Big Sur release using a USB pen drive and it went smoothly. The only issue so far is that the USB 3.1 ASmedia controller pcie card is not loaded properly and the USB 3.1 external disk is not recognized as such when connected. Attached are some pictures and my efi folder (excluding themes and doc folders). Any tips will be highly appreciated.

 

PXSX is normal for USB3 asmedia as additional controllers

remove USBinjectall and you'll see that the correct USB power supply starts working again
USBinjectall is an absolutely useful kext during installation, but in post installation it is to be removed from the feet as soon as possible, mapping the USB and refining hack settings.

[iCanaro]

47 minutes ago, Deadpool said:

I have fresh installed Catalina and selected update to Big Sur pop up message. Once ready, I started the update process and I have the exact same error when from clover screen it should start to update. Same error message. So I’m unable to update from Catalina to Big Sur using last commit version of clover. 

you have integrated the new quirks section, put as openruntime memory manager and verified that you start now?! otherwise you won't party with BS. 
Then if you can't download from appstore, there are at least a couple of scripts to download installer complete with big sur
RunME_Downloader of gengik84
IinstallScript_1016fullapp

[Deadpool]

13 minutes ago, iCanaro said:

you have integrated the new quirks section, put as openruntime memory manager and verified that you start now?! otherwise you won't party with BS. 
Then if you can't download from appstore, there are at least a couple of scripts to download installer complete with big sur
RunME_Downloader of gengik84
IinstallScript_1016fullapp

Hi @iCanaro I’m using last commit version of clover 5126. It boots Catalina correctly with quirks section and OpenRuntime. Everything works as expected. The only problem I have now is that I would like to update Catalina to Big Sur and I have the same error message as reported before when from clover screen it should start the update process.

[Jief_Machak]

What is the best (or recommanded) way to activate trim for SSD ? trimforce, or a patch ?

[MICKHAEL]

5 minutes ago, Jief_Machak said:

What is the best (or recommanded) way to activate trim for SSD ? trimforce, or a patch ?

hi, I think trimforce if its possible

[iCanaro]

5 minutes ago, Jief_Machak said:

What is the best (or recommanded) way to activate trim for SSD ? trimforce, or a patch ?

what leads to the desired result  generally both methods work.
My opinion is that if you want TRIM enabled even during installation processes, better patch, otherwise TRIMFORCE post installation is OK

 

1 minute ago, eSaF said:

@Jief_Machak - Hi - I was led to understand that most high end SSD Drives has inbuilt ability for garbage collection so by discarding the need for a third party patch or I am mistaken?

it's absolutely true what you say.
Forcing TRIM, however, could help those SSD drives where garbage collection doesn't do its job

[jlrycm]

1 hour ago, iCanaro said:

 

PXSX is normal for USB3 asmedia as additional controllers

remove USBinjectall and you'll see that the correct USB power supply starts working again
USBinjectall is an absolutely useful kext during installation, but in post installation it is to be removed from the feet as soon as possible, mapping the USB and refining hack settings.

Hello @iCanaro. Thanks a lot for sharing your thoughts. I’m using USBinjectall combined with a custom SSDT-UIAC which is a solution equally valid as the USBmaps.kext. From I have learned, the card has native support in Catalina and previous macOS versions and the SSDT-UIAC + USBINJECTALL couple was not supposed to have influence over USB controllers natively supported. I really don’t have an idea why this card is not working in Big Sur, unless the kext is not being uploaded properly. When I connect a drive to the USB Type C port, nothing happens, and as shown in the picture, the USB is displayed as 3.0 instead of 3.1 which is how is displayed in Catalina.  Also, in Catalina the USB 3.1 in this card appears to be supported by AppleUSBXHCIPCI which is a plug-in of IOUSBHostfamily kext. I thought about a workaround of loading the Catalina kext directly from OpenCore but not sure it would work. At least it’s a solution that some colleagues applied in Big Sur to enable the wifi cards whose native support was dropped in Big Sur. Any thoughts on that, @Slice, @Jief_Machak, @iCanaro or anyone else?

[Jief_Machak]

37 minutes ago, iCanaro said:

SSD drives where garbage collection doesn't do its job

Seems my case !

I had the patch, but since OC integration, the kext name must be the full name.

Thanks.

[iCanaro]

12 minutes ago, jlrycm said:

I’m using USBinjectall combined with a custom SSDT-UIAC which is a solution equally valid as the USBmaps.kext. From I have learned, the card has native support in Catalina and previous macOS versions and the SSDT-UIAC + USBINJECTALL couple was not supposed to have influence over USB controllers natively supported

no negative, the solution you adopt for me is not good, the use of USBinjectall brings power problems to USB ports.
if you want a good alternative, with hackintool generate USBPorts.kext and only use him
no USBinjectall, no SSDT-UIAC and no port limit patches

[jlrycm]

2 hours ago, iCanaro said:

 

PXSX is normal for USB3 asmedia as additional controllers

remove USBinjectall and you'll see that the correct USB power supply starts working again
USBinjectall is an absolutely useful kext during installation, but in post installation it is to be removed from the feet as soon as possible, mapping the USB and refining hack settings.

Hello @iCanaro. Thanks a lot for sharing your thoughts. I’m using USBinjectall combined with a custom SSDT-UIAC which is a solution equally valid as the USBmaps.kext. From I have learned, the card has native support in Catalina and previous macOS versions and the SSDT-UIAC + USBINJECTALL couple was not supposed to have influence over USB controllers natively supported. However, I could try the corpnewt USBmaps guide if it’s better than what I did.  I really don’t have an idea why this card is not working in Big Sur, unless the kext is not being uploaded properly. When I connect a drive to the USB Type C port, nothing happens, and as shown in the picture, the USB is displayed as 3.0 instead of 3.1 which is how is displayed in Catalina.  Also, in Catalina the USB 3.1 in this card appears to be supported by AppleUSBXHCIPCI which is a plug-in of IOUSBHostfamily kext. I thought about a workaround of loading the Catalina kext directly from OpenCore but not sure it would work. At least it’s a solution that some colleagues applied in Big Sur to enable the wifi cards whose native support was dropped in Big Sur. Another option I thought was to patch the AppleASMediaUSBXHCI that appears in the picture above as loading the USB 3.0 to force it to recognize the card ports as USB 3.1. Any thoughts about alternatives, @Slice, @Jief_Machak, @iCanaro or anyone else?

Edited November 17, 2020 by jlrycm

[chris1111]

29 minutes ago, mifjpn said:

Thank you,Slice and Jief!!

Hello everyone.
Was the location of CloverBackups decided to be "~/Desktop/Clover EFI Backups"?
It's not bad in an easy-to-see place.
But I think some people care about how it looks on Desktop.
My suggestion is "~/Clover EFI Backups".
Since this is the home folder, so you'll definitely notice it, and I think it's a convenient place to separate it from other folders.

What do you think of it?

If possible,
I am waiting for "Like", "sad" votes.
Thank you.

I think Everybody as suggestion and all is good but imposible to satisfy all people

if you prefer other directory why don't you do it yourself

Its verry simply

CloverBootloader/CloverPackage/package/Scripts.templates/EFIFolder/preinstall

Open with Xcode or any good textediter

Line 95 / 98 change it as you want. Simple as that

Spoiler

 

 

 

For my part, I prefer the Desktop at Home 

Edited November 17, 2020 by chris1111
Image in spoiler

[iCanaro]

for all Clover users who do not use custom SSDT-PLUG or SSDT x PM (Power Management), but use only the plugin type flag, to verify that the PM certainly does not work

 

https://www.macos86.it/topic/3834-power-management/?do=findComment&comment=93066

 

https://www.macos86.it/topic/3647-clover-quirks/?do=findComment&comment=89965

 

quick fix this but we recommend using ssdt x pm

[iCanaro]

1 hour ago, jlrycm said:

Hello @iCanaro. Thanks a lot for sharing your thoughts. I’m using USBinjectall combined with a custom SSDT-UIAC which is a solution equally valid as the USBmaps.kext. From I have learned, the card has native support in Catalina and previous macOS versions and the SSDT-UIAC + USBINJECTALL couple was not supposed to have influence over USB controllers natively supported. However, I could try the corpnewt USBmaps guide if it’s better than what I did.  I really don’t have an idea why this card is not working in Big Sur, unless the kext is not being uploaded properly. When I connect a drive to the USB Type C port, nothing happens, and as shown in the picture, the USB is displayed as 3.0 instead of 3.1 which is how is displayed in Catalina.  Also, in Catalina the USB 3.1 in this card appears to be supported by AppleUSBXHCIPCI which is a plug-in of IOUSBHostfamily kext. I thought about a workaround of loading the Catalina kext directly from OpenCore but not sure it would work. At least it’s a solution that some colleagues applied in Big Sur to enable the wifi cards whose native support was dropped in Big Sur. Another option I thought was to patch the AppleASMediaUSBXHCI that appears in the picture above as loading the USB 3.0 to force it to recognize the card ports as USB 3.1. Any thoughts about alternatives, @Slice, @Jief_Machak, @iCanaro or anyone else?

 

for me the solution is simple and I have been using it for some time on all hacks, that is, I create a special ssdt usb mapping by extracting my ACPI and modifying the one related to USB.
With haswell it is even easier, because there is a .dsl sample to be modified with macials to disable doors that you do not use and fall within the limit of 15 imposed by the fruit seller.
The point is that even though there have been these guides for years, as far as I know, they're only in Italian, and sometimes understanding or using translators, it's not easyhttps://www.macos86.it/topic/9-mappatura-porte-usb/?do=findComment&comment=149

 

personally i never recommend patching system files as much as possible configure everything from efi