Bug 623961
Summary: | The installed system is not configured with boot command: xdriver=vesa after installing with basic video driver | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | He Rui <rhe> | ||||||
Component: | xorg-x11-drv-vesa | Assignee: | X/OpenGL Maintenance List <xgl-maint> | ||||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 14 | CC: | awilliam, clydekunkel7734, kparal, xgl-maint | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2010-08-17 08:33:12 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
He Rui
2010-08-13 09:46:46 UTC
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! |