Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,887 posts in this topic

Recommended Posts

Matgen84
Matgen84
Posted
Posted
2 hours ago, jlrycm said:

@naiclub, I followed your suggestion and it did not work, the PXSX is not reporting outputs and the USB 3.1 is not loaded properly. I’m more and more convinced that if I figured out how to deal with the change in the AppleUSBXHCIPCI plug-in with respect to ASmedia, I may find the solution. The info.plist of such plug-in in Big Sur is attached for reference. The PCIE USB 3.1 card I have installed is based on ASMedia2142 controller and was natively supported in Catalina.

Info.plist


@jlrycm In the info.plist, It seems that Apple has replaced Asmedia2142 by Asmedia3142 in some lines. Maybe it's the reason why you've a problem with your card. Unfortunately, I don't know how to make a patch or a specific SSDT, sorry :)

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
On 11/19/2020 at 6:06 PM, chris1111 said:

@Jief_Machak Interesting :) bdmesg also gives the kexts patch info but differently if I understand

 

  Hide contents 


13:660  0:000  Finally: ExternalClock=25MHz BusSpeed=100000kHz CPUFreq=3300MHz PIS: hw.busfrequency=100000000Hz
13:660  0:000  Beginning OC
13:660  0:000  OCST: Missing vault data, ignoring...
13:669  0:008  config-oc.plist isn't use at all
13:669  0:000  AddKextsInArray from Other
13:669  0:000  ->Extra kext: Other\Lilu.kext (v.1.4.9)
13:669  0:000  ->Extra kext: Other\AirportBrcmFixup.kext (v.2.1.1)
13:669  0:000  ->Extra kext: Other\AppleALC.kext (v.1.5.4)
13:669  0:000  ->Extra kext: Other\IntelMausi.kext (v.1.0.3)
13:669  0:000  ->Extra kext: Other\SMCSuperIO.kext (v.1.1.8)
13:669  0:000  ->Extra kext: Other\WhateverGreen.kext (v.1.4.4)
13:669  0:000  ->Extra kext: Other\SMCProcessor.kext (v.1.1.8)
13:669  0:000  ->Extra kext: Other\Marvell-Injector.kext (v.1.1)
13:669  0:000  ->Extra kext: Other\VirtualSMC.kext (v.1.1.8)
13:669  0:000  ->Extra kext: Other\USBMap.kext (v.1.0)
13:669  0:000  AddKextsInArray from Off
13:669  0:000  AddKextsInArray from 11
13:669  0:000  AddKextsInArray from 11_normal
13:669  0:000  AddKextsInArray from 11.1
13:669  0:000  AddKextsInArray from 11.1_normal
13:669  0:000  AddKextsInArray from 11.1.0
13:669  0:000  AddKextsInArray from 11.1.0_normal
13:669  0:000  Bridge kext to OC : Path=Lilu.kext
13:675  0:006  info plist path: Kexts\Other\Lilu.kext\Contents\Info.plist
13:680  0:004  assign executable as 'Contents\MacOS\Lilu'
13:680  0:000  Bridge kext to OC : Path=VirtualSMC.kext
13:680  0:000  info plist path: Kexts\Other\VirtualSMC.kext\Contents\Info.plist
13:686  0:006  assign executable as 'Contents\MacOS\VirtualSMC'
13:686  0:000  Bridge kext to OC : Path=WhateverGreen.kext
13:686  0:000  info plist path: Kexts\Other\WhateverGreen.kext\Contents\Info.plist
13:690  0:004  assign executable as 'Contents\MacOS\WhateverGreen'
13:690  0:000  Bridge kext to OC : Path=AppleALC.kext
13:690  0:000  info plist path: Kexts\Other\AppleALC.kext\Contents\Info.plist
13:709  0:019  assign executable as 'Contents\MacOS\AppleALC'
13:709  0:000  Bridge kext to OC : Path=IntelMausi.kext
13:709  0:000  info plist path: Kexts\Other\IntelMausi.kext\Contents\Info.plist
13:712  0:003  assign executable as 'Contents\MacOS\IntelMausi'
13:712  0:000  Bridge kext to OC : Path=SMCProcessor.kext
13:712  0:000  info plist path: Kexts\Other\SMCProcessor.kext\Contents\Info.plist
13:717  0:005  assign executable as 'Contents\MacOS\SMCProcessor'
13:717  0:000  Bridge kext to OC : Path=SMCSuperIO.kext
13:717  0:000  info plist path: Kexts\Other\SMCSuperIO.kext\Contents\Info.plist
13:721  0:003  assign executable as 'Contents\MacOS\SMCSuperIO'
13:721  0:000  Bridge kext to OC : Path=AirportBrcmFixup.kext
13:721  0:000  info plist path: Kexts\Other\AirportBrcmFixup.kext\Contents\Info.plist
13:725  0:003  assign executable as 'Contents\MacOS\AirportBrcmFixup'
13:725  0:000  Bridge kext to OC : Path=Marvell-Injector.kext
13:725  0:000  info plist path: Kexts\Other\Marvell-Injector.kext\Contents\Info.plist
13:728  0:002  Bridge kext to OC : Path=USBMap.kext
13:728  0:000  info plist path: Kexts\Other\USBMap.kext\Contents\Info.plist
13:748  0:020  Load OpenRuntime.efi : Status Success
13:748  0:000  Start OpenRuntime.efi : Status Success
13:748  0:000  OC: OcMiscEarlyInit...
13:757  0:008  OC: Watchdog status is 1
13:759  0:002  OC: OpenCore DBG-061-2020-11-19 is loading in Optional mode (0/0)...
13:762  0:002  OC: Boot timestamp - 2020.11.19 14:58:23
13:764  0:002  OCCPU: MP services threads 4 (enabled 4) - Success
13:766  0:002  OCCPU: MP services Pkg 1 Cores 4 Threads 1 - Success
13:771  0:004  OCCPU: Found Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
13:773  0:002  OCCPU: Signature 306C3 Stepping 3 Model 3C Family 6 Type 0 ExtModel 3 ExtFamily 0 uCode 28
13:775  0:002  OCCPU: EIST CFG Lock 1
13:778  0:002  OCCPU: Discovered CpuFamily 6 CpuModel 60 CpuStepping 3 CpuGeneration 6
13:780  0:002  OCCPU: Ratio Min 8 Max 33 Current 33 Turbo 37 37 36 35
13:883  0:102  TscFrequency 3292371801
13:885  0:002  OCCPU: Detected Apple Processor Type: 06 -> 0605
13:888  0:002  OCCPU: CPUFrequencyFromTSC  3292371801Hz  3292MHz
13:892  0:004  OCCPU: CPUFrequency  3292371801Hz  3292MHz
13:895  0:002  OCCPU: FSBFrequency    99768842Hz    99MHz
13:897  0:002  OCCPU: Pkg 1 Cores 4 Threads 4
13:899  0:002  OC: OcLoadNvramSupport...
13:901  0:002  OC: Current version is DBG-061-2020-11-19
13:904  0:002  OC: OcMiscMiddleInit...
13:906  0:002  OC: LoadHandle 0 with BootProtect in  mode - Unsupported
13:908  0:002  OC: OcLoadUefiSupport...
13:911  0:002  OcAppleEventInstallProtocol
13:913  0:002  InternalCreateQueueEvent
13:918  0:004  EventCreateSimplePointerInstallNotifyEvent
13:920  0:002  InternalSimplePointerInstallNotifyFunction
13:923  0:002  InternalRegisterSimplePointerInterface
13:925  0:002  InternalRegisterSimplePointerInterface
13:927  0:002  InternalRegisterSimplePointerInterface
13:930  0:002  OcOSInfoInstallProtocol
13:932  0:002  OCRTC: OcAppleRtcRamInstallProtocol
13:934  0:002  OCRTC: Wake log is 0x00 0x00   0 0x00
13:937  0:002  OcAppleFbInfoInstallProtocol
13:939  0:002  OC: Loading Apple Secure Boot with Disabled (level 0)
13:944  0:004  OCABC: RTDFRG 1 DEVMMIO 0 NOSU 0 NOVRWR 0 NOSB 0 NOHBMAP 0 SMSLIDE 1 WRUNPROT 1
13:946  0:002  OCABC: FEXITBS 0 PRMRG 0 CSLIDE 1 MSLIDE 0 PRSRV 0 RBMAP 1 VMAP 1 APPLOS 0 RTPERMS 1
13:948  0:002  OCABC: Got rendezvous with OpenRuntime r11
13:950  0:002  OCABC: MAT support is 0
13:953  0:002  OC: RBVR 0 DDBR 0
13:955  0:002  OC: Got 0 drivers
13:958  0:002  OCC: Installing GOP (Unsupported) on ConsoleOutHandle...
13:960  0:002  OC: Requested resolution is 1366x768@0 (max: 0) from 1366x768
13:964  0:004  OCC: Requesting 1366x768@0 (max: 0) resolution, curr 0, total 10
13:967  0:002  OCC: Mode 0 - 1920x1080:1
13:969  0:002  OCC: Mode 1 - 640x480:1
13:971  0:002  OCC: Mode 2 - 800x600:1
13:974  0:002  OCC: Mode 3 - 1024x768:1
13:976  0:002  OCC: Mode 4 - 1280x720:1
13:978  0:002  OCC: Mode 5 - 1280x800:1
13:981  0:002  OCC: Mode 6 - 1280x1024:1
13:983  0:002  OCC: Mode 7 - 1440x900:1
13:985  0:002  OCC: Mode 8 - 1400x1050:1
13:990  0:004  OCC: Mode 9 - 1680x1050:1
13:992  0:002  OCC: No compatible mode for 1366x768@0 (max: 0) resolution
13:994  0:002  OC: Changed resolution to 1366x768@0 (max: 0) from 1366x768 - Not Found
13:997  0:002  OCC: Using builtin text renderer with 1 scale
14:005  0:007  OCC: Install console control (B6075A70/0/0), current - Success
14:007  0:002  OCC: Setup ASCII Output - Success
14:009  0:002  OC: Requested console mode is 0x0 (max: 0) from 
14:012  0:002  OC: Requested not to use audio
14:016  0:004  OC: OcLoadPlatformSupport...
14:019  0:002  OC: OcLoadDevPropsSupport...
14:021  0:002  OC: OcMiscLateInit...
14:023  0:002  OC: Invalid HibernateMode: 
14:025  0:002  OC: Translated HibernateMode  to 0
14:028  0:002  OC: Hibernation detection status is Not Found
14:030  0:002  OC: Panic log does not exist
14:032  0:002  OC: OcLoadKernelSupport...
14:035  0:002  OC: All green, starting boot management...
14:037  0:002  DevicePath = PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,D3B12EBB-E7A0-4AD6-9784-98CB674EDFB6,0x64028,0x1FFB4D00)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,D3386EEE9BA5904FB52C5ACF72DF87B2)/\4BB9C21C-8F09-3F39-BD5F-A151864A2A72\System\Library\CoreServices\boot.efi
14:040  0:003  OCB: Arch filtering B8E8A018(723512)->B8E8A018(723512) caps 4 - Success
14:064  0:024  GetOSVersion: 11.1 (20C5048k)
14:064  0:000  Will not patch boot.efi
14:064  0:000  === [ PatchSmbios ] =============================
14:064  0:000  insert table 9 for dev 0:0
14:064  0:000  insert table 9 for dev 0:1
14:064  0:000  insert table 9 for dev 19:0
14:064  0:000  insert table 9 for dev 0:0
14:064  0:000  Table 11 present, but rewritten for us
14:065  0:000  Not trusting SMBIOS because it's being sneaky...
14:065  0:000  Detected alternating SMBIOS channel banks
14:065  0:000  Channels: 2
14:065  0:000  Interleave: 0 2 1 3 4 6 5 7 8 10 9 11 12 14 13 15 16 18 17 19 20 22 21 23
14:065  0:000  SPD data in use:
14:065  0:000  SmbiosTable.Type17->Vendor = Micron Technology
14:065  0:000  SmbiosTable.Type17->SerialNumber = 0EFA7382
14:065  0:000  SmbiosTable.Type17->PartNumber = 16JTF1G64AZ-1G6E1E1
14:065  0:000  SMBIOS Type 17 Index = 0 => 0 0:
14:065  0:000  BANK 0 DIMM0 1600MHz 8192MB(Ext:0MB)
14:065  0:000  SPD data in use:
14:065  0:000  SmbiosTable.Type17->Vendor = Micron Technology
14:065  0:000  SmbiosTable.Type17->SerialNumber = 0EFA73AC
14:065  0:000  SmbiosTable.Type17->PartNumber = 16JTF1G64AZ-1G6E1E1
14:065  0:000  SMBIOS Type 17 Index = 1 => 1 2:
14:065  0:000  BANK 1 DIMM0 1600MHz 8192MB(Ext:0MB)
14:065  0:000  SMBIOS Type 17 Index = 2 => 2 1:
14:065  0:000  BANK 0 DIMM1 EMPTY
14:065  0:000  SMBIOS Type 17 Index = 3 => 3 3:
14:065  0:000  BANK 1 DIMM1 EMPTY
14:065  0:000  mTotalSystemMemory = 16384
14:065  0:000  NumberOfMemoryDevices = 4
14:065  0:000  Type20[0]->End = 0x7FFFFF, Type17[0] = 2000
14:065  0:000  Type20[1]->End = 0xFFFFFF, Type17[1] = 6000
14:065  0:000  Table 131 is present, CPUType=35
14:065  0:000  Change to: 605
14:065  0:000  === [ PatchACPI ] ===============================
14:065  0:000  Xsdt reallocation done
14:065  0:000  old FADT length=10C
14:065  0:000   SignatureFixup: 0xE35F0827 -> 0x0
14:065  0:000  Found OperationRegion(GNVS, SystemMemory, C9A00C18, ...)
14:065  0:000  Found OperationRegion(MCHT, SystemMemory, FED10000, ...)
14:065  0:000  Found OperationRegion(RCRB, SystemMemory, FED1C000, ...)
14:065  0:000  Found OperationRegion(MCA1, SystemMemory, F7FE0000, ...)
14:065  0:000  Found OperationRegion(MCA1, SystemMemory, F7FE0000, ...)
14:065  0:000  Found OperationRegion(CPSB, SystemMemory, C98F4E18, ...)
14:065  0:000  Found OperationRegion(TMMB, SystemMemory, FED40000, ...)
14:065  0:000  Found OperationRegion(TVID, SystemMemory, FED40F00, ...)
14:065  0:000  Found OperationRegion(TPMR, SystemMemory, FED40000, ...)
14:065  0:000  Found OperationRegion(VECT, SystemMemory, C9F64018, ...)
14:068  0:003  DSDT found in Clover volume: \EFI\CLOVER\ACPI\patched\DSDT.aml
14:069  0:000  Apply DsdtFixMask=0x10000000
14:069  0:000  === [ FixBiosDsdt ] =============================
14:069  0:000  OperationRegion (GNVS...) corrected from 0xD9A00C18 to addr=0xC9A00C18
14:069  0:000    indirect name=SRCB
14:069  0:000    indirect name=SRMB
14:069  0:000    indirect name=SRMB
14:069  0:000  OperationRegion (CPSB...) corrected from 0xD98F5E18 to addr=0xC98F4E18
14:070  0:000  OperationRegion (VECT...) corrected from 0xD9F64018 to addr=0xC9F64018
14:070  0:000  PreCleanup XSDT: count=13, length=140
14:070  0:000  PreCleanup XSDT, corrected XSDT: count=13, length=140
14:070  0:000  === [ ACPIPatchedAML ] ==========================
14:070  0:000  AutoMerge pass 1
14:070  0:000  Unsorted
14:070  0:000  Inserting SSDT.AML from \EFI\CLOVER\ACPI\patched: ignore on pass 1
14:070  0:000  Inserting SSDT-ARPT.aml from \EFI\CLOVER\ACPI\patched: ignore on pass 1
14:070  0:000  === [ ACPIDropTables ] ==========================
14:070  0:000  === [ DropSSDT ] ================================
14:070  0:000  Drop tables from XSDT, SIGN=SSDT TableID= Length=0
14:070  0:000   Table[3]: SSDT  Cpu0Ist  1337 dropped
14:070  0:000   Table[4]: SSDT  CpuPm  2776 dropped
14:070  0:000   Table[5]: SSDT  LakeTiny  455 dropped
14:070  0:000   Table[8]: SSDT  SataTabl  877 dropped
14:070  0:000   Table[9]: SSDT  SaSsdt   13452 dropped
14:070  0:000   Table[10]: SSDT  WMI  26255 dropped
14:070  0:000  === [ ACPIPatchedAML ] ==========================
14:070  0:000  AutoMerge pass 2
14:070  0:000  Unsorted
14:070  0:000  Inserting SSDT.AML from \EFI\CLOVER\ACPI\patched: size=1827 ... Success
14:071  0:001  Inserting SSDT-ARPT.aml from \EFI\CLOVER\ACPI\patched: size=190 ... Success
14:072  0:000  ApicCPUNum=4
14:072  0:000  Cleanup XSDT: count=15, length=156
14:072  0:000  corrected XSDT count=9, length=108
14:072  0:000  === [ RestSetup macOS ] =========================
14:072  0:000  NVidia GFX injection not set
14:072  0:000  Intel HD Graphics 4600 [8086:0412] :: PciRoot(0x0)\Pci(0x2,0x0)
14:072  0:000    ig-platform-id = 0x0d220003
14:072  0:000  Intel GFX revision  = 0x6
14:072  0:000  stringlength = 2160
14:072  0:000  CurrentMode: Width=1920 Height=1080
14:075  0:003  Use origin smbios table type 1 guid.
14:080  0:004  Custom boot screen not used because entry has unset use graphics

 

 

