|Summary:||HIS Radeon 9250CL 128 uses wrong DVI mode unless VGA is connected|
|Product:||xorg||Reporter:||Brice Goglin <brice.goglin>|
|Component:||Driver/Radeon||Assignee:||xf86-video-ati maintainers <xorg-driver-ati>|
|Status:||RESOLVED INVALID||QA Contact:||Xorg Project Team <xorg-team>|
|i915 platform:||i915 features:|
Description Brice Goglin 2008-09-05 15:26:12 UTC
Reported by Felix Schueller on the Debian BTS last week, occurs with today's xf86-video-ati git. He has a "HIS Radeon 9250CL 128" 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01) When he boots with only DVI connected, the screen remains black. If he plugs a VGA output, DVI will work fine. The difference seems to be that having VGA plugged will make the selected mode on DVI switch from rate 60.0 to 59.9, probably because the preferred mode for VGA uses rate 59.9. If he boots with VGA plugged and then forces DVI rate to 60.0, the screen goes black as well. The log and output of xrandr when VGA is disconnect, not working then, are at: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;bug=497209 http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=xrandr.notworking;att=2;bug=497209 When VGA is connected, xrandr says: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=xrandr.working;att=1;bug=497209 One thing we noticed is that S-video is wrongly detected as connected. We added the necessary xorg.conf stuff to ignore it.
Comment 1 Felix Schueller 2008-09-05 17:07:24 UTC
> One thing we noticed is that S-video is wrongly detected as connected. We added > the necessary xorg.conf stuff to ignore it. That is not exactly true, we tried it, but after that, X won't start: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=Xorg.svideo.log;att=3;bug=497209
Comment 2 Alex Deucher 2009-11-11 10:28:33 UTC
Is this still an issue with xf86-video-ati from git master?
Comment 3 Alex Deucher 2010-10-19 16:40:26 UTC
closing due to lack of feedback.
Comment 4 Adam Jackson 2018-06-12 19:07:55 UTC
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.