Jump to content
30960 posts in this topic

Recommended Posts

Hi @Slice
thanks for your great work on clover .
but the clover starting from r4380 doesnt work on my AMD FX mobo ( ASUS M5A97 R2.0 ) . The clover doesnt even load at all , it just sits on a black screen . 
i also tried the latest clover version but it didnt work too but its working fine on Ryzen mobo's .
so any suggestions regarding this ?

So, r4512 booted without issue with no modifications to my Config.plist (Yeah! thanks Slice!)

 

Checking the guide for moving over to the new methods I think I only have one item to change (Intel)...

1770867088_ScreenShot2018-06-01at23_24_34.png.c67d3d6fa0083e975627abeb444dcd4b.png

 

From my newly created config-imprint.plist I see this...

1343724255_ScreenShot2018-06-01at23_26_12.png.f8f23de62767643a79b805073fcce4b2.png

 

What I am not sure of is how I incorporate that into my current Config.plist...

	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<true/>
			<key>NVidia</key>
			<false/>
		</dict>

Can anyone please help?

Edited by D-an-W
3 hours ago, D-an-W said:

So, r4512 booted without issue with no modifications to my Config.plist (Yeah! thanks Slice!)

 

Checking the guide for moving over to the new methods I think I only have one item to change (Intel)...

1770867088_ScreenShot2018-06-01at23_24_34.png.c67d3d6fa0083e975627abeb444dcd4b.png

 

From my newly created config-imprint.plist I see this...

1343724255_ScreenShot2018-06-01at23_26_12.png.f8f23de62767643a79b805073fcce4b2.png

 

What I am not sure of is how I incorporate that into my current Config.plist...


	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<true/>
			<key>NVidia</key>
			<false/>
		</dict>

Can anyone please help?

I believe you need to remove inject intel from your current config.plist and copy and paste the properties from the imprint to your config in the appropriate section.

  • Like 1
8 hours ago, XLNC said:

Hi @Slice
thanks for your great work on clover .
but the clover starting from r4380 doesnt work on my AMD FX mobo ( ASUS M5A97 R2.0 ) . The clover doesnt even load at all , it just sits on a black screen . 
i also tried the latest clover version but it didnt work too but its working fine on Ryzen mobo's .
so any suggestions regarding this ?

Boot->Debug=YES

to see what is happen

  • Like 1

Hi All

Wake up my system after install thunderbolt card.

If I press sleep button went to sleep after 2 second wake up agan.

Please help for fix this.

Please check my files.

I install HibernationFixup.kext too.

 35    2 0xffffff7f84179000 0x6d000    0x6d000    as.vit9696.Lilu (1.2.3) DC607E11-9271-3E76-B07D-6B552EEF0158 <7 5 4 3 2 1>
   36    0 0xffffff7f841e6000 0x5000     0x5000     as.lvs1974.HibernationFixup (1.2.1) FC2AF3B6-0824-330F-B1B5-EB7D16B93FF8 <35 7 5 4 3 2 1>

 

My PM settings

System-wide power settings:
Currently in use:
 autorestart          0
 Sleep On Power Button 1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 powernap             1
 networkoversleep     0
 disksleep            10
 sleep                0 (sleep prevented by coreaudiod)
 hibernatemode        0
 ttyskeepawake        1
 displaysleep         23 (display sleep prevented by coreaudiod, com.apple.WebKit.WebContent)
 womp  

wake reason unknown?

Please help fix this issue.

Thank you.

 

Screen Shot 2018-06-02 at 2.01.21 PM.png

Screen Shot 2018-06-05 at 2.37.41 PM.png

navaratnam’s Mac Pro-wake.ioreg

Edited by nmano

Is there a problem with the config.plist when adding the new properties created by clover-genconfig? Or is there a problem with opening config.plist with clover configurator after all the new updates that semi corrupts the config.plist?

can somebody compile NvmExpressDxe for 32bit please. I need it for my unsupported MacPro1,1 running Yosemite. I have used USB Refind to boot it off, but it can't detect my nvme via PCI card due to lack of nvme efi.

 

The nvme is detected using NvmExpressDxe-64 on my MacPro4,1 but not on the MacPro1,1 due to being 32bit efi

 

Thanks.

Prematurely, uhmmmb... I'm waiting for devs when Clover will use "os_mojave.icns" (or whatever specified name) so I get a clue for updating my prev. themes to support it on GUI. Thanks.

