Clover General discussion

[Jief_Machak]

3 hours ago, naiclub said:

Terminal Saved Output1.text

Same symptoms There are 188 lines of warnings.

I think warning about no debug symbol is ok. Don't know why they are here...

[naiclub]

1 hour ago, Jief_Machak said:

I think warning about no debug symbol is ok. Don't know why they are here...

Spoiler

bdmesg.text

Latest clover 5126 works fine.

[matxpa]

F.Y.I

 

Clover build

with  XCODE8 ---> 188 warnings (most of them : "warning: no debug symbols in executable (-arch x86_64)")

with  GCC53   ---> 6 errors ... ignored ( ...BdsDxeOffset.raw] Error 1 (ignored), .../SmbiosGenDxeOffset.raw] Error 1 (ignored) and .../DisplayEngineOffset.raw] Error 1 (ignored)

 

[mnfesq]

For weeks, I have been unable to use Clover to boot my laptop.  Initially, I was able to use v.5124 but I had to reformat the hard drive I stored that in and when I downloaded it again, the new package didn't work.  Since then, 5125 and 5126 also did not work.  Every time, I got to the Clover menu page, completed the initial Clover boot and started the macOS boot and, during the first stage, it stopped at the same place.  The first photo shows where it stopped and the second photo shows the same entry when successfully booting with OC 0.63.

Spoiler

I have tried every possible configuration change and was beating myself up for not being able to figure out what I did wrong.  Today, I happened to see a link to CLOVERX64-5126-7f1b87c92.efi and gave that a try.  When I boot to BS preboot, it works like a charm.  Any ideas what caused my problem and what changed in this newer build of the Clover efi file?  It is a relief to be able to use Clover again.

[Jief_Machak]

20 minutes ago, mnfesq said:

Any ideas what caused my problem and what changed in this newer build of the Clover efi file

To know, you would have to try every commit, without changing configuration, until it doesn't work. There was like 10 commits between 5126 and now...

Glag it's working now.

[naiclub]

27 minutes ago, Jief_Machak said:

To know, you would have to try every commit, without changing configuration, until it doesn't work. There was like 10 commits between 5126 and now...

Glag it's working now.

Spoiler

bdmesg.text.log

This version installs the same as the latest clover5126, great.

[chris1111]

New program for Clover user and Wifi USB adapter on Big Sur ➤ WirelessAdapterCloverBigSur

maybe that can help some user with a non working wifi on laptop in BS

Edited November 14, 2020 by chris1111

[PG7]

6 minutes ago, chris1111 said:

New program for Clover user and Wifi USB adapter on Big Sur ➤ WirelessAdapterCloverBigSur

maybe that can help some user with a non working wifi on laptop in BS

 

good night Chris

you could also try to create a way to make these kext if you load directly into the Big Sur kernel for Atheros!

I have it here and I’m using it on Clover but it’s always a little tricky to load it directly with Clover (I don’t know why) with Clover they always carry it!

Thanks for any answer
if you need someone to test the signal I can do

have a good night

[chris1111]

8 minutes ago, PG7 said:

 

good night Chris

you could also try to create a way to make these kext if you load directly into the Big Sur kernel for Atheros!

I have it here and I’m using it on Clover but it’s always a little tricky to load it directly with Clover (I don’t know why) with Clover they always carry it!

Thanks for any answer
if you need someone to test the signal I can do

have a good night

thanks I have already try the kext you mention but I have also trouble with I give up on Atheros because even on Mojave or Catalina the Wifi signal is very poor, compare for example to Realtek USB Wifi. I still have a functional Atheros in a Catalina on one of my Dell Optiplex but it is only in principle to install it 

[naiclub]

Spoiler

bdmesg.log

sierra good working at last 26 clover

[iCanaro]

On 11/12/2020 at 2:14 PM, Jief_Machak said:

On 11/12/2020 at 12:31 PM, iCanaro said:

notes to developers:

 

on AMD systems, but not only that, I also think of notebooks with I2C, for some kext it is very important that a certain loading order is defined.
For example, on my AMD X570 AMDRyzenCPUPowerManagement.kext must be loaded before SMCAMDProcessor.kext; At the same time, AMDRyzenCPUPowerManagement.kext must be loaded after VirtualSMC.kext; but VirtualSMC is also a LILU plugin, so LILU must be at the top of the load order.
All this serves for the perfect functioning and integration of the various kexts
now on clover the only distinction is that the kexts in the other folder will be loaded as a priority over kexts in folders 10.xx 11
IMHO would be useful to have the ability to define load order for kexts, if not for everyone, but for some

