Jump to content
ErmaC

Clover General discussion

20,006 posts in this topic

Recommended Posts

3 minutes ago, vector sigma said:

creating folders for Clover is advised to have no blank spaces in the middle of the directory name

 

Or if they do, you need to take care of that with a "\ ". But yeah, better not use spaces. :)

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)
1 minute ago, arsradu said:

 

Or if they do, you need to take care of that with a "\ ". But yeah, better not use spaces. :)

The fact that edk2 scripts will fail later if a space exists

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)
2 minutes ago, vector sigma said:

The fact that edk2 scripts will fail later if a space exists

 

Oooh. THAT I did not know! :D I just don't like long names for directories anyways.

 

Thank you! Me learns every day.

Edited by arsradu

Share this post


Link to post
Share on other sites
On 7/26/2019 at 7:38 AM, Cyberdevs said:

I tested the app once more and there is no message like you said "ESP not found". here is the new output and the Terminal's screenshot:

 

Screen Shot 2019-07-26 at 9.58.55 AM.png

espfinder.plist.zip

Thanks! Anyway is wrong because I want disk0s1 and not disk1s1, why? I think your BIOS run device at index 0 automatically. I made an update and I think is now ok. You will see it with some great news.. in minutes.

Share this post


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

May be it is better to double efi folder on both disk0 and disk1?

I made some testing with apfs, core storage, Fusion and RAID with both hfs and APFS, the problem is that you can add a lot of Volumes. Plus I've no idea how to decompress each Payload from with in the package inside any potential ESP mirrored.

Share this post


Link to post
Share on other sites
Posted (edited)

new espfinder 0.3 Beta:

  1. RAID mirroring supported with both APFS and old filesystems
  2. Fusion drives
  3. CoreStorage
  4. mix of the above
  5. now a mount point is accepted as target volume
  6. a whole disk is accepted as well
  7. possibility to make the dump or not

 

new usage:

Usage examples:
espfinder -t disk2s4
or
espfinder -t /
or
espfinder -t /Volumes/VolName
or
espfinder -d -t /

-t	mount point or BSD Name, required option.

-d	a dump at ~/Desktop/espfinder.plist will be made.

so don't forget the -t option before the target disk or volume. Please try and report. To help me with debugging you have to ad -d as well:

espfinder -d -t /

and post espfinder.plist generated.

 

 

espfinder 0.3 Beta.zip

Edited by vector sigma
corrected the "usage" in 0.3

Share this post


Link to post
Share on other sites
15 minutes ago, Cyberdevs said:

@vector sigma

Here is the new dump from disk0s1 with espfinder 0.2

Hope this is the correct output.

espfinder.plist.zip

Yes but looks like you pass to it the esp already (disk0s1) so the result is easyly the same disk :P.  What's targeting any fusion/apfs etc. volume you have?

Share this post


Link to post
Share on other sites
Posted (edited)
14 hours ago, arsradu said:

@Slice I see a lot of people complaining about the drivers structure in 2.5k. And while I personally think the new structure makes a lot more sense than the old one, and while I think people will always complain about something, I also think that part of the problem is the fact that we never told them about those changes.

 

Maybe...for important things that could potentially affect functionality, it would be best to have a message in the installer, to let the people know about those changes. A lot of things happen because of miscommunication. So....let's communicate. Efficiently.

 

Just my personal opinion, of course.

3 hours ago, arsradu said:

 

The installer doesn't compile with AptioMemoryFix anymore, for reasons independent of Clover. Which is why it's been removed. Simple as that.


Also, there are plenty of AptioFix options in the current installer. Just use OsXAptioFix3Drv (comes with fixes for NVRAM, too). Would it help if someone renamed it to AptioMemoryFix? Cause AptioMemoryFix is nothing more than OsXAptioFixDrv, + some upgrades.

 

Also, you don't need to adjust anything manually... 

 

For the Z370 boot issue, make sure all the drivers are in the new directories, that you have at least one AptioFix driver, but not more than that, and that should be all. I think a verbose log might help to determine a potential kernel panic, if that's what's happening in your case.

 

 

 

