Jump to content
ErmaC

Clover General discussion

17,332 posts in this topic

Recommended Posts

@arsradu,

 

@pokenguyen's logout hook is only necessary in Yosemite DP2 - Clover's default launch daemon & shutdown script to save NVRAM are working well in other OSX versions.  Your findings suggest a problem caused by bugs in Yosemite DP2 and its interaction with your system.

 

Are you sure that there is no nvram.plist file on your Mavericks volume, only on Yosemite?  If so, I guess it is using the nvram.plist on the Yosemite partition and that file is getting updated (check its time stamp).  Personally, I would not delete it because I know what a headache it can be to get iMessages working again when it goes awry :).

 

The EFI-backups folder on the targetted partition is normal and done for safety's sake (I would leave it alone but it is not strictly necessary).  When you install Clover "for UEFI booting only", the EFI folder in the ESP is updated and a backup copy is placed in a EFI-Backups folder on the targetted partition.  The steps you took to place FakeSMC.kext + other necessary kexts in the EFI/EFI/Clover/Kexts/10.9 are correct (another way is to put FakeSMC in the "Other" folder and delete 10.6-10.10 folders ---> this injects the same kexts for all OSX versions).

 

The boot logo is a strange thing and I don't think it is fully understood why it shows on some systems and not others.  On both of my legacy systems (desktop GA-P55aUD3 with Radeon 5770, Laptop Dell XPSm1530 nVidia 8600GT), the Apple logo appears on a white screen with loader going all the way to completion.

 

Anyway good luck with your experiments but make sure to make full time-machine backups etc :).

 

PS NullCPUPowerManagement is not necessary with a properly patched DSDT and I would recommend getting rid of it since it prevents proper power management and sleep.

Share this post


Link to post
Share on other sites
Advertisement

@arsradu,

 

@pokenguyen's logout hook is only necessary in Yosemite DP2 - Clover's default launch daemon & shutdown script to save NVRAM are working well in other OSX versions.  Your findings suggest a problem caused by bugs in Yosemite DP2 and its interaction with your system.

 

Are you sure that there is no nvram.plist file on your Mavericks volume, only on Yosemite?  If so, I guess it is using the nvram.plist on the Yosemite partition and that file is getting updated (check its time stamp).  Personally, I would not delete it because I know what a headache it can be to get iMessages working again when it goes awry :).

 

The EFI-backups folder on the targetted partition is normal and done for safety's sake (I would leave it alone but it is not strictly necessary).  When you install Clover "for UEFI booting only", the EFI folder in the ESP is updated and a backup copy is placed in a EFI-Backups folder on the targetted partition.  The steps you took to place FakeSMC.kext + other necessary kexts in the EFI/EFI/Clover/Kexts/10.9 are correct (another way is to put FakeSMC in the "Other" folder and delete 10.6-10.10 folders ---> this injects the same kexts for all OSX versions).

 

The boot logo is a strange thing and I don't think it is fully understood why it shows on some systems and not others.  On both of my legacy systems (desktop GA-P55aUD3 with Radeon 5770, Laptop Dell XPSm1530 nVidia 8600GT), the Apple logo appears on a white screen with loader going all the way to completion.

 

Anyway good luck with your experiments but make sure to make full time-machine backups etc :).

 

PS NullCPUPowerManagement is not necessary with a properly patched DSDT and I would recommend getting rid of it since it prevents proper power management and sleep.

Ok, I won't delete it.

 

Yes, I'm pretty sure there is no nvram.plist on Mavericks. I can't take a screenshot right now since I'm not at home anymore, but I could try and get one tonight, when I get back home. Can it use the nvram.plist when I'm not booted into that partition? That's interesting.

Ok, I'll remove the NullCPUPowerManagement kext. I tried to boot without it before and nothing bad happened. So I guess, at least for me, it would be safe to remove. So thank you very much for that info.

