Contribute
Register

[Guide] Dell XPS 9560 Big Sur OpenCore

Joined
Nov 9, 2018
Messages
57
Motherboard
Dell XPS 9560 - YH90J
CPU
I7-7700HQ
Graphics
GTX 1050, HD 630
We have been faking a light sensor for I dunno how long b/c it was used so we could save brightness through reboots. I just assumed the light sensor kext would do the same and at least through my testing it did the job. We could test it by removing it and see if brightness still saves. If not we could remove it and add the SSDT als0 from my catalina build.

My Framebuffer patches have been the same since mojave i believe so I dunno what to tell you. You can go through the dortania guide and figure your own if you think there is a problem. The FakePCIID was so that HDMI Audio would be enabled, if there is another way to enable I haven't explored it yet as it works fine and has been the case for since I believe High Sierra. We aren't faking any PCI IDs with it so the warning on not to do it doesn't really apply here.

i2c has a GitHub which points to their documentation and compatibility https://voodooi2c.github.io/#index
Ahh okay. Isn't backlight/Brightness fixed through PLNF or Whatevergreen?

Because Brightness is saved through reboots even without SMCLightSensor.(Tested it just now, with multiple Brightness values)

EDIT:

I have looked into the Audio/Teams/Discord problem. It seems SMCDellSensor has caused some problems. In the release notes I found:

  • Reduce audio lags in SMCDellSensors
  • Reduce audio lags in SMCDellSensors when USB audio device is used
So it could be that there are still problems with DellSensor.
I currently removed it and testing the next few days without it.

Another Problem which I have is still shutdown. Its taking minutes. Then it reboots with a weird apple screen. Then shutdown works again. Then its having the same problem again.
I have added the weird apple boot screen as picture.

Is this because of my different SMBIOS?
 

Attachments

  • CCF8DBE7-65EB-4135-9855-71615D3A1777_1_105_c.jpeg
    CCF8DBE7-65EB-4135-9855-71615D3A1777_1_105_c.jpeg
    141 KB · Views: 9
Last edited:
Joined
Jun 24, 2014
Messages
290
Motherboard
ASUS Maximus VII Hero
CPU
i7 4790k
Graphics
HD 4600 + GTX 970
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. iOS
@LeLunZ
Yes brightness is fixed through those things you mentioned but at least at the time or whenever, they didn't save the brightness level through reboots. Made note on removing SMCLightSensor and testing for next release. Maybe whatevergreen implemented something for this over the years and I missed it.

I tested in dcord(I believe if we type out the actual comms app it'll need mod approval) apparently not still need approval for some reason.... for like 30 minutes maybe longer, audio/camera both on and shared full screen and no problems, the other user therealthingy here seemed to confirm everything was working with the latest release and mentioned these comms app issues before. You are using the latest release?

The SMBIOS thing could be an issue, I'm sure you read my reasons in the guide. Is there a specific reason you need to use 14,3? I find the only reason people want 14,3 is to pretend they have a better laptop lol. There is no logical reason to use 14,3 that I have come across. Note even for TB b/c we only have one port. I wonder if 14,3 macOS expecting the added security from the T2 chip is giving your system problems. Could be some added layer of security for use of camera/microphone? I don't know. I just looked at the notouchid kext and seems there are some reverts in commits and notice about not needing it in 11.1. This is exactly the reason I recommend using 14,1. Trying to patch out hardware requirements to fit a laptop profile doesn't really make sense when there's already a profile that doesn't have it.

My laptop shutsdown as normal maybe 5 seconds or so. Final thought the further you stray away from my setup like using a different SMBIOS the harder it is for me to help you or to figure out solutions for new problems. I'm glad you're doing your own investigating but I think you can understand where I'm coming from.
 
Last edited:
Joined
Jun 24, 2014
Messages
290
Motherboard
ASUS Maximus VII Hero
CPU
i7 4790k
Graphics
HD 4600 + GTX 970
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. iOS
Looks like 4K users can now get their 60Hz back, I'll release a version when the time comes but basically build whatevergreen and use the new boot arg as seen below. Someone want to test it out?

- Add max pixel clock override through `-igfxmpc` boot argument or `enable-max-pixel-clock-override` and `max-pixel-clock-frequency` device properties
source: #79
 
Joined
Apr 6, 2013
Messages
11
Motherboard
Dell XPS 15 9560
CPU
i7-7700HQ
Graphics
HD 630
Mobile Phone
  1. iOS
However, since I've stopped using Thunderbolt and disabled unnecessary kexts (SMCDellSensors.kext, SMCLightSensor.kext, SMCProcessor.kext, SMCSuperIO.kext) the problem seems to be gone (no freezes since then).

I tested in dcord(I believe if we type out the actual comms app it'll need mod approval) apparently not still need approval for some reason.... for like 30 minutes maybe longer, audio/camera both on and shared full screen and no problems, the other user therealthingy here seemed to confirm everything was working with the latest release and mentioned these comms app issues before. You are using the latest release?
I should note that I'm using the latest release w/ the previously mentioned kexts disabled (i.e. also SMCDellSensors.kext).

Since then I haven't had any issues w/ freezes using Discord, M$ Teams, etc.
 
Joined
Nov 9, 2018
Messages
57
Motherboard
Dell XPS 9560 - YH90J
CPU
I7-7700HQ
Graphics
GTX 1050, HD 630
@LeLunZ
Yes brightness is fixed through those things you mentioned but at least at the time or whenever, they didn't save the brightness level through reboots. Made note on removing SMCLightSensor and testing for next release. Maybe whatevergreen implemented something for this over the years and I missed it.

I tested in dcord(I believe if we type out the actual comms app it'll need mod approval) apparently not still need approval for some reason.... for like 30 minutes maybe longer, audio/camera both on and shared full screen and no problems, the other user therealthingy here seemed to confirm everything was working with the latest release and mentioned these comms app issues before. You are using the latest release?

The SMBIOS thing could be an issue, I'm sure you read my reasons in the guide. Is there a specific reason you need to use 14,3? I find the only reason people want 14,3 is to pretend they have a better laptop lol. There is no logical reason to use 14,3 that I have come across. Note even for TB b/c we only have one port. I wonder if 14,3 macOS expecting the added security from the T2 chip is giving your system problems. Could be some added layer of security for use of camera/microphone? I don't know. I just looked at the notouchid kext and seems there are some reverts in commits and notice about not needing it in 11.1. This is exactly the reason I recommend using 14,1. Trying to patch out hardware requirements to fit a laptop profile doesn't really make sense when there's already a profile that doesn't have it.

My laptop shutsdown as normal maybe 5 seconds or so. Final thought the further you stray away from my setup like using a different SMBIOS the harder it is for me to help you or to figure out solutions for new problems. I'm glad you're doing your own investigating but I think you can understand where I'm coming from.
Thx I understand.
Lesson learned :)
MacBook Pro 14,1 has i5 or i7 (different than the i7-7700HQ)

The 14,3 has the same Prozessor and display size.
that’s why I thought it’s better to take it
 
Joined
Mar 29, 2011
Messages
66
Motherboard
Gigabyte GA-Z77X-UD5H
CPU
Intel i5 3570K
Graphics
Gigabyte GTX 650ti Boost
Mac
Classic Mac
Mobile Phone
  1. Android
Looks like 4K users can now get their 60Hz back, I'll release a version when the time comes but basically build whatevergreen and use the new boot arg as seen below. Someone want to test it out?


source: #79
It works I can confirmed, no more 48Hz.
 
Joined
Jan 31, 2011
Messages
49
Motherboard
Gigabyte GA-Z68X-UD3H
CPU
i7-2600K
Graphics
Asus Geforce GTC 660 Ti
^^ What is the procedure???
 
Joined
Mar 29, 2011
Messages
66
Motherboard
Gigabyte GA-Z77X-UD5H
CPU
Intel i5 3570K
Graphics
Gigabyte GTX 650ti Boost
Mac
Classic Mac
Mobile Phone
  1. Android
^^ What is the procedure???
Add max pixel clock override through `-igfxmpc` boot argument and delete EDID patch from Device Properties "<key>AAPL00,override-no-connect</key>.
 
Joined
Dec 21, 2018
Messages
1
Motherboard
XPS 19 9560
CPU
i7
Graphics
4K
Mobile Phone
  1. Android
  2. iOS
I also have installed the "XPS 9560 v0.3 - OC 0.6.4" version of yours and is success build for Big Sur 11.1
Its working well, but only in one external monitor! Let me explain, when I start my xps 15 9560, I have the command screen running on the xps monitor, until stops and then I plug the the external monitor, and open the desktop normally, at the shame time the xps monitor turn to black screen (with touch screen working)!
I have also update the VoodooI2C, VoodooPS2Controller to newest version but the problem remain the same.
is there something else to try on?
Thank you for your time and efforts
 
Joined
Jun 24, 2014
Messages
290
Motherboard
ASUS Maximus VII Hero
CPU
i7 4790k
Graphics
HD 4600 + GTX 970
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. iOS
I also have installed the "XPS 9560 v0.3 - OC 0.6.4" version of yours and is success build for Big Sur 11.1
Its working well, but only in one external monitor! Let me explain, when I start my xps 15 9560, I have the command screen running on the xps monitor, until stops and then I plug the the external monitor, and open the desktop normally, at the shame time the xps monitor turn to black screen (with touch screen working)!
I have also update the VoodooI2C, VoodooPS2Controller to newest version but the problem remain the same.
is there something else to try on?
Thank you for your time and efforts
Pretty sure there is language barrier issue here because I'm not understanding you. Maybe you could record a short video of what is happening?
For your 4K screen, did you build the latest whatevergreen, remove the edid override and add the max pixel clock override patch via boot args or device properties?
 
Top