OsXAptioFix3Drv still doesn't work and my X299 system would NOT boot with it.  (I have two systems and one is a Z370 and one is a X299).  Fortunately, I did have a copy of AptionMemoryFix available and as soon as I installed it and removed the OsXAptioFix3Drv, the system booted. 

 

Also, actually, I did need to adjust the directories so that the both would boot.  That sounds like manual intervention to me. Had to move files from "drivers" to "drivers64EUFI", then delete the "drivers" folder and leave "drivers64UEFI", remove the aforementioned OsXAptioFix3Drv, then they would boot. 

 

And yes, I agree that communicating these changes in Clover and how someone might deal with them, that just might be a good idea....

Edited by meaganmargaret

Share this post


Link to post
Share on other sites
Posted (edited)
53 minutes ago, meaganmargaret said:

I did have a copy of AptionMemoryFix available and as soon as I installed it and removed the OsXAptioFix3Drv,

Hi, the question is why OsXAptioFix3Drv get selected. Doesn't happen by case, you choose it, at least in past.

As I've already said if one of the Memory Fix drivers are selected the installer takes care of deleting the conflictual ones as you cannot load more the one of them, so any of:

OsXAptioFixDrv.efi

OsXAptioFix2Drv.efi

OsxLowMemFixDrv.efi 

AptioMemoryFix.efi 

or any that has "memfix" or "aptiofix" in its name get deleted.

 

My point is that you have OsXAptioFix3Drv selected when you install Clover, things that happens only if you once selected him. Otherwise your AptioMemoryFix.efi will stay there alive until only you decide to delete it. So please ensure to uncheck OsXAptioFix3Drv in the installer the next time and for subsequent installations this will not happen again because the choice is not recordered.

53 minutes ago, meaganmargaret said:

Also, actually, I did need to adjust the directories so that the both would boot

Why? The installer made a perfect copy of your drivers64 and drivers64UEFI respectively in drivers/BIOS and drivers/UEFI, without deleting the old directories and their drivers so that you have to do nothing. And that only (only) happens if 'drivers' doesn't exist so that a migration only happen once. Clover now use drivers/UEFI or drivers/BIOS so is it useless to keep both just because if new path is found, that will be used.

 

Uncheck OsXAptioFix3Drv and you'll be fine. Directories just does nothing for Clover and the package only update new paths.

 

 

 

Edited by vector sigma
typo

Share this post


Link to post
Share on other sites
Posted (edited)
6 hours ago, telepati said:

Can somebody explain what are the differences between these three?

 

OsXAptioFixDrv.efi

OsXAptioFix2Drv.efi

OsXAptioFix3Drv.efi

 

From my memory (no pun intended):

 

OsXAptioFixDrv   -> first version, it was ok until Yosemite...I think? Then Apple changed something and it would just not work anymore. At least that's when I remember I had to update to OsXAptioFix2Drv.

OsXAptioFix2Drv -> as I said above, it fixed some issues with older (but not that old) versions of MacOS (at the time, called OS X).

OsXAptioFix3Drv -> added fixes for NVRAM (on boards without native nvram). No need for EmuVariable with this one.

 

Now, of course, there could be other changes, as well. These are just the ones I know of. :)

Edited by arsradu

Share this post


Link to post
Share on other sites
17 hours ago, vector sigma said:

Yes, just a double click with the mouse.

 

Can be any also "MyCoolDirectory" lol e.g.:

 

so create edk2 directory inside your cool directory:


mkdir -p ~/Desktop/MyCoolDirectory/edk2

then change directory:


cd ~/Desktop/MyCoolDirectory/edk2

then checkout Clover:


svn checkout https://svn.code.sf.net/p/cloverefiboot/code/ Clover

dowble click on:


~/Desktop/MyCoolDirectory/edk2/Clover/buildme

easy no?

 

EDIT

creating folders for Clover is advised to have no blank spaces in the middle of the directory name

 

Easy, right. Thanks a lot :) I've put a symlink of buildme on Desktop and I've keep src folder in /Users/my_name. More practical for me.

