Jump to content
ErmaC

Clover General discussion

19,022 posts in this topic

Recommended Posts

Thanks @Slice, Legacy r4241 works well under 10.13.1 (17B25c).

Already tested placing kexts on 10.13, or Other only.. both work and even got faster boot time (not sure what have U done, I mean for my mach).

 

#EDIT: The log file below is with 10.6 upto 10.13 & Other folders available on /kexts (but as prev, I'm only using 10.11 & 10.13 for kext inject)

bootlog.log_a43sj_r4241.txt.zip

Share this post


Link to post
Share on other sites
Advertisement

 Sorry for my bad english

 

I forgot to say that my Sierra HDD was connected. After select USB by F8 for booting, I try r4239 with USB installer. 

 

I don't understand your answer. what is the correct procedure in this case for testing? 

I just see no issues in your observations.

You started 10.12 and don't see 10.13. It is OK (All Correct).

 

Hi Slice,

 

Another test: Clover r4241 on HDD macOS 10.13.1 with HDD Sierra connected.

 

 

When I boot from macOS 10.13.1----->No injection (10.13 folder only). r4241.  Kext management  don't see empty folder (10.6, 10.7, etc)

 

When I boot from macOS 10.13.1----->Ok (10.13 folder only), r4233.   Kext management see all empty folder (10.6, 10.7, etc)

 

This is a difference between old and new Clover. You need no to see 10.6 folder if you boot 10.13.1.

Share this post


Link to post
Share on other sites

I just see no issues in your observations.

You started 10.12 and don't see 10.13. It is OK (All Correct).

 

 

This is a difference between old and new Clover. You need no to see 10.6 folder if you boot 10.13.1.

Slice, why no init InjectKextList for all folder then list kext for current system, then it will never fail inject kext even if user see 10.6 then boot 10.13?

 

syscl

Share this post


Link to post
Share on other sites

 

When I boot from macOS 10.13.1----->No injection (10.13 folder only). r4241.  Kext management  don't see empty folder (10.6, 10.7, etc)

 

 

@Matgen84,

 

From your boot log

90:535  0:026  GetOSVersion: 10.13.1 (17B25c)
90:842  0:000  Beginning FSInjection
90:842  0:000  skipping kext injection (not requested) 

Check your config.plist/SystemParameters/InjectKexts set to Yes or Detect?

 

 

	<key>SystemParameters</key>
	<dict>
		<key>InjectKexts</key>
		<string>Yes</string>
	</dict> 

 

 

 

 

 

Hmmb, sounds strange. I was also using r4239 under 10.13.1 (17B25C) but got no problem with Slice's FakeSMC (v3.5.0) & RealtekRTL8111 (v2.2.1).

 

Is there any unresolved patch when U were compiling r4239 binary using buildclover script? (I don't think so, though)

(I attached my compiled r4239 below, thanks).

 

 

It is impossible for unknown arch=.

I may propose that your compilation is buggy. What is your toolchain?

 

I think I compiled r4239 (XCODE 8.3.3 in 10.13, toolchain setting XCODE8) forgetting to revert @cecekpawon's diff patch from r4238...

 

 

 

4:038  0:000  Build with: [Args: -x64 -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_APPLE_HFSPLUS_DRIVER -t XCODE8 | -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.13 | XCODE: 8.3.3]

 

 

 

 

After deleting & re-downloading Clover r4241 from svn, everything OK again.  Clover r4241 boots successfully into 10.13.1beta and kexts detected in /10.xx & /Other.

 

Compiled with XCODE 8.2.1 in 10.11.6, toolchain setting XCODE8 ---> boots fine into 10.13.1beta, 10.13, 10.12.6, 10.7

Compiled with XCODE 9.0 in 10.13.1beta, toolchain setting XCODE8 ---> boots fine into 10.13.1beta, 10.13, 10.12.6, 10.7

 

Thanks everyone for helping with troubleshooting  :).

Boot logs.zip

Clover_v2.4k_r4241.zip

Share this post


Link to post
Share on other sites

Guys why EmuVariableUefi-64.efi affect the update process? When I try to update supplemental update I am getting this error;

 