About the Others folder in Clover...I didn't know that! That's pretty cool, especially for multi-booting. I actually only need FakeSMC in order to boot. Nothing else. Which is nice. :)

 

About the logos....man, I wish I could bring more light into this... I'm here if anyone needs anything. But I'm not sure where to start debugging this issue. So not sure what kind of info would be necessary for anyone to fix this.

Share this post


Link to post
Share on other sites

 

It is readable enough.

See

1:860  0:000    found entry 2. 'Boot Mac OS X from Mavericks_250_Sata', Volume 'Mavericks_250_Sata'
1:860  0:000  Boot redirected to Entry 2. 'Boot Mac OS X from Mavericks_250_Sata'

Is it that you want?

 

In this place

		<key>DefaultVolume</key>
		<string>HD(1,GPT,A8E466E1-9563-30A0-988E-3357B8353895,0x800,0xFF000)</string>

must be NAME, for example


		<key>DefaultVolume</key>
		<string>Mavericks_250_Sata</string>

Hi,

 

Actually, it's Mavericks_SSD I'd like Clover to boot on.

And I had already tried  that with no luck

        <key>DefaultVolume</key>

        <string>Mavericks_SSD</string>

 

Mavericks_250_Sata being the drive Clover always wants to boot to no matter what when reading nvram (<key>IgnoreNVRAMBoot</key> set to false)

 

Strange thing is that when I print the nvram of my system (nvram -p), the variables of the system do point  (Clover.MountEFI and efi-boot-device) towards Mavericks_SSD

 

Thank you anyway, with the option <key>IgnoreNVRAMBoot</key>

<true/> in config.plist, I'm able to boot on it
 
System seems stable, I've been able to update all my Apps, so far so good  :)

Share this post


Link to post
Share on other sites

Would it be possible to add the functionality of AHCIPortInjector to Clover at some point? I use it on my X79 to inject device names for the three different sata controllers (which show up as "unknown ahci controller" otherwise).

 

One less kext is always good and Clover already does quite a bit of injection already.

Share this post


Link to post
Share on other sites

Second level devices can't be injected at boot time because system Bus drivers (USB, SATA) will created new device description forgetting the description written by a bootloader.

A kext is only solution.

Share this post


Link to post
Share on other sites

where is the language stored in clover config etc??? copied Fabio's config for my board and it has made my default language Italian....

 

changed the language in Settings a while back but just redid a new test drive and problem still there... 

Share this post


Link to post
Share on other sites

where is the language stored in clover config etc??? copied Fabio's config for my board and it has made my default language Italian....

 

changed the language in Settings a while back but just redid a new test drive and problem still there...

Did you try opening up config.plist (in EFI/EFI/CLOVER/config.plist) with TextEdit (default text editor) and setting the language to en, as such?

 

<key>Language</key> 
<string>en:0</string>

Share this post


Link to post
Share on other sites

Try not to edit with text editor to avoid errors but with plist editor(google).

For changing from "it" (probably) to "en:0", I guess he can use any text editor, since it's just a word. I actually never had any issues with the default TextEdit. I mean, it's not like Notepad in Windows, which sucks for anything else other then writing hate mail to Microsoft. But I'll try that plist editor that you mentioned. Thank you. :)

Share this post


Link to post
Share on other sites

Did you try opening up config.plist (in EFI/EFI/CLOVER/config.plist) with TextEdit (default text editor) and setting the language to en, as such?

 

<key>Language</key> 
<string>en:0</string>

 

doh... i was being dumb just noticed that!!!

 

Try not to edit with text editor to avoid errors but with plist editor(google).

 

thanks... use a plist editor... 

Share this post


Link to post
Share on other sites

where is the language stored in clover config etc??? copied Fabio's config for my board and it has made my default language Italian....

 

changed the language in Settings a while back but just redid a new test drive and problem still there... 

 

use : http://www.insanelymac.com/forum/topic/282787-clover-v2-instructions/page-3

 

Fabio

Share this post


