Jump to content
Ricky Romero

60Hz 4K on Mavericks with GTX 760? [UPDATE: 10.9.3 works [UPDATED UPDATE: maybe]]

171 posts in this topic

Recommended Posts

Sorry, it's very confusing, the circumstances to get the 60Hz are really weird.

 

For some reason I get 60Hz if I boot from a USB PenDrive with the Default Clover EFI (that plist does not have a SMBIOS and it defaults to iMac 12,2) and instead of booting the installation (on the PenDrive) I select my Mavericks SSD already installed on the Clover Screen.

 

Now, on the the Mavericks SSD already installed I also have Clovers with its own EFI and plist, that plist is MacPro6,1. I am not sure if it is a coincidence but with iMac 14,2 it did not work.

 

Do you guys now if that makes any sense? Would a second EFI/plist do something? I cannot just copy the USB EFI to Disk, that does not work, I need to run first the USB and then the SSD.

Using your EFI (with nvidia injection), all I get is black screen ...... your experience is pretty weird  :yes:

Share this post


Link to post
Share on other sites
Advertisement

UP2414Q  still run at 30hz under Yosemite with iMac14,2 ......

I get black screen if I set SMBIOS to be MacPro6,1

 

Clover's default nvidia injection gives me a corrupted screen ......

I have a feeling that if I can get it working with MacPro6,1, I can get 60hz working.

Share this post


Link to post
Share on other sites

Yes, before I returned my legit 2013 Mac Pro, I was running 10.9.3 with full 60Hz and a Dell UP2414Q.  Support for the Dell was part of the excitement around 10.9.3.  I emailed Nvidia about this and they gave me the run around because I am using the Web Drivers for a Titan Black which isn't on their supported cards list.  It's def driver related tho.

 

Currently, the Dell can run at 60Hz on Hackintosh with AMD cards (Tahiti XT etc... R9 280X, HD 7970 etc..) and a 6,1 SMBios.  No Nvidia cards can currently run the UP2414Q at 60Hz. 

Sadly, I cannot run at 60hz with my AMD R9 280x or 290x and MacPro6,1 SMBIOS ......

 

Here is the screenshot under Yosemite DP1, with 290x and MacPro6,1

post-1106180-0-95429200-1402731406_thumb.png

Share this post


Link to post
Share on other sites

Is that ok that I don't have any icons in display settings (smaller text, bigger text), just the resolution numbers, and nothing about Hi-DPI like on screenshots here? My display still shows at 5120 x 2880 so I'm assuming it works correctly. using GTX 760 and samsung U28D590.

Share this post


Link to post
Share on other sites

Is that ok that I don't have any icons in display settings (smaller text, bigger text), just the resolution numbers, and nothing about Hi-DPI like on screenshots here? My display still shows at 5120 x 2880 so I'm assuming it works correctly. using GTX 760 and samsung U28D590.

What is your Product name in your smbios?

Share this post


Link to post
Share on other sites

Anyone know if the 31.5" Dell UP3214Q works with a Hack?

 

The only thing I found so far is that it does work on a Mac Pro (late 2013) according to this video, and in its comments the poster mentions that it runs at 60 Hz (two of them at least, not the 3rd). Also it is mentioned in Apples 4K support document. So I'm at least somewhat hopeful.

 

On the other hand, the 24" Dell runs fine [1] on a Mac Pro (late 2013, at work, with ASUS PQ321Q as main display), but was a bit troublesome on my Hack (at home, where I'm currently running an ASUS 28" PB287Q).

 

[1] Except that the Mac Pro can't run it in portrait mode, where the Hack could.

Share this post


Link to post
Share on other sites

Got a 31.5" Dell UP3214Q as main display on my Hack now. Unsurprisingly, it has the same problems that the 24" had:

  • Using MacPro6,1 SMBios with DisplayPort 1.2 setting off it runs at 30 Hz, including proper scaling options
  • Using MacPro6,1 SMBios with DisplayPort 1.2 setting on it stays black, with its power light flickering and menu unavailable because it can't detect any input source
  • Using iMac14,2 SMBios with DisplayPort 1.2 setting on or off (does not matter) it runs at 30 Hz, including proper scaling options.

That's using OS X 10.9.3 and Chameleon v2.2 r2377. I'll try more stuff later, such as 10.9.4 upgrade.

Share this post


Link to post
Share on other sites

Got a 31.5" Dell UP3214Q as main display on my Hack now. Unsurprisingly, it has the same problems that the 24" had:

  • Using MacPro6,1 SMBios with DisplayPort 1.2 setting off it runs at 30 Hz, including proper scaling options
  • Using MacPro6,1 SMBios with DisplayPort 1.2 setting on it stays black, with its power light flickering and menu unavailable because it can't detect any input source
  • Using iMac14,2 SMBios with DisplayPort 1.2 setting on or off (does not matter) it runs at 30 Hz, including proper scaling options.

That's using OS X 10.9.3 and Chameleon v2.2 r2377. I'll try more stuff later, such as 10.9.4 upgrade.

Could you test retina macbook pro SMBios?

Share this post


Link to post
Share on other sites

Could you test retina macbook pro SMBios?

 

Yes, that's also on the TODO list, as well as that Clover USB Stick with default SMBIOS combined with MacPro6,1 SMBios on the internal drive hybrid method that worked for somebody else.

Share this post


Link to post
Share on other sites

Still no luck with the UP3214Q:

  • With MacPro3,1 SMBios: Same behavior as with iMac14,2
  • With MacPro5,1 SMBios: Kernel panic during boot process
  • With MacBookPro11,3 SMBios: Same behavior as with iMac14,2
  • Clover USB stick: while I could select my internal boot drive (with MacPro6,1 SMBios on it) it would not boot - both displays stayed black so I shut down after a while

​I wonder if there's a firmware update available for the display that would help.

Share this post


Link to post
Share on other sites

Still no luck with the UP3214Q:

  • With MacPro3,1 SMBios: Same behavior as with iMac14,2
  • With MacPro5,1 SMBios: Kernel panic during boot process
  • With MacBookPro11,3 SMBios: Same behavior as with iMac14,2
  • Clover USB stick: while I could select my internal boot drive (with MacPro6,1 SMBios on it) it would not boot - both displays stayed black so I shut down after a while

