Jump to content
ErmaC

Clover problems report & features request

296 posts in this topic

Recommended Posts

Anybody tried 4384, don't work here, had to revert to 4380

define doesn't work please?

mine stuck at +++++++++++++++++++

had to use AptioMemoryFix

Share this post


Link to post
Share on other sites
Advertisement

Clover4384, AptioMemoryFixRC5.

I have no problems so far.

Z170m-Plus,OS X 10.13.DB5,Apfs

 

 

0:100  0:100  MemLog inited, TSC freq: 3504495820
0:104  0:004  CPU was calibrated with RTC
0:107  0:003  
0:108  0:000  Now is 18.1.2018,  7:42:27 (GMT)
0:112  0:004  Starting Clover revision: 4384 on American Megatrends EFI
0:119  0:007  Build with: [Args: -x64 -D USE_BIOS_BLOCKIO -D NO_GRUB_DRIVERS_EMBEDDED -D ENABLE_VBIOS_PATCH_CLOVEREFI -D DEBUG_ON_SERIAL_PORT -t XCODE5 | -D USE_BIOS_BLOCKIO -D NO_GRUB_DRIVERS_EMBEDDED -D ENABLE_VBIOS_PATCH_CLOVEREFI -D DEBUG_ON_SERIAL_PORT -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 9 | OS: 10.13.2 | XCODE: 9.2]
0:141  0:022  SelfDevicePath=PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x3,0xFFFF,0x0)\HD(1,GPT,98AC6E18-2974-4432-9E76-18772C419C46,0x28,0x64000) @B0CCD9D8
0:155  0:013  SelfDirPath = \EFI\BOOT
0:174  0:018  === [ Get Smbios ] ========================================
.....................
0:328  0:005  Boot status=0
0:331  0:002  Running on: 'System Product Name' with board 'Z170M-PLUS'
0:337  0:006  === [ GetCPUProperties ] ================================== 

 

 

Z77-ds3h,OS X 10.13.2

 

 

0:100  0:100  MemLog inited, TSC freq: 3403351673
0:104  0:004  CPU was calibrated with ACPI PM Timer
0:108  0:004  
0:109  0:000  Now is 18.1.2018,  7:43:24 (GMT)
0:113  0:004  Starting Clover revision: 4384 on American Megatrends EFI
0:120  0:006  Build with: [Args: -x64 -D USE_BIOS_BLOCKIO -D NO_GRUB_DRIVERS_EMBEDDED -D ENABLE_VBIOS_PATCH_CLOVEREFI -D DEBUG_ON_SERIAL_PORT -t XCODE5 | -D USE_BIOS_BLOCKIO -D NO_GRUB_DRIVERS_EMBEDDED -D ENABLE_VBIOS_PATCH_CLOVEREFI -D DEBUG_ON_SERIAL_PORT -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 9 | OS: 10.13.2 | XCODE: 9.2]
0:142  0:021  SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(1,GPT,0863F066-65A6-46F9-B747-72F25E463E02,0x28,0x64000) @C8975E18
0:155  0:013  SelfDirPath = \EFI\BOOT
.............................
0:314  0:005  Boot status=0
0:317  0:002  Running on: 'To be filled by O.E.M.' with board 'Z77-DS3H'
0:323  0:006  === [ GetCPUProperties ] ==================================
0:331  0:007  CPU Vendor = 756E6547 Model=206A7 

 

 

N53SV,OS X 10.9.5

 

 

