New comment by zdykstra on void-packages repository

https://github.com/void-linux/void-packages/issues/46758#issuecomment-1768910423

Comment:
Okay, I understand what's happening now. The `setfont` call that's being invoked isn't the one that ZFSBootMenu provides as a hook/contrib script, but is instead happening by the Dracut i18n module. They have a call to `setfont` that doesn't capture stdout/stderr, so when it errors out it just dumps straight to the console.

The font size is different in your locally built ZFSBootMenu image vs the binary release because the console auto-size hook is included by default in the binary release, but not local releases. That feature will be included/enabled by default in the upcoming ZFSBootMenu release. Until then, however, it has to be manually added to ZFSBootMenu. I'd recommend just sticking with the binary release for now - we'll have a few improvements to the local build process in the upcoming release.