post-803029-0-52147000-1507334145_thumb.png

 

But when I remove the EmuVariableUefi-64.efi I can update without any problem. 

Share this post


Link to post
Share on other sites

Guys why EmuVariableUefi-64.efi affect the update process? When I try to update supplemental update I am getting this error;

 

attachicon.giferror-install.png

 

But when I remove the EmuVariableUefi-64.efi I can update without any problem. 

I dont even have EmuVariableUEFI on my laptop and im getting that error.

Share this post


Link to post
Share on other sites

@slice can i have ur fakesmc 3.5 coz other user says using this version of fakesmc bypass the osinstall.mpkg damage error installing high sierra using clover uefi,,TIA

Share this post


Link to post
Share on other sites

 

 

 

@Matgen84,

 

From your boot log

90:535  0:026  GetOSVersion: 10.13.1 (17B25c)
90:842  0:000  Beginning FSInjection
90:842  0:000  skipping kext injection (not requested) 

Check your config.plist/SystemParameters/InjectKexts set to Yes or Detect?

 

 

I install r4241 in update mode. Config.plist work well if I downgrade to r4223 with EFI Backups, for example.

I just see no issues in your observations.

You started 10.12 and don't see 10.13. It is OK (All Correct).

 

 

This is Test r4239 from USB pendrive with HDD Sierra connected: I started 10.13. GetOSversion detected 10.12. Only Other folder in pendrive, boot High Sierra.

 

Sorry for my english.

Share this post


Link to post
Share on other sites

Slice, why no init InjectKextList for all folder then list kext for current system, then it will never fail inject kext even if user see 10.6 then boot 10.13?

 

syscl

You should realise the process of menu creation and running. There are two different process.

If we set Init InjectKextList into menu creation then it will be added with every menu entries that we already saw as double injection.

I can set the init conditionally if not inited yet.

Share this post


Link to post
Share on other sites

For those who have a problem with kext injection please test my version

attachicon.gifCLOVERX64.efi-4243.zip

Ah, forgot to mention that my prev tests were using "InjectKexts=Yes", now with "...=Detect" ur r4243 boots 10.13.1 (17B25c) fine from "/kexts/10.13" folder, also same result with manually buildclover script for r4243.

And how could we figure out that gotta "kext injection problem"..? Thanks.

bootlog.log_r4243_slice.txt.zip

bootlog.log_r4243_buildclover.txt.zip

Share this post


Link to post
Share on other sites

For those who have a problem with kext injection please test my version

attachicon.gifCLOVERX64.efi-4243.zip

 

Commits r4243: with or with without CloverX64.efi-4243, Clover get OSversion 10.12 when I boot from USB pen drive (10.13 only) and HDD Sierra connected: Kextd stall on AppleACPICPU and black screen

 

Commits r4243: with or with without CloverX64.efi-4243, Clover get OSversion 10.13.1 when I boot from HDD High Sierra (10.13 only) and HDD Sierra connected. Kextd stall on AppleACPICPU

 

 

Commits r4243 HDD 10.13.1 alone (10.13 folder only): with or  without CloverX64.efi-4243: No Injection -----> "Thinning failed" error. 

 

Here, new kext management don't work with 10.13 folder only

 

 

I don't understand why these issues?

preboot_Clover_r4243_USB.log.zip

preboot_Cloverr4243_HDD_alone.log.zip

Share this post


Link to post
Share on other sites

Commits r4243: with or with without CloverX64.efi-4243, Clover get OSversion 10.12 when I boot from USB pen drive (10.13 only) and HDD Sierra connected: Kextd stall on AppleACPICPU and black screen

 

Commits r4243: with or with without CloverX64.efi-4243, Clover get OSversion 10.13.1 when I boot from HDD High Sierra connected. Kextd stall on AppleACPICPU

 

 

Commits r4243 HDD 10.13.1 alone (10.13 folder only): with CloverX64.efi-4243: No Injection -----> "Thinning failed" error.  I don't test without CloverX64.efi-4243

 

 

I don't understand why these issues?