0:100  0:100  MemLog inited, TSC freq: 1995465558
0:100  0:000  CPU was calibrated with ACPI PM Timer
0:100  0:000  
0:100  0:000  Now is 18.1.2018,  7:36:52 (GMT)
0:100  0:000  Starting Clover revision: 4384 on American Megatrends EFI
0:100  0:000  Build with: [Args: -x64 -D USE_BIOS_BLOCKIO -D NO_GRUB_DRIVERS_EMBEDDED -D ENABLE_VBIOS_PATCH_CLOVEREFI -D DEBUG_ON_SERIAL_PORT -t XCODE5 | -D USE_BIOS_BLOCKIO -D NO_GRUB_DRIVERS_EMBEDDED -D ENABLE_VBIOS_PATCH_CLOVEREFI -D DEBUG_ON_SERIAL_PORT -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 9 | OS: 10.13.2 | XCODE: 9.2]
0:101  0:000  SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,F61211C5-87B9-4CDD-BE33-9DC9BD4A478E,0x28,0x64000) @22FF618
0:101  0:000  SelfDirPath = \EFI\CLOVER
...................
0:106  0:000  Running on: 'N53SV' with board 'N53SV'
0:106  0:000  === [ GetCPUProperties ] ==================================
0:106  0:000  CPU Vendor = 756E6547 Model=206A7
0:107  0:000   The CPU supported SSE4.1
0:107  0:000  BrandString = Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
......................
2:003  0:000  PrepareHibernation:
2:003  0:000      read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success
2:003  0:000      SleepImage name from pref: ImageVolume = 'OSX10.9.5', ImageName = '\private\var\vm\sleepimage'
2:004  0:000      returning previously calculated offset: B24ECD000
2:004  0:000   SleepImageOffset: B24ECD000
2:004  0:000  02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 | .....A..........
2:004  0:000  02 1F 03 12 0A 00 01 00 FF FF 00 00 04 04 18 00 | ................
2:005  0:000  42 00 32 00 34 00 45 00 43 00 44 00 30 00 30 00 | B.2.4.E.C.D.0.0.
2:005  0:000  30 00 00 00 7F FF 04 00                         | 0.......
2:005  0:000  boot-image before: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\B24ECD000
2:009  0:003  DeleteBootOption: Boot0082
2:012  0:003   Boot0082 deleted
2:012  0:000  DeleteFromBootOrder: 0082
2:012  0:000  BootOrder: 3: Boot0003, Boot0000, Boot0082
2:013  0:001   found at index 2
2:016  0:003  SetVariable: BootOrder = Success
2:017  0:000   IOHibernateRTCVariables found - will be used as boot-switch-vars
2:029  0:012  SetScreenResolution: 800x600 - already set
2:029  0:000  Custom boot is disabled
2:029  0:000  Closing events for wake 

 

 

Share this post


Link to post
Share on other sites

Anybody tried 4384, don't work here, had to revert to 4380

r4384 works just fine here on my legacy mach (sig)  :)

Whole "CloverV2" built with GCC under Ubuntu 17.10: Drive

.....  .....
1:403  0:000  Now is 18.1.2018,  6:12:30 (GMT)
1:403  0:000  Starting Clover revision: 4384 on CLOVER EFI
1:403  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t GCC53 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t GCC53 -n 5 | OS: Ubuntu 17.10]
.....  ..... 

Thanks.

preboot.log-r4384-gcc.zip

Share this post


Link to post
Share on other sites

Anybody tried 4384, don't work here, had to revert to 4380

Same here with r4384

 

I had to use AptioMemory instead of AptioFix3drv to start my system  :yes:

Share this post


Link to post
Share on other sites

Same here with r4384

 

I had to use AptioMemory instead of AptioFix3drv to start my system :yes:

Same issue here all I got in Verbose was lots of +'s with r4384.

Reverted to r4382 no issue.

 

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Same issue here all I got in Verbose was lots of +'s with r4384.

Reverted to r4382 no issue.

 

 

Sent from my SM-G930F using Tapatalk

Reverted to r4383 no issue too

Share this post


Link to post
Share on other sites

Before 4385, if you had both OsxAptioFixDrv and OsxAptioFix2Drv in drivers64UEFI, it would pick up the one that occurs first in the FAT32 directory iteration.  After 4385 there is a prioritisation, so OsxAptioFix2Drv is picked up first.  I suggest you keep just the one that works for use in drivers64UEFI and move the others to drivers-Off/drivers64UEFI.

 

Had to change OsxAptioFixDrv2 to  OsxAptioFixDrv for 4385  :thumbsup_anim:

Share this post


Link to post
Share on other sites

Hello,

Is possible to Clover recognize nvram plist files created for Chameleon based bootloaders (such as Enoch), since it has one already when emuvariable driver is used? I mean, if it could recognize and handle with these plist files, it would be possible to have only one plist file storing nvram variables visible and acessible to both bootloaders for the same system. This would be nice in a multibootloader installation. Thanks.

Share this post


Link to post
Share on other sites

Hello,

Is possible to Clover recognize nvram plist files created for Chameleon based bootloaders (such as Enoch), since it has one already when emuvariable driver is used? I mean, if it could recognize and handle with these plist files, it would be possible to have only one plist file storing nvram variables visible and acessible to both bootloaders for the same system. This would be nice in a multibootloader installation. Thanks.

Let Chameleon to be "like Clover".

nvram.plist is created by very common command

$ nvram -x -p>nvram.plist

