Description of problem: Install F14-Alpha-RC4 with the 2nd option:'install with basic video driver', complete installation, and reboot. Check grub.conf or /proc/cmdline, xdriver=vesa is not added as boot command. Version-Release number of selected component (if applicable): F14-Alpha-RC4 xorg-x11-drv-vesa-2.3.0-1.fc14 How reproducible: 100% Steps to Reproduce: 1. Install F14-Alpha-RC4 with the 2nd option:'install with basic video driver' 2. Reboot 3. Check grub.conf or /proc/cmdline Actual results: xdriver=vesa is not added as boot command Expected results: https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_Basic_Video_Driver
I believe this is a duplicated of bug #623129?
nomodeset has to be passed in order to get a graphical installer with: $ lspci | grep VGA 01:00.0 VGA compatible controller: ATI Technologies Inc RV630 [Radeon HD 2600 Series]
(In reply to comment #1) > I believe this is a duplicated of bug #623129? I tested F14-Alpha-RC4, it did use vesa driver during installation, but after reboot, when I checked the grub.conf, xdriver=vesa was not included.
Created attachment 438883 [details] tmp logs during install
Created attachment 438884 [details] logs after reboot to desktop
what's written in the test at present - "The installed system is configured with a boot argument: xdriver=vesa. This can be confirmed by inspecting /etc/grub.conf or /proc/cmdline on the installed system." - is not actually correct. This parameter is only considered by anaconda / live boot; it is *not* read by anything during boot of a normal installed system. To make the installed system use the vesa driver, anaconda should in fact have written a /etc/X11/xorg.conf file which specifies 'vesa' as the driver. Please check that it did so. If it did, then all is fine. James will update the test case.
(In reply to comment #6) > what's written in the test at present - "The installed system is configured > with a boot argument: xdriver=vesa. This can be confirmed by inspecting > /etc/grub.conf or /proc/cmdline on the installed system." - is not actually > correct. This parameter is only considered by anaconda / live boot; it is *not* > read by anything during boot of a normal installed system. > > To make the installed system use the vesa driver, anaconda should in fact have > written a /etc/X11/xorg.conf file which specifies 'vesa' as the driver. Please > check that it did so. If it did, then all is fine. James will update the test > case. Anaconda wrote this in /etc/X11/xorg.conf: Section "Device" Identifier "Videocard0" Driver "vesa" EndSection So that's why the installed system used vesa driver after reboot... Thanks Adam, then this is not a bug, and the expected result should remove the 'checking boot argument' and add this one instead?
Yes. I've already updated the test case, in fact. thanks!