Jump to content
ErmaC

Clover General discussion

18,955 posts in this topic

Recommended Posts

Advertisement

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?

 

Well it's hard to say, it could be, or it could have just been bugs in the driver. Or flawed injection. Or bad configuration. Or a million other things.... But I'd probably put the odds that yes, just destroying reserved regions for the graphics is probably not a good idea and causes problems....

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?

 

OMG, this AptioFix V1 makes HD4600 + nvidia work in final cut!

Share this post


Link to post
Share on other sites

 

OMG, this AptioFix V1 makes HD4600 + nvidia work in final cut!

 

Please try r4369 AptioFix2.

I WANT TO DESTROY APTIOFIX1! I NEED YOU TO NOT USE IT!!! TEST APTIOFIX2!!!!!!!!!! OBEY YOUR OVERLORDS!!!!!!!! I have taken too much medicine....

OsxAptioFix2Drv-64.efi

Share this post


Link to post
Share on other sites

@Slice, 

 

Hey, sorry for the premature packaging... lol. But there was a problem with r4368, can you please remove that package and make r4369 newest package?


Lol. Yes, that one works nicely, too!

 

Yes this is what I want to hear. FROM EVERYONE.  :surprised:

 

EDIT: Use AptioFix2 then.

Share this post


Link to post
Share on other sites

@Slice, 

 

Hey, sorry for the premature packaging... lol. But there was a problem with r4368, can you please remove that package and make r4369 newest package?

 

Yes this is what I want to hear. FROM EVERYONE.  :surprised:

 

EDIT: Use AptioFix2 then.

i always use AptioFix2 and no problems..

Share this post


Link to post
Share on other sites

on my system, x99, aptiofix2 would not boot without slide=128, without it, does printf work?

aptiofix 1 is ok.

 

Yes you need to enter a slide value sometimes to get AptioFix2 to work. Maybe it should be modified to determine that on it's own. I want to obsolete AptioFix.... Make AptioFix2 the one method to rule them all! Also rename it.... lol

 

EDIT: Test the newest AptioFix2 and see what the result is. Using a slide is not a big deal, it's done anyway to place the kernel.

 

i always use AptioFix2 and no problems..

 

The newest AptioFix2 from r4369 should be very different than the previous and should give you very close to 100% working system besides a few caveats that still need fixed but I want to get rid of AptioFix and rename AptioFix2 to something more appropriate. There should not be a need for AptioFix anymore as AptioFix2 should be sufficiently modified to work for every system. Or at least I hope.

Also everyone testing this driver, if you have EmuVar driver remove that because you should have working NVRAM.

Share this post


Link to post
Share on other sites
I want to get rid of AptioFix and rename AptioFix2 to something more appropriate. There should not be a need for AptioFix anymore as AptioFix2 should be sufficiently modified to work for every system. Or at least I hope.

 

That may be a good idea. Here I currently have a private copy of AptioFixV2, which I slightly refactored and cleaned from legacy & AptioFixV1 code.

In addition to that, as Fritz mentioned above, we slowly walked through some fixes and additions and discovered potential issues & dead code. 

I am not sure that it will be seriously changed any further (I will probably not do proper hibernation handoff), but if the cleaned code is proven to work with time I will share it.

Share this post


Link to post
Share on other sites

Hm, nvidia + hd4600 works, but in recent Firefox, 1080p60 youtube videos will stop sometimes (not so using nvidia only). Unsure if it is a Firefox issue or some kind of latency / synchronisation issue?  Luxmark showed better results with both enabled (8960 vs. 7275)

Share this post


Link to post
Share on other sites

Yes you need to enter a slide value sometimes to get AptioFix2 to work. Maybe it should be modified to determine that on it's own. I want to obsolete AptioFix.... Make AptioFix2 the one method to rule them all! Also rename it.... lol

 

EDIT: Test the newest AptioFix2 and see what the result is. Using a slide is not a big deal, it's done anyway to place the kernel.

 

where can i get the newest AptioFix2 ? im using r4369, is it the newest ?

how can i figure what slide value is proper for my system? is 128 ok ?

Share this post


Link to post
Share on other sites

Hm, nvidia + hd4600 works, but in recent Firefox, 1080p60 youtube videos will stop sometimes (not so using nvidia only). Unsure if it is a Firefox issue or some kind of latency / synchronisation issue?  Luxmark showed better results with both enabled (8960 vs. 7275)

 