Sorry, I didn't get a notification and saw your post late.

What bdmesg gives is the same as preboot.log.

And that : 

13:669  0:000  AddKextsInArray from Other
13:669  0:000  ->Extra kext: Other\Lilu.kext (v.1.4.9)
13:669  0:000  ->Extra kext: Other\AirportBrcmFixup.kext (v.2.1.1)
13:669  0:000  ->Extra kext: Other\AppleALC.kext (v.1.5.4)
13:669  0:000  ->Extra kext: Other\IntelMausi.kext (v.1.0.3)
13:669  0:000  ->Extra kext: Other\SMCSuperIO.kext (v.1.1.8)
13:669  0:000  ->Extra kext: Other\WhateverGreen.kext (v.1.4.4)
13:669  0:000  ->Extra kext: Other\SMCProcessor.kext (v.1.1.8)
13:669  0:000  ->Extra kext: Other\Marvell-Injector.kext (v.1.1)
13:669  0:000  ->Extra kext: Other\VirtualSMC.kext (v.1.1.8)
13:669  0:000  ->Extra kext: Other\USBMap.kext (v.1.0)

is not the injection order. Look further down, lines coming from OC.

 

 

 

Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted
19 minutes ago, Jief_Machak said:

Sorry, I didn't get a notification and saw your post late.

