On Thu, Feb 20, 2025 at 5:46 PM Go Canes <letsgonhlcanes0@xxxxxxxxx> wrote: > > I have a laptop running F40 Server with KDE, fully updated, that I > have been using without issue. I am in the process of moving to a new > laptop and plan to repurpose the old one. But I am running into an > issue with the old laptop. > > If the laptop is idle it locks up after ~25 minutes. "Idle" can mean > no one logged-in, or a user logged-in but not doing anything. If the > user is doing something, it does not lock-up. "Something" can be > running a Windows 10 VM, a ssh session running "top", etc. To recover > the system I have to do a hard-reset using the power switch. > > Things I have checked: > - Nothing is displayed on the screen > - There are no entries in the UEFI BIOS logs > - There are no messages for the lock-up shown by "journalctl -b -1 -r". > - All of the entries in /etc/systemd/sleep.conf have been changed from > "yes" to "no" and uncommented - no change > - systemctl entries for sleep, suspend, hibernate have been masked - no change > - Even though the desktop is KDE, I have checked "gsettings" for any > power or timeout related settings - nothing of interest > - If I boot off of a F40 Cinnamon install on a USB SSD drive, there > are no issues. > > Theories: > - auto sleep/suspend/hibernate - contraindicated by no change in > behavior with changes to sleep[.conf and/or masking system units. > Also, system should wake-up from any of these states. > - thermal event - contraindicated by lack of UEFI log entries, lack of > issue when system is active, lack of issue when booted off of USB > drive > - hardware issue - contraindicated by lack of issue when system is > active or booted off of USB drive. > > Any suggestions? The only other thing I can think of to try is a > re-install; I plan to do this eventually anyway, but wanted to delay > for a few weeks. In the meantime I guess I can keep the Windows 10 VM > running, it just seems wasteful. On the old laptop, try changing the chassis type to something other than laptop. I believe you can use hostnamectl to do it. This comes from an old Bay Trail machine that was misdetected, and it had weird power behaviors. See <https://www.google.com/search?q=systemd+change+chassis+type>. Eventually Red Hat added some logic to detect the Bay Trail machines to work around some of the misfeatures. Moving forward, buy an inexpensive Intel NUC when you want an inexpensive server. The thing about the NUCs is, Intel provied BIOS/UEFI updates. Eventually power problems get fixed in the firmware so you don't have to putz around with kernel and userland workarounds. On NUCs, you just disable S3, S4 and S5 power states in the BIOS/UEFI and things start working as expected. "Expected" means you can mask systemd services and things stop going to sleep or hibernate on your server. I've tried other mini-pc machines, like Beelinks. The OEM does not provide BIOS/UEFI updates, so problems never get fixed. Hence the reason I prefer Intel NUCs. Jeff -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
