Jump to content
ErmaC

Clover General discussion

20,012 posts in this topic

Recommended Posts

2 hours ago, Mork vom Ork said:

just installed CLOVER rev. 4528. But when i reboot, it still shows rev. 4525, also in the log it states to 4525:

 

0:100  0:000  Starting Clover revision: 4525 on American Megatrends EFI

 

But CLOVER PrefPane shows this:

clover_prefpane.jpg.cc4fcce76fd584fed4a33cb073e6cf12.jpg

Seems Legacy r4528 is working properly here, only I got no injected kexts version info but it's not mandatory. Thanks.

Clover-Pref-r4528.png

preboot-r4528.zip

Share this post


Link to post
Share on other sites
Advertisement
8 hours ago, Mork vom Ork said:

just installed CLOVER rev. 4528. But when i reboot, it still shows rev. 4525, also in the log it states to 4525:

 

0:100  0:000  Starting Clover revision: 4525 on American Megatrends EFI

 

But CLOVER PrefPane shows this:

 

I may propose that you installed CLOVERX64.EFI but booted from BOOTX64.EFI or even bootmgfw.efi

Share this post


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

I may propose that you installed CLOVERX64.EFI but booted from BOOTX64.EFI or even bootmgfw.efi

Show warning in installer when BOOTX64.EFI and bootmgfw.efi are present and differ from fresh CLOVERX64.EFI?

Share this post


Link to post
Share on other sites

Guys, is the Clover Wiki up to date in terms of how to build Clover from sources?

Cause it seems a bit outdated to me. And...since SF doesn’t really works for me to download the source from terminal, i’ll try to download it from web (hopefully that will work) and build Clover locally.

 

But yesterday when I tried that, using the method and the commands on the Wiki page, I got an error (I can’t remember the error now). So I thought I would ask, in case that procedure needs some kind of update in order to build the latest Clover.

 

 

Share this post


Link to post
Share on other sites
23 minutes ago, ellaosx said:

The wiki has not been updated for years afaik. 

Try build_clover in github by mickey1979

 

Well, that's the problem... SVN cuts my connection when I try to download larger amount of data (in order to create the build environment). That's what I was using so far, but at least recently, SF is really, really {censored} for downloading larger amounts of data (you can see my post above, for more info). And apparently I'm not the only one.

 

And that script apparently doesn't work with anything other than SVN. I would have used tianocore/edk2 source from Github...but I don't know which commit should be the equivalent of r27233 from svn. And...the latest Clover changes are still on SVN for as far as I know.... So, even if I use some other clone of that source, from github, since it's not the official one, I still don't have access to the latest changes. Which defies the purpose of trying to build Clover in the first place. I really don't know what to do.

 

I tried to download the sources manually and then run that script...but that didn't work. It still tries to connect to SVN...which again is down. So...that's why I was asking for an updated build method, using sources already downloaded (assuming I can download them without SF cutting my connection over and over again).

 

Even the main page of sourceforge is down. I don't know how do they expect anyone to get any work down with this kind of server issues.

 

325097108_ScreenShot2018-06-11at15_20_57.png.ce8ad2ac93d9c6416907fdd6497be70b.png

Edited by arsradu

Share this post


Link to post
Share on other sites
 
Well, that's the problem... SVN cuts my connection when I try to download larger amount of data (in order to create the build environment). That's what I was using so far, but at least recently, SF is really, really {censored} for downloading larger amounts of data (you can see my post above, for more info). And apparently I'm not the only one.
 
And that script apparently doesn't work with anything other than SVN. I would have used tianocore/edk2 source from Github...but I don't know which commit should be the equivalent of r27233 from svn. And...the latest Clover changes are still on SVN for as far as I know.... So, even if I use some other clone of that source, from github, since it's not the official one, I still don't have access to the latest changes. Which defies the purpose of trying to build Clover in the first place. I really don't know what to do.
 
I tried to download the sources manually and then run that script...but that didn't work. It still tries to connect to SVN...which again is down. So...that's why I was asking for an updated build method, using sources already downloaded (assuming I can download them without SF cutting my connection over and over again).
 
Even the main page of sourceforge is down. I don't know how do they expect anyone to get any work down with this kind of server issues.
 
325097108_ScreenShot2018-06-11at15_20_57.png.ce8ad2ac93d9c6416907fdd6497be70b.png
yes. now i can't commit some parts. i'm waiting that sf will be fix from large amount of data(connection issue)

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
3 minutes ago, arsradu said:

Ok, so the Github correspondent for EDK2 SVN r27233 would be: https://github.com/tianocore/edk2/commit/77ca824c652443bdf3edaa0bb109fd8225a71cd3. Not sure how much that would help...but anyway.

By the way, is this in use: https://github.com/svn2github/cloverefiboot ? :) 

 

Appears to be, that's the last commit from yesterday, so it probably does update daily at a certain time. However, that still relies on sourceforge. I wasn't having any trouble until today, it's a little slow.

Share this post


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

Appears to be, that's the last commit from yesterday, so it probably does update daily at a certain time. However, that still relies on sourceforge. I wasn't having any trouble until today, it's a little slow.

I'm assuming you're not trying to recreate the entire environment, right? Cause that part didn't work for me. :)) I'm trying to get to sources from web...but I still need an updated tutorial on building the latest version, once the sources are downloaded. Cause the one on Wiki....seems a bit out of date. Not just in terms of the SVN revision used for EDK2, but also, I feel like there was something else necessary with the newer Clover versions. An extra step... I just can't remember what it was. And I think that part is missing from the Wiki, since it wasn't necessary before.

 

Anyway, to me, SF was massively unreliable over the past few days. That's why I was asking (and looking for Github alternatives) if there is any way we could migrate to Github entirely, or if there are any real benefits for using SF that I might be missing. Since the sources are (more or less) already on Github, I'm thinking it shouldn't be that difficult to switch to it. Please, correct me if I'm wrong. :)

 

I mean, if SF works for you guys, that's awesome. You need it the most. But if it doesn't...or if there are better tools/solutions, maybe it's time to switch to something better (if Github would be a better alternative). I don't know.. It's just a suggestion. And I'm asking since I'm sure you guys have a LOT more experience using these services than I do.

Edited by arsradu

Share this post


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

Guys, is the Clover Wiki up to date in terms of how to build Clover from sources?

Cause it seems a bit outdated to me. And...since SF doesn’t really works for me to download the source from terminal, i’ll try to download it from web (hopefully that will work) and build Clover locally.

 

But yesterday when I tried that, using the method and the commands on the Wiki page, I got an error (I can’t remember the error now). So I thought I would ask, in case that procedure needs some kind of update in order to build the latest Clover.

 

 

There is new instructions, proved yesterday with Xcode9.4

 

Share this post


Link to post
Share on other sites

Aaaalrighty!

 

So...SF still sucks. Big time. I had to download the sources from the web version and copy-paste the Clover folder inside /UDK2018 because the terminal command to clone the repo was always ending in an error such as the one below (not at the same point, but the same time-out error).

 

588669147_ScreenShot2018-06-11at17_45_03.png.ec1fcb49316b32366ad27787c6775539.png

 

Now, after that, next issue I had was with the edksetup.sh script, which, apparently doesn't like to be invoked with "./" anymore, creating this beautiful error:

1720314240_ScreenShot2018-06-11at17_55_45.png.af90e0755be24e2ec95ed25db2bb023a.png

 

After some googling, I found out that it it works ok if you use it as such: ". edksetup.sh". (maybe we can add this to the instructions, as well...? :)  I'm guessing this is something new they added, since I don't remember seeing it before...)

 

After that, everything went smoothly (used Patches_for_UDK2018 as instructed, since I'm planning on building the latest version of Clover) until I reached the next milestone upon building:

Generating BootSectors
[NASM] boot0af.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot0af
[NASM] boot0ss.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot0ss
[NASM] boot0md.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot0md
[NASM] boot1h.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1h
[NASM] boot1h2.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1h2
[NASM] boot1f32.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1f32
[NASM] boot1f32alt.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1f32alt
[NASM] boot1x.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1x
boot1x.s:188: error: short jump is out of range
boot1x.s:193: error: short jump is out of range
boot1x.s:204: error: short jump is out of range
boot1x.s:233: error: short jump is out of range
make: *** [/Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1x] Error 1

Now the question is: what did I miss?

Just to confirm, should nasm be in /opt/local/bin/...on the root directory? Or...in ~/src/opt/local/bin...? It just seems odd that there's already a similar structure in src. It's like it's inviting you to put it there. :))

Anyway, I'm asking because now it's in /opt/local/bin/, as instructed. And..apparently that doesn't work too well, for some reason.

Edited by arsradu

Share this post


Link to post
Share on other sites
3 minutes ago, Zenith432 said:

@arsraduIt's from old version of nasm.  do nasm -v on the one it's using.

NASM version 0.98.40 (Apple Computer, Inc. build 11) compiled on May  2 2018

 

But...why? :))