so it will not depend on bootloader.

Share this post


Link to post
Share on other sites

Before 4385, if you had both OsxAptioFixDrv and OsxAptioFix2Drv in drivers64UEFI, it would pick up the one that occurs first in the FAT32 directory iteration.  After 4385 there is a prioritisation, so OsxAptioFix2Drv is picked up first.  I suggest you keep just the one that works for use in drivers64UEFI and move the others to drivers-Off/drivers64UEFI.

Was using OsxAptioFix2Drv only then had to change to OsxAptioFixDrv for 4385, otherwise no boot, just black screen.

Share this post


Link to post
Share on other sites

Let Chameleon to be "like Clover".

nvram.plist is created by very common command

$ nvram -x -p>nvram.plist

so it will not depend on bootloader.

Thank you for your reply. This solution works very well for Clover, since it can see the new nvram.plist and so it recognizes nvram variables defined in a Chameleon boot session. I've written a bash script and used a daemon to do this at every boot. In the other direction, I've had to use PlistBuddy to edit a nvram.plist file in the formatting that Chameleon expects, so that it can see nvram variables defined in a Clover session. Now I'm trying to make this also "scriptized". Thanks again.

Share this post


Link to post
Share on other sites

Hola y gracias por el cambio que propuse anteriormente.
Subir para evitar desplazarse y barra desplazamiento.

 

Hello and thank you for the change I proposed earlier.
Go up to avoid scrolling and scrolling.

post-471348-0-42743100-1516724783_thumb.png

Share this post


Link to post
Share on other sites

Hola y gracias por el cambio que propuse anteriormente.

Subir para evitar desplazarse y barra desplazamiento.

 

 

Hello and thank you for the change I proposed earlier.

Go up to avoid scrolling and scrolling.

try to replace the original one with this... and compile/build a new pkg...

 

Prueba con este html remplazando el original y luego vuelve a crear el pkg.

 

--> Conclusion.html.zip

 

ErmaC

Share this post


Link to post
Share on other sites

report lang issue to dev.
i reported this issue before
http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2565871
i traced this issue point. but not sure. I just want to report this point.
https://sourceforge.net/p/cloverefiboot/code/4414/tree/rEFIt_UEFI/Platform/DataHubCpu.c#l213
but surely effect lang after update with osxaptiofixv2+emul+ko set(config).

but if use osxaptiofixv3 or aptiomemoryfix without emul, what i mentioned above presents lang issue(ko+eng)
i checked this is OS X's business. so i checked realmac nvram dump.

realmac has this nvram vals
------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Lang
------------------------------------------------------------------------------
000000: 65 6e 67 00 |eng.|

------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:LangCodes
------------------------------------------------------------------------------
000000: 65 6e 67 00 |eng.|

------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLang
------------------------------------------------------------------------------
000000: 65 6e 2d 55 53 00 |en-US.|

------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLangCodes
------------------------------------------------------------------------------
000000: 65 6e 2d 55 53 00 |en-US.|



but clover has only

------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLang
------------------------------------------------------------------------------
000000: 65 6e 2d 55 53 00 |en-US.|

------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLangCodes
------------------------------------------------------------------------------
000000: 65 6e 2d 55 53 3b 6a 61 2d 4a 50 3b 66 72 2d 46 |en-US;ja-JP;fr-F|
000010: 52 3b 6b 6f 2d 4b 52 00 |R;ko-KR.|

------------------------------------------------------------------------------

does it effect lang issue after update?

thanks in advance.

 

EDIT1.

my friend's real MBP11,5 has 

<key>prev-lang:kbd</key>

<data>

a286MjUy

</data>

 

and

------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Lang
------------------------------------------------------------------------------
000000: 65 6e 67                                         |eng|
 
------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:LangCodes
------------------------------------------------------------------------------
000000: 65 6e 67                                         |eng|
 
there are not PlatformLang/PlatformLangCodes

Share this post


Link to post
Share on other sites

report lang issue to dev.

i reported this issue before

http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2565871

i traced this issue point. but not sure. I just want to report this point.

https://sourceforge.net/p/cloverefiboot/code/4414/tree/rEFIt_UEFI/Platform/DataHubCpu.c#l213

but surely effect lang after update with osxaptiofixv2+emul+ko set(config).

 

but if use osxaptiofixv3 or aptiomemoryfix without emul, what i mentioned above presents lang issue(ko+eng)

i checked this is OS X's business. so i checked realmac nvram dump.

 

