From Fedora Project Wiki

(cosmetic changes)
m (current hardware uses amdgpu and not radeon kernel driver, update the instructions)
 
(8 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.
|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
# Prepare a live image to be tested, or an installer image allowing to install the graphical desktop of choice.
|actions=
|actions=
# 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.
# Proceed with installation
# 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 {{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> 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 a netinst-style (non-Live) installer environment, use ''Ctrl+Alt+F2'' to switch to a virtual terminal.</ul>
<pre>
<li> Run the following command to verify that the system has been started with a <code>nomodeset</code> kernel boot argument:
[    71.321] (II) VESA(0): initializing int10
<pre>$ grep nomodeset /proc/cmdline
[   71.325] (II) VESA(0): Primary V_BIOS segment is: 0xc000
BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-38-20230326-n-1 rd.live.image nomodeset quiet rhgb</pre>
[    71.326] (II) VESA(0): VESA BIOS detected
If this doesn't print anything, it means it wasn't configured properly, please report a bug. <br/>
[    71.326] (II) VESA(0): VESA VBE Version 2.0
Note: Other keywords might differ on your system from the example above. We're only concerned about the presence of the specified argument here.
[    71.326] (II) VESA(0): VESA VBE Total Mem: 4096 kB
<li> If you booted the image in a BIOS mode (not UEFI), additionally verify that the system has been started with a <code>vga=791</code> kernel boot argument:
[    71.326] (II) VESA(0): VESA VBE OEM: VGABIOS Cirrus extension
<pre>$ grep vga=791 /proc/cmdline
[    71.326] (II) VESA(0): VESA VBE OEM Software Rev: 1.0
BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-38-20230326-n-1 rd.live.image nomodeset vga=791 quiet rhgb</pre>
[   71.326] (II) VESA(0): VESA VBE OEM Vendor: VGABIOS Cirrus extension
If this doesn't print anything, it means it wasn't configured properly, please report a bug.
[   71.326] (II) VESA(0): VESA VBE OEM Product: VGABIOS Cirrus extension
<li> Run the following command to display properties of your graphics card and see if there's any <code>Driver:</code> line present:
[    71.326] (II) VESA(0): VESA VBE OEM Product Rev: 1.0</pre>
<pre>$ lspci -kvmm | sed -n '/VGA/,/^$/p'
<li>on UEFI systems</li>
Class: VGA compatible controller
<pre>
Vendor: Intel Corporation
[   34.947] (II) [KMS] drm report modesetting isn't supported.
Device: CometLake-H GT2 [UHD Graphics]
[    34.947] (WW) Falling back to old probe method for modesetting
SVendor: Lenovo
[    34.947] (II) Loading sub module "fbdevhw"
SDevice: Device 22c2
[    34.947] (II) LoadModule: "fbdevhw"
Rev: 05
[   34.947] (**) FBDEV(2): claimed PCI slot 1@0:0:0
Module: i915</pre>
[    34.947] (II) FBDEV(2): using default device
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:
[    34.948] (II) FBDEV(0): Creating default Display subsection in Screen section
<pre>Driver: i915</pre>
"Default Screen Section" for depth/fbbpp 24/32</pre>
then you're running with a native hardware driver (in this case, ''i915''; other most common drivers include ''amdgpu'' and ''nouveau''). In this case, the fallback graphics were not started properly, please report a bug.
</ul>
<li> Run the following command and see which drivers were initialized during boot:
If there are many lines containing <code>(II) VESA(0):</code> or <code>FBDEV</code>, it indicates you are using the correct driver.
<pre>$ journalctl -k | grep -F '[drm] Initialized'
</li>
jun 10 09:48:08 hydra kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0</pre>
<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>
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:
<li>When X starts on the installed system, it should be using the ''vesa'' (on BIOS) or ''fbdev'' (on UEFI) driver. Confirm by checking {{filename|/var/log/Xorg.0.log}} for similar output to the above from the installer</li>
<pre>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</pre>
(in this case ''i915''; or ''amdgpu'', ''nouveau'', etc), then please report a bug.
<li> Run the installer.
<ul><li>In a netinst-style (non-Live) installer environment, press ''Alt+Right arrow'' repeatedly until you find the graphical session again.</ul>
<li> Proceed with installation.
<li> Boot the newly installed system.
<li> Repeat steps 4 to 7 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]]

Latest revision as of 12:19, 24 January 2024

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.
Associated release criterion
This test case is associated with the Fedora_42_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.

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 a netinst-style (non-Live) installer environment, use Ctrl+Alt+F2 to switch to a virtual terminal.
  4. Run the following command to verify that the system has been started with a nomodeset kernel boot argument: 
    $ grep nomodeset /proc/cmdline
 BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-38-20230326-n-1 rd.live.image nomodeset quiet rhgb

    If this doesn't print anything, it means it wasn't configured properly, please report a bug.
    Note: Other keywords might differ on your system from the example above. We're only concerned about the presence of the specified argument here.

  5. If you booted the image in a BIOS mode (not UEFI), additionally verify that the system has been started with a vga=791 kernel boot argument: 
    $ grep vga=791 /proc/cmdline
BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-38-20230326-n-1 rd.live.image nomodeset vga=791 quiet rhgb

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

  6. 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 amdgpu and nouveau). In this case, the fallback graphics were not started properly, please report a bug.

  7. 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 amdgpu, nouveau, etc), then please report a bug.

  8. Run the installer.
    • In a netinst-style (non-Live) installer environment, press Alt+Right arrow repeatedly until you find the graphical session again.
  9. Proceed with installation.
  10. Boot the newly installed system.
  11. Repeat steps 4 to 7 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=699246"