What bdmesg gives is the same as preboot.log.

And that : 


13:669  0:000  AddKextsInArray from Other
13:669  0:000  ->Extra kext: Other\Lilu.kext (v.1.4.9)
13:669  0:000  ->Extra kext: Other\AirportBrcmFixup.kext (v.2.1.1)
13:669  0:000  ->Extra kext: Other\AppleALC.kext (v.1.5.4)
13:669  0:000  ->Extra kext: Other\IntelMausi.kext (v.1.0.3)
13:669  0:000  ->Extra kext: Other\SMCSuperIO.kext (v.1.1.8)
13:669  0:000  ->Extra kext: Other\WhateverGreen.kext (v.1.4.4)
13:669  0:000  ->Extra kext: Other\SMCProcessor.kext (v.1.1.8)
13:669  0:000  ->Extra kext: Other\Marvell-Injector.kext (v.1.1)
13:669  0:000  ->Extra kext: Other\VirtualSMC.kext (v.1.1.8)
13:669  0:000  ->Extra kext: Other\USBMap.kext (v.1.0)

is not the injection order. Look further down, lines coming from OC.

 

 

 

Everything work normal whitout  injection order. 373695373.png.92c4e8bc0b2a38ac5cbc8da7a204ae44.png

Link to comment
Share on other sites
maclinuxG4
maclinuxG4
Posted
Posted

