Jump to content
ErmaC

Clover General discussion

20,478 posts in this topic

Recommended Posts

Posted (edited)
23 minutes ago, pkdesign said:

Just updated to 4988 and am confused by install. There is a drivers64UEFI folder in clover folder.

 

1) Is this left over from my original 4972 install and was not deleted by Clover?

2) Will this be a problem when I restart?

3) Do I just put the drivers in the drivers64UEFI folder into the new drivers>UEFI folder and delete the driver64UEFI folder?

4) Why do I have a BIOS folder when I have a UEFI mobo and did not select any of those during install?

 

Thanks!

 

 

1) it's been decided to keep both the new folder scheme, and the old one, for retro-compatibility. But I feel like this created more confusion to the users.

2) unlikely (but just in case, make a USB drive with Clover on it and double check your drivers and drivers64UEFI folders). Make sure all your necessary drivers are in there.

3) if you're not planning on going back to an old version of Clover (which still uses drivers64 and drivers64UEFI scheme), without reinstalling that version, but by simply copy-pasting the drivers to your EFI/Clover folder, then yes, you can delete. In other words, if you want to use an older version, just use the damn installer! :)) Don't just copy-paste folders from one version to the other. Unless you rename them to match the old folder naming scheme (meaning drivers64 for BIOS and drivers64UEFI for UEFI booting).

4) Did you reselect UEFI drivers, along with the corresponding UEFI drivers? If yes...that might be a bug. Nothing to worry about. It just won't use those. But yeah, could be a bug.

Edited by arsradu

Share this post


Link to post
Share on other sites
Advertisement

hello Slice good night

 

something is wrong in clover .. that is only my opinion.. the value is zero

 

many people now is changing the source code .. clover is beginning slow to boot the OS, and not always boot the OS first time when u are doing a new update to the system.

what I want to say about this , u must begin to work the files in clover.. and do a cleanup in the source code .. I'm sure many lines are now deprecated.. I know is a hard job ... but I'm sure u are the right person to do this ... another point something is wrong in inject kext in Mojave and in Catalina..

 

sorry to disturb u , in all work u do for booting macOS 

 

all the best

 

Share this post


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

is it more correct to use the name "firmware" instead of drivers?

 

pic.png

No, there are drivers sorted by firmwares.

Share this post


Link to post
Share on other sites
Posted (edited)

@fusion71au Many thanks for the detailed post above. :) 

 

Problem is...nothing worked so far. :)) Probably in part due to the fact that I have almost 0 experience with booting Legacy (I didn't really need it), but also in part due to the fact that I'm probably doing something wrong (probably not related to the actual ISO, but we can't know for sure until I'm able to boot in Legacy mode).

I created an iso with everything ok in terms of config (thanks for the script), themes, all of that. Aaand...even with the embedded theme set up and the same config as the one I use for booting on a daily basis, I still get exactly the same result. Which makes me think maybe the problem is somewhere else.

 

Now, in terms of trying to load those drivers manually from EFI Shell...that didn't go too well either.

First of all, the DVD ROM is USB based (external). Not sure if this is relevant in any way. But I'm just mentioning it in case it is.

Second of all, it shows in Shell as blkC, with Alias (null).

So, while I can do blkC:, it doesn't seem to have anything inside (I tried a simple ls and I got some error, I don't remember which one exactly off the top of my head). I can't see the contents of the CD. And none of the other "fs" entries is linking to this CD-ROM. All of them are my hard disks/SSD. So not what I needed.

 

However, if I'm not mistaken, I've got the exact same issue when booting off of an USB drive, with Clover in Legacy mode. Booting in Legacy mode doesn't seem to work for me, for some reason. Never bothered to find out why, since my motherboard has an UEFI firmware. So I never needed to boot Legacy. 

But I was thinking, maybe I should focus on booting in Legacy mode first, then trying to understand (and debug) why booting off of the DVD doesn't work. Cause the reason might be the same. And it would take a lot less time to edit the files on a USB drive, than erasing and rewriting a CD every time I want to test a new scenario.

Also, I couldn't find an option in the UEFI menu to boot CDs in UEFI mode or something like that... So I don't think my motherboard has this feature.

 

I'll try to play with the Legacy mode a bit more, on a USB drive. See if I can get it to boot. We'll see what the results tell us after that. Since nobody else complained about booting in Legacy mode, I'm guessing it's probably something specific to my system.

Edited by arsradu

Share this post


Link to post
Share on other sites

@Sherlocks and all, r4994 should install in 10.15 by automatically change the root fs as rw (of course this is only done in 10.15+). There's a dialog anyone can translate in any language.

 

Clover_v2.4k_r4994.zip

 

