Just to preface this, I’m a complete NixOS noob so this might very well just be a skill issue.
I have installed and enjoyed NixOS for a couple days, but I recently made a change to my configuration.nix that ended up causing my PC to not finish its boot (or at least that’s my best guess, it just waited indefinitely just before the login screen).
“No worries,” i thought, “I’ll just force it to shut down, roll back to the previous iteration and be on my merry way!”
Which is exactly what I did, except the laptop’s touchpad has been unresponsive ever since. Plugging in a USB mouse works fine, and everything else works perfectly, but even rolling back to earlier iterations hasn’t been able to fix this.
This might just be something that got messed up during the failed boot, and I think reinstalling NixOS will probably fix it (source: It worked when I first installed it, and a similar problem I got when using Arch got fixed this way), but I hoped I could fix it without resorting to such a radical solution.
Additional information:
As mentionned in the title, I mainly use hyprland, however the problem persists on the default GNOME DE.
The laptop I’m using seems to use fairly annoying parts as far as harware support goes (for instance, my WiFi adapter has no linux drivers anywhere so I’m forced to use a USB antenna), but I don’t think that’s the core issue here.
Also since you forced shutdown, try sudo nix-store --repair --verify --check-contents to ensure there’s no store corruption (it may take a few minutes, or much longer, depending on the size of your store).
Yes that’s what I meant. Note that in a typical nix-channel setup, you need to update the channels as root. (Each user has their own set of channels, root user’s channels are used for NixOS by default.)
This indicates an error related to the GPU. Please take a look at the actual journal, not the systemd output during boot. You need to figure out what happened after this message was printed.
Make sure it’s actually stalled. Try switching to another virtual terminal for instance.
From what I can tell, you have a GUI configured in your config.
So I haven’t had the time to do anything related to the logs, but I did try at the time switching to another virtual terminal, which didn’t work.
I do have a GUI configured now, but I didn’t at the time (I think i forgot to specify a path, or used an invalid one).
I also tried booting through a live USB into other OSs (namely NixOS live and Debian), and the mouse problem still persists, so this might just be a harware problem. I’ll try reinstalling a clean system, including the boot partition, but it seems the root cause isn’t a faulty NixOS system.
So, I reinstalled NixOS from scratch (which, might I add, made me appreciate the declarative config even more), making sure to create a new /boot partition. As suspected, I must have messed something up during that faulty boot, because once reinstalled everything worked again!
Thanks for your help, I learned a lot on NixOS through this experience. Will update if I experience the problem again, but I think it really was just a messed up /boot partition.