Bug 234811 - Beastie boot loader garbled, does not clear screen before drawing
Summary: Beastie boot loader garbled, does not clear screen before drawing
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: arm (show other bugs)
Version: 12.0-RELEASE
Hardware: arm64 Any
: --- Affects Only Me
Assignee: Warner Losh
URL:
Keywords: loader
Depends on:
Blocks:
 
Reported: 2019-01-10 03:49 UTC by oitdmser
Modified: 2019-01-11 09:49 UTC (History)
2 users (show)

See Also:


Attachments
beastie bootloader menu overlaid on prior stout (196.33 KB, image/jpeg)
2019-01-10 03:49 UTC, oitdmser
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description oitdmser 2019-01-10 03:49:32 UTC
Created attachment 200972 [details]
beastie bootloader menu overlaid on prior stout

Beastie bootloader does not clear screen before drawing menu.

By default the Raspberry Pi ARM64 image ha beastie_disable="YES" in /boot/loader.conf. Changing this to "NO" or commenting the line out enables the bootloader menu. In each case the menu displays but does not clear the screen making it very difficult to discern menu options. This happens regardless of the loader_color="XX" setting in /boot/loader.conf.
Comment 1 Emmanuel Vadot freebsd_committer 2019-01-10 04:59:57 UTC
For the overlay and clearing part is this actually a u-boot "bug"
Doing a clear screen in the simple text output protocol doesn't clear the graphical part.
For the garbled output seen in your attachment I don't really know what's going on, maybe u-boot doesn't have the fonts for the character used by the box ?
I'll try to do test.
Comment 2 Warner Losh freebsd_committer 2019-01-10 06:15:03 UTC
If manu doesn't find anything, I'll take a look...
Comment 3 oitdmser 2019-01-10 12:50:46 UTC
I think the output is only really 'garbled' because the text overlays the previous u-boot output. I think the menu would look fine if it was drawn on a clear screen
Comment 4 Emmanuel Vadot freebsd_committer 2019-01-11 09:49:31 UTC
loader_menu_frame="ascii" in loader.conf fixes the weird char.