Search results

@m0crt I'm sorry, I gave up on getting my 8570w working long ago. The early problem reports I posted in this thread should contain what you need. If you don't have the DreamColor display, it may work fine for you, but you'd probably have better luck with what Dsynos80 just posted from the sounds...

Because I thought maybe you wanted to see how many USB ports are possible on this system. Done, everything should now be up to date, and the port limit removal stuff is gone. Report attached.

Sorry, here you go.

I totally overlooked that I had that enabled. I disabled that, and I now have Bluetooth. :) Thanks!

I did boot with that in the boot arguments. When I boot without it, some of those unused ports are omitted in the ioreg.

My Elitebook 850 G1 has been running well from following the Probook guide. I recently got an AzureWave wifi/Bluetooth card for it, with the BCM4352 chipset, and I cannot get the Bluetooth to show up. From installing lsusb through 'brew' it seems as though the OS doesn't see Bluetooth device...

Then maybe it's something about display_cfg or connector-type. I'll have to do some more research. If all else fails I may look into getting an AMD MXM card for this thing and see if I have the same issue.

Could the internal display issue be a missing or incorrect framebuffer for the internal display? I noticed that normally the frame buffer for all ports is called "NVDA". But when booted with nv_disable=1, the internal one is called ".Display_boot" while the others are called "IONDRVFramebuffer"...

Do I also want to omit my SSDT-GFX1.aml patch? Would it conflict with the new patches in config.plist, or would it still help to inject the EDID? If I have to inject the EDID in config.plist instead, what are the other values I need to put in, in regards to these screenshots from the EDID...

I have these changes ready to go. Do I want to also use the smart merge?

I'm currently dropping all OEM tables. If I attempt this patch, I want to then keep the OEM tables, correct? And I would also want to omit the SSDT-GFX1.aml I made? Is this also done in config.plist, or in the ACPI files?

To clear up the confusion I may have caused, I've restored the SSDT-GFX1.aml file to the one I had with the EDID properly injected, and updated problem reports are attached. I totally forgot that I screwed with it more. 30227 is with nv_disable=1, and 10005 is with NVDA.

Actually, scratch that... I remember that I indeed did make a change to that aml file late last night, and is probably why EDID isn't being injected now. I'll fix that and do another report.

The only things different about that boot compared to the boot from the previous problem report, is nv_disable=1 is added to the boot arguments, and that I renamed SSDT-1.aml to SSDT-GFX1.aml as per your suggestion. It's still reading it since GFX1 is still in IORegistryExplorer. Nothing else...

NVDA,Display-C@2 is an external monitor plugged into the DP port on the dock. B is the DP port on the side of the laptop, and D is the DVI port on the dock. I've tried booting without the external plugged in, both docked and undocked, and the internal display doesn't come up in either case. In...

After figuring out the shiloh guide, I think I made some progress. I put together an SSDT file that at least accomplishes renaming GFX0 to GFX1 and I see this change reflected in IORegistryExplorer. Unfortunately I am missing some information that I likely need to put in it along with the EDID...

Since I'm using your build of Clover 4701 and that I don't have the video defined in the Devices section, is this not the way to do it? (I realize that the DualLink and ProductID are useless in there, but am I injecting the EDID wrong?)

I think I found something more relevant to what should be edited in SSDT-2-NVIDIAGF.aml, where it lists a path of \_SB.PCI0.PEGP.DGFX, but I still don't understand how to go about fixing it. Problem report attached. (I know you don't mess with Nvidia-based systems; I really appreciate you...

I found the correct EDID for it, injected it, and it's still the same. I'm pretty sure it's an issue with the DSDT. This guide seems to apply to my situation: https://www.tonymacx86.com/threads/ssdt-gpu-graphics-card-injection.183354/ But I just cannot follow it. I've studied it for hours...

Do any of you other folks who have the HP Elitebook 8570w also have the "DreamColor" display? Using the HP guide along with piecing together info from the other setups I've came across, including the one in this thread, I have macOS Mojave running on one of these with almost everything working...