When can put this kext in the hard coded order list.

(please everybody, don't start with "it's bad to hard code, etc.").

 

I understand that they have now been included in Clover's code, other kexts with a specific loading order
If so, could you check if everything is OK?
I ask this because now inserting SMCAMDProcessor always gives me kernel panic with Catalina, instead no problem with mojave and big sur

this is the author specification of AMDRyzenCPUPowerManagement and SMCAMDProcessor, how they should be loaded and dependencies.
https://github.com/trulyspinach/SMCAMDProcessor

I previously wanted AMDRyzenCPUPowerManagement in the OTHER folder and SMCAMDProcessor folder on 11 10.15 10.14
now other is empty and I keep the kexts in its folder for each macOS.
Even returning to the old way, mojave and big sur ok no problem, instead always catalina kernel panic to the boot related to SMCAMDProcessor
Thank you @Jief_Machak

 

Spoiler

Anonymous UUID:       123AB5B9-6820-7F6F-B0EC-5D96D491A1D2

 

Sun Nov 15 01:21:50 2020

 

*** Panic Report ***

panic(cpu 26 caller 0xffffff801e2449ea): Kernel trap at 0xffffff7fa3ecbc71, type 14=page fault, registers:

CR0: 0x0000000080010033, CR2: 0x000000001de00000, CR3: 0x0000000030735000, CR4: 0x00000000003406e0

RAX: 0x000000001de00000, RBX: 0xffffff8066ece000, RCX: 0x0000000000000000, RDX: 0x0000000001000000

RSP: 0xffffff83d5dfbdd0, RBP: 0xffffff83d5dfbde0, RSI: 0xffffff8066ece000, RDI: 0xffffff80670ebe20

R8:  0xffffff80670e4060, R9:  0x0000000000000006, R10: 0xaaaaaaaaaaaaaaab, R11: 0x0000000000000002

R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0xffffff80670ebe20, R15: 0xffffff80670ebe20

RFL: 0x0000000000010202, RIP: 0xffffff7fa3ecbc71, CS:  0x0000000000000008, SS:  0x0000000000000000

Fault CR2: 0x000000001de00000, Error code: 0x0000000000000000, Fault CPU: 0x1a, PL: 0, VF: 1

 

Backtrace (CPU 26), Frame : Return Address

0xffffff83d5dfb830 : 0xffffff801e11868d mach_kernel : _handle_debugger_trap + 0x49d

0xffffff83d5dfb880 : 0xffffff801e252ab5 mach_kernel : _kdp_i386_trap + 0x155

0xffffff83d5dfb8c0 : 0xffffff801e24463e mach_kernel : _kernel_trap + 0x4ee

0xffffff83d5dfb910 : 0xffffff801e0bea40 mach_kernel : _return_from_trap + 0xe0

0xffffff83d5dfb930 : 0xffffff801e117d57 mach_kernel : _DebuggerTrapWithState + 0x17

0xffffff83d5dfba30 : 0xffffff801e118147 mach_kernel : _panic_trap_to_debugger + 0x227

0xffffff83d5dfba80 : 0xffffff801e8bf2bc mach_kernel : _panic + 0x54

0xffffff83d5dfbaf0 : 0xffffff801e2449ea mach_kernel : _sync_iss_to_iks + 0x2aa

0xffffff83d5dfbc70 : 0xffffff801e2446e8 mach_kernel : _kernel_trap + 0x598

0xffffff83d5dfbcc0 : 0xffffff801e0bea40 mach_kernel : _return_from_trap + 0xe0

0xffffff83d5dfbce0 : 0xffffff7fa3ecbc71 wtf.spinach.SMCAMDProcessor : __ZN15SMCAMDProcessor5startEP9IOService + 0x25

0xffffff83d5dfbde0 : 0xffffff801e804dc6 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6

0xffffff83d5dfbe40 : 0xffffff801e804901 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xad1

0xffffff83d5dfbef0 : 0xffffff801e803c9e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2de

0xffffff83d5dfbf50 : 0xffffff801e806456 mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x186

0xffffff83d5dfbfa0 : 0xffffff801e0be13e mach_kernel : _call_continuation + 0x2e

      Kernel Extensions in backtrace:

         wtf.spinach.SMCAMDProcessor(1.0)[5384C3B3-8A06-38B0-A983-DD7567476396]@0xffffff7fa3eca000->0xffffff7fa3ed2fff

            dependency: as.vit9696.Lilu(1.4.9)[6E38576B-9675-3D9E-9763-5B0F9DA1B098]@0xffffff7fa3e87000

            dependency: as.vit9696.VirtualSMC(1.1.8)[3BC5157C-7E87-31A4-8C61-3770E078BA73]@0xffffff7fa3eb1000

            dependency: com.apple.iokit.IOPCIFamily(2.9)[2F37AE58-E6B9-3B18-9092-3B80D34C334B]@0xffffff7f9ed1a000

            dependency: com.apple.kec.Libm(1)[5B023622-E5C0-32FB-9731-6D82AAAA7397]@0xffffff7f9eb5f000

            dependency: wtf.spinach.AMDRyzenCPUPowerManagement(0.6.3)[03176D75-8A9F-36D2-A619-E3CC890AE4D3]@0xffffff7fa59fe000

 

BSD process name corresponding to current thread: kernel_task

Boot args: -v keepsyms=1 debug=0x100 -inniebeta 

 

Mac OS version:

Not yet set

 

Kernel version:

Darwin Kernel Version 19.6.0: Thu Oct 29 22:56:45 PDT 2020; root:xnu-6153.141.2.2~1/RELEASE_X86_64

Kernel UUID: 9B5A7191-5B84-3990-8710-D9BD9273A8E5

Kernel slide:     0x000000001de00000

Kernel text base: 0xffffff801e000000

__HIB  text base: 0xffffff801df00000

System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)

