Regression from fully working in original F13 release. The gnome-display-properties provided in control-center from the F14 DVD installer (repo: anaconda-InstallationRepo-201010211827.x86_64) fails to recognize either monitor. It mirrors displays and reports 'Monitor:Unknown' and 'Refresh Rate: 0Hz' and 'Rotation not supported' In early F13 at least, gnome-display-properties was able to recognize and configure both outputs of the single AGP card to display different views of the desktop and with full control of resolution and rotation. I say 'early F13' because I version-locked the kernel as some kernel versions in the 2.6.34 and 2.6.35 range) caused video problems. Name : control-center Arch : x86_64 Epoch : 1 Version : 2.32.0 Release : 1.fc14 Size : 8.5 M Repo : installed From repo : anaconda-InstallationRepo-201010211827.x86_64 In F13 the gnome panel applet which I assume was gnome-display-properties was able to recognize this ATI card. What do you recommend? Thank you. control-center Arch : x86_64 Epoch : 1 Version : 2.32.0 Release : 1.fc14 Size : 8.5 M Repo : installed From repo : anaconda-InstallationRepo-201010211827.x86_64 lspci -vvv recognizes both outputs of the AGP videocard. It concludes with: 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 0054 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (2000ns min), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at e000 [size=256] Region 2: Memory at fbe00000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at fbd00000 [disabled] [size=128K] Capabilities: [58] AGP version 3.0 Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8 Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none> Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel modules: radeon, radeonfb 01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (Secondary) (rev 01) Subsystem: ASUSTeK Computer Inc. Device 0055 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (2000ns min), Cache Line Size: 64 bytes Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M] Region 1: Memory at fbf00000 (32-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
(In reply to comment #0) > Regression from fully working in original F13 release. > > The gnome-display-properties provided in control-center from the F14 DVD > installer (repo: anaconda-InstallationRepo-201010211827.x86_64) > fails to recognize either monitor. It mirrors displays and > reports 'Monitor:Unknown' and 'Refresh Rate: 0Hz' and 'Rotation not > supported' > > In early F13 at least, gnome-display-properties was able to recognize and > configure both outputs of the single AGP card to display different views of the > desktop and with full control of resolution and rotation. > > I say 'early F13' because I version-locked the kernel as some kernel versions > in the 2.6.34 and 2.6.35 range) caused video problems. > > Name : control-center > Arch : x86_64 > Epoch : 1 > Version : 2.32.0 > Release : 1.fc14 > Size : 8.5 M > Repo : installed > From repo : anaconda-InstallationRepo-201010211827.x86_64 > > In F13 the gnome panel applet which I assume was gnome-display-properties > was able to recognize this ATI card. > > > What do you recommend? Thank you. Run "xrandr -q" and attach your Xorg.0.log when reproducing the problem
Created attachment 460959 [details] Xorg.0.log FROM 2.6.36-1.fc15.x86_64 boot Thank you Bastien! $ xrandr -q xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 1280 x 1024, maximum 1280 x 1024 default connected 1280x1024+0+0 0mm x 0mm 1280x1024 0.0* 1024x768 0.0 800x600 0.0 640x480 0.0
Is there anything else that would be helpful?
The XRandR support in the ATI driver is broken for your system.
Thank you Bastien for the update! Do you know, or where can I go to find out: Q: is it just xorg-x11-drv-ati that is broken, or what else? Q: Which versions are bad? (if I stay with F13 on which version should I lock xorg?) Q: Does this apply to all ATI cards? Q: How can I find out when it's fixed, or whether it won't be fixed?
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 add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), and * output of the dmesg command to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
(In reply to comment #5) > Thank you Bastien for the update! > > Do you know, or where can I go to find out: I have no idea. But XRandR (as shown by the output of "xrandr -q") reports a 0Hz refresh rate, and only one monitor. So there's nothing that the display preferences can do if the driver returns bogus or broken information.
Matej Cepl: I tried adding drm.debug=0x04 to the kernel command line of gfx_test_week_20110221_x86-64.iso . Restarted computer but boot (both normal and 'Boot Basic Video') fails (system automatically reboots) if drm.debug=0x04 is added to the kernel command line. /etc/X11/xorg.conf does not exist. I will attach dmesg output.
Created attachment 480406 [details] dmesg output FROM gfx_test_week_20110221_x86-64.iso
(In reply to comment #8) > /etc/X11/xorg.conf does not exist. > I will attach dmesg output. [ 35.944] (==) Using config file: "/etc/X11/xorg.conf" Whoops! Could you please try again and make there really isn't a one? And could you attach this one. You did try to start with "Basic driver" or xdriver=vesa, right?
Created attachment 480553 [details] dmesg output #2 FROM gfx_test_week_20110221_x86-64.iso
Created attachment 480554 [details] /var/log/Xorg.0.log FROM gfx_test_week_20110221_x86-64.iso
(In reply to comment #10) > (In reply to comment #8) > > /etc/X11/xorg.conf does not exist. > > I will attach dmesg output. > > [ 35.944] (==) Using config file: "/etc/X11/xorg.conf" > > Whoops! Could you please try again and make there really isn't a one? And could > you attach this one. You did try to start with "Basic driver" or xdriver=vesa, > right? The very first attachment above, Xorg.0.log, is from my original report months ago; I've labelled the current attachments 'FROM gfx_test_week_20110221_x86-64.iso' and I am using the 'Boot Basic Video' menu option which sets xdriver=vesa nomodeset rd.luks=0 rd.md=0 rd.dm=0
Could the problem lie in the VIA chips rather than with the graphics card itself? Hardware profile is at http://www.smolts.org/client/show/pub_6a2dc543-dffc-43d6-a581-b3416f479f6d
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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