| 11 Mar 2025 |
 @elvishjerricco:matrix.org | "EFI says to allocate here" and systemd-boot says "but I WANTED it behind there!" | 18:11:28 |
| @elvishjerricco:matrix.org | sidenote, I'm extremely annoyed by andre4ik3's comment claiming to show the answer clearly when it's anything but clear | 18:13:13 |
 aloisw | If xmalloc_initrd_pages is the correct function, then it asks the firmware to allocate anywhere below 4G: https://github.com/systemd/systemd/blob/7fa3b5018bfffa176c77a2a5794dce792eebadcb/src/boot/util.h#L111-L115 | 18:15:59 |
| @elvishjerricco:matrix.org | yes | 18:16:15 |
| @elvishjerricco:matrix.org | so why should 358M be hard to allocate below 4G? | 18:16:28 |
| aloisw | It just asks the firmware to do that and it fails, ask the firmware I guess. | 18:16:48 |
| @elvishjerricco:matrix.org | (unless the decompressed size is huge) | 18:16:51 |
| @elvishjerricco:matrix.org | wait not it doesn't decompress | 18:17:05 |
| aloisw | Systemd-boot does not decompress the initrd and I think the kernel alread | 18:17:07 |
| @elvishjerricco:matrix.org | * wait no it doesn't decompress | 18:17:09 |
| aloisw | * Systemd-boot does not decompress the initrd and I think the kernel already has virtual memory at the point it does. | 18:17:18 |
| @elvishjerricco:matrix.org | regardless, the bug on nixos's side is how the hell we made a 358M initrd | 18:18:00 |
| @elvishjerricco:matrix.org | god dammit nvidia firmware | 18:41:01 |
| @elvishjerricco:matrix.org | K900: do you expect that putting your nvidia modules / firmware in initrd would make it 358M? Because that's what happened | 18:41:35 |
| @elvishjerricco:matrix.org | I don't know why it only happened for them on unstable, but I suspect they left some info out | 18:42:19 |
 K900 | Uhh | 18:48:39 |
| K900 | I think the Nvidia firmware is chonky | 18:48:45 |
| K900 | But I don't know if it's that chonky | 18:48:50 |
 antifuchs | Did it pull in a ton of x11 libs? | 19:03:12 |
| @elvishjerricco:matrix.org | the firmware files wouldn't | 19:30:15 |
|  Adam Neverwas removed their display name adam_neverwas. | 23:24:10 |
| 12 Mar 2025 |
| Adam Neverwas set their display name to Adam Neverwas. | 14:27:30 |
| 13 Mar 2025 |
 mornix | Hi, I saw this is the place to talk about boot counting (via #330017). Is https://github.com/NixOS/nixpkgs/issues/337089 still seen as the way forward? And if so how can I help with boot counting? | 01:16:26 |
| 17 Mar 2025 |
| antifuchs | well this is unpleasant: it seems that systemd-networkd is now starting after zfs filesystems get unlocked, which makes it difficult for my ssh server to get online so I can remotely enter the encryption password | 13:11:46 |
| antifuchs | also, huh, did boot.initrd.systemd start setting networking.usePredictableInterfaceNames to off? I had to set up a rule for eno1 but that device isn't present, only eno1np0 and eno1np1 | 13:32:23 |
| antifuchs | * also, huh, did boot.initrd.systemd change interface naming schemes? I had to set up a rule for eno1 but that device isn't present, only eno1np0 and eno1np1 | 13:34:53 |
| antifuchs | * also, huh, did boot.initrd.systemd change interface naming schemes in nixos-unstable? I had to set up a rule for eno1 but that device isn't present, only eno1np0 and eno1np1 | 13:35:02 |
 gdamjan | that seems to be kernel dependent | 13:41:16 |
| antifuchs | yeah, seems so. I should make up my own names for netdevs | 13:52:11 |
| antifuchs | still, what a damn trap to run into /: | 13:52:20 |
