Bug 800497

Summary: Black screen in installer
Product: [Fedora] Fedora Reporter: Per Steinar Iversen <PerSteinar.Iversen>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 17CC: airlied, ajax, bskeggs, gansalmon, g.kaviyarasu, itamar, jonathan, kernel-maint, madhu.chinakonda, pmrpla, vanmeeuwen+fedora
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: 2013-07-31 21:46:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Output from lspci
none
Nouveau log none

Description Per Steinar Iversen 2012-03-06 15:14:03 UTC
Created attachment 567985 [details]
Output from lspci

Description of problem:

Installer fails: Screen blacks out when booting installer from dvd.
acpi=off works and allows installation, the installation then finally fails to
boot - possibly a different issue.

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


How reproducible:

Always

Steps to Reproduce:
1. Boot F17 alpha dvd
2. Screen black out, passing acpi=off allows boot to continue
3.
  
Actual results:

Graphical install does not work

Expected results:

Install should work

Additional info:

The machine is an "HP Pavilion HPE h8-1080sc". The output from lspci under F16 is attached. The cpu is listed by lshw as "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"

Under F16 there is no problem installing but later updates broke the nouveau driver, the Nvidia driver from rpmfusion works fine.

Comment 1 Dave Jones 2012-03-06 16:25:46 UTC
My hunch is that this is related to a problem that I saw recently.
https://lkml.org/lkml/2012/2/23/303

Comment 2 Per Steinar Iversen 2012-03-08 10:25:36 UTC
(In reply to comment #1)
> My hunch is that this is related to a problem that I saw recently.
> https://lkml.org/lkml/2012/2/23/303

I just tried setting slub_debug=-1 but the screen still goes black and there
is no output even after 1 hour.

Comment 3 Per Steinar Iversen 2012-03-09 12:41:31 UTC
Created attachment 568886 [details]
Nouveau log

Comment 4 Per Steinar Iversen 2012-03-09 12:45:44 UTC
Even when booting in text mode the screen blacks out.

As a last test I reinstalled F16, that works fine with the initial kernel.

Then I installed kernel-3.3.0-0.rc6.git0.2.fc17.x86_64, see new attachment
for messages related to the nouveau driver.

The X log ends with:

[    32.231] (II) NOUVEAU(0): NVEnterVT is called.
[    34.230] (EE) NOUVEAU(0): failed to set mode: Device or resource busy
Fatal server error:
[    34.230] failed to create screen resources

Comment 5 Pedro Almeida 2012-03-17 17:37:10 UTC
Same here with a GTX260M, but I can also install by choosing "Troubleshooting->Install Fedora in basic graphics mode". Until I hit the btrfs bug, that is.

Comment 6 Per Steinar Iversen 2012-04-12 06:27:31 UTC
I tried the recent kernel-3.3.0-0.rc6.git2.2.fc18.x86_64.rpm and it works, nouveau works once more. kernel 3.1 worked for this machine, 3.2 and 3.3 did not and now 3.4 seems to be ok again.

Comment 7 Fedora End Of Life 2013-07-03 21:01:44 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 8 Fedora End Of Life 2013-07-31 21:46:19 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.