Edited by Badruzeus

Guys is there any changes in 10.13.4-10.13.5 with XCPM or Kext injection?

 

Installing both fresh works perfectly fine, however loading it after install hard locks the system, even the reset button won't work, have to pull the power cord out.

10.13.3 works like a charm, same clover(latest), same config (minus small changes for USB and EIST)

 

IMG_1520.thumb.JPG.c847705289d7b8492aba0248084bbc3c.JPG

Edited by Balamut
56 minutes ago, SavageAUS said:

Try switching to build_clover.command

What do you mean by Switching to build_clover.command??? There is no such that command inside folder. I am using CloverGrowerPro not CloverGrower :D

2 hours ago, Gabeloooooo said:

I've tried searching for info everywhere but can't figure out what SMCHelper-64.efi does. Do we still need it after clover 4509?

https://www.insanelymac.com/forum/topic/304530-clover-change-explanations/?do=findComment&amp;comment=2294940

2 hours ago, Gabeloooooo said:

I've tried searching for info everywhere but can't figure out what SMCHelper-64.efi does. Do we still need it after clover 4509?

 

7 hours ago, Andres ZeroCross said:

What do you mean by Switching to build_clover.command??? There is no such that command inside folder. I am using CloverGrowerPro not CloverGrower :D

CloverGrowerPro is not working. Why do you use it? Because you are developer? In this case you are able to fix the script. You want to take new Clover? There are other possibilities to get it ready-to-use.

  • Like 1

Hi,

 

I've made an utterly stupid mistake regarding KernelLapic patch. It was my fault. And now I want to fix it up. :)

Index: rEFIt_UEFI/Platform/kernel_patcher.c
===================================================================
--- rEFIt_UEFI/Platform/kernel_patcher.c	(revision 4516)
+++ rEFIt_UEFI/Platform/kernel_patcher.c	(working copy)
@@ -664,14 +664,21 @@
         patchLocation = i+1398;
         DBG("Found Sierra Lapic panic at 0x%08x\n", patchLocation);
         break;
-      //PMheart: 10.13.DP1/10.14.DP1
+      //PMheart: 10.13.DP1
     } else if (bytes[i+0] == 0x65 && bytes[i+1] == 0x8B && bytes[i+2] == 0x0C && bytes[i+3] == 0x25 &&
         bytes[i+4] == 0x1C && bytes[i+5] == 0x00 && bytes[i+6] == 0x00 && bytes[i+7] == 0x00 &&
         bytes[i+1407] == 0x65 && bytes[i+1408] == 0x8B && bytes[i+1409] == 0x0C && bytes[i+1410] == 0x25 &&
         bytes[i+1411] == 0x1C && bytes[i+1412] == 0x00 && bytes[i+1413] == 0x00 && bytes[i+1414] == 0x00) {
         patchLocation = i+1396;
-        DBG("Found High Sierra/Mojave Lapic panic at 0x%08x\n", patchLocation);
+        DBG("Found High Sierra Lapic panic at 0x%08x\n", patchLocation);
         break;
+      //PMheart: 10.14.DP1
+    } else if (bytes[i+0] == 0x65 && bytes[i+1] == 0x8B && bytes[i+2] == 0x0C && bytes[i+3] == 0x25 &&
+        bytes[i+4] == 0x1C && bytes[i+5] == 0x00 && bytes[i+6] == 0x00 && bytes[i+7] == 0x00 &&
+        bytes[i+1396] == 0x65 && bytes[i+1397] == 0x8B && bytes[i+1398] == 0x0C && bytes[i+1399] == 0x25 &&
+        bytes[i+1400] == 0x1C && bytes[i+1401] == 0x00 && bytes[i+1402] == 0x00 && bytes[i+1403] == 0x00) {
+        patchLocation = i+1385;
+        DBG("Found Mojave Lapic panic at 0x%08x\n", patchLocation);
+        break;
     }
   }
 

 

Before anybody wants to draft a new release for 10.14 compatibility, here is a pre-compiled binary for temporary use. (I will remove it once a new version supporting 10.14 has been available on SF.)

EDIT: So finally you should go with r4522 available on SF. Binaries REMOVED.

 

 

For a more detailed usage (especially for newbies), please see

 

Edited by PMheart
  • Like 4
×
×
  • Create New...