00:00 <jaeger> Though noctua does have the "chromax" ones, they're usually more expensive here

11:51 <emmett1> Guys, when CRUX dev gonna fix broken grub?

11:51 <emmett1> Bugs thats introduced by e2fsprogs long ago

11:52 <emmett1> I already report before in #crux but seems still no fix

12:30 <farkuhar> emmett1: are you referring to the metadata checksum seed (stored in the superblock by mke2fs, but not recognized by grub)? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030846

12:32 <emmett1> Yeah this is it

12:33 <emmett1> I have my own patched grub local port while waiting crux dev fix it

12:33 <emmett1> Looks like they not fix it

12:34 <emmett1> I feel bad for new users wanna try crux

12:34 <emmett1> Stuck on broken grub when try to install crux

12:34 <emmett1> Like this guy:

12:34 <emmett1> https://www.reddit.com/r/linux4noobs/comments/14s2coz/grubinstall_error_unknown_filesystem/?utm_source=share&utm_medium=ios_app&utm_name=ioscss&utm_content=2&utm_term=1

12:38 <farkuhar> I'm curious why patching grub is the preferred fix, rather than changing the default invocation of mke2fs so that it doesn't try to store incompatible extensions in the superblock. Add to the bash_profile on the ISO something like alias mke2fs=..., and that should prevent any grub breakage.

12:42 <farkuhar> but an alias in the bash_profile might be too fragile. Better to change /etc/mke2fs.conf, and disable the incompatible extensions that way.

12:48 <farkuhar> If I'm reading the chronology correctly, grub 2.06 was released first, and then e2fsprogs came out with the breaking change. It doesn't seem fair to apply patches to grub, if e2fsprogs can be configured to play nice with the official grub 2.06 release.

13:03 <emmett1> Yeah you right, e2fsprogs caused it, so e2fsprogs side should be fixing it

13:04 <emmett1> Yeah you right, e2fsprogs caused it, so e2fsprogs side should be fixing it

13:04 <emmett1> Any ways should be okay as long as it get fixed.

13:05 <emmett1> I’m not good enough to configure mke2fs stuff to avoid the error, i found patch to fix it so i just use it on my local repo

13:06 <farkuhar> Plus, the fix for e2fsprogs only involves a config file on the ISO, rather than forcing grub users to rebuild a port that they probably won't need to run again anyway.

13:07 <emmett1> Yeah, but at least it gets users to get crux installed

13:15 <farkuhar> To be honest, I haven't used grub at all since configuring my kernels with EFI stub support. Then after writing the handbook section on syslinux, I switched all my machines to syslinux as a bootloader. That detour left little time for revisiting the grub section of the handbook, to ensure that all the instructions still worked as advertised.

13:37 <emmett1> I’m still stuck with grub

13:38 <emmett1> Been use it since 1st day i use linux

13:39 <emmett1> syslinux i only use on my custom linux iso of various distros

13:40 <emmett1> Both with grub for EFI

15:15 <jaeger> Ugh... rust makes for another python module dependency bloat, now with jsonschema

20:56 <farkuhar> Heh, just figured out why my first build of Linux 6.4.1 failed to boot. Apparently syslinux uses the deprecated EFI handover protocol, but my .config had the line "# CONFIG_EFI_HANDOVER_PROTOCOL is not set."

21:01 <farkuhar> The option to turn off this legacy code was merged in Linux 6.2, but I wasn't following the development closely enough to realize the implications for syslinux booting. https://bugs.archlinux.org/task/77632

21:12 <jaeger> oops

21:12 <jaeger> Good to know, wasn't aware of that