Jump to content
ErmaC

Clover problems report & features request

683 posts in this topic

Recommended Posts

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
Advertisement

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

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

I just got the same issue you have after I deleted src folder for second time to see if I got your issue and I did. I did a ping test to both repo's edk and clover and it returned results so that means there is internet access.

 I then manually tried svn up the clover directory and it updated to 4415 so it must be something in the script. maybe the way it checks for the revisions accessing sourcrforge changed.

 I also noticed that because of the issue it did not check for aptiofix updates

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 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 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By cvad
      Small tool to download, compile and build the latest Clover X64 package.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
       
    • By blxkspell
      Hey!
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
       
       
    • By kylon
      Cloud Clover Editor allows you to manage Clover EFI and Ozmosis configs everywhere!
       
       
      WEB
      Open Cloud Clover Editor
       
      APP (MacOS - Discontinued)
      Clover flying editor ( Micky1979 )
       
       
       
       
      Sources: https://bitbucket.org/kylon/cloud-clover-editor-cce/overview


      To run CCE at home you will need:
       
      An HTTP server (Apache, Nginx, ...) PHP 5.3.3+ (latest PHP version is always recommended for better performances/security) Sqlite3 PHP extension  
       
      Some Features:
       
      Edit text in tables:
      Editable fields are marked with a text cursor.
      Double click, or tap and hold, to open the inline editor.
      You can now press Enter or click outside to save your changes.
       
       
      Tri-state checkboxes:
      There are 3 possible states for a checkbox: Checked, indeterminate and unchecked.
       
      Checked: Value is true;
      Indeterminate: Value is false;
      Unchecked: Value is not set (ie, removed from plist)
       
      Working with multiple configs:
      The right sidebar is your multitasking menu.
      Use the add button to create a new config and add it to the list.
      You can safely switch between all your configs, no changes will be lost.
      You can mix Clover EFI and Ozmosis configs.


      Config Upgrade feature:
      In the case you are using old configuration options, CCE gives you the ability to automatically upgrade your config.
       
       
      Copy to:
      You can copy patches between your configs (you will love this when you need to copy kernel and kext patches ;D ).
      You will find a yellow copy icon if that field does support the copyTo feature.
       
       
      Ozmosis Mode:
      A new setting, Cloud Clover Editor Mode, is now added in Cloud Clover Editor -> CCE Settings.
      This will let you switch from Clover EFI to Ozmosis mode.
      Changes to your current file will be lost.
       
       
      CCE Bank 2.0:
      Thanks to @cecekpawon for the idea.
       
      CCE Bank is a database where you can save/load Clover EFI and Ozmosis configs.
      You can protect your config from unwanted modifications or make a publicly editable config.
       
      To save a config in CCE Bank you only need to check the "Save to CCE Bank" option.
       
      Tick the box generate a new CID, if you don t have one.
       
      A CID (CCE ID) acts like a container and it is your authentication key.
      You can group multiple configs under the same CID or generate as many CIDs as you like.
       
      Edit Modes:
      Public: Anyone can make modifications, only the owner can change its settings. Private: Only the owner can make modifications and change its settings. MyBank: Only the owner can see this config, make modifications or change its settings.  
      MyBank is your private area.
      Change the 'view mode' to switch between the public bank and your personal bank.
       
      To manage your currently loaded config, go to Cloud Clover Editor -> Open config -> click the settings button.
       
       
      Notes:
      Locked/Private configs are marked with a padlock MyBank configs are only visibile in your private area Only the owner of a locked config can save the modifications in CCE Bank, hower you are free to do whatever you want in CCE and download the modified config If you loose your CID you can just reply or pm me No account is required!  
       
      Main Features:
      Left sidebar does support touch swipe on touch devices.
      No changes will be lost on page reload.
       
       
      Credits
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support Please let me know if i forgot you!
    • By d2a
      So I'm finally joining the grown-ups and trying to set up a new(ish) hack. In the past I've used legacy Clover with my old Gigabyte board and thought I knew what I was doing. But I've been trying to get a UEFI Clover-based install to work and it's going nowhere.
       
      My new system (listed as SysB in sig) is a Gigabyte Z97X-UD3H-BK rev1.1 with firmware F6, an i7 4790K CPU and 4x4GB Corsair 1866MHz. I have the firmware settings set as per various guides and thought this should be a pretty painless transition...
       
      I have successfully run the installer for El Cap several times, but can't get the machine to boot reliably - it seems to change behaviour each boot. Sometimes boot hangs at the Gigabyte logo after choosing boot volume via F12, sometimes it boots to clover but displays no bootable drives, sometimes displays ElCap SSD in Clover but wont boot from it with kernel cache error, and occasionally it will boot all the way.
       
      What I'd like to know is:
       
      Should I update the mobo firmware to the latest version? This board has two more recent Bios software downloads, but they wont allow me to drop back to the version currently installed. I'm nervous to update unless this is likely to be the culprit. Is this just a UEFI issue? If the simple answer is just go legacy mode, maybe I should just avoid the issue... FInally, does anyone else have a working clover install on this board they could share with me? I think I've got it set up as it should be but the strange inconsistent boot behaviour makes me wonder... Thanks
×