| 10 Mar 2025 |
 ElvishJerricco | yea, might be impossible if you can't distinguish first-parent | 21:28:39 |
| ElvishJerricco | ah darn, the merge's master parent is only mildly cached | 21:34:35 |
| ElvishJerricco | I don't suppose we keep an easily parsed list of commits the channel was bumped to, do we? | 21:35:25 |
 emily | sure. the Hydra eval list | 21:47:19 |
| ElvishJerricco | ended up using this :P https://releases.nixos.org/?prefix=nixos/unstable/ | 21:47:39 |
|  Gaël joined the room. | 22:07:57 |
|  Charles left the room. | 22:30:19 |
| ElvishJerricco | new development on the issue: The 256.7 version of systemd-boot that originally introduced the 4GB boundary bug successfully boots a 24.11 generation but not a nixos-unstable generation | 23:39:00 |
| ElvishJerricco | with the same failure as the 257.2 systemd-boot | 23:39:26 |
| ElvishJerricco | so given that the breakage definitely happens between 256.6 and 256.7, just like the 4GB issue, it's certainly related, but probably a little different since it doesn't happen on a 24.11 generation | 23:40:34 |
 eyJhb | In reply to @elvishjerricco:matrix.org
I don't suppose we keep an easily parsed list of commits the channel was bumped to, do we? I'm planning on starting such a list again. I'm so tired of it not being easily available | 23:56:54 |
| 11 Mar 2025 |
 raitobezarius | In reply to @elvishjerricco:matrix.org
so given that the breakage definitely happens between 256.6 and 256.7, just like the 4GB issue, it's certainly related, but probably a little different since it doesn't happen on a 24.11 generation exciting | 01:16:51 |
| * raitobezarius put one cent on d7ae71b9c187133db028a52cd05145f6c1ef8a50 and one cent on d64193a2a652b15db9cb9ed10c6b77a17ca46cd2 | 01:20:06 |
| ElvishJerricco | K900: I guess I should ask you if anything changed since 24.11 in how the kernels look to systemd-boot that could screw it up? | 02:55:41 |
| ElvishJerricco | because the same systemd-boot is only broken for kernels from unstable, not from 24.11 | 02:56:17 |
 K900 | In reply to @elvishjerricco:matrix.org
K900: I guess I should ask you if anything changed since 24.11 in how the kernels look to systemd-boot that could screw it up? Don't think so? | 05:41:08 |
| ElvishJerricco | yea I didn't think so... I wondered about file size too but the kernel and initrd are both only barely larger in unstable | 05:41:36 |
| ElvishJerricco | I mean certainly there's something different about these that causes the issue, as they are indeed the parameters that triggers the broken boot loader behavior | 05:42:13 |
| ElvishJerricco | just can't think of anything | 05:42:21 |
| ElvishJerricco | I don't know enough about how PEs work but it might be something as stupid as the virtual addresses used by the kernel sections? (Is that the right terminology for a kernel PE?) | 05:43:45 |
| raitobezarius | In reply to @elvishjerricco:matrix.org
I don't know enough about how PEs work but it might be something as stupid as the virtual addresses used by the kernel sections? (Is that the right terminology for a kernel PE?) bingrep might help | 11:39:13 |
 Arian | Didn't systemd-boot have some weird changes in stub | 15:15:20 |
| Arian | Not that this should affect a normal nixos install though.. | 15:16:45 |
| ElvishJerricco | jesus the guy has a 350M initrd | 17:59:00 |
| ElvishJerricco | https://discourse.nixos.org/t/systemd-boot-failing-to-boot-a-nixos-warbler-system-due-to-an-efi-assertion-failure/61450/13?u=elvishjerricco | 17:59:01 |
| ElvishJerricco | ok that's a bug of its own | 17:59:10 |
| ElvishJerricco | we shouldn't make initrds that big unless user knows what and why | 17:59:26 |
| ElvishJerricco | but also systemd-boot shouldn't die because of it | 17:59:55 |
 aloisw | Well 350M not fitting into memory after decompression sounds plausible. | 18:00:44 |
| ElvishJerricco | plausible for the 4G boundary, yes | 18:01:06 |
