From Fedora Project Wiki

(855824)
(tag as associated with release criteria)
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:Associated_release_criterion|Basic|expected-image-boot-behavior}}
{{Template:Associated_release_criterion|Final|basic-graphics-mode}}
{{QA/Test_Case
{{QA/Test_Case
|description=This is to verify that Fedora can be installed in a safe graphics mode, using highly compatible video driver called ''vesa''.
|description=This is to verify that Fedora can be installed in a safe graphics mode, using highly compatible video driver.
{{admon/important|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=
|setup=
# Prepare any media for booting the installer
# Prepare any media for booting the installer
Line 10: Line 14:
<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.  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 systems or [https://lists.fedoraproject.org/pipermail/test/2013-July/116918.html ''efifb / fbdev'' driver on UEFI systems].  Confirm driver usage by inspecting <code>journalctl -ab</code> (GNOME), {{filename|/var/log/Xorg.0.log}} (KDE and other desktops) or {{filename|/tmp/X.log}} (non-live 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 22: Line 28:
[    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>, it indicates you are using the correct driver.</li>
<li>on UEFI systems</li>
{{admon/note|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 [https://bugzilla.redhat.com/show_bug.cgi?id{{=}}855824 bug 855824]}}
<pre>
<li>The installed system should contain {{filename|/etc/X11/xorg.conf}} or {{filename|/etc/X11/xorg.conf.d/XX-somename.conf}} file which specifies the ''vesa'' driver in the <code>Device</code> section</li>
[    34.947] (II) [KMS] drm report modesetting isn't supported.
{{admon/note|Fix in progress|This requirement might not be satisfied until we solve [https://bugzilla.redhat.com/show_bug.cgi?id{{=}}858270 bug 858270]}}
[    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>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>
<li>When X starts on the installed system, it should be using the ''vesa'' driver.  Confirm by checking {{filename|/var/log/Xorg.0.log}} for similar output to the above from the installer</li>
<li>When X starts on the installed system, it should be using the ''vesa'' (on BIOS) or ''fbdev'' (on UEFI) driver.  Confirm by checking <code>journalctl -ab</code> (GNOME) or {{filename|/var/log/Xorg.0.log}} (KDE and other desktops) for similar output to the above from the installer</li>
</ol>
</ol>
}}
}}


[[Category:User Interface]]
[[Category:User Interface]]

Revision as of 01:33, 3 April 2019

Note.png
Associated release criterion
This test case is associated with the Basic_Release_Criteria#expected-image-boot-behavior release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
Note.png
Associated release criterion
This test case is associated with the Fedora_40_Final_Release_Criteria#basic-graphics-mode release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


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 systems or efifb / fbdev driver on UEFI systems. Confirm driver usage by inspecting journalctl -ab (GNOME), /var/log/Xorg.0.log (KDE and other desktops) or /tmp/X.log (non-live 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 (on BIOS) or fbdev (on UEFI) driver. Confirm by checking journalctl -ab (GNOME) or /var/log/Xorg.0.log (KDE and other desktops) for similar output to the above from the installer
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Anaconda_User_Interface_Basic_Video_Driver&oldid=539415"