Bug 493483 - KMS:RV670PRO:Radeon HD 3850 wrong mode on Iiyama Vision Master Pro 410
Summary: KMS:RV670PRO:Radeon HD 3850 wrong mode on Iiyama Vision Master Pro 410
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2009-04-01 22:03 UTC by Andrew Gormanly
Modified: 2018-04-11 08:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-05 06:57:57 UTC
Type: ---

Attachments (Terms of Use)
dmesg output (100.11 KB, text/plain)
2009-11-21 22:21 UTC, Andrew Gormanly
no flags Details
X log (67.94 KB, text/plain)
2009-11-21 22:21 UTC, Andrew Gormanly
no flags Details

Description Andrew Gormanly 2009-04-01 22:03:46 UTC
Description of problem:
Radeon driver gets wrong mode on Iiyama Vision Master Pro 410 monitor

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

How reproducible:
Every time

Steps to Reproduce:
1. boot
Actual results:

Expected results:

Additional info:

Comment 1 Andrew Gormanly 2009-04-01 22:17:16 UTC
Radeon test day test 1

Comment 2 Andrew Gormanly 2009-04-01 22:34:03 UTC
Works if I don't use modeset.radeon=1 as a kernel parameter at the boot prompt

Comment 3 Matěj Cepl 2009-04-03 16:00:11 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf (if you have one) whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 4 François Cami 2009-04-06 21:30:46 UTC

Could you please try to boot into runlevel 3 without nomodeset :
  nomodeset 3
and run the following commands :
  modprobe -r radeon drm
  modprobe drm debug=1
  modprobe radeon modeset=1
  init 5

Please add dmesg output, and Xorg.0.log from this attempt as
uncompressed *text/plain* attachments to this bug as well.

Thank you.

Fedora Bugzappers volunteer triage team

Comment 5 Bug Zapper 2009-06-09 13:02:17 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:

Comment 6 Matěj Cepl 2009-11-05 18:24:34 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 7 Andrew Gormanly 2009-11-21 22:20:00 UTC
(In reply to comment #4)

Sorry for the horrendously slow reply.

Am attaching dmesg and Xorg log output for the Fedora 12 i686 case, in which the nomodeset boot parameter must be used to achieve 1600x1200 on this machine, after deletion of /etc/X11/xorg.conf.

The attached files are for the case where it does not work, after deleting xorg.conf and following the boot and modprobe process suggested by François (I get 1280x1024).  Simply booting with nomodeset works, though.

I hope to be able to try a hand-crafted xorg.conf with the radeonhd driver and report results.

Comment 8 Andrew Gormanly 2009-11-21 22:21:21 UTC
Created attachment 372809 [details]
dmesg output

Comment 9 Andrew Gormanly 2009-11-21 22:21:55 UTC
Created attachment 372810 [details]
X log

Comment 10 François Cami 2009-11-22 01:57:12 UTC
All logs aboard, marking as triaged, switching owner to jglisse, keeping status as "NEW" as per new policy.

Thank you.

Fedora Bugzappers volunteer triage team

Comment 11 Chris Campbell 2009-12-08 18:25:32 UTC
changing status to ASSIGNED (Fedora 12)

Fedora Bugzappers volunteer triage team

Comment 12 Jérôme Glisse 2010-03-11 15:01:26 UTC
Please boot with KMS enabled and with drm.debug=15 and attach dmesg & xorg log

Comment 13 Vedran Miletić 2010-05-24 19:19:08 UTC
Improving summary.


Fedora Bugzappers volunteer triage team

[This triage is part of collective effort done by students of University of
Rijeka Department of Informatics.]

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

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 12'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 12 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 15 Bug Zapper 2010-12-05 06:57:57 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.