Link to post
Share on other sites

My resolution is fine once I boot to desktop but the resolution is wrong at the boot prompt.  I am using bootcamp theme is there a way to increase the resolution maybe with nvram setting?  Not sure if this parameter can be written to nvram?

Share this post


Link to post
Share on other sites

My resolution is fine once I boot to desktop but the resolution is wrong at the boot prompt.  I am using bootcamp theme is there a way to increase the resolution maybe with nvram setting?  Not sure if this parameter can be written to nvram?

	<key>GUI</key>
	<dict>
		<key>ScreenResolution</key>
		<string>1440x900</string>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>CustomEDID</key>
		<data>AP///////wAyDADfAAAAAAASAQOAIRV4CunVmVlTjigmUFQAAAABAQEBAQEBAQEBAQEBAQEB3iGgcFCEHzAgIFYAS88QAAAY3iGgcFCEHzAgIFYAS88QAAAAAAAA/gBXNjU3RwAxNTRXUDEKAAAA/gAjMz1IZYSq/wIBCiAgAJo=</data>
		<key>InjectEDID</key>
		<true/>
		<key>PatchVBios</key>
		<true/>
	</dict>


Share this post


Link to post
Share on other sites
	<key>GUI</key>
	<dict>
		<key>ScreenResolution</key>
		<string>1440x900</string>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>CustomEDID</key>
		<data>AP///////wAyDADfAAAAAAASAQOAIRV4CunVmVlTjigmUFQAAAABAQEBAQEBAQEBAQEBAQEB3iGgcFCEHzAgIFYAS88QAAAY3iGgcFCEHzAgIFYAS88QAAAAAAAA/gBXNjU3RwAxNTRXUDEKAAAA/gAjMz1IZYSq/wIBCiAgAJo=</data>
		<key>InjectEDID</key>
		<true/>
		<key>PatchVBios</key>
		<true/>
	</dict>


 

 

Thanks for helping.  Would the CustomEDID change if I wanted a higher resolution, 1920x1080?

 

For some odd reason it lowered the resolution even more and the text and bootcamp prompt is now even larger.

 

 

Edited:

 

I see that it can't set the 1920x1080 because log says its not found?  I see its setting it to 800x600.

0:348  0:001  Loading FSInject-64.efi
0:349  0:000  Loading OsxAptioFixDrv-64.efi
0:350  0:001  Loading OsxFatBinaryDrv-64.efi
0:351  0:000  Video bios patch requested or CustomEDID - forcing video reconnect
0:351  0:000  2 drivers needs connecting ...
0:351  0:000  PlatformDriverOverrideProtocol->GetDriver overriden
0:351  0:000  Video driver loaded: disconnect Success
0:415  0:063  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:415  0:000  VideoBiosPatchNativeFromEdid:
0:415  0:000   Bios: nVidia, nv_data_table_offset: 0x2B5, nv_data_table: 0xC02B7, std_vesa: 0xC4465, nv_mode_table: 0xC446A, mode_table_size: 0x10
0:415  0:000   VideoBiosPatchInit(LegacyRegion = Success) = Success
0:415  0:000   VideoBiosUnlock:  unlocked
0:417  0:002   Patching: BT_NVDA
0:417  0:000   Parse Edid: descriptor block 0 is timing descriptor (h_active: 1440, v_active: 900, h_sync_offset: 32, h_sync_width: 32, h_blanking: 112, v_blanking: 31, pixel_clock: 8670, v_sync_offset: 5, v_sync_width: 6)
0:418  0:000   patch 0: patched 1 time(s)
0:418  0:000   patch 1: patched 1 time(s)
0:419  0:000   patch 2: patched 1 time(s)
0:420  0:000   patch 3: patched 1 time(s)
0:420  0:000   VideoBiosLock: Success
1:261  0:841  LoadDrivers() end
1:261  0:000  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success
1:266  0:005  SetScreenResolution: 1920x1080 - not found!
1:266  0:000  Console modes reported: 4, available modes:
1:266  0:000    Mode 1: 80x25
1:266  0:000    Mode 3: 100x31 (current mode)
1:266  0:000    Mode 4: 128x40
1:266  0:000  SetScreenResolution: 800x600 - already set
1:266  0:000  reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,54ED2158-BDF8-4FF2-BC80-5056F922678E,0x28,0x64000)
1:266  0:000  new SelfHandle=5975B118
1:266  0:000  CPU Vendor = 756E6547 Model=306C3
1:266  0:000  The CPU supported turbo
1:266  0:000  BrandString = Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
1:266  0:000  MSR 0xE2 before patch 1E000405
1:266  0:000  MSR 0xE4              00021814
1:266  0:000  MSR 0xCE              00080838_F3011800
1:266  0:000  non-usable FLEX_RATIO = 50000
1:266  0:000  corrected FLEX_RATIO = 40000
1:266  0:000  MSR 0x1B0             00000000
1:266  0:000  FSBFrequency=100MHz
1:266  0:000  Corrected FSBFrequency=100MHz
1:266  0:000  Vendor/Model/Stepping: 0x756E6547/0x3C/0x3
1:266  0:000  Family/ExtFamily: 0x6/0x0
1:266  0:000  MaxDiv/MinDiv: 24.0/8
1:266  0:000  Turbo: 32/32/33/34
1:266  0:000  Features: 0xBFEBFBFF
1:266  0:000  Threads: 8
1:266  0:000  Cores: 4
1:266  0:000  FSB: 100 MHz
1:266  0:000  CPU: 2400 MHz
1:266  0:000  TSC: 2400 MHz
1:266  0:000  PIS: 400 MHz

