Change:
after = [ "dev-random.device" ]; <ins> # Clean shutdown without DefaultDependencies conflicts = [ "shutdown.target" ]; before = [ "sysinit.target" "shutdown.target" ]; </ins> description = "Hardware RNG Entropy Gatherer Daemon"; # rngd may have to start early to avoid entropy starvation during boot with encrypted swap

Discussion:
Describe the bug Very slow boot. And hang on shutdown. something about waiting for rngd To Reproduce Steps to reproduce the behavior: Change channel to 20.03 BETA update channel: nix-channel --update nixos-rebuild switch --upgrade boot.kernelPackages = pkgs.linuxPackageslatest; Expected behavior Be able to boot in under 30sec. And shutdown without hangs. Screenshots ! ! Additional context After login from sddm. I'm still waiting for gui to start. login to awesome window manager. All my partition are on nvme m.2 ssd. I was not having this issue on 19.09. With the same setup. One other thing I notice. I can only used reboot and shutdown now in root. was not the case in 19.09. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
I reproduce the boot time issue on too. On a I have the following output for (reversed journalctl output) : On I have the following output (also reversed journalctl log) : I have the feeling that the daemon is not behaving properly and is causing bootup/shutdowns to be stuck while waiting it.
I haven't seen any boot time increase, but shutdown seems to be waiting about 20 seconds for on my laptop.
Only most recent change to rngd service Perhaps try reverting it and see if there's a difference (in a controllable environment)
Yeah, if I revert shutdown doesn't have a . Startup doesn't have an issue on my machine.
The only change seems to be for my config at least?
one of the changes with 20.03 is the default kernel changed from 4.19 (previous LTS) to 5.5 (current LTS). As far as "slow boot" is concerned, If there is a kernel-side regression that is causing issues on your hardware, switching to 4.19 would help figuring out where the issue may lie. That is, assuming you weren't already using Linux 5.5 on NixOS 19.09.
To figure out what's the problem on boot, I suggest: That allows you to figure out exactly what's starting when and why it waited.
Did it for me, at least for shutdown.
i had to convert it to png.

to post it here. From what I can tell. Half sec for display-manager.service and then 8 sec to user- to load. Then nscd.service took 21 sec. After that. 38.5 sec user- And dev- took 19.5 sec. ! Don't think this is giving me the full picture. What other stuff can help pin point the long startup? Just switch to kernel 4.19. Same issue. Should I upload both my and hardware-
I see dhcpcd isn't blocking display-manager startup or login.
Then nscd.service took 21 sec. After that. 38.5 sec user- And dev- took 19.5 sec. dhcpcd took 9.8 seconds, then nscd started within 7ms. Then there's a long delay until the user with uid 1000 logs in and another long wait until fuse becomes active, which I believe is probably the actual issue. Can you try to mount your dav mountpoint through startup scripts of your user instead of systemd? At the far end you can see network- is very late and marks the point when all network interfaces are online. Which probably means that your dependencies on the network may slow down the whole boot of the system. My suggestion would be to try and disable your network mounts (webdav, etc) during boot and see if that changes anything.
Well, I switching around display manager. I had one thing pop up. With lightdm and gdm. But this does not pop up with sddm. Witch is odd. I have not touch this part. Since was made. I mostly only used weird. But still keep wireless stuff for bluetooth. networking.useDHCP = false; networking.interfaces.enp10s0.useDHCP = true; networking.interfaces.wlp8s0.useDHCP = true; And I have iwd enable.
So I figure out my issue with boot. It now under 30sec. Startup finished in 14.828s (firmware) + 4.153s (loader) + 5.459s (kernel) + 2.913s (userspace) = 27.353s reached after 2.910s in userspace Change I made so far.

networking.useDHCP = false; #networking.interfaces.enp10s0.useDHCP = true; #networking.interfaces.wlp8s0.useDHCP = true; And for my network + for wifi backend. But there a new issue. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Now if I or . I only get this: `` No other info pop up for me. Just . It does not blinks.