Contribute
Register

[Guide] Dell XPS 9560 Monterey OpenCore

Joined
Jun 24, 2014
Messages
289
Motherboard
ASUS Maximus VII Hero
CPU
i7 4790k
Graphics
HD 4600 + GTX 970
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. iOS
So, no touchscreen is not the end of the world perhaps but without voodooI2CHID the touchpad is hot garbage. Inputs can be jerky but the gestures are almost unusable. 2 finger scrolling works OK (Some jerkiness) but the 3-4 finger swipe (Swiping up and also left<->right) barely works and the pinch gesture does not work at all.

So no more kernel panics but also a bad experience with the touchpad... I'll update if I find a solution in the meantime but I may end up just reverting to Monteray because that was flawless.
Think an easy solution to this would be disable the touchscreen via bios, could be a quick fix while still keeping voodooI2CHID. If you still want touch for windows and not turn it off in bios then change the scope below from Return (GPLD (Zero, 0x05)) to Return (GPLD (Zero, Zero))

SSDT-USBP.aml
Code:
        Scope (HS09)
        {
            Method (_UPC, 0, NotSerialized)  // _UPC: USB Port Capabilities
            {
                Return (GUPC (One))
            }

            Method (_PLD, 0, NotSerialized)  // _PLD: Physical Location of Device
            {
                Return (GPLD (Zero, 0x05))
            }
        }

No idea if this will work, set the USB port to be external, believe you'd change GPLD call to be (One, 0x05). I think: Zero = internal and One = external as referenced by HS01 and HS02 being external ports?

It looks like voodooi2c causes the panic but since it's only on shutdown, we can guess when macOS shuts down it asks voodooi2c to do xyz to the USB controller to power down. I looked at the thread linked and the crash report, it's crashing when recalling something stored in RAM on shutdown. If we change the port to external it may circumvent this call but won't be surprised if thats not the case. SSDT-I2C.aml is a bit beyond me since I been away so long but the solution will have to be there or by voodooi2c dev changing some thing during shutdown operations.

offtopic
I visited this thread bc I have the laptop back but it's kind of broken (hinge separation), very young nephew and high energy dog. Was curious on what has been happening with this nice laptop. I'm glad to see everyone chugging along with their hacks, brings back good memories. The things I've learned while doing hackintosh stuff has been a great asset at my work which provided me a sweet a M1 MBP over a year ago, Apple Silicon does not disappoint.
 
Joined
Jul 25, 2013
Messages
423
Motherboard
Asus X99 Deluxe
CPU
E5-2697v3
Graphics
RX 580
Mac
  1. iMac
  2. MacBook
  3. MacBook Air
  4. MacBook Pro
  5. Mac Pro
Classic Mac
  1. iMac
  2. Power Mac
  3. Xserve
Mobile Phone
  1. Android
  2. iOS
offtopic
I visited this thread bc I have the laptop back but it's kind of broken (hinge separation), very young nephew and high energy dog. Was curious on what has been happening with this nice laptop. I'm glad to see everyone chugging along with their hacks, brings back good memories. The things I've learned while doing hackintosh stuff has been a great asset at my work which provided me a sweet a M1 MBP over a year ago, Apple Silicon does not disappoint.

Depending on how the hinge broke, and how serviceable you need it to be in the future, some epoxy will do wonders here. I fixed my old Precision 5510 (XPS 9550) this way, and it's still kicking.
 
Joined
Jun 24, 2014
Messages
289
Motherboard
ASUS Maximus VII Hero
CPU
i7 4790k
Graphics
HD 4600 + GTX 970
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. iOS
Depending on how the hinge broke, and how serviceable you need it to be in the future, some epoxy will do wonders here. I fixed my old Precision 5510 (XPS 9550) this way, and it's still kicking.
THAT is a great idea. I will try this. One of the standoffs (?) where the hinge is screwed down broke. Maybe I can get it glued back on and then at worse over epoxy it so that it holds when its screwed back in. Thank you.
 
Joined
Sep 27, 2020
Messages
35
Motherboard
Dell XPS 9560
CPU
i5-7300HQ
Graphics
GTX 1050
Mac
  1. MacBook Air
Mobile Phone
  1. Android
My 9560 had been chugging along pretty well until I started having problems with iCloud. I am asking for help here because some of the symptoms keep changing.

When I first set it up, it was clear that upon startup, my wifi dongle (en0) had to connect first to make things good with Apple; I have a single App Store purchase (Magnet) that fails to register and the system lets me know. Sometimes I would have to wait for wifi to connect (so that Magnet would get registered) before plugging in my Ethernet USB adapter for more speed.