the order of loaded kext is herafter 

13:669  0:000  AddKextsInArray from 11.1.0
13:669  0:000  AddKextsInArray from 11.1.0_normal
13:669  0:000  Bridge kext to OC : Path=Lilu.kext
13:675  0:006  info plist path: Kexts\Other\Lilu.kext\Contents\Info.plist
13:680  0:004  assign executable as 'Contents\MacOS\Lilu'
13:680  0:000  Bridge kext to OC : Path=VirtualSMC.kext
13:680  0:000  info plist path: Kexts\Other\VirtualSMC.kext\Contents\Info.plist
13:686  0:006  assign executable as 'Contents\MacOS\VirtualSMC'
13:686  0:000  Bridge kext to OC : Path=WhateverGreen.kext
13:686  0:000  info plist path: Kexts\Other\WhateverGreen.kext\Contents\Info.plist
13:690  0:004  assign executable as 'Contents\MacOS\WhateverGreen'
13:690  0:000  Bridge kext to OC : Path=AppleALC.kext
13:690  0:000  info plist path: Kexts\Other\AppleALC.kext\Contents\Info.plist
13:709  0:019  assign executable as 'Contents\MacOS\AppleALC'
13:709  0:000  Bridge kext to OC : Path=IntelMausi.kext
13:709  0:000  info plist path: Kexts\Other\IntelMausi.kext\Contents\Info.plist
13:712  0:003  assign executable as 'Contents\MacOS\IntelMausi'
13:712  0:000  Bridge kext to OC : Path=SMCProcessor.kext
13:712  0:000  info plist path: Kexts\Other\SMCProcessor.kext\Contents\Info.plist
13:717  0:005  assign executable as 'Contents\MacOS\SMCProcessor'
13:717  0:000  Bridge kext to OC : Path=SMCSuperIO.kext
13:717  0:000  info plist path: Kexts\Other\SMCSuperIO.kext\Contents\Info.plist
13:721  0:003  assign executable as 'Contents\MacOS\SMCSuperIO'
13:721  0:000  Bridge kext to OC : Path=AirportBrcmFixup.kext
13:721  0:000  info plist path: Kexts\Other\AirportBrcmFixup.kext\Contents\Info.plist
13:725  0:003  assign executable as 'Contents\MacOS\AirportBrcmFixup'
13:725  0:000  Bridge kext to OC : Path=Marvell-Injector.kext
13:725  0:000  info plist path: Kexts\Other\Marvell-Injector.kext\Contents\Info.plist
13:728  0:002  Bridge kext to OC : Path=USBMap.kext
13:728  0:000  info plist path: Kexts\Other\USBMap.kext\Contents\Info.plist
Link to comment
Share on other sites
PG7
PG7
Posted
Posted (edited)