It's hard to say, I think that some code needs refactored or removed from the fix as it no longer is relevant and some decisions made years ago are no longer viable or were never viable, where we decided working was better than not.... I have a feeling that the code DF and I were just talking about plays a big part in intel GPUs problems that seem to appear. Like HD3000 artifacts/sync issues and HD4000+ HDCP issues.

where can i get the newest AptioFix2 ? im using r4369, is it the newest ?

how can i figure what slide value is proper for my system? is 128 ok ?

 

I posted it a few posts back but r4369 is newest. I also gave method for determining slide if needed a few posts ago.

 

Care to share??

 

I posted mostly the same driver a few posts ago. He meant he just cleaned it up, refactored, and removed some stuff not needed, I imagine he will release it when it's ready, like he said.

Share this post


Link to post
Share on other sites

4369 released.

@all, please more comments about changes:

1. Sleep/Wake (mode=0)

2. Hibernation (mode=25)

3. NVRAM without EmuVariableUefi

4. Intel graphics artefacts.

 

Runtime code areas are no longer allowed to be relocated by boot.efi like runtime data areas. Runtime methods for NVRAM variables are shimmed to enable writing into runtime code regions during the methods, then disabled upon return. Native NVRAM should work for everyone now. Sleep/hibernation has been a discussion, unsure, it may be broken, but fixable? That will be a longer term evaluation, but I think we all pretty much agree that it is not correct and will need fixed (there may be an element of luck for success). The Intel graphics problem, not fixed, just discussed the removing of the reserved area for these GPUs and how it's probably a better idea to somehow preserve this region because why would it exist if it wasn't needed?

 

EDIT: Forgot, thanks for the package update.

Share this post


Link to post
Share on other sites

Yes you need to enter a slide value sometimes to get AptioFix2 to work. Maybe it should be modified to determine that on it's own. I want to obsolete AptioFix.... Make AptioFix2 the one method to rule them all! Also rename it.... lol

 

EDIT: Test the newest AptioFix2 and see what the result is. Using a slide is not a big deal, it's done anyway to place the kernel.

 

 

The newest AptioFix2 from r4369 should be very different than the previous and should give you very close to 100% working system besides a few caveats that still need fixed but I want to get rid of AptioFix and rename AptioFix2 to something more appropriate. There should not be a need for AptioFix anymore as AptioFix2 should be sufficiently modified to work for every system. Or at least I hope.

Also everyone testing this driver, if you have EmuVar driver remove that because you should have working NVRAM.

Desktop hack in sig.

I previously used EmuVar (for nvidia card) but with Clover 4369 i removed EmuVar and rebooted without issue.

GTX 960 working as it should.

NVRAM appears functional.

EDIT:

Maybe not

post-1083558-0-08816000-1515309405_thumb.png

Share this post


Link to post
Share on other sites

Desktop hack in sig.

I previously used EmuVar (for nvidia card) but with Clover 4369 i removed EmuVar and rebooted without issue.

GTX 960 working as it should.

NVRAM appears functional.

EDIT:

Maybe not

 

To test whether it is working go into terminal and use the command like

sudo nvram test="value"

Then restart and run

sudo nvram -p

And see if the test variable is there. You can then delete it:

sudo nvram -d test

If the variable is not there you do not have working NVRAM. Would need to get more info then.

Share this post


Link to post
Share on other sites

To test whether it is working go into terminal and use the command like

sudo nvram test="value"
Then restart and run
sudo nvram -p
And see if the test variable is there. You can then delete it:
sudo nvram -d test
If the variable is not there you do not have working NVRAM. Would need to get more info then.

NVRAM is functional. I used the code you provided and after reboot in NVRAM I see

test value

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

I posted it a few posts back but r4369 is newest. I also gave method for determining slide if needed a few posts ago.

you mean this ?

 

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.

 

i don't understand, im not programmer or coder

would you please to help me??

here is my memmap

 