@Slice take a look at localizable.strings and tell me if is now ok. To All, at the beginning of the localizable.strings now there are two new localization to be translated, as just said for the dialogs the package now show you in Catalina.

Share this post


Link to post
Share on other sites
1 minute ago, chris1111 said:

@vector sigma

I test the new distribution its like to be working  

I made it all "embeded" + a check for the OS should not be  older then catalina:

  function checkFileSystemIsWritable()
  {
    var result = true;
    if (-1 == system.numericalCompare('10.14.9', system.version.ProductVersion)) {
        result = false;
        var cmd = '/usr/bin/osascript -e\''
        cmd += 'do shell script "mount -uw /" with prompt '
        cmd += '"' + system.localizedString('MakingRootRW') + '"'
        cmd += ' with administrator privileges\''
        try
        {
           cmd = system.runOnce('/bin/sh', '-c', cmd);
           result = (cmd == 0);
           } catch (e) {
            system.log('mount -uw / returned with error: ' + e);
            result = false;
         }
         
         if (result == false) {
          my.result.message = system.localizedString('GoToFailRootRW');
          my.result.type = 'Fatal';
         }
     }
	system.log("checkFileSystemIsWritable() returned: " + result);
    return result;
  }

 

Share this post


Link to post
Share on other sites
1 minute ago, vector sigma said:

I made it all "embeded" + a check for the OS should not be  older then catalina:


  function checkFileSystemIsWritable()
  {
    var result = true;
    if (-1 == system.numericalCompare('10.14.9', system.version.ProductVersion)) {
        result = false;
        var cmd = '/usr/bin/osascript -e\''
        cmd += 'do shell script "mount -uw /" with prompt '
        cmd += '"' + system.localizedString('MakingRootRW') + '"'
        cmd += ' with administrator privileges\''
        try
        {
           cmd = system.runOnce('/bin/sh', '-c', cmd);
           result = (cmd == 0);
           } catch (e) {
            system.log('mount -uw / returned with error: ' + e);
            result = false;
         }
         
         if (result == false) {
          my.result.message = system.localizedString('GoToFailRootRW');
          my.result.type = 'Fatal';
         }
     }
	system.log("checkFileSystemIsWritable() returned: " + result);
    return result;
  }

 

Yea I see

did you find info from NPM site 

Share this post


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

did you find info from NPM site 

No on the Apple developer portal

Anyway this I guess cannot be killed by Apple because all this is done before even the target volume is selected. Which is also a downside if you want to install else where.

Edited by vector sigma

Share this post


Link to post
Share on other sites

Hi 

 

Sorry if is off-topic. I try to build r4994 and I got this issue...

 

Capture d’écran 2019-07-12 à 18.25.59.png

Share this post


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

I try to build r4994 and I got this issue...

Make:

Status = ReadDisk (
      DiskIo,
      DiskIo2,
      MediaId,
      EfiFileCurrentExtentOffset,
      EfiFileCurrentExtentSize,
      (CHAR8*)EfiFileBuffer + CurPos
      );

to be:

Status = ReadDisk (
      DiskIo,
      DiskIo2,
      MediaId,
      EfiFileCurrentExtentOffset,
      EfiFileCurrentExtentSize,
      EfiFileBuffer + CurPos
      );

in ApfsDriverLoader.c

Share this post


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

Make:


Status = ReadDisk (
      DiskIo,
      DiskIo2,
      MediaId,
      EfiFileCurrentExtentOffset,
      EfiFileCurrentExtentSize,
      (CHAR8*)EfiFileBuffer + CurPos
      );

to be:


Status = ReadDisk (
      DiskIo,
      DiskIo2,
      MediaId,
      EfiFileCurrentExtentOffset,
      EfiFileCurrentExtentSize,
      EfiFileBuffer + CurPos
      );

in ApfsDriverLoader.c

 

I do make a mistake because no more directories 

 

EDIT: I try to compile in Mojave 10.14.5 / Xcode 10.2.1

 

Capture d’écran 2019-07-12 à 18.46.46.png

Edited by Matgen84

Share this post


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

Did you use a script or did you do that manually? Any way something should appear in terminal...

 

I use manual makepkg in Terminal

 

========= Translating Resources ========
/Users/mathieu/src/udk2018/clover/cloverpackage/package/../../../../opt/local
Updating 'en' strings file for CloverUpdater... done
Updating 'en' strings file for Clover Preference Panel... done
Updating strings file for Clover Preference Panel... done
 (204 entries)

