From Fedora Project Wiki

Bootloader Test Day
Test-days-banner.svg

Date 2021-04-12 to 2021-04-13
Time all day

Website QA/Test Days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

This Test Day will focus on testing the new shim 15.4 and GRUB 2.06. This is an extremely important test day as the newly signed shim needs testing. Grub also gets an update and we would like to ensure that bootloaders works as intended.

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:

You can chat with us on IRC. See the infobox on top of the page to learn the right IRC channel.

Prerequisite for Test Day[edit]

  • Recommended: Media (USB flash drive, SD Card, or optical) imaged with any Fedora 32, 33, or 34 edition or spin ISO image, in case rescue is necessary.
  • x86_64 computers with UEFI firmware:
    • Media imaged with one of the special test day ISO images.
    • You do not need to have Fedora installed.
    • You do not need to test both images. Most folks will prefer the smaller netinstall image.
  • All other computers, including x86_64 with BIOS firmware, and arm/aarch64:
    • Either Fedora 33 or 34 installed and fully updated.

How to test?[edit]

There are prerequisites for this test day that you should gather before getting started:

  • Identify whether the firmware type for your computer is EFI/UEFI or BIOS by executing the following on terminal.
[ -d /sys/firmware/efi ] && echo UEFI || echo BIOS
mokutil --sb-state
  • Create an rescue USB stick, just in case.

Visit the results page and click on the column title links that correspond to your systems' firmware type. Column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for that test.

Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.

Reporting bugs[edit]

All bugs should be reported into Bugzilla, in most cases against the Grub component. If you are unsure about exactly how to file the report or what other information to include, just ask us on IRC (see instructions above).

Test Results[edit]

Test results will be exported here once the test day is over. See How to test? section for information how to submit results and see the live results.