Share this post


Link to post
Share on other sites
10 hours ago, telepati said:

Can somebody explain what are the differences between these three?

 

OsXAptioFixDrv.efi

OsXAptioFix2Drv.efi

OsXAptioFix3Drv.efi

I for one can't see the reason for 3, surely there should be one and it adjusts itself accordingly

Share this post


Link to post
Share on other sites
32 minutes ago, Matgen84 said:

Easy, right. Thanks a lot :) I've put a symlink of buildme on Desktop and I've keep src folder in /Users/my_name. More practical for me.

Just updated with more usefull options :)

----------------------------------------------------------
buildme Beta, Clover v2.5k r5029
EDKII in use: vUDK2018
Patches in use: Patches_for_UDK2018

1) build Clover		   5) update Clover	     9) show diff
2) make pkg		   6) update edk2	    10) quit
3) make iso		   7) status
4) build all		   8) check remote changes
Please enter your choice: 8
Password: 
------------------------------------------------------------------------
r5029 | vectorsigma | 2019-07-28 11:34:38 +0200 (Sun, 28 Jul 2019) | 1 line
Changed paths:
   M /buildme

corretions and update for the buildme script
------------------------------------------------------------------------

 

Share this post


Link to post
Share on other sites
11 hours ago, telepati said:

Can somebody explain what are the differences between these three?

 

OsXAptioFixDrv.efi

OsXAptioFix2Drv.efi

OsXAptioFix3Drv.efi

As far as I remember fix2 is no more taking into account as redundant.

Share this post


Link to post
Share on other sites
Posted (edited)

r5030:

  1. espfinder. new way to mount the ESP using this command line. Is Beta so for now is only activated if /useespfinder is present in the root
    sudo touch /useespfinder
     The installation now fail if you select "Install in the ESP" but no ESP is found.
  2. README.txt created at old drivers64 and drivers64UEFI where is written for the changes made about new drivers directories.
Edited by vector sigma

Share this post


Link to post
Share on other sites
16 hours ago, telepati said:

Can somebody explain what are the differences between these three?

 

OsXAptioFixDrv.efi

OsXAptioFix2Drv.efi

OsXAptioFix3Drv.efi

My bad, I've only listed a driver that doesn't exist .. I was deceived by OsXAptioFix3Drv.efi

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, vector sigma said:

r5030:

  1. Instant log. At the and of the installation the log produced by the package is opened in your broswer for an instant view. In the log are present latest changes and new behaviour of the package. 
  2. README.txt created at old drivers64 and drivers64UEFI where is written for the changes made about new drivers directories.

 

About #1:

 

Can we make the instant log less instant and more...on demand? Like with a checkbox somewhere (maybe called View Log) at the end of the installer, and only open the browser, if that box is checked?

 

Oooor....even better, would it be possible to do it right inside of the installer, instead of opening a new browser window (kind of intrusive in my opinion)? This way, it will also match the installer's light mode/dark mode. If we do it in browser, it's always light (unless we add some css to it, which I think is a bit too much for a simple log), it pops up without anyone knowing about it and it can't be turned off.

 

I think the idea is good, but I think it needs a bit of refinement. :) 

 

About #2:

 

It's not a bad idea...but it's just as hidden as not saying anything. Nobody will see it unless they already know about it. And they won't know about it, if we don't tell them about it. And the log doesn't say anything about a README in their old drivers64* folders. Not to mention, I don't know if it's even worth adding that, if we show the log (and/or a message before the installation in which we say something like: "Drivers path has been changed from drivers64UEFI to drivers/UEFI, and from drivers64 to drivers/BIOS. Please, make sure everything is ok with your drivers before restarting your computer. "

[Continue/Cancel buttons]

 

They way I see it:

 

