Jief_Machak Posted October 5, 2020 Share Posted October 5, 2020 45 minutes ago, Jief_Machak said: Yes, to still be able to load Windows or Linux... macOS cannot be started without kexts. Panic removed. 1 Link to comment Share on other sites More sharing options...
Jief_Machak Posted October 5, 2020 Share Posted October 5, 2020 (edited) 2 hours ago, pico joe said: 16 hours ago, Jief_Machak said: Interesting and good to know : if it hangs when you boot OpenCore (It stops after Watchdog status is 0, HDD led is blinking constantly), it maybe because of your EFI partition full. In my case, it was full of OC logs. yes .. hang with OC when switch from clover I've opened an issue on their bug tracker... Edited October 5, 2020 by Jief_Machak Link to comment Share on other sites More sharing options...
JorgeMax Posted October 5, 2020 Share Posted October 5, 2020 I'm doing a new installation of Big Sur, but I'm stuck in a repetition with a word "SIGILL" and also "SIGABRT" I’ve tried looking around this in other topics, but I haven’t found Thank you for your help Link to comment Share on other sites More sharing options...
naiclub Posted October 5, 2020 Share Posted October 5, 2020 (edited) 48 minutes ago, JorgeMax said: I'm doing a new installation of Big Sur, but I'm stuck in a repetition with a word "SIGILL" and also "SIGABRT" I’ve tried looking around this in other topics, but I haven’t found Thank you for your help You need to open the hidden drive (Preboot). Then choose this drive to boot, good luck edit..After that, the installation is complete if complete Preboot drives will disappear as normal drives. Completed the installation process. I've already said it on this page. หน้านี้ Edited October 5, 2020 by naiclub Link to comment Share on other sites More sharing options...
JorgeMax Posted October 5, 2020 Share Posted October 5, 2020 1 hour ago, naiclub said: You need to open the hidden drive (Preboot). Then choose this drive to boot, good luck edit..After that, the installation is complete if complete Preboot drives will disappear as normal drives. Completed the installation process. I've already said it on this page. หน้านี้ I've already gone through this step It already starts with the partition with the given name of the example system: "BigSurTest" The step is to finish and go to the final settings Spoiler Link to comment Share on other sites More sharing options...
naiclub Posted October 5, 2020 Share Posted October 5, 2020 (edited) 1 hour ago, JorgeMax said: I've already gone through this step It already starts with the partition with the given name of the example system: "BigSurTest" The step is to finish and go to the final settings Hide contents Ok you use oc boot or clover if using clover Look at the picture I attached (preboot), if available, delete it And save the clover file Spoiler Edited October 5, 2020 by naiclub Link to comment Share on other sites More sharing options...
JorgeMax Posted October 5, 2020 Share Posted October 5, 2020 2 hours ago, naiclub said: Ok you use oc boot or clover if using clover Look at the picture I attached (preboot), if available, delete it And save the clover file Reveal hidden contents Even making it visible, the same situation occurs Thank you for your help Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 5, 2020 Share Posted October 5, 2020 2 minutes ago, JorgeMax said: Even making it visible, the same situation occurs Thank you for your help I had the same issue once, I erased the whole disk and before starting the installation process I booted with OC and cleared nvram and then rebooted the system from the pre-released version of 5123 and then the installation went very smoothly. 1 Link to comment Share on other sites More sharing options...
naiclub Posted October 5, 2020 Share Posted October 5, 2020 7 minutes ago, JorgeMax said: Even making it visible, the same situation occurs Thank you for your help So you haven't completed the installation process. I said all You have to boot with the pre-boot drive until you reach the setting selection page to login. Link to comment Share on other sites More sharing options...
naiclub Posted October 5, 2020 Share Posted October 5, 2020 (edited) 15 minutes ago, Cyberdevs said: I had the same issue once, I erased the whole disk and before starting the installation process I booted with OC and cleared nvram and then rebooted the system from the pre-released version of 5123 and then the installation went very smoothly. I was used to being the type he specified. But I don't see the need to delete the new drive. Just select the correct boot drive. Do not try to enter the main drive that has the name of that drive. edit..bigsur this version install at least 3-4 rounds Unlike the previous version Edited October 5, 2020 by naiclub Link to comment Share on other sites More sharing options...
JorgeMax Posted October 5, 2020 Share Posted October 5, 2020 10 minutes ago, naiclub said: So you haven't completed the installation process. I said all You have to boot with the pre-boot drive until you reach the setting selection page to login. Yes, this problem is after the "preboot" process. Then it restarts and I see the disc with the name given there in the format of the drive 14 minutes ago, Cyberdevs said: I had the same issue once, I erased the whole disk and before starting the installation process I booted with OC and cleared nvram and then rebooted the system from the pre-released version of 5123 and then the installation went very smoothly. I left the other units with the other systems plugged in, like a second installation of Big Sur, Mojave and windows Is it a conflict with Big Sur already installed? Check here Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 5, 2020 Share Posted October 5, 2020 11 minutes ago, JorgeMax said: I left the other units with the other systems plugged in, like a second installation of Big Sur, Mojave and windows Is it a conflict with Big Sur already installed? Check here No I don't think so. unless they are on the same drive which might be the cause for the issue that you are having. This issue isn't related to Clover and most likely is related to your specific setup (EFI folder and settings) so I suggest to make a new topic and continue the troubleshooting process there. Link to comment Share on other sites More sharing options...
naiclub Posted October 5, 2020 Share Posted October 5, 2020 10 minutes ago, JorgeMax said: Yes, this problem is after the "preboot" process. Then it restarts and I see the disc with the name given there in the format of the drive I left the other units with the other systems plugged in, like a second installation of Big Sur, Mojave and windows Is it a conflict with Big Sur already installed? Check here Spoiler Give an example to see. Actually, it must have 3 drives. 1. Drive to install 2. The driver to update the installation. 3. The main drive to enter the system If the installation is complete Will only take 2 drives 1. Drive to install 2. Drive to login You will need to access the 2nd drive until the drive is gone. Link to comment Share on other sites More sharing options...
tluck Posted October 5, 2020 Share Posted October 5, 2020 (edited) 15 hours ago, Jief_Machak said: The message show the path UNDER oem path. I improved it in the last commit the display the full path. I've just tried, and everything is loaded from the right place. Could you compile the latest commit, remove the ACPI folder duplication and try ? edit: on Clover revision: 5123 (opencore_integration, commit 458d071ec) after more tests. i see that it does load the SSDT- files from OEM/.../ACPI/patched - good. but is actually it is not loading the DSDT.aml file from there (i get the one from BIOS) (even tho it says it finds it OEM). -- not good. So with just DSDT.aml (duplicated) to CLOVER/APCI/patched, then all is good. Edited October 6, 2020 by tluck Link to comment Share on other sites More sharing options...
naiclub Posted October 5, 2020 Share Posted October 5, 2020 41 minutes ago, mifjpn said: Hello everyone. I woke up in Japan at midnight and checked. Has anything changed? CloverBootloader% git rev-parse --short HEAD 53645a424 After compiling this, I installed Clover_r5123.pkg, but after selecting an entry for both Big Sur and Catalina, one "_" appears in the upper left on a black screen and it stops. Is it my big mistake? BSCANTBOOTdebug10060329.log CTCANTBOOTdebug10060335.log config.plist Thank you. Try this for your own files.config.plist Link to comment Share on other sites More sharing options...
prcmelo Posted October 5, 2020 Share Posted October 5, 2020 (edited) I'm getting the same "SIGILL" Error from this So, since I still can see the "Preboot HD" I've tried to boot from it following the advice of @naiclub but when booting from "Preboot HD" I have this problem https://imgur.com/a/0weje9F and after it reboots... I'm leaving my EFI Folder in case someone can help me. Thanks!!! EFI ga-h97-d3h.zip Edited October 5, 2020 by prcmelo Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 5, 2020 Share Posted October 5, 2020 @prcmelo Check this post Link to comment Share on other sites More sharing options...
prcmelo Posted October 5, 2020 Share Posted October 5, 2020 Hi, @Cyberdevs I've downloaded your Clover Folder before and I had no success... so I started to change it following my 10.15.7 EFI, and still no success... I have tried many configurations and followed many advices, but nothing yet But thanks for your help, let's see if some "miracle" happens on my Hack Link to comment Share on other sites More sharing options...
fusion71au Posted October 5, 2020 Share Posted October 5, 2020 (edited) Tested latest Clover r5123_2bc776d63 on my legacy desktop GAP55aUD3 (System2 in signature). Good News Boots 10.13.6, 10.15.7 and Big Sur Beta (already installed + Installer USB) OEM ACPI is preserved when booting non mac OSes eg Windows, Linux --> preserves OEM activation Kext Injection working well from OEM folders, correctly reads config.plist in OEM folders Bugs Like @tluck report, I noticed that my patched DSDT must also be placed in /EFI/CLOVER/ACPI/patched (in addition to /EFI/CLOVER/OEM/P55A-UD3/ACPI/patched) if using OEM folders for configuration, despite boot log confirming DSDT.aml present in OEM folder. Some kext patching fails eg ALPM IO Error AppleAHCIPort <dict> <key>Comment</key> <string>ALPM IO Error AppleAHCIPort</string> <key>Disabled</key> <false/> <key>Find</key> <data>QGACAA==</data> <key>InfoPlistPatch</key> <false/> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data>AAAAAA==</data> </dict> ---> some of my SATA Hard Disks are not initialized ... Spoiler Bootlogs & EFI Official Clover r5122 all OK, except can't boot Big Sur...GAP55aUD3_Clover_r5122_f4e10b1a2_Bootlog_HighSierra.txt Clover r5122_OC_integration boots all macOS OK, Kext Patching OK (ALPM IO patch works) but OEM folders not working...GAP55aUD3_Clover_r5122OCintegration_08add4995_Bootlog_HighSierra.txt Latest Clover r5123_2bc776d63 boots all macOS OK, Windows OEM OK, ALPM IO kext patching fails, patched DSDT must also be put in /EFI/CLOVER/ACPI/patched...GAP55aUD3_Clover_r5123_ 2bc776d63_Bootlog_HighSierra.txt EFI with Clover r5123_2bc776d63.zip Edit1: Kext patching works again if you give "full" name of kext eg For ALPM IO Error AppleAHCIPort patch, name of target should be com.apple.driver.AppleAHCIPort, not just AppleAHCIPort. Edit2: CLOVERX64._r5123_8e0f4ad24 has fixed OEM folders DSDT issue. Edited October 6, 2020 by fusion71au Clover r5123_8e0f4ad24 has fixed OEM folders DSDT issue 5 1 Link to comment Share on other sites More sharing options...
Slice Posted October 6, 2020 Share Posted October 6, 2020 7 hours ago, fusion71au said: Some kext patching fails eg ALPM IO Error AppleAHCIPort <dict> <key>Comment</key> <string>ALPM IO Error AppleAHCIPort</string> <key>Disabled</key> <false/> <key>Find</key> <data>QGACAA==</data> <key>InfoPlistPatch</key> <false/> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data>AAAAAA==</data> </dict> ---> some of my SATA Hard Disks are not initialized ... May be it requires full name like com.apple.iokti.AppleAHCIPort. (sorry I am not sure exactly the name) 4 Link to comment Share on other sites More sharing options...
fusion71au Posted October 6, 2020 Share Posted October 6, 2020 25 minutes ago, Slice said: May be it requires full name like com.apple.iokti.AppleAHCIPort. (sorry I am not sure exactly the name) Thanks, kext patching works after giving the target kext its' "full name", like in OC config.plist AppleAHCIPort ---> com.apple.driver.AppleAHCIPort Spoiler //From boot log 14:000 0:000 Bridge com.apple.driver.AppleAHCIPort patch to OC : com.apple.driver.AppleAHCIPort (ALPM IO Error AppleAHCIPort) 3 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted October 6, 2020 Share Posted October 6, 2020 Hi @Jief_MachakTested latest Clover r5123_2bc776d63 on my UEFI desktop Gigabyte Z390 Aorus Master: only Clover GUI work, I can't boot at all Big Sur Installed or USB Installer (don(t try Catalina). I only see underscore dash nothing else. 1 Link to comment Share on other sites More sharing options...
iCanaro Posted October 6, 2020 Share Posted October 6, 2020 (edited) same thing, with the Clover just filled in, when you select a macOS from the GUI, then black screen and 1 dash in the top left I also tried on my Z170 and Z97 hacks, using the same Clover working on the Z370, but they immediately go into kernel panic or crash. Even with these hacks I have the option to start them with OC 061 over Clover 5122-OcQuirks, this to say, that I do not start from scratch. debug.log 3 KP_Z170.zip Edited October 6, 2020 by iCanaro 1 1 Link to comment Share on other sites More sharing options...
SavageAUS Posted October 6, 2020 Share Posted October 6, 2020 24 minutes ago, Matgen84 said: Hi @Jief_MachakTested latest Clover r5123_2bc776d63 on my UEFI desktop Gigabyte Z390 Aorus Master: only Clover GUI work, I can't boot at all Big Sur Installed or USB Installer (don(t try Catalina). I only see underscore dash nothing else. I’ve tried 5123 from github (not sure if yours is different) and I can boot Big Sur, Catalina, Windows but not Arch Linux. 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted October 6, 2020 Share Posted October 6, 2020 7 minutes ago, SavageAUS said: I’ve tried 5123 from github (not sure if yours is different) and I can boot Big Sur, Catalina, Windows but not Arch Linux. Mine is different than pre-release. I build r5123 commit 2bc776d63. @iCanaro has the same problem as me. Link to comment Share on other sites More sharing options...
Recommended Posts