Bug 1093737

Summary: Discrete Card not available to Desktop
Product: [Fedora] Fedora Reporter: Onyeibo Oku <twohotis>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rawhideCC: airlied, ajax, bskeggs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-04 05:25:43 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

Description Onyeibo Oku 2014-05-02 14:04:00 UTC
Created attachment 891824 [details]
Xorg.0.log

Description of problem:
After an update this morning, my machine can no longer get past gdm (no graphical desktop environment). A preliminary perusal of Xorg.0.log seems to suggest that the issue is associated with the second Card (discrete).  See attached log for details.  The Laptop spots two cards (a) Intel HD4000 and NVIDIA® GeForce® GT 635M with 2GB DDR3 VRAM. 

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

How reproducible:
I couldn't recreate the scenario because a downgrade was not possible (according to "dnf downgrade xxxx").  Otherwise, the log confirms the issue

Steps to Reproduce:
1. Upgrade Fedora 21 (rawhide) to the latest releases
2. Reboot
3. You will end up with a blank screen.  Level-3 works.  Running startx from level-3 throws an error and X exits

Actual results:
See step (3) above

Expected results:
The login screen should show next -OR- the desktop should show if 'startx' is issued from level-3

Additional info:
System Specs = ASUS N56VJ with NVIDIA® GeForce® GT 635M with 2GB DDR3 VRAM

Comment 1 Onyeibo Oku 2014-05-04 05:25:43 UTC
A recent update fixed this issue.  Apparently, it wasn't an xorg bug (suspecting Kernel or Gnome-shell).  False Alarm ... closing this