clover r5126

 

I come here to post two problems that I encounter and can be solved (at least I think)

 

- I use an Atheros ar9285 Wifi and then I got the kext here

 

- I tested it a lot and I even managed to get it to work, but it is incomprehensible to know why it works one hour and then it may not work!

 

- I tested with OpenCore and with FUnciona all the time! and that's until I can get it to work on Clover

 

- did some tests and my result is the order of loading the kext by Clover
if we manage to apply a correct order the Wifi works Normal with Clover

 

- I have the same problem with a touchpad kext for ALPS ps2 pro Dell
in OpenCore it loads and works normal, in Clover it happens the same as with the Wifi kext (in previous versions of macOS it works without problems)

 

- I got a debug and a preboot where everything is working with Clover and another where NAO works
for me the order of loading the kext is the problem

 

- I leave the debugs for you to analyze and certainly advise me the indicated way to do it

 

- I tried to install the kext with Chris Droplet in L / E but it doesn't work

 

 since already Thanks to all and good weekend

preboot-funciona o touchpad com a boa kext.log

debug-funciona o touchpad com a boa kext.log

debug-Atheros+touchpad OK.log

preboot-Atheros+touchpad OK.log

Edited by PG7
  • Like 2
Link to comment
Share on other sites
PG7
PG7
Posted
Posted
3 minutes ago, iCanaro said:

