QA:Testcase Anaconda User Interface Basic Video Driver

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(try to update for UEFI and remove xdriver=vesa expectations per latest discussion with ajax (rhbz 1009828))
Line 11: Line 11:
 
<ol>
 
<ol>
 
<li>There is a special menu item at the initial boot screen to boot the installer in a safe graphics mode</li>
 
<li>There is a special menu item at the initial boot screen to boot the installer in a safe graphics mode</li>
<li>The graphical installer displays properly and uses the ''vesa'' driver (or alternatively ''fbdev'' on certain UEFI systems).  Confirm driver usage by inspecting {{filename|/var/log/Xorg.0.log}} or {{filename|/tmp/X.log}} (depending on your install media).  You should see output similar to the following:
+
<li>The graphical installer displays properly and uses the ''vesa'' driver on BIOS sytems or ''efifb / fbdev'' driver on UEFI systems (see [https://lists.fedoraproject.org/pipermail/test/2013-July/116918.html test mailing list]).  Confirm driver usage by inspecting {{filename|/var/log/Xorg.0.log}} or {{filename|/tmp/X.log}} (depending on your install media).  You should see output similar to the following:
 +
<ul>
 +
<li>on BIOS systems</li>
 
<pre>
 
<pre>
 
[    71.321] (II) VESA(0): initializing int10
 
[    71.321] (II) VESA(0): initializing int10
Line 23: Line 25:
 
[    71.326] (II) VESA(0): VESA VBE OEM Product: 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</pre>
 
[    71.326] (II) VESA(0): VESA VBE OEM Product Rev: 1.0</pre>
If there are many lines containing <code>(II) VESA(0):</code> (or <code>fbdev</code>), it indicates you are using the correct driver.
+
<li>on UEFI systems</li>
{{admon/note|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 / fbdev'' driver (see [https://lists.fedoraproject.org/pipermail/test/2013-July/116918.html test mailing list]). But most UEFI systems will still probably use vesa for basic video driver.}}
+
<pre>
 +
[    34.947] (II) [KMS] drm report modesetting isn't supported.
 +
[    34.947] (WW) Falling back to old probe method for modesetting
 +
[    34.947] (II) Loading sub module "fbdevhw"
 +
[    34.947] (II) LoadModule: "fbdevhw"
 +
[    34.947] (**) FBDEV(2): claimed PCI slot 1@0:0:0
 +
[    34.947] (II) FBDEV(2): using default device
 +
[    34.948] (II) FBDEV(0): Creating default Display subsection in Screen section
 +
"Default Screen Section" for depth/fbbpp 24/32</pre>
 +
</ul>
 +
If there are many lines containing <code>(II) VESA(0):</code> or <code>FBDEV</code>, it indicates you are using the correct driver.
 
</li>
 
</li>
 
<li>The installed system should contain <code>nomodeset</code> keyword specified in the kernel boot line. You can check by inspecting {{filename|/proc/cmdline}} and {{filename|/boot/grub2/grub.cfg}}.</li>
 
<li>The installed system should contain <code>nomodeset</code> keyword specified in the kernel boot line. You can check by inspecting {{filename|/proc/cmdline}} and {{filename|/boot/grub2/grub.cfg}}.</li>

Revision as of 12:49, 20 November 2013

Contents

Description

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

Important.png
Bare metal only
This test case has to be tried on a bare metal system only. We need to ensure that users can boot even with not well supported graphics cards. Graphics is usually not a problem in virtual machines and therefore VM testing is not beneficial here. Please use bare metal system.

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

  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 on BIOS sytems or efifb / fbdev driver on UEFI systems (see test mailing list). 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:
    • on BIOS systems
    • [    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
    • on UEFI systems
    • [    34.947] (II) [KMS] drm report modesetting isn't supported.
      [    34.947] (WW) Falling back to old probe method for modesetting
      [    34.947] (II) Loading sub module "fbdevhw"
      [    34.947] (II) LoadModule: "fbdevhw"
      [    34.947] (**) FBDEV(2): claimed PCI slot 1@0:0:0
      [    34.947] (II) FBDEV(2): using default device
      [    34.948] (II) FBDEV(0): Creating default Display subsection in Screen section
      	"Default Screen Section" for depth/fbbpp 24/32

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

  3. 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.
  4. When X starts on the installed system, it should be using the vesa (or fbdev) driver. Confirm by checking /var/log/Xorg.0.log for similar output to the above from the installer