Edited Again:

 

This is the log before I do the edits as you had.  It cannot find 1920x1024 and sets the resolution higher in this instance.

0:408  0:000  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:586  0:177  LoadDrivers() end
0:586  0:000  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success
0:592  0:006  SetScreenResolution: 1920x1080 - not found!
0:592  0:000  SetMaxResolution: found best mode 1: 1024x768Video mode change to mode #1: Success
0:748  0:155   - set
0:748  0:000  Console modes reported: 4, available modes:
0:748  0:000    Mode 1: 80x25
0:748  0:000    Mode 3: 100x31 (current mode)
0:748  0:000    Mode 4: 128x40
0:748  0:000  SetScreenResolution: 1024x768 - already set
0:748  0:000  reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,54ED2158-BDF8-4FF2-BC80-5056F922678E,0x28,0x64000)
0:748  0:000  new SelfHandle=5975B118
0:748  0:000  CPU Vendor = 756E6547 Model=306C3
0:748  0:000  The CPU supported turbo
0:748  0:000  BrandString = Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
0:748  0:000  MSR 0xE2 before patch 1E000405
0:748  0:000  MSR 0xE4              00021814
0:748  0:000  MSR 0xCE              00080838_F3011800
0:748  0:000  non-usable FLEX_RATIO = 50000
0:748  0:000  corrected FLEX_RATIO = 40000
0:748  0:000  MSR 0x1B0             00000000
0:748  0:000  FSBFrequency=100MHz
0:748  0:000  Corrected FSBFrequency=100MHz

Share this post


Link to post
Share on other sites

You need to use CsmVideoDxe-64.efi driver in order for a non UEFI video card to function correctly, otherwise you only receive a few basic modes that must be supported in UEFI firmware such as 800x600 and 1024x768. You also need an EDID that correctly identifies the mode you want to set. The one that slice posted was for 1440x900 as it shows in your log. There are many tools that you can use to generate an EDID, then either convert it to base64 with <data> tag or hex with <string> tag.

 

 

That did it.  Just adding that driver gave me back the 1920x1024 resolution in console/boot menu.  I am already injecting in DSDT nvcap etc not sure why I don't need EDID injection?

0:699  0:205    0 640x480 attr=3BF - ok, 640x480, working, highest, pref=0
0:701  0:001    1 800x600 attr=3BF - ok, 800x600, working, highest, pref=1
0:703  0:001    2 1024x768 attr=3BF - ok, 1024x768, working, highest, pref=2
0:705  0:001    3 1280x1024 attr=3BF - ok
0:715  0:010    4 1920x1080 attr=3BF - ok
0:717  0:001    5 1280x800 attr=3BF - ok
0:717  0:000  CsmVideo: New mode: 2 1024x768 - set
0:881  0:163   - SetMode pref 2 (2) = Success
0:881  0:000  CsmVideoCheckForVbe - Success
0:881  0:000  CsmVideoDriverBindingStart end Success
0:881  0:000  CsmVideo: New mode: 1 800x600 - blocking that switch
0:881  0:000  CsmVideo: New mode: 0 640x480 - blocking that switch
1:050  0:168  LoadDrivers() end
1:050  0:000  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success
1:056  0:005  SetScreenResolution: 1920x1080 - setting Mode 4
1:056  0:000  CsmVideo: New mode: 4 1920x1080 - set
1:364  0:308  Video mode change to mode #4: Success
1:364  0:000  Console modes reported: 4, available modes:
1:364  0:000    Mode 1: 80x25
1:364  0:000    Mode 3: 100x31 (current mode)
1:364  0:000    Mode 4: 128x40
1:364  0:000  SetScreenResolution: 1920x1080 - already set
1:364  0:000  reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,54ED2158-BDF8-4FF2-BC80-5056F922678E,0x28,0x64000)

Edited again:

 

Does this basically mean my GTX 770m is not a UEFI card?  Any way to truly tell?

 

 

 

Edited again:

 

Now nothing makes sense.  I have another laptop exactly same model this one has Clover 2747 the logs above are from Clover 2750.  On this laptop I do not have the CSMVideoDXe64 installed.

0:328  0:026  Found theme __MACOSX - no theme.plist
0:329  0:000  Found theme MaverickLogin_4_3
0:331  0:002  Found theme MaverickLogin_16_9
0:341  0:009  Found theme Shield
0:410  0:068  Loading early settings
0:410  0:000  timeout set to 4
0:410  0:000  Default theme: bootcamp
0:410  0:000  Hiding entries with string \EFI\BOOT\BOOTX64.EFI
0:410  0:000  Hiding entries with string Windows
0:410  0:000  LoadDrivers() start
0:429  0:019  Loading HFSPlus.efi
0:440  0:011   - driver needs connecting
0:440  0:000  Loading OsxAptioFixDrv-64.efi
0:448  0:008  Loading EmuVariableUefi-64.efi
0:463  0:014  EmuVariableUefi Initialize: VariableCommonInitialize = Success, orig services stored, install gEmuVariableControlProtocolGuid = Success
0:464  0:001  Loading FSInject-64.efi
0:479  0:014  1 drivers needs connecting ...
0:479  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
0:479  0:000  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:672  0:193  LoadDrivers() end
0:672  0:000  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent = Success, done
0:678  0:005  SetScreenResolution: 1920x1080 - already set
0:678  0:000  Console modes reported: 4, available modes:
0:678  0:000    Mode 1: 80x25
0:678  0:000    Mode 2: 80x50
0:678  0:000    Mode 3: 100x31
0:678  0:000    Mode 4: 128x40 (current mode)
0:678  0:000  SetScreenResolution: 1920x1080 - already set
0:678  0:000  reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,60377C13-636F-41D7-948F-18F0C7709F2D,0x28,0x64000)
0:678  0:000  new SelfHandle=59466418
0:678  0:000  CPU Vendor = 756E6547 Model=306C3
0:678  0:000  The CPU supported turbo
0:678  0:000  BrandString = Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
0:678  0:000  MSR 0xE2 before patch 1E000405

Share this post


Link to post
Share on other sites