System shutdown begun: NO

Panic diags file unavailable, panic occurred prior to initialization

 

System uptime in nanoseconds: 944549369

 

EOF

Model: iMacPro1,1, BootROM 1037.120.87.0.0, 16 processors, 3,50 GHz, 32 GB, SMC 

Graphics: Vega 10 XL/XT [Asus Arez Vega56], Vega 10 XL/XT [Asus Arez Vega56], spdisplays_pcie_device, 8 GB

Memory Module: BANK 0/DIMM0, 8 GB, DDR4, 2133 MHz, Unknown, 3733 C17 Series

Memory Module: BANK 1/DIMM0, 8 GB, DDR4, 2133 MHz, Unknown, 3733 C17 Series

Memory Module: BANK 2/DIMM0, 8 GB, DDR4, 2133 MHz, Unknown, 3733 C17 Series

Memory Module: BANK 3/DIMM0, 8 GB, DDR4, 2133 MHz, Unknown, 3733 C17 Series

Bluetooth: Version 6.0.14d11, 3 services, 17 devices, 1 incoming serial ports

Network Service: Ethernet, Ethernet, en0

PCI Card: FCH SMBus Controller, SMBus, Built In

PCI Card: Matisse USB 3.0 Host Controller, USB controller #3, Built In

PCI Card: Realtek ALC1220 Codec, Analog Audio device, Built In

PCI Card: Vega 10 XL/XT [Asus Arez Vega56], Display Controller, PCIe-4 Slot-1

PCI Card: Vega 10 HDMI Audio [Asus Arez Vega56], HDMI/DP Audio device, PCIe-4 Slot-1

PCI Card: Realtek RTL8125A PCI Express 2.5 Gigabit Ethernet, Ethernet controller, Built In

PCI Card: Wi-Fi 6 AX200, Network controller, Built In

PCI Card: FCH SATA Controller [AHCI mode], SATA controller #2, Built In

PCI Card: FCH SATA Controller [AHCI mode], SATA controller #1, Built In

PCI Card: Matisse USB 3.0 Host Controller, USB controller #1, Built In

PCI Card: Matisse USB 3.0 Host Controller, USB controller #2, Built In

Serial ATA Device: SanDisk SDSSDH32000G, 2 TB

Serial ATA Device: SATA3 2TB SSD, 2 TB

Serial ATA Device: WDC WD30EFRX-68EUZN0, 3 TB

Serial ATA Device: WDC WD30EFRX-68EUZN0, 3 TB

USB Device: USB 3.1 Bus

USB Device: USB2.0 Hub

