search

zachs78 / MacOS-XPS-9500-OpenCore

OpenCore EFI that allows you to install and boot macOS X Catalina on your Dell XPS 15 9500 (2020)
MIT License
98 stars 11 forks source link

Potential Fix for S3 sleep and headphone jack #3

Open Drowningfish223 opened 3 years ago

Drowningfish223 commented 3 years ago

check out this to fix S3 sleep. rEFInd is a great tool, but AcpiPatcher.efi might also be able to be injected in the opencore/drivers folder if you don't want to use rEFInd. If you get a flickering screen or have the igpu lock to 350 mhz after sleep, add igfxfw=2 to your boot args to load apple's native GuC firmware. That also enables iGPU power management.

For the headphone jack, try adding verbstub.kext to your kexts folder. Jaromeyer has a folder with materials and instructions on his read.me on how to install combojack, which is a related utility. His solution worked for me.

Also, how efficient is S2 sleep? Please let me know, because I've had sleep related issues on my laptop and disabling S3 could be a solution.

Let me know if any of this works!

Drowningfish223 commented 3 years ago

@zachs78 Also, I forgot to mention-karabiner elements will let you map your function keys, including brightness. I recommend checking it out. You might have to use the top-case apple logo setting to change brightness if the default brightness option doesn't work. You'll understand if you check it out.

Another quick question: given the amazingly large trackpad, do you have any palm rejection issues?

Good luck!

zachs78 commented 3 years ago

rEFInd isn't going to help. This is an OpenCore EFI? AFAIK rEFI is an EFI to re-enable S3 for Windows 2004. I am not on Windows 2004 yet and CsEnable works well there. S3 is just as broken though (Dell BIOS bug) and S2 sleep is terrible!

I want to map the brightness key properly via SSDT. Any idea how to do that?

I haven't had any problems with palm rejection to be honest, but I use an external keyboard and mouse most of the time. The keyboard layout with the home button sharing the same physical button as F11 doesn't quite work for a programmer. Given that I have an external dock and bluetooth headset, I haven't found the need to use a headphone jack either. The only real annoyance is I can't put the laptop to sleep, but it's no different to Windows.

thefiredragon commented 3 years ago

I could remap brightness keys I had also own a Dell XPS, I would share my effort here

thefiredragon commented 3 years ago

@zachs78 I'll contact dell support, and also found your dell threads about broken sleep, dell don't want to test it internally and want to replace the motherboard of my device, what do you think? I had wrote 3 days about it.

Rastafabisch commented 3 years ago

There might be another way for enabling sleep support. Apparently S3 sleep mode can be successfully hacktivated on either the 13” 9300, as well as the 17” 9700 model. That said it is know that the same setting do not yield in a useable S3 mode on the 9500 model due to the aforementioned firmware bug. However what might be a doable approach, is to flash a 9700 bios to the 9500 model as those are fairly similar. This could also be done incrementally by comparing both bios and replacing only certain modules (UEFI tool + bin-Walk). @zachs78: Do you think this is feasible?

suservu123 commented 3 years ago

AcpiPatcher.efi can enable s3 standby Before: D0AFB097-C0B1-44DD-857D-44BF66983748 After: 27AD909E-36C5-4F1A-A49D-C85BDF144C17

but when computer wake it will be black screen and have to be hard reset

  1. Combojack doesn’t work for My xps 9500
thefiredragon commented 3 years ago

How did you enabled s3?

suservu123 commented 3 years ago

How did you enabled s3?

Yeah, and cannot wake :)))

suservu123 commented 3 years ago

How did you enabled s3?

Use rEFind to enable s3 with driver: acpipatcher.efi .By this way linux and win wake with black screen

suservu123 commented 3 years ago

50F226BF-B18F-480F-9A9F-E341445E3075

yep you can sleep but when wake up laptop screen will be black just, backlight just turn on

thefiredragon commented 3 years ago

But external Screen Turn on?

theres a new bios update 1.7 or something like this

suservu123 commented 3 years ago

But external Screen Turn on?

theres a new bios update 1.7 or something like this

My bios is newest. Maybe flash bios 1.4 will slove the problem

sweet3c commented 3 years ago

@zachs78 bios 1.8 slove the S3 Sleep problem?
In windows OS the Application "Dell Command | Configure" has many options to controll bios I'm not sure is that userful.

I tried the DeepinOS, this OS can support Sleep

thefiredragon commented 3 years ago

For me 1.8 also not enable s3 sleep It will Hang on s3 logo

VGerris commented 1 year ago

one of many threads is here : https://www.dell.com/community/Precision-Mobile-Workstations/precision-5550-S3-sleep-not-working/td-p/7759319 ( 5550 precision is pretty much xps 9500 with different wifi and nvidia chip). you can still enable S3 with a registry setting but as many post, after wake the laptop hangs - depending on your signs of life settings you get a black screen or the Dell logo. This is a major BIOS bug that I reported to Dell support and posted on the community forums about, so far without results. I would be interested to know if anyone can make S3 sleep work with DSDT patches by figuring out what precisely goes wrong at S3 wake. Perhaps injection with OpenCore (or rEFIt) can fix it or at least let it fall back to S2. The only thing that works for me is to disable S3 sleep and use hibernate. I tried to use this : https://github.com/acidanthera/HibernationFixup but no matter what I try, the laptop either does not sleep like 'modern sleep' and uses more than 5% an hour and stays hot, or it goes in some form of sleep but does not wake up, even with the S3 disabled. Hibernate is a bad solution because it wears the SSD but it is arguably better than no sleep (modern) but I cannot get it to work on MacOS. On Windows it seems the OS hibernates when S3 is forced to be enabled, so Dell must have done something in the drivers. On Linux, with S3 enabled in BIOS the machine hangs, with it disabled it uses a lot of energy ( haven't tried hibernate yet).

Dell does a terrible job here and should really fix this in the BIOS. Any workaround for MacOS is appreciated also for brightness mapping (DSDT).

AO554 commented 1 year ago

50F226BF-B18F-480F-9A9F-E341445E3075

yep you can sleep but when wake up laptop screen will be black just, backlight just turn on

It would make me curious to believe then if its just platformid/ACPI patching for the display part just to get working again otherwise, thats what I'd first suspect since its coming out of sleep

VGerris commented 1 year ago

For the record, Dell did replace my motherboard, did a terrible job at it, with a screw missing, screws loose, protection pads loose, etc. The support was the worst experience ever. On the plus side, I got them to admit that the problem is in the BIOS ( firmware ) and also that they will fix it, but that they could not give a timeline - so don't be surprised if it is in fact never. The worst is that while the laptop was away, two BIOS updates were released, that did not solve the issue ( on 1.21 now ). I tried to implement a workaround with HibernateFixup. It almost works, but after wake and boot with preselected MacOS in OC, it hangs in black screen. I will try to see if I can find the root cause for it.

I also tried to patch the DSDT by having S3 do S0 but I am not sure if it did anything, I got the same issue with the wake to logo hang issue. I did try to compare an XPS 9700 BIOS with my Precision 5550 but there were to many differences. Could anyone dump the full DSDT and SSDT files for the latest BIOS of that? I hope someone else with more knowledge on this may be of help, I think looking with more understanding to the diff might point to the cause of the problem, or at least makes it work with the sign-of-life options off, like on the XPS 9700.

I would love to see S3 fixed. Let's keep going :)

VGerris commented 1 year ago

Precision 5550 BIOS got an update to 1.22 without option to go back to 1.21 or earlier. It does not fix the S3 issue.

VGerris commented 1 year ago

update to 1.23.1 , no change. yes Dell, you suck.

VGerris commented 1 year ago

I am thinking about selling the Precision 5550 because of the sleep issue. Does anyone have any suggestions on last attempts tp try? I bought an HP and intent to never look back if I get a good price for this machine. cheers

VGerris commented 1 year ago

Got my hands on an XPS 17 and thought sleep did not work, but it turned out it only works when power is plugged in at the time the sleep is triggered, see also : https://www.reddit.com/r/Dell/comments/hla8yk/how_to_enable_s3_deep_sleep_on_xps_17_9700_in/ . This does not work on the XPS 15. I am not sure if I have enough time and skill to find the XPS 17 issue - this seems fixable. If anyone is up for the task or can help, please let me know. Tips on tooling, testing, debugging, methods etc. If that issue can be fixed it may be possible to compare BIOSes and find the additional bug in the XPS 15 / Precision 5550. Thanks!

sweet3c commented 1 year ago

Got my hands on an XPS 17 and thought sleep did not work, but it turned out it only works when power is plugged in at the time the sleep is triggered, see also : https://www.reddit.com/r/Dell/comments/hla8yk/how_to_enable_s3_deep_sleep_on_xps_17_9700_in/ . This does not work on the XPS 15. I am not sure if I have enough time and skill to find the XPS 17 issue - this seems fixable. If anyone is up for the task or can help, please let me know. Tips on tooling, testing, debugging, methods etc. If that issue can be fixed it may be possible to compare BIOSes and find the additional bug in the XPS 15 / Precision 5550. Thanks!

I have asked the DELL service, the recover is XPS9500 The hardware design is flawed, so I give up trying

jkbuha commented 1 year ago

