Bug 616079 - dark screen after update to new kernel
Summary: dark screen after update to new kernel
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-19 15:43 UTC by Tomas Pelka
Modified: 2011-06-29 13:16 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2011-06-29 13:16:49 UTC

Attachments (Terms of Use)
demsg.log (122.70 KB, text/plain)
2010-07-19 15:48 UTC, Tomas Pelka
no flags Details
xorg.log (37.25 KB, text/plain)
2010-07-19 15:49 UTC, Tomas Pelka
no flags Details
dmesg on koji kernel (122.72 KB, text/plain)
2010-07-20 06:55 UTC, Tomas Pelka
no flags Details
xorg.log on koji kernel (40.62 KB, text/plain)
2010-07-20 06:56 UTC, Tomas Pelka
no flags Details
dmesg log (122.57 KB, text/plain)
2010-07-28 08:37 UTC, Tomas Pelka
no flags Details
dmesg_07-28-10- (122.64 KB, text/plain)
2010-07-28 08:51 UTC, Tomas Pelka
no flags Details

Description Tomas Pelka 2010-07-19 15:43:18 UTC
Description of problem:
SSIA, logs attached

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

How reproducible:

Steps to Reproduce:
Actual results:
black screen, only backlight lid

Expected results:
should work

Additional info:
works fine with kernel-

Comment 1 Tomas Pelka 2010-07-19 15:48:13 UTC
Created attachment 432926 [details]

booted with drm.debug=14

Comment 2 Tomas Pelka 2010-07-19 15:49:16 UTC
Created attachment 432928 [details]

Comment 3 Ben Skeggs 2010-07-19 22:24:28 UTC
Can you try http://koji.fedoraproject.org/koji/buildinfo?buildID=183992 (kernel- and see if that helps?

Comment 4 Tomas Pelka 2010-07-20 06:55:38 UTC
Created attachment 433080 [details]
dmesg on koji kernel

Comment 5 Tomas Pelka 2010-07-20 06:56:15 UTC
Created attachment 433082 [details]
xorg.log on koji kernel

Comment 6 Tomas Pelka 2010-07-20 06:57:29 UTC
I'm sorry Ben, nothing changed in

Cheers Tom.

Comment 7 Tomas Pelka 2010-07-28 08:37:52 UTC
Created attachment 434951 [details]
dmesg log

kernel options:
log_buf_len=1 drm.debug=14 nouveau.reg_debug=0x0200 3

Comment 8 Tomas Pelka 2010-07-28 08:51:48 UTC
Created attachment 434954 [details]

Similar issue on

Dmesg log ( with "log_buf_len=1 drm.debug=14 nouveau.reg_debug=0x0200 3" options) attached.

Comment 9 Bug Zapper 2011-06-01 13:26:46 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 

Comment 10 Bug Zapper 2011-06-29 13:16:49 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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