Jump to content
tonyx86

Mojave on Dell Latitude E6410 With Working Sleep

168 posts in this topic

Recommended Posts

Advertisement

@tonyx86 Do you will update to Catalina directly from settings (if its possible) or do a clean install?

31 minutes ago, tonyx86 said:

Look what popped up on my HackBookPro6,2!

Screen Shot 2019-10-08 at 1.29.17 PM.png

I was trying to download and it have some trouble with my network. So I seek the patched dosdude version.

Look at: http://dosdude1.com/catalina/

Share this post


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

@tonyx86 Do you will update to Catalina directly from settings (if its possible) or do a clean install?

 I haven't updated to the next major release of macOS until it is required to upgrade XCode, so it may be a while before i try Catalina.  When I do try, I will do the following:

  1. Perform a full system backup (Carbon Copy)
  2. Attemp an upgrade from Mojave via System Preferences > Software Update and then apply dosdude patches using dosdude's post install utility
  3. If that doesn't work, I'll attempt to update Mojave by using the Catalina USB Installer (patched with Dosdude patcher) and then apply dosdude patches using the post install utility.
  4. If that doesn't work, I'll perform a clean install of Catalina (using the Catalina USB Installer created with Dosdude patcher) and apply dosdude post install patches

Share this post


Link to post
Share on other sites
18 hours ago, tonyx86 said:

 I haven't updated to the next major release of macOS until it is required to upgrade XCode, so it may be a while before i try Catalina.  When I do try, I will do the following:

  1. Perform a full system backup (Carbon Copy)
  2. Attemp an upgrade from Mojave via System Preferences > Software Update and then apply dosdude patches using dosdude's post install utility
  3. If that doesn't work, I'll attempt to update Mojave by using the Catalina USB Installer (patched with Dosdude patcher) and then apply dosdude patches using the post install utility.
  4. If that doesn't work, I'll perform a clean install of Catalina (using the Catalina USB Installer created with Dosdude patcher) and apply dosdude post install patches

Only to be an example, at my Dell Optiplex 780 with Mojave running absolutely normal, I am tried the 4th step you spoke above but the first phase (about 10 minutes) pass but it reboots without any question and continues the second phase (estimating about 32 minutes) and crash/reboot. I will continue testing on this old Core2Quad after mess with my Latitude to see the many errors can be possible to solve.

Share this post


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

Only to be an example, at my Dell Optiplex 780 with Mojave running absolutely normal, I am tried the 4th step you spoke above but the first phase (about 10 minutes) pass but it reboots without any question and continues the second phase (estimating about 32 minutes) and crash/reboot. I will continue testing on this old Core2Quad after mess with my Latitude to see the many errors can be possible to solve.

 

I admire you for your courage!  I am not so bold and allow the process and updates to mature for a while before trying.  There will be A LOT of revisions and lessons learned - that's about the only thing of which I can be sure.  When the process and updates are mature, I suspect that the Catalina install process will be exactly the same as the Mojave installation process described in this thread (same DSDT, same SSDTs, same kexts).

 

EDIT: I might have a suggestion for you - before that final reboot, use dosdude's Catalina patcher post install utility to apply the patches.  If they don't work and you experience crashes (again), re-run the post install utility, re-apply the patches and choose the "Force rebuild cache" option.

Edited by tonyx86

Share this post


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

 

I admire you for your courage!  I am not so bold and allow the process and updates to mature for a while before trying.  There will be A LOT of revisions and lessons learned - that's about the only thing of which I can be sure.  When the process and updates are mature, I suspect that the Catalina install process will be exactly the same as the Mojave installation process described in this thread (same DSDT, same SSDTs, same kexts).

 

EDIT: I might have a suggestion for you - before that final reboot, use dosdude's Catalina patcher post install utility to apply the patches.  If they don't work and you experience crashes (again), re-run the post install utility, re-apply the patches and choose the "Force rebuild cache" option.

 

Finaly after using that flags in Clover it could start the second phase and finished install.

Success with basic kexts. Intellmausi is not working for my desktop so using the old AppleIntelE1000e.kext (v. 3.3.6 from 18/10/2017) my network is live.

Sorry for this offtopic post but I had to share my success with someone...

All Apple ID services are online nicely. :D

photo4967557091950700617.jpg

