From Fedora Project Wiki

(adjust to also cover testing live images)
(we can rely on X11 logs any longer, because now even with nomodeset Wayland is used (on UEFI). Rewrite the whole test case with the best approach I could find.)
Line 3: Line 3:


{{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.
|description=This is to verify that Fedora can be installed in a basic 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.}}
{{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, or the live image to be tested.
# Prepare a live image to be tested, or an installer image allowing to install the graphical desktop of choice.
|actions=
|actions=
# Boot the installer or live image using a safe graphics mode. There is a special menu item for this at the initial boot screen, usually under ''Troubleshooting'' menu.
# Proceed with installation, launching the installer after boot if testing a live image.
# Boot the new system
|results=
<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> At the initial boot screen, check that there is a menu item for booting into a ''basic graphics mode'' (usually under the ''Troubleshooting'' menu).
<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:
<li> Boot into the basic graphics mode.
<ul>
<li> After booting into the desktop/installer, open a terminal application.
<li>on BIOS systems</li>
<ul><li>In the installer environment, use ''Ctrl+Alt+F2'' to switch to a virtual terminal.</ul>
<pre>
<li> Run the following command to display properties of your graphics card and see if there's any <code>Driver:</code> line present:
[    71.321] (II) VESA(0): initializing int10
<pre>$ lspci -kvmm | sed -n '/VGA/,/^$/p'
[    71.325] (II) VESA(0): Primary V_BIOS segment is: 0xc000
Class: VGA compatible controller
[    71.326] (II) VESA(0): VESA BIOS detected
Vendor: Intel Corporation
[   71.326] (II) VESA(0): VESA VBE Version 2.0
Device: CometLake-H GT2 [UHD Graphics]
[    71.326] (II) VESA(0): VESA VBE Total Mem: 4096 kB
SVendor: Lenovo
[    71.326] (II) VESA(0): VESA VBE OEM: VGABIOS Cirrus extension
SDevice: Device 22c2
[   71.326] (II) VESA(0): VESA VBE OEM Software Rev: 1.0
Rev: 05
[    71.326] (II) VESA(0): VESA VBE OEM Vendor: VGABIOS Cirrus extension
Module: i915</pre>
[    71.326] (II) VESA(0): VESA VBE OEM Product: VGABIOS Cirrus extension
If there's no <code>Driver:</code> line, everything is correct, you're almost certainly running under a fallback graphics driver like ''simpledrm'' or ''vesa''. If there's a <code>Driver:</code> line, for example:
[    71.326] (II) VESA(0): VESA VBE OEM Product Rev: 1.0</pre>
<pre>Driver: i915</pre>
<li>on UEFI systems</li>
then you're running with a native hardware driver (in this case, ''i915''; other most common drivers include ''radeon'' and ''nouveau''). In this case, the fallback graphics were not started properly, please report a bug.
<pre>
<li> As a second check, run the following command and see which drivers were initialized during boot:
[   34.947] (II) [KMS] drm report modesetting isn't supported.
<pre>$ journalctl -k | grep -F '[drm] Initialized'
[    34.947] (WW) Falling back to old probe method for modesetting
jun 10 09:48:08 hydra kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0</pre>
[    34.947] (II) Loading sub module "fbdevhw"
If you only see <code>Initialized simpledrm</code> or no line at all, you should be running on a fallback graphics driver correctly. If you see the initialization of a native hardware driver as well, for example:
[    34.947] (II) LoadModule: "fbdevhw"
<pre>jun 10 09:48:08 hydra kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
[   34.947] (**) FBDEV(2): claimed PCI slot 1@0:0:0
jun 10 09:48:09 hydra kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 1</pre>
[    34.947] (II) FBDEV(2): using default device
(in this case ''i915''; or ''radeon'', ''nouveau'', etc), then please report a bug.
[    34.948] (II) FBDEV(0): Creating default Display subsection in Screen section
<li> Run the installer.
"Default Screen Section" for depth/fbbpp 24/32</pre>
<ul><li>In the installer environment, press ''Alt+Right arrow'' repeatedly until you find the graphical session again.</ul>
</ul>
<li> Proceed with installation.
If there are many lines containing <code>(II) VESA(0):</code> or <code>FBDEV</code>, it indicates you are using the correct driver.
<li> Boot the newly installed system.
</li>
<li> Start a terminal application and verify that the system has been configured to boot with a <code>nomodeset</code> kernel boot argument:
<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>
<pre>$ grep nomodeset /proc/cmdline
<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>
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.17.14-300.fc36.x86_64 root=UUID=5f7d257e-ceaa-44f7-905f-1fa0ca4b1dbb ro rootflags=subvol=root rd.luks.uuid=luks-b3f3824c-d386-4c66-a69b-2833107b4390 nomodeset rhgb quiet</pre>
If this doesn't print anything, it means it wasn't configured properly, please report a bug.
<li> Repeat steps 4 and 5 to verify that your installed system isn't using a native hardware driver.
</ol>
</ol>
|results=
# Both the installer environment and the installed desktop must use a fallback graphics driver instead of a native hardware driver.
}}
}}


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

