radeonhd fails to detect dual monitor with RV635

[pureblood]

Binary package hint: xserver-xorg-video-radeonhd

The radeonhd driver for my graphic card (VGA compatible controller: ATI Technologies Inc Device 9596, Subsystem: Hightech Information System Ltd. Device 0028, which I think has chipset RV635) seems unable to detect my dual monitor setup. This problem was present with Intrepid and is still present with the new radeonhd 1.2.4 driver on Jaunty, so I decided to file a bug report. I am not sure this is the best place to report it though.
Long story short, with the radeon driver everything seems to be fine, but the radeonhd driver seems to believe that only one monitor is connected. I am attaching the Xorg.0.log files and the output for 'xrandr -q' for both configurations, that is, with radeon and with radeonhd. I hope this should be enough to pin down the problem, but feel free to ask me for more information.
On a side note, the fglrx driver freezes the X server, so I uninstalled it on my system.. The version of the X server I am using is 1.6.0 but I guess all of this is irrelevant since same problem happened equally with Intrepid and Jaunty.

[Rafał Miłecki (zajec5)]

I just checked first 5 lines of radeonhd log:

(EE) RADEONHD(0): The fglrx kernel module is loaded. This can have obvious
     or subtle side effects. See radeonhd(4) for details.

Reproduce with removed fglrx and after full reboot (even better with powering off for being 100% sure) please.

[pureblood (freeseek)]

Binary package hint: xserver-xorg-video-radeonhd

The radeonhd driver for my graphic card (VGA compatible controller: ATI Technologies Inc Device 9596, Subsystem: Hightech Information System Ltd. Device 0028, which I think has chipset RV635) seems unable to detect my dual monitor setup. This problem was present with Intrepid and is still present with the new radeonhd 1.2.4 driver on Jaunty, so I decided to file a bug report. I am not sure this is the best place to report it though.
Long story short, with the radeon driver everything seems to be fine, but the radeonhd driver seems to believe that only one monitor is connected. I am attaching the Xorg.0.log files and the output for 'xrandr -q' for both configurations, that is, with radeon and with radeonhd. I hope this should be enough to pin down the problem, but feel free to ask me for more information.
On a side note, the fglrx driver freezes the X server, so I uninstalled it on my system.. The version of the X server I am using is 1.6.0 but I guess all of this is irrelevant since same problem happened equally with Intrepid and Jaunty.

[Tormod Volden (tormodvolden)]

Thanks for your report. It would be nice if you can report this bug upstream at bugs.freedesktop.org, but first please test the updated 1.2.5 packages in my PPA https://launchpad.net/~tormodvolden/+archive/ppa to see if the issue has been fixed and attach the new Xorg.0.log to the report. Upstream does not like tarballs either :)

If you have any questions about testing or upstream bug filing feel free to ask here.

[pureblood (freeseek)]

Thanks for the prompt answer. I have tried version 1.2.5 and nothing different happened. I reattached the same output as before using the new radeonhd. I am on my way to report the problem on bugs.freedesktop.org. What do you mean with upstream anyway?

[Tormod Volden (tormodvolden)]

By upstream we mean the xorg developer community which produces the software, bugs.freedesktop.org in fact. They generally don't read distribution bug tracker like ours, so usually we have to "upstream" the bug reports once we have verified that it is not a user/distribution/packaging problem.

"xrandr --verbose" output can also be useful sometimes. Please attach each file separately.

[pureblood (freeseek)]

Created an attachment (id=25000)
This tarball contains four different files.

Here I collected the logs again, this time with the "xrandr --verbose" option. Whatever the problem is, it has been there for quite a while, since I had it with Ubuntu Intrepid as well since I bought this graphic card. By the way, why is the interface for bugs.freedesktop.org so badly designed? It really turns you down when you want to file a report, especially if it is the first time.

[Stephan (stephan-h)]

This may or may not be connected:

Desktop box with jaunty live CD, two monitors on a card with RV515.
Monitor 1 is connected directly via DVI,
Monitor 2 (analog) is connected via a DVI-to-VGA adapter.

I fetched xserver-xorg-video-radeonhd_1.2.4-2_i386.deb, installed it
and edited xorg.conf to use radeonhd.

Effect: radeonhd does not see the VGA behind the adapter,
xrandr reports disconnected.
When using radeon instead, this problem does not occur.

My reason for trying radeonhd was that radeon crashes when
configuring for Xinerama => no way to separate both displays.

Since I'm running of the live CD, to ensure upgrade won't kick me
into nirwana, collecting files to attach is not sooo convenient,
but if s.o. tells me which files / outputs would help in this case
I could certainly provide those.

[Tormod Volden (tormodvolden)]

pureblood, I found your upstream report. Please note that they also prefer the attachments as separate, plain text files. It takes too much time for busy developers to download tarball archives and unpack them, and it also makes any automatic processing difficult. Server disk space, on the other hand, is not an issue.

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[Timo Aaltonen (tjaalton)]

there is no -radeonhd in the archive anymore, closing the bugs.

[Jeremy Sequoia (jeremyhu)]

Does this issue occur with the preferred ati driver (xf86-vide-ati)? If so, please move this to the Driver/Radeon component.

Development of radeonhd has pretty much halted and development focus is on the ati driver. Please see http://www.x.org/wiki/radeonhd

If the issue does not exist in the ati driver (or if there is no response to this message), this bug will be closed as WONTFIX unless someone contributes a patch.

[Jeremy Sequoia (jeremyhu)]

Closing due to lack of response. Please reopen and move to the Driver/Radeon
component if this issue persists with xf86-video-ati