USB Device: MYSTIC LIGHT

USB Device: USB 3.1 Bus

USB Device: USB 2.0 Hub

USB Device: USB OPTICAL MOUSE

USB Device: Trust Keyboard

USB Device: Bluetooth HCI

USB Device: USB 3.1 Bus

USB Device: USB OPTICAL MOUSE

Thunderbolt Bus: 

 

Edited November 15, 2020 by iCanaro

[PG7]

13 minutes ago, chris1111 said:

thanks I have already try the kext you mention but I have also trouble with I give up on Atheros because even on Mojave or Catalina the Wifi signal is very poor, compare for example to Realtek USB Wifi. I still have a functional Atheros in a Catalina on one of my Dell Optiplex but it is only in principle to install it 

 

 

here I am with her in Big Sur 20B29 with Clover r5126 this is working normal as in all systems!

 

Spoiler

 

[iCanaro]

today in the X570 AMD hack I ran the security update 2020-006 for high sierra, started and completed using OpenCore, as finished, restarted with Clover and.....
Surprise! the bigsur preboot systemversion has been changed.
This, in my opinion, closes the question that the problem may be Clover, but it is linked to high sierra and it may be that I keep it in HFS+

 

Spoiler

 

 

 

 

Edited November 15, 2020 by iCanaro

[LockDown]

Can i just add ExtendBTFeatureFlags (Bt4lecontinuity replacement)

in quirks section and it will just work in clover?

[Matgen84]

8 minutes ago, ellaosx said:

Can i just add ExtendBTFeatureFlags (Bt4lecontinuity replacement)

in quirks section and it will just work in clover?

I think not because this quirk must be declared in the various Clover code files to work. 

 

[MICKHAEL]

hello to all, 

I just what to inform, if someone have blackscreen symptom, like Clover are not loading, check your UEFI drivers folder, and change HfsPlus.efi to Vboxhfs.efi

Quote

 

[LockDown]

@MICKHAEL is this before or after the clover GUI loads?

[MICKHAEL]

10 minutes ago, ellaosx said:

@MICKHAEL is this before or after the clover GUI loads?

thats before GUI.
HfsPlus just block GUI loading

[Matgen84]

42 minutes ago, MICKHAEL said:

hello to all, 

I just what to inform, if someone have blackscreen symptom, like Clover are not loading, check your UEFI drivers folder, and change HfsPlus.efi to Vboxhfs.efi

 

 

This looks like BootloaderChooser: where do you find cloverx64-2020-11-14-13-15-10-2cdab64-dirty-jief commits ! Please.

[MICKHAEL]

1 hour ago, Matgen84 said:

 

This looks like BootloaderChooser: where do you find cloverx64-2020-11-14-13-15-10-2cdab64-dirty-jief commits ! Please.

From developer. Debug version)

[SavageAUS]

22 hours ago, iCanaro said:

 

great very well
that config you can also continue to use it, know that it only works for catalina and big sur, so it would not start mojave and high sierra

Do you mean the new one you created for me to install BS? Is ok to still use it?

[iCanaro]

yes

[Jief_Machak]

The under screen is misleading. It's is indeed BootloaderChooser that is starting a "special" Clover that display "Start". It was just to be sure that Clover is really loading.

The things is : if you have an early crash in Clover, the symptom could just be a black screen (or just BootloaderChooser messages) and no debug.log.

Looks like HFSPlus.efi can crash. That is the point of the post.

 

 

2 hours ago, MICKHAEL said:

I just what to inform, if someone have blackscreen symptom, like Clover are not loading, check your UEFI drivers folder, and change HfsPlus.efi to Vboxhfs.efi

Quote

 

 

[PG7]

@Jief_Machak @Slice  @iCanaro

 

 

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

 

I tried everything even with OpenCore with and without DSDT plus and minus Kext several Bios configurations but the error always remains the same ...

 

I send update via the system directly and the error is identical but it happens after 15 minutes !!!

someone who has a solution or ideas to test
SO happens with Big Sur (all versions)

I have no problems to boot with a disk where the system is already installed!

 

Thanks

 

Google translate ! 

 

 

 

Spoiler

 

Historique de Programme d’installation 15-Nov-2020.txt

[naiclub]

Spoiler

This version is not light at all.

bdmesg.log

 

Edited November 15, 2020 by naiclub