Updating 'en' strings file for CloverUpdater... done
Generating de interface... done
Generating es interface... done
Generating fr interface... done
Generating hr interface... done
Generating id interface... done
Generating it interface... done
Generating ja interface... done
Generating ko interface... done
Generating lv interface... done
Generating nl interface... done
Generating pl interface... done
Generating pt-BR interface... done
Generating pt interface... done
Generating ro interface... done
Generating ru interface... done
Generating tr interface... done
Generating uk interface... done
Generating vi interface... done
Generating zh_CN interface... done
Generating zh_TW interface... done
Building CloverUpdater application...
[XCODE]
Updating 'en' strings file for Clover Preference Panel... done
Generating de interface... done
Generating es interface... done
Generating fr interface... done
Generating hr interface... done
Generating id interface... done
Generating it interface... done
Generating ja interface... done
Generating ko interface... done
Generating lv interface... done
Generating nl interface... done
Generating pl interface... done
Generating pt-BR interface... done
Generating pt interface... done
Generating ro interface... done
Generating ru interface... done
Generating tr interface... done
Generating uk interface... done
Generating vi interface... done
Generating zh_CN interface... done
Generating zh_TW interface... done
Updating strings file for Clover Preference Panel... done
Check de strings... done
Check en strings... done
Check es strings... done
Check fr strings... done
Check hr strings... done
Check id strings... done
Check it strings... done
Check ja strings... done
Check ko strings... done
Check lv strings... done
Check nl strings... done
Check pl strings... done
Check pt-BR strings... done
Check pt strings... done
Check ro strings... done
Check ru strings... done
Check tr strings... done
Check uk strings... done
Check vi strings... done
Check zh_CN strings... done
Check zh_TW strings... done
Building CloverPrefpane preference...
[XCODE]
================= Making all in boot1-install =================
	[XCODE] boot1-install
================= Making all in partutil =================
	[XCODE] partutil
================= Making all in bdmesg =================
	[XCODE] bdmesg
================= Making all in clover-genconfig =================
	[XCODE] clover-genconfig

  -------------------------------
  Building Clover Install Package
  -------------------------------

====================== Preinstall ======================
	[BUILD] Pre
===================== Installation =====================
	[BUILD] UEFI.only
================== Target ESP ==========================
	[BUILD] Target.ESP
=================== BiosBoot ===========================
	[BUILD] BiosBoot
===================== Utils ============================
	[BUILD] Utils
===================== EFI folder =======================
	[BUILD] EFIFolder
===================== off drivers ======================
find: /Users/mathieu/src/udk2018/clover/cloverpackage/CloverV2/EFI/CLOVER/drivers: No such file or directory
	[BUILD] off
===================== BootLoaders ======================
	[BUILD] AltBoot
	[BUILD] bootNo
	[BUILD] boot0af
	[BUILD] boot0ss
====================== CloverEFI =======================
	[BUILD] cloverEFI.64.sata
===================== RC Scripts =======================
	[BUILD] rc.scripts.on.target
	[BUILD] rc.scripts.on.all.volumes
	[BUILD] rc.scripts.core
================= Optional RC Scripts ==================
	[BUILD] disable_sleep_proxy_client
======================== Themes ========================
	[BUILD] Clovy
	[BUILD] BGM
	[BUILD] cesium
	[BUILD] CloverThemeManager
==================== Clover Prefpane ===================
	[BUILD] CloverPrefpane
================= Post =================
	[BUILD] Post

 --------------------------
 Building process complete!
 --------------------------

 Build info.
 ===========
  Package name: Clover_v2.4k_r4994.pkg
  MD5:          91def03c5481e636a48ab21c1e213d12
  Version:      v2.4k
  Stage:        v2.4k
  Date/Time:    2019-07-12 18:33:46
  Built by:     mathieu
  Copyright     2012-2019

  adding: Clover_v2.4k_r4994.pkg (deflated 0%)
  adding: Clover_v2.4k_r4994.pkg.md5 (stored 0%)
total 35064
drwxr-xr-x   9 mathieu  staff      288 Jul 12 18:43 .
drwxr-xr-x  15 mathieu  staff      480 Jul 12 18:43 ..
-rw-r--r--@  1 mathieu  staff  8754566 Jul 12 18:43 Clover_v2.4k_r4994.pkg
-rw-r--r--   1 mathieu  staff       68 Jul 12 18:43 Clover_v2.4k_r4994.pkg.md5
-rw-r--r--   1 mathieu  staff  8733421 Jul 12 18:43 Clover_v2.4k_r4994.zip
drwxr-xr-x   3 mathieu  staff       96 Jul 12 18:43 Resources
drwxr-xr-x   6 mathieu  staff      192 Jul 12 18:43 build
drwxr-xr-x   3 mathieu  staff       96 Jul 12 18:43 package
drwxr-xr-x   6 mathieu  staff      192 Jul 12 18:43 utils

 

Share this post


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

Drivers directories are created by ebuild.sh. Run it before ..otherwise. And please post what's on your terminal entirely please.

 