Type       Start            End              # Pages          Attributes
Available  0000000000000000-000000000003EFFF 000000000000003F 000000000000000F
RT_Data    000000000003F000-000000000003FFFF 0000000000000001 800000000000000F
Available  0000000000040000-000000000009FFFF 0000000000000060 000000000000000F
Available  0000000000100000-000000000FFFFFFF 000000000000FF00 000000000000000F
BS_Code    0000000010000000-000000001000AFFF 000000000000000B 000000000000000F
Available  000000001000B000-00000000A562FFFF 0000000000095625 000000000000000F
LoaderCode 00000000A5630000-00000000A57B9FFF 000000000000018A 000000000000000F
LoaderData 00000000A57BA000-00000000A6EA2FFF 00000000000016E9 000000000000000F
BS_Data    00000000A6EA3000-00000000A6F22FFF 0000000000000080 000000000000000F
LoaderData 00000000A6F23000-00000000AD7A5FFF 0000000000006883 000000000000000F
BS_Data    00000000AD7A6000-00000000B97A5FFF 000000000000C000 000000000000000F
Available  00000000B97A6000-00000000B9A0FFFF 000000000000026A 000000000000000F
BS_Code    00000000B9A10000-00000000BA432FFF 0000000000000A23 000000000000000F
Reserved   00000000BA433000-00000000BB196FFF 0000000000000D64 000000000000000F
ACPI_Recl  00000000BB197000-00000000BB1F6FFF 0000000000000060 000000000000000F
ACPI_NVS   00000000BB1F7000-00000000BD3F7FFF 0000000000002201 000000000000000F
RT_Data    00000000BD3F8000-00000000BDC99FFF 00000000000008A2 800000000000000F
RT_Code    00000000BDC9A000-00000000BDD02FFF 0000000000000069 800000000000000F
BS_Data    00000000BDD03000-00000000BDD03FFF 0000000000000001 000000000000000F
RT_Data    00000000BDD04000-00000000BDD89FFF 0000000000000086 800000000000000F
BS_Data    00000000BDD8A000-00000000BDFFFFFF 0000000000000276 000000000000000F
Available  0000000100000000-000000083FFFFFFF 0000000000740000 000000000000000F
Reserved   00000000BE000000-00000000BEFFFFFF 0000000000001000 0000000000000000
MMIO       00000000E0000000-00000000EFFFFFFF 0000000000010000 8000000000000001
MMIO       00000000FED1C000-00000000FED44FFF 0000000000000029 8000000000000001
MMIO       00000000FF000000-00000000FFFFFFFF 0000000000001000 8000000000000001
 
  Reserved  :          7,524 Pages (30,818,304 Bytes)
  LoaderCode:            394 Pages (1,613,824 Bytes)
  LoaderData:         32,620 Pages (133,611,520 Bytes)
  BS_Code   :          2,606 Pages (10,674,176 Bytes)
  BS_Data   :         49,911 Pages (204,435,456 Bytes)
  RT_Code   :            105 Pages (430,080 Bytes)
  RT_Data   :          2,345 Pages (9,605,120 Bytes)
  ACPI_Recl :             96 Pages (393,216 Bytes)
  ACPI_NVS  :          8,705 Pages (35,655,680 Bytes)
  MMIO      :         69,673 Pages (285,380,608 Bytes)
  MMIO_Port :              0 Pages (0 Bytes)
  PalCode   :              0 Pages (0 Bytes)
  Available :      8,280,110 Pages (33,915,330,560 Bytes)
  Persistent:              0 Pages (0 Bytes)
              -------------- 
Total Memory:         32,722 MB (34,311,749,632 Bytes)

 

 

Share this post


Link to post
Share on other sites

NVRAM is functional. I used the code you provided and after reboot in NVRAM I see

test value
Sent from my SM-G930F using Tapatalk

 

 

Awesome.

 

you mean this ?

 

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.

 

i don't understand, im not programmer or coder

would you please to help me??

here is my memmap

 

 

