Glad you posted this here. I just applied it and will report back if it works. I found this article about diagnosing the issue but I wasn’t sure how to solve the issue.
I was on zen kernel, then went back to regular latest. Now I find this article: Linux Kernels - 4 Different Types of Kernels Explained - LinuxForDevices and I’m wondering: Should I go back to zen for the performance? How much power cost are we talking, here?
1 Like
Hi all, is anyone else having issues with steam games running on NixOS? I have it installed via programs.steam.enable = true in my configuration.nix, and so far I’ve tried to play Slime Rancher 1 which occasionally crashes my entire system and turns off the laptop but is mostly okay, and Satisfactory, which near-instantly (just in the settings menu) crashes my entire system and turns off the laptop.
Just wanted to check if there’s a common sense fix before I go and open an issue on NixOS discourse, since I can’t find any other reports of this I thought it could be a hardware issue.
Please let me know where to look in terms of system logs if needed!
The only issue I encountered with steam was after prolonged use. I am pretty sure it was a cooling issue for me as for gaming I use an external keyboard, mouse, and display so I had the lid closed. Once I put a laptop cooler under it there have been no issues.
I have been having issues getting valve index working, but even there I’ve had no crashes when I got the loading environment partially working.
I agree that it sounds like your issue is a hardware issue.
1 Like
Please elaborate on the /run/system/transient parts. The rest makes sense, but why are you creating a symlink here and then deleting it? Is this to prevent it from restarting on its own by making it fail to create a file in that location? And if so, won’t this method just keep filling up errors in the log?
From what I’ve gathered, the architecture of fprintd with the general authentication stack means that it doesn’t need to be actually started all the time. Rather, it can be dynamically started when needed to authenticate the user. Because of that, simply stopping (or even disabling) the service isn’t actually enough to properly disable fingerprint-based authentication. To do that, the service needs to be masked (ie. symlink its unit file to /dev/null to prevent it from ever being started). The problem is that fprintd’s unit file on NixOS lives on the immutable nix store filesystem, so you can’t just make a symlink there. To get around that, you create a symlink in /run/systemd/transient, which is a volatile (ie. won’t persist between reboots) way of adjusting the unit file for a particular service. By symlinking fprintd.service to /dev/null in the transient directory, we’re effectively masking the unit for as long as the current boot (It will be undone by a reboot), bypassing the RO issue of the nix store.
By creating the masked symlink and reloading the daemon, it becomes impossible for any part of the system to start fprintd, effectively disabling fingerprint authentication. By removing that symlink and reloading the daemon again, fprintd becomes accessible again.
Thanks. That helps a bunch. Your script seems to work well, so I appreciate it.
I have expanded the nixos wiki page on the framework 16 and provided guidance on how to resolve some of the known issues. I have skimmed trough this thread and if I missed anything feel free to point me to a message.
2 Likes
Also: if somebody here more familiar with udev rules and device IDs can help me figure out what is wrong with my attempt to disable the trackpad from being able to wake the device, I’d appreciate some help with that.
My framework 16 suddenly stopped being able to connect to hidden networks.
I’m on kernel 6.8.12, my AP is broadcasting a network with 5Ghz, and WPA3/WPA2 security, model is the WAX610 Netgear. I don’t think it’s my AP I think it’s the laptop because other devices connect to this hidden network fine. I can connect to other networks without an issue but just not hidden networks.
Not sure what logs I should post, so I’ll post NetworkManager’s and dmesg.
-- Boot b505a11d52294afe8d5d496909450d89 --
Jul 05 18:00:25 nixon systemd[1]: Starting Network Manager...
Jul 05 18:00:25 nixon systemd[1]: Started Network Manager.
Jul 05 18:08:41 nixon systemd[1]: Stopping Network Manager...
Jul 05 18:08:41 nixon systemd[1]: NetworkManager.service: Deactivated successfully.
Jul 05 18:08:41 nixon systemd[1]: Stopped Network Manager.
Jul 05 18:08:41 nixon systemd[1]: NetworkManager.service: Consumed 951ms CPU time, 12.3M memory peak, 0B memory swap peak, read 9.2M from disk, written 0B to disk, received 0B IP traffic, sent 912B IP traffic.
Jul 05 18:08:41 nixon systemd[1]: Starting Network Manager...
Jul 05 18:08:41 nixon systemd[1]: Started Network Manager.
Jul 05 18:17:50 nixon NetworkManager[8442]: /nix/store/gnqzwzvlmn3kngkj03qwqsarbs03mcv1-openresolv-3.13.2/sbin/.resolvconf-wrapped: line 888: kill: (8441) - No such process
Jul 05 18:17:50 nixon NetworkManager[8442]: clearing stale lock pid 8441
Jul 05 18:21:24 nixon NetworkManager[6297]: <warn> [1720174884.6955] device (wlp1s0): Activation: (wifi) association took too long, failing activation
Jul 05 18:21:24 nixon NetworkManager[6297]: <warn> [1720174884.8004] device (wlp1s0): Activation: failed for connection 'hypernet'
Jul 05 18:23:09 nixon NetworkManager[6297]: <warn> [1720174989.6953] device (wlp1s0): Activation: (wifi) association took too long, failing activation
Jul 05 18:23:09 nixon NetworkManager[6297]: <warn> [1720174989.8120] device (wlp1s0): Activation: failed for connection 'hypernet'
lines 406-484/484 (END)
dmesg:
[ 1978.795038] wlp1s0: authenticate with 94:a6:7e:9a:ca:e2 (local address=e8:65:38:52:53:ff)
[ 1978.809237] wlp1s0: send auth to 94:a6:7e:9a:ca:e2 (try 1/3)
[ 1978.847584] wlp1s0: authenticate with 94:a6:7e:9a:ca:e2 (local address=e8:65:38:52:53:ff)
[ 1978.857204] wlp1s0: send auth to 94:a6:7e:9a:ca:e2 (try 1/3)
[ 1978.861716] wlp1s0: authenticated
[ 1978.863291] wlp1s0: associate with 94:a6:7e:9a:ca:e2 (try 1/3)
[ 1978.877289] wlp1s0: RX AssocResp from 94:a6:7e:9a:ca:e2 (capab=0x511 status=0 aid=2)
[ 1978.910712] wlp1s0: associated
[ 1978.958920] wlp1s0: Limiting TX power to 21 (24 - 3) dBm as advertised by 94:a6:7e:9a:ca:e2
Is this a known issue and what can I do to solve it? Thanks
Edit: Changing the hidden network to broadcast does not fix the issue. I think the laptop is just not picking up the signal of the specific network? The 2 networks I’m testing it on are from the same AP.
I’m running into an issue where Chromium and Electron programs are using my dGPU instead of iGPU. Anyone know how to fix this?
Not sure if this is normal, but btop is reporting the dGPU as “gpu0” and the iGPU as “gpu1”, so maybe it’s defaulting to the lowest number? Everything else seems to be using the correct device (games on the dGPU and regular programs in the iGPU).