All works fine under Mojave. Thanks :)

 

Please commit your new ApfsDriverLoader.c

Share this post


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

Make:


Status = ReadDisk (
      DiskIo,
      DiskIo2,
      MediaId,
      EfiFileCurrentExtentOffset,
      EfiFileCurrentExtentSize,
      (CHAR8*)EfiFileBuffer + CurPos
      );

to be:


Status = ReadDisk (
      DiskIo,
      DiskIo2,
      MediaId,
      EfiFileCurrentExtentOffset,
      EfiFileCurrentExtentSize,
      EfiFileBuffer + CurPos
      );

in ApfsDriverLoader.c

It rather should be (UINT8*)

Share this post


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

It rather should be (UINT8*)

is inited as VOID*, I guess it is compatible with the smallest size of UInt8. But yes.

Share this post


Link to post
Share on other sites

Hi @fusion71au !

 

So, after a long day of testing, I managed to find the cause for the red text screen with x64 Exception Type 06. And it seems to have something to do with Clover itself.

 

Older versions like 3911 work fine. But only if I select BiosBlockIO. With SATA, I get the exact same behavior (blinking cursor for a while, then "not found" then red screen). With BiosBlockIO it goes straight into Clover GUI (with a few icon issues for the embedded theme)...but it gets there. 

 

1706622046_Screenshot2019-07-12at23_59_51.thumb.png.bca66d81f2f6dbdbebbd1506ea19486b.png

 

Also, 3911 had its own issues (mouse and keyboard not working in Clover GUI). Fixed it by removing AppleKeyAggregator. Newer versions don't seem to have it, so I guess that's ok.

 

Another problem with 3911 is, of course, the fact that it can't boot Mojave (and not because of APFS, since I've got ApfsDriverLoader already in place, it's most likely the kext injection). :)) So...while I did get to the Clover GUI and I did manage to get my keyboard working so I can select the boot drive, I got stuck on my way to Desktop.

 

So, to sum up:

1. newer versions of Clover (such as 4993) don't have BiosBlockIO anymore, so I will get that red screen if I select the SATA option and try to boot in Legacy mode (and yes, it looks like I remembered correctly, I DO get the exact same issue booting off of the USB as I did booting from the DVD, and now we know why).

2. older versions (such as 3911) can boot ok in Legacy mode, but only if BiosBlockIO is selected. Same issue if SATA is selected. Problem here is that those versions can't boot newer MacOS versions, such as Mojave.

So...yeah, not sure why BiosBlockIO was removed for Legacy booting...but I can't seem to be able to boot otherwise.

 

So, in a nutshell, older Clover can boot to Clover GUI, but can't get any further, due to OS issues, newer Clover can't boot even into the GUI, due to SATA issues (red screen with "x64 Exception Type 06" error) but, in theory, it should be able to boot Mojave.

 

Maybe there's something in BIOS that should be checked in order for this to work with SATA, as well...? No idea. But so far, these are the results. :)

Share this post


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

is inited as VOID*, I guess it is compatible with the smallest size of UInt8. But yes.

I made this change because of what? 

It was initially VOID*, but it is not compatible with VS2013 (error C2036).

Share this post


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

Hi @fusion71au !

 

So, to sum up:

1. newer versions of Clover (such as 4993) don't have BiosBlockIO anymore, so I will get that red screen if I select the SATA option and try to boot in Legacy mode (and yes, it looks like I remembered correctly, I DO get the exact same issue booting off of the USB as I did booting from the DVD, and now we know why).

2. older versions (such as 3911) can boot ok in Legacy mode, but only if BiosBlockIO is selected. Same issue if SATA is selected. Problem here is that those versions can't boot newer MacOS versions, such as Mojave.

So...yeah, not sure why BiosBlockIO was removed for Legacy booting...but I can't seem to be able to boot otherwise.

 

So, in a nutshell, older Clover can boot to Clover GUI, but can't get any further, due to OS issues, newer Clover can't boot even into the GUI, due to SATA issues (red screen with "x64 Exception Type 06" error) but, in theory, it should be able to boot Mojave.

 

Maybe there's something in BIOS that should be checked in order for this to work with SATA, as well...? No idea. But so far, these are the results. :)

 

@arsradu,

 

I noticed the makeiso script formats the iso with -eltorito-boot, to allow for legacy BIOS booting, and it also uses boot6 instead of boot7 (BiosBlockIO) which works on your system.  I'm guessing the presence of the legacy BIOS code is what makes the CD-DVD-ROM "invisible" to your firmware when it is set to boot to "UEFI only".

 

Try the following modified makeiso files (place in ~/src/edk2/Clover/CloverPackage) to generate the Clover ISO instead of the default one...

