Bug 810663

Summary: N10 detected as vesa and fails with 'no screens found' - it should have detected intel which works
Product: [Fedora] Fedora Reporter: Mads Kiilerich <mads>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: 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-02-13 08:20: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
messages, booted without X config, then X config created and prefdm restarted
none
X log, no config, failing
none
X log, intel config, works none

Description Mads Kiilerich 2012-04-07 21:44:46 UTC
Created attachment 575971 [details]
messages, booted without X config, then X config created and prefdm restarted

On a Dell Inspiron Mini 1018 A2 video doesn't work out of the box. KMS works but it fails to start X.

It works fine after creating a simple /etc/X11/xorg.conf.d/01-video.conf 
Section "Device"
	Identifier  "Card0"
	Driver      "intel"
EndSection

I would expect that to happen automatically.

http://www.smolts.org/client/show/pub_a1dce481-611b-4273-abdd-0c400589e41a

Comment 1 Mads Kiilerich 2012-04-07 21:45:34 UTC
Created attachment 575972 [details]
X log, no config, failing

Comment 2 Mads Kiilerich 2012-04-07 21:46:12 UTC
Created attachment 575973 [details]
X log, intel config, works

Comment 3 Adam Jackson 2012-04-09 17:24:17 UTC
(In reply to comment #1)
> Created attachment 575972 [details]
> X log, no config, failing

No, that's not "no config".  It even says so:

[    30.358] (==) Using config file: "/etc/X11/xorg.conf"

What content does xorg.conf have when this happens?

Comment 4 Fedora End Of Life 2013-01-16 10:04:35 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 08:21:17 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.