Hi guys, spotted this just now when I was looking at S3 sleep for the 9520. This is going to sound a bit controversial, but under one of the latest mainline linux kernels (mine's kali 6.1.0) it is possible to successfully trigger S3 sleep/wake under Linux. Logs hereunder:

`──(jkbuha㉿kali)-[~/Downloads/XPS-9520-AlderLake-OpenCore-main/EFI] └─$ uname -a
Linux kali 6.1.0-kali9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1kali1 (2023-05-12) x86_64 GNU/Linux

┌──(jkbuha㉿kali)-[~/Downloads/XPS-9520-AlderLake-OpenCore-main/EFI] └─$ cat /sys/power/mem_sleep s2idle [deep]

┌──(jkbuha㉿kali)-[~/Downloads/XPS-9520-AlderLake-OpenCore-main/EFI] └─$ dmesg | grep S3 [ 0.247410] ACPI: PM: (supports S0 S3 S4 S5) [ 53.907883] ACPI: PM: Preparing to enter system sleep state S3 [ 54.213848] ACPI: PM: Waking up from system sleep state S3

┌──(jkbuha㉿kali)-[~/Downloads/XPS-9520-AlderLake-OpenCore-main/EFI] └─$ `

To validate this you'll need to (a) set the ACPI UEFI IFR 'S3 Sleep' variable to enabled (default is off for 9510/20/30 but should be set for 9500) and also boot linux from an existing partition where mem_sleep is already set to [deep], as it's usually not enabled by default on a live usb.

I suspect the kernel devs have activated a different wake path via _GPRW but will spend some more time investigating this to see if it can be backported onto MacOS and injected via SSDT.

VGerris commented 1 year ago

hi, thanks for sharing, that may be interesting. Just for clarity, when running Linux with mem_sleep set to deep ( kernel param ) on both 9500 and 9700 models, they hang, but the 9700 works when on power. It may be interesting to look at the kernel patches to understand what is fixed, because something more is broken in the BIOS - and very likely some device's sleep or wake action. Any hints on how to pin it down are very much appreciated, I still have both models with multiple OSes to test!

jkbuha commented 1 year ago

I can leave here the dmesg log for a successful 9520 deep (S3) mem_sleep

[ 30.584022] PM: suspend entry (deep) [ 30.593445] Filesystems sync: 0.009 seconds [ 30.593752] (NULL device ): firmware: direct-loading firmware regulatory.db.p7s [ 30.593758] (NULL device ): firmware: direct-loading firmware iwlwifi-so-a0-gf-a0.pnvm [ 30.593759] (NULL device ): firmware: direct-loading firmware regulatory.db [ 30.593768] (NULL device ): firmware: direct-loading firmware intel/ibt-0040-0041.ddc [ 30.593901] (NULL device ): firmware: direct-loading firmware intel/ibt-0040-0041.sfi [ 30.593934] (NULL device ): firmware: direct-loading firmware iwlwifi-so-a0-gf-a0-72.ucode [ 30.593994] (NULL device ): firmware: direct-loading firmware i915/adlp_dmc_ver2_16.bin [ 30.594263] (NULL device ): firmware: direct-loading firmware i915/adlp_guc_70.bin [ 30.594438] (NULL device *): firmware: direct-loading firmware i915/tgl_huc.bin [ 30.594960] Freezing user space processes [ 30.615610] Freezing user space processes completed (elapsed 0.020 seconds) [ 30.615613] OOM killer disabled. [ 30.615613] Freezing remaining freezable tasks [ 30.616781] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) [ 30.616822] printk: Suspending console(s) (use no_console_suspend to debug) [ 31.188030] ACPI: EC: interrupt blocked [ 31.264884] ACPI: PM: Preparing to enter system sleep state S3 [ 31.286289] ACPI: EC: event blocked [ 31.286297] ACPI: EC: EC stopped [ 31.286299] ACPI: PM: Saving platform NVS memory [ 31.286452] Disabling non-boot CPUs ... [ 31.290329] smpboot: CPU 1 is now offline [ 31.299793] smpboot: CPU 2 is now offline [ 31.308268] smpboot: CPU 3 is now offline [ 31.311329] smpboot: CPU 4 is now offline [ 31.316461] smpboot: CPU 5 is now offline [ 31.319094] smpboot: CPU 6 is now offline [ 31.324214] smpboot: CPU 7 is now offline [ 31.326881] smpboot: CPU 8 is now offline [ 31.331874] smpboot: CPU 9 is now offline [ 31.334578] smpboot: CPU 10 is now offline [ 31.339412] smpboot: CPU 11 is now offline [ 31.341948] smpboot: CPU 12 is now offline [ 31.344303] smpboot: CPU 13 is now offline [ 31.346608] smpboot: CPU 14 is now offline [ 31.349223] smpboot: CPU 15 is now offline [ 31.351543] smpboot: CPU 16 is now offline [ 31.353858] smpboot: CPU 17 is now offline [ 31.355943] smpboot: CPU 18 is now offline [ 31.358106] smpboot: CPU 19 is now offline [ 31.389021] ACPI: PM: Low-level resume complete [ 31.389111] ACPI: EC: EC started [ 31.389114] ACPI: PM: Restoring platform NVS memory [ 31.390460] Enabling non-boot CPUs ... [ 31.390588] x86: Booting SMP configuration: [ 31.390591] smpboot: Booting Node 0 Processor 1 APIC 0x1 [ 31.401366] CPU1 is up [ 31.401442] smpboot: Booting Node 0 Processor 2 APIC 0x8 [ 31.440925] CPU2 is up [ 31.440997] smpboot: Booting Node 0 Processor 3 APIC 0x9 [ 31.452201] CPU3 is up [ 31.452270] smpboot: Booting Node 0 Processor 4 APIC 0x10 [ 31.460588] CPU4 is up [ 31.460647] smpboot: Booting Node 0 Processor 5 APIC 0x11 [ 31.462911] CPU5 is up [ 31.462969] smpboot: Booting Node 0 Processor 6 APIC 0x18 [ 31.470404] CPU6 is up [ 31.470469] smpboot: Booting Node 0 Processor 7 APIC 0x19 [ 31.472789] CPU7 is up [ 31.472848] smpboot: Booting Node 0 Processor 8 APIC 0x20 [ 31.480339] CPU8 is up [ 31.480413] smpboot: Booting Node 0 Processor 9 APIC 0x21 [ 31.482948] CPU9 is up [ 31.483002] smpboot: Booting Node 0 Processor 10 APIC 0x28 [ 31.490498] CPU10 is up [ 31.490575] smpboot: Booting Node 0 Processor 11 APIC 0x29 [ 31.492994] CPU11 is up [ 31.493069] smpboot: Booting Node 0 Processor 12 APIC 0x30 [ 31.499557] core: cpu_atom PMU driver: PEBS-via-PT [ 31.499562] ... version: 5 [ 31.499562] ... bit width: 48 [ 31.499563] ... generic registers: 6 [ 31.499564] ... value mask: 0000ffffffffffff [ 31.499564] ... max period: 00007fffffffffff [ 31.499565] ... fixed-purpose events: 3 [ 31.499565] ... event mask: 000000070000003f [ 31.500340] CPU12 is up [ 31.500412] smpboot: Booting Node 0 Processor 13 APIC 0x32 [ 31.504144] CPU13 is up [ 31.504218] smpboot: Booting Node 0 Processor 14 APIC 0x34 [ 31.508045] CPU14 is up [ 31.508128] smpboot: Booting Node 0 Processor 15 APIC 0x36 [ 31.511970] CPU15 is up [ 31.512050] smpboot: Booting Node 0 Processor 16 APIC 0x38 [ 31.519054] CPU16 is up [ 31.519104] smpboot: Booting Node 0 Processor 17 APIC 0x3a [ 31.523055] CPU17 is up [ 31.523113] smpboot: Booting Node 0 Processor 18 APIC 0x3c [ 31.526924] CPU18 is up [ 31.526982] smpboot: Booting Node 0 Processor 19 APIC 0x3e [ 31.531013] CPU19 is up [ 31.539714] ACPI: PM: Waking up from system sleep state S3 [ 31.587716] ACPI: EC: interrupt unblocked [ 31.689843] ACPI: button: The lid device is not compliant to SW_LID. [ 61.703044] ACPI Error: Aborting method _SB.PC00.PEG1.NPON due to previous error (AE_AML_LOOP_TIMEOUT) (20220331/psparse-529) [ 61.703107] ACPI Error: Aborting method _SB.PC00.PEG1.PG01._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20220331/psparse-529) [ 61.845964] ACPI: EC: event unblocked [ 61.866527] i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_70.bin version 70.5.1 [ 61.866531] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3 [ 61.873297] xhci_hcd 0000:00:0d.0: xHC error in resume, USBSTS 0x401, Reinit [ 61.873309] usb usb3: root hub lost power or was reset [ 61.873313] usb usb4: root hub lost power or was reset [ 61.879655] i915 0000:00:02.0: [drm] HuC authenticated [ 61.880030] i915 0000:00:02.0: [drm] GuC submission enabled [ 61.880031] i915 0000:00:02.0: [drm] GuC SLPC enabled [ 61.880378] i915 0000:00:02.0: [drm] GuC RC: enabled [ 61.884069] nvme nvme0: 20/0/0 default/read/poll queues [ 61.920002] nvme nvme1: 20/0/0 default/read/poll queues [ 62.115247] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [ 62.391262] usb 1-6: reset high-speed USB device number 2 using xhci_hcd [ 62.421360] ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done OK, num_hid_devices=1 [ 62.559301] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) [ 62.561728] Bluetooth: hci0: Device revision is 0 [ 62.561737] Bluetooth: hci0: Secure boot is enabled [ 62.561739] Bluetooth: hci0: OTP lock is enabled [ 62.561740] Bluetooth: hci0: API lock is enabled [ 62.561742] Bluetooth: hci0: Debug lock is disabled [ 62.561743] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 62.561747] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 [ 62.561757] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi [ 62.561856] Bluetooth: hci0: Boot Address: 0x100800 [ 62.561859] Bluetooth: hci0: Firmware Version: 107-51.22 [ 62.562372] OOM killer enabled. [ 62.562383] Restarting tasks ... done. [ 62.563435] random: crng reseeded on system resumption [ 62.578816] usb 1-9: USB disconnect, device number 3 [ 62.610895] PM: suspend exit [ 62.710877] usb 1-9: new full-speed USB device number 5 using xhci_hcd [ 62.864842] usb 1-9: New USB device found, idVendor=27c6, idProduct=63ac, bcdDevice= 1.00 [ 62.864857] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 62.864862] usb 1-9: Product: Goodix USB2.0 MISC [ 62.864866] usb 1-9: Manufacturer: Goodix Technology Co., Ltd. [ 62.864869] usb 1-9: SerialNumber: UID820612F3_XXXX_MOC_B0 [ 64.490387] Bluetooth: hci0: Waiting for firmware download to complete [ 64.490582] Bluetooth: hci0: Firmware loaded in 1883616 usecs [ 64.490911] Bluetooth: hci0: Waiting for device to boot [ 64.507778] Bluetooth: hci0: Device booted in 16786 usecs [ 64.507800] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc [ 64.511972] Bluetooth: hci0: Applying Intel DDC parameters completed [ 64.515960] Bluetooth: hci0: Firmware timestamp 2022.51 buildtype 1 build 56683<