Both logs with NOT MY clover.

Share this post


Link to post
Share on other sites

Forgot when I have edited my previous post. Can you look it. Please

 

 

New attached files here with your cloverX64. 

No, it is not my Clover.  B)

Share this post


Link to post
Share on other sites

Both logs with NOT MY clover.

For testing, I replace cloverX64.efi compiled by your clover. Good or bad use? I re-download your cloverx64.efi-4243 and try again. 

 

___Matgen84___

 

mv CLOVERX64.efi to \EFI\BOOT\BOOTX64.efi ?

what version: original or new slice's cloverx64.efi-4243? CloverX64 will be the same version in /EFI/BOOT/ and /EFI/Clover. I suppose? Thanks

 

 

Edit: with CLOVERX64.efi-4243 - 10.13 Only --->Injection but kext stall AppleACICPU, black screen with pointer

         with CLOVERX64.efi-4243 - Other Only---> Failed injection with kext stall AppleACICPU....

 

I put Slice's CloverX64: in /EFI/Clover and renamed it to BOOTX64 before put it  /EFI/BOOT/

post-1110743-0-49617800-1507379614_thumb.png

preboot_CLOVERX64.efi-4243_1013Only.log.zip

preboot_CLOVERX64.efi-4243_OtherOnly.log.zip

Share this post


Link to post
Share on other sites

Slice test version should contain: "Args: -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.11.6 | XCODE: 7.3.1".
Yes, \EFI\Clover\CLOVERX64.efi should be same with \EFI\BOOT\BOOTX64.efi
To check your Clover path / booted from:
0:100  0:000  SelfDevicePath=PciRoot(0x0)...
0:100  0:000  SelfDirPath = \EFI\BOOT

Share this post


Link to post
Share on other sites

Slice test version should contain: "Args: -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.11.6 | XCODE: 7.3.1".

Yes, \EFI\Clover\CLOVERX64.efi should be same with \EFI\BOOT\BOOTX64.efi

To check your Clover path / booted from:

0:100  0:000  SelfDevicePath=PciRoot(0x0)...

0:100  0:000  SelfDirPath = \EFI\BOOT

Thanks @cecekpawon

 

