#TIL that the preventWakeOnAC workaround from nixos-hardware is no longer needed with kernel >= 6.7 because of
I’m getting the “No devices available” error when enrolling fingerprints on my Intel 12th gen Framework, despite it working fine in Manjaro. I’ve tried clearing the old fingerprints, updating the firmware (even though the guide said it’s only needed for 13th gen and AMD), nothing is working.
My config contains:
services.fprintd.enable = true;
services.fprintd.tod.enable = true;
services.fprintd.tod.driver = pkgs.libfprint-2-tod1-goodix;
security.pam.services.login.fprintAuth = true;
Any ideas?
I’d love two separate nixos threads for AMD and intel, things are getting pretty messy
8 Likes
Does anyone else have a problem with the cpu frequency? It appears to be stuck at 400Hz no matter what.
intel_pstate is active and governor is ‘performance’.
I don’t think I had this problem yesterday, I only noticed after adding a TLP configuration but even reverting that doesn’t make a difference
Good evening all,
Hoping to get a few pointers on where to start with a few issues I’m having.
I’m a bit of a newer Linux user as I’ve used Fedora for about a year, but never had to tinker as it’s always worked / never gotten in the way of my needs, but this weekend I decided to learn something new with my flash new toy.
So here are my issues:
- When connecting the dock, either 1)The external screen wakes, and no peripherals work, or 2) the screen is not recognised but all my peripherals work
- The HDMI expansion card does nothing. Not so much as an audible device tone.
Some context, I have run my laptop in dual boot with Fedora 39 for about a fortnight and had neither of the above issues.
Things I have tried:
- nixos-rebuild switch --upgrade
- changing to unstable branch
- applying the nixos-hardware config
- trying a different Desktop Environment
- quick google searches before realising I’m in too deep and don’t have enough established knowledge of linux or Nix
- going back to Fedora as a sanity check
I appreciate this is probably not the best initial place to ask this, but I figured it was contextually, worth doing as we’re all on (somewhat) similar platforms. I’m happy to go and read and/or play, but I don’t know where to start.
Any hints, tips or ideas would be greatly appreciated.
Cheers,
I thought I’d share my config here for my 12th-gen Intel Framework laptop
This is a flake-based config with home-manager as a module. It includes the recommended TLP config from Framework. I’m currently running a pre-release version of System76s COSMIC desktop environment (which is awesome!), but also have configuration for KDE Plasma 6. I also have Firefox and Neovim configured through home-manager.
1 Like
I am in the process of working with the NixOS community right now (literally in chat in another tab) for a community support program.
Soon, once we get everything dialed in, you will see NixOS recommendations in the nearish future.
17 Likes
That’s awesome to hear and is definitely something I would love to participate in! Will you link to any upcoming announcements in this thread?
I’m going insane I have a AMD Framework, Latest BIOS, Latest Kernel, and I keep getting this error which disconnects my USB-C AMP/Headphone Setup like 3 seconds after I connect it (It works for like 3 seconds then makes a pop sound and stops working, and this error shows up, I reconnect it, and it works for 3 more seconds than stops working.)
Even after it stops working, it still shows up as an available output too.
For some reason, TIDaL-HiFi works until I switch my window to Firefox and start playing audio, then it breaks again??? Something with switching windows from TIDaL-Hifi to Firefox and playing audio (e.g a youtube video) breaks it.
Kernel: 6.8.2
NixOS: Unstable Branch
GNOME 45
Definitely not NixOS-specific, so it would probably be better to ask in some other thread.
But anyway, are you sure that this error actually appears right after the disconnect? Does it appear every time? Many people are getting this error, so it would be good to confirm that it is actually related. My logs are definitely full of this error and I don’t think it has any negative effect in my setup. You might also consider following e.g. [RESOLVED] AMD F39 USB-C hiccups with external display directly connected via USB-C - #16 by Matt_Hartley.
It is related, I tested multiple times, after the disconnect it shows that error in the log.
Yep, it will be announce here. Nix team has already put this together - I am crafting my asks now to send them. Working directly with them.
Now we need to fill in the blanks with help from the community. This entry is for 11th gen, but we need it for all selections here.
https://wiki.nixos.org/wiki/Hardware/Framework/Laptop_13
We have two spaces, best to start here and let them know you want to join up and help with contributions here. They have set up a dedicated Matrix chat, but best start here and request directions on what works best for their team.
7 Likes
Yes, I’m sure since it works with other Linux computers (my mom’s computer that’s running Arch currently)
Hi! I am seeing similar - did you find a solution?
Not sure if this solves it, but they did just merge Framework 16 support into the hardware repo here: Reposted added framework 16 by jkoking · Pull Request #915 · NixOS/nixos-hardware · GitHub
I see it includes a tweak for Fix TRRS headphones missing a mic which might be related?
For your information: I found the following wiki pages about Framework Laptop.
1 Like
I am having an issue where sometimes when I resume from hibernation, the wifi drivers are not loaded. I have to do sudo modprobe -r mt7921e && sleep 10 && sudo modprobe mt7921e to get wifi working again.
I am on an AMD framework running 23.11 with the latest kernel, using the nixos-hardware repo. My disk has luks encryping an LVM that has a root and swap volumns.
Not really sure where to start troubleshooting, but am open to suggestions.
First of all, what are the symptoms? Anything in dmesg? Do you see the physical interface e.g. in ip l? Also what do you mean by “drivers”? You are saing that you have to do modrprobe -r, so sounds like the module gets loaded?