QA:Testcase Anaconda User Interface Basic Video Driver

Description

This is to verify that Fedora can be installed in a safe graphics mode, using highly compatible video driver called vesa.

Setup

1. Prepare any media for booting the installer

How to test

1. Boot the installer using a safe graphics mode. There is a special menu item for this at the initial boot screen, usually under Troubleshooting menu.
2. Proceed with installation
3. Boot the new system

Expected Results

vesa might not be supported on UEFI systems
Since UEFI systems cannot rely on vesa support, its alternative, called GOP, should be used instead. GOP is handled by efifb driver (see test mailing list). But most UEFI systems will still probably use vesa for basic video driver.

.

1. There is a special menu item at the initial boot screen to boot the installer in a safe graphics mode
2. The graphical installer displays properly and uses the vesa driver. Confirm driver usage by inspecting /var/log/Xorg.0.log or /tmp/X.log (depending on your install media). You should see output similar to the following:

   [    71.321] (II) VESA(0): initializing int10
   [    71.325] (II) VESA(0): Primary V_BIOS segment is: 0xc000
   [    71.326] (II) VESA(0): VESA BIOS detected
   [    71.326] (II) VESA(0): VESA VBE Version 2.0
   [    71.326] (II) VESA(0): VESA VBE Total Mem: 4096 kB
   [    71.326] (II) VESA(0): VESA VBE OEM: VGABIOS Cirrus extension
   [    71.326] (II) VESA(0): VESA VBE OEM Software Rev: 1.0
   [    71.326] (II) VESA(0): VESA VBE OEM Vendor: VGABIOS Cirrus extension
   [    71.326] (II) VESA(0): VESA VBE OEM Product: VGABIOS Cirrus extension
   [    71.326] (II) VESA(0): VESA VBE OEM Product Rev: 1.0

   If there are many lines containing (II) VESA(0):, it indicates you are using the correct driver.

Vesa not used in virtual machines
In virtual machines it is possible that a different driver will be used, e.g. qxl. This is described in bug 855824
3. The installed system should contain /etc/X11/xorg.conf or /etc/X11/xorg.conf.d/XX-somename.conf file which specifies the vesa driver in the Device section

Fix in progress
This requirement might not be satisfied until we solve bug 858270
4. The installed system should contain nomodeset keyword specified in the kernel boot line. You can check by inspecting /proc/cmdline and /boot/grub2/grub.cfg.
5. When X starts on the installed system, it should be using the vesa driver. Confirm by checking /var/log/Xorg.0.log for similar output to the above from the installer