1. the message should be included inside the installer itself (doesn't necessarily need to be the actual install log, but just the important stuff from it, like an Announcement, if you wish). In this case, the message informs about changes in drivers folders structure.

2. should be displayed BEFORE making any changes (so that people can choose whether or not they wanna do it), so it can't be the log itself, since that one is generated at the end of the installation.

3. my suggestion would be something similar to this (but with a different content, of course). Now, I think this message is not from Clover itself, is it? But I've seen similar things with other packages (such as Nvidia's graphics driver). Anyway, if we can get the installer to show something like this, with a custom message, this is what I would go for.

 

264656665_Screenshot2019-07-28at20_13_05.thumb.png.830a7cf2405ba1bcc3972bf4b4ddac4f.png

 

Also, some typos inside the Clover log:

 

"reposytory" should be "repository" :) 

"vicevera" should be "vice-versa".

 

 

 

 

 

Edited by arsradu

Share this post


Link to post
Share on other sites
Posted (edited)

 

1 hour ago, arsradu said:

Can we make the instant log less instant and more...on demand? Like with a checkbox somewhere (maybe called View Log) at the end of the installer, and only open the browser, if that box is checked?

 

Oooor....even better, would it be possible to do it right inside of the installer, instead of opening a new browser window (kind of intrusive in my opinion)? This way, it will also match the installer's light mode/dark mode. If we do it in browser, it's always light (unless we add some css to it, which I think is a bit too much for a simple log), it pops up without anyone knowing about it and it can't be turned off.

Sorry but are you installing Clover every minutes of your life? Seriusly who cares of light/dark if the only purpose is to let you read a log where you can find installation errors (or user errors like "removing AptioMemoryFix.efi because OsxAptioFis3Drv.efi is installed) that you can fix before reboot?

Sorry again but this is a bit frustrating, because instead of read the log, your attention goes to the window appearance?? :cry: Is like watch a very beatifull Mother Nature-girl and focus to its poor shoes Lol.

(log as root and set the appearance like your user account.. and this will be fixed I guess ;)

 

1 hour ago, arsradu said:

About #2:

 

It's not a bad idea...but it's just as hidden as not saying anything. Nobody will see it unless they already know about it. And they won't know about it, if we don't tell them about it."

It's done for who can't install in the ESP (like RAID-APFS-Fusion drives) and for testing purpose, next time someone claim a "mount ESP" failure ... vector sigma will pop up sayng "Hey, have you tried sudo touch /useespfinder without recompiling Clover" ?. Until this day I think no one wants a poor tested stuff and since I've asked for help and only few tested it, never will be an option for a beta almost aplha software, just I give a chance to the user and a chance that someone with this problem is intrested in testing it and see if the problem is solved... and maybe a chance to have  a report of a success/failure back.

 

1 hour ago, arsradu said:

1. the message should be included inside the installer itself (doesn't necessarily need to be the actual install log, but just the important stuff from it, like an Announcement, if you wish). In this case, the message informs about changes in drivers folders structure.

2. should be displayed BEFORE making any changes (so that people can choose whether or not they wanna do it), so it can't be the log itself, since that one is generated at the end of the installation.

3. my suggestion would be something similar to this (but with a different content, of course). Now, I think this message is not from Clover itself, is it? But I've seen similar things with other packages (such as Nvidia's graphics driver). Anyway, if we can get the installer to show something like this, with a custom message, this is what I would go for.

No much words to say other than that this should be fantastic.... but what show up in your picture comes directly from Installer.app and we have no control on it. The Clover log is done anyway and I have no time to make complicate things as you asked, just I used already present resources (the log). A lot of things can be theorically be done, one of them is to not use a .pkg executed by Apple's Installer.app that is almost out of control of any developers, and write a new program that just does what a dev want. Changes are all explained here, but again, is frustrating to note no one cares about it, like Clover's installer should have a brain and also be telepath. Also I'm a lot surprised on how lot of peoples run the installer without even watch what one is going to install and w/o know that a boot failure can happen. In fact I always use a pen drive to test newer Clover, even if a change is done by me, and only later I'll proceed with the installation. Also Apple released an update recently that cause kernel panics, Clover is not realistically better of such big software House.

 

Thanks for make me aware of the typos.

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)