Share this post


Link to post
Share on other sites

It's a bug in the build process.

ebuild.sh calculates NASM_PREFIX using logic

BootHFS/Makefile just uses "nasm" and takes whatever is in the path

OTOH ebuild.sh also does pathmunge "$TOOLCHAIN_DIR/bin"

 

So if the nasm in the path is not the same as the one NASM_PREFIX you can end up using wrong nasm to build boot sectors and get this error.

Share this post


Link to post
Share on other sites
18 minutes ago, arsradu said:

NASM version 0.98.40 (Apple Computer, Inc. build 11) compiled on May  2 2018

 

But...why? :))

I told

Quote

3. Download NASM https://www.nasm.us/pub/nasm/releasebuilds/2.13.03/macosx/nasm-2.13.03-macosx.zip, unpack  and copy to     /opt/local/bin

The folder may be invisible then


sudo chflags nohidden /opt

or it may not exists then


sudo mkdir /opt

sudo mkdir /opt/local

sudo mkdir /opt/local/bin

then


sudo cp ~/Downloads/nasm-2.13.03/nasm /opt/local/bin

May be I forget to say how to set /opt/local/bin to be in priority

Share this post


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

I told

May be I forget to say how to set /opt/local/bin to be in priority

 

:) Yep, that's what I tried initially. But, as you saw above, I got an error. And that apparently was because I was using old nasm.

 

Now, /opt/local/bin is not present in etc/paths. Should I add it there?

 

2136436025_ScreenShot2018-06-11at19_12_44.png.e48f218ae6b66b47da3aa74aca31783e.png

Share this post


Link to post
Share on other sites

iHack:Clover Slice$ echo $PATH

/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin

It was needed for other project but I don't know the logic of new ebuild.sh, what is default NASM path.

Share this post


Link to post
Share on other sites

gate way issue happen when getting clover source from svn in windows.
normally, i commit source in windows after download clean clover source to avoid mistake.
but in last 2days, i never download clean source in windows from svn. always shown connection problem(gate way too. it means host disconnect my connection in sf. so i can't access sf site for some times). i just hope sf will back. because now i have a some part to cleanup clover source.

Aaaalrighty!
 
So...SF still sucks. Big time. I had to download the sources from the web version and copy-paste the Clover folder inside /UDK2018 because the terminal command to clone the repo was always ending in an error such as the one below (not at the same point, but the same time-out error).
 
588669147_ScreenShot2018-06-11at17_45_03.png.ec1fcb49316b32366ad27787c6775539.png
 
Now, after that, next issue I had was with the edksetup.sh script, which, apparently doesn't like to be invoked with "./" anymore, creating this beautiful error:
1720314240_ScreenShot2018-06-11at17_55_45.png.af90e0755be24e2ec95ed25db2bb023a.png
 
After some googling, I found out that it it works ok if you use it as such: ". edksetup.sh". (maybe we can add this to the instructions, as well...?   I'm guessing this is something new they added, since I don't remember seeing it before...)
 
After that, everything went smoothly (used Patches_for_UDK2018 as instructed, since I'm planning on building the latest version of Clover) until I reached the next milestone upon building:
Generating BootSectors[NASM] boot0af.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot0af[NASM] boot0ss.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot0ss[NASM] boot0md.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot0md[NASM] boot1h.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1h[NASM] boot1h2.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1h2[NASM] boot1f32.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1f32[NASM] boot1f32alt.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1f32alt[NASM] boot1x.s -> /Users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1xboot1x.s:188: error: short jump is out of rangeboot1x.s:193: error: short jump is out of rangeboot1x.s:204: error: short jump is out of rangeboot1x.s:233: error: short jump is out of rangemake: *** [/users/user/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1x] Error 1

Now the question is: what did I miss?
Just to confirm, should nasm be in /opt/local/bin/...on the root directory? Or...in ~/src/opt/local/bin...? It just seems odd that there's already a similar structure in src. It's like it's inviting you to put it there. :))
Anyway, I'm asking because now it's in /opt/local/bin/, as instructed. And..apparently that doesn't work too well, for some reason.



나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


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

iHack:Clover Slice$ echo $PATH

/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin

It was needed for other project but I don't know the logic of new ebuild.sh, what is default NASM path.

 

Yeeep, you already had it in $PATH from before. :P  No problem, I added it there now, as well. And made sure it's the right version.

NASM version 2.13.03 compiled on Feb  7 2018

But it couldn't have been that easy, now could it? :)) Now it says there is ' nothing to be done for "all" '.

 

Well, I disagree. I think there are a plenty of things to be done. For all! :)) Not sure what does it mean by that.

 -> VBoxHfs-64.efi
  -> GrubEXFAT-64.efi
  -> GrubISO9660-64.efi
  -> GrubNTFS-64.efi
  -> GrubUDF-64.efi
  -> XhciDxe-64.efi
  -> CsmVideoDxe-64.efi
  -> EmuVariableUefi-64.efi
  -> OsxAptioFix3Drv-64.efi
  -> OsxAptioFix2Drv-64.efi
  -> OsxAptioFixDrv-64.efi
  -> OsxFatBinaryDrv-64.efi
  -> OsxLowMemFixDrv-64.efi
  -> PartitionDxe-64.efi
  -> UsbMouseDxe-64.efi
  -> UsbKbDxe-64.efi
  -> Fat-64.efi
  -> EnglishDxe-64.efi
  -> NvmExpressDxe-64.efi
  -> Ps2MouseDxe-64.efi
  -> VBoxExt2-64.efi
  -> VBoxExt4-64.efi
  -> VBoxIso9600-64.efi
  -> HashServiceFix-64.efi
