| 11 Mar 2025 |
 aloisw | In reply to @elvishjerricco:matrix.org
systemd-boot or systemd-stub will pass the initrd via a custom uefi protocl Oh wait, it's only the kernel that decompresses it. Ignore what I said then. | 18:07:10 |
 ElvishJerricco | yea.... | 18:07:27 |
| ElvishJerricco | certainly the issue must have to do with the massive initrd; that's such a strange and blatant variable | 18:08:22 |
| ElvishJerricco | but I have no idea why | 18:08:26 |
| aloisw | (Unless for some reason it fails to do a contiguous allocation of the 358.5 megabytes, but that's not that much from remote speculation.) | 18:08:27 |
| ElvishJerricco | unless it wants to allocate that close to the 4G boundary I guess? | 18:08:54 |
| ElvishJerricco | no idea why it would | 18:09:01 |
| ElvishJerricco | i mean that might actually just be randomness or board specificness | 18:10:46 |
| ElvishJerricco | "EFI says to allocate here" and systemd-boot says "but I WANTED it behind there!" | 18:11:28 |
| ElvishJerricco | 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 | yes | 18:16:15 |
| ElvishJerricco | 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 | (unless the decompressed size is huge) | 18:16:51 |
| ElvishJerricco | 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 | * 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 | regardless, the bug on nixos's side is how the hell we made a 358M initrd | 18:18:00 |
| ElvishJerricco | god dammit nvidia firmware | 18:41:01 |
| ElvishJerricco | 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 | 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 | 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 |