Type       Start            End              # Pages          Attributes
Available  0000000000000000-000000000003EFFF 000000000000003F 000000000000000F
RT_Data    000000000003F000-000000000003FFFF 0000000000000001 800000000000000F
Available  0000000000040000-000000000009FFFF 0000000000000060 000000000000000F
Available  0000000000100000-000000000FFFFFFF 000000000000FF00 000000000000000F
BS_Code    0000000010000000-000000001000AFFF 000000000000000B 000000000000000F
Available  000000001000B000-00000000A562FFFF 0000000000095625 000000000000000F
LoaderCode 00000000A5630000-00000000A57B9FFF 000000000000018A 000000000000000F
LoaderData 00000000A57BA000-00000000A6EA2FFF 00000000000016E9 000000000000000F
BS_Data    00000000A6EA3000-00000000A6F22FFF 0000000000000080 000000000000000F
LoaderData 00000000A6F23000-00000000AD7A5FFF 0000000000006883 000000000000000F
BS_Data    00000000AD7A6000-00000000B97A5FFF 000000000000C000 000000000000000F
Available  00000000B97A6000-00000000B9A0FFFF 000000000000026A 000000000000000F
BS_Code    00000000B9A10000-00000000BA432FFF 0000000000000A23 000000000000000F
Reserved   00000000BA433000-00000000BB196FFF 0000000000000D64 000000000000000F
ACPI_Recl  00000000BB197000-00000000BB1F6FFF 0000000000000060 000000000000000F
ACPI_NVS   00000000BB1F7000-00000000BD3F7FFF 0000000000002201 000000000000000F
RT_Data    00000000BD3F8000-00000000BDC99FFF 00000000000008A2 800000000000000F
RT_Code    00000000BDC9A000-00000000BDD02FFF 0000000000000069 800000000000000F
BS_Data    00000000BDD03000-00000000BDD03FFF 0000000000000001 000000000000000F
RT_Data    00000000BDD04000-00000000BDD89FFF 0000000000000086 800000000000000F
BS_Data    00000000BDD8A000-00000000BDFFFFFF 0000000000000276 000000000000000F
Available  0000000100000000-000000083FFFFFFF 0000000000740000 000000000000000F
Reserved   00000000BE000000-00000000BEFFFFFF 0000000000001000 0000000000000000
MMIO       00000000E0000000-00000000EFFFFFFF 0000000000010000 8000000000000001
MMIO       00000000FED1C000-00000000FED44FFF 0000000000000029 8000000000000001
MMIO       00000000FF000000-00000000FFFFFFFF 0000000000001000 8000000000000001
 
  Reserved  :          7,524 Pages (30,818,304 Bytes)
  LoaderCode:            394 Pages (1,613,824 Bytes)
  LoaderData:         32,620 Pages (133,611,520 Bytes)
  BS_Code   :          2,606 Pages (10,674,176 Bytes)
  BS_Data   :         49,911 Pages (204,435,456 Bytes)
  RT_Code   :            105 Pages (430,080 Bytes)
  RT_Data   :          2,345 Pages (9,605,120 Bytes)
  ACPI_Recl :             96 Pages (393,216 Bytes)
  ACPI_NVS  :          8,705 Pages (35,655,680 Bytes)
  MMIO      :         69,673 Pages (285,380,608 Bytes)
  MMIO_Port :              0 Pages (0 Bytes)
  PalCode   :              0 Pages (0 Bytes)
  Available :      8,280,110 Pages (33,915,330,560 Bytes)
  Persistent:              0 Pages (0 Bytes)
              -------------- 
Total Memory:         32,722 MB (34,311,749,632 Bytes)

 

 

Is this the memmap from after you enter clover GUI and then use EFI shell? If so then, you're going to want to select this region because it has the most free pages below 0x100000000:

Available  000000001000B000-00000000A562FFFF 0000000000095625 000000000000000F

So to calculate the slide:

0x1000B000 - 0x100000 = 0xFF0B000
0xFF0B000 / 0x200000 = 0x7F

Now need to verify that will give a valid region:

0x7F * 0x200000 = 0xFE00000
0xFE00000 + 0x100000 = 0xFF00000 

0x7F is not valid slide because the address 0xFF00000 < 0x1000B000. Increase slide by one and recalculate:

0x80 * 0x200000 = 0x10000000
0x10000000 + 0x100000 = 0x10100000

0x80 is valid slide because it falls within the region, 0x10100000 >= 0x1000B000. Now calculate the remaining pages in region:

0x1000B000 + (0x95625 * 0x1000) = 0xA5630000
0xA5630000 - 0x10100000 = 0x95530000
0x95530000 / 0x1000 = 0x95530

The region has 0x95530 pages which is definitely more than 0x12000 pages (about ~300MB and usually the size of the kernelcache is less than that). So your slide is 0x80 or 128. Which you already knew but I guess I just mathematically proved for you. Did you try without setting any slide first? If that doesn't work use slide=128.

 

EDIT: Mixed up some numbers but fixed it.

EDIT2: If you get less than 0x12000 pages left over when you do this calculation then try another region and choose the one that yields the highest available pages.

EDIT3: If after you do this to every available region and none even come close to having 0x12000 pages then you have the fragmentation issue. You will have to fallback to AptioFix for now, until that issue is resolved.

EDIT4: Only increase the slide value once per region just because of alignment, move onto the next region after one increase.

Share this post


Link to post
Share on other sites

 

Awesome.

 

 

Is this the memmap from after you enter clover GUI and then use EFI shell? If so then, you're going to want to select this region because it has the most free pages below 0x100000000:

