Test Day:2009-04-09 UEFI

What to test?

Today's installment of Fedora Test Day will focus on Features/EFI. The objective is to verify that affected components (ie, grub, kernel, efibootmgr) provide the expected UEFI functionality on appropriate hardware (ie, it locates devices, installs, and boots). Fedora 11's UEFI 2.1 implementation has been tested on Intel UEFI-capable systems only; those with access to other vendors UEFI-capable systems are actively solicited to validate their hardware.

Supported Architectures currently are X86 and X86_64. No Fedora 11 compose of IA64 is available.

Who's available

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

Person	Timezone
Peter Jones (developer)	UTC-4
Brian Maly (developer)	UTC-4
Bhavna Sarathy (developer)	UTC-4
James Laska (tester)	UTC-4
Chris Ward (tester)	UTC+2
Martin Koci (tester)	UTC+2
Charles Rose (tester)	UTC+5:30
Liam (tester)	UTC+8
Juan Rodriguez (tester)	UTC-5

Normal practice is to find these people on #fedora-qa for assistance. Note that these folks are based in the eastern US and in Brno, Czech Republic. We are trying to find coverage for other timezones such as China, India. Testers in those locations can send questions by email if help is not available on IRC.

What's Needed To Test

Required for testing Features/EFI:

• Rawhide or Fedora 11 Beta fully updated.
• A system capable of testing Features/EFI support
• A Red Hat Bugzilla account.

Optional but recommended for testing Features/EFI:

• FAS Account - you can create an account in 3 minutes if you don't have one. This account lets you make non-anonymous contributions to the Fedora wiki.
• Your hardware profile uploaded to Smolt according to these instructions

Rawhide is raw
Rawhide is a development branch of Fedora. While changes to Fedora post-beta are limited, it is advised you back up your data before participating.

How To Test

Testing will require using a system running Rawhide. There are several methods available for updating your system to rawhide. The following sections outline two methods.

Download Media

Some tests will require that you download a boot.iso from Rawhide or F-11-Beta for your architecture.

Rawhide	Fedora 11 Beta
i386	i386
x86_64	x86_64

Alternatively, you may download a efidisk.img from Rawhide or F-11-Beta for your architecture.

Rawhide	Fedora 11 Beta
i386	i386
x86_64	x86_64

Testing

Perform each of the following test cases:

Boot tests

The following tests do not depend on having a running Beta or rawhide system. They need only boot media (or PXE), whose images can be downloaded from daily rawhide, for instance. In the case of Apple Macintosh hardware with Intel CPU, this is good because it is difficult to complete a successful install of Fedora 11 Beta; for instance: BZ 444490 or 494390.

1. QA:Testcase_UEFI_boot.iso
2. QA:Testcase_efidisk.img
3. QA:Testcase_UEFI_pxeboot
4. QA:Testcase_2TB_Storage_Device
5. QA:Testcase_At_Least_10_Storage_Devices

Updates required
Due to a bug in anaconda, the use of an updates image is required to complete an installation. Anaconda fixes for UEFI testing will be added to http://clumens.fedorapeople.org/updates.img. To use the updates.img, you must boot with the following option:

updates=http://clumens.fedorapeople.org/updates.img

Report your results

If you have problems with any of the tests, report a bug to Bugzilla. If you are unsure about exactly how to file the report, just ask on IRC and we will help you.

NDA Hardware?
If testing on hardware not yet released, you may desire to set the appropriate confidential privacy flag on your bug.

Once you have completed the tests, add your results to the Results table below.

The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to your Smolt hardware profile (see above for a link with instructions on submitting your hardware profile to Smolt). For each test case, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, as a link to the bug report for the failure. If you could not perform one test (for example, you cannot perform the more advanced tests because the basic one fails, or you cannot perform the multihead test as you have only one display), enter the word N/A. In the comments column, enter any additional information that is related to your testing.

Results

User	Smolt Profile	boot.iso	efidisk.img	pxeboot	2TB	10 devices	Comments
User:SampleUser
Baybal Ni		efi executes ok, but the kernel itself fails
James Laska		FAIL	FAIL				Can't boot efidisk.img USB directly from BIOS, can only boot from EFI shell
Mildred	Smolt profile	N/A	N/A	N/A	N/A	N/A	with KMS, the framebuffer works as well as plymouth, xorgs freeze the system completely (fixed image on the screen). With nomodeset, the framebuffer is jammed, xorg makes the screen backlight blink and stops eventually. CTRL-ALT-DEL works to reboot the system. Bug
Juan Rodriguez			Worked				Used Fedora 11 Beta, booting from USB.
Charles Rose	PowerEdge R710		PASS