Bug 1093737 - Discrete Card not available to Desktop
Summary: Discrete Card not available to Desktop
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-02 14:04 UTC by Onyeibo Oku
Modified: 2014-05-04 05:25 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-04 05:25:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Xorg.0.log (26.00 KB, text/plain)
2014-05-02 14:04 UTC, Onyeibo Oku
no flags Details

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


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