makeiso_boot7.zip ---> uses boot 7 instead of boot 6 for legacy boot

makeiso_uefi_only.zip ---> removed -eltorito-boot formatting so only UEFI booting possible

 

PS BiosBlockIO is still available in the latest Clover Pkg installer r4995.  If the boot7/BosBlockIO installed by r4995 doesn't work, then simply replace it with the boot7 "boot" file from Clover r3911 (keep the rest of the files from Clover r4995, including CLOVERX64.efi, BOOTX64.efi and the new drivers folder file structure)...

 

BiosBlockIO.png.b2405cfea903cbfcee7b388de9265433.png1770777261_Bootfile.png.a70ac1b6f2c7150185c4c4e99ea329a9.png

 

Good Luck!

Clover_v2.4k_r4995.pkg.zip

Edited by fusion71au
typo

Share this post


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

It rather should be (UINT8*)

 

 

9 hours ago, vector sigma said:

is inited as VOID*, I guess it is compatible with the smallest size of UInt8. But yes.

 

exrpression (UNIT8*) don't work in Mojave / Xcode 10.2.1: can't compile. Please commit previous vector sigma diff or else.

 

make: Nothing to be done for `tbuild'.
make: Nothing to be done for `tbuild'.
make: Nothing to be done for `tbuild'.
make: Nothing to be done for `tbuild'.
make: Nothing to be done for `tbuild'.
/Users/mathieu/src/UDK2018/Clover/FileSystems/ApfsDriverLoader/ApfsDriverLoader.c:953:20: error: expected expression
            (UNIT8*)EfiFileBuffer + CurPos
                   ^
/Users/mathieu/src/UDK2018/Clover/FileSystems/ApfsDriverLoader/ApfsDriverLoader.c:953:14: error: use of undeclared identifier 'UNIT8'
            (UNIT8*)EfiFileBuffer + CurPos
             ^
2 errors generated.
make: *** [/Users/mathieu/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/Clover/FileSystems/ApfsDriverLoader/ApfsDriverLoader/OUTPUT/ApfsDriverLoader.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/mathieu/src/udk2018/Build/Clover/RELEASE_XCODE8/X64/Clover/FileSystems/ApfsDriverLoader/ApfsDriverLoader]


build.py...
 : error F002: Failed to build module
	/Users/mathieu/src/udk2018/Clover/FileSystems/ApfsDriverLoader/ApfsDriverLoader.inf [X64, XCODE8, RELEASE]

- Failed -

 

Share this post


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

 

 

 

exrpression (UNIT8*) don't work in Mojave / Xcode 10.2.1: can't compile. Please commit previous vector sigma diff or else.

 


make: Nothing to be done for `tbuild'.
make: Nothing to be done for `tbuild'.
make: Nothing to be done for `tbuild'.
make: Nothing to be done for `tbuild'.
make: Nothing to be done for `tbuild'.
/Users/mathieu/src/UDK2018/Clover/FileSystems/ApfsDriverLoader/ApfsDriverLoader.c:953:20: error: expected expression
            (UNIT8*)EfiFileBuffer + CurPos
                   ^
/Users/mathieu/src/UDK2018/Clover/FileSystems/ApfsDriverLoader/ApfsDriverLoader.c:953:14: error: use of undeclared identifier 'UNIT8'
            (UNIT8*)EfiFileBuffer + CurPos
             ^
2 errors generated.
make: *** [/Users/mathieu/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/Clover/FileSystems/ApfsDriverLoader/ApfsDriverLoader/OUTPUT/ApfsDriverLoader.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/mathieu/src/udk2018/Build/Clover/RELEASE_XCODE8/X64/Clover/FileSystems/ApfsDriverLoader/ApfsDriverLoader]


build.py...
 : error F002: Failed to build module
	/Users/mathieu/src/udk2018/Clover/FileSystems/ApfsDriverLoader/ApfsDriverLoader.inf [X64, XCODE8, RELEASE]

- Failed -

 