​I wonder if there's a firmware update available for the display that would help.

Could just wait a bit and buy a monitor that doesn't use MST. My samsung U28D590 is fine, soon probably there will be 32-inch screens that don't use MST.

 

Update: Never mind, didn't knew you already had 4 monitors with 3 of them IPS)

Share this post


Link to post
Share on other sites

Yeah, and MST isn't necessarily the culprit, as my 31.5" ASUS works just fine with it.

 

Also, the 24" Dell worked perfectly with some of the earlier 10.9.3 betas, and Windows 8.1, and on a real MacPro6,1 with 10.9.3/10.9.4. :-/

 

BTW the 31.5" Dell replaced the 28" ASUS (sold it to a friend) so I'm back to 3x IPS, all of them with MST.

Share this post


Link to post
Share on other sites

Got a 31.5" Dell UP3214Q as main display on my Hack now. Unsurprisingly, it has the same problems that the 24" had:

  • Using MacPro6,1 SMBios with DisplayPort 1.2 setting off it runs at 30 Hz, including proper scaling options
  • Using MacPro6,1 SMBios with DisplayPort 1.2 setting on it stays black, with its power light flickering and menu unavailable because it can't detect any input source
  • Using iMac14,2 SMBios with DisplayPort 1.2 setting on or off (does not matter) it runs at 30 Hz, including proper scaling options.

That's using OS X 10.9.3 and Chameleon v2.2 r2377. I'll try more stuff later, such as 10.9.4 upgrade.

A remark for the second point (MacPro6,1 SMBios with DisplayPort 1.2 setting on): if you power-cycle or temporarily change the input on the monitor, then it gets recognized and runs fine in 30Hz mode.

Share this post


Link to post
Share on other sites

Thanks, that's what I'm currently doing (given I still boot into Win 8.1 from time to time and want to avoid switching the DisplayPort 1.2 setting; even though it's far easier to do than on the ASUS :P because of DELLs good on-screen menu and buttons).

 

BTW given it still won't run at 60 Hz I might eventually swap it with the ASUS 31.5", which is currently on a Mac Pro at work.

Share this post


Link to post
Share on other sites

A few weeks ago I pulled the EDID out of that IOReg from the previous page, and it is different from my own up2414q EDID. It may be worth popping that into a display override, I simply haven't had the time or motivation to play with it lately. There are other differences in IOReg as well that may be worth reproducing in your own DSDT.

Share this post


Link to post
Share on other sites

Updating to 10.9.4 didn't help make the UP3214Q work any better either.

 

Also I noticed that when you Option-click the Scaled button in the Displays preference pane to display more resolutions, and also check Show low resolution modes, it does show the Refresh rate popup menu once again. It reads 30.3 Hz when the display stays black, and unfortunately the popup menu is grayed out, so one can't select any other refresh rates.

Share this post


Link to post
Share on other sites

Culled from nVidia's website.

https://developer.nvidia.com/4k-ultra-high-resolution-development

 

 

I think it should answer some of your questions

  Resolutions

The 4K display standard contains two resolutions:

  • 3840*2160: This is the standard resolution supported by TVs and monitors
  • 4096*2160: Projectors will support this slightly wider aspect ratio format
Industry Support for 4K

There are 2 ways of delivering 4K content, HDMI and DisplayPort.

A) HDMI

The current HDMI 1.4 standard only has bandwidth for 4K at 30hz. HDMI 2.0 will add support for 4K at 60Hz. Details should become clearer in late 2013. There are a few TVs on sale today that support 4K @ 30Hz through HDMI.

B) DisplayPort 1.2

DisplayPort can support 4K @ 60Hz using Multi-Stream Transport(MST). The graphics card provides signals for multiple displays but these are multiplexed on a single cable. Computer monitors such as the ASUS PQ321Q 31.5-in 4K 60 Hz Tiled Monitor take input using this format.

NVIDIA GPU support for 4K Resolutions

All GeForce GTX 600 and 700 series GPUs can support 4K resolutions through DisplayPort. The NVIDIA driver automatically detects 4K 60Hz tiled format, so no special user set up is required. In order to power games at this resolution with settings turned up NVIDIA recommends GTX 780 SLI or better.

What consumer 4K displays available today?

A variety of solutions are available today from manufactures like Asus and Sharp. Dell has also recently announced their 4K UltraSharp 32 display with availability in Q4 2013.

4K Development Tips and Tricks 1) Support 4K resolutions natively

The standard 4K UHD display resolution for monitors and televisions is 3840 x 2160 pixels. Projectors supporting the wider 4096 x 2160 pixels will also be available. Your game title should enumerate the available modes (using functions such as EnumDisplaySettings or GetDisplayModeList) and support native rendering to those resolutions.

2) Provide the Highest Resolution Textures

Texture content that is optimized to avoid magnification at 1080p resolution will magnify at 4K, leading to blurry textures when you get up close to surfaces. To maximize the quality at 4K screen resolution, provide the highest texel density you possibly can in your game by using the largest possible texture sizes. For example, for textures where the player can get close enough for 1:1 texel to pixel ratio, 4096 x 4096 textures will provide the highest quality. This is especially important for textures which provide detail, such as albedo textures, normal maps, and displacement maps, but can also be important for procedurally generated textures, such as light maps, which can be generated at higher resolution for display on 4K screens.

3) Enable Anisotropic Filtering

4K screens will resolve additional underlying detail, so maximizing texture detail is key. Using anisotropic filtering will add detail to the image, and be even more noticeable at 4K resolutions.

4) Optimize for SLI

4K UHD has four times the pixels of 1080p – which means four times the pixel workload. Scaling with SLI multi-GPU setups will be even more important to ensure the smoothest experience at 4K resolutions. Be careful to avoid the usual SLI pitfalls, such as interframe dependencies, CPU-GPU sync points, and improper use of queries.

You can find the SLI developer documentation here.

5) Provide Scaling for UI Elements

Resolution-dependent UI elements (bitmaps) will look smaller at 4K – which may be preferred by some game players, while others will find them too small. Providing scaling support or favoring resolution-independent UI techniques will guarantee the best experience for every gamer.

