Dell Latitude 5400 Chrome (Sarien) not sleeping

Support Linux Support
1

Hey, as in title. Following the tutorial, I’ve managed to successfully dual boot CachyOS + Gnome on my Sarien notebook. I can confirm that most of the features, save for the touchscreen, work out of the box, including LTE connectivity.

I’ve come across three issues that I haven’t been able to solve:

  1. The laptop does not suspend - closing the lid makes it stay warm and obliterate the battery, and requires a hard reset (f2+power) in order to unfreeze the black screen after opening. Pressing the power button / choosing “suspend” in the power menu makes the laptop wake up immediately. No problems with sleep when in ChromeOS.

  2. Sometimes, on boot, the screen glitches and becomes grayish-white, either during the boot process, or after log-in. Turning off Wayland and defaulting to X11 made the problem happen only during the initial boot process, though pressing power once and letting it “cycle” through the broken sleep usually brings me to the login screen just fine.

  3. Every three or four shutdowns, the computer refuses to shut down. Pressing escape on the splash shows cycling red text messages all over the screen. Sometimes, after a few minutes, the system just freezes in this state.

I can provide further information if one guides me through, I’m not too good with linux (hopefully yet) but I’m not afraid to google and learn.

2

Please run sudo dmesg -C then run sudo systemctl suspend, and then post output of sudo dmesg here.

Also could be worth reading Power management/Suspend and hibernate - ArchWiki and following the instructions to change between s2idle and deep sleep mode.

3

Here’s the dmesg output after a failed sleep attempt. It is worth noting that the first few attempts were successful, and the device did fully go to sleep successfully - it shuts down the screen, then keyboard backlight, then finally the power button. On a failed attempt, it does the exact same things then just wakes up.

I’m going to check whether it has something to do with the wifi connection or the WWAN connection, as right after the failed sleep attempt, the WWAN card craps out and refuses to connect until reboot, so it might be something related to it.

I’ll also test deep sleep and report back.

Anyhow, here’s the output:

[  570.599638] PM: suspend entry (s2idle)
[  570.617057] Filesystems sync: 0.017 seconds
[  570.643826] Freezing user space processes
[  570.646091] Freezing user space processes completed (elapsed 0.002 seconds)
[  570.646103] OOM killer disabled.
[  570.646106] Freezing remaining freezable tasks
[  570.647724] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[  570.647737] printk: Suspending console(s) (use no_console_suspend to debug)
[  570.679016] e1000e: EEE TX LPI TIMER: 00000011
[  571.066660] ACPI: EC: interrupt blocked
[  571.068937] intel_pch_thermal 0000:00:12.0: CPU-PCH is cool [39C]
[  571.158693] ACPI: EC: interrupt unblocked
[  571.224581] nvme nvme0: 8/0/0 default/read/poll queues
[  571.306473] elan_i2c i2c-ELAN0000:00: invalid report id data (ff)
[  571.369180] mip4_ts i2c-MLFS0000:00: Empty packet
[  571.420077] usb 1-6: reset high-speed USB device number 2 using xhci_hcd
[  571.502949] ata1: SATA link down (SStatus 4 SControl 300)
[  571.838501] OOM killer enabled.
[  571.838507] Restarting tasks ... done.
[  571.839750] random: crng reseeded on system resumption
[  571.910242] PM: suspend exit
[  572.007286] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down

EDIT: I think I narrowed down the issue to the WWAN module: apparently the fibocom modem REALLY doesn’t like to go to sleep when it has an active connection - simply flipping the connection switch to “off” mitigates the entire problem; should I leave it connected to my carrier when closing the lid or when pressing suspend, it wakes the system up and craps out completely, preventing its disabling and borking sleep for the remainder of the session.

I will verify if that’s really a workaround, but for now it seems like I found my answer. Furthermore, that might be a bug worth reporting, methinks.

Now I only have issues 2 and 3 to somehow debug - the glitched screen from issue 2 happens also after wakeup now, but it’s quickly solved by sleeping and waking the PC up again. I’ll make a separate reply with dmesg if I get the issue reproduced.

4

From your dmesg post, without additional info on your Sarien setup, it seems that yours have the touchscreen panel. I don’t experience the issues in #2 and #3 and I’m running CachyOS as well but mine doesn’t come with the touchscreen though. That may be something worth looking into as well.

5

Yeah, it’s one of the upper tiers, according to Dell’s specifications. The touchscreen unfortunately doesn’t work at all and I haven’t been able to find anything online that might help me with troubleshooting it.

As for #2 and #3, as soon as the problems occur i’ll snap a few photos with my phone and reply here.

As for the sleep issue, after a few days of testing, both s2idle and deep sleep work perfectly well if I break the LTE connection before sleeping the laptop, so it is indeed the reason behind the problems with sleep.

           .-------------------------:                    archie@sarien
          .+=========================.                    -------------
         :++===++==================-       :++-           OS: CachyOS Linux x86_64
        :*++====+++++=============-        .==:           Host: Sarien (rev17)
       -*+++=====+***++==========:                        Kernel: Linux 6.12.3-1-cachyos
      =*++++========------------:                         Uptime: 7 mins
     =*+++++=====-                     ...                Packages: 1425 (pacman), 30 (flatpak)
   .+*+++++=-===:                    .=+++=:              Shell: fish 3.7.1
  :++++=====-==:                     -*****+              Display (LGD063E): 1920x1080 @ 60 Hz in 14" [Built-in]
 :++========-=.                      .=+**+.              DE: GNOME 47.2
