Bug 489892

Summary: No GDM with nomodeset
Product: [Fedora] Fedora Reporter: Saikat Guha <sg266>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: ajax, awilliam, mcepl, xgl-maint
Target Milestone: ---Flags: mcepl: needinfo? (sg266)
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-28 07:27:14 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
/var/log/messages none

Description Saikat Guha 2009-03-12 09:55:16 EDT
Graphical boot not reached with nomodeset kernel option set.

Test https://fedoraproject.org/wiki/QA:Testcase_intelvideo_nokms



Comment 1 Saikat Guha 2009-03-12 09:55:57 EDT
Created attachment 334928 [details]
Comment 2 Saikat Guha 2009-03-12 09:57:01 EDT
Created attachment 334929 [details]
Comment 3 Adam Williamson 2009-04-16 19:09:16 EDT
Does it work when modesetting *is* enabled?

If so, we wouldn't actually worry too much: modesetting is the default now. Really, the nomodeset test case only exists to cover the situation where it fails with modesetting but works without - that way, we know the bug is in the modesetting code somewhere. It's a kinda 'backstop' test case :)

Fedora Bugzappers volunteer triage team
Comment 4 Saikat Guha 2009-04-16 20:04:02 EDT
(In reply to comment #3)
> Does it work when modesetting *is* enabled?

Depends on your definition of "work". With modesetting enabled GDM does come up, but the display stops working if the user sneezes:
- http://bugs.freedesktop.org/show_bug.cgi?id=21230
- bug 489907
- bug 473347
- bug 489938

Manually setting Xorg driver to "vesa" and modesetting to disabled fixes all the above issues. But then there is no acceleration obviously.  

So basically, cannot enable modesetting, nor disable modesetting.
Comment 5 Adam Williamson 2009-04-17 12:27:48 EDT
OK, but this particular bug doesn't trigger. Thanks. Just useful for prioritization: we would likely rather work on the bugs in the KMS case, then.

Fedora Bugzappers volunteer triage team
Comment 6 Saikat Guha 2009-04-24 02:07:40 EDT
For anyone running into this bug while using nomodeset on an intel chip, a workaround is to add
   Option      "AccelMethod" "exa"
to the Device section in /etc/X11/xorg.conf. A new xorg config file can be created with
   Xorg -configure :1
Comment 7 Bug Zapper 2009-06-09 08:09:25 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 9 Matěj Cepl 2009-11-05 13:22:52 EST
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Comment 10 Matěj Cepl 2010-02-26 07:25:57 EST
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Comment 11 Bug Zapper 2010-04-27 09:09:57 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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: 
Comment 12 Bug Zapper 2010-06-28 07:27:14 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.