| 15 Jan 2023 |
 @elvishjerricco:matrix.org | Nice, my initrd networkd PR has officially demonstrated value over scripted initrd networking. I've always had problems where initrd networking on my home server wouldn't work when I need it most: After a power outage. I'm pretty sure the server starts back up before my router, so its initrd fails to get a DHCP lease quick enough and gives up. systemd initrd networkd managed without issue | 21:01:25 |
| 24 Jan 2023 |
 flokli | ElvishJerricco: can we merge it in? | 23:24:22 |
| 25 Jan 2023 |
 @vika:fireburn.ru | Huh, that's weird:
Jan 25 06:17:24 localhost systemd[1]: Found device WD PC SN740 SDDPNQD-1T00-1027 nixos-hydrangea.
Jan 25 06:17:24 localhost systemd[1]: Found device WD PC SN740 SDDPNQD-1T00-1027 swap-hydrangea.
Jan 25 06:17:24 localhost systemd[1]: Starting Cryptography Setup for nixos-hydrangea...
Jan 25 06:17:24 localhost systemd[1]: Starting Cryptography Setup for swap-hydrangea...
Jan 25 06:17:24 localhost systemd-cryptsetup[312]: TPM2 driver name 'device' not valid, refusing.
Jan 25 06:17:24 localhost systemd-cryptsetup[311]: TPM2 driver name 'device' not valid, refusing.
This has worked before, but stopped after an update. Maybe someone here is wise enough to know what's up?
| 03:51:56 |
| @vika:fireburn.ru | Thankfully if I boot an older system, it does work, so at least it's not my TPM being broken! | 03:52:16 |
| @elvishjerricco:matrix.org | Vika (she/her): I think that's a known and fixed bug | 03:53:12 |
| @elvishjerricco:matrix.org | Vika (she/her): specifically https://github.com/NixOS/nixpkgs/pull/210896 | 03:55:24 |
| @vika:fireburn.ru | oh wow it's in staging 😭😭😭😭😭😭 | 03:57:43 |
| @vika:fireburn.ru | i don't know if i can afford rebuilding the world while cherry-picking updates | 03:58:07 |
| @vika:fireburn.ru | i guess i'll resort to entering my passphrase every time I boot like in the old times until it hits nixos-unstable | 03:58:34 |
| @elvishjerricco:matrix.org | Maybe you can just roll back to before the bug? It's quite recent | 03:58:36 |
| @vika:fireburn.ru | oh, do you know the commit that introduced the bug? perhaps it was some systemd update? | 03:58:56 |
| @vika:fireburn.ru | it probably happened somewhere before Jan 15 and Jan 24, since these are the dates for my updates... | 03:59:50 |
| @elvishjerricco:matrix.org | Vika (she/her): it should have been the last systems update I believe | 04:00:39 |
| @elvishjerricco:matrix.org | * Vika (she/her): it should have been the last systemd update I believe | 04:00:44 |
| @vika:fireburn.ru | 47de6ecabb0609bc8b4212842fb01533b3616874 systemd: 252.3 -> 252.4
ed9e8cd687b08a4e8f3d673f25c12e345afd65cb systemd: 252.1 -> 252.3
| 04:03:53 |
| @vika:fireburn.ru | well, two possibly-bad commits are better than 2760 (not including merge commits) | 04:04:27 |
| @elvishjerricco:matrix.org | I'm not sure which one it was but I am on my phone at the moment so I'm not well equipped to figure it out :P | 04:04:56 |
| @vika:fireburn.ru | 4194 with merge commits | 04:04:59 |
| @vika:fireburn.ru | In reply to @elvishjerricco:matrix.org
I'm not sure which one it was but I am on my phone at the moment so I'm not well equipped to figure it out :P it's ok I guess I'll just try both! | 04:05:06 |
| @vika:fireburn.ru | In reply to @vika:fireburn.ru
47de6ecabb0609bc8b4212842fb01533b3616874 systemd: 252.3 -> 252.4
ed9e8cd687b08a4e8f3d673f25c12e345afd65cb systemd: 252.1 -> 252.3
and yes, that 252.4 update was in fact the bad one! | 04:50:31 |
 @gdamjan:spodeli.org | shouldn't that be 'auto' ? | 10:04:30 |
| @elvishjerricco:matrix.org | gdamjan: hm? | 10:56:47 |
| @gdamjan:spodeli.org | actually, I'm confused what 'device' is there? | 11:20:13 |
| @elvishjerricco:matrix.org | gdamjan: As I understand it, there's a bunch of different ${tpm2-tss}/lib/libtss2-tcti-*.so drivers for various TPMs. The issue was that systemd got a patch that made it so it doesn't check the correct locations to find these on NixOS. So if you had tpm2-device=auto, it would find your TPM device in /dev and determine which driver to load, but fail to properly find that driver | 11:29:43 |
| @elvishjerricco:matrix.org | one of them just happens to have a weird name device | 11:30:05 |
| @gdamjan:spodeli.org | 👍️ | 11:31:52 |
 @lily:lily.flowers | Does anyone have any thoughts on whether changing the ACTION="add" to ACTION="add|change" is a good idea here? https://github.com/systemd/systemd/blob/f2592ef0e113aef0e8e7141cab2b17521760b064/rules.d/90-vconsole.rules.in#L12
It fixes my issue with the vconsole settings racing in initrd and sometimes causing the vconsole settings to get reverted when vtcon initializes (and udev rule fires) before drm/modesetting/i915/something else does (idk where exactly it's getting reset but it only happens after the udev rule like 1 in 10 boots) | 17:54:18 |
| @elvishjerricco:matrix.org | Lily Foster: I just realized we don't actually add systemd-vconsole-setup.service to initrd... Do you add that in your config yourself? | 18:14:47 |
| @lily:lily.flowers | I do not. It didn't seem to help anything when I tried to add it so I removed it again | 18:15:19 |
| @lily:lily.flowers | The systemd-vconsole-setup seems to get run only from the udev rule, not from the .service | 18:15:40 |
