Jump to content
30960 posts in this topic

Recommended Posts

@jsl2000patches are not mine, I have converted only the naming from opencore to clover following @Slicenaming in clover development thread (by the way we miss a pair of it to be complete)

 

I am using 17h patches..and maybe (I am not sure) they are not the same for your FX CPU...

Edited by Guest

Nice support, thanks.

I had this idea when there was this big mess about Quirks section name and place in config.plist. Some people forgot to rename it and that was ignored completely.

This will be integrated to Clover, so people should start using it ! :yes:

  • Like 5
24 minutes ago, fabiosun said:

@jsl2000patches are not mine, I have converted only the naming from opencore to clover following @Slicenaming in clover development thread (by the way we miss a pair of it to be complete)

 

I am using 17h patches..and maybe (I am not sure) they are not the same for your FX CPU...

17h patch for Ryzen and 15h-16h for FX-8x00/6x00.

I have applied these different respective patches converted from OpenCore format, but still in vain.

9 minutes ago, MacKonsti said:

Please @Jief_Machak kindly fix spelling "Unknow" to "Unknown" :D Is there a repo to get alers of new versions? Or you will share theme here only? Thank you again for your tool.

Done !

Thanks for the report.

I will be integrated into Clover, and, I suppose, into the package... In the meantime, probably here.

Edited by Jief_Machak
  • Like 2
  • Thanks 1
20 minutes ago, Jief_Machak said:

I had this idea when there was this big mess about Quirks section name and place in config.plist.

Looking forward to checking this utility in next Clover update. Thank you mate.

 

But I am a little discouraged with these new "Quirks"... This is a huge change and messes a lot with stable Clover boots of the past... Removing AptioMemoryFix doesn't tell us what are the respective Quirks to set. Are these changes really only Big Sur focused?

 

