asahi-uboot/m1n1 update silently breaks boot when fbcon=map:99 is in GRUB_CMDLINE_LINUX_DEFAULT

[cried-nutty-won]

Summary

After updating asahi-uboot, m1n1 and linux-asahi (6.19.12+1 → 6.19.14+2) on Void Linux
Asahi (MacBook Pro M1 Pro 14"), both old and new kernels hang silently at
"Loading initial ramdisk ..." with no error output.

Root cause

fbcon=map:99 in GRUB_CMDLINE_LINUX_DEFAULT causes a silent hang during initramfs
loading with the updated u-boot/m1n1 stack. Removing this parameter restores normal boot
on both kernels.

This parameter was previously recommended to suppress framebuffer console conflicts on
Apple Silicon under earlier Asahi stack versions.

System

• Machine: MacBook Pro 14" M1 Pro
• OS: Void Linux Asahi (aarch64)
• Packages updated: linux-asahi, asahi-uboot-2025.10+2_1, m1n1-1.5.2_1
• Kernel before: 6.19.12+1-asahi_2
• Kernel after: 6.19.14+2-asahi_1

Fix

Remove fbcon=map:99 from /etc/default/grub and regenerate:

sudo grub-mkconfig -o /boot/grub/grub.cfg

Suggestion

A post-install message in the asahi-uboot or m1n1 xbps package warning users to remove
fbcon=map:99 would prevent this silent breakage. The INSTALL hook mechanism in
xbps-src supports this natively.

[classabbyamp]

why was that in your kernel cmdline in the first place? it's not documented by Void to add that anywhere.