Do they have the same firmware versions? It appears that they are either not truly identical, which is entirely possible even when they are the same model, or you need to upgrade the firmware on one of them.

 

 

Both have the same windows driver/firmware.   I did not realize that the one that needs the CSMVideoDXE driver is the one on OSX 10.9.4 and the other that does not need it is on 10.9.3.  So that must be why.  Both on Clover 2751 now.

 

Thanks

Share this post


Link to post
Share on other sites
post-702252-0-80012500-1403470611_thumb.png
post-702252-0-59581100-1403470663_thumb.png

Hi, a help from you, you who are more experienced.

I have the problem for artifacts with Intel HD3000 integrated in my laptop... the problem occurs with both the Mavericks and Yosemite.

 

I have selected various combinations - EDID and configuration in the Clover.

I have not solved the problem.

 

Thanks to all for your help

Hi all,

obody has a solution, i'm sorry do not use Clover.....  :(

 

the problem is intermittent.

Share this post


Link to post
Share on other sites

Hi, a help from you, you who are more experienced.

I have the problem for artifacts with Intel HD3000 integrated in my laptop... the problem occurs with both the Mavericks and Yosemite.

 

I have selected various combinations - EDID and configuration in the Clover.

I have not solved the problem.

 

Thanks to all for your help

 

 

I used to have the same HD3000 artifact problem and I solved it by adding 'slide=0' into the Boot arguments. 

 

Not sure but why don't you give it a try.

Share this post


Link to post
Share on other sites

I used to have the same HD3000 artifact problem and I solved it by adding 'slide=0' into the Boot arguments. 

 

Not sure but why don't you give it a try.

 

Thanks let you know!

Share this post


Link to post
Share on other sites

I used to have the same HD3000 artifact problem and I solved it by adding 'slide=0' into the Boot arguments. 

 

Not sure but why don't you give it a try.