photo4967975743887878233.jpg

Share this post


Link to post
Share on other sites

Only for fun, this Catalina USB 2.0 disk boots on my Latitude E6510 (with DSDT and kexts using this guide by @tonyx86), after installing it on another Dell desktop.

The USB was the only way cause I dont have any spare SSD... but loads (slowly obviously).

Cheers... and long life to E6000 series.

catalina usb.jpeg

Share this post


Link to post
Share on other sites

Attached is an updated DSDT for the Latitude E6410.  Details are as follows.

 

I have noticed that the Latitude E6410 screen may briefly go "white" on system restart.  The white screen is not really a problem, but I believe it indicates a flaw in the way I applied the discrete graphics _OFF() logic.  I suspect this white screen is because I was calling the discrete graphics _OFF() function at the beginning of _PTS() (before other restart functions have completed).  I moved _OFF() to the end of _PTS() ( note I also had to move _ON() to the end of _WAK() as described earlier in this thread).  I believe that this change has fixed the white-screen issue.  This change does not affect shutdown (and I've never observed a white screen during shutdown), because  _OFF() is not called in _PTS() when shutting down.

 

EDIT: This fix appears to have resolved another issue that I had observed: Occasionally, when I would restart from Mojave and boot High Sierra, I would experience a white screen.  This would resolve itself, but it always made me wonder.  I suspect that the incorrect placement of _OFF() in _PTS() left the discrete graphics in a bad state from the previous session.  With this fix, I don't experience the white screen when switching from Mojave to High Sierra.

 

 

DSDT.zip

Edited by tonyx86

Share this post


Link to post
Share on other sites

I have added the following "known issue" to Post #1 of this thread:  After applying Mojave updates, HWMonitor may not display discrete graphics attributes.  On systems with multiple displays, a second (or third) display may not be active after applying the Mojave update.  The solution to this is to run "sudo kextcache -i /" (in a terminal window) and reboot.  This will usually fix the issue.  If the issue is not fixed, run DosDude's Post Install Utility, apply the Legacy Graphics Patch, reboot and then run "sudo kextcache -i /" if necessary.

Share this post


Link to post
Share on other sites

The necessary tricks necessary to obtain support and OpenGL-only graphics acceleration on unsupported nVidia Tesla GPUs (and others) differ between individual versions of Mojave. What worked up to 10.14.3 was no longer sufficient in 10.14.4 which requires additional replacement of frameworks and same again in 10.14.5/.6.

 

So, what's essential after each Mojave update is to apply the necessary and appropriate replacements, especially the frameworks ones. Of course, rebuilding cache should systematically be performed too.

 

Plenty of threads on the matter on this forum and others (here for instance) and tools also exist that apply the necessary mods according to Mojave's target version.

Edited by Hervé

Share this post


Link to post
Share on other sites
On 11/10/2019 at 12:12 PM, Hervé said:

The necessary tricks necessary to obtain support and OpenGL-only graphics acceleration on unsupported nVidia Tesla GPUs (and others) differ between individual versions of Mojave. What worked up to 10.14.3 was no longer sufficient in 10.14.4 which requires additional replacement of frameworks and same again in 10.14.5/.6.

 

Thanks, @Hervé - Good to know.  It makes me appreciate even more just how much work went into the DosDude patcher.  The patcher greatly simplifies all of the "behind-the-scenes" Mojave changes.  Starting with 10.14.4 (and subsequently 10.14.5 and 10.14.6), applying Mojave patches and security updates to my four systems (Thinkpad T61, Latitude E6410, DIY socket 1156/9800GT and DIY socket 775/8600GT) required no more than a "sudo kextcache -i /" or re-applying DosDude post-install  patch after applying the Mojave update.

Edited by tonyx86

Share this post


Link to post
Share on other sites

I needed the SD Card Reader, so I followed the VoodooSDHC.kext installation instructions here.  I was able to access images on the SD Card, so it does appear that VoodooSDHC.kext works in Mojave.  I added VoodooSDHC.kext to the kext list on Post #1 of this thread.

 

Note that the SD Card Reader must be enabled in BIOS.

 

EDIT: Use the updated DSDT that I attached a couple of posts later in this thread.  This new DSDT resolves a SD Card mounting issue on battery power.

Edited by tonyx86
Added note about updated DSDT

Share this post


Link to post
Share on other sites

Interesting observation - wondering if anyone else has seen this.  I inserted an SD Card while my E6410 was running on battery power.  The SD card did not mount.  I have not seen this when using the SD Card slot on A/C power.

 

I wonder if I screwed something up in the DSDT when I was playing with EJD (trying to figure out the sleep problem).  If anyone else sees this difference in SD Card behavior between A/C and battery, I'll take a look at the DSDT.  Otherwise, it may be just my system / SD Card.

Edited by tonyx86

Share this post


Link to post
Share on other sites

Attached is an updated DSDT for the Latitude E6410.  Details below.

 

While attempting to fix sleep, I had gone down an incorrect path where I changed the EJD (Ejection Dependent Device) configuration for Device (PXSX) (what I now know to be the SD Card slot).  The changes I made did not fix sleep and they broke PXSX.  I experienced SD Card mounting problems when running on battery power.  The attached DSDT restores Device (PXSX) EJD configuration to its original state.  This appears to have resolved the SD Card issues.

DSDT.zip

Share this post


Link to post
Share on other sites

Attached is an updated DSDT for the Latitude E6410.  Details below.

 

When I was experimenting with the discrete graphics _OFF and _ON methods (in _PTS and _WAK methods respectively), I should have made _OFF and _ON conditional on S3 and S4 states only.  The attached DSDT makes sure that _OFF and _ON are only invoked when entering and exiting sleep states S3 and S4.

DSDT.zip

Share this post


Link to post
Share on other sites

I have updated Post #1 of this thread to be consistent with the latest state of my E6410.  The config files attached to Post #1 (in E6410.zip) include the latest from my fully working system.

Share this post


Link to post
Share on other sites

I added my Latitude E6410 BIOS settings to Post #1 of this thread in the section titled "Brief Installation Guide"

Edited by tonyx86

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 FreqFeeder
      Hi there!
      I'm a newbie to the concept of installing a Mac OS on alternative hardware. Please bear with me
      I have a Lenovo Thinkpad x250 with 5th generation i7-5600U CPU, 16GB RAM, and Intel HD Graphics 5500. (I'd be glad to add any additional hardware details if needed)
      My goal is to have a dual boot machine - Mojave and Win 10. I have two separated physical drives.
      I've tried different methods, but none was stable to be operable.
      If anyone of you has the experience with this specific model it will be really great to hear your opinion.

      Thanks!
    • By verdazil
      This is not intended to be a complete and comprehensive installation guide. There are many installation guides on the forum and installing macOS is no different from installing on other desktop builds. Rather, this is supplemental information specific to the my hardware listed below. I hope you find this information useful and this will save you a little time.
       
      Hardware
      MB: Huananzhi X79-ZD3
      CPU: Intel® Xeon E5-2689, 1.2-3.6 GHz
      Chipset: Sandy Bridge-E Q65 (C600/C200)
      Memory: Samsung 4x8 Gb ECC/REG DDR3, 1866 MHz
      Video: Saphire Nitro+ Radeon RX 590
      Monitor: BENQ-BL2711U + LG TV 42LF650V
      SSD + HDD: NVMe M.2 Samsung 970 EVO 250 Gb + HDD Seagate 2 Tb
      WiFi: Fenvi FV-T919 BCM94360CD
      Mac model: MacPro6,1
      MacOS version tested: Mojave 10.14.6 (18G1012)
       
      What works?
      - Video: 4K x 60Hz on BENQ-BL2711U + Full HD x 60Hz on LG TV 42LF650V
      - Sound: audio jack + HDMI audio on both monitors
      - Wi-Fi (out of the box)
      - USB2 && USB3 ports
      - LAN
      - Bluetooth (out of the box)
       
      What does not work?
      - Sleep mode: not tested / I don't need
       
      BIOS Configuration, what's important:
      Bios Version: 4.6.5.4
      Legacy USB Support: [Enabled]
      XHCI Hand-off: [Enabled]
      EHCI Hand-off: [Enabled]
      USB Mass Storage Driver Support: [Enabled]
      Hyper-threading: [Enabled]
      Active Processor Cores: [All]
      Serial Port: [Disabled]
      Intel(R) VT-d : [Disabled]
      Launch CSM: [Enabled]
      Boot option filter: [UEFI only]
      Launch Storage OpROM policy : [UEFI only]
      Launch Video OpROM policy : [UEFI only]
       
      Here is what I used to install and configure the system:
      FakeSMC: make with Clover Builder https://github.com/Dids/clover-builder/releases Audio: https://github.com/vit9696/AppleALC Video: https://github.com/acidanthera/WhateverGreen/releases USB: https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads + PMHeart/DalianSky patches LAN: http://www.insanelymac.com/forum/topic/287161-new-driver-for-realtek-rtl8111/ CPU Power management: https://www.insanelymac.com/forum/topic/324270-sandy-bridge-e-ivy-bridge-e-power-management-1013-appstore-release   Clover configuration:
      Clover version: v2.5k r5088
      You can get the configuration file and the necessary kexts from the link at the end of the message
      Note: you must insert your own SeralNumber && MLB && ROM && SmUUID in the config.plist file.
       
      How to use
      To make a bootable flash drive, you can use my EFI directory (link at the end of the message). Tested for Mojave 10.14.6 installation.
      https://drive.google.com/file/d/1tjbwuUWg_PlQCVt5PTRFG6HsNby_BcgN
    • By valueimagery
      Apologies ahead of time if this is in the wrong thread (please move to appropriate thread if necessary) as it applies to pre-installation and post-installation, Mojave and Catalina, motherboards, user preferences, but it's all related and I just had to get all this written down since it's all resolved...
       
      The issues:
      MOJAVE 10.14.6 2019 SECURITY UPDATE
      CATALINA 10.15.1 INSTALLER USB
      POST Mother Board UPDATE ISSUES
      UEFI Bootloader disappearing from BIOS boot menu/setup
      MAPS NOT WORKING/ CORRUPT USER/LIBRARY/CACHE
      GPT HEADER CORRUPTION AT BOOT
       
      This is my system which has worked flawlessly ever since 10.14.1 and automatic updates within the OS.
      10.14.6 iMac 18,3
      ASUS Rog Maximux X Code Bios v 2023
      Sapphire Nitro+ RX 580 Special Edition
      1 NVME System Drive, 1 x 1TB NVME Scratch Disk,  4 Internal 8TB HDD in raid 1+0, 4 x 3TB in a raid 5 setup with enclosure, 1 Backup System SSD, 1 2TB Time machine HDD (get to why I’m listing the drives later)
       
      Instead of making different posts for all of these issues that I’ve spent that past two weeks trying to solve (I almost gave up) I thought for anyone else out there experiencing one or any of the above issues you might find a solution in this thread.
       
      First let me say thanks to all the people out there in the various hackintosh communities (hackintoshers, tonymac, insanelymac, olarila, reddit) I researched every single one to find solutions for all these issues.
       
      Second, invest in Carbon Copy Cloner and make sure you make constant backups of your system drives.  Otherwise there would be no way to troubleshoot.
       
      So this all stemmed from not being able to update to Mojave 10.14.6 2019 Security Update released in November 2019.  
      My original post:
      Link removed:
      https://www.reddit.com/r/hackintosh/comments/e2naku/cant_update_mojave_to_security_update_2019001/
       
      There were plenty of different errors through troubleshooting:
      Kextdstall[1] (240s) ‘AppleACPICPU’
      or
      considerRebuildOfPrelinkedKernel com.apple.nke.webcontentfilter trigger rebuild
      or
      com.apple.xpc.launchd.domain.system
      <error>: Could not read path: path = /Library/LaunchDaemons, error=2: No suchfile or directory
      And
      IOG flags 0x3(0x51)

      IOConsoleUsers” gIOScreenLockState 3, hs 0, bs0, now 0, sm 0x0
      (The last two, still exist, but don’t stall/severely halt boot, and I’m not really sure if it’s an issue that needs to be addressed as I believe I’ve used the correct format of Device Properties to inject my framebuffer as a headless UHD 630 with 0x3E980003)
       
      Then once I managed to get past some of the installer stalls I always ended at “Installer resources were not found” prompting a restart and continuous loop cycle of no successful install.
       
      Then I tried making a bootable Catalina USB and couldn’t even install a fresh copy of 10.15.1 on a separate SSD.  Again getting errors in verbose mode that would stall and go no further.
       
      Then after cloning, and failing, and cloning and failing, changing bios settings, at some points my UEFI bootloader would completely disappear for my Samsung NVME 970 pro system drive.
       
      Was really getting frustrated, but was determined to fix it.  And here they are one by one in the order I Fixed them:
       
      Clover UEFI Bootloader Disapepared from Boot Menu
      So first I figured out what was going on with the UEFI bootloader disappearing.  I tried complete wipes of the APFS drive, Reinstalling Clover on the EFI partition.  Nothing.  Finally Found the solution here thanks to @chibabah
      Link removed:
      Tips:
      1)    If you have lots of connected drives use the Page Up and Page Down key to scroll through results of bcfg boot dump
      2)    Use Disk Utility or Terminal before hand to verify the exact UUID of your EFI system drive that has disappeared.
       
       
      Post Motherboard Update
      Now this seems to apply to a lot of people in the community who have updated and unknowingly couldn’t boot their system, or in my case, couldn’t update the current OS to the latest version.  This seemed to apply to my ASUS Maximus X Code v 2203.
      Thanks @mattystonnie for your ACPI patch found here:
      Link removed:
       
      Can’t Install fresh version of Catalina 10.15.1
      So after almost giving up on not getting the latest Mojave Security update, I wondered if Catalina would have the same issues.  Well it had different issues.
      Stall - Virtual IOReturn ionvmecontroller
      AppleACPICPU stalling
      Requiring EC device
      So I found this reddit thread thanks @dracoflar:
      https://www.reddit.com/r/hackintosh/comments/den28t/whats_new_in_macos_catalina/
       
      And applied the SSDTTime.command create by @corpnewt @noone @rehabman available here:
      https://github.com/corpnewt/SSDTTime
       
      The SSDT-EC.aml file it created from my DSDT.aml was the FINAL KEY in allowing the Catalina Installer to complete.
       
      Tips:
      1)    If you haven’t already created a SSDT before, for example a custom USB SSDT, it is placed in your EFI/Clover/ACPI/Patched/
      2)    In your config.plist under ACPI Check “AutoMerge” so that it is true.  This will automatically load any custom SSDT files from your patched folder.
       
      Apple Maps not loading
      This had been something that I had issues with before, more so with location services not working.  However, after several clones, and a succesful Catalina Install/User Migration, location services was fine, but Maps was a blank grey grid, couldn’t find an address, get directions, load satellite image.   Ended up being a corrupt User Library since other System Users had no issues using the application Maps.
      To fix this I used the following resources:
      https://appletoolbox.com/fix-corrupt-user-accounts-macos/
      1)
      Quit Maps
      Give Terminal Full Disk Access and the type:
      diskutil resetUserPermissions / `id -u`
       
      2)
      Deleting The Entire User Library Cache folder
      ~/Library/Caches
       
      3)
      Delete folder ~/Library/Containers/com.apple.Maps/
       
      4)
      Restart Mac.  All these caches and temporary folders will repopulated themselves and Maps should resume working.  
       
      Installing Mojave 10.14.6 2019 Security Update
      This by far is the craziest of them all.  Whether the above things I implemented to my EFI or config.plist actually played a part or not in it finally working I guess I’ll never know.  But it is finally solved.  Simply by unplugging all drives.  Appears to be an issue with real macs too:
      https://bartechtv.com/macos-could-not-be-installed-on-your-computer-error-when-installing-mojave-on-hackintosh/
      Link removed:
      Didn’t have to go the terminal route as some did in the tonymac thread above.
       
      So since I have A LOT of drives I simply turned off my external enclosure, physically unplugged by 2nd NVME scratch drive, and disabled the SATA connectors in the BIOS.
       
      Low and behold after two restarts the Security update completed without a hitch or stall.
       
      After install I re-enabled/ connected/turned on all my drives, an no issues.  
       
      This must be a Mojave issue as I didn’t need to do this when installing Catalina from a USB installer.
       
      GPT header corruption has been detected
      And lastly for anyone out there with an ASUS Maximus Motherboard that has updated to the latest BIOS.  There seems to be an issue with external drives plugged into the PC (mine is in the back USB C port)  During boot the PC can’t POST and forces user into setup.
       
      I know there is nothing wrong with the GPT partition as I’ve run multiple tests in windows and mac.  And it’s a known issue with other ASUS motherboard users:
      https://rog.asus.com/forum/showthread.php?114955-GPT-header-corruption
       
      Temporary Solution:
      Until a BIOS update addresses this, go to your BIOS settings
      BOOT\Boot Configuration
      And change the Boot Sector (MBR/GPT) Recovery Policy to “Auto Recovery”
       
    • By valueimagery
      Hello,

      Anyone else having issues with the latest security update 2019-001 10.14.6 for Mojave?

      Have never had issues updating since 10.14.2 in the past. But this once gets stuck on these last 4 lines:
      "
      Adding AGDP mode validate property
      iMac.local com.apple.xpc.launchd[1] (org.ntp.sntp.188) <Warning>: Servuce exited with abnormal code: 1
      considerRebuildOfPrelinkedKernel com.apple.nke.webcontentfilter trigger reguild
      Forcing CS_RUNTIME for entitlement: com.apple.rootless.install iMac.Local com.apple.xpc.launchd[1] (com.apple.displaypolicyd.200) <Warning>: Service exited with abnormal code: 1
      "

      The only way to boot is to force shutdown and overide boot from the system volume and bypass the Mac OS Install volume.

      Doing a bit of research from similar issues with users and security updates most boot problems are caused/resolved by fixing:

      Location of Kexts (virtualsmc in Clover's "/kexts/Other/", latest kexts installed with ##### in L/E/ with cache updated by Kext utility)
      The Injection of Kexts (i've tried both detect and inject = yes)
      Mismatched Kext (fakesmc + virtual smc both in use, which they are not)
      A bad config.plist (works booting the normal system voluem, i've attached)
      A graphic injector issue (currently using iMac18,3 + RX580 with the UHD630 in a headless state)
      Multiple Drivers Folder - The old clover /driversuefi64/ folder present and conflicting with the latest /drivers/uefi/ folder (only /drivers/uefi/ present)

      The only thing that is different from this update than previous updates is that I transitioned to VirtualSMC from previously using FAKESMC/ FAKESMCsensors kexts with previous Mojave releases.

      I uninstalled the FAKESMC and all the sensors kexts using terminal and the following command and can confirm they are not present in the Clover "other folder" or the /L/E/ folder.
      sudo rm -rf /Library/Extensions/".....".kext

      After transitiong to VirtualSMC I did read with the readme that the VirtualSmc.efi should be placed in the /drivers/UEFI/ folder in clover. So I have added that to the EFI/CLOVER/DRIVERS/UEFI/ folder manually. Can anyone confirm if this is necessary?

      I've attached my config.plist file and screenshots of the verbose readout stalling as well.

      Any guidance would be great!


      KEXTS I'VE INSTALLED IN /L/E/:
      WhateverGreen.kext
      VirtualSMC.kext
      USBInjectAll.kext
      SMCSuperIO.kext
      SMCProcessor.kext
      Lilu.kext
      IntelMausiEthernet.kext
      BrcmPatchRAM3.kext
      BrcmFirmwareRepo.kext
      BrcmBluetoothInjector.kext
      AppleALC.kext
      AirportBrcmFixup.kext
      configNOSN.plist


    • By ezyrdr
      hallo hallo!
      I've been here on since snow leopard days, but still, im less than a rookie when it comes to hackintoshing! im just format it, copy it, install it dude-like! ahajajahaa sorry but I've been gettin this arb_buffer not present in my whatevergreen or don't know what OpenGL driver...steam games like Dying Light aren't playable since mojave 14.2 (no video, black screen) and several other opengl apps wont behave correctly at all...soo i only got you people to givme any idea of what am i doin wrong here with my installation, cause i got latest whatevergreen, as you could see from the capture im sending ... maybe i should go for a better video card?? i was thinkin buying a RX 590 8GB from Sapphire would kinda do de trick...but if a got a prob with my installation, most likely not uh!? ahaaja well thats from me for now, hope you guys are havin it this holidays with fam & loved ones, and are safe & witta rockin piece of hackintosh to play around with catalina, which is pretty cool system for me right now!
      HAPPY HOLIDAYS EVERYONE & BE SAFE!!!    ~_^

      ~edit~
      maybe i misconfigured ATI enabling in CloverEditor over the config file?!
×