6) Perform Adaptive Tessellation Based on Screen Space Metrics

Tessellation is a great fit for 4K displays, as the additional detail will be even more impressive at high resolutions. To get the most of adaptive tessellation on 4K, make sure you're using adaptive techniques which take into account screen resolution when determining tessellation factor. You'll want to be using more triangles at 4K, and screen-space tessellation metrics will naturally provide this.

7) Beware of Magnification Artifacts

In addition to magnification of source textures (see “Provide the Highest Resolution Textures” above), you will get additional magnification at 4K of fetches from other offscreen render targets, such as shadow maps. This can result in unpleasant and unexpected artifacts. It's best to test these algorithms at 4K resolution and work around these issues, such as by increasing your shadow map resolution or filter quality.

8) Optimize Video Memory Consumption

4K resolution is obviously heavier on video memory consumption than lower resolutions. Four times the pixels will mean four times the memory used for screen sized buffers, in addition to any additional memory consumed by higher resolution source art (“Maximize Texture Resolution” above) or higher resolution intermediate surfaces such as shadow maps (“Beware of Magnification Artifacts” above).

Share this post


Link to post
Share on other sites

I would guess most people who are into this topic know all of this already. ;) Additionally, nowadays there are some displays that can do UHD @ ~60 Hz with SST, such as the Asus P287Q, Samsung U28D590D or Lenovo Pro2840m. Of these at least the Asus model works fine on a Hack.

 

And while OS X officially supports some MST displays and HiDPI scaling since 10.9.3 (a little earlier for the Mac Pro), some of those officially supported displays (namely the Dell models) do not work properly on Hack (when running OS X that is, they work fine in Windows), see earlier posts.

 

Speaking about Dell, I moved the Dell UP3214Q to my office today, and on a Mac Pro (late 2013) it runs fine at 60 Hz, same as the secondary display (UP2414Q).

 