In the kernel dev chats I can see some unorthodox return to wake through a different EC mapping. I'll see where it leads. In the meantime if you can see if can spot any differences in the 9700 sleep logs (or at least where the 9500 fails).

VGerris commented 12 months ago

This is my dmesg output for a lid closed sleep on Fedora 38, kernel 6.4.14-fc200 on the XPS 9700 ( latest BIOS ).

[ 153.230924] wlp0s20f3: deauthenticating from ba:15:a2:3b:f0:cd by local choice (Reason: 3=DEAUTH_LEAVING) [ 153.669465] ACPI: button: The lid device is not compliant to SW_LID. [ 154.522133] rfkill: input handler enabled [ 154.680796] PM: suspend entry (deep) [ 154.748605] Filesystems sync: 0.067 seconds [ 154.787889] Freezing user space processes [ 154.789226] Freezing user space processes completed (elapsed 0.001 seconds) [ 154.789228] OOM killer disabled. [ 154.789229] Freezing remaining freezable tasks [ 154.790188] Freezing remaining freezable tasks completed (elapsed 0.000 seconds) [ 154.790226] printk: Suspending console(s) (use no_console_suspend to debug) [ 157.128832] PM: suspend devices took 2.339 seconds [ 157.159547] ACPI: EC: interrupt blocked [ 157.253246] ACPI: PM: Preparing to enter system sleep state S3 [ 157.257073] ACPI: EC: event blocked [ 157.257074] ACPI: EC: EC stopped [ 157.257074] ACPI: PM: Saving platform NVS memory [ 157.257138] Disabling non-boot CPUs ... [ 157.258702] smpboot: CPU 1 is now offline [ 157.260760] smpboot: CPU 2 is now offline [ 157.262785] smpboot: CPU 3 is now offline [ 157.264799] smpboot: CPU 4 is now offline [ 157.266811] smpboot: CPU 5 is now offline [ 157.268810] smpboot: CPU 6 is now offline [ 157.271334] smpboot: CPU 7 is now offline [ 157.273240] smpboot: CPU 8 is now offline [ 157.275602] smpboot: CPU 9 is now offline [ 157.277430] smpboot: CPU 10 is now offline [ 157.279271] smpboot: CPU 11 is now offline [ 157.281091] smpboot: CPU 12 is now offline [ 157.282847] smpboot: CPU 13 is now offline [ 157.284620] smpboot: CPU 14 is now offline [ 157.286428] smpboot: CPU 15 is now offline [ 157.291142] ACPI: PM: Low-level resume complete [ 157.291212] ACPI: EC: EC started [ 157.291213] ACPI: PM: Restoring platform NVS memory [ 157.292556] Enabling non-boot CPUs ... [ 157.292599] x86: Booting SMP configuration: [ 157.292599] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 157.294208] CPU1 is up [ 157.294230] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 157.295726] CPU2 is up [ 157.295744] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 157.297286] CPU3 is up [ 157.297304] smpboot: Booting Node 0 Processor 4 APIC 0x8 [ 157.298839] CPU4 is up [ 157.298857] smpboot: Booting Node 0 Processor 5 APIC 0xa [ 157.300396] CPU5 is up [ 157.300414] smpboot: Booting Node 0 Processor 6 APIC 0xc [ 157.301979] CPU6 is up [ 157.301997] smpboot: Booting Node 0 Processor 7 APIC 0xe [ 157.303596] CPU7 is up [ 157.303614] smpboot: Booting Node 0 Processor 8 APIC 0x1 [ 157.304500] CPU8 is up [ 157.304524] smpboot: Booting Node 0 Processor 9 APIC 0x3 [ 157.305233] CPU9 is up [ 157.305254] smpboot: Booting Node 0 Processor 10 APIC 0x5 [ 157.305964] CPU10 is up [ 157.305982] smpboot: Booting Node 0 Processor 11 APIC 0x7 [ 157.306703] CPU11 is up [ 157.306723] smpboot: Booting Node 0 Processor 12 APIC 0x9 [ 157.307453] CPU12 is up [ 157.307473] smpboot: Booting Node 0 Processor 13 APIC 0xb [ 157.308209] CPU13 is up [ 157.308227] smpboot: Booting Node 0 Processor 14 APIC 0xd [ 157.308987] CPU14 is up [ 157.309006] smpboot: Booting Node 0 Processor 15 APIC 0xf [ 157.309793] CPU15 is up [ 157.315293] ACPI: PM: Waking up from system sleep state S3 [ 157.453139] ACPI: EC: interrupt unblocked [ 158.842695] ACPI: EC: event unblocked [ 158.857975] xhci_hcd 0000:01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 158.857978] usb usb3: root hub lost power or was reset [ 158.857979] usb usb4: root hub lost power or was reset [ 158.865357] xhci_hcd 0000:a5:00.0: xHC error in resume, USBSTS 0x401, Reinit [ 158.865359] usb usb7: root hub lost power or was reset [ 158.865360] usb usb8: root hub lost power or was reset [ 158.865361] xhci_hcd 0000:3b:00.0: xHC error in resume, USBSTS 0x401, Reinit [ 158.865364] usb usb5: root hub lost power or was reset [ 158.865365] usb usb6: root hub lost power or was reset [ 158.888216] nvme nvme0: 8/0/0 default/read/poll queues [ 158.897898] i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is disabled/in DSI mode with an ungated DDI clock, gate it [ 158.897905] i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it [ 158.897918] i915 0000:00:02.0: [drm] [ENCODER:113:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it [ 158.897926] i915 0000:00:02.0: [drm] [ENCODER:120:DDI D/PHY D] is disabled/in DSI mode with an ungated DDI clock, gate it [ 159.077180] usb 1-5: reset high-speed USB device number 3 using xhci_hcd [ 159.148805] nvme nvme1: 8/0/0 default/read/poll queues [ 159.152472] nvme nvme1: Ignoring bogus Namespace Identifiers [ 159.345916] ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done OK, num_hid_devices=1 [ 160.091100] PM: resume devices took 1.249 seconds [ 160.091353] pcieport 0000:00:1c.0: PCI bridge to [bus 04] [ 160.091376] pcieport 0000:00:1c.0: bridge window [mem 0xd2100000-0xd21fffff] [ 160.091512] pci_bus 0000:07: Allocating resources [ 160.091539] pci_bus 0000:3b: Allocating resources [ 160.091666] pci_bus 0000:71: Allocating resources [ 160.091683] pci_bus 0000:a5: Allocating resources [ 160.091733] pcieport 0000:00:1b.0: PCI bridge to [bus 02] [ 160.091767] pcieport 0000:00:1b.0: bridge window [mem 0xd2300000-0xd23fffff] [ 160.092324] OOM killer enabled. [ 160.092328] Restarting tasks ... [ 160.092372] pcieport 0000:00:1b.4: PCI bridge to [bus 03] [ 160.092384] pcieport 0000:00:1b.4: bridge window [mem 0xd2200000-0xd22fffff] [ 160.092508] pci_bus 0000:07: Allocating resources [ 160.092537] pci_bus 0000:3b: Allocating resources [ 160.092654] pci_bus 0000:71: Allocating resources [ 160.092676] pci_bus 0000:a5: Allocating resources [ 160.093955] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915]) [ 160.094840] done. [ 160.094852] random: crng reseeded on system resumption [ 160.156809] PM: suspend exit [ 160.602409] rfkill: input handler disabled [ 160.614078] evdi: [I] (card0) Opened by Task 1047 (systemd-logind) of process 1047 (systemd-logind) [ 160.614398] evdi: [I] (card1) Opened by Task 1047 (systemd-logind) of process 1047 (systemd-logind) [ 160.614706] evdi: [I] (card2) Opened by Task 1047 (systemd-logind) of process 1047 (systemd-logind) [ 160.615054] evdi: [I] (card3) Opened by Task 1047 (systemd-logind) of process 1047 (systemd-logind) [ 160.899867] evdi: [I] (card0) Closed by Task 9900 (gnome-shell) of process 9900 (gnome-shell) [ 160.900106] evdi: [I] (card1) Closed by Task 9900 (gnome-shell) of process 9900 (gnome-shell) [ 160.900328] evdi: [I] (card2) Closed by Task 9900 (gnome-shell) of process 9900 (gnome-shell) [ 160.900548] evdi: [I] (card3) Closed by Task 9900 (gnome-shell) of process 9900 (gnome-shell) [ 161.974794] hid-sensor-hub 001F:8087:0AC2.0003: timeout waiting for response from ISHTP device [ 164.371697] wlp0s20f3: authenticate with ba:15:a2:3b:f0:cd [ 164.375487] wlp0s20f3: send auth to ba:15:a2:3b:f0:cd (try 1/3) [ 164.426685] wlp0s20f3: authenticated [ 164.427235] wlp0s20f3: associate with ba:15:a2:3b:f0:cd (try 1/3) [ 164.429289] wlp0s20f3: RX AssocResp from ba:15:a2:3b:f0:cd (capab=0x1011 status=0 aid=18) [ 164.439928] wlp0s20f3: associated [ 164.464341] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready [ 164.490304] wlp0s20f3: Limiting TX power to 23 (23 - 0) dBm as advertised by ba:15:a2:3b:f0:cd [ 168.479291] wlp0s20f3: deauthenticating from ba:15:a2:3b:f0:cd by local choice (Reason: 3=DEAUTH_LEAVING) [ 168.744191] rfkill: input handler enabled [ 168.890774] PM: suspend entry (deep) [ 168.918075] Filesystems sync: 0.027 seconds [ 168.918425] Freezing user space processes [ 168.925369] Freezing user space processes completed (elapsed 0.006 seconds) [ 168.925372] OOM killer disabled. [ 168.925372] Freezing remaining freezable tasks [ 168.926288] Freezing remaining freezable tasks completed (elapsed 0.000 seconds) [ 168.926326] printk: Suspending console(s) (use no_console_suspend to debug) [ 169.701793] PM: suspend devices took 0.775 seconds [ 169.732802] ACPI: EC: interrupt blocked [ 169.827656] ACPI: PM: Preparing to enter system sleep state S3 [ 169.831557] ACPI: EC: event blocked [ 169.831558] ACPI: EC: EC stopped [ 169.831558] ACPI: PM: Saving platform NVS memory [ 169.831625] Disabling non-boot CPUs ... [ 169.833190] smpboot: CPU 1 is now offline [ 169.835170] smpboot: CPU 2 is now offline [ 169.837215] smpboot: CPU 3 is now offline [ 169.839246] smpboot: CPU 4 is now offline [ 169.841286] smpboot: CPU 5 is now offline [ 169.843159] smpboot: CPU 6 is now offline [ 169.845093] smpboot: CPU 7 is now offline [ 169.847699] smpboot: CPU 8 is now offline [ 169.849542] smpboot: CPU 9 is now offline [ 169.851228] smpboot: CPU 10 is now offline [ 169.853015] smpboot: CPU 11 is now offline [ 169.854829] smpboot: CPU 12 is now offline [ 169.856342] smpboot: CPU 13 is now offline [ 169.857822] smpboot: CPU 14 is now offline [ 169.859337] smpboot: CPU 15 is now offline [ 169.863859] ACPI: PM: Low-level resume complete [ 169.863928] ACPI: EC: EC started [ 169.863929] ACPI: PM: Restoring platform NVS memory [ 169.865298] Enabling non-boot CPUs ... [ 169.865327] x86: Booting SMP configuration: [ 169.865328] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 169.866960] CPU1 is up [ 169.866983] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 169.868542] CPU2 is up [ 169.868561] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 169.870108] CPU3 is up [ 169.870125] smpboot: Booting Node 0 Processor 4 APIC 0x8 [ 169.871683] CPU4 is up [ 169.871702] smpboot: Booting Node 0 Processor 5 APIC 0xa [ 169.873268] CPU5 is up [ 169.873285] smpboot: Booting Node 0 Processor 6 APIC 0xc [ 169.874877] CPU6 is up [ 169.874895] smpboot: Booting Node 0 Processor 7 APIC 0xe [ 169.876521] CPU7 is up [ 169.876539] smpboot: Booting Node 0 Processor 8 APIC 0x1 [ 169.877440] CPU8 is up [ 169.877464] smpboot: Booting Node 0 Processor 9 APIC 0x3 [ 169.878188] CPU9 is up [ 169.878206] smpboot: Booting Node 0 Processor 10 APIC 0x5 [ 169.878934] CPU10 is up [ 169.878953] smpboot: Booting Node 0 Processor 11 APIC 0x7 [ 169.879695] CPU11 is up [ 169.879716] smpboot: Booting Node 0 Processor 12 APIC 0x9 [ 169.880469] CPU12 is up [ 169.880488] smpboot: Booting Node 0 Processor 13 APIC 0xb [ 169.881250] CPU13 is up [ 169.881269] smpboot: Booting Node 0 Processor 14 APIC 0xd [ 169.882044] CPU14 is up [ 169.882062] smpboot: Booting Node 0 Processor 15 APIC 0xf [ 169.882862] CPU15 is up [ 169.888342] ACPI: PM: Waking up from system sleep state S3 [ 170.026449] ACPI: EC: interrupt unblocked [ 171.391781] ACPI: EC: event unblocked [ 171.406433] xhci_hcd 0000:01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 171.406439] usb usb3: root hub lost power or was reset [ 171.406440] usb usb4: root hub lost power or was reset [ 171.412192] xhci_hcd 0000:3b:00.0: xHC error in resume, USBSTS 0x401, Reinit [ 171.412194] usb usb5: root hub lost power or was reset [ 171.412195] usb usb6: root hub lost power or was reset [ 171.412311] xhci_hcd 0000:a5:00.0: xHC error in resume, USBSTS 0x401, Reinit [ 171.412313] usb usb7: root hub lost power or was reset [ 171.412314] usb usb8: root hub lost power or was reset [ 171.437341] nvme nvme0: 8/0/0 default/read/poll queues [ 171.447562] i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is disabled/in DSI mode with an ungated DDI clock, gate it [ 171.447576] i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it [ 171.447591] i915 0000:00:02.0: [drm] [ENCODER:113:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it [ 171.447606] i915 0000:00:02.0: [drm] [ENCODER:120:DDI D/PHY D] is disabled/in DSI mode with an ungated DDI clock, gate it [ 171.625799] usb 1-5: reset high-speed USB device number 3 using xhci_hcd [ 171.697529] nvme nvme1: 8/0/0 default/read/poll queues [ 171.701252] nvme nvme1: Ignoring bogus Namespace Identifiers [ 171.887049] ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done OK, num_hid_devices=1 [ 172.654499] PM: resume devices took 1.262 seconds [ 172.654629] pcieport 0000:00:1c.0: PCI bridge to [bus 04] [ 172.654642] pcieport 0000:00:1c.0: bridge window [mem 0xd2100000-0xd21fffff] [ 172.654736] pci_bus 0000:07: Allocating resources [ 172.654754] pci_bus 0000:3b: Allocating resources [ 172.654828] pci_bus 0000:71: Allocating resources [ 172.654843] pci_bus 0000:a5: Allocating resources [ 172.654871] pcieport 0000:00:1b.0: PCI bridge to [bus 02] [ 172.654877] pcieport 0000:00:1b.0: bridge window [mem 0xd2300000-0xd23fffff] [ 172.655356] pcieport 0000:00:1b.4: PCI bridge to [bus 03] [ 172.655362] pcieport 0000:00:1b.4: bridge window [mem 0xd2200000-0xd22fffff] [ 172.655439] OOM killer enabled. [ 172.655440] Restarting tasks ... [ 172.655455] pci_bus 0000:07: Allocating resources [ 172.655482] pci_bus 0000:3b: Allocating resources [ 172.655587] pci_bus 0000:71: Allocating resources [ 172.655616] pci_bus 0000:a5: Allocating resources [ 172.656963] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915]) [ 172.657264] done. [ 172.657273] random: crng reseeded on system resumption [ 172.720583] PM: suspend exit [ 173.153988] rfkill: input handler disabled [ 173.157014] evdi: [I] (card0) Opened by Task 1047 (systemd-logind) of process 1047 (systemd-logind) [ 173.157284] evdi: [I] (card1) Opened by Task 1047 (systemd-logind) of process 1047 (systemd-logind) [ 173.157518] evdi: [I] (card2) Opened by Task 1047 (systemd-logind) of process 1047 (systemd-logind) [ 173.157844] evdi: [I] (card3) Opened by Task 1047 (systemd-logind) of process 1047 (systemd-logind) [ 173.466641] evdi: [I] (card0) Closed by Task 9900 (gnome-shell) of process 9900 (gnome-shell) [ 173.466934] evdi: [I] (card1) Closed by Task 9900 (gnome-shell) of process 9900 (gnome-shell) [ 173.467157] evdi: [I] (card2) Closed by Task 9900 (gnome-shell) of process 9900 (gnome-shell) [ 173.467370] evdi: [I] (card3) Closed by Task 9900 (gnome-shell) of process 9900 (gnome-shell) [ 174.523798] hid-sensor-hub 001F:8087:0AC2.0003: timeout waiting for response from ISHTP device [ 176.903992] wlp0s20f3: authenticate with ba:15:a2:3b:f0:cd [ 176.907952] wlp0s20f3: send auth to ba:15:a2:3b:f0:cd (try 1/3) [ 176.954964] wlp0s20f3: authenticated [ 176.955544] wlp0s20f3: associate with ba:15:a2:3b:f0:cd (try 1/3) [ 176.957302] wlp0s20f3: RX AssocResp from ba:15:a2:3b:f0:cd (capab=0x1011 status=0 aid=24) [ 176.966294] wlp0s20f3: associated [ 176.997378] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready [ 176.998662] wlp0s20f3: Limiting TX power to 23 (23 - 0) dBm as advertised by ba:15:a2:3b:f0:cd

