QA:Testcase Anaconda User Interface Basic Video Driver
This is to verify that Fedora can be installed in a safe graphics mode, using highly compatible video driver.
- Prepare any media for booting the installer
How to test
- 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
- There is a special menu item at the initial boot screen to boot the installer in a safe graphics mode
- 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
/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
- The installed system should contain
nomodesetkeyword specified in the kernel boot line. You can check by inspecting
- When X starts on the installed system, it should be using the vesa (on BIOS) or fbdev (on UEFI) driver. Confirm by checking
/var/log/Xorg.0.logfor similar output to the above from the installer
[ 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.