efi_printk(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– efi_printk(9) β€” the Kernel API Manual page where your fave EFI stub printk lives ✨

okay so bestie, welcome to efi_printk(9) from the Kernel API Manual β€” yes the whole manual, and yes this function is basically the EFI stub's little messenger goblin 🧚 that sends your kernel message out into the world. lowkey iconic.


🌸 NAME 🌸

efi_printk β€” print a kernel message πŸ’Œ


✨ SYNOPSIS ✨

int efi_printk (const char *fmt , ... );

like, that's the whole vibe. int in, characters out. slay.


πŸŽ€ ARGUMENTS πŸŽ€

  • fmt β€” the format string 🫢 the star of the show, the main character, the thing you're actually printing.
  • ... β€” variable arguments πŸ’… all the extra lil friends that get slotted into your format string. they're just vibing in the ellipsis.

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the tea β˜• β€” the first letter of the format string is what decides the logging level of the message. that's the whole trick, iykyk.

and the vibe check: if that level is less than the current EFI logging level, the message gets suppressed 😭 like, sorry bestie, not today, the filter said no.

also important and you gotta know it: the message will be truncated to 255 bytes. so don't come at it with a novel, it's giving short-form content only πŸ“

no cap, 255 bytes is the limit. write like it.

⭐ RETURN ⭐

returns the number of printed characters ✨ so you literally get receipts on how much got printed. obsessed.


πŸ”₯ SEE ALSO πŸ”₯


so yeah, that's the page πŸ’œ go forth, print your messages, respect the 255-byte limit, and remember that the first letter runs the whole show.

this has been ./drivers/firmware/efi/libstub (the path, the whole path) and the page is dated October 2026, from the same crew that brought you efi_printk(9) πŸ¦‹ bye bestie, mwah πŸ’…βœ¨

πŸ“¦ where this page comes from