Bug 827107

Summary: Nouveau not working on Lenovo T420
Product: [Fedora] Fedora Reporter: klement.sekera
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: aal, airlied, ajax, awilliam, bskeggs, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-15 14:37:23 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:

Description klement.sekera 2012-05-31 15:56:26 UTC
When discrete graphics is selected in BIOS after installing the Fedora to force the NVIDIA card to be used, then the boot process freezes right after the grub prompt (the logo is not displayed at all).

When optimus is selected, the nouveau driver is not used, instead, the intel graphics in the cpu is used.

Comment 1 Adam Williamson 2013-05-14 20:32:27 UTC
Assigning to correct component. Can you please provide as much of the data listed at https://fedoraproject.org/wiki/How_to_debug_Xorg_problems as possible? Is this still the case with latest F17 updates, or with F18/F19 if you've upgraded? Thanks!

Comment 2 klement.sekera 2013-05-15 07:53:27 UTC
Hi, the boot process freeze is tied to another bug and can be worked around by disabling vt-d support in virtualization settings in bios.

I don't know about nouveau anymore, since I switched to binary nvidia drivers some time ago.

Comment 3 Adam Williamson 2013-05-15 14:36:35 UTC
Thanks. Is there already a report for the other bug? If so, we could close this.

Comment 4 Adam Williamson 2013-05-15 14:37:23 UTC
Ah, I knew I knew it already. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=752613

*** This bug has been marked as a duplicate of bug 752613 ***