Jump to content
ErmaC

Clover General discussion

19,030 posts in this topic

Recommended Posts

Advertisement

Hey where have you been? Thanks.. I thought it was just me. AptiofixV1 had no problem to boot with -x here :)

The life of pre-university is kind of busy so I hardly get an appropriate time to visit IM... Fortunately it's now about to be the vacation. :)

Oh yes, but you have to disable SIP NVRAM Protection/Restriction (CsrActiveConfig = 0x40) with AptioFix v1.

Share this post


Link to post
Share on other sites

@Slice,

 

Can you please build a new package for sf.net because of new AptioFix?

 

 

OK, but I not sure that all correct because I am not at home.

Share this post


Link to post
Share on other sites

Nah, hibernation just wasn't fixed with the changes though I'm not sure it's exactly fixed correctly now. There is not going to be MORE AptioFix that's for sure, trying to get rid of them all but one. Stop trying to make more. Stop it. Stop. Please. Stop. I beg of you.

 

 

OK, but I not sure that all correct because I am not at home.

 

Ah yes, it has issues but no more than it already did. Just different ones. It should be cool now though, except the hibernation memory handoff. I'm pretty sure that there's still a problem there....

Share this post


Link to post
Share on other sites

Can anyone help with this panic on a 10.13.2 install? First startup (I cloned a working install to it). I tried dropping MATS and some other tables, but no luck.

Is there a way I can check my tables to see which one is causing this problem? Or is it something else entirely?

FakeSMC is 6.25.

 

Also, does Inject EDID work in Clover if you do not have AMD/Nvidia/Intel injection set to True?

 

Thanks!

 

post-358090-0-34355300-1515270682_thumb.jpg

Share this post


Link to post
Share on other sites

Looks like the same problem, try adding config.plist/DSDT/Fixes/FixHeaders=true.

 

Thanks. I should have tried that earlier.

That gets me past it. Now to figure out my bizarre EDID issue, or whatever it is.

 

When I run ioreg -l | grep "IODisplayEDID" , I get no output.

 

I have the below in my config. What I am doing wrong that the OS is not seeing that EDID?

<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<true/>
		</dict>
		<key>EDID</key>
		<dict>
			<key>Inject</key>
			<true/>
			<key>Custom</key>
			<data>AP///////wBMo08xAAAAAwAZAQS1Hyp4Cg+VrlJDsCYPUFQAAAABAQEBAQEBAQEBAQEBAQEB+anKZIC4VrAYEFUAKo0RAAAYAAAAAQAAAAAAAAAAAAAAAAAAAAAA/gBTQU1TVU5HICAgICAgAAAA/gBMVE0yODJSTDAxICAgAEg=</data>
			<key>VendorID</key>
			<string></string>
			<key>ProductID</key>
			<string></string>
		</dict>
		<key>NvidiaSingle</key>
		<false/>
	</dict>

Share this post


Link to post
Share on other sites

Problem with Clover r4368 on Skylake-X/X299 with SMBIOS iMacPro1,1

 

After updating Clover to r4368, I get a KP at boot (see attached image). 

 

The guilty might be FakeSMC.kext..

 

Any solution?  

post-1362934-0-38733100-1515284947_thumb.png

Share this post


Link to post
Share on other sites

I assume you're using AptioFix1... to use AptioFix1, update to r4369 or switch to using AptioFix2.

 

Yes, I use OsxAptioFixDrv-64.efi + Test2-2016.efi..

 

Switched now to Clover r4369... 

 

Everything works again as expected.. Many thanks for the extremely useful hint. 

 

However, like in Clover r4366, I am not able to boot the 10.13.2 USB Flash Drive Installer with SMBIOS iMacPro1,1. 

 

Guess the problem is however not Clover.. The problem might be that the iMacPro BoardID and iMacPro1,1 ModelProperties are not part of the PlatfromSupport.plist of the macOS 10.13.2 Installer Package. 

Share this post


Link to post
Share on other sites

Yes, I use OsxAptioFixDrv-64.efi + Test2-2016.efi..

 

Switched now to Clover r4369... 

 

