Bug 884945 - when plugged second monitor, after upgrading kernel to 3.6.9-4, computer with ATI Radeon HD 6570 became unusable
Summary: when plugged second monitor, after upgrading kernel to 3.6.9-4, computer with...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-07 05:56 UTC by Mikhail
Modified: 2014-02-05 13:39 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 13:39:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output (14.98 KB, application/x-7z-compressed)
2012-12-07 05:56 UTC, Mikhail
no flags Details
message log (57.88 KB, application/x-7z-compressed)
2012-12-07 05:57 UTC, Mikhail
no flags Details
desktop after loading (2.68 MB, image/png)
2012-12-20 05:57 UTC, Mikhail
no flags Details

Description Mikhail 2012-12-07 05:56:46 UTC
Created attachment 659211 [details]
dmesg output

Description of problem:
After upgrading kernel to 3.6.9-4, computer with ATI Radeon HD 6570 became unusable

Second monitor blink during boot, and don't appear login screen

Comment 1 Mikhail 2012-12-07 05:57:15 UTC
Created attachment 659212 [details]
message log

Comment 2 Mikhail 2012-12-11 12:38:22 UTC
This occurs only when plugged second monitor.

Comment 3 Mikhail 2012-12-13 14:15:11 UTC
Also with kernel  3.6.10-4

Comment 4 Mikhail 2012-12-20 05:54:25 UTC
Kernel 3.6.11-3 problem still not fixed

Comment 5 Mikhail 2012-12-20 05:57:31 UTC
Created attachment 666521 [details]
desktop after loading

Comment 6 Mikhail 2013-01-06 07:13:03 UTC
Kernel  3.7.1-2 problem still not fixed

Comment 7 Mikhail 2013-01-10 13:06:53 UTC
Kernel  3.7.1-5.fc18 problem still not fixed

Comment 8 Mikhail 2013-01-16 07:35:46 UTC
$ uname -a
Linux telecon_16.afbank.ru 3.7.2-201.fc18.i686.PAE #1 SMP Fri Jan 11 22:30:06 UTC 2013 i686 i686 i386 GNU/Linux

problem still not fixed :(

Comment 9 Mikhail 2013-01-21 05:08:05 UTC
$ uname -a
Linux telecon_16.afbank.ru 3.7.2-204.fc18.i686.PAE #1 SMP Wed Jan 16 16:31:26 UTC 2013 i686 i686 i386 GNU/Linux

problem still not fixed :(

Comment 10 Mikhail 2013-01-28 04:59:25 UTC
$ uname -a
Linux telecon_16.afbank.ru 3.7.4-204.fc18.i686.PAE #1 SMP Wed Jan 23 16:58:41 UTC 2013 i686 i686 i386 GNU/Linux

problem still not fixed :(

Comment 11 Mikhail 2013-02-04 05:25:23 UTC
$ uname -a
Linux telecon_16.afbank.ru 3.7.5-201.fc18.i686.PAE #1 SMP Mon Jan 28 20:06:14 UTC 2013 i686 i686 i386 GNU/Linux

problem still not fixed :(

Comment 12 Mikhail 2013-02-06 05:10:04 UTC
$ uname -a
Linux telecon_16.afbank.ru 3.7.6-201.fc18.i686.PAE #1 SMP Mon Feb 4 16:05:44 UTC 2013 i686 i686 i386 GNU/Linux

problem still not fixed :(

Comment 13 Mikhail 2013-02-15 05:35:44 UTC
$ uname -a
Linux telecon_16.afbank.ru 3.7.7-201.fc18.i686.PAE #1 SMP Tue Feb 12 22:49:01 UTC 2013 i686 i686 i386 GNU/Linux


problem still not fixed :(

Comment 14 Mikhail 2013-02-20 08:54:38 UTC
$ uname -a
Linux telecon_16.afbank.ru 3.7.9-201.fc18.i686.PAE #1 SMP Mon Feb 18 21:21:43 UTC 2013 i686 i686 i386 GNU/Linux


problem still not fixed :(

Comment 15 Mikhail 2013-03-07 12:02:03 UTC
$ uname -a
Linux telecon_16.afbank.ru 3.8.1-201.fc18.i686.PAE #1 SMP Thu Feb 28 19:37:29 UTC 2013 i686 i686 i386 GNU/Linux

problem still not fixed :(

Comment 16 Mikhail 2013-03-11 04:54:45 UTC
$ uname -a
Linux telecon_16.afbank.ru 3.8.2-206.fc18.i686.PAE #1 SMP Fri Mar 8 15:15:17 UTC 2013 i686 i686 i386 GNU/Linux

problem still not fixed :(


Anybody read my report?

Comment 17 iwiznia 2013-03-17 00:08:21 UTC
Same issue here, I'm in:
Linux localhost.localdomain 3.8.2-206.fc18.x86_64 #1 SMP Fri Mar 8 15:03:34 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Comment 18 Mikhail 2013-03-18 08:00:52 UTC
$ uname -a
Linux telecon_16.afbank.ru 3.8.3-201.fc18.i686.PAE #1 SMP Thu Mar 14 21:42:11 UTC 2013 i686 i686 i386 GNU/Linux

problem still not fixed :(

Addition: problem occurs only when I connect second monitor on Radeon via D-sub connector.

Comment 19 Mikhail 2013-03-18 08:02:09 UTC
This means, HDMI + DVI work correctly.

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

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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 21 Fedora End Of Life 2014-02-05 13:39:08 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.