.+==========-.                          .                 WM: Mutter (X11)
 :+++++++====-                                .--==-.     WM Theme: Adwaita
  :++==========.                             :+++++++:    Theme: Adwaita [GTK2/3/4]
   .-===========.                            =*****+*+    Icons: Colloid-Dark [GTK2/3/4]
    .-===========:                           .+*****+:    Font: Cantarell (11pt) [GTK2/3/4]
      -=======++++:::::::::::::::::::::::::-:  .---:      Cursor: Adwaita (24px)
       :======++++====+++******************=.             Terminal: GNOME Terminal 3.54.2
        :=====+++==========++++++++++++++*-               Terminal Font: Source Code Pro (10pt)
         .====++==============++++++++++*-                CPU: Intel(R) Core(TM) i5-8365U (8) @ 4.10 GHz
          .===+==================+++++++:                 GPU: Intel UHD Graphics 620 @ 1.10 GHz [Integrated]
           .-=======================+++:                  Memory: 2.95 GiB / 31.22 GiB (9%)
             ..........................                   Swap: 0 B / 31.22 GiB (0%)
                                                          Disk (/): 91.61 GiB / 329.55 GiB (28%) - btrfs
                                                          Local IP (wlan0): 192.168.143.104/24
                                                          Battery (DELL C5GV285): 96% (8 hours, 39 mins remaining) [Discharging]
                                                          Locale: en_US.UTF-8

Edit: right after I sent the message, I tried rebooting the laptop. It froze, so after a hard reboot I entered

sudo journalctl -k -b 0 -o short-precise -p 4

This was the output:

