Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not displaying characters with tones in systemd boot menu properly #344

Open
peigongdsd opened this issue May 26, 2024 · 7 comments
Open

Comments

@peigongdsd
Copy link

peigongdsd commented May 26, 2024

The latest version of nixos is named 24.11.20240526.a457dae (Vicuña), while the character ñ of Vicuña is not properly displayed in systemd-boot shipped with lanzaboote. See the latest entry in the following image.

image

@nikstur
Copy link
Member

nikstur commented Jun 8, 2024

I don't believe this is a lanzaboote issue. On my system, the character is displayed correclty. It suspect this might be an issue in your UEFI implementation (or less likely a bug in systemd-boot).

@RaitoBezarius
Copy link
Member

I confirmed this works out of the box on my:

UEFI 2.80 (American Megatrends 5.26)

system.

i.e. the fonts are available on modern up-to-date UEFI.

@RaitoBezarius
Copy link
Member

@nikstur We could consider implementing a "my firmware is bad" mode to strip accents and so on, to be honest.

@peigongdsd
Copy link
Author

So I think this is not the right place to ask help for this problem. Maybe I should turn to systemd-boot?

@RaitoBezarius
Copy link
Member

systemd-boot is not responsible for this, neither. This is an OEM problem with your firmware. You should contact your PC manufacturer and ask them to push a firmware update that includes a font with those glyphs.

@nikstur
Copy link
Member

nikstur commented Jun 9, 2024

We could consider implementing a "my firmware is bad" mode

The problem with these workarounds is that there's endless things we could address with hardly any ability to test it.

@RaitoBezarius
Copy link
Member

Well, here, the test is pretty trivial, you take EDK2, remove the font that contains a certain glyph, boot and observe garbled output, the test can confirm that we ASCII-ify things or whatever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants