Jump to content
ErmaC

Clover General discussion

19,645 posts in this topic

Recommended Posts

Advertisement
21 hours ago, Slice said:

Clover package contains a shell that will work if launch it from clover.

Weird is, now I'm also having a same issue even running Clover's UEFI Shell through VM (VirtualBox)..

with or w/o drivers64UEFI/EnglishDxe-64.efi installed.

Screenshot 26.png

Share this post


Link to post
Share on other sites
21 hours ago, Slice said:

Clover package contains a shell that will work if launch it from clover.

how is working ? how activate or run or enter in shell mode ? what must be make for this efi shell ? tky

Share this post


Link to post
Share on other sites
1 hour ago, corint1 said:

how is working ? how activate or run or enter in shell mode ? what must be make for this efi shell ? tky

Use this option on your config.plist:

	<key>GUI</key>
	<dict>
		...
		<key>Scan</key>
		<true/>
		...
	</dict>



Screenshot 27.png

Edited by Badruzeus

Share this post


Link to post
Share on other sites
25 minutes ago, Badruzeus said:

Use this option on your config.plist:


	<key>GUI</key>
	<dict>
		...
		<key>Scan</key>
		<true/>
		...
	</dict>

 

thank you ... can you post an EFI folder with all files needed for activate sound ? I do not manage or did not understand what to do ...

 

Share this post


Link to post
Share on other sites
16 minutes ago, STLVNUB said:

Pity all the OTHER bits aren't included as well as this by itself is useless!

Did you mean BootChimeCfg.efi? You could include it into package manually, right? Hah haa

But *.wav files? Oh sh*t.. it makes the *.pkg "Not Sexy", can't imagine sound.wav && sound_night.wav from \themes will increase some MegaBytes in size, not a big deal since users are still able to customize by their selves (I think).



Screenshot 28.png

Edited by Badruzeus

Share this post


Link to post
Share on other sites
Did you mean BootChimeCfg.efi? You could include it into package manually, right? Hah haa
But *.wav files? Oh sh*t.. it makes the *.pkg "Not Sexy", can't imagine sound.wav && sound_night.wav from \themes will increase some MegaBytes in size, not a big deal since users are still able to customize by their selves (I think).




485626210_Screenshot28.png.b68bb56d4847f18c39b7ead94c74862b.png




Please how to include BootChimeCfg.efi into clover package?


Sent from my iPhone using Tapatalk
Did you mean BootChimeCfg.efi? You could include it into package manually, right? Hah haa
But *.wav files? Oh sh*t.. it makes the *.pkg "Not Sexy", can't imagine sound.wav && sound_night.wav from \themes will increase some MegaBytes in size, not a big deal since users are still able to customize by their selves (I think).




485626210_Screenshot28.png.b68bb56d4847f18c39b7ead94c74862b.png




Please how to include BootChimeCfg.efi into clover package?


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
12 minutes ago, SavageAUS said:

Please how to include BootChimeCfg.efi into clover package?

 

I believe there's better way than this:

(Clover build root on my case is ~/udk, not ~/src)

Spoiler

// Update Clover
cd ~/udk/UDK2018/
svn co svn://svn.code.sf.net/p/cloverefiboot/code/ Clover
cd Clover
./ebuild.sh --ext-co -fr

// Manually adding *.efi files (I have prebuilt AudioPkg binaries) 
cp ~/udk/EXT_PACKAGES/AudioPkg/UDK/Build/AudioPkg/RELEASE_XCODE5/X64/BootChimeCfg.efi ~/udk/UDK2018/Clover/CloverPackage/CloverV2/EFI/CLOVER/tools

// Make PKG (Sorry, 3rd party themes are excluded on my case)
cd ~/udk/UDK2018/Clover/CloverPackage/
./makepkg --nothemes

 

 

Share this post


Link to post
Share on other sites
On 1/11/2019 at 2:29 PM, ellaosx said:

i got voodohda dump now.

 

voodoohda_dump.txt

 

Note: i am using applealc because voodoohda is only showing headphone & digital out.

 

On 1/11/2019 at 8:05 PM, Slice said:

OK, this is very problematic codec. I think BootChime can output to headphone. You have to choose this output in cfg and attach a headphone to hear something.

VoodooHDA can be tuned to use internal speaker. It was not happened because headphone has higher priority.

Change

nid20 config 0x90172110