gru 06 20:22:20.078559 sarien kernel: x86/cpu: SGX disabled or unsupported by BIOS.
gru 06 20:22:20.078889 sarien kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
gru 06 20:22:20.086600 sarien kernel: hpet_acpi_add: no address or irqs in _CRS
gru 06 20:22:20.089250 sarien kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
gru 06 20:22:20.089257 sarien kernel: i8042: Warning: Keylock active
gru 06 20:22:20.127661 sarien kernel: vboxdrv: loading out-of-tree module taints kernel.
gru 06 20:22:20.153654 sarien kernel: VBoxNetAdp: Successfully started.
gru 06 20:22:20.155667 sarien kernel: VBoxNetFlt: Successfully started.
gru 06 20:22:20.360670 sarien kernel: cros_ec_lpcs cros_ec_lpcs.0: couldn't reserve memmap region
gru 06 20:22:20.360808 sarien kernel: cros_ec_lpcs cros_ec_lpcs.0: probe with driver cros_ec_lpcs failed with error -16
gru 06 20:22:20.443660 sarien kernel: elan_i2c i2c-ELAN0000:00: supply vcc not found, using dummy regulator
gru 06 20:22:20.719655 sarien kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
gru 06 20:22:20.719893 sarien kernel: simple-framebuffer simple-framebuffer.0: [drm] could not acquire memory region [mem 0xc0000000-0xc02fffff flags 0x80000200]
gru 06 20:22:20.720603 sarien kernel: dell_smbios: Unable to run on non-Dell system
gru 06 20:22:20.722903 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 0
gru 06 20:22:20.723025 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 1
gru 06 20:22:20.723143 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 2
gru 06 20:22:20.723262 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 3
gru 06 20:22:20.725002 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 4
gru 06 20:22:20.725143 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 6
gru 06 20:22:20.725270 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 8
gru 06 20:22:20.725394 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 9
gru 06 20:22:20.725517 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 10
gru 06 20:22:20.725643 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 11
gru 06 20:22:20.725769 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 15
gru 06 20:22:20.725889 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 16
gru 06 20:22:20.726010 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 18
gru 06 20:22:20.726830 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 19
gru 06 20:22:20.727244 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 20
gru 06 20:22:20.727431 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 21
gru 06 20:22:20.727559 sarien kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 28
gru 06 20:22:20.730826 sarien kernel: dell_smbios: Unable to run on non-Dell system
gru 06 20:22:21.936855 sarien kernel: i2c_designware i2c_designware.0: controller timed out
gru 06 20:22:21.938665 sarien kernel: mip4_ts i2c-MLFS0000:00: mip4_i2c_xfer - i2c_transfer failed: -110 (-110)
gru 06 20:22:22.960690 sarien kernel: i2c_designware i2c_designware.0: controller timed out
gru 06 20:22:22.961355 sarien kernel: mip4_ts i2c-MLFS0000:00: mip4_i2c_xfer - i2c_transfer failed: -110 (-110)
gru 06 20:22:23.984703 sarien kernel: i2c_designware i2c_designware.0: controller timed out
gru 06 20:22:23.985250 sarien kernel: mip4_ts i2c-MLFS0000:00: mip4_i2c_xfer - i2c_transfer failed: -110 (-110)
gru 06 20:22:23.985611 sarien kernel: mip4_ts i2c-MLFS0000:00: Failed to read packet info: -110
gru 06 20:22:24.185747 sarien kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
gru 06 20:22:27.780717 sarien kernel: simple-framebuffer simple-framebuffer.0: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 0 (slots)
gru 06 20:22:27.895694 sarien kernel: [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=192.168.143.104 DST=224.0.0.252 LEN=52 TOS=0x00 PREC=0x00 TTL=255 ID=8187 PROTO=UDP SPT=5355 DPT=5355 LEN=32 
gru 06 20:22:28.146714 sarien kernel: [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=192.168.143.104 DST=224.0.0.252 LEN=52 TOS=0x00 PREC=0x00 TTL=255 ID=8398 PROTO=UDP SPT=5355 DPT=5355 LEN=32 
gru 06 20:22:28.397695 sarien kernel: [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=192.168.143.104 DST=224.0.0.252 LEN=52 TOS=0x00 PREC=0x00 TTL=255 ID=8595 PROTO=UDP SPT=5355 DPT=5355 LEN=32 
gru 06 20:22:29.684685 sarien kernel: [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:e670:511a:073b:8cd5 DST=ff02:0000:0000:0000:0000:0000:0001:0003 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=387504 PROTO=UDP SPT=5355 DPT=5355 LEN=32 
gru 06 20:22:30.035696 sarien kernel: [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:e670:511a:073b:8cd5 DST=ff02:0000:0000:0000:0000:0000:0001:0003 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=387504 PROTO=UDP SPT=5355 DPT=5355 LEN=32 
gru 06 20:22:30.312699 sarien kernel: [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:e670:511a:073b:8cd5 DST=ff02:0000:0000:0000:0000:0000:0001:0003 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=387504 PROTO=UDP SPT=5355 DPT=5355 LEN=32 
gru 06 20:22:42.282717 sarien kernel: block nvme0n1: No UUID available providing old NGUID

This time, however, what I saw on screen in verbose mode looked like regular, sucessful shutdown, instead of errors all over the screen, though - this one’s rarer.

6

Yep, looks like the touchscreen controller is interfering somehow. Could you try blacklisting those modules associated with the touchscreen?

7

Blacklisted the melfas_mip4 module, as you suggested. Now my idle wattage got lower, and dmesg doesn’t show the i2c problems anymore. I’ll update if the freezes continue, but at least I don’t get the i2c xfer fail messages anymore. I’m gonna update if fhe freezes continue.

I also found this discussion online, seems like the touchscreen wasn’t fixed in coreboot for Sarien? I may be wrong though, I have no programming background and just learn as I go.

Furthermore, I found something that might point me in the general direction of the problem with the screen.

First, how the problem looks like:

IMG_20241208_154511688
IMG_20241208_1545116881920×2560 152 KB

I also found an “unknown display” that shows up in xrandr --query, as “None-1-1” with a 1024x768 resolution. When it’s enabled, the mouse flickers or becomes a giant square on the display, that still moves and acts like a cursor. It also causes problems with multi-monitor setups, so, after some searching I followed this reddit advice, ignoring the display device completely. Somehow, I suspect that this may be the culprit behind the gray screens? I also attempted to disable SimpleDRM with “initcall_blacklist=simpledrm_platform_driver_init” but something invokes it anyway:

sudo dmesg | grep "drm"
[    0.000000] Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-cachyos root=UUID=68d70b8d-2865-4998-81d6-142118a8a3c0 rw rootflags=subvol=@ nowatchdog nvme_load=YES zswap.enabled=0 splash loglevel=3 mem_sleep_default=deep initcall_blacklist=simpledrm_platform_driver_init
[    0.102764] Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-cachyos root=UUID=68d70b8d-2865-4998-81d6-142118a8a3c0 rw rootflags=subvol=@ nowatchdog nvme_load=YES zswap.enabled=0 splash loglevel=3 mem_sleep_default=deep initcall_blacklist=simpledrm_platform_driver_init
[    0.102881] blacklisting initcall simpledrm_platform_driver_init
[    0.759054] ACPI: bus type drm_connector registered
[    1.625236] i915 0000:00:02.0: [drm] Found COFFEELAKE/ULT (device ID 3ea0) display version 9.00 stepping N/A
[    1.678384] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[    1.730967] [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 0
[    1.874747] fbcon: i915drmfb (fb0) is primary device
[    3.250082] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[    4.157403] systemd[1]: Starting Load Kernel Module drm...
[    4.174829] systemd[1]: [email protected]: Deactivated successfully.
[    4.174943] systemd[1]: Finished Load Kernel Module drm.
[    4.624405] simple-framebuffer simple-framebuffer.0: [drm] could not acquire memory region [mem 0xc0000000-0xc02fffff flags 0x80000200]
[    4.624548] simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
[    4.624550] [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 1
[    4.625173] simple-framebuffer simple-framebuffer.0: [drm] fb1: simpledrmdrmfb frame buffer device

So that concludes my personal ability to troubleshoot this.

1 Like