I personally cannot boot any Catalina hack. Dortania guide(s) have these "Clover" Quirks split in 2 places, I checked twice Coffee Lake (as there's no Whiskey Lake for my Lenovo S145) one by one setting, and still cannot boot successfully :( Not even sure if my boot is mixed with previous <key>KernelAndKextPatches</key> as @Slice explained in his post here.

 

Are there corresponding Quirk values that AptioMemoryFix was using before, so we can get them set in Quirks section of config, does anyone know? Thank you.

  • Thanks 1
5 minutes ago, MacKonsti said:

Looking forward to checking this utility in next Clover update. Thank you mate.

 

But I am a little discouraged with these new "Quirks"... This is a huge change and messes a lot with stable Clover boots of the past... Removing AptioMemoryFix doesn't tell us what are the respective Quirks to set. Are these changes really only Big Sur focused?

 

I personally cannot boot any Catalina hack. Dortania guide(s) have these "Clover" Quirks split in 2 places, I checked twice Coffee Lake (as there's no Whiskey Lake for my Lenovo S145) one by one setting, and still cannot boot successfully :( Not even sure if my boot is mixed with previous <key>KernelAndKextPatches</key> as @Slice explained in his post here.

 

Are there corresponding Quirk values that AptioMemoryFix was using before, so we can get them set in Quirks section of config, does anyone know? Thank you.

Yes it's mainly booter quirks and kernel quirks from OC that were united under Quirks section in Clover.

Does this validator report any warnings or error. Maybe your quirks are in the wrong place, and have no effects? Clean all the warnings and errors.

Sorry I can't help with which value the quirks should be for your platform. You may find someone here. Also look for successful OC configuration for a similar platform.

  • Like 1
  • Thanks 1

Booting to Pre-boot volume works fine and booting to the regular system volume does generate a KP. The KP can be found in the quote below. 

 

Well done Jief_Machak and Slice. 

 

Quote

panic(cpu 0 caller 0xffffff80146bd8ea): "Rooting from the live fs of a sealed volume is not allowed on a RELEASE build\n"com.apple./AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/apfs/apfs-1677.40.51.201.1/kext/apfs_vfsops.c:2011
Backtrace (CPU 0), Frame : Return Address
0xffffffa054a42ea0 : 0xffffff80116b666d 
0xffffffa054a42ef0 : 0xffffff80117f8f93 
0xffffffa054a42f30 : 0xffffff80117e95ca 
0xffffffa054a42f80 : 0xffffff801165ba2f 
0xffffffa054a42fa0 : 0xffffff80116b5f0d 
0xffffffa054a430c0 : 0xffffff80116b61f8 
0xffffffa054a43130 : 0xffffff8011eb792a 
0xffffffa054a431a0 : 0xffffff80146bd8ea 
0xffffffa054a43990 : 0xffffff80146c6d70 
0xffffffa054a439c0 : 0xffffff801193cb20 
0xffffffa054a43b40 : 0xffffff8011bf9883 
0xffffffa054a43e70 : 0xffffff80116e3e83 
0xffffffa054a43fa0 : 0xffffff801165b13e 
      Kernel Extensions in backtrace:
         com.apple.filesystems.apfs(1677.40.51)[82FE49D0-2A08-3128-B5A7-D0D3BF99D28D]com.apple.0xffffff8014643000-com.apple.driver.0xffffff80147a6fff
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[AB65643D-1BE4-35C1-B566-2898844DADE0]com.apple.0xffffff8012a34000-com.apple.driver.0xffffff8012a3dfff
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[7A75BFCC-F40A-3991-8D3D-BA843F37A7F8]com.apple.0xffffff8012a47000-com.apple.driver.0xffffff8012a4cfff
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[B69C1AF1-494E-3321-B1FE-1EC42C6F2A5E]com.apple.0xffffff8012e82000-com.apple.driver.0xffffff8012e88fff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[63B7DD4D-C3CC-311C-9FD7-30032779F1F8]com.apple.0xffffff801410f000-com.apple.driver.0xffffff8014120fff
            dependency: com.apple.kec.corecrypto(1.0)[B1A179FD-27C2-3F5B-A97B-267774ECA9DF]com.apple.0xffffff80147d4000-com.apple.driver.0xffffff8014860fff
            dependency: com.apple.security.AppleImage4(3.0.0)[9F4F723F-52EE-3B0F-AB02-9755CCEB7DF7]com.apple.0xffffff8012aa9000-com.apple.driver.0xffffff8012ab8fff

Process name corresponding to current thread: kernel_task
Boot args: agdpmod=pikera shikigva=160 shiki-id=Mac-7BA5B2D9E42DDD94 

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 20.1.0: Wed Oct  7 21:17:40 PDT 2020; root:xnu-7195.40.137.201.1~1/RELEASE_X86_64
Kernel UUID: D5AE727A-F8F2-31EE-B874-4E907B0C5115
KernelCache slide: 0x0000000011400000
KernelCache base:  0xffffff8011600000
Kernel slide:      0x0000000011410000
Kernel text base:  0xffffff8011610000
__HIB  text base: 0xffffff8011500000
System model name: iMac15,1 (Mac-42FD25EABCABB274)
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization
Hibernation exit count: 0

System uptime in nanoseconds: 637629113
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x0000000026017764
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x0000000cbdadaab0 0x0000000000000000
last started kext at 565014267: com.apple.driver.AppleFileSystemDriver    3.0.1 (addr 0xffffff8012a68000, size 4096)
loaded kexts:
com.insanelymac.IntelMausiEthernet    2.5.1d1
ru.joedm.SMCSuperIO    1.1.7
org.rehabman.driver.FakePCIID.XHCIMux    1.3.15
org.rehabman.driver.FakePCIID    1.3.15
as.vit9696.SMCProcessor    1.1.7
as.vit9696.VirtualSMC    1.1.7
com.rehabman.driver.USBInjectAll    0.7.5
as.lvs1974.HibernationFixup    1.3.6
as.vit9696.AppleALC    1.5.3
as.vit9696.WhateverGreen    1.4.3
as.vit9696.Lilu    1.4.8
com.apple.driver.AppleFileSystemDriver    3.0.1
com.apple.filesystems.tmpfs    1
com.apple.filesystems.apfs    1677.40.51
com.apple.filesystems.hfs.kext    556.40.4
com.apple.BootCache    40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
com.apple.private.KextAudit    1.0
com.apple.driver.AppleAHCIPort    346
com.apple.driver.AirPort.BrcmNIC    1400.1.1
com.apple.driver.AppleACPIButtons    6.1
com.apple.driver.AppleACPIEC    6.1
com.apple.driver.AppleRTC    2.0
com.apple.driver.AppleHPET    1.8
com.apple.driver.AppleSMBIOS    2.1
com.apple.driver.AppleAPIC    1.7
com.apple.AppleSystemPolicy    2.0.0
com.apple.nke.applicationfirewall    310
com.apple.iokit.IOKitRegistryCompatibility    1
com.apple.iokit.EndpointSecurity    1
com.apple.driver.AppleBSDKextStarter    3
com.apple.iokit.IOSurface    289.3
com.apple.filesystems.hfs.encodings.kext    1
com.apple.driver.AppleXsanScheme    3
com.apple.iokit.IOAHCIBlockStorage    332
com.apple.driver.usb.AppleUSBHostPacketFilter    1.0
com.apple.iokit.IOUSBFamily    900.4.2
com.apple.iokit.IOAHCIFamily    294
com.apple.iokit.IO80211Family    1200.12.2b1
com.apple.iokit.IOSkywalkFamily    1
com.apple.driver.mDNSOffloadUserClient    1.0.1b8
com.apple.driver.corecapture    1.0.4
com.apple.driver.AppleEFINVRAM    2.1
com.apple.driver.usb.AppleUSBEHCIPCI    1.2
com.apple.driver.usb.AppleUSBEHCI    1.2
com.apple.driver.AppleIntelLpssGspi    3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI    1.2
com.apple.driver.usb.AppleUSBXHCI    1.2
com.apple.iokit.IOSMBusFamily    1.1
com.apple.iokit.IOHIDFamily    2.0.0
com.apple.driver.AppleEFIRuntime    2.1
com.apple.security.AppleImage4    3.0.0
com.apple.iokit.IOTimeSyncFamily    900.11
com.apple.iokit.IONetworkingFamily    3.4
com.apple.driver.DiskImages    493.0.0
com.apple.iokit.IOBluetoothFamily    8.0.0d60
com.apple.iokit.IOReportFamily    47
com.apple.iokit.IOBluetoothPacketLogger    8.0.0d60
com.apple.security.quarantine    4
com.apple.security.sandbox    300.0
com.apple.kext.AppleMatch    1.0.0d1
com.apple.iokit.CoreAnalyticsFamily    1
com.apple.driver.AppleSSE    1.0
com.apple.driver.AppleKeyStore    2
com.apple.driver.AppleUSBTDM    511.40.7
com.apple.iokit.IOUSBMassStorageDriver    184.40.6
com.apple.iokit.IOSCSIBlockCommandsDevice    436.40.6
com.apple.iokit.IOStorageFamily    2.1
com.apple.iokit.IOSCSIArchitectureModelFamily    436.40.6
com.apple.driver.AppleMobileFileIntegrity    1.0.5
com.apple.kext.CoreTrust    1
com.apple.driver.AppleFDEKeyStore    28.30
com.apple.driver.AppleEffaceableStorage    1.0
com.apple.driver.AppleCredentialManager    1.0
com.apple.driver.KernelRelayHost    1
com.apple.iokit.IOUSBHostFamily    1.2
com.apple.driver.AppleUSBHostMergeProperties    1.2
com.apple.driver.usb.AppleUSBCommon    1.0
com.apple.driver.AppleBusPowerController    1.0
com.apple.driver.AppleSEPManager    1.0.1
com.apple.driver.IOSlaveProcessor    1
com.apple.driver.AppleACPIPlatform    6.1
com.apple.driver.AppleSMC    3.1.9
com.apple.iokit.IOPCIFamily    2.9
com.apple.iokit.IOACPIFamily    1.4
com.apple.driver.watchdog    1
com.apple.kec.pthread    1
com.apple.kec.corecrypto    1.0
com.apple.kec.Libm    1

 

1 hour ago, kushwavez said:

Happened for me when tried to install from USB. Avoid normal partitions, always use Preboots when installing. I only could fix that by start the whole installation again.

I used preboot as a starter but it immediately restarted.
Need to go to the main partitions Is like a video posted

9 hours ago, fabiosun said:
10 hours ago, SavageAUS said:

 

@SavageAUSpatches are good

have you posted some screen of your hang in BS?

have you posted that log?

Your Catalina working config could work easily with a minimal difference in quirk part

I have posted the panic in the Big Sur thread I believe, i will update this post with an image and hopefully a log soon. 

 

Spoiler

IMG_0652.thumb.jpg.460f689ac86df6e706907089a141e8ee.jpg

 

 

debug.log

Edited by SavageAUS

before goodnight
KernelToPatch for the operation of AMD systems
I "enjoyed" working a bit using the existing patches and:

26-patch config that starts Catalina and Mojave
29-patch config that starts Catalina and BS
38-patch config that starts Catalina and BS
to be converted oc to Clover
for me there is no shortage of field
only matchos is missing because to make the patches for bs work you don't have to define the matchos and leave the field blank

developers, so far you have done a great job, but to make AMD users enjoy multiboot systems better, matchos with Big Sur need to work properly

anyway thank you @Slice @Jief_Machak

  • Haha 1
Just now, iCanaro said:

before goodnight
KernelToPatch for the operation of AMD systems
I "enjoyed" working a bit using the existing patches and:

26-patch config that starts Catalina and Mojave
29-patch config that starts Catalina and BS
38-patch config that starts Catalina and BS
to be converted oc to Clover
for me there is no shortage of field
only matchos is missing because to make the patches for bs work you don't have to define the matchos and leave the field blank

developers, so far you have done a great job, but to make AMD users enjoy multiboot systems better, matchos with Big Sur need to work properly

anyway thank you @Slice @Jief_Machak

Can you share these patch .plists 

6 minutes ago, Jief_Machak said:

I will very soon update Clover to show Preboot and NOT main partitions for BigSur.

Make sure you didn't force hide Preboot in config.plist.

I don’t mind using preboot until Big Sur is officially released as this may just be a beta thing. 

  • Like 1
Just now, Jief_Machak said:

Wouldn't be surprise it'll stay. I'm pretty sure Apple doesn't support booting on main partition.

What is the problem to always boot on Preboot ?

No problem, just not what I’m used too that’s all. 

  • Thanks 1
1 hour ago, Jief_Machak said:

Wouldn't be surprise it'll stay. I'm pretty sure Apple doesn't support booting on main partition.

What is the problem to always boot on Preboot ?

Older systems has no it.

  • Thanks 1
1 hour ago, Jief_Machak said:

Wouldn't be surprise it'll stay. I'm pretty sure Apple doesn't support booting on main partition.

What is the problem to always boot on Preboot ?

 

I cannot comment on what is the correct behavior to boot the main partition or the pre-boot partition, you know this much better than I. I'm just a regular macOS user :)

 

I noticed that if I go to "Startup Disk" I cannot select the pre-boot volume, and when I select my macOS installation and press restart there will be a KP. So it seems that it does not try to boot from pre-boot, because then it should work without KP.

 

Clover has always worked with selecting the main macOS partition in the boot menu and OC can boot from main macOS partition as well.

 

Just my 2 cents.

 

EDIT: Forgot to say that in the earlier betas we could boot through selecting main partition in Clover as well. I think beta 9 and earlier worked fine that way.

 

Edited by Common_Sense
  • Like 1
8 minutes ago, Slice said:

May be set in config.plist something like Boot->AlwaysPreboot=YES/NO ?

 

@Slice Why not, but only for Big Sur, I suppose. Because previous macOS boot fine from main partition. If I understand well.

Edited by Matgen84
  • Thanks 1
×
×
  • Create New...