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.
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.
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
- Prepare a live image to be tested, or an installer image allowing to install the graphical desktop of choice.
How to test
- At the initial boot screen, check that there is a menu item for booting into a basic graphics mode (usually under the Troubleshooting menu).
- Boot into the basic graphics mode.
- 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.
- 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 aDriver: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.
- 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 simpledrmor 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.
- Run the installer.
- In a netinst-style (non-Live) installer environment, press Alt+Right arrow repeatedly until you find the graphical session again.
- Proceed with installation.
- Boot the newly installed system.
- Start a terminal application and verify that the system has been configured to boot with a
nomodesetkernel 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.
- Repeat steps 4 and 5 to verify that your installed system isn't using a native hardware driver.
Expected Results
- Both the installer environment and the installed desktop must use a fallback graphics driver instead of a native hardware driver.