might be an issue with NVram because now the touchscreen does not work on wake and there is a strange effect where the logo shows, then gets garbeled and another sleep wake action seems to be needed. I will try to post again when that is fixed, but thought it might be useful to share anyway. This sing of life ( logo ) has something to do with the issue too I believe. Would be fantastic to get to the bottom of this :)!

VGerris commented 12 months ago

here is the output of dmesg after an NVram reset. Sign of life logo was on in Bios, after disabling that the behaviour disappeared and I get a 'normal S3 sleep' on this XPS 9700:

[ 15.421439] evdi: [I] (card3) Closed by Task 3099 (gnome-shell) of process 3099 (gnome-shell) [ 51.024170] wlp0s20f3: deauthenticating from ba:15:a2:3b:f0:cd by local choice (Reason: 3=DEAUTH_LEAVING) [ 51.472653] ACPI: button: The lid device is not compliant to SW_LID. [ 52.401117] rfkill: input handler enabled [ 52.560668] PM: suspend entry (deep) [ 52.587398] Filesystems sync: 0.026 seconds [ 52.630800] Freezing user space processes [ 52.632367] Freezing user space processes completed (elapsed 0.001 seconds) [ 52.632369] OOM killer disabled. [ 52.632370] Freezing remaining freezable tasks [ 52.633543] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) [ 52.633583] printk: Suspending console(s) (use no_console_suspend to debug) [ 54.924441] PM: suspend devices took 2.290 seconds [ 54.955116] ACPI: EC: interrupt blocked [ 55.049460] ACPI: PM: Preparing to enter system sleep state S3 [ 55.056258] ACPI: EC: event blocked [ 55.056261] ACPI: EC: EC stopped [ 55.056262] ACPI: PM: Saving platform NVS memory [ 55.056380] Disabling non-boot CPUs ... [ 55.058696] smpboot: CPU 1 is now offline [ 55.062067] smpboot: CPU 2 is now offline [ 55.065331] smpboot: CPU 3 is now offline [ 55.068563] smpboot: CPU 4 is now offline [ 55.073031] smpboot: CPU 5 is now offline [ 55.075918] smpboot: CPU 6 is now offline [ 55.078622] smpboot: CPU 7 is now offline [ 55.083148] smpboot: CPU 8 is now offline [ 55.085881] smpboot: CPU 9 is now offline [ 55.088468] smpboot: CPU 10 is now offline [ 55.091176] smpboot: CPU 11 is now offline [ 55.093705] smpboot: CPU 12 is now offline [ 55.096453] smpboot: CPU 13 is now offline [ 55.098945] smpboot: CPU 14 is now offline [ 55.101456] smpboot: CPU 15 is now offline [ 55.106442] ACPI: PM: Low-level resume complete [ 55.106512] ACPI: EC: EC started [ 55.106512] ACPI: PM: Restoring platform NVS memory [ 55.107911] Enabling non-boot CPUs ... [ 55.107940] x86: Booting SMP configuration: [ 55.107940] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 55.109601] CPU1 is up [ 55.109624] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 55.111159] CPU2 is up [ 55.111180] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 55.112711] CPU3 is up [ 55.112729] smpboot: Booting Node 0 Processor 4 APIC 0x8 [ 55.114275] CPU4 is up [ 55.114293] smpboot: Booting Node 0 Processor 5 APIC 0xa [ 55.115839] CPU5 is up [ 55.115856] smpboot: Booting Node 0 Processor 6 APIC 0xc [ 55.117444] CPU6 is up [ 55.117462] smpboot: Booting Node 0 Processor 7 APIC 0xe [ 55.119066] CPU7 is up [ 55.119084] smpboot: Booting Node 0 Processor 8 APIC 0x1 [ 55.119937] CPU8 is up [ 55.119962] smpboot: Booting Node 0 Processor 9 APIC 0x3 [ 55.120669] CPU9 is up [ 55.120687] smpboot: Booting Node 0 Processor 10 APIC 0x5 [ 55.121402] CPU10 is up [ 55.121421] smpboot: Booting Node 0 Processor 11 APIC 0x7 [ 55.122156] CPU11 is up [ 55.122175] smpboot: Booting Node 0 Processor 12 APIC 0x9 [ 55.122920] CPU12 is up [ 55.122939] smpboot: Booting Node 0 Processor 13 APIC 0xb [ 55.123687] CPU13 is up [ 55.123709] smpboot: Booting Node 0 Processor 14 APIC 0xd [ 55.124475] CPU14 is up [ 55.124493] smpboot: Booting Node 0 Processor 15 APIC 0xf [ 55.125279] CPU15 is up [ 55.130743] ACPI: PM: Waking up from system sleep state S3 [ 55.264226] ACPI: EC: interrupt unblocked [ 56.703308] ACPI: EC: event unblocked [ 56.714124] xhci_hcd 0000:a5:00.0: xHC error in resume, USBSTS 0x401, Reinit [ 56.714127] usb usb7: root hub lost power or was reset [ 56.714129] usb usb8: root hub lost power or was reset [ 56.714217] xhci_hcd 0000:3b:00.0: xHC error in resume, USBSTS 0x401, Reinit [ 56.714220] usb usb5: root hub lost power or was reset [ 56.714221] usb usb6: root hub lost power or was reset [ 56.724106] xhci_hcd 0000:01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 56.724108] usb usb3: root hub lost power or was reset [ 56.724109] usb usb4: root hub lost power or was reset [ 56.738907] nvme nvme0: 8/0/0 default/read/poll queues [ 56.748859] i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is disabled/in DSI mode with an ungated DDI clock, gate it [ 56.750857] i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it [ 56.756491] i915 0000:00:02.0: [drm] [ENCODER:113:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it [ 56.761792] i915 0000:00:02.0: [drm] [ENCODER:120:DDI D/PHY D] is disabled/in DSI mode with an ungated DDI clock, gate it [ 56.937142] usb 1-5: reset high-speed USB device number 3 using xhci_hcd [ 56.998720] nvme nvme1: 8/0/0 default/read/poll queues [ 57.002445] nvme nvme1: Ignoring bogus Namespace Identifiers [ 57.197917] ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done OK, num_hid_devices=1 [ 57.961341] PM: resume devices took 1.258 seconds [ 57.961459] pcieport 0000:00:1c.0: PCI bridge to [bus 04] [ 57.961469] pcieport 0000:00:1c.0: bridge window [mem 0xd2100000-0xd21fffff] [ 57.961567] pci_bus 0000:07: Allocating resources [ 57.961584] pci_bus 0000:3b: Allocating resources [ 57.961658] pci_bus 0000:71: Allocating resources [ 57.961673] pci_bus 0000:a5: Allocating resources [ 57.961698] pcieport 0000:00:1b.0: PCI bridge to [bus 02] [ 57.961701] pcieport 0000:00:1b.0: bridge window [mem 0xd2300000-0xd23fffff] [ 57.962226] pcieport 0000:00:1b.4: PCI bridge to [bus 03] [ 57.962232] pcieport 0000:00:1b.4: bridge window [mem 0xd2200000-0xd22fffff] [ 57.962332] pci_bus 0000:07: Allocating resources [ 57.962350] pci_bus 0000:3b: Allocating resources [ 57.962443] OOM killer enabled. [ 57.962444] Restarting tasks ... [ 57.962450] pci_bus 0000:71: Allocating resources [ 57.962476] pci_bus 0000:a5: Allocating resources [ 57.963857] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915]) [ 57.964674] done. [ 57.964686] random: crng reseeded on system resumption [ 58.035036] PM: suspend exit [ 58.457046] rfkill: input handler disabled [ 58.472042] evdi: [I] (card0) Opened by Task 1053 (systemd-logind) of process 1053 (systemd-logind) [ 58.472397] evdi: [I] (card1) Opened by Task 1053 (systemd-logind) of process 1053 (systemd-logind) [ 58.472652] evdi: [I] (card2) Opened by Task 1053 (systemd-logind) of process 1053 (systemd-logind) [ 58.472925] evdi: [I] (card3) Opened by Task 1053 (systemd-logind) of process 1053 (systemd-logind) [ 58.768951] evdi: [I] (card0) Closed by Task 3099 (gnome-shell) of process 3099 (gnome-shell) [ 58.769256] evdi: [I] (card1) Closed by Task 3099 (gnome-shell) of process 3099 (gnome-shell) [ 58.769482] evdi: [I] (card2) Closed by Task 3099 (gnome-shell) of process 3099 (gnome-shell) [ 58.769700] evdi: [I] (card3) Closed by Task 3099 (gnome-shell) of process 3099 (gnome-shell) [ 59.835012] hid-sensor-hub 001F:8087:0AC2.0003: timeout waiting for response from ISHTP device [ 62.203753] ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-110) [ 62.227738] wlp0s20f3: authenticate with ba:15:a2:3b:f0:cd [ 62.233896] wlp0s20f3: send auth to ba:15:a2:3b:f0:cd (try 1/3) [ 62.288376] wlp0s20f3: authenticated [ 62.288748] wlp0s20f3: associate with ba:15:a2:3b:f0:cd (try 1/3) [ 62.291140] wlp0s20f3: RX AssocResp from ba:15:a2:3b:f0:cd (capab=0x1011 status=0 aid=10) [ 62.300736] wlp0s20f3: associated [ 62.336591] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready [ 62.374559] wlp0s20f3: Limiting TX power to 23 (23 - 0) dBm as advertised by ba:15:a2:3b:f0:cd

