You are not logged in.
Pages: 1
Hi, I'm generally new to Arch Linux, as I have only used it once or twice.
I'm having an issue where I can't get my Chromebook (Modified Firmware to run Arch) to sleep consistently. The screen will shut off, but the keyboard backlight stays lit, and the power LED stays solid (Supposed to flash while in sleep.)
Every couple of times that I restart, randomly, Sleep seems to work without issue, and will work until the next time the device is restarted.
Thanks
Last edited by velcoreNarthas (2024-10-16 20:06:21)
Offline
Para todos todo, para nosotros nada
Offline
I tried adding the kernel parameters listed there, and it didn't work for me. I would like to add, that before first logging in, it will sleep fine. After I log in, it can't sleep whatsoever, unless I'm really lucky.
These are the kernel parameters I added: modprobe tpm_tis force=1 interrupts=0
Is there anything else I should try?
Offline
https://wiki.archlinux.org/title/Chrome … ng_suspend
When the sleep fails, can you still somehow wake the system or ssh into it?
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Ceterum censeo: is there a parallel windows installation?
Offline
No, I only have an Arch Linux install right now. It doesn't really make it to sleep, and really only turns off the screen. The keyboard backlight stays on, the power LED never starts flashing.
They keyboard backlight has issues turning off at all, too.
Here is the output of the command given: https://0x0.st/XIip.txt
Update: I screwed around a bit, and somehow, the keyboard backlight is now able to turn off. The system still doesn't sleep, as the fan stays running. I expect the keyboard to stop working again soon, as this has happened before.
Last edited by velcoreNarthas (2024-10-15 18:27:42)
Offline
Oct 15 11:30:13 laptrt-ULTRAMKIII systemd[1]: Reached target Sleep.
Oct 15 11:30:13 laptrt-ULTRAMKIII systemd[1]: Starting System Suspend...
Oct 15 11:30:13 laptrt-ULTRAMKIII wpa_supplicant[734]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 15 11:30:13 laptrt-ULTRAMKIII wpa_supplicant[734]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 15 11:30:13 laptrt-ULTRAMKIII wpa_supplicant[734]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Oct 15 11:30:13 laptrt-ULTRAMKIII systemd-sleep[1750]: Successfully froze unit 'user.slice'.
Oct 15 11:30:13 laptrt-ULTRAMKIII systemd-sleep[1750]: Performing sleep operation 'suspend'...
Oct 15 11:30:13 laptrt-ULTRAMKIII kernel: PM: suspend entry (s2idle)
Oct 15 11:30:14 laptrt-ULTRAMKIII kernel: Filesystems sync: 0.012 seconds
Oct 15 11:30:14 laptrt-ULTRAMKIII wpa_supplicant[734]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 15 11:30:14 laptrt-ULTRAMKIII wpa_supplicant[734]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 15 11:30:14 laptrt-ULTRAMKIII wpa_supplicant[734]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: Freezing user space processes
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: OOM killer disabled.
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: Freezing remaining freezable tasks
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: ACPI: EC: interrupt blocked
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: ACPI: EC: interrupt unblocked
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.29.2
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: OOM killer enabled.
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: Restarting tasks ...
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: done.
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: random: crng reseeded on system resumption
Oct 15 11:30:24 laptrt-ULTRAMKIII systemd-sleep[1750]: System returned from sleep operation 'suspend'.
Oct 15 11:30:24 laptrt-ULTRAMKIII bluetoothd[630]: Controller resume with wake event 0x0
Oct 15 11:30:24 laptrt-ULTRAMKIII systemd-sleep[1750]: Successfully thawed unit 'user.slice'.
Oct 15 11:30:24 laptrt-ULTRAMKIII kernel: PM: suspend exit
Oct 15 11:30:24 laptrt-ULTRAMKIII systemd[1]: systemd-suspend.service: Deactivated successfully.
Oct 15 11:30:24 laptrt-ULTRAMKIII systemd[1]: Finished System Suspend.
Oct 15 11:30:24 laptrt-ULTRAMKIII systemd[1]: Stopped target Sleep.
s2idle only, but the system "sleeps" for 10 seconds.
I guess "deep" sleep (S3) isn't available?
cat /sys/power/mem_sleep
A random google however suggests otherwise?
https://www.quantulum.co.uk/blog/debian … hromebook/
Offline
Running
cat /sys/power/mem_sleep
Produces
s2idle [deep]
Doing what they did in the guide (Specifically adding the kernel parameter) causes the system to sleep for a split second, but then to wake right after.
Also, I figured out how to reproduce the conditions to make the keyboard backlight work. (It's very janky).
I found that if I edited the kblight using ectool, then, while charging, hibernated, on the next boot, it would work properly.
It will then work until the next time you fully shut down the device.
Offline
Doing what they did in the guide (Specifically adding the kernel parameter) causes the system to sleep for a split second, but then to wake right after.
Do you have a journal for that, because
s2idle [deep]
isn't reflected in the one you posted.
Offline
Sure, I ran the command to get the journal since last boot again.
Offline
There's no sleep attempt in that journal.
Offline
Sorry, I forgot to do that, I had just restarted to do something. Here is the journal again.
Offline
Now there're multiple sleep attempts that all get broken immediately (and spuriously, I assume) resulting in an xhci error. ehci doesn't show up in the journal.
cat /proc/acpi/wakeup
Offline
Running
cat /proc/acpi/wakeup
Produced
Device S-state Status Sysfs node
LID0 S4 *enabled platform:PNP0C0D:00
CREC S5 *disabled platform:GOOG0004:00
*disabled gpio:gpiochip1
H02C S3 *disabled i2c:i2c-GXTP7288:00
CRFP S3 *enabled spi:spi-PRP0001:00
*disabled gpio:gpiochip2
XHCI S3 *enabled pci:0000:00:14.0
GLAN S4 *disabled
TXHC S4 *enabled pci:0000:00:0d.0
TDM0 S4 *enabled pci:0000:00:0d.2
TDM1 S4 *enabled pci:0000:00:0d.3
TRP0 S4 *enabled pci:0000:00:07.0
PXSX S4 *disabled
TRP1 S4 *enabled pci:0000:00:07.1
PXSX S4 *disabled
TRP2 S4 *enabled pci:0000:00:07.2
PXSX S4 *disabled
TRP3 S4 *disabled
PXSX S4 *disabled
CNVW S3 *disabled pci:0000:00:14.3
Offline
echo XCHI | sudo tee /proc/acpi/wakeup
cat /proc/acpi/wakeup # should be disabled now
In doubt just disable all (except for maybe the lid?) and see whether you can sleep the system (and wake it, somehow
Offline
Yay!
LID0 S4 *enabled platform:PNP0C0D:00
CREC S5 *disabled platform:GOOG0004:00
*disabled gpio:gpiochip1
H02C S3 *disabled i2c:i2c-GXTP7288:00
CRFP S3 *disabled spi:spi-PRP0001:00
*enabled gpio:gpiochip2
XHCI S3 *disabled pci:0000:00:14.0
GLAN S4 *disabled
TXHC S4 *disabled pci:0000:00:0d.0
TDM0 S4 *disabled pci:0000:00:0d.2
TDM1 S4 *disabled pci:0000:00:0d.3
TRP0 S4 *disabled pci:0000:00:07.0
PXSX S4 *disabled
TRP1 S4 *disabled pci:0000:00:07.1
PXSX S4 *disabled
TRP2 S4 *disabled pci:0000:00:07.2
PXSX S4 *disabled
TRP3 S4 *disabled
PXSX S4 *disabled
CNVW S3 *disabled pci:0000:00:14.3
I disabled all but LID0, (I couldn't figure out how to disable the blank ones) and it was able to sleep
The system is able to wake up by pressing the power button.
Then, by going through each device and enabling them, I found that enabling 'CRFP', and ONLY 'CRFP' caused it to wake up right after.
EDIT: I found that the device gets enabled when the system reboots. I'm probably going to write a script to have it disabled on startup.
Last edited by velcoreNarthas (2024-10-16 17:11:01)
Offline
\o/
I found that the device gets enabled when the system reboots.
=> https://wiki.archlinux.org/title/System … rary_files
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Pages: 1