I confirm, this is the trick.

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 zebity
      Hi Hypervisors,
       
      I have been working to move my Late 2009 Xserve MacOS Server onto Ubuntu 18.04 LTS QEMU/KVM based virtual machine using OVMF and Clover.
       
      After much effort and testing based on the following information from: Kraxel's, Kholia, Gordon Turner and Clover site:
      https://www.kraxel.org/blog/2017/09/running-macos-as-guest-in-kvm/
      https://github.com/kholia/OSX-KVM
      https://gist.github.com/gordonturner/2a2e5ecde5e7860b52e2
      https://clover-wiki.zetam.org/Home
       
      I have now managed to get OVMF/Clover boot and install of MacOS Sierra.
       
      I started with Ubuntu 16.04 initially but this required download and compile of QEMU to get update of machines to: pc-q35-2.9 or better, so I moved to Ubuntu 18.04, which has pc-q35.2.11 available as standard.
       
      So I am now working with standard Ubuntu 18.04 LTS based systems with following packages: kvm/qemu/libvirt/bridge-utils/ovmf/virt-manager
       
      As I want to use PCIe Passthrough for a number of PCIe card currently installed in the server (SmallTree 10GbE & Areca ARC-1883 SAS RAID) I set up my machine with linux kernel boot configuration (/etc/default/grub) of: 
      GRUB_CMDLINE_LINUX_DEFAULT="iommu=1 intel_iommu=on" (as my machine is intel VT-d based HW virtualisation)
       
      This resulted in creation of a number of iommu groups (see /sys/kernel/iommu_group directory for this and this posting for information: https://forum.level1techs.com/t/ubuntu-17-04-vfio-pcie-passthrough-kernel-update-4-14-rc1/119639 , noting that Ubuntu 18.04 LTS has kernel version: 4.15.0-22-generic so there is no need to do kernel update for iommu to work).
       
      Using bare minimal Clover config.plist:
       
       
      And following Clover UEFI drivers:
       
      I can boot MacOS, but it is very very slow... it sits on the apple boot logo for over a minutes before finally moving onto the progress bar.
      The other problem I have is that no PCI or Network devices appear in the "About This Mac" System Information Report and I cannot get any network connectivity from bridged E1000 network device.
       
      Here is my virtlib.xml dump for the virtual machine:
       

      Can any one advise of whether I need to update the CLOVER config.plist to add extra items in to allow network and PCI Passthrough to work.
       
      Thank you.
       
      Regards,
       
      Zebity
       
    • By frankiee
      Hi there, time for my first guide after asking so many things
       
      Updated for newer Clover versions and with additional instructions for more apps: gdisk and RU.
       
      So what may be overlooked sometimes in the whole boot loader discussion is the ability of UEFI to do more than just loading an OS. This is why I see ".efi" files as "apps" because in fact they just are, built on a special kind of API: UEFI. So, you can actually do stuff like editing, diagnosing, testing certain stuff at the lowest possible system level without booting to any OS.
       
      DISCLAIMER: Use this guide at your own risk! For educational purposes only! Should do not any harm, but remember you are dealing with rather low level stuff. But at least for me everything went flawless.
       
      Prerequisites:
      Working clover installation Clover Configurator or some app to edit the config.plist  
      1) Memtest
       
      This is how to install the UEFI version of Memtest with Clover:
      Download memtest, I used this link: Image for creating boot-able USB Drive Open the archive by double clicking on it. Mount the file memtest86-usb.img within by double clicking again. Now, you should see a folder named EFI in this volume, containing a folder BOOT. Open it. The files containing it are the actual app, in 32 and 64 bit versions. Think in almost all cases we want to use the 64 bit version. Now, mount your EFI partition, using Clover configurator. Create a folder named MemTest86 in the EFI folder on your main drive. Copy all files in the EFI/BOOT folder from the mounted image to your newly created folder. That ends the basic setup! Now, we add the correct Menu entry to the clover boot menu, so that we can actually start this app.
       
      Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Under "Custom Entries", add an entry like this:
       

       
      Please note while the path you enter is not case sensitive, you must make sure you use the backslash "\" for entering paths, and not a slash. So basically what we do is tell clover where it can find the app, give it a name, and tell clover it is a "Windows" app. Note: with older Clover versions we had to set this to "Linux", but for now "Windows" is the setting that works.
       
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <true/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>MemTest86</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string>\EFI\CLOVER\themes\Icons\os_mint.png</string> <key>Path</key> <string>\EFI\MemTest86\BOOTX64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> Now, save and reboot and you should see the newly created entry. Note that I also used a custom Icon - this is optional - in case you don't you will just see a generic windows icon instead:
       

       
      And this is how it looks like:
       

       

       
      PS: also noticeably faster and you get also more features with this version than with the older version, for example it does now write a log file. For more Information, see: http://www.passmark.com/forum/showthread.php?4315-Memtest86-Version-5-Beta-%28Pure-UEFI%29
       
       
      2) gdisk
       
      Another app you can use is the UEFI version of gdisk (aka GPT fdisk), which you can use to edit and change your partitions.
       
      Warning! Install and use this app at your own risk! If you do something wrong here you might nuke your drive(s), so only use that if you know what you are doing.
       
      This is how to do it (even easier):
      Download here: https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.1/gdisk-binaries/gdisk-efi-1.0.1.zip/download Mount your EFI partition Unzip the file and copy the resulting folder to your EFI Folder, so your path goes like this "/Volumes/EFI/EFI/gdisk-efi" Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Add an entry like this:  
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <false/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>GDisk</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string></string> <key>Path</key> <string>\EFI\gdisk-efi\gdisk_x64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> When everything went OK you should see this after selecting the respective entry in Clover:
       

       
       
      3) RU
       
      I recently found one more app that might be interesting to some, and thats "Read Universal" or in short "RU". This is a tool that enables you to debug your BIOS and read (and modify!) every imaginable data, including UEFI variables, ACPI Tables etc.
       
      Warning, again! I think blindly messing around with this app is even more dangerous, but on the other hand it gives you access to a lot of potentially interesting stuff.
      Download here: http://ruexe.blogspot.de/ The next steps are basically the same as above so make a folder in your EFI partition, copy the .EFI files and make another custom entry in your config.plist Here are some screens:
       

       

       

       
       
      So this is what you also can do with UEFI and clover. I am curious which other useful applications might exist!
       
      Anybody who knows, maybe post it here?
    • By TimNeumann
      MB: Asus X99 A-II
      RAM: G.Skill Ripjaws V F4-3200C16D-32GVK (3200MHz, 4x 16GB DIMMs, so Total 64GB) in quad-channel configuration.
      CPU: i7 6800k @4.0Ghz
      GPUs: GTX 1080 Ti and GTX 1060 3GB
      (each one a monitor, because I can't get DVI to run parallel with DP on the 1080Ti, and my second monitor only has DVI/VGA)
      OS: High Sierra 10.13.2 (17C88) / Clover revision: 4392
       
      Hello everybody,
      I occasionally have system crashes and suspect that it is related to RAM. However, this RAM is completely new, and a run with MemTest86+ from the USB stick showed no errors. However, if I use Memtest on MacOS, I get a bunch of error messages, but sometimes none (I restart the computer between tests).  
      As I just discovered, my RAM is not on the recommended vendor list of my motherboard, nor is it on the manufacturer side of the RAM. I have read several times that the RAM may not have been tested by the manufacturer on this platform. Not a single X99 motherboard is listed for this RAM.
      So I also suspect that my RAM is not compatible.
      But if that were the case, how could it sometimes work completely error-free?
       
      During RAM tests in summer 2017 (a slightly different setup, 4x8GB but still G.Skill Ripjaws V) I had no errors at Memtest under MacOS, if I remember correctly. At that time it ran under Sierra 10.12.6. AptioMemoryFix.efi could also cause problems.
      I am appreciative for any help!
       
      Here is an excerpt from a faulty test.
      It is noticeable that it is always the same address during the test, but a different one after each test.
      Memtest version 4.22 (64-bit) Copyright (C) 2004 Charles Cazabon Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port) Licensed under the GNU General Public License version 2 only Mac OS X 10.13.2 (17C88) running in multiuser mode Memory Page Size: 4096 System has 12 Intel core(s) with SSE Requested memory: 57232MB (60012990464 bytes) Available memory: 57232MB (60012990464 bytes) Allocated memory: 57232MB (60012990464 bytes) at local address 0x00000001033e1000 Attempting memory lock... locked successfully Partitioning memory into 2 comparison buffers... Buffer A: 28616MB (30006495232 bytes) starts at local address 0x00000001033e1000 Buffer B: 28616MB (30006495232 bytes) starts at local address 0x00000007ffc4d800 Running 1 test sequence... (CTRL-C to quit) Test sequence 1 of 1: Running tests on full 57232MB region... Stuck Address : ok Linear PRN : testing 7 of 16 FAILURE! Data mismatch at local address 0x0000000e88133d30 Expected Data: 0xc4c340079ac9a645, Actual Data: 0xc4c3400788468846 Running comparison tests using 28616MB buffers... Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : testing 80 of 256 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x4f4f4f4f4f4f4f4f, BUFB Data: 0x4f4f4f4f88468846 Checkerboard : testing 3 of 64 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x5555555555555555, BUFB Data: 0x5555555588468846 Bit Spread : testing 1 of 128 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000005, BUFB Data: 0x0000000088468846 Bit Flip : testing 74 of 512 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000200, BUFB Data: 0x0000000088468846 Walking Ones : testing 40 of 128 Clover Files attached
      config.plist
      drivers64UEFI.zip
      kexts.zip
      ACPI.zip
    • By BurpSuite
      screenshot:
       

       
      description:
      github: https://github.com/burpsuite/clover_theme
×