The touchscreen stops working after the wake, which is something I read about happening for other models. That does not happen on MacOS last time I checked. Looked forward to any findings you may do!

jkbuha commented 12 months ago

Can you attach here the current (linux) DSDT.aml for the 9700?

sudo cat /sys/firmware/acpi/tables/DSDT > DSDT.aml

VGerris commented 12 months ago

DSDT-xps-9700.zip

sure, there you go.

VGerris commented 11 months ago

hi, any updates ? does anyone know how I could find what changes on the ACPI level when the power is plugged/unplugged ? With that I could look at the methods of the BIOS file to see where such a change can affect the sleep. Thank you.

jkbuha commented 11 months ago

Have managed to replicate (successfully) sleep/wake cycles on the 9520 but no amount of patching on the 9500 ACPI tables (so far) seems to revive the S3 sleep cycle. However there’s some degree of success with S4 sleep (hibernate), I can get the 9500 to resume hibernation but it seems to crash shortly thereafter, which is likely either (a) some RTC variable patch I need to amend or (b) an NVRAM area of memory

VGerris commented 11 months ago

hi, that is really good news, I have actually tried hibernation via MacOS but it suffered from that problem : reboot or hang. That does not happen in Linux I believe but I might be wrongly remembering. Can you explain how you do this work of testing and with what tools? Then I might be able to join the effort when time allows. Would already be a great win to have hibernate working. Also note that the dump I shared was from the XPS 9700 ans has working S3 sleep when the power is plugged in :). Thanks and looking forward to nail this !