Everything works again as expected.. Many thanks for the extremely useful hint. 

 

However, like in Clover r4366, I am not able to boot the 10.13.2 USB Flash Drive Installer with SMBIOS iMacPro1,1. 

 

Guess the problem is however not Clover.. The problem might be that the iMacPro BoardID and iMacPro1,1 ModelProperties are not part of the PlatfromSupport.plist of the macOS 10.13.2 Installer Package. 

 

They are not supported fully yet. But you should not be using those two drivers together, ever. Please remove those two drivers and use only the newest revisions AptioFix2. You may need to add a slide=N argument if it doesn't find a region to place the kernel.

Share this post


Link to post
Share on other sites

They are not supported fully yet. But you should not be using those two drivers together, ever. Please remove those two drivers and use only the newest revisions AptioFix2. You may need to add a slide=N argument if it doesn't find a region to place the kernel.

 

Is there any reason why I should not use these two drivers together with Skylake-X/X299? They work absolutely flawless, while AptioFix2 still leads to occasional memory allocation errors at early boot... 

Share this post


Link to post
Share on other sites

Is there any reason why I should not use these two drivers together with Skylake-X/X299? They work absolutely flawless, while AptioFix2 still leads to occasional memory allocation errors at early boot... 

 

You should try using just AptioFix2 with r4369. It should work. The memory allocation error is another issue, it should not happen as often now as not as much will be needed without relocating runtime. That's due to firmware memory fragmentation. The reason not to use the two drivers is because first they are meant to only be used alone. Second, the one not named AptioFix just deletes random memory below a certain address with no idea what the memory is used for...

Share this post


Link to post
Share on other sites

You should try using just AptioFix2 with r4639. It should work. The memory allocation error is another issue, it should not happen as often now as not as much will be needed without relocating runtime. That's due to firmware memory fragmentation. The reason not to use the two drivers is because first they are meant to only be used alone. Second, the one not named AptioFix just deletes random memory below a certain address with no idea what the memory is used for...

 

O.k. thanks for the details.. I will try to use AptioFix2 with the slide boot flag.. Without this boot flag I get a print,f error at early boot... slide=0 is fine or do I really have to use slide=N?   

Share this post


Link to post
Share on other sites

O.k. thanks for the details.. I will try to use AptioFix2 with the slide boot flag.. Without this boot flag I get a print,f error at early boot... slide=0 is fine or do I really have to use slide=N?

 

Once you get into the clover GUI, you need to go into the EFI shell and use the memmap command find the available region that has the largest space and calculate the slide value. You do that by taking the address of the region you found, subtract 0x100000 then divide by 0x200000. Now you have the slide value, you must make sure it is good. Do the calculation 0x100000 + (slide * 0x200000). That should give you the same address of the free area, if not add one to the slide or find another region and repeat.

 

EDIT: It's also ok if address calculated with the slide just offsets slightly into the region as long as there is still enough space for the kernel to load, usually around 0x12000 pages is good enough.

where do I get r4639?

I guess that's just a typo.. I guess it should properly read r4369...

 

Yes it's a typo, I fixed it, meant r4369.

Share this post


Link to post
Share on other sites

We were just revising some AptioFix stuff...

https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/OsxAptioFixDrv/Lib.c#l380

 

Are there any real technical details on this?

1) There is no source for the range... or a description of what the issue even is.

2) The kernel treats Reserved (that's what I expect it to be... or isn't it?) the same way as it treats ACPI_NVS afaik (please correct me if wrong... with sources).

3) The kernel only uses EFI_MEMORY_RUNTIME and some other, proprietary one, so setting it to 0 should have no effect, if the region there does not have RT set.

 

tyvm

Share this post


Link to post
Share on other sites

We were just revising some AptioFix stuff...

https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/OsxAptioFixDrv/Lib.c#l380

 

Are there any real technical details on this?

1) There is no source for the range... or a description of what the issue even is.

2) The kernel treats Reserved (that's what I expect it to be... or isn't it?) the same way as it treats ACPI_NVS afaik (please correct me if wrong... with sources).

