| 15 Jun 2023 |
 K900 (deprecated) | I get it | 17:18:50 |
| K900 (deprecated) | It's hard | 17:18:51 |
 ElvishJerricco | I still have no idea what modesetting really means | 17:19:39 |
| K900 (deprecated) | It just means switching the display mode | 17:20:04 |
| K900 (deprecated) | Like, ideally you'd want to maintain the same display mode from power on to desktop, and have all the boot stages realize it was set correctly by firmware and not touch it after | 17:20:42 |
 @lily:lily.flowers | Just nomodeset on the kernel cmdline, easy (/s) | 17:38:36 |
| @lily:lily.flowers | In reply to @k900:conduit.0upti.me
It's triple monitors though Same models or no? | 17:40:28 |
| K900 (deprecated) | That would be too easy lmao | 17:40:37 |
| ElvishJerricco | Anyone mind tossing a review at this? https://github.com/NixOS/nixpkgs/pull/237154 | 18:45:16 |
| ElvishJerricco | Lily Foster: Well, the plymouth update didn't end up improving the inexplicable 5-10 seconds that it takes for plymouth to start up in initrd. But I can at least say everything works as expected on my desktop! | 18:56:38 |
| ElvishJerricco | i am curious about that gist you linked though, so I'm going to mess with that for a minute | 18:57:00 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
Lily Foster: Well, the plymouth update didn't end up improving the inexplicable 5-10 seconds that it takes for plymouth to start up in initrd. But I can at least say everything works as expected on my desktop! 5-10 seconds to start up? In systemd-initrd? | 19:20:15 |
| @lily:lily.flowers | I've not seen that... | 19:20:20 |
| @lily:lily.flowers | I might ask you to share logs | 19:20:29 |
| ElvishJerricco | Lily Foster: Yea, plymouth has always taken about 6 seconds to get started and show a password prompt for me. Logs have indicated that basically nothing happens in the interim | 19:21:27 |
| @lily:lily.flowers | Would you mind nabbing logs with plymouth:debug on the kernel cmdline sometime? | 19:21:50 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
Anyone mind tossing a review at this? https://github.com/NixOS/nixpkgs/pull/237154 Any reason this was done as an import within the same file? | 19:24:54 |
| ElvishJerricco | In reply to @lily:lily.flowers
Any reason this was done as an import within the same file? I didn't really see another clean way to do it, without threading an isInitrd function parameter through the whole mkOption hierarchy or something like that | 19:34:51 |
| ElvishJerricco | In reply to @lily:lily.flowers
Any reason this was done as an import within the same file? * I didn't really see another clean way to do it, without threading an isInitrd function parameter through the whole commonOptions hierarchy or something like that | 19:35:03 |
| ElvishJerricco | since it's changing the default of an existing option | 19:35:15 |
| ElvishJerricco | In reply to @lily:lily.flowers
Would you mind nabbing logs with plymouth:debug on the kernel cmdline sometime? $ journalctl -b 0 | grep -i plymouth
Jun 15 15:31:59 localhost kernel: Command line: initrd=\efi\nixos\xdmzixriby5jk6jxvd3m79ciryndjnfm-initrd-linux-6.3.7-initrd.efi init=/nix/store/qr8c7ccym056dricl45qlc9kni6w4r8b-nixos-system-jace-23.11.20230615.c5ca97a/init delayacct quiet nohibernate splash loglevel=0 plymouth:debug
Jun 15 15:31:59 localhost kernel: Kernel command line: initrd=\efi\nixos\xdmzixriby5jk6jxvd3m79ciryndjnfm-initrd-linux-6.3.7-initrd.efi init=/nix/store/qr8c7ccym056dricl45qlc9kni6w4r8b-nixos-system-jace-23.11.20230615.c5ca97a/init delayacct quiet nohibernate splash loglevel=0 plymouth:debug
Jun 15 15:31:59 localhost kernel: Unknown kernel command line parameters "splash plymouth:debug", will be passed to user space.
Jun 15 15:31:59 localhost kernel: plymouth:debug
Jun 15 15:31:59 localhost systemd[1]: Tell Plymouth To Write Out Runtime Data was skipped because of an unmet condition check (ConditionPathExists=!/etc/initrd-release).
Jun 15 15:31:59 localhost systemd[1]: Starting Show Plymouth Boot Screen...
Jun 15 15:31:59 localhost plymouthd[373]: 00:00:00.496 ../src/main.c:1956:check_verbosity : redirecting debug output to /dev/tty1
Jun 15 15:31:59 localhost plymouthd[373]: xkbcommon: ERROR: failed to add default include path /nix/store/0zl3x9ggy4sdik97cgbijkalllmkw70b-xkeyboard-config-2.33/etc/X11/xkb
Jun 15 15:31:59 localhost plymouth[374]: 00:00:00.507 ../src/libply/ply-event-loop.c:766:ply_event_loop_stop_watchin: stopping watching fd 6
Jun 15 15:31:59 localhost plymouth[374]: 00:00:00.507 ../src/libply/ply-event-loop.c:782:ply_event_loop_stop_watchin: removing destination for fd 6
Jun 15 15:31:59 localhost plymouth[374]: 00:00:00.507 ../src/libply/ply-event-loop.c:766:ply_event_loop_stop_watchin: stopping watching fd 6
Jun 15 15:31:59 localhost plymouth[374]: 00:00:00.507 ../src/libply/ply-event-loop.c:782:ply_event_loop_stop_watchin: removing destination for fd 6
Jun 15 15:31:59 localhost plymouth[374]: 00:00:00.507 ../src/client/ply-boot-client.c:807:ply_boot_client_detach_fro: detaching from event loop
Jun 15 15:31:59 localhost systemd[1]: Started Show Plymouth Boot Screen.
Jun 15 15:31:59 localhost systemd[1]: Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
Jun 15 15:31:59 localhost systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
Jun 15 15:32:03 localhost systemd[1]: Started Forward Password Requests to Plymouth.
Jun 15 15:32:07 localhost plymouthd[373]: Fontconfig warning: no <cachedir> elements found. Check configuration.
Jun 15 15:32:07 localhost plymouthd[373]: Fontconfig warning: adding <cachedir>/var/cache/fontconfig</cachedir>
Jun 15 15:32:07 localhost plymouthd[373]: Fontconfig warning: adding <cachedir prefix="xdg">fontconfig</cachedir>
Jun 15 15:32:10 jace systemd[1]: Starting Plymouth switch root service...
Jun 15 15:32:10 jace systemd[1]: Finished Plymouth switch root service.
Jun 15 15:32:10 jace systemd[1]: systemd-ask-password-plymouth.service: Deactivated successfully.
Jun 15 15:32:10 jace systemd[1]: Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
Jun 15 15:32:10 jace systemd[1]: plymouth-switch-root.service: Deactivated successfully.
Jun 15 15:32:10 jace systemd[1]: Stopped Plymouth switch root service.
Jun 15 15:32:11 jace systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Jun 15 15:32:11 jace plymouth[1643]: 00:00:12.595 ../src/libply/ply-event-loop.c:766:ply_event_loop_stop_watchin: stopping watching fd 6
Jun 15 15:32:11 jace plymouth[1643]: 00:00:12.595 ../src/libply/ply-event-loop.c:782:ply_event_loop_stop_watchin: removing destination for fd 6
Jun 15 15:32:11 jace plymouth[1643]: 00:00:12.596 ../src/libply/ply-event-loop.c:766:ply_event_loop_stop_watchin: stopping watching fd 6
Jun 15 15:32:11 jace plymouth[1643]: 00:00:12.596 ../src/libply/ply-event-loop.c:782:ply_event_loop_stop_watchin: removing destination for fd 6
Jun 15 15:32:11 jace plymouth[1643]: 00:00:12.596 ../src/client/ply-boot-client.c:807:ply_boot_client_detach_fro: detaching from event loop
Jun 15 15:32:11 jace systemd[1]: Finished Tell Plymouth To Write Out Runtime Data.
Jun 15 15:32:11 jace systemd[1]: Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
Jun 15 15:32:16 jace plymouth[2047]: 00:00:17.568 ../src/client/plymouth.c:425:on_disconnect : disconnect
Jun 15 15:32:16 jace plymouth[2047]: 00:00:17.568 ../src/libply/ply-event-loop.c:1143:ply_event_loop_free_destin: freeing destination (0, (nil), 0x403d30) of fd 6
Jun 15 15:32:16 jace plymouth[2047]: 00:00:17.568 ../src/client/ply-boot-client.c:807:ply_boot_client_detach_fro: detaching from event loop
| 19:36:25 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
since it's changing the default of an existing option Yeah I was wondering if that's what the goal was and if there was just a better way to accomplish that as well. If I remember I'll try to give a proper review later (I mostly just did a quick once-over) | 19:37:46 |
| ElvishJerricco | I believe the gap between Started Show Plymouth Boot Screen. and Fontconfig warning: no <cachedir> elements found. Check configuration. is the gap where nothing is happening. I see some of these plymouth debug messages on screen, and then it stays like that for about 8 seconds, and then the password prompt suddenly shows up. | 19:38:09 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
I believe the gap between Started Show Plymouth Boot Screen. and Fontconfig warning: no <cachedir> elements found. Check configuration. is the gap where nothing is happening. I see some of these plymouth debug messages on screen, and then it stays like that for about 8 seconds, and then the password prompt suddenly shows up. Weird... Yeah I don't know any potential causes off the top of my head | 19:39:00 |
|  @ulli:hrnz.li set a profile picture. | 22:19:56 |
| 16 Jun 2023 |
 @uep:matrix.org | In reply to @elvishjerricco:matrix.org
So the message can calculate which mountpoints are busted https://github.com/NixOS/nixpkgs/pull/238021
I punted on the calculation for now, as much as I'm in favour of better errors for nixos in particular. But the message text seems sufficient
| 00:52:22 |
| 22 Jun 2023 |
 @nikstur:matrix.org | I have a curious issue with the systemd initrd. The 9p mounts break when I start a VM with virtualisation.diskImage = null; and I have absolutely no idea how why where and what is going on. It works if the root is not volatile (so not a tmpfs). I only found this message: 9pnet_virtio: no channels available for device which sounds like kmods are missing. | 09:04:19 |
| @nikstur:matrix.org | Any ideas? | 09:04:45 |
 @gdamjan:spodeli.org | do you have the virtio_pci and/or virtio_mmio loaded? | 09:53:29 |
| @gdamjan:spodeli.org | 9pnet_virtio uses virtio to communicate to the host, but virtio_pci, virtio_mmio provide the virtio transport to the guest drivers. | 09:56:20 |