Available  000000001000B000-00000000A562FFFF 0000000000095625 000000000000000F

So to calculate the slide:

0x1000B000 - 0x100000 = 0xFF0B000
0xFF0B000 / 0x200000 = 0x7F

Now need to verify that will give a valid region:

0x7F * 0x200000 = 0xFE00000
0xFE00000 + 0x100000 = 0xFF00000 

0x7F is not valid slide because the address 0xFF00000 < 0x1000B000. Increase slide by one and recalculate:

0x80 * 0x200000 = 0x10000000
0x10000000 + 0x100000 = 0x10100000

0x80 is valid slide because it falls within the region, 0x10100000 >= 0x1000B000. Now calculate the remaining pages in region:

0x1000B000 + (0x95625 * 0x1000) = 0xA5630000
0xA5630000 - 0x10100000 = 0x95530000
0x95530000 / 0x1000 = 0x95530

The region has 0x95530 pages which is definitely more than 0x12000 pages (about ~300MB and usually the size of the kernelcache is less than that). So your slide is 0x80 or 128. Which you already knew but I guess I just mathematically proved for you. Did you try without setting any slide first? If that doesn't work use slide=128.

 

EDIT: Mixed up some numbers but fixed it.

EDIT2: If you get less than 0x12000 pages left over when you do this calculation then try another region and choose the one that yields the highest available pages.

EDIT3: If after you do this to every available region and none even come close to having 0x12000 pages then you have the fragmentation issue. You will have to fallback to AptioFix for now, until that issue is resolved.

thanks a lot,

i already tried without slide, "does printf work?" hang.

when i use this memmap, in my UEFI driver still aptiofix 1 not v2, it doesnt matter, right?

Share this post


Link to post
Share on other sites

thanks a lot,

i already tried without slide, "does printf work?" hang.

when i use this memmap, in my UEFI driver still aptiofix 1 not v2, it doesnt matter, right?

 

No, you should use AptioFix2 above AptioFix always. If AptioFix2 does not work even with slide value, then fallback to AptioFix. You should be good though with slide=128 with AptioFix2.

 

EDIT: Where is "does printf work??" even from? WTF? That's a weird message. Is that from boot.efi? I don't see where that's in clover....

Share this post


Link to post
Share on other sites

No, you should use AptioFix2 above AptioFix always. If AptioFix2 does not work even with slide value, then fallback to AptioFix. You should be good though with slide=128 with AptioFix2.

i only can boot with slide=128, i cant if slide=80

so, i must/should use aptiofix2 with slide=128 instead of aptiofix without slide arg?

Share this post


Link to post
Share on other sites

i only can boot with slide=128, i cant if slide=80

so, i must/should use aptiofix2 with slide=128 instead of aptiofix without slide arg?

 

No, you misunderstood I wrote 0x80 and 128, those are the same number just in hexadecimal and decimal. And yes you should use AptioFix2. It should probably be made to automatically calculate the slide if one is not given.

Share this post


Link to post
Share on other sites

No, you misunderstood I wrote 0x80 and 128, those are the same number just in hexadecimal and decimal. And yes you should use AptioFix2. It should probably be made to automatically calculate the slide if one is not given.

