Aren/rulimine
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
7465392191
rulimine/CONFIG.md
pitust 7465392191 fwcfg: document the features
2021-11-30 00:58:35 +01:00

14 KiB
Raw Blame History

Limine configuration file

Location of the config file

Limine scans for a config file on the boot drive. Every partition on the boot drive is scanned sequentially (first partition first, last partition last) for the presence of either a /limine.cfg, /boot/limine.cfg, or a /EFI/BOOT/limine.cfg file, in that order.

If no config file is found in the aforementioned locations, limine looks for the file on the fw_cfg interface called opt/org.limine-bootloader.config. If that is not present, limine enters the so-called "simple mode", where the kernel is loaded from opt/org.limine-bootloader.kernel, and, (if present), the background is loaded from opt/org.limine-bootloader.background.

Once the file is located, Limine will use it as its config file. Other possible candidates in subsequent partitions or directories are ignored.

It is thus imperative that the intended config file is placed in a location that will not be shadowed by another potentially candidate config file.

Structure of the config file

The Limine configuration file is comprised of assignments and entries. Comments begin in '#'.

Entries and sub-entries

Entries describe boot entries which the user can select in the boot menu.

An entry is simply a line starting with : followed by a newline-terminated string. Any locally assignable key that comes after it, and before another entry, or the end of the file, will be tied to the entry.

An entry can be a directory, meaning it can hold sub-entries. In order for an entry to become a directory, it needs to have a sub-entry following right after it.

A sub-entry is an entry with a number of : greater than 1 prepended to it. Each : represents 1 level deeper down the tree hierarchy of directories and entries.

Directories can be expanded (meaning they will not show up as collapsed in the menu) by default if a + is put between the :s and the beginning of the entry's name.

Assignments

Assignments are simple KEY=VALUE style assignments. VALUE can have spaces and = symbols, without requiring quotations. New lines are delimiters.

Some assignments are part of an entry (local), some other assignments are global. Global assignments can appear anywhere in the file and are not part of an entry, although usually one would put them at the beginning of the config. Some local assignments are shared between entries using any protocol, while other local assignments are specific to a given protocol.

Some keys take URIs as values; these are described in the next section.