Things have since become weird and were complicated by a flaky USB port (clearly hardware and common on the 9560); I've now switched the dongle. For a while, I couldn't get Magnet to register. One of the fixes suggested was to log out of iCloud and back in. Now, I simply can't log back in (from system prefs) so contacts, calendars, etc. are messed up. I get "Could not communicate with the server." However, I can logout and login just fine in the App Store.

None of the methods proposed for real Macs for this error have fixed this. Confusing me further, Magnet now registers at startup (but only most of the time) even without being logged in!

Does this combination suggest an obvious culprit? Should I regenerate the serial as though this is a new installation? Should I wipe and reinstall?

Thanks!
 
Last edited:
Joined
Dec 16, 2013
Messages
5
Motherboard
Dell XPS 9560
CPU
Intel Core i7
Graphics
Intel HD Graphics 630
Thank you for sharing your info. Can you please tell me if you are having issues with Bluetooth on your DW1830?
No issues with BT. I can turn it on and off. Occasionally if I run too much on the CPU or push the laptop too hard it "locks up" and everything disconnects. (Then I can't turn it on or off.) This happens rarely and I haven't quite figured out why it happens. Otherwise, it displays the connected devices or scans like normal.
 
Joined
Sep 27, 2020
Messages
35
Motherboard
Dell XPS 9560
CPU
i5-7300HQ
Graphics
GTX 1050
Mac
  1. MacBook Air
Mobile Phone
  1. Android
Has anyone tried the new VoodooI2C to see if the touchscreen is working porperly?
I rarely use my touchscreen, but you prompted me to check.

I upgraded to 13.1 after significant difficulties. I update kexts with OCA and have VoodooI2C 2.7.1 and VoodooI2CHID 1. I am set up with a huge 4K monitor run through the DP of a TB16 dock. My touchscreen works on both the external monitor and the laptop screen. I tested the touchpad (rarely use it) and it seems to work better than ever.
 
Joined
Sep 18, 2010
Messages
583
Motherboard
Asus Z87 Maximus Gene VI
CPU
i7-4790K
Graphics
Vega 64
Mac
  1. iMac
Mobile Phone
  1. iOS
I rarely use my touchscreen, but you prompted me to check.

I upgraded to 13.1 after significant difficulties. I update kexts with OCA and have VoodooI2C 2.7.1 and VoodooI2CHID 1. I am set up with a huge 4K monitor run through the DP of a TB16 dock. My touchscreen works on both the external monitor and the laptop screen. I tested the touchpad (rarely use it) and it seems to work better than ever.
Good to know. I want to buy this laptop but only if Ventura is compatible with it. I have been following this thread and saw that everyone who upgraded to Ventura had issues with the touchscreen. I'm hoping everything else is functioning correctly.
 
Joined
Jul 15, 2019
Messages
29
Motherboard
Dell XPS 9560
CPU
i7-7700HQ
Graphics
GTX 1050/HD 630
Mac
  1. MacBook Air
Mobile Phone
  1. Android
I rarely use my touchscreen, but you prompted me to check.

I upgraded to 13.1 after significant difficulties. I update kexts with OCA and have VoodooI2C 2.7.1 and VoodooI2CHID 1. I am set up with a huge 4K monitor run through the DP of a TB16 dock. My touchscreen works on both the external monitor and the laptop screen. I tested the touchpad (rarely use it) and it seems to work better than ever.

Hmmm... I was hopeful after reading your message. I just now upgraded the I2C kexts to the newest 2.7.1 versions and upgraded to Ventura 13.1. Using OC 0.8.8, checked my config file and all looks correct.

I'm still getting kernel panics, just like when I tried before. The error log is identical. Downloaded the kexts directly from the I2C Github page and also cleared NVRAM, just in case. Nope, kernel panicking every time I go to shut down or restart the machine. Looking on the Github issues page, people are still reporting this issue with 2.7.1.
Disabled the touchscreen in the BIOS and at least the Kernel Panics have stopped. Will probably just live with this for the time being, as I don't fancy cloning from my CCC bootable backup and then doing the Filevault encryption again. Will keep an eye on I2C releases and that issues section to see if there are any updates.

Aside from the kernel panics, the upgrade to 13.1 was pretty smooth and the other functionality all seems to be as it was before.

Genuinely curious as to why your machine doesn't experience kernel panics upon shut down/restarts and mine does. Either way, can't recommend anyone upgrades to Ventura based on my experience but if someone wants to be a guinea pig to give it a try, I would appreciate it.
 
Top