Copy Applications:
  -> bdmesg.efi
Done!

Generating BootSectors
make: Nothing to be done for `all'.
Done!
Edited by arsradu

Share this post


Link to post
Share on other sites

I just run build_clover script under Ubuntu 18.04 and also got issue with network connectivity.. it seems something wrong with the server but I'm not really sure, done with local ~/src rebuilt from scratch this morning under mac, then tonight we see this.

Screenshot from 2018-06-11 23-45-12.jpg

Share this post


Link to post
Share on other sites
27 minutes ago, arsradu said:

But it couldn't have been that easy, now could it? :)) Now it says there is ' nothing to be done for "all" '.

 

Well, I disagree. I think there are a plenty of things to be done. For all! :)) Not sure what does it mean by that.

./ebuild.sh cleanpkg

Share this post


Link to post
Share on other sites

Hi guys...

 

while everything just worked fine with Clover_v2.4k_r4522, system boot fails on both my X299 and X99 Systems with clover Clover_v2.4k_r4532. After several months,  I am again confronted with memory allocation errors or system boot failures at *********.

 

Did you change once more AptioMemoryFix.efi,  or what is the source of the problem? 

 

If I change back to Clover_v2.4k_r4522, everything works as expected. 

 

This morning I was able to download and build Clover_v2.4k_r4532 with Build_Clover.command on my X99 system after deleting the "src" directory in my home directory. However, on my X299 system, the clover build failed even after deleting the src directory and rebuilding clover from scratch.

 

Now , when I try to download and build clover from scratch, I also get server connection errors as already reported by others... 

 

Any thoughts on the above? Hope we can find the way back to a working clover configuration. 

 

Cheers,

 

KGP

 

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
       
      ---Extract one Full dump for DSDT edits, post files---
       
      RunMe.app

      https://www.youtube.com/watch?v=k9wmIfGLe3A
       
      ---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 fusion71au
      Clover r5051 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_r5051 for VMware.zip". Mount Clover-v2.5k-5051-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 shinho73
      Hello everyone. I managed to install AMD Sierra V5(10.12.6) on my old AMD A8 7600 PC(Mother Board-A58M-E, GPU- Palit Geforce GT730 DDR3). Everything is working except the GPU. The GT730 DDR3 GF108 is natively supported on Sierra, but for some reason, it is not working. On Clover Config, "Inject Nvidia" is selected, no Nvidia Web, and nv_disable=1. On "About This Mac" it just says " NVIDIA Chip Model 3 MB".
      I have attached config.plist. Can someone look at it please? Any help will be greatly appreciated. Thank you. 





      config.plist
    • 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
       
       
       
       
       
       
       
       
       
       
       
       
       
×