Bug 503259 - Booting with fedora 11 LiveCD RC2 -> After X starts, Monitor is sleeping mode.
Summary: Booting with fedora 11 LiveCD RC2 -> After X starts, Monitor is sleeping mode.
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 11
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-30 02:51 UTC by sangu
Modified: 2018-04-11 18:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-14 23:10:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg (61.55 KB, text/plain)
2009-05-30 02:51 UTC, sangu
no flags Details
/var/log/Xorg.0.log (87.40 KB, text/plain)
2009-05-30 02:52 UTC, sangu
no flags Details

Description sangu 2009-05-30 02:51:31 UTC
Created attachment 345969 [details]
dmesg

Description of problem:
Booting with fedora 11 LiveCD RC2 < http://alt.fedoraproject.org/pub/alt/stage/f11-rc2/Fedora-11-x86_64-Live/Fedora-11-x86_64-Live.iso > 
After X starts, Monitor is sleeping  mode.

VGA : 9800 GT
monitor : DELL S2209W

Version-Release number of selected component (if applicable):
Fedora 11 x86_64 LiveCD RC2 

How reproducible:
always

Steps to Reproduce:
1. Booting with Fedora 11 x86_64 LiveCD RC2 
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 sangu 2009-05-30 02:52:47 UTC
Created attachment 345970 [details]
/var/log/Xorg.0.log

Comment 2 Bug Zapper 2009-06-09 16:50:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Ben Skeggs 2009-08-24 03:33:12 UTC
Do you see better behaviour if you boot with "nouveau.modeset=1" in your kernel options?

Comment 4 Matěj Cepl 2009-11-05 18:30:18 UTC
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Comment 5 Chris Campbell 2009-12-02 14:05:00 UTC
Sangu, could you please reply to Comment #3?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 6 Matěj Cepl 2010-02-26 12:24:27 UTC
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]

Comment 7 Bug Zapper 2010-04-27 14:34:54 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Chris Campbell 2010-06-14 23:10:38 UTC
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as INSUFFICIENT_DATA.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers


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