realmac has this nvram vals

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Lang

------------------------------------------------------------------------------

000000: 65 6e 67 00 |eng.|

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:LangCodes

------------------------------------------------------------------------------

000000: 65 6e 67 00 |eng.|

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLang

------------------------------------------------------------------------------

000000: 65 6e 2d 55 53 00 |en-US.|

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLangCodes

------------------------------------------------------------------------------

000000: 65 6e 2d 55 53 00 |en-US.|

 

 

 

but clover has only

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLang

------------------------------------------------------------------------------

000000: 65 6e 2d 55 53 00 |en-US.|

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLangCodes

------------------------------------------------------------------------------

000000: 65 6e 2d 55 53 3b 6a 61 2d 4a 50 3b 66 72 2d 46 |en-US;ja-JP;fr-F|

000010: 52 3b 6b 6f 2d 4b 52 00 |R;ko-KR.|

 

------------------------------------------------------------------------------

 

does it effect lang issue after update?

 

thanks in advance.

 

EDIT1.

my friend's real MBP11,5 has 

<key>prev-lang:kbd</key>

<data>

a286MjUy

</data>

 

and

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Lang

------------------------------------------------------------------------------

000000: 65 6e 67                                         |eng|

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:LangCodes

------------------------------------------------------------------------------

000000: 65 6e 67                                         |eng|

 

 

there are not PlatformLang/PlatformLangCodes

 

Apple uses a modified EFI 1.10 firmware so it probably never updated from previous protocols those variables are deprecated variables in UEFI:

Lang      NV, BS, RT The language code that the system is configured for. This value is deprecated.
LangCodes BS, RT     The language codes that the firmware supports. This value is deprecated.
Lang has been deprecated. If the platform supports this variable, it must map any changes in the Lang variable into PlatformLang in the appropriate format.
[LangCodes] has been deprecated. If the platform supports this variable, it must map any changes in the [LangCodes] variable into [PlatformLangCodes] in the appropriate format.
*I made some corrections to what seem like obvious mistakes in the specification language

PlatformLang and PlatformLangCodes use RFC 4646, where Lang and LangCodes use ISO 639-2. But none the less, we should set them if they are not present.

Share this post


Link to post
Share on other sites

Apple uses a modified EFI 1.10 firmware so it probably never updated from previous protocols those variables are deprecated variables in UEFI:

Lang      NV, BS, RT The language code that the system is configured for. This value is deprecated.LangCodes BS, RT     The language codes that the firmware supports. This value is deprecated.
Lang has been deprecated. If the platform supports this variable, it must map any changes in the Lang variable into PlatformLang in the appropriate format.[LangCodes] has been deprecated. If the platform supports this variable, it must map any changes in the [LangCodes] variable into [PlatformLangCodes] in the appropriate format.*I made some corrections to what seem like obvious mistakes in the specification language
PlatformLang and PlatformLangCodes use RFC 4646, where Lang and LangCodes use ISO 639-2. But none the less, we should set them if they are not present.
Thanks. So how can i test? Just add lang and lang code?

Current, pre-lang:kbd nvram key effects system lang after update. Because aptiofixv2+emu combination is no problem.

 

Does it equal pre-lang:kbd and lang?

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

Thanks. So how can i test? Just add lang and lang code?

 

Yeah, just add them. But you have to use ISO 639-2, so they are different language codes. Lang and LangCodes are firmware variables, they are almost surely not supported by almost all UEFI firmware, so you'd have to still set the others still too. This probably means that it might not be able to find some protocols that relied on this language code format because they have been switched to work with RFC4646 and PlatformLang(Codes). Like EFI_UNICODE_COLLATION_PROTOCOL...

 

Current, pre-lang:kbd nvram key effects system lang after update. Because aptiofixv2+emu combination is no problem.

 

Does it equal pre-lang:kbd and lang?

 

No, that is an Apple GUID variable, that should get set by setting a keyboard and language in system preferences (or when you do that during install). Did you remember to apply all the variables from your nvram.plist to your native NVRAM after removing EmuVar?

Share this post


Link to post
Share on other sites

Yeah, just add them. But you have to use ISO 639-2, so they are different language codes. Lang and LangCodes are firmware variables, they are almost surely not supported by almost all UEFI firmware, so you'd have to still set the others still too. This probably means that it might not be able to find some protocols that relied on this language code format because they have been switched to work with RFC4646 and PlatformLang(Codes). Like EFI_UNICODE_COLLATION_PROTOCOL...

 

 