Yesterday I moved a (Mac ROM) GTX 680 (which I had sold to a friend earlier, long story) back into my old Mac Pro (see sig), replacing a Radeon 5870, updated the Mac Pro to 10.9.4 (it hadn't been used in months :P ) to give the Dell a try before I took it away. In the Displays preference pane it didn't show the usual 5 scalings/resolutions, but instead it showed the selection list that is usually only displayed once the Scaled radio button is clicked while the Option key is pressed. It could run the display at full resolution, but 30 Hz only. I'll give the ASUS PQ321 a try once I took it back home, to see if that's a Dell-specific issue.

Share this post


Link to post
Share on other sites

Any progress on this? I have Dell UP2414Q. When using MacPro 6,1 SMBIOS DP 1.2 results in blank screen. When I delete SMBIOS section from config.plist Clover auto sets it to iMac 14,2 and DP 1.2 works fine but 1080p @30Hz HiDPI, or 1080p @60Hz non HiDPI (Using Display Maestro).

 

Really hope there will be a solution soon as it is a bit laggy on 30Hz.

 

Btw, has anyone tried to use MacPro Retina 2014 SMBIOS?

Share this post


Link to post
Share on other sites

 

Sorry, it's very confusing, the circumstances to get the 60Hz are really weird.

 

For some reason I get 60Hz if I boot from a USB PenDrive with the Default Clover EFI (that plist does not have a SMBIOS and it defaults to iMac 12,2) and instead of booting the installation (on the PenDrive) I select my Mavericks SSD already installed on the Clover Screen.

 

Now, on the the Mavericks SSD already installed I also have Clovers with its own EFI and plist, that plist is MacPro6,1. I am not sure if it is a coincidence but with iMac 14,2 it did not work.

 

Do you guys now if that makes any sense? Would a second EFI/plist do something? I cannot just copy the USB EFI to Disk, that does not work, I need to run first the USB and then the SSD.

 

I have tried what you said and it does not work for me. Maybe because I have EVGA GTX 660Ti.

 

On the HDD I have MacPro 6,1 SMBIOS and on the Clover USB iMac 12,2.

 

What happens is:

 

iMac 12,2 with Nvidia injection off = Black display

iMac 12,2 with Nvidia injection on but without Clover setting "FixDisplay_0100" and FakeID for Nvidia =

 

RiCKKAv.jpg

 

iMac 12,2 with Nvidia injection on and by using Clover setting "FixDisplay_0100" and FakeID for Nvidia =

 

It shows only 3840x2160 and 1920x1080 but does not list any HiDPI modes, but whenI select 1920x1080 it looks like it is HiDPI, weird.

As you can see it also does not list any refresh rates for those 2 resolutions but I know its running at 30Hz.

 

Y9v7C86l.jpg

 

 

Btw, what revision is your monitor? Mine is A01 but apparently there is A02 also which solves issues with cold booting etc.

 

I will buy a Nvidia 800 series card when they get released, hopefully next mont, they should work better with 4K and maybe the issues with MST will be solved.

 

I really hope to get this working at 60Hz since using Windows at 4K is not so pleasant, at 100% scaling the text is small and puts a lot of strain on the eyes, at 150% scaling it is better but there is blurry text in some software (even in some apps that is part of the OS, like device manager) while some other software ignores the scaling and is showing very small text that is hard to read, etc.

Share this post


Link to post
Share on other sites

I have not been able to run it in 60Hz lately :( 

 

I have tried everything that worked before but after the update to 10.9.4 I cannot longer get it at 60Hz. Mine is A00.

 

 

 
I have tried what you said and it does not work for me. Maybe because I have EVGA GTX 660Ti.

 

On the HDD I have MacPro 6,1 SMBIOS and on the Clover USB iMac 12,2.
 
What happens is:
 
iMac 12,2 with Nvidia injection off = Black display
iMac 12,2 with Nvidia injection on but without Clover setting "FixDisplay_0100" and FakeID for Nvidia =
 
RiCKKAv.jpg
 
iMac 12,2 with Nvidia injection on and by using Clover setting "FixDisplay_0100" and FakeID for Nvidia =
 
It shows only 3840x2160 and 1920x1080 but does not list any HiDPI modes, but whenI select 1920x1080 it looks like it is HiDPI, weird.
As you can see it also does not list any refresh rates for those 2 resolutions but I know its running at 30Hz.
 
Y9v7C86l.jpg

 

 

Btw, what revision is your monitor? Mine is A01 but apparently there is A02 also which solves issues with cold booting etc.

 

I will buy a Nvidia 800 series card when they get released, hopefully next mont, they should work better with 4K and maybe the issues with MST will be solved.

 

I really hope to get this working at 60Hz since using Windows at 4K is not so pleasant, at 100% scaling the text is small and puts a lot of strain on the eyes, at 150% scaling it is better but there is blurry text in some software (even in some apps that is part of the OS, like device manager) while some other software ignores the scaling and is showing very small text that is hard to read, etc.

 

Share this post


Link to post
Share on other sites

I have not been able to run it in 60Hz lately :(

 

I have tried everything that worked before but after the update to 10.9.4 I cannot longer get it at 60Hz. Mine is A00.

 

Have you tried to revert to 10.9.3 and do what you did before?

I tried 10.9.5 13F14 now and it does not work too :(

Share this post


Link to post
Share on other sites

Have you tried to revert to 10.9.3 and do what you did before?

I tried 10.9.5 13F14 now and it does not work too :(

 

I haven't :( I am using Windows from time to time instead, MacOS is so much better as HiDPI, I am waiting to see if Yosemite solves anything.

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
      Install MacOS with Olarila Image, Step by Step, Install and Post Install  
      https://www.olarila.com/topic/5794-hackintosh-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/
          First... If you need DSDT edits for SkyLake, KabyLake or CoffeeLake... -Post your full Clover folder with original tables in Origin folder(Extract with F4 in Clover boot screen) -Post Ioreg, extract with Ioreg Explorer http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=222606 -Run it, post files generated in your desktop http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=222609  Installation   --Create a bootable copy of macOS Sierra Check out the link http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/   --Create a bootable copy of macOS HighSierra Check out the link http://diskmakerx.com/   --Paste my EFI folder into EFI partition  EFI GA H110M-S2.zip     --Install Sierra/High Sierra and boot into system!   Post Installation   --Paste my EFI folder into EFI partition  EFI GA H110M-S2.zip     --Reboot and activate video!   -Nvidia WebDriver Sierra http://www.insanelymac.com/forum/topic/312525-nvidia-web-driver-updates-for-macos-sierra-update-07212017/ -Nvidia WebDriver High Sierra http://www.insanelymac.com/forum/topic/324195-nvidia-web-driver-updates-for-macos-high-sierra-update-10162017/ -Cuda http://www.insanelymac.com/forum/topic/302795-cuda-90214-is-out-update-10162017/   --DSDT My DSDT with Skylake patches DSDT.GA H110M-S2.zip   Patches -FIX ERRORS AND WARNINGS -HPET -SATA -DMAC -SLPB -DARWIN -LPC -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -USBX -PMCR -EC -PNLF -HDMI   -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!   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 and many, many, many others!   We're all here to have fun and learn from each other!   ENJOY!  
    • By zee.malik2008
      Nvidia GT 640 3Gb not working in High sierra PC Dell Optiplex 9010. Spinning icon with mouse curser nothing else
    • By tonyx86
      This thread for installing Catalina on the Dell Latitude E6410 WITH NVIDIA GRAPHICS (BIOS A17, NVidia 3100m) will help you install a fresh installation of Catalina on your Dell Latitude E6410, it will help you upgrade from 10.15.2 to 10.15.3 (if you originally installed Catalina from this thread) and it will also help you upgrade from Mojave 10.14.6 if you have already installed Mojave by following the instructions here.  The instructions in this first post assume that you are installing Catalina in an APFS container.  If you are curious about the evolution of this solution and how sleep/wake was solved, review the Mojave installation thread.
       
      Important: This Thread is NOT intended to help you install macOS on a Latitude E6410 with Intel HD Graphics (without Nvidia graphics).  The DSDT attached to this first post (in E6410-Catalina.zip) is VERY SPECIFIC to the Nvidia graphics implementation and has not been edited for HD Graphics - there are elements required for HD Graphics that are missing from the attached DSDT and there are DSDT mods that have not been tested with HD Graphics.  Also, the kexts attached to this first post are specific to a Broadcom Wi-Fi card which must replace the original Intel Wi-Fi card.
       
      This first post will be modified to reflect lessons learned and to reflect the most current working state of my Latitude E6410 (with NVidia 3100m discrete graphics) running Catalina.  Issues, observations and performance tips are recorded toward the bottom of this first post.  My recommended CLOVER configuration is specified toward the bottom of this first post.
       
      *** If you want help with your installation, please post your issue along with problem reporting files generated using @black.dragon74's problem reporting tool.  Google 'GENERATE PROPER PROBLEM REPORTING FILES black.dragon74' to find it. ***.  If Catalina's Read-Only protections block your installation of black.dragon74's gen_debug script, please copy the attached gen_debug script to your Desktop, change script properties with the terminal command 'chmod a+x ~/Desktop/gen_debug' and run the script from your Desktop.
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) Wi-Fi: Broadcom BCM 94352HMB (replaced original Wi-Fi card) BIOS (version A17) configured as follows (leave default unless listed here): Boot Sequence: USB, Internal HDD, CD/DVD, Modular Bay HDD; Boot List Option: Legacy; Integrated NIC:Enabled; Parallel Port: Disabled; Serial Port: Disabled; SATA Operation: AHCI; Misc Devices: Enable Modular Bay, Camera, External USB, Microphone, Media Card and 1394; Latitude ON Reader: Disabled; Keyboard Illumination: Auto ALS and Input; Ambient Light Sensor: Enabled; OROM Keyboard Access: Disable; TPM Security: Disable; Computrace:Deactivate; CPU XD Support: Enable; Performance: Enable all options; Power Management: Disable Wake on AC, Disable Wake on LAN/WAN, Express Charge: Standard, Charge Behavior: Enabled; Keypad: Fn Key Only; Mouse/Touchpad: Touchpad/PS-2 Mouse; USB Emulation: Enable Legacy; Fn Key Emulation: Disabled; Fastboot: Thorough; Virtualization: Enable Intel Virtualization, Disable VT for Direct I/O, Disable Trusted Execution; Wireless Switch: Bluetooth and WLAN; Wireless Device Enable: Bluetooth and WLAN;   
      Versions of the software used in this installation are listed below the installation steps.  EFI and kexts for Catalina are attached to this first post in E6410-Catalina.zip.  CLOVER configuration is specified below the installation steps.
       
      Wi-Fi connection to an Access Point is delayed when using AppleALC for sound.  Do not use Apple ALC.  Use VoodooHDA pkg 2.9.2 v15 for sound.
       
      Steps to install Catalina on a Dell Latitude E6410 (BIOS A17, NVidia 3100m)
      Make sure that your system matches my system description above (including BIOS version, Wi-Fi card, BIOS settings) If performing an upgrade from Mojave or a previous version of Catalina, backup your Mojave or Catalina partition! (Carbon Copy or similar) Download Catalina Installer Download DosDude Catalina Patcher Use DosDude Patcher to create Catalina USB Installer Delete LegacyUSBInjector.kext (we're using @RehabMan's USBInjectAll.kext with custom SSDT) and delete SIPManager.kext (CLOVER is managing SIP) from Catalina USB Installer's /Library/Extensions folder Copy all but the FakeSMC sensor kexts in E6410-Catalina.zip (attached) LE folder to the Catalina USB Installer /Library/Extensions (copy all kexts (including FakeSMC.kext) but not the FakeSMC sensor kexts) Install CLOVER Bootloader (Legacy) on USB Installer using the EFI in the E6410-Catalina.zip (attached).  Use the CLOVER configuration specified below.  Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values. Reset your Latitude E6410 NVRAM by doing the following (this may be important if you're making changes to your existing EFI and won't hurt anything if you're not making any changes) turn-off your laptop remove A/C power and main battery press and hold the power button for 30 seconds restore A/C power and battery Boot your Latitude E6410 from the Catalina USB Installer that you created in steps 5-8. Select "Reinstall macOS" (note that I have existing installations of Mojave and High Sierra on my Latitude E6410, so it's possible that this menu item changes to "Install macOS" if you don't have any previous macOS installations). Select your Catalina destination partition (which will be your Mojave or previous Catalina partition if you are upgrading) After the Catalina Installer reboots the first time, boot from the "macOS Installer" partition on the disk that you selected as your Catalina destination (not the macOS installer on the USB) After the Catalina Installer reboots the second time, boot the Catalina macOS Installer on the USB Select the Post Install Patcher utility Select only the following Post Install Patches (no other patches / options) Install Patch Updater Legacy Video After the Post Install Patcher reboots,  boot from the newly installed (or upgraded) Catalina partition and complete the macOS configuration Remove these kexts (if they exist) from /Library/Extensions: LegacyUSBInjector.kext, LegacyUSBVideoSupport.kext and SIPManager.kext If you are performing a fresh installation of Catalina (I may be changing kext installation to EFI/Clover/kexts/Other to address Brcm Bluetooth Issue.  See discussions in Known Issues below and later in this thread): Install CLOVER on your boot disk and configure EFI using files in the attached E6410-Catalina.zip.  Use the CLOVER configuration below.  Your EFI Clover/kexts/Other folder needs only FakeSMC.kext, IntelMausiEthernet.kext, USBInjectAll.kext and VoodooPS2.kext.  Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values. Install all kexts in the attached E6410-Catalina.zip LE folder to your /Library/Extensions folder.  NOTE: These instructions assume installation of Brcm kexts in /Library/Extensions.  Read the Brcm install instructions if you're installing kexts in EFI/Clover/kexts/Other, since your installation and at least one kext WILL BE DIFFERENT. Copy HWMonitor from the application folder in the attached E6410-Catalina.zip to your Applications folder. Install VoodooHDA (I installed using the Classic method) Skip to Step 21 If you are upgrading from a previous version of Catalina using the instructions from this thread or from Mojave that you installed using the instructions here (I may be changing kext installation to EFI/Clover/kexts/Other to address Brcm Bluetooth Issue.  See discussions in Known Issues below and later in this thread): Update Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /Library/Extensions) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. NOTE: These instructions assume installation of Brcm kexts in /Library/Extensions.  Read the Brcm install instructions if you're installing kexts in EFI/Clover/kexts/Other, since your installation and at least one kext WILL BE DIFFERENT. Update IntelMausiEthernet.kext Remove VoodooSDHC.kext from /Library/Extensions Re-install VoodooHDA if necessary (I installed using the Classic method) Ensure PROPER kext installation: If you're manually installing kexts in /Library/Extensions, make sure that you execute the following (in terminal) cd /Library/Extensions sudo chown -R root:wheel *.kext sudo chmod -R 755 *.kext sudo kextcache -i / After you execute 'sudo kextcache -i /' you should observe that ALL kexts are allowed.  If not, your kext directory attributes are probably incorrect.  Repeat kext installation and try again. Reboot from your new/upgraded Catalina partition Welcome to macOS Catalina! Change the keyboard type to ISO (System Preferences > Keyboard > Change Keyboard Type) Swap the Command and Option keys (System Preferences > Keyboard > Modifier Keys) Set hibernatemode: In terminal, execute sudo pmset -a hibernatemode 0 sudo rm -f /var/vm/sleepimage sudo touch /var/vm/sleepimage sudo chflags schg /var/vm/sleepimage  
      Version Info at the time of this writing:
      Catalina Installer 10.15.3 CLOVER v2.5k r5103 DosDude Catalina Patcher: v1.3.0 Lilu.kext 1.4.2 AirportBrcmFixup.kext 2.0.6 BrcmFirmwareRepo.kext 2.5.1 BrcmBluetoothInjector.kext 2.5.1 BrcmPatchRAM3.kext 2.5.1 IntelMausiEthernet.kext 2.5.0
      VoodooHDA.kext 2.9.2 v15 (NOT AppleALC)
       
      What is not working (that was working in Mojave)
      SD Card Slot (had to remove VoodooSDHC.kext which caused system freeze on wake)  
      Known Issues and Their Solutions
      (Solved - no further work required) USB sleep/wake power IORegistry keys are not injected (not included in Mojave's or Catalina's IOUSBHostFamily.kext).  Solution is to added SSDT-USBX.aml to EFI/CLOVER/ACPI/patched.  The attached SSDT-USBX.aml includes USB sleep/wake properties for MacBookPro6,2 from High Sierra 10.13.6 IOUSBHostFamily.kext. (No solution yet) Brightness slider does not work in System Preferences > Displays.  Brightness is easily controlled with Dell brightness keys.  There is some work on this later in this thread, but I will not be solving this as I'm content with the Dell brightness keys (and Ambient Light Sensor works to auto-adjust brightness). I continue to refine the DSDT and CLOVER config.plist to optimize my Latitude E6410 for multi-booting between various macOS versions (High Sierra, Mojave and Catalina at the time of this writing). If you upgrade your Latitude E6410 EFI using my attached EFI, you may find that your Latitude E6410 is stuck in a boot-loop that ends in a white screen and reboots.  Clear your system by doing the following: turn off your laptop, remove A/C power, remove the main battery, press and hold the power button for 30 seconds, restore A/C power and battery, boot normally.  I have only found this to be necessary (very rarely) after making an EFI change, but you may find it helpful if making kext changes in /Library/Extensions as well. (Possible solution: move Brcm kexts to E/C/k/O with Clover "Inject Kexts" = YES.  Not yet implemented in the attached E6410-Catalina.zip file, so I'm leaving this work-around). (Work-around - no permanent solution yet) Cannot turn on Bluetooth after shutting-down with Bluetooth off.  Work-around is to leave Bluetooth on.  I don't use Bluetooth and don't mind, so this will likely be solved by someone else.  If you experience this issue and can't turn-on Bluetooth, I have found that putting the laptop to sleep (Fn-F1) and then waking the laptop restores proper operation of Bluetooth.  I have posted a problem description, logs and problem reporting files in this thread for help with this problem. (Solved - no further work required) Laptop does not sleep when closing lid.  Solution appears to be a combination of adding Notify (LID0) code to Method (BTNV), adding Device (PNLF) and adding the definition for pwm-info in the DSDT.  No surprise that the Latitude E6410 has yet another incomplete ACPI implementation.  I am using the same EFI for High Sierra 10.13.6, Mojave 10.14.6 and Catalina 10.15.3 and it works in all three macOSes. (No solution yet) No SD Card Slot (had to remove VoodooSDHC.kext) - I read somewhere that there is a solution that does not require any kexts (just a DSDT edit).  Haven't yet implemented this fix. (Not a problem that needs to be solved - leaving for historical purposes.  I am running Catalina without this.) - IOHWControl does not load under GFX0 (as observed in IORegistryExplorer).  Solution (if it needs to be solved) is to install AppleHWSensor.kext from a DosDude-patched Mojave /S/L/E in Catalina's /L/E.  Copy and install your own or use the kext attached to this post. (Solved - no further work required) Wi-Fi connection is delayed until a minute or so after boot - Use VoodooHDA and NOT AppleALC (Solved - no further work required) External USB ports do not work after waking from sleep (S3) - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Boot and shut-down time of Catalina is slower than Mojave - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Wi-Fi is not immediately available at OS startup - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Laptop freezes on wake - Remove VoodooSDHC.kext from /Library/Extensions  
      Tips for Improved Performance (on this and other older systems)
      System Preferences > Spotlight > Search Results: Uncheck all options System Preferences > Spotlight > Privacy: Add all Volumes System Preferences > Accessibility > Display: Check "Reduce motion" System Preferences > Accessibility > Display: Check "Reduce transparency"  
      Other tips
      If your fan is always running and temps are good, try pressing Fn + z (I haven't noticed this issue for a while since I completed DSDT edits for Mojave, but keeping this here for historical purposes)  
      CLOVER Installation: Use these configuration options
      Install Clover in the ESP Boot Sectors Install boot0af in MBR Clover for BIOS (legacy) booting Clover EFI 64-bits SATA BIOS Drivers, 64-bit Recommended drivers FSInject File System drivers ApfsDriverLoader Install RC scripts on target volume Themes Choose your desired theme Install Clover Preference Pane After clicking "Continue", if prompted with "This Clover package is incompatible with this version of macOS," install anyway  
      After CLOVER installation is complete Copy the following from the attached E6410-Catalina.zip ACPI patched contents config.plist (change XX-MASKED-XX values to your own) kexts/Other (remove all other kext folders) Remove christmas and new year folders from themes (if present)  
      Credits
      Thanks to those who contributed to my Mojave solution and to the DosDude team (for the incredible macOS patchers), I think this Catalina installation was the easiest macOS installation that I have experienced (so far).  Many thanks to @Slice and his team for the incredible work on CLOVER and for continuing to support old legacy systems like this.  Also, thanks to @Mieze and @headkaze and others I'm sure for maintaining the Brcm kexts.  And finally, I still prefer to manually apply patches to the DSDTs in my systems.  CLOVER offers extensive patching functionality, but I'm old-school and like to have an error-free, fully-patched DSDT with a simple CLOVER config.plist.  I think that this manual DSDT patching approach (which required an extensive review and debugging of the original unpatched DSDT in this thread) is the reason that this Latitude E6410 is such a perfect MacBookPro6,2.  Thank you @RehabMan for being a great teacher and for always insisting on problem reporting files .
       
       

      AppleHWSensor.kext.zip

      gen_debug
      E6410-Catalina-3v6.zip
    • By tonyx86
      *** I have started another thread for installing Catalina on the Dell Latitude E6410.  If you were thinking of installing Mojave, but would prefer to skip right to Catalina, click here. ***
       
      I was inspired by @duduclx post here for installing El Capitan on a Dell Latitude E6410, so I decided to install Mojave 10.14.5 and subsequently 10.14.6.  Everything works perfectly (including sleep).  I'm starting this thread hoping to help others install Mojave on their E6410s.  A brief installation guide is provided later in this first post.  The interested reader is encouraged to read the other posts in this thread to see how this solution evolved and to learn additional tips/details not provided in this first post (including dual-booting with macOS and Windows).
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) MacOS: Mojave 10.14.6 (APFS) (Patched with DosDude Mojave Patcher 1.3.3) MacModel: MacBookPro 6,2 (LPCB._DSM.Name "pci8086,3b09") Kexts: Lilu 1.3.6, VoodooHDA 2.9.2, AirportBrcmFixup 2.0.0, IntelMausiEthernet 2.4.1d1, ACPIBatteryManager 1.90.1, BrcmPatchRam2.kext, BrcmFirmwareRepo.kext, VoodooPS2Controller (the "Refined ALPS Touchpad" version - release 6 developed by @Dr. Hurt and compiled by @bronxteck), not the original version), USBInjectAll (with custom SSDT-UIAC), VoodooSDHC.kext (configured as shown here). Wi-Fi: Broadcom BCM 94352HMB (with AirportBrcmFixup.kext) CLOVER (Legacy): R4961  
      Configuration items that may be different from what you have seen in other E6410 configurations
      Addition of _OFF and _ON methods to _PTS and _WAK methods respectively (to control discrete graphics in order to enable sleep/wake) LPCB._DSM patched with device-id "3b09" AND "name", "pci8086,3b09" for native Nehalem power management with MacBookPro 6,2 ECDV renamed to EC so that AppleBusPowerController loads AGP.VID._DSM patched with device-id "0a29" so that AppleGraphicsPowerManagement loads No CLOVER Generate P or Generate C States (with the correct LPCB._DSM and MacBookPro 6,2, these CLOVER options are unnecessary for this architecture and only limit max multiplier and reduce number of P states) DSDT patched to include HDAU device (device-id 0x0be3)  
      What is NOT working:
      Display brightness can be controlled with keyboard keys, but cannot be controlled with slider in Display settings. Graphics Power Management - AGPM loads (because 10de,0a29 device is injected), but there's no evidence that 3100m frequency and voltage is changing.
        What is NOT tested:
      Smartcard Reader eSata (I have this disabled in my BIOS) Firewire Port (it does appear in the Network settings, just haven't tried it) Microphone Jack PC Card Slot (I have this disabled in my BIOS)  
      What IS working:
      SLEEP IS WORKING! Everything else not mentioned above.   Speedstep/CPUPowerManagement is perfect, system temps are low, CPU multiplier operates as expected, battery life is long Shutdown is fast Display/graphics acceleration is perfect (thanks to DosDude's Mojave patcher) Brightness (adjusted with brightness keys on keyboard) works perfectly Battery Manager works (battery status is displayed in menu bar) simply by installing ACPIBatterManager.kext. Wi-Fi (after changing to Broadcom BCM94352HMB and installing AirportBrcmFixup.kext) Audio (volume adjustable, volume indicator appears in menu bar).  Switched to VoodooHDA from AppleALC after AppleALC caused slow boot due to "IOHDACodecFunction timeout." Ethernet port (with IntelMausiEthernet.kext) Broadcom BCM20702A0 Bluetooth (with BrcmPatchRam2.kext and BrcmFirmwareRepo.kext) Optical Drive External VGA (with corrected NVCAP.  Need NVCAP 04000000 00000100 0E000000 00000007 00000000 (credit: here) for working external VGA display. Headphone jack Display Port (tested using DP > HDMI adapter) Camera SD Card Reader  
      Known issues and their solutions (These issues have all been resolved, with the solutions incorporated into the attached config files.  The issues are listed here for historical purposes and no further work is needed unless stated otherwise).
      USB sleep/wake power IORegistry keys are no longer provided in IOUSBHostFamily.kext after High Sierra 10.13.6.  Solution is to added SSDT-USBX.aml to EFI/CLOVER/ACPI/patched.  The attached SSDT-USBX.aml includes USB sleep/wake properties for MacBookPro6,2 from High Sierra 10.13.6 IOUSBHostFamily.kext. Laptop does not sleep on lid close.  Solution is to add Notify (LID0) code to Method (BTNV) in the DSDT.  This is solved in the attached DSDT. Leaving this for historical purposes, but the CLOVER USBFix is no longer necessary after finding that I had incorrectly applied the DSDT _DSM patch for Device (EHC1).  The CLOVER USBFix is not needed after fixing the DSDT..  AAPL,clock-id and device_type do not appear in IORegistry for EHC1.  Solution is to use CLOVER on-the-fly patching/fixing/renaming for EHC1 and EHC2.  Thank you, @feartech, for this tip. ALPS trackpad performance is not good with the "standard" VoodooPS2Controller.kext that I initially used.  Switching to the "Refined ALPS TouchPad driver" is a big improvement.  I've implemented and tested this on my system.  The ALPS version of VoodooPS2Controller.kext mixes up a few keys.  Need to switch the Command and Option keys (System Preferences > Keyboard > Modifier Keys) and change keyboard type to ISO European. This configuration (captured in the attached config files) uses an injected device-id (10de,0a29) for NVidia 3100m to get AGPM to load.  While I haven't observed any performance differences, a better approach may be to inject AGPM properties for device 10de,0a6c (the actual device-id for the 3100m).  This AGPM method is discussed later in this thread.  I have briefly tested this "FakeSMC.kext method" for injecting AGPM attributes without any noticeable changes in laptop/graphics behavior. IOHWControl is not loaded under AGPM (Should be AGP > VID > NVDA,Display-A@0 > NVDATesla > AGPM > gpu-control > IOHWControl as viewed in IORegistryExplorer).  It is loaded on a real MacBookPro6,2 running Mojave and is loaded on this Dell Latitude E6410 running High Sierra.  If I "Inject NVidia" via CLOVER, IOHWControl loads properly. The Dell Latitude DSDT (BIOS A17) has a bug in Method (GNOT).  In the method, the expression  If (LOr (LGreater (OSYS, 0x07D0), LLess (OSYS, 0x07D6))) always evaluates to TRUE, so the patched DSDT has no dependency on the value of OSYS.  I suspect that LOr should be replaced with LAnd, so that this expression is TRUE for variants of Windows 2001 and False for any other OS.  While this may have no affect on MacOS, it makes one wonder how such an obvious bug made it through Dell QA and is still present in BIOS A17.  Also makes one wonder whether the sleep problem (which no one has solved) was fixed in Windows to address another DSDT bug. The assigned value of ACOS and OSYS in the DSDT are conditional on the operating system.  There is no condition for "Darwin."  The solution is to add a condition for "Darwin" (making it equivalent to one of the defined operating systems (e.g. Linux, Win7, etc).  The attached config hard-codes ACOS and OSYS values equivalent to those for Linux.  Another way to handle this (different from the method employed in the attached config files) might be to override _OSI with XOSI (defined in a custom SSDT). The portType of the Internal Bluetooth device is portType=0 which, according to Rehabman's comments in SSDT-UIAC-All.dsl, is an external USB 2 port.  This should be an internal USB port (portType=2).  I learned through trial and error that the HUB1 and HUB2 definitions in Rehabman's SSDT-UIAC-ALL.dsl apply to the ports on the EHCx USB hubs.  The solution is to include the HUB1 definition in SSDT-UIAC.dsl and change portType to 2 for HP15.  This change doesn't appear to affect/fix sleep, but it may prevent instant wake if we get sleep working. There are minor differences between a real MacBookPro6,2 IORegistry dump and this HackBookPro6,2 IORegistry dump that can be resolved with simple DSDT edits.  I am now running with these changes, but haven't found these changes to make any difference in operational behavior.
      Rename Device (AC) -> Device (ADP1) Remove UID from Device (HPET) Add compatible ID "PNP0C01" to Device (HPET) Change ADP1:_STA from 0x0F to 0xFFFFFFFF Enable Ambient Light Sensor and renamed to Device (ALS0) from Device (ALS) Add compatible ID "smc-als" to ALS0 Rename LID -> LID0 Change "name" definitions to Buffers in _DSM methods Rename Device (PBTN) to PWRB Rename Device (SBTN) to SLPB Sleep / Wake does not work with the basic DSDT edits.  I have discovered that Sleep / Wake can be made to work by adding discrete graphics _OFF and _ON methods to _PTS and _WAK methods respectively (borrowed the concept and code from a working E6430 DSDT: Credit here: https://osxlatitude.com/forums/topic/9248-working-sleep-on-intel-hd-and-nvidia-nvs-on-dell-latitude-e6430-optimus-enabled-or-disabled/page/6/. The Clover boot arg should be changed to "darkwake=0" for reasons explained by @holyfield in this thread.  Leaving this for historical purposes: LCD screen is blank when waking laptop by opening lid (screen is not blank when waking with power button).  Solution is to add darkwake=8 to CLOVER boot args.  Thank you @Hervé for this tip.  
      Brief Installation Guide:
      Configure BIOS (version A17) as follows (leave default unless listed here): Boot Sequence: USB, Internal HDD, CD/DVD, Modular Bay HDD; Boot List Option: Legacy; Integrated NIC: Enabled; Parallel Port: Disabled; Serial Port: Disabled; SATA Operation: AHCI; Misc Devices: Enable Modular Bay, Camera, External USB, Microphone, Media Card and 1394; Latitude ON Reader: Disabled; Keyboard Illumination: Auto ALS and Input; Ambient Light Sensor: Enabled; OROM Keyboard Access: Disable; TPM Security: Disable; Computrace: Deactivate; CPU XD Support: Enable; Performance: Enable all options; Power Management: Disable Wake on AC, Disable Wake on LAN/WAN, Express Charge: Standard, Charge Behavior: Enabled; Keypad: Fn Key Only; Mouse/Touchpad: Touchpad/PS-2 Mouse; USB Emulation: Enable Legacy; Fn Key Emulation: Disabled; Fastboot: Thorough; Virtualization: Enable Intel Virtualization, Disable VT for Direct I/O, Disable Trusted Execution; Wireless Switch: Bluetooth and WLAN; Wireless Device Enable: Bluetooth and WLAN;  Create your MacOS installer USB (Use DosDude's Mojave Patcher for Mojave) (start with High Sierra and not Mojave if you're new to hackintosh). Install CLOVER (Legacy) on installer USB using attached EFI as your guide for patched ACPI, kexts and config.plist Install MacOS to your SSD.  When you run DosDude's Mojave Patcher, DO NOT install LegacyUSBInjector.kext - you're going to use Rehabman's USBInjectAll.kext.  Also, do not install the DosDude SIP kext (you're using CLOVER to manage SIP). Install the following kexts in /Library/Extensions:  ACPIBatteryManager.kext, AirportBrcmFixup.kext, BrcmFirmwareRepo.kext, BrcmPatchRAM2.kext, FakeSMC.kext, FakeSMC_ACPISensors.kext, FakeSMC_CPUSensors.kext, FakeSMC_GPUSensors.kext, FakeSMC_LPCSensors.kext, IntelMausiEthernet.kext, Lilu.kext, USBInjectAll.kext, VoodooPS2Controller.kext (the "Refined ALPS Touchpad driver," not the original), VoodooSDHC.kext (configured as shown here). Switch Command and Option keys to compensate for Refined ALPS driver issue (System Preferences > Keyboard > Modifier Keys).  Also change keyboard type to ISO European to fix the [ ` ~ ] key (to the left of the "1" (one) key. Install VoodooHDA Install HWMonitor application  
      Tips for Improved Performance (on this and other older systems)
      System Preferences > Spotlight > Search Results: Uncheck all options System Preferences > Spotlight > Privacy: Add all Volumes System Preferences > Accessibility > Display: Check "Reduce motion" System Preferences > Accessibility > Display: Check "Reduce transparency"  
      Other tips
      If your fan is always running and temps are good, try pressing Fn + z 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.  
      Credits
      In addition to those mentioned in this first post and in subsequent posts in this thread, much of this solution for the Latitude E6410 was made possible by the numerous contributions of @RehabMan.  I hope he's doing well, wherever he is.  Hopefully he has long since forgotten what a PIA I was (and still am) as I was (and still am) learning hackOS.  
       


      E6410-Mojave-v4.zip
    • By TomZanna
      Hi, I'm trying to install Mac Os Catalina on a HP 550-132NL.
      The system has:
      i7-6700
      RAM 12 GB
      GT 730
      LAN Realtek RTL8161
      ALC3863
       
      It passes the verbose phase but after the Apple logo goes away, it gets stuck on a grey screen and I can only move the pointer.
      Can I try to boot with the iGPU?
       
      origin.zip
      CLOVER_dGPU_USB_3.zip
×