have you tried to put in the other folder the kext that needs to be uploaded first and in 11 the other?!

 

yes I did, I forgot to mention it!

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
On 11/20/2020 at 6:49 PM, mifjpn said:

Thank you as always

It seems that there was a person who tried it at a Japanese forum.
The following is automatic translation.
------
Anonymous
The guests

It's not directly related to Big Sur, but I think Clover will be updated to 5126.
I will write it here.
When I put Big Sur + Clover 5126 in Thinkpad X240, I modified Voodoo PS2 for X240.
The Controller is loaded, but the Trackpad under it is no longer loaded.
In the end, the cause was that "/ EFI ~ kext / Contents / MacOS / file name" was long.

(NG)
VoodooPS2Controller_ThinkpadX240.kext / Contents / PlugIns / VoodooPS2Trackpad_ThinkpadX240.kext
(OK)
VoodooPS2Controller_X240.kext / Contents / PlugIns / VoodooPS2Trackpad_X240.kext

When the file name is shortened little by little, it seems NG if the length of / EFI ~ is 140 characters or more.
No problem with Clover5107, no problem with the original Voodoo PS2 (because the file name is short)
So I spent a whole day investigating.
I don't think anyone would give it such a long file name, but this is just an example.
------

Long names related to Voodoo seem to need attention.
I will tell the story of Jief to Japan.

Thank you,

Tell Japan it’s fixed.

thanks.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites
jlrycm
jlrycm
Posted
Posted
On 11/20/2020 at 2:00 PM, Matgen84 said:


@jlrycm In the info.plist, It seems that Apple has replaced Asmedia2142 by Asmedia3142 in some lines. Maybe it's the reason why you've a problem with your card. Unfortunately, I don't know how to make a patch or a specific SSDT, sorry :)

@iCanaro, @Matgen84, I checked with the vendor and this is what they responded.

C388ED7F-AA59-4280-A309-8F5EF8829598.png

  • Like 2
Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted

to me it comes to think that it is more a problem of your PCI card in combination with the motherboard, have you tried to change pci slots where inserted?
On my Z370 is a built-in chip on the motherboard and on big sur it is properly recognized

from ioreg on big sur works with the driver asmedia 3142 but in reality it's 2142

2114456770_Schermata2020-11-21alle23_44_48.thumb.jpg.dc07306e38ea1b93ce2319ef59405064.jpg

  • Like 2
  • Haha 1
Link to comment
Share on other sites
yapan4
yapan4
Posted
Posted (edited)

Hi, all.

Now Clover is stable and is used as the main bootloader to install macOS and to run an already installed system.
Thank you developers and all for assist.
But x299 and c422 users have a problem. I'm not sure if this is Clover's problem, because Open Core users also report the same or similar problem. There are also isolated reports from other chipsets but mostly it's the x299 and my c422 machine.
This is a stop on a black screen with a thick horizontal cursor and POST code 97 after reboot. The reset button does not help. Only the power button helps.
Problem has been present steadily since Clover version 5123 - 5124 (exactly unknown) and on the Big Sur betas and release.
Apeares after the user, bootloader or system has made any changes to the NVRAM (my guesses).

Hope somebody known solution. Or need developers intervention?

 

Thank You and sorry my google translated English.

yapan4_C422_EFI.zip

yapan4_C422_debug.log

Edited by yapan4
  • Sad 1
Link to comment
Share on other sites
jlrycm
jlrycm
Posted
Posted
13 hours ago, iCanaro said:

to me it comes to think that it is more a problem of your PCI card in combination with the motherboard, have you tried to change pci slots where inserted?
On my Z370 is a built-in chip on the motherboard and on big sur it is properly recognized

from ioreg on big sur works with the driver asmedia 3142 but in reality it's 2142

2114456770_Schermata2020-11-21alle23_44_48.thumb.jpg.dc07306e38ea1b93ce2319ef59405064.jpg

@iCanaro, thanks for your feedback. Unfortunately I only have one PCIEX4 slot available for this card. I ordered a Startech card which uses the ASMEDIA 3142 and claims to be supported in Big Sur.  

  • Like 2
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted
3 hours ago, yapan4 said:

Hi, all.

Now Clover is stable and is used as the main bootloader to install macOS and to run an already installed system.
Thank you developers and all for assist.
But x299 and c422 users have a problem. I'm not sure if this is Clover's problem, because Open Core users also report the same or similar problem. There are also isolated reports from other chipsets but mostly it's the x299 and my c422 machine.
This is a stop on a black screen with a thick horizontal cursor and POST code 97 after reboot. The reset button does not help. Only the power button helps.
Problem has been present steadily since Clover version 5123 - 5124 (exactly unknown) and on the Big Sur betas and release.
Apeares after the user, bootloader or system has made any changes to the NVRAM (my guesses).

Hope somebody known solution. Or need developers intervention?

 

Thank You and sorry my google translated English.

yapan4_C422_EFI.zip

yapan4_C422_debug.log

Your problem is likely to come from
FakeSMC.kext \ Contents \ PlugIns \ LPCSensors.kext
\ FakeSMC.kext \ Contents \ PlugIns \ GPUSensors.kext
\ FakeSMC.kext \ Contents \ PlugIns \ CPUSensors.kext
FakeSMC.kext \ Contents \ PlugIns \ ACPISensors.kext
This is a version that does not support bigsur catalina.blaaaaa.
Well, you should use the slide version ..

3 hours ago, yapan4 said:
2 hours ago, jlrycm said:

@iCanaro, thanks for your feedback. Unfortunately I only have one PCIEX4 slot available for this card. I ordered a Startech card which uses the ASMEDIA 3142 and claims to be supported in Big Sur.  

Need to patch it too, DSDT should work.

 

  • Like 1
Link to comment
Share on other sites
yapan4
yapan4
Posted
Posted
49 minutes ago, naiclub said:

Your problem is likely to come from
FakeSMC.kext \ Contents \ PlugIns \ LPCSensors.kext
\ FakeSMC.kext \ Contents \ PlugIns \ GPUSensors.kext
\ FakeSMC.kext \ Contents \ PlugIns \ CPUSensors.kext
FakeSMC.kext \ Contents \ PlugIns \ ACPISensors.kext
This is a version that does not support bigsur catalina.blaaaaa.
Well, you should use the slide version ..

@naiclub

I already tried different FakeSMC and VirtualSMC kexts versions, do not helped.