jkbuha commented 11 months ago

OK I think I've finally fixed hibernation (S4) sleep on the XPS 9500 and 9520. It involved excluding a few registers from the RTC banks, and unlocking some IFR variables. I'll post a full EFI when I get some confirmation from your end first. Could you please try the following:

UEFI IFR variables:

setup_var PchSetup 0x16 00 (RTC Memory Lock ->Disabled) setup_var CpuSetup 0x3E 00 (CFG Lock ->Disabled)

OpenCore (0.9.5) Add Kexts RTCMemoryFixup.kext HibernationFixup.kext

HibernateMode -> NVRAM DiscardHibernateMap -> True

boot-args: hbfx-ahbm=1 -hbfx-disable-patch-pci rtcfx_exclude=A0-A7

macOS

pmset -a hibernatemode 25 pmset -a standby 1 pmset -a standbydelaylow 1 pmset -a standbydelayhigh 1

VGerris commented 11 months ago

That sounds promising. I have CFG unlocked already. I use a slightly different command because I never found the one to execute the one you show, like so: setup_var_cv CpuSetup 0x3e 0x01 0x00 setup_var_cv CpuSetup 0xda 0x01 0x00 So I ran for PchSetup : setup_var_cv PchSetup 0x16 0x01 0x00 I got some confirmation it worked.

Upgraded OC from 093 to 095 and to latest Lilu and WEG (Ventura 13.5.2). Enabled HibernateFixup and RTCMemoryFixup.

HibernateMode -> NVRAM DiscardHibernateMap -> True in config

It looked promising : sleep entered and stayed. After opening screen no response, then when pressing power button the bootloader and when booting a black screen and a hang ( no CAPS key response ). This looks like what I had pulle off before, but then it often rebooted. I wanted to fo the way you're taking here but have no idea how :). So glad you took it. Still happy to learn on how you approach this? Then I can help better.

Does this work for you on the 9500? would love to try the EFI in that case.

For completeness, my boot args tried : org: keepsyms=1 -wegdbg -igfxblr -lilubetaall -wegnoegpu agdpmod=vit9696 hbfx-ahbm=65 -hbfx-disable-patch-pci -hbfx-dump-nvram igfxonln=1 forceRenderStandby=0 -hbfx-beta darkwake=0 - here I had the HibernateMode set to Auto and discard to false to get the black screen.

keepsyms=1 -wegdbg -igfxblr -lilubetaall -wegnoegpu agdpmod=vit9696 hbfx-ahbm=1 -hbfxdbg -hbfx-disable-patch-pci -noDC9 -nodisplaysleepDC6 igfxonln=1 forceRenderStandby=0 rtcfx_exclude=A0-A7 -hbfx-beta darkwake=0

keepsyms=1 -wegdbg -igfxblr -lilubetaall -wegnoegpu agdpmod=vit9696 hbfx-ahbm=65 -hbfxdbg -hbfx-disable-patch-pci -noDC9 -nodisplaysleepDC6 igfxonln=1 forceRenderStandby=0 rtcfx_exclude=A0-A7 -hbfx-beta

keepsyms=1 -wegdbg -igfxblr -lilubetaall -wegnoegpu hbfx-ahbm=1 -hbfxdbg -hbfx-disable-patch-pci -noDC9 -nodisplaysleepDC6 igfxonln=1 forceRenderStandby=0 rtcfx_exclude=A0-A7 -hbfx-beta

It looks like progress to me, please let me know what I can study to help, or perhaps share EFI for testing? Thank you very much!

jkbuha commented 11 months ago

Sure, here's the link to my repo:

https://github.com/jkbuha/XPS-9500-IceLake-OpenCore

It's based on my existing XPS 9520 repo and some further ACPI optimisation for the XPS 9500. As it stands S4 works perfectly on both machines, which means that if this EFI config doesnt work for you it might be due to additional UEFI variables, macOS specific config (I use Monterey) or even hardware (I have the FHD variant, for example).

VGerris commented 11 months ago

Thanks a lot, I will test, investigate and report back. I saw a BIOS update and upgraded to 1.24. I run Ventura ( have run Sonoma Beta successfully vefore too ). I have the version with 4k touch screen it may matter - I do not understand the precise differences in OC for that but I can try to figure that out.

Any hints on how you figured out these registers and how you go about debugging this ? It would be of great help to many I think to understand more about that process to learn.

With S4 working, any plans on taking a look at S3 or for me on how to approach that on the half working XPS 9700 ? And brightness keys :)? Thanks again for sharing, will get back as soon as I have some results.

jkbuha commented 11 months ago

So a few notes+caveats for my setup:

  1. I have downgraded the 9500 Bios to 1.15.1 as it supports undervolting. I have a specific github repo on how to do it, but (a) it's not easy (b) it might brick your machine if not done properly. I would not downgrade the bios for now unless this is the only issue left to try.
  2. What's for sure is that a 4k touchscreen requires a larger framebuffer than a FHD non-touch does, but with my EFI you should at least be restoring hibernation to the previously visible screen. However the hardware used will affect how you hibernate wake. Eg: What's the size of your RAM, what processor do you have, as it may involve writing to additional RTC (or even NVRAM) variables. However if you can hibernate and restart the laptop using my EFI without any Bios/CMOS errors, it means that excluding the A0-A7 RTC registers is working sufficiently well for your setup. It will probably work for the 9700 too with minimal rework.
  3. To debug the registers you need to reverse engineer the UEFI IFR variable list using tools such as UEFITools. There are some good guides on how to do it, for now I wouldn't touch these as you may soft-brick the machine with incorrect settings. I'll optimise them further once a repeatable setup on your machine (and ideally others) is confirmed.
  4. Brightness keys work (with my EFI) with Fn S+B, but I've remapped them to F6+F7 using BetterTouchTool.
  5. Regarding S3 sleep on the 9500, I tried patching some ACPI tables related to EC-triggered events, and I've managed to get the first part of the wake stage working on linux, however there seems to be some incomplete tables that are preventing some of the devices from waking up properly. It can probably be done by someone with (a) better understanding of ACPI events (b) more bandwidth. However, honestly speaking I'm actually happy with a properly working S4 hibernate cycle; the laptop boots in less than 10sec (I thought it was going to be much longer) and uses absolutely no charge when off. You can even set the machine to power up on lid opening and opencore to autorestore a hibernated session, which will speed up the process 1-2sec more.
VGerris commented 11 months ago

hi, thanks for the quick reply and explanation! I will see where I can start, any hints on where the EC parts are missing?

I tried your EFI and it crashed because of the wifi driver, after upgrading that it booted properly and everything seems to work well. Unfortunately sleep did not, it hung like when using S3. I reapplied the pmset settings as root and upgraded to 13.6 too because pmset kept showing softwarenotify... as preventing sleep. After NVram reset I got similar behavior as before - sleep works, wake does not trigger on lid but with power button ( totally fine for me ) but at boot it halts on black screen. This time it also rebooted after a few seconds and I caught the panic, perhaps something useful :