Globally assignable keys are:

  • TIMEOUT - Specifies the timeout in seconds before the first entry is automatically booted. If set to no, disable automatic boot. If set to 0, boots default entry instantly (see DEFAULT_ENTRY key).
  • QUIET - If set to yes, enable quiet mode, where all screen output except panics and important warnings is suppressed. If TIMEOUT is not 0, the TIMEOUT still occurs, and pressing any key during the timeout will reveal the menu and disable quiet mode.
  • DEFAULT_ENTRY - 1-based entry index of the entry which will be automatically selected at startup. If unspecified, it is 1.
  • GRAPHICS - If set to yes, use a graphical framebuffer for the boot menu, else use text mode. Ignored with Limine UEFI, forced to yes.
  • MENU_RESOLUTION - Specify screen resolution to be used by the Limine menu in the form <width>x<height>. This will only affect the menu, not any booted OS. If not specified, Limine will pick a resolution automatically. If the resolution is not available, Limine will pick another one automatically. Ignored if GRAPHICS is not yes.
  • MENU_BRANDING - A string that will be displayed on top of the Limine menu.
  • MENU_BRANDING_COLOUR - A value between 0 and 7 specifying the colour of the branding string. Default is cyan (6).
  • MENU_BRANDING_COLOR - Alias of MENU_BRANDING_COLOUR.
  • MENU_FONT - URI path to a font file to be used instead of the default one for the menu and terminal. The font file must be a code page 437 character set comprised of 256 consecutive glyph bitmaps. Each glyph's bitmap must be expressed left to right (1 byte per row), and top to bottom (16 bytes per whole glyph by default; see MENU_FONT_SIZE). See e.g. the VGA text mode font collection for fonts.
  • TERMINAL_FONT - Alias of MENU_FONT.
  • MENU_FONT_SIZE - The size of the font in dots, which must correspond to the font file or the display will be garbled. Note that glyphs are always one byte wide, and columns over 8 are empty. Many fonts may be used in both 8- and 9-dot wide variants. Defaults to 8x16. Ignored if MENU_FONT or TERMINAL_FONT not set or if the font fails to load.
  • TERMINAL_FONT_SIZE - Alias of MENU_FONT_SIZE.
  • MENU_FONT_SCALE - Scaling for the font in the x and y directions. 2x2 would display the font in double size, which is useful on high-DPI displays at native resolution. 2x1 only makes the font twice as wide, similar to the VGA 40 column mode. 4x2 might be good for a narrow font on a high resolution display. Values over 8 are disallowed. Default is no scaling, i.e. 1x1.
  • TERMINAL_FONT_SCALE - Alias of MENU_FONT_SCALE.
  • MENU_FONT_SPACING - Horizontal spacing, in pixels, between glyphs on screen. It is equivalent to setting a font width of <specified width>+<this value>, except this value is preserved even in case font loading fails, and it also applies to the built-in Limine font. Defaults to 1. 0 is allowed.
  • TERMINAL_FONT_SPACING - Alias of MENU_FONT_SPACING.
  • THEME_COLOURS - Specifies the colour palette used by the terminal (AARRGGBB). It is a ; separated array of 10 colours: black, red, green, brown, blue, magenta, cyan, gray, background, and foreground respectively. While an alpha transparency value can be specified for every colour, it is ignored for all but background. Ignored if GRAPHICS is not yes.
  • THEME_COLORS - Alias of THEME_COLOURS.
  • THEME_BACKGROUND - Alias of the background value in THEME_COLOURS.
  • THEME_FOREGROUND - Alias of the foreground value in THEME_COLOURS.
  • THEME_BRIGHT_COLOURS - Specifies the bright colour palette used by the terminal (XXRRGGBB). It is a ; separated array of 8 bright colours: dark gray, bright red, bright green, yellow, bright blue, bright magenta, bright cyan, and white respectively. Alpha transparency values are ignored. Ignored if GRAPHICS is not yes.
  • THEME_BRIGHT_COLORS - Alias of THEME_BRIGHT_COLOURS.
  • THEME_MARGIN - Set the amount of margin around the terminal. Ignored if GRAPHICS is not yes.
  • THEME_MARGIN_GRADIENT - Set the thickness in pixel for the gradient around the terminal. Ignored if GRAPHICS is not yes.
  • BACKGROUND_PATH - URI where to find the background .BMP file. Ignored if GRAPHICS is not yes.
  • BACKGROUND_STYLE - The style which will be used to display the background image: tiled, centered, or stretched. Default is tiled.
  • BACKDROP_COLOUR - When the background style is centered, this specifies the colour of the backdrop for parts of the screen not covered by the background image, in RRGGBB format.
  • BACKDROP_COLOR - Alias of BACKDROP_COLOUR.
  • EDITOR_ENABLED - If set to no, the editor will not be accessible. Defaults to yes.
  • EDITOR_HIGHLIGHTING - If set to no, syntax highlighting in the editor will be disabled. Defaults to yes.
  • EDITOR_VALIDATION - If set to no, the editor will not alert you about invalid keys / syntax errors. Defaults to yes.
  • VERBOSE - If set to yes, print additional information during boot. Defaults to not verbose.
  • RANDOMISE_MEMORY - If set to yes, randomise the contents of RAM at bootup in order to find bugs related to non zeroed memory or for security reasons. This option will slow down boot time significantly.
  • RANDOMIZE_MEMORY - Alias of RANDOMISE_MEMORY.

Locally assignable (non protocol specific) keys are:

  • COMMENT - An optional comment string that will be displayed by the bootloader on the menu when an entry is selected.
  • PROTOCOL - The boot protocol that will be used to boot the kernel. Valid protocols are: linux, stivale, stivale2, chainload, multiboot or multiboot1 and multiboot2. If the protocol is omitted, Limine will try to autodetect it, following this list of protocols, in this order: stivale2 -> stivale1 -> multiboot2 -> multiboot1 -> linux -> failure.
  • CMDLINE - The command line string to be passed to the kernel. Can be omitted.
  • KERNEL_CMDLINE - Alias of CMDLINE.

