spakk Posted January 20 Share Posted January 20 Who among you still has an old AMD computer with a "K8, K10, or K15 CPU-FAMILY" and coincidentally also has a freshly installed macOS Mojave 10.14.6 on the internal or external hard drive to test a new kernel? If you have any questions about which CPUs we are talking about, you can find the appropriate AMD CPUs that may be supported by the kernel at: http://www.amdarea51.de/cpus/archiv/archiv.php I urrently have a Phenom II 1100t CPU but an outdated Nvidia 550 TI graphics card, which may not be supported by Mojave. I don't want to invest anything in my old AMD system at the moment. However, the emulator should support SSE4.1 functions. Currently, the system reboots after reaching this point: hfs: mounted macOS Base System_macOS_mojave-10146 on device b(1, 10) load_init_program: attempting to load /sbin/launchd VM Swap Subsystem is ON After that, the PC restarts and subsequently resets the BIOS. Presumably, the old RTC Kext driver I am using is not performing the desired work. About the kernel: I have completely redesigned the emulator and added the missing features for SSE4.1 and other changes to deal with the problems with "Invalid Opcode Error" loops. Check out the boot behavior in my video. I'm using a USB stick with macOS Mojave 10.14.4 and the kernel is 10.14.6. It doesn't make a bad impression. If are interested, then you can send me a PM. Here is my video in MOV format showing the boot behavior of the AMD kernel: https://uploadnow.io/f/SK6pGqc Any help to help me resolve the issue of rebooting when the message “VM Swap Subsystem is ON” is appreciated. 2 Link to comment Share on other sites More sharing options...
spakk Posted January 25 Author Share Posted January 25 Hello everyone, I urgently need help from experienced OpenCore users who can assist me in understanding what I might be doing wrong in my current experiment. Please note that this is just an experiment to get an old AMD Phenom II X6 1100t running. I have configured OpenCore to a certain extent but seem to be stuck at this point (see attached image). While I can access OpenShell, my knowledge ends there. How do I access my hard drive with the associated MacOS partition to test it with my new AMD kernel? Any help is welcome. For my initial attempt, I used the Enoch bootloader. Unfortunately, I couldn't boot an APFS partition with it, so I had to try configuring OpenCore. I must admit that I haven't dealt with Clover or OpenCore before, and now I'm facing this challenge and need assistance. Thank you in advance for your help! Why can't I access the macOS HD even though I created this HD on my Macintosh and was able to boot from it without any issues as an external HD? Info: I know it may not be possible to enter the desktop with my GTX 550 Ti, but for testing purposes, that would be completely sufficient. I intentionally did not use the AMD BIN patch in the config.plist with which I am trying to boot the system, as I want to use my patched AMD kernel for K8, K10, or K15. A config.plist with the AMD BIN patch is also present in the EFI folder Edit: EFI folder was faulty Link to comment Share on other sites More sharing options...
Shaneee Posted January 25 Share Posted January 25 @spakk Hide Auxiliary is enabled in your config. Either disable it or press the space bar when at the OpenCore GUI to show all bootable drives. USB installers tend to hide in there. If that's not the case see below. All of your OpenCore logs provided in the zip are empty but you've got logging enabled. You'll need to use the DEBUG build of OpenCore. Then we can see if the image is even being deteced by OpenCore. 3 Link to comment Share on other sites More sharing options...
spakk Posted January 25 Author Share Posted January 25 45 minutes ago, Shaneee said: @spakk Hide Auxiliary is enabled in your config. Either disable it or press the space bar when at the OpenCore GUI to show all bootable drives. USB installers tend to hide in there. If that's not the case see below. All of your OpenCore logs provided in the zip are empty but you've got logging enabled. You'll need to use the DEBUG build of OpenCore. Then we can see if the image is even being deteced by OpenCore. Hi Shanee, I was hoping you'd reach out ;-). Thanks a lot for your prompt response. I've systematically addressed and cleared all error logs, so they are currently empty. However, I'll follow your instructions and attempt to correct the issues you described. I'll get back to you later I have been using the latest DEBUG build version 0.97 <dict> <key>Arguments</key> <string></string> <key>Auxiliary</key> <false/> ............ <false/> I have now deactivated it; I will now attempt to boot the system with this configuration. @Shanneee Unfortunately, everything remains unchanged. I cannot detect any other partitions except for the EFI partition on the hard drive. The log is also without any entries. I must have unintentionally changed something, and as a result, for the past three or four boot attempts, I haven't received a filled log. I'm attaching an older log here. opencore-2012-01-02-223801.txt Link to comment Share on other sites More sharing options...
feartech Posted January 25 Share Posted January 25 5 hours ago, spakk said: Hi Shanee, I was hoping you'd reach out ;-). Thanks a lot for your prompt response. I've systematically addressed and cleared all error logs, so they are currently empty. However, I'll follow your instructions and attempt to correct the issues you described. I'll get back to you later I have been using the latest DEBUG build version 0.97 <dict> <key>Arguments</key> <string></string> <key>Auxiliary</key> <false/> ............ <false/> I have now deactivated it; I will now attempt to boot the system with this configuration. @Shanneee Unfortunately, everything remains unchanged. I cannot detect any other partitions except for the EFI partition on the hard drive. The log is also without any entries. I must have unintentionally changed something, and as a result, for the past three or four boot attempts, I haven't received a filled log. I'm attaching an older log here. opencore-2012-01-02-223801.txt 256 kB · 1 download you should run ocvalidate on your config.plist as you have a lot of errors that will need to be fixed up also at the end of your log: 00:666 00:007 OC: Driver OpenRuntime.efi at 0 is successfully loaded! 00:674 00:007 OC: Driver OpenCanopy.efi at 1 () is being loaded... 00:686 00:011 OC: Driver OpenCanopy.efi at 1 cannot be found! 1 Link to comment Share on other sites More sharing options...
spakk Posted January 25 Author Share Posted January 25 2 hours ago, feartech said: you should run ocvalidate on your config.plist as you have a lot of errors that will need to be fixed up also at the end of your log: 00:666 00:007 OC: Driver OpenRuntime.efi at 0 is successfully loaded! 00:674 00:007 OC: Driver OpenCanopy.efi at 1 () is being loaded... 00:686 00:011 OC: Driver OpenCanopy.efi at 1 cannot be found! Thank you for your feedback. However, the error log I attached is a bit older, as I believe I've already addressed all the issues listed in the old log in the config.plist. My current issue is that I'm not making progress, and currently, no errors are being displayed in the log. In this state, no other hard drives or partitions are shown, except for the EFI partition of the drive from which I'm booting OpenCore. When I boot with HFSplus.efi, I receive the following panic message: "!!!! x64 exception type - 0000000000000006 !!!". Therefore, I am using the OpenHFS version. I've attached the entire EFI folder for your review. Edit: I will download the OCValidate app and try my luck to fix the issues. I will get back to you later. Thanks for the suggestion with the app. Edit1: The OCValidate app has shown me exactly the opposite of what the DEBUG log indicated. Here are the error messages that the OCValidate app has identified. ****************************************************** Config Validator OpenCore 0.9.5 Drag config.plist file to verify it ****************************************************** Start of verification: /Users/mein/Desktop/Config Validator.app/Contents/Resources/script: line 27: Sleep: command not found /Users/mein/Desktop/Config Validator.app/Contents/Resources/script: line 37: Sleep: command not found NOTE: This version of ocvalidate is only compatible with OpenCore version 0.9.5! OCS: Missing key Strategy, context <Block>! OCS: Missing key CustomPciSerialDevice, context <Quirks>! OCS: Missing key DisableIoMapperMapping, context <Quirks>! OCS: Missing key ForceAquantiaEthernet, context <Quirks>! OCS: Missing key Patch, context <Kernel>! OCS: Missing key InstanceIdentifier, context <Boot>! OCS: No schema for SerialInit at 5 index, context <Debug>! OCS: Missing key LogModules, context <Debug>! OCS: No schema for AllowNvramReset at 0 index, context <Security>! OCS: No schema for AllowToggleSip at 2 index, context <Security>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key Serial, context <Misc>! OCS: No schema for LegacyEnable at 2 index, context <NVRAM>! OCS: Missing key PointerDwellClickTimeout, context <AppleInput>! OCS: Missing key PointerDwellDoubleClickTimeout, context <AppleInput>! OCS: Missing key PointerDwellRadius, context <AppleInput>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key LoadEarly, context <Drivers>! OCS: Missing key ConsoleFont, context <Output>! OCS: Missing key GopBurstMode, context <Output>! OCS: Missing key InitialMode, context <Output>! OCS: Missing key PciIo, context <ProtocolOverrides>! OCS: Missing key ResizeUsePciRbIo, context <Quirks>! OCS: Missing key ShimRetainProtocol, context <Quirks>! Serialisation returns 50 errors! OpenUsbKbDxe.efi at UEFI->Drivers[11] should NEVER be used together with UEFI->Input->KeySupport! OpenUsbKbDxe.efi at UEFI->Drivers[11], and Ps2KeyboardDxe.efi at UEFI->Drivers[12], should NEVER co-exist! UEFI->Output->InitialMode is illegal (Can only be Auto, Text, or Graphics)! CheckUefi returns 3 errors! Completed validating /Volumes/EFI/EFI/OC/config.plist in 2 ms. Found 53 issues requiring attention. I can see that there is still a lot of work ahead of me to fix all these errors. Link to comment Share on other sites More sharing options...
Shaneee Posted January 25 Share Posted January 25 @spakk From that log I don't see it recognising any filesystems. Is the board UEFI and devices UEFI compatible? You may have better luck using OpenCore in legacy mode. See here, https://dortania.github.io/OpenCore-Install-Guide/installer-guide/mac-install.html#legacy-setup 1 Link to comment Share on other sites More sharing options...
spakk Posted January 25 Author Share Posted January 25 8 minutes ago, Shaneee said: @spakk Aus diesem Protokoll geht hervor, dass es keine Dateisysteme erkennt. Ist das Board UEFI und die Geräte UEFI-kompatibel? Möglicherweise haben Sie mehr Glück, wenn Sie OpenCore im Legacy-Modus verwenden. Siehe hier, https://dortania.github.io/OpenCore-Install-Guide/installer-guide/mac-install.html#legacy-setup I will tackle the legacy setup and hope that somehow I will be able to revive my old AMD Hackintosh using OC. Thank you very much for the suggestion. 😃 1 Link to comment Share on other sites More sharing options...
spakk Posted January 25 Author Share Posted January 25 Now I'm making some progress and can also detect my MacOS partition with OpenCore. However, there are still some error messages that need to be addressed before I can proceed with testing the boot from the Mojave partition. I will attach a few pictures of the boot results and include the error messages here. and here are the error messages from Config Validator OpenCore 0.9.5 app: ****************************************************** Config Validator OpenCore 0.9.5 Drag config.plist file to verify it ****************************************************** Start of verification: /Users/mein/Desktop/Config Validator.app/Contents/Resources/script: line 27: Sleep: command not found /Users/mein/Desktop/Config Validator.app/Contents/Resources/script: line 37: Sleep: command not found NOTE: This version of ocvalidate is only compatible with OpenCore version 0.9.5! OCS: Missing key Base, context <Patch>! OCS: Missing key BaseSkip, context <Patch>! OCS: Missing key Base, context <Patch>! OCS: Missing key BaseSkip, context <Patch>! OCS: Missing key SyncTableIds, context <Quirks>! OCS: Missing key ForceBooterSignature, context <Quirks>! OCS: Missing key ResizeAppleGpuBars, context <Quirks>! OCS: Missing key Strategy, context <Block>! OCS: Missing key CustomPciSerialDevice, context <Quirks>! OCS: Missing key DisableIoMapperMapping, context <Quirks>! OCS: Missing key ForceAquantiaEthernet, context <Quirks>! OCS: Missing key ProvideCurrentCpuInfo, context <Quirks>! OCS: Missing key SetApfsTrimTimeout, context <Quirks>! OCS: Missing key CustomKernel, context <Scheme>! OCS: Missing key HibernateSkipsPicker, context <Boot>! OCS: Missing key InstanceIdentifier, context <Boot>! OCS: Missing key LauncherOption, context <Boot>! OCS: Missing key LauncherPath, context <Boot>! OCS: Missing key PickerVariant, context <Boot>! OCS: No schema for SerialInit at 5 index, context <Debug>! OCS: Missing key LogModules, context <Debug>! OCS: Missing key Flavour, context <Entries>! OCS: No schema for AllowNvramReset at 0 index, context <Security>! OCS: No schema for BootProtect at 5 index, context <Security>! OCS: Missing key Flavour, context <Tools>! OCS: Missing key FullNvramAccess, context <Tools>! OCS: Missing key Serial, context <Misc>! OCS: No schema for LegacyEnable at 2 index, context <NVRAM>! OCS: No schema for AdviseWindows at 0 index, context <Generic>! OCS: Failed to parse data field as value with type mdata and <__PLACEHOLDER__> contents, context <ROM>! OCS: Missing key AdviseFeatures, context <Generic>! OCS: Missing key MaxBIOSVersion, context <Generic>! OCS: Missing key UseRawUuidEncoding, context <PlatformInfo>! OCS: No schema for AudioOut at 2 index, context <Audio>! OCS: No schema for MinimumVolume at 4 index, context <Audio>! OCS: No schema for VolumeAmplifier at 6 index, context <Audio>! OCS: Missing key AudioOutMask, context <Audio>! OCS: Missing key DisconnectHda, context <Audio>! OCS: Missing key MaximumGain, context <Audio>! OCS: Missing key MinimumAssistGain, context <Audio>! OCS: Missing key MinimumAudibleGain, context <Audio>! OCS: Missing key ResetTrafficClass, context <Audio>! OCS: Missing key SetupDelay, context <Audio>! OCS: Couldn't get array serialized at 0 index! OCS: Couldn't get array serialized at 1 index! OCS: Couldn't get array serialized at 2 index! OCS: No schema for KeyMergeThreshold at 2 index, context <Input>! OCS: Missing key ConsoleFont, context <Output>! OCS: Missing key GopBurstMode, context <Output>! OCS: Missing key GopPassThrough, context <Output>! OCS: Missing key InitialMode, context <Output>! OCS: Missing key ReconnectGraphicsOnConnect, context <Output>! OCS: Missing key UIScale, context <Output>! OCS: No schema for AppleEvent at 3 index, context <ProtocolOverrides>! OCS: Missing key AppleEg2Info, context <ProtocolOverrides>! OCS: Missing key PciIo, context <ProtocolOverrides>! OCS: No schema for DeduplicateBootOrder at 0 index, context <Quirks>! OCS: Missing key ActivateHpetSupport, context <Quirks>! OCS: Missing key DisableSecurityPolicy, context <Quirks>! OCS: Missing key EnableVectorAcceleration, context <Quirks>! OCS: Missing key EnableVmx, context <Quirks>! OCS: Missing key ForceOcWriteFlash, context <Quirks>! OCS: Missing key ForgeUefiSupport, context <Quirks>! OCS: Missing key ReloadOptionRoms, context <Quirks>! OCS: Missing key ResizeGpuBars, context <Quirks>! OCS: Missing key ResizeUsePciRbIo, context <Quirks>! OCS: Missing key ShimRetainProtocol, context <Quirks>! OCS: Missing key AppleInput, context <UEFI>! Serialisation returns 68 errors! Booter->Quirks->ProvideCustomSlide is enabled, but OpenRuntime.efi is not loaded at UEFI->Drivers! Booter->Quirks->EnableWriteUnprotector is enabled, but OpenRuntime.efi is not loaded at UEFI->Drivers! CheckBooter returns 2 errors! PlatformInfo->Generic->SystemUUID is borked (Can only be empty, special string OEM or valid UUID)! CheckPlatformInfo returns 1 error! UEFI->Quirks->RequestBootVarRouting is enabled, but OpenRuntime.efi is not loaded at UEFI->Drivers! UEFI->Output->InitialMode is illegal (Can only be Auto, Text, or Graphics)! CheckUefi returns 2 errors! Completed validating /Volumes/EFI/EFI/OC/config.plist in 4 ms. Found 73 issues requiring attention. Edit: I would like to ensure that error logs are generated during the boot process of OpenCore on my EFI partition. Unfortunately, I am having difficulties configuring this in the Config.plist. If someone is proficient in this area, please help me implement it with a code example. Link to comment Share on other sites More sharing options...
Shaneee Posted January 26 Share Posted January 26 @spakk Send over the current EFI your using and I'll sort these errors for you. Link to comment Share on other sites More sharing options...
spakk Posted January 26 Author Share Posted January 26 On 1/26/2024 at 9:36 AM, Shaneee said: @spakk Send over the current EFI your using and I'll sort these errors for you. @Shaneehere is the last EFI folder Edit: EFI folder was faulty Link to comment Share on other sites More sharing options...
Shaneee Posted January 26 Share Posted January 26 6 minutes ago, spakk said: @Shaneehere is the last EFI folder EFI.zip 3.31 MB · 0 downloads Updated config.plist and ensured version of files matches. No validation errors now. No other changes made. EFI.zip 1 Link to comment Share on other sites More sharing options...
spakk Posted January 26 Author Share Posted January 26 1 hour ago, Shaneee said: Updated config.plist and ensured version of files matches. No validation errors now. No other changes made. EFI.zip 6.66 MB · 0 downloads The HfsPlus.efi is causing the well-known !!!x64 exception type - 0000000000000006 !!! (red screen). I have disabled it in the config.plist file. Code: ...... <dict> <key>Arguments</key> <string></string> <key>Comment</key> <string></string> <key>Disabled</key> <true/> <key>LoadEarly</key> <false/> <key>Path</key> <string>HfsPlus.efi</string> </dict> ``` But what is the alternative? OpenHfsPlus.efi? Or is there something now that remedies this error during boot on AMD system? I will try to boot with this configuration: <key>Drivers</key> <array> <dict> <----------- I have completely removed this entry for HfsPlus.efi <key>Arguments</key> <----------- <string></string> <----------- <key>Comment</key> <----------- <string></string> <----------- <key>Enabled</key> <----------- <true/> <----------- <key>LoadEarly</key> <----------- <false/> <----------- <key>Path</key> <----------- <string>OpenHfsPlus.efi</string> <------ </dict> <----------- <dict> <key>Arguments</key> <string></string> <key>Comment</key> <string></string> <key>Disabled</key> <true/> <key>LoadEarly</key> <false/> <key>Path</key> <string>HfsPlus.efi</string> </dict> <dict> <key>Arguments</key> <string></string> <key>Comment</key> <string></string> <key>Enabled</key> <true/> <key>LoadEarly</key> <false/> <key>Path</key> <string>OpenCanopy.efi</string> </dict> <dict> <key>Arguments</key> <string></string> <key>Comment</key> <string></string> <key>Enabled</key> <true/> <key>LoadEarly</key> <false/> <key>Path</key> <string>OpenRuntime.efi</string> </dict> Edit: Unfortunately, it's just like at the beginning when I wasn't booting from Legacy EFI. It must be something else that needs to be adjusted. I noticed that you replaced the OpenCore.efi. Is that the one from the OpenCore DEBUG package? Because I can only recognize the EFI partition but not the macOS partition. Link to comment Share on other sites More sharing options...
Shaneee Posted January 26 Share Posted January 26 Ahh yeah if you still need debug grab the 0.9.7 debug and replace OpenCore.efi I think the drive not showing up is a result of how the USB has been made. I suggest you make the USB using createinstallmedia and load your custom kernel via OpenCore. The documents show how this is done. 1 Link to comment Share on other sites More sharing options...
spakk Posted January 30 Author Share Posted January 30 In the past few days, I've been working intensively on configuring OpenCore, and I've finally succeeded in getting the bootloader up and running. The Dortania team has developed an impressive tool. Initially, I was overwhelmed by the abundance of information I had to gather for the initial attempts. However, gradually, I familiarized myself with creating configuration options. I was able to make all the necessary adjustments and ultimately resolve the essential errors to successfully operate the bootloader. Now, the next crucial step is to test the kernel. Once there is progress, I will provide an update. At the beginning, due to ignorance, I adopted many completely crazy inputs from other users, and I was about to shelve the OpenCore topic. Then, Shanee pointed me in the right direction to try it with the Legacy Boot from OpenCore. After reading up on it, I suddenly came across an older post that continued to inspire me. 1 Link to comment Share on other sites More sharing options...
spakk Posted January 31 Author Share Posted January 31 The boot process now stops at this point. The displayed messages suggest that the boot process is successful up to a certain point, but afterward, the execution of the system is halted or blocked. The specific messages do not provide enough information for me to determine the exact cause. Even entering the data of my Random Access Memory (RAM) into the config.plist did not yield the expected result. Therefore, I need your advice. (see image) Edit: For your information, I am using my patched kernel without the AMD patches in the config.plist. Any ideas on taking a further step forward to observe the kernel's boot behavior would be greatly appreciated. Link to comment Share on other sites More sharing options...
Shaneee Posted January 31 Share Posted January 31 It's either not picking up the custom kernel which should be noted in the log or the kernel isn't working. This is where a modern AMD CPU will halt without the kernel patches enabled/configured correctly. Link to comment Share on other sites More sharing options...
spakk Posted January 31 Author Share Posted January 31 15 minutes ago, Shaneee said: It's either not picking up the custom kernel which should be noted in the log or the kernel isn't working. This is where a modern AMD CPU will halt without the kernel patches enabled/configured correctly. In the end, I have to come to terms with the fact that it might not work in the end due to outdated hardware. I simply wanted to replicate the boot process I previously performed with the Enoch bootloader using OpenCore, to see how far I can get with it and to check if the Opemu is working flawlessly or not. Well, it's just an attempt after all. Link to comment Share on other sites More sharing options...
Shaneee Posted January 31 Share Posted January 31 Have you checked the logs? Might be worth giving Clover a go? Link to comment Share on other sites More sharing options...
spakk Posted January 31 Author Share Posted January 31 17 minutes ago, Shaneee said: Have you checked the logs? Might be worth giving Clover a go? I will give it a try with Clover, but it's a pity that Enoch doesn't support APFS partitions. Link to comment Share on other sites More sharing options...
Shaneee Posted January 31 Share Posted January 31 It may or may not work but worth a shot I guess. Link to comment Share on other sites More sharing options...
spakk Posted February 1 Author Share Posted February 1 14 hours ago, Shaneee said: It may or may not work but worth a shot I guess. It seems that the Enoch Bootloader and some of us on insaneleymac.com have already reached a considerable age. As is customary in the course of life, interest in the old ones fades, and this apparently applies to Enoch and the older CPUs with missing functions as well. 1 Link to comment Share on other sites More sharing options...
spakk Posted February 9 Author Share Posted February 9 Hello folks, Today, I was finally able to take some time to both build the High Sierra Kernel and create a bootable USB installer for my initial test. As you can see in the video, the system boots smoothly. Unfortunately, it halts at the point: "apfs_module_start:1279: load: com.apple.filesystems.apfs. v748.51.0 748.77.8. 2018/06/21." I've read reports from other users online who faced the same issue and eventually resolved it with an ACPI patch and a current BIOS update using the Clover bootloader. I've already performed the latest BIOS update and I'm using the Enoch bootloader, but I'm not exactly sure where to start in order to fix the problem on my motherboard. Can anyone explain how I can address this issue on my motherboard? Edit: You must have wondered why I reverted to High Sierra, even though the heading clearly states "Mojave 10.14.6." The answer is quite straightforward: I've undertaken every possible effort to configure Clover and OpenCore for my hardware, ultimately encountering limitations. A user who recently reached out to me suggested I should initially conduct the test with Sierra or High Sierra, and that's the reason for today's experiment. 20240209_131350a.mp4 Link to comment Share on other sites More sharing options...
Shaneee Posted February 9 Share Posted February 9 See here, https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/extended/kernel-issues.html#stuck-on-rtc-pci-configuration-begins-previous-shutdown-hpet-hid-legacy Could be a few things, IRQ conflict, PCI issue, SATA issue or NVRAM. Can you send the kernel over. I've got an old Athlon machine in the attic, I can try and revive it. 1 Link to comment Share on other sites More sharing options...
spakk Posted February 9 Author Share Posted February 9 On 2/9/2024 at 1:47 PM, Shaneee said: See here, https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/extended/kernel-issues.html#stuck-on-rtc-pci-configuration-begins-previous-shutdown-hpet-hid-legacy Could be a few things, IRQ conflict, PCI issue, SATA issue or NVRAM. Can you send the kernel over. I've got an old Athlon machine in the attic, I can try and revive it. I'll upload the kernel in a few minutes. I went shopping briefly and am on my way home. Additionally, I'm using the System.kext for this kernel. You can use it from your High Sierra Kernel 10.13.6 on GitHub to bypass all those "loops error" messages with the icons. Edit: 1 Link to comment Share on other sites More sharing options...
Recommended Posts