It's really ridiculously frustrating to be blocked at the very beginning here on something like that I have very little visibility into. I understand that GRUB needs to be small as a bootloader but I definitely could use more info than "out of memory". Can you give me *any* information about why? Absolutely not.

I'm pretty resilient to tinkering with things once I can get a kernel loaded, I'll even compile modules and find firmware for the install, but hamstrung at the bootloader is arrrrrgh.

Partial success today, as I have booted Debian 10.0 and made it to the point where I can backup the internal drive. Given this old old grub2 works, I'm wondering if this is something we will be able to fix for Debian bookworm. I'll need to investigate more and possibly write up my struggles for the benefit of future geeks.

For now, I backup using dd, gzip and ssh. Only 5 hours estimated for the 1T drive backup. Considering finding an alternate target for the backup 😅

One of the annoying things about this bug is that there are a bunch of things to try if you have an installed Linux system, and none of them are usable to initially install a system.

Now that I have a candidate installation media, even if it's from 2019, after backup I can install and claw my way into the present and also engage the workarounds for the bug.

Slowly clawing my way into the present-day kernels. Hoping that at some point the builtin keyboard will start to work 🫠

(The builtin keyboard started working with the unstable Debian kernel)

@jamuraa

have you said yet what model this is? Was a time once I would take media into a store to make sure it would boot to a live system, but options to do that have been thinning out.

(Understood if you're reserving that level of detail for a write-up)