Revision as of 11:59, 10 June 2022

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_41_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 basic 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 a live image to be tested, or an installer image allowing to install the graphical desktop of choice.

How to test

  1. At the initial boot screen, check that there is a menu item for booting into a basic graphics mode (usually under the Troubleshooting menu).
  2. Boot into the basic graphics mode.
  3. After booting into the desktop/installer, open a terminal application.
    • In the installer environment, use Ctrl+Alt+F2 to switch to a virtual terminal.
  4. Run the following command to display properties of your graphics card and see if there's any Driver: line present: 
    $ lspci -kvmm | sed -n '/VGA/,/^$/p'
Class:	VGA compatible controller
Vendor:	Intel Corporation
Device:	CometLake-H GT2 [UHD Graphics]
SVendor:	Lenovo
SDevice:	Device 22c2
Rev:	05
Module:	i915

    If there's no Driver: line, everything is correct, you're almost certainly running under a fallback graphics driver like simpledrm or vesa. If there's a Driver: line, for example: 

    Driver: i915

    then you're running with a native hardware driver (in this case, i915; other most common drivers include radeon and nouveau). In this case, the fallback graphics were not started properly, please report a bug.

  5. As a second check, run the following command and see which drivers were initialized during boot: 
    $ journalctl -k | grep -F '[drm] Initialized'
jun 10 09:48:08 hydra kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0

    If you only see Initialized simpledrm or no line at all, you should be running on a fallback graphics driver correctly. If you see the initialization of a native hardware driver as well, for example: 

    jun 10 09:48:08 hydra kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
jun 10 09:48:09 hydra kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 1

    (in this case i915; or radeon, nouveau, etc), then please report a bug.

  6. Run the installer.
    • In the installer environment, press Alt+Right arrow repeatedly until you find the graphical session again.
  7. Proceed with installation.
  8. Boot the newly installed system.
  9. Start a terminal application and verify that the system has been configured to boot with a nomodeset kernel boot argument: 
    $ grep nomodeset /proc/cmdline
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.17.14-300.fc36.x86_64 root=UUID=5f7d257e-ceaa-44f7-905f-1fa0ca4b1dbb ro rootflags=subvol=root rd.luks.uuid=luks-b3f3824c-d386-4c66-a69b-2833107b4390 nomodeset rhgb quiet

    If this doesn't print anything, it means it wasn't configured properly, please report a bug.

  10. Repeat steps 4 and 5 to verify that your installed system isn't using a native hardware driver.

Expected Results

  1. Both the installer environment and the installed desktop must use a fallback graphics driver instead of a native hardware driver.
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Anaconda_User_Interface_Basic_Video_Driver&oldid=646796"