1. Maan...those were only suggestions. Not requests... And the whole point was to help make the user experience a little better by suggesting a few improvements. If you don't think they're necessary in any way, please, ignore my previous message.

 

Now I feel sorry for mentioning it.

 

2. I think you very well know that I always offered myself to help whenever necessary. I don't have a Fusion drive. So I couldn't test that. 

 

3. OK. I understand. Thanks for the info.

Edited by arsradu

Share this post


Link to post
Share on other sites
Posted (edited)
16 minutes ago, arsradu said:

Now I feel sorry for mentioning it.

no problems Bro' :wink_anim:, don't give too much weight to my words, my english is bad and I can't turn the words as well as I would like and being more "diplomatic" how I wish. Just I pass all the day working on Clover....

 

16 minutes ago, arsradu said:

I think you very well know that I always offered myself to help whenever necessary. I don't have a Fusion drive. So I couldn't test that. 

Wasn't a claim you didn't offer your help, you already did a lot of times. It is the entire eco system that looks a bit complicated..

 

Hope you didn't get offended for the comparison of the girl and its shoes, was a quip... just made to be humorous...

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)

The fact that I didn't mention the other things (which are already great) doesn't mean I don't see them. I just chose to focus on the improvements, and what could be done (in my opinion, of course), to make it even better! That's all.

 

And diplomatic or not, I can still feel your frustration. You could have written in Chinese, and I would have still get it.

Also, take it slow. Step by step. There is no rush. Things need to done right, not fast.

Rome wasn't built in a day. I guess you should know that. :) 

Edited by arsradu

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 MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI CLOVER Z390 DESIGNARE.zip
       
      ---OPENCORE FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI OPENCORE Z390 DESIGNARE.zip
       
      ---DSDT patch requests is here---
       
      https://olarila.com/forum/viewtopic.php?f=19&t=1131
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By kylon
      Cloud Clover Editor is an open source application that allows you to manage various Hackintosh Bootloaders configs everywhere.

      Open Cloud Clover Editor
       
      Cloud Clover Editor Wiki
      Cloud Clover Editor Sources
       
       
      Features
      Supports Clover EFI, Ozmosis, Chameleon, OpenCore GUI and Text Editor Mode CCE Bank Mobile friendly  
      Officially supported browsers
      Chrome 42+ Microsoft Edge 14+ Firefox 39+ Safari 10+ Opera 29+ Opera Mobile 12+ Chrome for Android 75+ Firefox for Android 67+  
       
      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  (Discontinued) 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 gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) ->  Link download
       Può essere solo aggiunto manualmente scaricando dal link sopra e collocandolo nella rispettiva cartella
       NOTA: in questo caso non selezionare nessun OsxAptioFixDRV durante l'installazione di clover oppure rimuovetelo                        successivamente. 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
       
       
       
       
       
       
       
       
       
       
       
       
    • By Alesss
      Good morning,
       
      I've the following pieces of hardware:
      - i7 6700K
      - GTX 1080
      - Asus Z170 Deluxe
      - NVME hard drives
       
      Yesterday I've successfully completed a High Sierra installation (I can't migrate to Mojave due to missing NVIDIA web drivers) but the system (even though it works correctly) seems to show a kernel panic at every shutdown/reboot.
       
      Please find the RunMe.app report attached.
       
      A couple of notes:
      - I've installed the audio kexts through the acidanthera AppleALC procedure
      - I've generated the SSDT with pikessdt script
      - Nvidia web drivers have been installed with the vulgo/webdriver.sh script that requires the WhateverGreen and the ngfxcompat=1 boot argument
      - AirportBrcmFixup.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext have been used to unlock the full potential of the integrated Wi-Fi card
      - I've tried to clean nvram and motherboard CMOS with no avail
      - I've tried to update Clover to the latest version but it always results in an unbootable system
       
      It's a pity because everything seems to work correctly (USB ports, graphics, Wifi card, Continuity and so on. I haven't tried sleep but I don't use it anyway ) but this crash is fairly annoying.
       
      Thank you very much,
      Alesss
       
      Send me Ales-iMac.zip
    • By Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
×