3) The kernel only uses EFI_MEMORY_RUNTIME and some other, proprietary one, so setting it to 0 should have no effect, if the region there does not have RT set.

 

tyvm

 

Because he wants to get rid of that region, he set it to a type and attribute he knew would be ignored by the kernel, it has to do with like the first generation of pure UEFI gigabyte boards. I seem to recall some stupid region being there. Not sure why we want to get rid of reserved areas before that though, probably need those and might explain why HD3000 has some issues. It may be because they need to be rwx... But there's gotta be a better solution than just disappearing it. I'm not a big fan of just disappearing memory like it's a mobster with cement shoes.....

Share this post


Link to post
Share on other sites

Because he wants to get rid of that region, he set it to a type and attribute he knew would be ignored by the kernel, it has to do with like the first generation of pure UEFI gigabyte boards. I seem to recall some stupid region being there. Not sure why we want to get rid of reserved areas before that though, probably need those and might explain why HD3000 has some issues. It may be because they need to be rwx... But there's gotta be a better solution than just disappearing it. I'm not a big fan of just disappearing memory like it's a mobster with cement shoes.....

 

Are you sure that the issue you are remembering is not the one above, by dmazar? That was discussed on POSX in 2012. That "sleep fix" is rather new

Share this post


Link to post
Share on other sites

Are you sure that the issue you are remembering is not the one above, by dmazar? That was discussed on POSX in 2012. That "sleep fix" is rather new

 

Which one? I said two different things. The first was slice adding that because he had a gigabyte board that has that weird region and needed it removed I guess, I think the lines commented below that are also from him. The other, the reserved regions is dmazar, and I was just wondering why he disappeared a reserved region for the GPUs. I did not use different nouns for either of them so it reads weird... lol.

 

EDIT: I don't remember exactly what the conversation about it from 2012 was. But looking at it now, I think it was a mistake to not try fix the region instead of destroying it.

Share this post


Link to post
Share on other sites

Which one? I said two different things. The first was slice adding that because he had a gigabyte board that has that weird region and needed it removed I guess, I think the lines commented below that are also from him. The other, the reserved regions is dmazar, and I was just wondering why he disappeared a reserved region for the GPUs. I did not use different nouns for either of them so it reads weird... lol.

 

EDIT: I don't remember exactly what the conversation about it from 2012 was. But looking at it now, I think it was a mistake to not try fix the region instead of destroying it.

 

Nah, I just don't remember there ever being any talk about that sleep fix... in fact it was added a commit doing mostly unrelated stuff, it's not even mentioned in the log lol.

 

Anyway, if you are at your dev setup dmazar's workaround should be changed to changing the region to MMIO (which was proven to work back then too), The issue was probably boot.efi ignoring RT Reserved, so not assigning a virtual address, and the kernel then trying to map it, which of course blows up. MMIO ensures it stays in the same physical location, is not cached (we don't know what it is used for after all...) and gets a valid vAddress.

Share this post


Link to post
Share on other sites

Nah, I just don't remember there ever being any talk about that sleep fix... in fact it was added a commit doing mostly unrelated stuff, it's not even mentioned in the log lol.

 

Oh, there was no talk of it. He just did it. I seem to recall one day he said something and then it was done. I don't think it really affects anything but it should probably be a little more precise....

 

EDIT: Maybe it could possibly even be removed now, after the newest changes.

 

Anyway, if you are at your dev setup dmazar's workaround should be changed to changing the region to MMIO (which was proven to work back then too), The issue was probably boot.efi ignoring RT Reserved, so not assigning a virtual address, and the kernel then trying to map it, which of course blows up. MMIO ensures it stays in the same physical location, is not cached (we don't know what it is used for after all...) and gets a valid vAddress.

 

Yeah, that's what I meant, I don't know why he just destroyed the region. But it could need to be rwx like I said and we both know that the kernel doesn't seem to want to allow that. His comments around the commented out stuff don't make sense though... He says that MMIO blocks during DefragmentRuntimeServices, but why would that be the case? Maybe he just switched the comments wrong. Now I want to see what actually does work since I have an HD3000. Except it currently doesn't work in clover because the injection is broken.... Grrr.

