Recently Browsing 0 members
No registered users viewing this page.
I'm looking for the best route to achieve this upgrade, so I have been stuck with HS since Nvidia drivers stopped being supported on newer MacOS releases. Now I'm having an AMD 5700 xt on the way and want to plan the upgrade properly. I have added some information below and questions that might help with your recommendation.
Current GPU 1080 ti with Nvidia webdrivers installed. So should I uninstall the webdriver before adding the new GPU? Clover is being used and EFI attached. Any kext must be removed? or parameters adjusted MacOS HS 10.13.6, should I upgrade before using the new GPU? CPU: 9900K Motherboard:ROG MAXIMUS XI HERO (WI-FI) Dual Monitors I have a Time machine backup, Do you recommend a fresh install? and If I did, will I be able to restore my data/apps as-is?
Please let yourself free to explore further aspects to considers.
If WEG, Lilu, etc. exist in 10.14 /L/E, when upgrade to 10.15, are they needed in Clover/kexts/Other?By exquirentibus
Dumb question, but ... if I already have these kexts installed to /L/E:
Do I also need to copy them to Clover/kexts/Other when upgrading from 10.14, and then delete them ( as they are not currently in Clover/kexts/Other)?
And do I need to set config.plist/SystemParameters/InjectKexts=Detect so that Clover will inject all applicable (depending on version) kexts in EFI/Clover/kexts/Other only if FakeSMC.kext is NOT in kernel cache.
Cloud Clover Editor is an open source application that allows you to manage the configuration of various Hackintosh Bootloaders.
Open Cloud Clover Editor
Cloud Clover Editor Wiki
Cloud Clover Editor Sources
Supports Clover EFI, Ozmosis, Chameleon, OpenCore GUI and Text Editor Mode CCE Bank Mobile friendly and more...
Officially supported browsers
Chrome 42+ Microsoft Edge 14+ Firefox 39+ Safari 10+ Opera 29+ Opera Mobile 12+ Chrome for Android 75+ Firefox for Android 67+
mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor (Discontinued) crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support
Please let me know if i forgot you!
I'm trying to boot MacOS on a Chromebook without UEFI. I'm stuck at getting the bootloader (Chameleon/Clover) to work.
My setup / context:
I have an Acer Chromebook Spin 13.
2 x USB-C 1 x USB-A 3.0 MicroSD Slot No USB A 2.0 (I've read that Clover has problems with USB 3.0) Firmware:
There's no UEFI firmware available and by default, it doesn't even allow booting anything other than ChromeOS. Thanks to MrChromebox (big shoutouts!), I flashed a custom legacy bios that allows me to boot anything linux related. This bios is flashed into the RW_LEGACY section of the existing bootloader (coreboot afaik) and doesn't have any configuration options. If I have to change a setting, I could try compiling his bios payload myself with the specific setting enabled.
What I've tried so far:
Only selected setting was "Install chameleon on the chosen path", rest was unselected.
1 - Install chameleon first without restoring the basesystem:
> boot0: GPT
> boot0: done
(hangs; pressing power button once shuts down
Chameleon installation log is attached as "Chameleon_Installer_Log_BEFORE".
2 - Install Chameleon after restoring the base system:
> boot0: GPT
> boot0: GPT
> boot0: doneboot1: /boot <- Exactly like that, no line break in between
(hangs; pressing power button once shuts down)
I haven't been able to reproduce #2 after wiping the drive and doing the same thing again. Subsequent attempts have resulted in either #1 of either Chameleon or Clover.
Chameleon installation log is attached as "Chameleon_Installer_Log_AFTER".
I tried multiple settings and configurations, but all of them boiled down to either one of these.
1 - Doesn't do anything, just hangs at "Booting from usb..."
2 - Boots into the blue/grey mode as shown in the attached images.
According to MrChromebox, this could be an old Tianocore DUET It doesn't detect anything (cpu frequency, ram, partitions or disks)
I've read pretty much every article, github readme and other types of documentation for coreboot, tianocore, clover, chameleon and MrChromebox' rw_legacy payloads and right now, I'm totally clueless as to what to try next...
A few questions that came up:
Why does chameleon hang? What is it looking for, /boot was clearly written to the disk by the Chameleon installer? What exactly is the blue/grey image? According to MrChromebox, it could be Tianocore DUET Where does it come from? Clover? The mainboard itself? Why does the blue/grey thing not detect my processor frequency or any partitions/drives? Can I use some sort of DUET bootloader to chainload Clover?
If you guys could answer any of them or if you have any other guesses or information as to what's happening, I'd be really happy!