Hello, I'm currently using xorg-server 1.4 and xf86-video-ati 6.7.195 on a Radeon X550 (RV370) 5B63 (PCIE). Yesterday I decided to try the new TV-out support, and I connected a PAL tv to my video card using a S-VHS-to-composite adapter, a composite cable and a composite-to-SCART adapter. I couldn't make it works, but this is not important now; what's important is that now during POST, when I change the BIOS settings and during the boot of the linux kernel with the standard VESA framebuffer driver the refresh rate is stuck to 50 Hz (it was 60 Hz before). To the contrary, when using X all the usual refresh rates are available, and the same's true for the radeonfb framebuffer driver (but I can't use it because of bug 10259). During my tests I rebooted with the TV connected; according to what I found searching with google, in this case the card sets both the monitor and the TV to 50 Hz, but when the card is not connected it should default again to 60 Hz. This doesn't happen in my case. I don't know if this is important but I also used "xrandr --output S-video --set load_detection 1".
Created attachment 12101 [details] xrandr --verbose output (1) xrandr --verbose output without a TV connected and with load_detection 0
Created attachment 12102 [details] xrandr --verbose output (2) xrandr --verbose output without a TV connected and with load_detection 1
Created attachment 12103 [details] xorg.conf
Created attachment 12104 [details] Xorg.0.log Xorg.0.log (without a TV connected)
The console and VGA mode are all handled by the bios. the X server doesn't really affect that other than restoring the old state when you switch VTs. I suspect, as you suggested, that the bios uses a 50 Hz compatible mode to light up the outputs if a tv is detected as attached. What does this have to do with X?
Bugzilla Upgrade Mass Bug Change NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO. - benjsc fd.o Wrangler
bios issue.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.