panic(cpu 0 caller 0xffffff800ecd01ac): Hibernate restore error e00002bc @IOHibernateIO.cpp:2694
Panicked task 0xffffff95034f1258: 198 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff99cf6f8598, Frame : Return Address
0xfffffffc00493800 : 0xffffff800e67205d mach_kernel : _handle_debugger_trap + 0x4ad
0xfffffffc00493850 : 0xffffff800e7c6144 mach_kernel : _kdp_i386_trap + 0x114
0xfffffffc00493890 : 0xffffff800e7b5c57 mach_kernel : _kernel_trap + 0x3b7
0xfffffffc004938e0 : 0xffffff800e612951 mach_kernel : _return_from_trap + 0xc1
0xfffffffc00493900 : 0xffffff800e67233d mach_kernel : _DebuggerTrapWithState + 0x5d
0xfffffffc004939f0 : 0xffffff800e6719e7 mach_kernel : _panic_trap_to_debugger + 0x1a7
0xfffffffc00493a50 : 0xffffff800eddb32b mach_kernel : _panic + 0x84
0xfffffffc00493b40 : 0xffffff800ecd01ac mach_kernel : _hibernate_machine_init + 0x12cc
0xfffffffc00493c00 : 0xffffff800e7c43b7 mach_kernel : _ml_hibernate_active_post + 0x27
0xfffffffc00493c10 : 0xffffff800ed3772a mach_kernel : _IOCPURunPlatformActiveActions + 0x6a
0xfffffffc00493c40 : 0xffffff800e7c3b62 mach_kernel : _acpi_sleep_kernel + 0x2b2
0xfffffffc00493c90 : 0xffffff800f574f92 com.apple.driver.AppleACPIPlatform : __ZN23AppleACPIPlatformExpert13sleepPlatformEv + 0x20e
0xfffffffc00493ce0 : 0xffffff800f5793b5 com.apple.driver.AppleACPIPlatform : __ZN12AppleACPICPU7haltCPUEv + 0x75
0xfffffffc00493d00 : 0xffffff800ed37325 mach_kernel : __Z16IOCPUSleepKernelv + 0x1b5
0xfffffffc00493d50 : 0xffffff800ed88774 mach_kernel : __ZN14IOPMrootDomain15powerChangeDoneEm + 0xac4
0xfffffffc00493dd0 : 0xffffff800ecf97c9 mach_kernel : __ZN9IOService8all_doneEv + 0x739
0xfffffffc00493e40 : 0xffffff800ecf65a6 mach_kernel : __ZN9IOService23actionPMWorkQueueInvokeEP11IOPMRequestP13IOPMWorkQueue + 0x876
0xfffffffc00493e90 : 0xffffff800ecf3cc0 mach_kernel : __ZN13IOPMWorkQueue17checkRequestQueueEP11queue_entryPb + 0x90
0xfffffffc00493ee0 : 0xffffff800ecf3b6a mach_kernel : __ZN13IOPMWorkQueue12checkForWorkEv + 0xca
0xfffffffc00493f20 : 0xffffff800ed120be mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x12e
0xfffffffc00493f60 : 0xffffff800ed11707 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x37
0xfffffffc00493fa0 : 0xffffff800e61219e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.driver.AppleACPIPlatform(6.1)[079C50B9-FCFD-3C4C-8BC4-3CF9DD26F27A]@0xffffff800f569000->0xffffff800f5e0fff
            dependency: com.apple.driver.AppleSMC(3.1.9)[DD55DA6A-679A-3797-947C-0B50B7B5B659]@0xffffff800fcde000->0xffffff800fcfafff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[D342E754-A422-3F44-BFFB-DEE93F6723BC]@0xffffff8010c3c000->0xffffff8010c3dfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[F11A1D9C-398D-3933-94D6-9539D3B7B1FD]@0xffffff80110ac000->0xffffff80110ddfff

Process name corresponding to current thread (0xffffff99cf6f8598): kernel_task
Boot args: -v keepsyms=1 kext-dev-mode=1 -igfxblr hbfx-ahbm=3 rtcfx_exclude=A0-A7

Mac OS version:
22G120

Kernel version:
Darwin Kernel Version 22.6.0: Fri Sep 15 13:39:52 PDT 2023; root:xnu-8796.141.3.700.8~1/RELEASE_X86_64
Kernel UUID: F75FC53F-FC1A-3AB6-8980-EF66A83DD51D
roots installed: 0
KernelCache slide: 0x000000000e200000
KernelCache base:  0xffffff800e400000
Kernel slide:      0x000000000e2dc000
Kernel text base:  0xffffff800e4dc000
__HIB  text base: 0xffffff800e300000
System model name: MacBookPro16,4 (Mac-A61BADE1FDAD7B05)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 147091209830
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000000223f51c0b5
  Sleep   : 0x0000001f99a0f46d 0x0000000532730b52 0x0000000000000000
  Wake    : 0x0000000000000000 0x00000005dcea05ca 0x0000001f9f267bb1
Compressor Info: 1% of compressed pages limit (OK) and 0% of segments limit (OK) with 2 swapfiles and OK swap space
Zone info:
  Zone map: 0xffffff8035181000 - 0xffffffa035181000
  . PGZ   : 0xffffff8035181000 - 0xffffff8039182000
  . VM    : 0xffffff8039182000 - 0xffffff85054b5000
  . RO    : 0xffffff85054b5000 - 0xffffff869eb1b000
  . GEN0  : 0xffffff869eb1b000 - 0xffffff8b6ae4e000
  . GEN1  : 0xffffff8b6ae4e000 - 0xffffff9037181000
  . GEN2  : 0xffffff9037181000 - 0xffffff95034b4000
  . GEN3  : 0xffffff95034b4000 - 0xffffff99cf7e7000
  . DATA  : 0xffffff99cf7e7000 - 0xffffffa035181000
  Metadata: 0xffffffa8a47a3000 - 0xffffffa8c47a3000
  Bitmaps : 0xffffffa8c47a3000 - 0xffffffa8ca7a3000
  Extra   : 0 - 0

It would be great if it is region related only, any hints are appreciated, like where to look for and regarding S3 what EC parts.

How many RAM do you have and in which config? I can experiment with that ( currently 2x16GB ). I am happy to try and get this to work, basically running your EFI purely with exception of wifi driver ( ventura one ) and then the OS. Thanks again!

[edit] could perhaps be bios settings too, do you have a list of important ones ?[/edit]

VGerris commented 11 months ago

oh, and then the more interesting one even perhaps, you @jkbuha mention an XPS 9520 with this all working, does it mean you got OS X working on a 12th gen laptop ?? Because then I may want one :).

jkbuha commented 11 months ago

Here's my power settings if it helps:

`jkbuha@MacBook-Pro ~ % pmset -g

System-wide power settings:

Currently in use:

standbydelaylow 1

standby 1

halfdim 1

hibernatefile /var/vm/sleepimage

proximitywake 0

powernap 0

gpuswitch 0

disksleep 10

standbydelayhigh 1

sleep 1 (sleep prevented by Intel Power Gadget)

hibernatemode 25

ttyskeepawake 1

displaysleep 15

tcpkeepalive 0

highstandbythreshold 50

lowpowermode 0

lidwake 1

jkbuha@MacBook-Pro ~ %

`

I'm on 16GB (8x2GB) but have ordered a 32GB kit to see if it still works. Obvious things first - is the swapfile present and constantly updating (/var/vm/swapfile)?

Sounds like it's Ventura-specific though, as AppleACPIPlatform is crashing on restore. What CPU are you using; is it the i7-10750 (if not you'll need to replace it with your specific CPUFriend + Data)

BIOS settings-wise, I dont recall exactly what's been changed but I'll see if I can obtain some form of dump/delta from the default settings.

And yes, I have managed to make the XPS 9520 work perfectly (with an eGPU obvs as macOS doesnt support Iris Xe, check out my github for more info)

VGerris commented 11 months ago

Thanks for sharing! I will try with 2x 8, I have 2x 32 usually. I have an i7-10875 so I'll look at that ( think I didn't use CPUfriend before or reused one I found ). BIOS settings may help, or perhaps it is just your BIOS version. I removed the sleep image once and at boot I saw the loging screen but then it rebooted - so looked close and way further than I ever got :).

Regarding your BIOS choice, I think 1.21 and up until current work with undervolting, I ran voltageshift, you need to unlock this MSR register you showed and I had one line different there which may matter: setup_var_cv CpuSetup 0xda 0x01 0x00 Works on XPS 9700 with latest BIOS too I believe - I had to fiddle with reloading to factory defaults in BIOS for it to work. I'm short on time a bit and compiled voltageshift but on testing machines I have fresh installs so missing some history.

How are your sign of life settings set? mine are off. Thanks again!

jkbuha commented 11 months ago

afaik 9500 bios 1.22 and above cannot be undervolted as MSR registers have been blocked due to plundervolt updates. but in any case it shouldn't affect hibernate/wake logic so I wouldn't bother with it for now.

all sign of life options have been disabled.

good luck!

On Wed, 27 Sep 2023 at 12:39, OpenMinded @.***> wrote:

Thanks for sharing! I will try with 2x 8, I have 2x 32 usually. I have an i7-10875 so I'll look at that ( think I didn't use CPUfriend before or reused one I found ). BIOS settings may help, or perhaps it is just your BIOS version. I removed the sleep image once and at boot I saw the loging screen but then it rebooted - so looked close and way further than I ever got :).