Share this post


Link to post
Share on other sites

Btw. maybe offtopic, but I never was able to properly use the Intel HD4600 next to a AMD or nvidia gfx, using it as a secondary OpenCL processor: On 10.9 it caused visual graphics glitches in Maps.app, in 10.12+10.13 it works in Maps.app, but final Cut will crash.  Luxmark works.  Maybe this is related to some memory mapping problem, too?

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

  • Similar Content

    • By Gorec
      Hi.
      I apologize in advance if I didn't post in the right category and if my title and description aren't specific enough :c
       
      My config in a nutshell:
      CPU: i7 5820k GPU: MSI GTX 1060 3GB RAM: 16 GB MOBO: MSI X99 SLI PLUS I attached RunMe output with all the details of my built.
       
      Some background:
      I have my Hackintosh for about half a year. That time I managed to make it works and fix major issues, but some of them left unresolved since then and I ignored them until now.
      I use my Hackintosh for Adobe projects (PR, AE, PS, IL, AU and a lot more) - most of them connected with video editing of course browsing with Chrome and other small tasks.
       
      Problems:
      Random restarts - this is the biggest one. I'm starting to work on bigger and bigger projects and at this time I think I can't allow this to happen that often. In the past, they happened like once a day or a couple of times a week. However, now it's just frustrating when it happens even 5 or more times a day. I've tried to observe and find out what can be the cause but I haven't managed to find any connections. I thought it happens when Premiere or another app is using GPU, but I haven't seen increased usage when it restarts. I think that it can be connected with GPU, memory or PSU or... meh, anything else. I don't have resources to check if it'll work with other components. There should be some fix for this. I will really appreciate any help with this :c Restart instead of shutdown & sleep doesn't work. I've tried to look through some Google results for this and tried many solutions (as you can see in attached Clover folder), but I think the right one for many of these issues is to make my own DSDT. Glitches, freezes and other things while encoding a video. It happens very often when I try to do this. Maybe it is an issue with GPU or (hopefully) only with GPU drivers which can be fixed with some patch. Today my headphones stopped working. I have a multi-output device configured in the Audio MIDI Setup app which includes my headphones (HyperX Cloud via USB) and Soundflowerbed virtual audio device for capturing system audio. Today while I was trying (like 15 times) to encode a video in Media Encoder in the background and watch video on YouTube I stopped hearing anything from my system. Of course, it restarted a couple of times as always, but even this didn't solve this. If I plug them directly with mini jack (not via USB Soundcard which was in the box and which I always used) in the front IO or the back I only hear some loud noise It takes EX-Fat formatted volumes a few minutes to mount after each restart. I found a workaround to format it with NTFS since I have Tuxera installed and I will reformat these volumes when I will find time for this, but maybe there is some fix for this. GPU is a little bit hot. HW Monitor shows it is only 45-55 degrees, but for my hand is a little bit hot, idk. Also related to GPU - glitch after POST but before entering Clover boot menu. It is a black screen with little white squared glitches for a few seconds. Maybe it indicates the GPU drivers are loading, but maybe it shouldn't be like this. And if I can ask about that - I can't make all applications hide on startup. I, obviously, have "Hide" checkbox checked on every login item in settings, but it doesn't work, none of the apps is hidden in the dock. Is there a way to fix this? Also a small but annoying problem - I can't turn off permanently Mojave update notification (since I tried to install it, and I had to reverse to High Sierra because I had a black screen and I didn't have time for repairing all of them. Tags are not working in Finder - every time I tag a file or folder and make a change in it (for example save a text file) the tag disappears.  
      So, with knowing all of that, is there a way to make a proper DSDT file for my Hackintosh? I tried to look through some guides on how to make it but I think I reached my abilities to understand how Mac OS works and what all of these things are, so I'm asking you guys politely, would someone like to help me? At least with these random restarts? :/
      I really begin to think that I'm a newbie in configuring all of that Clover things - even after what I managed to do with my PC. Help me, pleease... :c
       
      If you have any questions post it below, I will really appreciate any help <3
      Send me MBP-Gorec.home.zip
    • 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?
       
       
×