Please don't kill "random KASLR", thx ;p

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 Reel
      All work 10.10, 10.11, 10,12
      camera not work in 10.13, 10.14
      You need SwitchResX that the screen does not freeze
      Custom resolutions: Back porch - lines change to 2
      UEFI boot moded bios https://github.com/Thiblizz/l502x-modded-bios
       
      For 10.14 you need: HD3000 Fix for Mojave.zip
      Installed in S/L/E 
       
      SMBIOS: MacbookPro 8.3 or MacbookPro 9.1
       
       

       

       
       
    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
    • By SepehrM
      I'm trying to install High Sierra 10.13.3 on an ASUS N552VW laptop, and I get stuck after this message:
      "could not recover SATA HDD after 5 attempts, terminating" 
      And some other warnings afterwards.
      Specs:
      CPU: Intel Skylake 6700HQ 2.6GHz
      RAM: 16GB DDR4
      2TB HDD + 128GB SSD
      GPU: Intel HD Graphics 530 + Nvidia GTX960m
      I'm installing using a 16GB USB3 flash drive on one of HDD volumes (UEFI Mode)
       
      I uploaded the verbose log and clover config.plist
      config-new.plist

    • By RougeOne
      Budget Workstation MacOS 10.14.1 build: z370 AORUS Gaming 5 - i5-8600K - RX 580 - UHD 630
      flawless iGPU/dGPU integration, fast FCPX editing/rendering, great overall performance for ~$1200 / ~£1000
       
      Update: updated WhateverGreen and Lilu, then updated OS to 10.14.3 and everything is fine! Even iMessage, which previously I hadn't been able to make work, is now working - possibly the update flushed the NVRAM?
       
      I'm gonna come straight out and admit it - I used newb tools which are considered taboo on InsanelyMac, and so this isn't so much an installation guide as it is a green flag to anyone considering the same hardware. My first and previous Hackintosh project was just over ten years ago and this site was massively helpful, so this is my (very small) way of giving back.
       
      EFI DIRECTORY
      http://s000.tinyupload.com/index.php?file_id=97606131925137056003
       
      HARDWARE
      CPU: Intel i5-8600K 3.6GHz hexacore (contains UHD 630 iGPU)
      CPU Cooler: be quiet! Pure Rock Slim (no paste needed, and fan facing front)
      Mobo: GIGABYTE z370 AORUS Gaming 5 (WIFI)
      RAM: 1x 8GB CORSAIR Vengeance LPX C16 2666MHz (in first slot)
      GFX Card: Sapphire RX 580 NITRO+ SE
      SATA: used ports 0, 1, 3, 5 (HDD problems when connected to port 4)
      HDD: generic
      DVD Drive: generic
      PSU: EVGA 500W Semi Modular (but you should get 650W!)
      Case: CoolerMaster CM590 III
      Fans: 2x stock case fans (one sucky on front, one blowy on back), 3x be quiet! BL046 120mm fans (two blowy on top, one sucky on front). Airflow near-perfectly balanced.
       
      ADVICE
      With the Clover configuration, you want to pay close attention to all things relating to graphics. There are some specific settings for ACPI, Boot, Devices and Graphics which should be copied exactly in order to get the iGPU and dGPU to work in perfect harmony. For instance, make sure you use ig-platform-id 59120003 rather than 59120000 if you want FCPX to be usable. With the right settings, FCPX will not only run, but run flawlessly.
       
      I was not able to figure out how to make NVRAM/PRAM behave itself, and I got errors when I tried to issue relevant commands. As a result, I could not at first get iMessage to work properly. It worked once on my first installation attempt but not from subsequent attempts. This Clover configuration therefore has no consideration whatsoever toward iMessage reliability - however, iMessage ended up working somehow, anyway - I noticed it after I'd updated to 10.14.3 but this may just have been coincidence.
       
      Onboard WiFi does not work. There is no driver for it. I'm using wired ethernet to a bridge router as it was cheaper than getting a compatible PCI card.
       
      Audio is working well after I installed the z370 audio patch, then the ALC1220 codecs, then AppleALC.
       
      With kexts for generic 3rd party SATA and generic 3rd party eSATA, my HDDs and DVD drive work perfectly well.
       
      Sleep/Wake functions run perfectly. iCloud functions run perfectly. Shutdown leaves the mobo LEDs on, annoyingly.
       
      My USB 3 ports seem to suffer from low power output, and I don't know why.
       
      Overall, this system appears to run about as well under MacOS 10.14 Mojave as it does under Windows 7. I would solidly recommend this build to anyone looking to build a computer for workstation purposes, on a budget.
    • By JhonneR
      Good morning, everyone, I'm sorry if I was wrong in choosing the topic but I need help.
      I have found it extremely difficult to mount a Hackintosh in my acer.
      Setup;
      I5 2430m 2.4 6GB RAM
      Mobo P5we0 - Intel intel Graphics 3000
      At the moment I have not found out what my audio codecs are.
      but I'll leave the link on the motherboard.
      however, my real problem is several.
      I have already used the itakos image, I have already used several images that could be installed normally and that after installing the image I do not have internet via cable or wireless.
      And another, I already looked in other forums and I know that I will be called a donkey in the logical question but I have not been able to install the [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] or clover to start from the Hard Disk, so I do not know what to do.At the moment I still do not know if there has already been someone who has already installed the High Sierra or just the Sierra in this notebook model and obtained permanent success.
      If anyone can help me, I'll be grateful.
      Installations without success, but with the system already installed in ACER;
      SIERRA
      HIGH SIERRA
      MOJAVE
      All with the same symptom. Starting only by the bootable USB stick and without internet connection via cable and wireless.
      Appreciate ! Acer 5750 Official Page
×