Like grub exists and the main config file exists and grub appears on boot and functions but there is absolutely nothing inside of grub.d and after creating my own 40_custom file and runningupdate-grub nothing happens.
@adiz
Shouldn't there be something like "dpkg-reconfigure -f" to force it recreating the default config files? I don't remember much about Debian, but I think it's something like that.
@m0xee@social.librem.one I'll have to check into that. I have Debian and Haiku dual-booting on my miniPC without issue. This is a fresh install of Debian on this laptop, so nothing funky should have been done with it.
@adiz Dunno, maybe Haiku messed up the EFI partition on primary disk, but empty grub.d looks wrong anyway 🤷
@adiz Oh, that!
I think it doesn't scan for other operating systems by default now, you have to set GRUB_DISABLE_OS_PROBER=false in /etc/default/grub to force it.
Here: https://wiki.archlinux.org/title/GRUB#Detecting_other_operating_systems
It's about Arch, but it's exactly the same in Void and I'm pretty sure, in Debian too.
@m0xee@social.librem.one No, I've got that setup, but it's irrelevant because Haiku doesn't ship with its own EFI setup that allows grub to detect it with os-prober. So, you have to create a folder in boot/efi on the UEFI partition for Haiku with Haiku's own bootloader placed inside there, then you create a manual entry inside 40_custom of grub.d that points to the directory on the UUID of the UEFI partition and then run update-grub. I've done it before and it works, just not on this newest Debian installation on the X230.
https://www.haiku-os.org/guides/uefi_booting
https://www.haiku-os.org/guides/booting/