Jump to content
Mezmaron

HP Elitebook 8570w with Quadro K2000M

11 posts in this topic

Recommended Posts

I installed macOS Mojave on an HP Elitebook 8570w with Quadro K2000M video with 1920x1080 "DreamColor" display. Nvidia-only, no Optimus, Intel, etc. I've installed macOS on several laptops over the past 2 years, and this is my first attempt at a system with Nvidia Graphics.

 

Most things are working, except the internal display. I can get it to work if I use nv_disable=1, but that's not optimal of course. External displays work fine, and that's what I'm currently using with it. 

 

From using guides from other forums and piecing together configs from others with the same laptop, I'm to the point where I'm injecting some video properties, including the EDID, through a Clover hotpatched ACPI file, but it seems like I'm missing some things, or not understanding some of the settings enough to where I have the correct values. Unfortunately, it's not clear if the other people with the same laptop that claimed to be successful have the same LCD that mine does, and thus I'm not sure if that's the issue. 

 

The main settings I'm questioning at the moment in the SSDT file I made are display_cfg and connector-type. The 'connector-type' especially, since the guide I followed to create this SSDT file for the blank screen issue was mainly for desktop systems. I also understand that the display_cfg setting can also determine which video ports are being used and such.

 

I'm also curious whether or not the web drivers when they become available will magically fix this. I'm also considering getting an AMD MXM card that's compatible with this laptop to see if I have the same issue.

 

If anyone out there is skilled with Nvidia and ACPI settings on laptops, I'd appreciate the help. Just let me know what files I need to post.

 

 

Share this post


Link to post
Share on other sites
Advertisement

Try and play with different SMBIOS settings. You're probably using a MacBookPro9,x right now. Experiment with such profiles as iMac or MacPro.

Share this post


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

Try and play with different SMBIOS settings. You're probably using a MacBookPro9,x right now. Experiment with such profiles as iMac or MacPro.

 

For that to properly take effect, do I have to also change the BoardID and such, or only the ProductName?

Share this post


Link to post
Share on other sites

Hello!

 

I have made the experience with Geforce mobile  fermi gfx, that injecting properties in DSDT or SSDT comes to late to get the internal display working. Using a mobile device SMB is obligatory. Try it with MBP 9,1 / 10,1; as Herve has writen, and create with gfxutil a correct property string to inject it with Clover and disable Clover gfx injection and any property injection by DSDT/SSDT.

 

Getting an  original ioregfile of MBP 9,1/10,1 could be helpful to create a string for your K2000m.

 

Have fun.

Share this post


Link to post
Share on other sites

Try with a full SMBIOS profile to begin with. If you find one (or more) profile that gives you internal display, we can adjust the board id of the SMBIOS profile that you'd be expected to use (MBP9,x/10,x).

Share this post


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

Try with a full SMBIOS profile to begin with. If you find one (or more) profile that gives you internal display, we can adjust the board id of the SMBIOS profile that you'd be expected to use (MBP9,x/10,x).

 

I just tried a ton of different ones, to no avail.

 

It makes no sense to me why I've seen others with this same laptop, same video, have no trouble at all with the internal display. I've looked over configs that they posted and I can find nothing significant. They're not even using hot patches like I tried. Unfortunately, those people are no longer active on the forum I saw them post on, or I'd try and get in touch with them to see if they're using the DreamColor display. That's the only variable I can think of that would be different.

 

I'm about to give up and install High Sierra so that I can install the web drivers, and see if that's the magic key. That is one thing I noticed that the others are using, though I'm not sure how they're doing it with Mojave, unless they started with High Sierra and upgraded, and the web drivers remained.

Share this post


Link to post
Share on other sites

So I installed High Sierra on another volume, installed the web drivers, and it was no different.

 

The DSDT/SSDTs for this laptop are a little odd when it comes to video. The PCI slot is identified as "PEGP", and there is a GFX0 device under it, which macOS seems to see as the graphics card. However, there is also a "DGFX" device entry. In one of the SSDT tables called "SSDT-2-NVIDIAGF.aml" which I imagine is obviously related specifically to the graphics card, DGFX seems to be what it refers to as the graphics card. This apparently is odd when it comes to Hackintosh stuff, since I can find few references to it when searching for info on DSDT/SSDT patching.

 

So I thought a possible solution would be to rename the present GFX0 to GFX1, and DGFX to GFX0 in the DSDT.aml and SSDT-2-NVIDIAGF.aml and throw them in the patched folder. This also failed.

 

If I don't get this figured out soon, I may pick up the AMD MXM card that is compatible with this laptop, which is a FirePro M4000, and hope that I have an easier time with that.

Edited by Mezmaron
Tried what I proposed, and updated with the result.

Share this post


Link to post
Share on other sites

I ordered the FirePro M4000 MxM card, I'm really hoping it "just works" and that I don't have the same problem. It's apparently similar to a Radeon HD 7770M.

 

I'm very skeptical, however. Anyone else have any predictions on it working?

Share this post


Link to post
Share on other sites

The AMD FirePro M4000 card arrived, and it's installed.

 

Now, at the same part of the boot process where the internal display previously turned off, now the system reboots.

 

I don't get it. I have no Nvidia-specific kexts or config.plist entries. What Mac model with AMD graphics would be good to use for the SMBIOS, assuming that's the issue?

Share this post


Link to post
Share on other sites

I've since given up on it, unfortunately, and went back to the Windows install on that laptop. It was just too frustrating after working on it for 3 weeks straight and getting nowhere.

 

FWIW, I booted from a Linux live USB at one point and it identified the internal display as using an eDP connection instead of LVDS. Maybe that was the key, but I did try specifying the port as an eDP with a hotpatch. It would show my changes in ioreg, but it made no difference. Whether or not I was doing it right is another matter, but I was getting no answers anywhere.

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.

×