Bug 1071545 - fails to start headless Xorg with radeon/nouveau driver and kernel modeset enabled
Summary: fails to start headless Xorg with radeon/nouveau driver and kernel modeset en...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-01 15:20 UTC by Fabrice Bellet
Modified: 2015-06-29 19:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 19:11:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
xorg config file (103 bytes, text/plain)
2014-03-01 15:20 UTC, Fabrice Bellet
no flags Details
Xorg.0.log file (6.31 KB, text/plain)
2014-03-01 15:21 UTC, Fabrice Bellet
no flags Details
dmesg output (68.66 KB, text/plain)
2014-03-01 15:22 UTC, Fabrice Bellet
no flags Details

Description Fabrice Bellet 2014-03-01 15:20:37 UTC
Created attachment 869386 [details]
xorg config file

Hi!

I'm trying to run a headless Xorg server. When I don't specify anything in an xorg.conf file, the vesa driver is used, and provides a headless 640x480 X server. But if I write in the xorg.conf file that I'd prefer to use the hardware dedicated driver instead of the vesa driver, Xorg fails to start, with this error in the kernel log :

[   42.837451] detected fb_set_par error, error code: -22
[   43.126197] detected fb_set_par error, error code: -22
[   43.255799] detected fb_set_par error, error code: -22

Comment 1 Fabrice Bellet 2014-03-01 15:21:46 UTC
Created attachment 869387 [details]
Xorg.0.log file

Comment 2 Fabrice Bellet 2014-03-01 15:22:46 UTC
Created attachment 869388 [details]
dmesg output

Comment 3 Fedora End Of Life 2015-05-29 11:06:44 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 4 Fedora End Of Life 2015-06-29 19:11:35 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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


Note You need to log in before you can comment on or make changes to this bug.