Regarding your BIOS choice, I think 1.21 and up until current work with undervolting, I ran voltageshift, you need to unlock this MSR register you showed and I had one line different there which may matter: setup_var_cv CpuSetup 0xda 0x01 0x00 Works on XPS 9700 with latest BIOS too I believe - I had to fiddle with reloading to factory defaults in BIOS for it to work. I'm short on time a bit and compiled voltageshift but on testing machines I have fresh installs so missing some history.

How are your sign of life settings set? mine are off. Thanks again!

— Reply to this email directly, view it on GitHub https://github.com/zachs78/MacOS-XPS-9500-OpenCore/issues/3#issuecomment-1737224880, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJMMC6RQRYUPQ2O72FMFELX4QF5LANCNFSM4R3ZR2FQ . You are receiving this because you were mentioned.Message ID: @.***>

VGerris commented 11 months ago

It still works on 1.24 BIOS on my 5550 : mac@macs-MacBook-Pro VoltageShift % ./voltageshift_1.25/voltageshift offset -100 -100 -100

VoltageShift offset Tool

Before CPU voltageoffset: 0mv Before GPU voltageoffset: 0mv Before CPU Cache: 0mv

After CPU voltageoffset: -100mv After GPU voltageoffset: -100mv After CPU Cache: -100mv

mac@macs-MacBook-Pro VoltageShift % ./voltageshift_1.25/voltageshift offset -100 -100 -100

VoltageShift offset Tool

Before CPU voltageoffset: -100mv Before GPU voltageoffset: -100mv Before CPU Cache: -100mv

After CPU voltageoffset: -100mv After GPU voltageoffset: -100mv After CPU Cache: -100mv

Regarding the crash, the stacktrace seems to point to a CPU issue indeed, cpu7 I saw, which you do not have and I do. I tried to work around that by limiting to 6 cpus in the BIOS but that didn't work.

Is it the CPUfriend data kext that should be setup proper? Feels we are getting close :).

jkbuha commented 11 months ago

You need to generate your own CPUFriend for your processor.

https://github.com/corpnewt/CPUFriendFriend

On Wed, 27 Sep 2023 at 14:01, OpenMinded @.***> wrote:

It still works on 1.24 BIOS on my 5550 : @. VoltageShift % ./voltageshift_1.25/voltageshift offset -100 -100 -100 VoltageShift offset Tool Before CPU voltageoffset: 0mv Before GPU voltageoffset: 0mv Before CPU Cache: 0mv After CPU voltageoffset: -100mv After GPU voltageoffset: -100mv After CPU Cache: -100mv @. VoltageShift % ./voltageshift_1.25/voltageshift offset -100 -100 -100 VoltageShift offset Tool Before CPU voltageoffset: -100mv Before GPU voltageoffset: -100mv Before CPU Cache: -100mv After CPU voltageoffset: -100mv After GPU voltageoffset: -100mv After CPU Cache: -100mv

Regarding the crash, the stacktrace seems to point to a CPU issue indeed, cpu7 I saw, which you do not have and I do. I tried to work around that by limiting to 6 cpus in the BIOS but that didn't work.

Is it the CPUfriend data kext that should be setup proper? Feels we are getting close :).

— Reply to this email directly, view it on GitHub https://github.com/zachs78/MacOS-XPS-9500-OpenCore/issues/3#issuecomment-1737356064, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJMMC4KNUVP3JA7OUMMWI3X4QPS7ANCNFSM4R3ZR2FQ . You are receiving this because you were mentioned.Message ID: @.***>

VGerris commented 11 months ago

I read that, but it also says may not be needed, is it? I booted without both friend and data enabled, same problem I did notice this which is a similar problem : https://github.com/trulyspinach/SMCAMDProcessor/issues/82 . There is a fix but I don't know it it's related, same error line ( cpu7.... )

Thinking about that sleepimage , reminded me that indeed it wears disk :). If only S3 ....

On Wed, Sep 27, 2023, 18:10 jkbuha @.***> wrote:

You need to generate your own CPUFriend for your processor.

https://github.com/corpnewt/CPUFriendFriend

On Wed, 27 Sep 2023 at 14:01, OpenMinded @.***> wrote:

It still works on 1.24 BIOS on my 5550 : @. VoltageShift % ./voltageshift_1.25/voltageshift offset -100 -100 -100 VoltageShift offset Tool Before CPU voltageoffset: 0mv Before GPU voltageoffset: 0mv Before CPU Cache: 0mv After CPU voltageoffset: -100mv After GPU voltageoffset: -100mv After CPU Cache: -100mv @. VoltageShift % ./voltageshift_1.25/voltageshift offset -100 -100 -100 VoltageShift offset Tool Before CPU voltageoffset: -100mv Before GPU voltageoffset: -100mv Before CPU Cache: -100mv After CPU voltageoffset: -100mv After GPU voltageoffset: -100mv After CPU Cache: -100mv

Regarding the crash, the stacktrace seems to point to a CPU issue indeed, cpu7 I saw, which you do not have and I do. I tried to work around that by limiting to 6 cpus in the BIOS but that didn't work.

Is it the CPUfriend data kext that should be setup proper? Feels we are getting close :).

— Reply to this email directly, view it on GitHub < https://github.com/zachs78/MacOS-XPS-9500-OpenCore/issues/3#issuecomment-1737356064>,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAJMMC4KNUVP3JA7OUMMWI3X4QPS7ANCNFSM4R3ZR2FQ>

. You are receiving this because you were mentioned.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/zachs78/MacOS-XPS-9500-OpenCore/issues/3#issuecomment-1737695740, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGB3COG4TLF6RMTHGNIUSLX4RFWTANCNFSM4R3ZR2FQ . You are receiving this because you commented.Message ID: @.***>

VGerris commented 11 months ago

I tried the following:

I read a bit on that error and it seems related to registers, others posted about it. Perhaps this 8 core CPU needs some more or different ones skipped? It is interesting that sometimes when it wakes, it does show the login screen but it is frozen, but most of the time it is black and it will reboot in both cases after a few seconds.

I am interested in your results with 2x 16 memory. I will try to test on my XPS 9700, it is also an 8 core with 4k touch screen though :). I will also try different mem configs if it works with current EFI, it is slightly different I think.

If you have any ideas on what to try more I am all ears and eyes :)! Thanks again

VGerris commented 11 months ago

Some success :)! Although a bit unexpected:

I am clueless to why this is, I did unlock the same registers and it is the latest BIOS ( I actually ran the update of it before trying the disk ).

So in a way, really great news, although I really really hope there is something to be done for the 5550 :) ? Tested with 64 GB, works too. Awesome job, also 4k touchscreen works on right resolution - I can barely believe it :).

I might use the XPS 9700 for a bit, although I really prefer 15" and less weight :). Perhaps S3 is fixable on hat one, it already works with power plugged in.

Thank you very much again, it is great to have S4 working at least and at least on XPS 9500 / 9700 it seems. I hope other Precision 5550 owners can give this a try and share experience, thank you all!

[edit] oh my, now I stuck the disk back in the 5550 and it worked lol :). No idea why but very happy camper! That is with 32 GB. cheers![/edit] [edit2] It seems the problem with black screen and reboot occurs when the M2 disk is in slot 1, not in slot 2. The XPS 9700 was only tested with slot too, so it may be the issue of the slot 1 hindering proper wake-up. [/edit2]

jkbuha commented 11 months ago

Well done! Try increasing the exclusion range: (rtcfx_exclude=00-FF) and see if it works on the precision.

On Thu, 28 Sep 2023 at 00:13, OpenMinded @.***> wrote:

Some success :)! Although a bit unexpected:

  • Precision 5550 with 64 GB - not working
  • take M2 drive from it and stick in XPS 9700 - success! I think the only changed was : rtcfx_exclude=A0-A7 to rtcfx_exclude=A0-A8 which was left from a change on the 5550 where it did not work. It has 32 GB memory which came from the 5550.

I am clueless to why this is, I did unlock the same registers and it is the latest BIOS ( I actually ran the update of it before trying the disk ).

So in a way, really great news, although I really really hope there is something to be done for the 5550 :) ? Tested with 64 GB, works too. Awesome job, also 4k touchscreen works on right resolution - I can barely believe it :).

I might use the XPS 9700 for a bit, although I really prefer 15" and less weight :). Perhaps S3 is fixable on hat one, it already works with power plugged in.

Thank you very much again, it is great to have S4 working at least and at least on XPS 9500 / 9700 it seems. I hope other Precision 5550 owners can give this a try and share experience, thank you all!

— Reply to this email directly, view it on GitHub https://github.com/zachs78/MacOS-XPS-9500-OpenCore/issues/3#issuecomment-1738225831, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJMMC2YX422DSDPZYYAVFDX4SXJJANCNFSM4R3ZR2FQ . You are receiving this because you were mentioned.Message ID: @.***>

VGerris commented 11 months ago

hi, it does not work in slot 1, and it resets the time :). Did you try switching slots in yours? might have the same problem.

jkbuha commented 11 months ago

Ok, so we've concluded that (a) rtcfx_exclude=A0-A7 works for 9500/5500/9700 (please confirm) (b) there are certain issues with certain drives or positions - please let me know which make/model of M2 drive doesn't work in slot 1.

I have 2 drives: SK Hynix (1TB) and Crucial P3 Plus (2TB) and the machine restores perfectly from S4. But we clearly need to make more tests.

I'm working in some more iterative tests at the moment, and will shortly update my EFI repo.