Bug 1036016

Summary: xorg fallback to vesa instead of intel driver for 945GSE
Product: [Fedora] Fedora Reporter: Stefan Assmann <sassmann>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: airlied, ajax, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-01 23:07:56 UTC Type: Bug
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 Flags
xorg.0.log
none
dmesg
none
lspci none

Description Stefan Assmann 2013-11-29 08:20:50 UTC
Created attachment 830516 [details]
xorg.0.log

Description of problem:
Using an atom based system, xorg uses vesa instead of intel driver.

lspci -nn
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.21.12-2.fc19.i686
xorg-x11-server-Xorg-1.14.4-3.fc19.i686

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
uses vesa

Expected results:
uses intel driver

Comment 1 Stefan Assmann 2013-11-29 08:21:30 UTC
Created attachment 830517 [details]
dmesg

Comment 2 Stefan Assmann 2013-11-29 08:22:18 UTC
Created attachment 830518 [details]
lspci

Comment 3 Stefan Assmann 2013-11-29 08:23:51 UTC
Tried to force the intel driver with
Section "Device"
        Driver     "intel"
EndSection
didn't work. Driver doesn't find the hardware.

Comment 4 Dave Airlie 2013-12-01 23:07:56 UTC
remove the nomodeset from your kernel command line.

Comment 5 Stefan Assmann 2013-12-02 07:55:17 UTC
Hi Dave,
thanks for the notice. I wonder why the nomodeset is there in the first place. It must have been placed there during installation as I didn't add it myself.

Comment 6 Dave Airlie 2013-12-02 21:57:36 UTC
forced text mode or safe video mode install perhaps?

Comment 7 Stefan Assmann 2013-12-03 07:38:42 UTC
Ah, I've installed with safe video mode IIRC. I thought that shouldn't affect the installed system but obviously I've been mistaken. Thanks a lot Dave.