Attached preboot files in post #14809 are correct. But r4243 don't work in my system despite Slice test version. Downgrade to 4223 version, my system work.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By rtke333
      Acer Aspire V15 V5-591G - Mojave 10.14.4
       
      (Note: mine is 55TU version, but the bootpack will work fine with another versions of 591G, for example: V5-591G-71K2, -764Z, -59PU, etc.)
      Specifications:
      - Motherboard: USOPP_SLS (Skylake-H PCH)
      - BIOS:Insyde Corp. v 1.15
      - CPU:Intel Core i5-6300HQ 2.3 GHz (Skylake)
      - GPU: NVIDIA GeForce GTX 950M 2 GB (Optimus) & Intel HD Graphics 530
      - RAM:SK hynix 4 GB DDR4 (Later I bought + KINGSTON 4 GB) 2133 MHz
      - WiFi + Bluetooth:Qualcomm Atheros QCNFA344A 5 GHz (Later -> Broadcom BRCM94352Z M.2 5 GHz WiFi + 4.0 Bluetooth)
      - Audio:Realtek HD Audio: ALC 255 
      - Ethernet: Realtek RTL8168/8111
      - Card Reader:Realtek USB 2.0 Card Reader (USB2.0-CRW)
      - Webcam:HD Webcam
      - HDD:TOSHIBA MQ01ACF032 320 GB HDD
      - SSD:SPCC M.2 230 GB SSD
      - Display:1366x768 (15.6", Matte)
      - Battery: 6 cell 56Wh / 5040mAh
      - Connectors: 
      1x SD Card Reader 2x USB 3.0 (1x USB Charging), 1x USB 2.0 1x VGA 1x HDMI 1x 3.5mm microphone/audio combined jack connector 1x Ethernet (Rj-45) - Keyboard & Touchpad:Multi-Touch & Multi-gestures ELAN 501 Touchpad, Backlight Keyboard.
      Working:  
      - Wi-Fi (with BCM94352Z)
      - Bluetooth hand-off (With BCM94352Z)
      -Full Graphics enabled on HD 530: ig-platform-id: 0x191b0000 (HD 530 Mobile)
      - Display: if default colour profile is corrupted (blue is not actual blue but purplish) Use "Rec. ITU-R BT. 709-5" Color Profile (System Pref. -> Displays -> Color)
      -HDMI & VGA Outputs: AppleGraphicsDevicePolicy.kext Clover patch
      - Audio (ALC 255):(Internal Speakers, Internal Microphone, Headphone jack with AppleALC, ALCPlugFix -> layout-id=17)
      - Ethernet Realtek 8168/8111: RealtekRTL8111.kext
      - App Store, Messages, FaceTime, Siri, iCloud(native)
      - Integrated webcam(native)
      - 3.0 USB (native)
      - Touchpad and Keyboard(ELAN501): Fn keys are good, the weird thing is the Brightness key. On my keyboard it's Pause Break:Br-up, Fn+F12:Br-dwn-> To fix this try Karabiner (VoodoPS2Controller.kext), - for gestures try SmartTouchpad drivers
      - Battery info:Install ACPIBatteryManager.kext with Kext Utility or other installer.
      - Sleep Mode
      - SSD with TRIM enabled (to enable trim, open Terminal and write "sudo trimforce enable")
      Not working:
      - Original Wi-Fi (Qualcomm Atheros QCNFA344A):  unsupported, you need switch to BCM94352Z or just use a mini usb wifi dongle.
      - NVIDIA GeForce GTX 950M: Optimus not supported.
      - Card Reader: Unsupported -> Can't really fix because I don't have any SD Card at the moment, maybe can be fixed by adding Prod & Ven IDs to AppleStorageDevices.kext, I never used it anyway. name: "USB2.0-CRW" Prod ID: "0x0129" Ven ID: "0x0bda  (Realtek Semiconductor Corp.)"
      For Wi-Fi:
      - 1st method:You can choose an external USB wifi dongle (I used TP-Link Archer T1U (5GHz support), TP-Link has official macOS drivers, you just need to install it
      -2nd and I think the best method:Replace your M.2 Qualcomm Card with a compatible BCM94352Zcard (you will have hand-off Bluetooth too), just install the kexts (enabled with BrcmFirmwareData.kext, BrcmPatchRAM2.kext, FakePCIID.kext, FakePCIID_Broadcom_WiFi.kext, they're all in my attached zip). You could buy this card from ebay, aliexpress, or amazon
       
      Issues:
      - None
      BIOS Settings:
      - BIOS version 1.15 (irrelevant)
      - Secure Boot: Disabled
      - Touchpad: Advanced
      - Boot mode:UEFI
      Getting ready for Installation:
      - Download the install zip (bootpack & postinstall): Click here -> acer_aspire_v591g_installfiles.zip
      Installation:
      - Create an installer with any method you know (- Mac: createinstallmedia - Windows: Transmac, Vmware, Win32diskimager)
      - Copy my Clover folder to the USB's EFI folder
      - Boot with the Installer USB
      - If you stuck in boot, reboot and in the Clover bootloader select "config_debug.cfg" -> you'll have more informations about the freeze
       
      Please open the README.rtf in my install zip for more informations about the USB Installer & Post installation!
      If you have a single RAM and getting panic at boot, then you need to edit the "config.plist" with these (SMBIOS->after "Version 1.0"):
      ->Edit "Frequency" and "Size" to match your RAM values
      <key>Version</key> <string>1.0</string> <key>Memory</key> <dict> <key>Channels</key> <integer>1</integer> <key>SlotCount</key> <integer>1</integer> <key>Modules</key> <array> <dict> <key>Slot</key> <integer>0</integer> <key>Size</key> <integer>8192</integer> <key>Frequency</key> <integer>2133</integer> <key>Type</key> <string>DDR4</string> </dict> </array> </dict> </dict>  
      PowerManagement  fix:
      Set HWPEnable=YES in Clover (already set), CPUFloor to "700", Frequency to "2300" and "3200"(Normal and Turbo, if you have i7-6700HQ version then it should be "2600", "3500") and "FrequencyVectors" from "0x0d000000" to "0x07000000" in "S/L/E/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources/Mac-A5C67F76ED83108C.plist", MSR _xcpm_idle Patch to KernelToPatch in Clover (If you have High Sierra, change "MatchOS" to 10.13):

      <key>KernelToPatch</key> <array> <dict> <key>Comment</key> <string>MSR 0xE2 _xcpm_idle instant reboot(c) Pike R. Alpha</string> <key>Disabled</key> <false/> <key>Find</key> <data> ILniAAAADzA= </data> <key>MatchOS</key> <string>10.14</string> <key>Replace</key> <data> ILniAAAAkJA= </data> </dict> </array> Reboot, and it's 800MHz in idle state, same on Windows.
       

       
      Before updating to a new version of Mojave please update kexts (and clover if necessary) to newer versions to avoid kernel panics.
      Generate a serial number with Clover Configurator.app (open up your config.plist with CC then -> SMBIOS -> Serial Number -> Generate New)
      Mojave & Windows 10 Dual-Boot:
      Dual-boot clean install (on one drive), UEFI Only:
       
       Boot into your Mac installer, Create 2 partitions in GUID table (1 for Win (I used FAT32 but I think it doesn't matter what you choose), 1 for Mac),   Install Mac, boot with your USB, mount your EFI partition (use terminal or an EFI mounter app), create an EFI folder (if there is no folder), copy the CLOVER folder I attached to the EFI folder, restart,  Boot into your Win installer, Format the partition you created for Win, install.   Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       5.  You're done! It will booting into Clover when you start the system, and you can select Win or Mac (or another OS if installed on a 3rd partition).
       
      Dual-boot with Windows installed first (on one drive), UEFI Only:
      If you already have Windows and you don't want to lose all your data there is a hope:
      I created a video from this restore method: [Hackintosh] Dual-Boot High Sierra & Windows - when Windows already installed - no data waste - UEFI
      You need bootable Mac Installer and a full system restore image (link is in my video's description).
      (You may see errors if your EFI partition is not 200 MB)
       Boot into your Windows, resize your partition or create one for Mac.  Boot into your Mac installer and in Disk Utility format the partition you created.  Restore from image: select your full system restore image.  When it's finished restoring you just need to restart, then boot to the system with your usb.  When you successfully booted to Mac desktop, mount your EFI partition (use terminal or an EFI mounter app), open EFI, you will see there is a Microsoft folder already (don't touch that!). Copy my CLOVER folder to the EFI folder then Restart.  Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       7.  You're done! You can select your old Windows and your new macOS!
      (Only tried with Windows 8/8.1/10. I don't know Windows 7,etc.)
       
      IF YOU GETTING ERRORS DURING MAC RESTORE:
      - Make sure you have partitions in GPT
      - Windows using 100 MB EFI and will annoy the Mac restore. Don't worry, just ignore the errors.
       
      IF YOU GETTING ERRORS DURING WINDOWS INSTALLATION (could not be formatted, etc):
      - Make sure you have GPT partitions, and GPT (UEFI) installer, also disconnect all external storage drives (except the installer USB)
       
      IF YOU USED RESTORE METHOD THEN CAN'T MOUNT YOUR EFI PARTITION (No EFI partition found):
      - It's because your EFI is not 200 MB or not an "Apple" original EFI,  but do not worry, try another EFI mounter, or mount from terminal (I used EFI mounter v3: Getting errors, but you can mount and use without problem)
      - You also could "mount" the EFI from Windows:
      1st method: open cmd in administrator mode and type:
      diskpart
      list vol (Now select the "System" volume,(FAT 32) For example I select 4)
      sel vol 4
      list part(Select System type partition, for example 2)
      sel part 2
      assign letter=b(This will "mount" your EFI partition)
      Open Explorer++ or TotalCommander in administrator mode to manage EFI
      remove letter=b (This will "unmount" your EFI)
      2nd method: open cmd in administrator mode and type:
      mountvol b: /s (This will mount your EFI)
      Open Explorer++ or TotalCommander in administrator mode to manage EFI
      mountvol b: /d (This will unmount your EFI)
      Thanks to all OSXLatitude members for helping me out! (Jake Lo, Hervé, Bronxteck, black.dragon74)!
      Notes:
      2019.03.30: Fixed USB 3.0 ports, fixed Bluetooth crashes after sleep -> updated bootpack
      2019.03.28: Updated to 10.14.4. Unexpected crashes while updating to 10.14.4 -> fixed by updating Clover to the latest (v4910) version. Bluetooth crashes appeared -> fixed by downgraded Brcm*.kexts. Updated bootpack.
      2019.02.24: Bluetooth crashes after sleep -> fixed, updated bootpack. 
      2019.02.22: Updated to 10.14.3. Fixed HDMI Audio by installing "FakePCIID_Intel_HDMI_Audio.kext" -> fixed freezing during boot. Fixed brightness levels by installing "AppleBacklightFixup.kext". Also updated bootpack & postinstall zip down in attachments.
      2019.01.21: Removed FakeSMC.kext, SMCHelper-64.efi, replaced by VirtualSMC.kext, VirtualSMC.efi because I got random freezes when booting system (kextd stall[0], (120s): 'AppleACPICPU' -> CPU is at 100%, fans are spinning fast), also updated bootpack in the attachments "acer_aspire_v591g-55tu_clover.zip"-> Freeze continued, brought back FakeSMC, deleted VirtualSMC (caused BT crashes).
      2019.01.18: HDMI Audio is fixed, I didn't do anything HDMI Audio is not fixed, sometimes it worked but most likely not. (no idea why)
      2018.12.09: Updated to 10.14.2 -> did without any complication
      2018.11.28: Fixed combo-jack garbage sound output by installing ALCPlugFix and CodecCommander.kext
      2018.11.01: Updated to 10.14.1 -> HDMI & VGA ports are gone again. -> Fixed by "AppleIntelSKLGraphicsFramebuffer.kext" rollback from 10.14.
      2018.09.28: Updated to Mojave 10.14 -> Fixed HDMI & VGA Outputs by adding "AppleGraphicsDevicePolicy.kext" patches to config.plist, HDMI audio not working
    • By ciriousjoker
      TLDR:
      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.
      Available ports:
      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:
      Chameleon attempts:
      Only selected setting was "Install chameleon on the chosen path", rest was unselected.
       
      1 - Install chameleon first without restoring the basesystem:
      Output:
      > 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:
      Output:
      > 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".
       
      Clover attempts:
      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!
      Chameleon_Installer_Log_BEFORE.txt
      Chameleon_Installer_Log_AFTER.txt





    • By outdoormagic
      Short Version:
      I have two drives with the exact same EFI folder (and I can boot into Clover from either one), shouldn't I be able to boot into MacOS from either one?
       
      More Detail:
      I've done a few hacks so far and this never happened. (Gigabyte z370 / 8700k / Vega, Asus z390 / i5-9600k / 1080). Now, I'm setting up a ThinkPad X1 Gen 6. (Yes, I do expect problems on laptops, but that's not the question).
       
      Mojave 10.14.4 now boots from the internal SSD. So far, so good. Here's the problem.
       
      I installed Mojave on a USB drive (for backup / rescue) and copied the entire EFI partition of my boot drive to the EFI partition on the USB drive. So... I should be able to boot from the USB drive, right? Wrong. Ran Clover installer on the USB itself. Same outcome.
       
      With F12, I can boot from the USB into Clover and select the OS on the USB. The boot sequence hangs on End Random Seed, but before the usual '++++++++' line.
      So, boot into Clover on internal boot drive, then select OS on USB. Same thing.
       
      Read the forums, I saw the posts about AptioMemoryFix, so I tried the various other drivers on the USB. No go.
       
      I haven't found the solution yet to the USB boot issue, but what puzzles me is that if I have two drives with the exact same EFI folder (and I can boot into Clover from either one), shouldn't I be able to boot into MacOS from either one?
       
       
×