Locally assignable (protocol specific) keys are:

  • Linux protocol:

    • KERNEL_PATH - The URI path of the kernel.
    • MODULE_PATH - The URI path to a module (such as initramfs).

    Note that one can define this last variable multiple times to specify multiple modules.

    • RESOLUTION - The resolution to be used. This setting takes the form of <width>x<height>x<bpp>. If the resolution is not available, Limine will pick another one automatically. Omitting <bpp> will default to 32.
    • TEXTMODE - If set to yes, prefer text mode. (BIOS only)

  • stivale and stivale2 protocols:

    • KERNEL_PATH - The URI path of the kernel.
    • MODULE_PATH - The URI path to a module.
    • MODULE_STRING - A string to be passed to a module.

    Note: One can define these 2 last variable multiple times to specify multiple modules. The entries will be matched in order. E.g.: The 1st module path entry will be matched to the 1st module string entry that appear, and so on.

    Note: If MODULE_STRING is not specified for an entry, the MODULE_STRING will default to the MODULE_PATH.

    • RESOLUTION - The resolution to be used should the kernel request a graphical framebuffer. This setting takes the form of <width>x<height>x<bpp> and overrides any resolution requested by the kernel, or automatic resolution requests. If the resolution is not available, Limine will pick another one automatically. Omitting <bpp> will default to 32.
    • KASLR - For relocatable kernels, if set to no, disable kernel address space layout randomisation. KASLR is enabled by default.
    • TEXTMODE - If set to yes, prefer text mode if the kernel has no video mode requirements. (Only for stivale2)

  • Chainload protocol on BIOS:

    • DRIVE - The 1-based BIOS drive to chainload.
    • PARTITION - The 1-based BIOS partition to chainload, if omitted, chainload drive.

  • Chainload protocol on UEFI:

    • IMAGE_PATH - URI of the EFI application to chainload.
    • RESOLUTION - The resolution to be used. This setting takes the form of <width>x<height>x<bpp>. If the resolution is not available, Limine will pick another one automatically. Omitting <bpp> will default to 32.

  • multiboot1 and multiboot2 protocols:

    • KERNEL_PATH - The URI path of the kernel.
    • MODULE_PATH - The URI path to a module.
    • MODULE_STRING - A string to be passed to a module.

    Note that one can define these 2 last variable multiple times to specify multiple modules. The entries will be matched in order. E.g.: the 1st module path entry will be matched to the 1st module string entry that appear, and so on.

    • RESOLUTION - The resolution to be used should the kernel request a graphical framebuffer. This setting takes the form of <width>x<height>x<bpp> and overrides any resolution requested by the kernel. If the resolution is not available, Limine will pick another one automatically. Omitting <bpp> will default to 32.

URIs

A URI is a path that Limine uses to locate resources in the whole system. It is comprised of a resource, a root, and a path. It takes the form of:

resource://root/path

The format for root changes depending on the resource used.

A resource can be one of the following:

  • boot - If booted off PXE this is an alias of tftp. Else the root is the 1-based decimal value representing the partition on the boot drive (values of 5+ for MBR logical partitions). If omitted, the partition containing the configuration file on the boot drive is used. For example: boot://2/... will use partition 2 of the boot drive and boot:///... will use the partition containing the config file on the boot drive.
  • hdd - Hard disk drives. The root takes the form of drive:partition; for example: hdd://3:1/... would use hard drive 3, partition 1. Partitions and drives are both 1-based (partition values of 5+ for MBR logical partitions). Omitting the partition is possible; for example: hdd://2:/.... Omitting the partition will access the entire volume instead of a specific partition (useful for unpartitioned media).
  • odd - Optical disk drives (CDs/DVDs/...). The root takes the form of drive:partition; for example: odd://3:1/... would use optical drive 3, partition 1. Partitions and drives are both 1-based (partition values of 5+ for MBR logical partitions). Omitting the partition is possible; for example: odd://2:/.... Omitting the partition will access the entire volume instead of a specific partition (useful for unpartitioned media, which is often the case for optical media).
  • guid - The root takes the form of a GUID/UUID, such as guid://736b5698-5ae1-4dff-be2c-ef8f44a61c52/.... The GUID is that of either a filesystem, when available, or a GPT partition GUID, when using GPT, in a unified namespace.
  • uuid - Alias of guid.
  • tftp - The root is the IP address of the tftp server to load the file from. If the root is left empty (tftp:///...) the file will be loaded from the server Limine booted from. This resource is only available when booting off PXE.
  • fwcfg - The root must be empty. The path refers to a fw_cfg filename to be loaded. The canonical place to put fw_cfg files is in the opt/fqdn.<name> namespace.

A URI can optionally be prefixed by a $ character to indicate that the file pointed to be the URI is a gzip-compressed payload to be uncompressed on the fly. E.g.: $boot:///somemodule.gz.