Tweet
I am using TV-out on RS482. Load detection does not work, and S-video is always shown as disconnected. The following sequence, present in many tutorials, fails and screen remains empty.
However, if I pass kernel option "video=SVIDEO-1:e" (or "video=SVIDEO-1:ei" - no difference on screen; "e" for "enabled, and "i" for "interlaced") it works just fine. I can do with it as I please via xrandr: clone view, extended desktop, change TV standard (at least PAL and NTSC both work), etc. I even see boot messages on my TV.
This does introduce some unwanted side effects. Firstly, console is correctly set to 1400x1050, but usable area is limited to 800x600, while the rest is just empty black area. Secondly, GDM starts at 800x600, and then switches to 1400x1050 when GNOME desktop loads, so the resolution on my screen changes several times during boot sequence.
If I do not use the kernel parameter, I can still sometimes get S-video to work by opening "gnome-display-properties" and mashing "Detect monitors" button like crazy. This usually results is losing the signal again in couple of seconds. I did not check what the button is actually doing, but it is rather weird.
My question is whether this is a bug? And how can S-video output be (force-)enabled at runtime?
Code:
$ xrandr --output S-video --set load_detection 1 $ xrandr --addmode S-video 800x600 $ xrandr --output S-video --mode 800x600
This does introduce some unwanted side effects. Firstly, console is correctly set to 1400x1050, but usable area is limited to 800x600, while the rest is just empty black area. Secondly, GDM starts at 800x600, and then switches to 1400x1050 when GNOME desktop loads, so the resolution on my screen changes several times during boot sequence.
If I do not use the kernel parameter, I can still sometimes get S-video to work by opening "gnome-display-properties" and mashing "Detect monitors" button like crazy. This usually results is losing the signal again in couple of seconds. I did not check what the button is actually doing, but it is rather weird.
My question is whether this is a bug? And how can S-video output be (force-)enabled at runtime?