Not UNIT8 but UINT8 like in rev 4996.

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 kushwavez
      Acer Aspire V15 V5-591G - Catalina 10.15
      Original link:
      https://osxlatitude.com/forums/topic/11355-acer-aspire-v-15-v5-591g-catalina-windows-10/
      (Note: mine is 55TU version, but the bootpack will work fine with another versions of 591G, for example: V5-591G-71K2, -764Z, -59PU, etc.)
      Specifications:
      - Motherboard: USOPP_SLS (Skylake-H PCH)
      - BIOS: Insyde Corp. v 1.15
      - CPU: Intel Core i5-6300HQ 2.3 GHz (Skylake)
      - GPU: NVIDIA GeForce GTX 950M 2 GB (Optimus) & Intel HD Graphics 530
      - RAM: SK hynix 4 GB DDR4 (Later I bought + KINGSTON 4 GB) 2133 MHz
      - WiFi + Bluetooth: Qualcomm Atheros QCNFA344A 5 GHz (Later -> Broadcom BRCM94352Z M.2 5 GHz WiFi + 4.0 Bluetooth)
      - Audio: Realtek HD Audio: ALC 255 
      - Ethernet: Realtek RTL8168/8111
      - Card Reader: Realtek USB 2.0 Card Reader (USB2.0-CRW)
      - Webcam: HD Webcam
      - HDD: TOSHIBA MQ01ACF032 320 GB HDD
      - SSD: SPCC M.2 230 GB SSD
      - Display: 1366x768 (15.6", Matte)
      - Battery: 6 cell 56Wh / 5040mAh
      - Connectors: 
      1x SD Card Reader 2x USB 3.0 (1x USB Charging), 1x USB 2.0 1x VGA 1x HDMI 1x 3.5mm microphone/audio combined jack connector 1x Ethernet (Rj-45) - Keyboard & Touchpad: Multi-Touch & Multi-gestures ELAN 501 Touchpad, Backlight Keyboard.
      Working:  
      - Wi-Fi (with BCM94352Z)
      - Bluetooth hand-off (With BCM94352Z)
      - Full Graphics enabled on HD 530: ig-platform-id: 0x191b0000 (HD 530 Mobile)
      - Display: if default colour profile is corrupted (blue is not actual blue but purplish) Use "Rec. ITU-R BT. 709-5" Color Profile (System Pref. -> Displays -> Color)
      - HDMI & VGA Outputs: AppleGraphicsDevicePolicy.kext Clover patch
      - Audio (ALC 255): (Internal Speakers, Internal Microphone, Headphone jack with AppleALC, ALCPlugFix -> layout-id=17)
      - Ethernet Realtek 8168/8111: RealtekRTL8111.kext
      - App Store, Messages, FaceTime, Siri, iCloud (native)
      - Integrated webcam (native)
      - 3.0 USB (native)
      - Touchpad and Keyboard (ELAN501): Fn keys are good, the weird thing is the Brightness key. On my keyboard it's Pause Break:Br-up, Fn+F12:Br-dwn-> To fix this try Karabiner (VoodoPS2Controller.kext), - for gestures try SmartTouchpad drivers
      - Battery info: Install ACPIBatteryManager.kext with Kext Utility or other installer.
      - Sleep Mode
      - SSD with TRIM enabled (to enable trim, open Terminal and write "sudo trimforce enable")
      Not working:
      - Original Wi-Fi (Qualcomm Atheros QCNFA344A):  unsupported, you need switch to BCM94352Z or just use a mini usb wifi dongle.
      - NVIDIA GeForce GTX 950M: Optimus not supported.
      - Card Reader: Unsupported -> Can't really fix because I don't have any SD Card at the moment, maybe can be fixed by adding Prod & Ven IDs to AppleStorageDevices.kext, I never used it anyway. name: "USB2.0-CRW" Prod ID: "0x0129" Ven ID: "0x0bda  (Realtek Semiconductor Corp.)"
      For Wi-Fi:
      - 1st method: You can choose an external USB wifi dongle (I used TP-Link Archer T1U (5GHz support), TP-Link has official macOS drivers, you just need to install it
      - 2nd and I think the best method: Replace your M.2 Qualcomm Card with a compatible BCM94352Z card (you will have hand-off Bluetooth too), just install the kexts (enabled with BrcmFirmwareRepo.kext, BrcmPatchRAM2.kext, FakePCIID.kext, FakePCIID_Broadcom_WiFi.kext, they're all in my attached zip). You could buy this card from ebay, aliexpress, or amazon
       
      Issues:
      - None
      BIOS Settings:
      - BIOS version 1.15 (irrelevant)
      - Secure Boot: Disabled
      - Touchpad: Advanced
      - Boot mode: UEFI
      Getting ready for Installation:
      - Download the Catalina install zip (bootpack & postinstall): acer_aspire_V591G-55TU_cata.zip
      Installation:
      - Create an installer with any method you know (- Mac: createinstallmedia - Windows: Transmac, Vmware, Win32diskimager)
      - Copy my Clover folder to the USB's EFI folder
      - Boot with the Installer USB
      - If you stuck in boot, reboot and in the Clover bootloader select "config_debug.cfg" -> you'll have more informations about the freeze
       
      Please open the README.rtf in my install zip for more informations about the USB Installer & Post installation!
      For any system kext installation\modification you need to boot with config_debug.plist (or disable SIP manually)
      Also on Catalina the System folder is read-only, so you need to remount in rw. 
      If you have a single RAM and getting panic at boot, then you need to edit the "config.plist" with these (SMBIOS->after "Version 1.0"):
      ->Edit "Frequency" and "Size" to match your RAM values
      <key>Version</key> <string>1.0</string> <key>Memory</key> <dict> <key>Channels</key> <integer>1</integer> <key>SlotCount</key> <integer>1</integer> <key>Modules</key> <array> <dict> <key>Slot</key> <integer>0</integer> <key>Size</key> <integer>8192</integer> <key>Frequency</key> <integer>2133</integer> <key>Type</key> <string>DDR4</string> </dict> </array> </dict> </dict>  
      PowerManagement  fix:
      Set HWPEnable=YES in Clover (already set), CPUFloor to "700", Frequency to "2300" and "3200"(Normal and Turbo, if you have i7-6700HQ version then it should be "2600", "3500") and "FrequencyVectors" from "0x0d000000" to "0x07000000" in "S/L/E/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources/Mac-A5C67F76ED83108C.plist", MSR _xcpm_idle Patch to KernelToPatch in Clover (If you have High Sierra, change "MatchOS" to 10.13):

      <key>KernelToPatch</key> <array> <dict> <key>Comment</key> <string>MSR 0xE2 _xcpm_idle instant reboot(c) Pike R. Alpha</string> <key>Disabled</key> <false/> <key>Find</key> <data> ILniAAAADzA= </data> <key>MatchOS</key> <string>10.14</string> <key>Replace</key> <data> ILniAAAAkJA= </data> </dict> </array> Reboot, and it's 800MHz in idle state, same on Windows.
       

      Elan SmartTouchpad
      I only use scrolling, one-, double- & tripletap
      If you want to try other gestures go to this link for more informations, options (v4.6.5) ->  DETAILS ABOUT THE SMART TOUCHPAD DRIVER FEATURES
      Fn Brightness keys not working with this, tried several things without success. With VoodoPS2Controller it's working, but you'll have no gestures (neither scrolling).
       
       
      Before updating to a new version of Catalina please update kexts (and clover if necessary) to newer versions to avoid kernel panics.
      Generate a serial number with Clover Configurator.app (open up your config.plist with CC then -> SMBIOS -> Serial Number -> Generate New)
       
      Catalina & Windows 10 Dual-Boot:
      Dual-boot clean install (on one drive), UEFI Only:
       
       Boot into your Mac installer, Create 2 partitions in GUID table (1 for Win (I used FAT32 but I think it doesn't matter what you choose), 1 for Mac),   Install Mac, boot with your USB, mount your EFI partition (use terminal or an EFI mounter app), create an EFI folder (if there is no folder), copy the CLOVER folder I attached to the EFI folder, restart,  Boot into your Win installer, Format the partition you created for Win, install.   Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       5.  You're done! It will booting into Clover when you start the system, and you can select Win or Mac (or another OS if installed on a 3rd partition).
       
      Dual-boot with Windows installed first (on one drive), UEFI Only:
      If you already have Windows and you don't want to lose all your data there is a hope:
      I created a video from this restore method: [Hackintosh] Dual-Boot High Sierra & Windows - when Windows already installed - no data waste - UEFI
      You need bootable Mac Installer and a full system restore image (link is in my video's description).
      (You may see errors if your EFI partition is not 200 MB)
       Boot into your Windows, resize your partition or create one for Mac.  Boot into your Mac installer and in Disk Utility format the partition you created.  Restore from image: select your full system restore image.  When it's finished restoring you just need to restart, then boot to the system with your usb.  When you successfully booted to Mac desktop, mount your EFI partition (use terminal or an EFI mounter app), open EFI, you will see there is a Microsoft folder already (don't touch that!). Copy my CLOVER folder to the EFI folder then Restart.  Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       7.  You're done! You can select your old Windows and your new macOS!
      (Only tried with Windows 8/8.1/10. I don't know Windows 7,etc.)
       
      IF YOU GETTING ERRORS DURING MAC RESTORE:
      - Make sure you have partitions in GPT
      - Windows using 100 MB EFI and will annoy the Mac restore. Don't worry, just ignore the errors.
       
      IF YOU GETTING ERRORS DURING WINDOWS INSTALLATION (could not be formatted, etc):
      - Make sure you have GPT partitions, and GPT (UEFI) installer, also disconnect all external storage drives (except the installer USB)
       
      IF YOU USED RESTORE METHOD THEN CAN'T MOUNT YOUR EFI PARTITION (No EFI partition found):
      - It's because your EFI is not 200 MB or not an "Apple" original EFI,  but do not worry, try another EFI mounter, or mount from terminal (I used EFI mounter v3: Getting errors, but you can mount and use without problem)
      - You also could "mount" the EFI from Windows:
      1st method: open cmd in administrator mode and type:
      diskpart list vol (Now select the "System" volume,(FAT 32) For example I select 4) sel vol 4 list part (Select System type partition, for example 2) sel part 2 assign letter=b (This will "mount" your EFI partition) Open Explorer++ or TotalCommander in administrator mode to manage EFI remove letter=b (This will "unmount" your EFI) 2nd method: open cmd in administrator mode and type:
      mountvol b: /s (This will mount your EFI) Open Explorer++ or TotalCommander in administrator mode to manage EFI mountvol b: /d (This will unmount your EFI) Thanks to all OSXLatitude members for helping me out! (Jake Lo, Hervé, Bronxteck, black.dragon74)!
      Notes:
      2019.10.09: Installed macOS Catalina 10.15 -> Updated Clover, kexts & config.plist -> no problem so far
      2019.08.18: Updated to 10.14.6 -> no problem when/after installing
      2019.06.01: Updated to 10.14.5 -> no problem when/after installing
      2019.04.25: Optimized touchpad scrolling -> updated install files
      2019.03.30: Fixed USB 3.0 ports, fixed Bluetooth crashes after sleep -> updated bootpack
      2019.03.28: Updated to 10.14.4. Unexpected crashes while updating to 10.14.4 -> fixed by updating Clover to the latest (v4910) version. Bluetooth crashes appeared -> fixed by downgraded Brcm*.kexts. Updated bootpack.
      2019.02.24: Bluetooth crashes after sleep -> fixed, updated bootpack. 
      2019.02.22: Updated to 10.14.3. Fixed HDMI Audio by installing "FakePCIID_Intel_HDMI_Audio.kext" -> fixed freezing during boot. Fixed brightness levels by installing "AppleBacklightFixup.kext". Also updated bootpack & postinstall zip down in attachments.
      2019.01.21: Removed FakeSMC.kext, SMCHelper-64.efi, replaced by VirtualSMC.kext, VirtualSMC.efi because I got random freezes when booting system (kextd stall[0], (120s): 'AppleACPICPU' -> CPU is at 100%, fans are spinning fast), also updated bootpack in the attachments "acer_aspire_v591g-55tu_clover.zip" -> Freeze continued, brought back FakeSMC, deleted VirtualSMC (caused BT crashes).
      2019.01.18: HDMI Audio is fixed, I didn't do anything HDMI Audio is not fixed, sometimes it worked but most likely not. (no idea why)
      2018.12.09: Updated to 10.14.2 -> did without any complication
      2018.11.28: Fixed combo-jack garbage sound output by installing ALCPlugFix and CodecCommander.kext
      2018.11.01: Updated to 10.14.1 -> HDMI & VGA ports are gone again. -> Fixed by "AppleIntelSKLGraphicsFramebuffer.kext" rollback from 10.14.
      2018.09.28: Updated to Mojave 10.14 -> Fixed HDMI & VGA Outputs by adding "AppleGraphicsDevicePolicy.kext" patches to config.plist, HDMI audio not working
    • 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---
      https://olarila.com/files/Clover.Folder/EFI CLOVER Z390 DESIGNARE.zip
      *Use this folder with FULL DSDT PATCHED
       
      ---OPENCORE FOLDER---
      https://olarila.com/forum/download/file.php?id=24376
      *Use this folder with FULL DSDT PATCHED
       
       
      ---Extract one Full dump for DSDT edits, post files---
       
      RunMe.app
       
       
       
      ---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 e97
      HackPro X99 System
      Until Apple blesses us with the MacPro7,1 – this is for those that require tools to do their work.
      An appropriate bicycle for the mind.
       
       

       

       

       
      Specs:
       
      CPU: Intel Xeon E5-2678 v3 (12 core, 2.5 GHz / 3.3 GHz Boost)
      Motherboard: SZMZ X99-8D3
      RAM: 16GB DDR3-14900R 1866Mhz ECC RDIMM modules
      GPU: Radeon RX Vega 64 8GB
      Storage: Phison E12 m.2 NVMe PCI-E 3.0 x4 SSD
      Water blocks: BARROW CPU + GPU
      Radiator: 360mm x 25mm slim
      Pump: DDC
       
      Case dimensions: 431 mm x 342 mm x 177 mm
       
       
       
      XCPM OFF
       

       
      XCPM ON
       

       
      OpenCL
       

       
       
       
      iMacPro1,1
       

       
       

       
      OpenCL
       

       
       
      NVMe
       

       
       
      Win 10 x64 v1809
       
      AIDA64 - Cache & Memory
       

       
       
      EFI-Clover-X99.zip
       
       
       
       
       
       
      Anyone else I forgot
       
       
×