nid30 config 0x02211020

I also think nid18 should be Microphone. I don't remember what is required config because I am not at home. 

And nid19 is internal mic.

 

what will be my codec #?

<key>NodesToPatch</key>
<array>
<dict>
	<key>Codec</key>
	<integer>???</integer>
	<key>Config</key>
	<string>0x90172110</string>
	<key>Node</key>
	<integer>20</integer>
</dict>
</array>

 

Share this post


Link to post
Share on other sites
On 1/12/2019 at 1:59 PM, Slice said:

Clover package contains a shell that will work if launch it from clover.

OK, definitely it's possible with:

FS0:
cd EFI\CLOVER\tools
rm Shell64U.efi
cp Shell64.efi Shell64U.efi

I can run Legacy Shell version via UEFI > edit EFI\CLOVER\config.plist && save it as well but..

OFC "bcfg" is missing.. honestly, I don't really need bcfg since my AMI Bios comes with "Boot Entry" Options.

(Ah worse, nv vars are not saved using this.. #LoL)

 

From my test results with some of EFI Shell's, only v2.0 & v2.2 are running under UEFI.

Could be, limitation on my laptop with old AMI Aptio v2.01 firmware right?

 

No idea where these commits have gone (or replaced later with a better one), was from more than 5 years ago, I think #LoL

Spoiler

+  // dmazar: AMI Aptio 2.0 returns 0 as MaxVarSize - fix it
+  if (MaxVarSize <= 0) MaxVarSize = 16384;

 

 

_Shell2.zip

Share this post


Link to post
Share on other sites
3 hours ago, ellaosx said:

 

 

what will be my codec #?


<key>NodesToPatch</key>
<array>
<dict>
	<key>Codec</key>
	<integer>???</integer>
	<key>Config</key>
	<string>0x90172110</string>
	<key>Node</key>
	<integer>20</integer>
</dict>
</array>

 

 

From your dump I see

Probing codec #0...
 HDA Codec #0: Realtek (Unknown)
 HDA Codec ID: 0x10ec0256

Your codec # is zero.

 

39 minutes ago, Badruzeus said:

OK, definitely it's possible with:


FS0:
cd EFI\CLOVER\tools
rm Shell64U.efi
cp Shell64.efi Shell64U.efi

I can run Legacy Shell version via UEFI > edit EFI\CLOVER\config.plist && save it as well but..

OFC "bcfg" is missing.. honestly, I don't really need bcfg since my AMI Bios comes with "Boot Entry" Options.

(Ah worse, nv vars are not saved using this.. #LoL)

 

From my test results with some of EFI Shell's, only v2.0 & v2.2 are running under UEFI.

Could be, limitation on my laptop with old AMI Aptio v2.01 firmware right?

 

No idea where these commits have gone (or replaced later with a better one), was from more than 5 years ago, I think #LoL

  Reveal hidden contents

 

_Shell2.zip

Because UEFI 2.0 has no UnicodeCollation protocol.

Share this post


Link to post
Share on other sites
2 minutes ago, Slice said:

Because UEFI 2.0 has no UnicodeCollation protocol.

Ah, OK.. no worry then; I can still use old version of your Shell via Clover UEFI.

Also thanks for "> edit config.plist" ability, it's useful feature which is better than I've to boot into Linux for fixing wrong config.

Share this post


Link to post
Share on other sites
On 1/8/2019 at 12:28 PM, Dr. Hurt said:

Sorry if this has been asked before, but how do I get the boot chime with Clover legacy?

 

Which files do I need and where do I put them? Also, any changes needed in config? 

I'm using embedded theme.

 

Edit: Got it to work. A users' guide would still be useful though.

I'm guessing us users with BIOS (non UEFI) motherboards are out of luck? I get sound when in Clover Shell but not during boot.

Edited by pkdesign

Share this post


Link to post
Share on other sites
1 hour ago, pkdesign said:

I'm guessing us users with BIOS (non UEFI) motherboards are out of luck? I get sound when in Clover Shell but not during boot.

I get both if i combine slice & Goldfish64

Share this post


Link to post
Share on other sites

Are these 2 NVRAM vars created by BootChimeCfg (red rectangles)?

Correct me if I'm wrong; can we run eg. this command via Terminal w/o Shell > fs0:\efi\clover\tools\bootchimecfg then?

sudo nvram specialbootdevice blah blah blah

Thanks.

 

 

 

nvram -p.png
[/spoler]

 

#EDIT: ..and I have this on my preboot logs with r4847:

 

preboot.png

 

nvram_dmpstore_all_a43sj.txt.zip

Edited by Badruzeus

Share this post


Link to post
Share on other sites
14 hours ago, ellaosx said:

I get both if i combine slice & Goldfish64

What do you mean both? Could you tell me exactly what you did?

 

EDIT:
I added BootChimeDxe and got startup sound but immediately got red screen of death.

Edited by pkdesign

Share this post


Link to post
Share on other sites

 

I am able to get the test sound from BootChime.Cfg.efi in shell but it doesn't play at boot and it doesn't play under the Startup sound options in Clover. My system is UEFI based.

 

I am using

 

AudioDxe-64.efi from v2.4k_r4848 in drivers64UEFI

 

and

 

BootChime.Cfg.efi and BootChimeDxe.efi from Goldfish64 AudioPKG in tools.

 

How to further trouble-shoot?

 

 

Share this post


Link to post
Share on other sites
6 minutes ago, Tobiko said:

 

I am able to get the test sound from BootChime.Cfg.efi in shell but it doesn't play at boot and it doesn't play under the Startup sound options in Clover. My system is UEFI based.

 

I am using

 

AudioDxe-64.efi from v2.4k_r4848 in drivers64UEFI

 

and

 

BootChime.Cfg.efi and BootChimeDxe.efi from Goldfish64 AudioPKG in tools.

 

How to further trouble-shoot?

 

 

 

Do you put sound file in your theme folder? I think you do not use BootChimeDxe.efi (it's a driver not a tool). Some others members can help you better than me.

 

Take a look for parameters:

 

Share this post


Link to post
Share on other sites

Hi,

 

 

 

Thanks. I saw that thread. I used this as a guide but using the different file versions I mentioned. I use the Clovy theme which has a sound.wav in it. I also tried adding the sound.wav Slice provided to /EFI. 

 

I tried it on my desktop and it worked fine using BootChime.Cfg.efi from GoldFish64, the AudioDXE-64 from Clover and the Clovy theme which has a sound.wav. 

 

So on my laptop which is where this all started, I removed BootChimeDxe.efi rebooted, ran BootChime.Cfg.efi again it still worked from there. Cleared the NVRAM, ran BootChime.Cfg.efi and set up the device and volume again, rebooted a couple of times but still no luck. I even wiped clover and started fresh even recompiling the AudioPKG still not working on the Laptop. Just from the shell. 

Edited by Tobiko
tried additional steps

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

  • Similar Content

    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      Requirements
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

       
      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
       

       
      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave 18A391:  For macOS Mojave or High Sierra, use macOS_iso_creator.tool on page 4 of thread.
      UPDATE macOS Catalina Beta DP3_19A501i:  For Catalina, @jpz4085 has made an automated batch file to create a Catalina VM in Windows with iMac 14,2 SMBIOS.  You can still use my macOS_iso_creator.tool on page 5 to make an installer ISO to attach to the VM.
       
       
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By JackBauer24
      Hello,
       
      I have installed OSx86 10.11 (El Capitan) on April 2016 on my Asus Z170 Deluxe system.
       
      For installation I used this Thread.
       
      I used it a lot and it worked well. Meanwhile I switched to Linux and I use Win10 time to time. So OSX was forgotten. Also it did not boot correctly anymore.
       
      Now I wanted to start with a fresh installation and use OSX more often again. I want to use OSX 10.13 High Sierra. Is it working on my Asus Z170 Deluxe? I have the same Hardware as of April 2016 only the graphics card was updated to a Nvidia GTX1080.
       
      My Hardware in detail: Asus Z-170-Deluxe (Bios 3801), i7-6700k, EVGA GeForce GTX 1080 SC GAMING ACX 3.0, Samsung 950 Pro/M2 NVME 512MB, HDD 4 TB)
      Can I use some of support files from the old thread for the installation (see attachment)? Can I still use  Clover 2.3k r3292 Special Edition v2 ? Or do I need a newer version?
       
      Has someone installed High Sierra successfully on the Asus Z170 Deluxe ?
       
      About some hints where to start I would be thankful.
       
      regards
      JackBauer24
       
      Z170DeluxeFiles.zip
×