Bug 538486

I wonder whether the following, mentioned in my post to Bug # 533959, is another consequence of the problems with my graphic card's support:
BACKGROUND: The radeon driver is rather unstable, clashing with Flash + FireFox (see Bug # 533959), so
* I had to switch to the VESA driver, since the flgrx driver is apparently no longer available, so
* Using the VESA driver, no need to set nomodeset, still
* I no longer get to benefit from hardware acceleration, which is a pain.

Please let me know whether all these should be considered sufficiently related (though separate from Bug # 533959) to be condensed in this one bug report, or whether they should each be filed as a separate bug report.

Quite obviously, the sooner this is fixed, the happier I will be, and I assume, so will other users of the same line of graphic cards. After all, Linux does run on older hardware.

Thanks for the great distro, go Fedora!

Please attach full dmesg. You likely among the few having issue with radeon 9200 (when excluding GL issues). It's likely related to your monitor having bad edid and KMS not dealing that well with that. If it's due to bad edid then this bug is a duplicate of :
https://bugzilla.redhat.com/show_bug.cgi?id=533632

Created attachment 375027 [details]
dmesg log when unsing radeon driver and kernelmode is on

Created attachment 375029 [details]
dmesg log when using radeon driver but kernelmode is off

Created attachment 375031 [details]
dmesg log when using vesa driver and kernel mode is on

Note that in order not to mess up my desktop, the two other dmesg logs I posted were taken while I logged into a dummy account, while this one is my corrent regular setup. This different set of user settings will explain some of the differences (I spotted the fact that Skype is mentinoed in this log but not teh others), however, I don't expect that to materially impact the research for fixing this bug.

I checked out bug#533632, to see whether it is a duplicate, and saw it quoted some kernel logs, so I executed

# grep edid /var/log/messages

I can now report that there was no output.

Hi A,
Could you boot with drm.debug=1 in the kernel command line and attach the resulting dmesg log?

Thanks in advance,

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

Created attachment 380914 [details]
dmesg log when using vesa driver and drm.debug=1 set

That should be enough, thank you.

Jerome, that bug does not look like the "bad edid" problem to me.

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

I upgraded to Fedora 13, and the problem persists.

Since the conflict between the Radeon driver and Firefox+Flash seems solved, I am now back to using the Radeon driver, but in order to use the full resolution my screens offers, I have to use nomodeset.

I have noticed one improvement, though it may result from having made a change in the BIOS settings: I increased the AGP memory from 64MB to 128MB, which is what my card has. I am not sure what that BIOS setting is all about, but now, without nomodeset, at least I get 1024x768, which is an improvement over 800x600.

This issue, however, still needs fixing.

Please boot with kms enable (without the nomodeset option) and with drm.debug=15 and attach dmesg to the bug (with all component update to lastest f13)

Created attachment 423952 [details]
dmesg log with drm.debug=15, kernel mode on (default), radeon driver and 256 AGB aperture

I am attaching the dmesg log.

By the way, I wrote above: "I increased the AGP memory from 64MB to 128MB, which is what my card has." That was about AGP Aperture size. I now tried with 256MB, but it doesn't seem to make a difference, so I will probably turn it back to 128MB, or even 64MB.

This problem has disappeared, after I switched from using a VGA cable to using DVI. My problem in this bug also disappeared: https://bugzilla.redhat.com/show_bug.cgi?id=629282

I would be interested in learning why there are these problems with the VGA setup but not with DVI, though.

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

As using a DVI cable provides a workaround, I no longer suffer from this bug, but perhaps it should be fixed in the interest of ironing out kinks that could hurt other users.

(In reply to comment #15)
> As using a DVI cable provides a workaround, I no longer suffer from this bug,
> but perhaps it should be fixed in the interest of ironing out kinks that could
> hurt other users.

Would you be so kind and just for sake of testing, could you try to reproduce it with VGA cable, please? It would be lovely to know how much alive it is in the current (or more recent) Fedora.

Thank you very much

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

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.