Bug 600892

Summary: Xorg fails to start on "Intel Corporation 82G33/G31" when kernel is booted with 'nomodeset' option
Product: [Fedora] Fedora Reporter: sudheer <sudheer.divakaran>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: ajax, anton, awilliam, bskeggs, dougsland, gansalmon, itamar, jonathan, kernel-maint, peterscott, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: ia64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-25 21:16:35 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 Flags
xserver log none

Description sudheer 2010-06-06 14:55:00 UTC 
Created attachment 421605 [details]
xserver log

Description of problem:

I have installed FC13 (x64) but X Server fails to start on my machine having "Intel Corporation 82G33/G31" Integrated Graphics Controller when the kernel is booted with 'nomodeset option'. When I realised that 'nomodeset' option in grub.conf was causing the issue so removed it and the X server started functioning.

Please find the attachment Xorg.0.log

My smolt id is

http://www.smolts.org/client/show/pub_f2d9c681-9168-4d4a-93d7-ba470a580124




Version-Release number of selected component (if applicable):

Fedora 13 x64 : xorg-x11-drv-intel-2.11.0-4.fc13.x86_64



Steps to Reproduce:
1. Edit grub.conf & add nomodeset to the kernel option list

  
Actual results:


Expected results:

X server will not start

Additional info:
Comment 1 Adam Williamson 2010-06-07 13:54:18 UTC 
this is expected and intended behaviour in F13, the use of nomodeset is no longer supported with the intel driver.

perhaps we should make the 'nomodeset' option a no-op with intel and nouveau, and print a warning in logs somewhere? re-assigning to kernel with ajax and ben CC'ed for input.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 2 Adam Williamson 2010-06-07 14:01:43 UTC 
*** Bug 600949 has been marked as a duplicate of this bug. ***
Comment 3 Ben Skeggs 2010-06-07 22:20:21 UTC 
I guess we could have some kind of message printed in the logs somewhere, I'd like to keep "nomodeset" however, as it's very useful in those situations where we fail to initialise the display for whatever reason.
Comment 4 Adam Williamson 2010-06-09 18:46:49 UTC 
I'm not sure what you mean...how is it useful, when the X driver can't work with it? What's the point of loading nouveau with nomodeset versus just not loading it at all? Does it help for diagnostics somehow?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 5 Adam Williamson 2010-06-09 18:48:00 UTC 
Or do you just mean that it makes handling the situation easier for users, because it's easier to just put in 'nomodeset' than it is to actually disable the module?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 6 Adam Jackson 2010-10-25 21:16:35 UTC 
We should fall back to vesa magically when you say "nomodeset" now.