Note: - This Is Stop during machine boot, not Clover or Big Sur,  hackintosh cannot finalise POST-process after reboot. And it doesn't come to the menu of a choice of a disk or Clover's GUI.

Thank you

yapan4_C422_with_Slices_FakeSMC_debug.log

  • Like 1
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted
26 minutes ago, yapan4 said:

@naiclub

I already tried different FakeSMC and VirtualSMC kexts versions, do not helped.

Note: - This Is Stop during machine boot, not Clover or Big Sur,  hackintosh cannot finalise POST-process after reboot. And it doesn't come to the menu of a choice of a disk or Clover's GUI.

Thank you

yapan4_C422_with_Slices_FakeSMC_debug.log

CtlnaAHCIPort.kext<------------- Have or not

  • Like 2
Link to comment
Share on other sites
yapan4
yapan4
Posted
Posted (edited)

Thanks, @naiclub

I will test your EFI Folder and do report later...

 

 

Hmm, Bootstrap with Clover, it is new for me...

 

 

Update: 

With your EFI Folder Big Sur boot Ok. I did not make any changes except set SetupVirtualMap Quirk to No (that is necessary for x299/c422 motherboards).

Black screen with horizontal cursor and POST code 97 went nowhere:(

debug.log

Edited by yapan4
Link to comment
Share on other sites
Deadpool
Deadpool
Posted
Posted (edited)

Hi @Jief_Machak / @Slice ,

I tried a fresh new install of big sur with clover 5126 2 days ago last commit version (usb created with apple official createinstallmedia method). The installation goes well but when it arrives on the last part (the boot where it should start the gui where it let you configure your username, password, internet connection general preferences etc..) it stops to a never end error: too many corpses being created.

 

I have found this solution on the web, but it seems that does not work on big sur. Could you please indicate me if the command here below should be maybe converted to a Big Sur new folder structure / path or how to solve the problem in a different way? Thank you in advance!

 

Restart your Mac and hold down Command-R tostart up from macOS Recovery.

  
If the startup drive has FileVault turned on, open Disk Utility and proceed with the next step. If FileVault is off, skip to step 5.

  
Select the startup drive and click Mount in the Disk Utility toolbar. When prompted, select a login name and enter the password. Then click Unlock to mount the startup drive.

  
Quit Disk Utility.

  
Choose Utilities > Terminal from the menu bar.

  
Type this command in Terminal:cd /Volumes/Macintosh\ HD/var/db/caches/opendirectory/
Modify the command to reflect the name of the startup volume if it's not Macintosh HD. Remember to use an escape character \ before each white space in the command path.

  
Press Return.

  
Type this command in Terminal:mv ./mbr_cache ./mbr_cache-old
The mv Terminal command is safer than the rm command. Errant white space in an rm command can destroy the user's data.

  
Press Return.

  
Quit Terminal.

  
Choose Apple () menu > Restart.

 

 
The first startup after running these commands takes longer than usual as the cache is recreated. Subsequent startups will take the normal amount of time.

Edited by Deadpool
  • Like 2
Link to comment
Share on other sites
jlrycm
jlrycm
Posted
Posted
10 hours ago, naiclub said:

Your problem is likely to come from
FakeSMC.kext \ Contents \ PlugIns \ LPCSensors.kext
\ FakeSMC.kext \ Contents \ PlugIns \ GPUSensors.kext
\ FakeSMC.kext \ Contents \ PlugIns \ CPUSensors.kext
FakeSMC.kext \ Contents \ PlugIns \ ACPISensors.kext
This is a version that does not support bigsur catalina.blaaaaa.
Well, you should use the slide version ..

 

@naiclub, appreciate your feedback. If patching is feasible, could you advise in which way / suggest a good guide to follow  in order to make my USB 3.1 external card bus to work?

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
12 hours ago, yapan4 said:

Thanks, @naiclub

I will test your EFI Folder and do report later...

 

 

Hmm, Bootstrap with Clover, it is new for me...

 

 

Update: 

With your EFI Folder Big Sur boot Ok. I did not make any changes except set SetupVirtualMap Quirk to No (that is necessary for x299/c422 motherboards).

Black screen with horizontal cursor and POST code 97 went nowhere:(

debug.log

 

Hi @yapan4

Bootstrap.efi is no more use by Clover. This driver was used when Jief made the first attempts to integrate opencore, in September. It can be deleted :) Have a look to CloverPKG you don't see it.

  • Like 3
  • Thanks 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...