No, that is an Apple GUID variable, that should get set by setting a keyboard and language in system preferences (or when you do that during install). Did you remember to apply all the variables from your nvram.plist to your native NVRAM after removing EmuVar?

Thank you for info. Yes. I checked it with several test times. I removed EmuVar+osaptiofixv2 and rcscript and nvram.plist. then sudo nvram -c. And check nvram -p until update beta. Then put osxaptiofixv3 or aptiomemoryfix in driver64uefi folder, then update beta. Then i found lang issue of reboot windows.

 

So, i just saw difference between emul+fixv2+ko(config) and (fixv3 or memoryfix). Just there is whethe pre-lang:kdb exist. Iike you said before, this key osx business(recorded in code). I didn't understand. It means what. So i compared my nvram dump and realmac from darwindump tool to close to problem.

 

나의 LG-F800S 의 Tapatalk에서 보냄

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   1 member

  • Similar Content

    • By thomaspetersen
      Hi All
       
      I'm trying to start a Hackintosh High Sierra 10.13.5 installation:
      - MSI B350 PC Mate
      - Ryzen 5 - 2600
      - Radeon Pro 580 GPU
      - 4 x 8GB DDR4
      (Have a working clover bootloader for HS 10.13.3 - but for some reason, I can't use that setup with the 10.13.5) 
       
      Have tried different bootloader setup, with different outcomes...
      ATM. I get this error/hang - "Unknown CPU: family = 0x17, model = 0x8, Stepping = 0x2"
      Have search google, and can see that the threads ppl. are getting this, is when they look at "About this mac", I haven't yet installed the OSX.
       
      So can someone help...

      I'm running the newest Kexts: AppleALC, FakeSMC, Lilu, RealtekRTL8111, USBInjectAll and WhateverGreen.
      In Bootloader setup, i'm running: -v, -s, -f, -no_compat_check, busratio=34, PCIRootUID=1, npci=0x2000, dart=0 and nv_disable=1
      In SMBIOS i'm using the iMac18,2 and in RT i'm using BooterConfig: 0x28 and CsrActiveConfig: 0x67
      In installed drivers i'm using: AptioMemoryFix, EmuVariableUefi-64, OsxAptioFixDrv-64 (Have tried Fix2 as well)
       
      But i'm, keep getting the Unknown CPU hang/error, can someone help...
      Or do someone have a setup with the same CPU and GPU, that can show me his/her setup for Bootloader/Kexts...
    • By Teress
      I get a lot of questions about HOW TO BACKUP A HACKINTOSH. So I decided to create Complete Guide with 5 methods described in detail, how to easily make bootable clones of Hackintosh system disks, or backup your data. Full step by step tutorial is here:
       
       
    • By Anirban Mandal
      Hello everyone.
       
      I am new to this hackintosh world (about 1 week now) and I am very impressed with the sort of results it has yielded in my workflow. I use my laptop for guitar DSP and recording audio and have been able to come up with a good enough mackintosh build for it (using High Sierra 10.13.1 now).
       
      For the past one week I have been trying to get rid of an annoying popup "your computer was. restarted because of an error". If you take a look at the error report you shall notice Darwin 18.0.0 as being mentioned, which I presume is Mojave.
       
      What I had done is install 10.13.1 -> 10.13.3 -> 10.13.5 -> 10.14 Beta, where the 10.14 Beta failed and since then the error started popping up. After that I have reinstalled 10.13.1 multiple times, installed it to a different hard disk, used 'shred' from a linux live session on my laptops HDD and installed and still that error message won't go away.
       
      Everything functions fine, the error message is just annoying. If someone can help me get rid of it, it would just make the hackontish build cooler.
       
      PFA Error report.
       
      Cheers.
      Error Report.rtf
    • By STLVNUB
      Reviving my old INSTAHackintosh, it's been a while....
      Purpose:
      Create User Custom Install iso/dmg with bootloader, apps and user-settings.
      Create Live iso/usb.
      What Versions:
      Tiger-Current ( bit ambitious but hey I like a challenge ).
      Why:
      Because I can!
      I'm not too impressed with the way Apple and others handle their installs.
      Support for 4 Bootloaders:
      Chameleon
      Clover Legacy
      Refit Ozmosis
      Clover UEFI
      Keep you informed as I progress from scratch.
      This could take a while, it's NOT my priority.
      Will probably release in Os versions, starting at Mojave and working backwards.
×