I have been struggling to get my TV-out working on ivtv (installed on
Ubuntu Feisty). Mythtv works fine, so ivtv is installed correctly. (I
can use my 'other' TV-output which converts VGA to Composite. The
quality of this picture is acceptable, but not great; I know the 350's
TV-out is much better).
I can give the following information:
1) As soon as I connected the TV-out cable to the 350 and the TV, I got
a black screen on the TV. This means it is sending a signal, because the
screen is blue when the TV is not getting any signal at all.
2) I live in Europe, and need a PAL(-B/G) signal.
3) I played around with some old (!) information from
http://ivtv.writeme.ch/tiki-index.php?page=TvOutPal and
http://ivtv.writeme.ch/tiki-index.php?page=TvOutHowto
which instructs what lines to add to /etc/modprobe.d/aliases (I think
thats the Ubuntu equivalent of /etc/modules.conf). Long story short,
some combination of lines (which I cannot remember and have not been
able to reproduce) gave a crystal clear TV-output with MythTV (which I
set up to use /dev/video16). However: no sound and no overlay (for
example, when I activated the program guide, it would not appear on the
screen).
I remember examining the output of dmesg and it seemed the lines I was
adding to aliases contained syntaxes that were not (or no longer)
recognized. Which line/command was the magic one to enable the TV-out, I
cannot tell.
4) I restored my original aliases file, but added
install ivtv /sbin/modprobe --ignore-install ivtv; /sbin/modprobe ivtv-fb
as suggested in
http://www.mythtv.org/wiki/index.php/IVTV_Install
and updated the modules and rebooted. By chance I noticed some text
flashing on the TV while rebooting! Now, If I press cntrl-alt-f1 my
monitor goes blank and I see the terminal on the TV. Also when booting
into recovery mode, I see the messages floating by on my monitor until
it hits ivtv0-fb, after which the output switches to the TV.
/In this situation, when I watch TV on MythTV, I get a black screen with
the terminal covering almost all of the screen. Only at the edges I see
a TV-picture. Also, still no sound. /
5) When I do: sudo rmmod saa7127, the tv-screen goes blue, as expected.
6) Current output of dmesg:
[ 16.543497] ivtv: ==================== START INIT IVTV
====================
[ 16.543500] ivtv: version 0.10.1 (tagged release) loading
[ 16.543501] ivtv: Linux version: 2.6.20-15-generic SMP mod_unload 586
[ 16.543503] ivtv: In case of problems please include the debug info
between
[ 16.543504] ivtv: the START INIT IVTV and END INIT IVTV lines, along
with
[ 16.543506] ivtv: any module options, when mailing the ivtv-users
mailinglist.
[ 16.543793] ivtv0: Autodetected Hauppauge card (cx23415 based)
[ 17.215564] ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
[ 17.237366] ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
[ 17.464035] ivtv0: Encoder revision: 0x02050032
[ 17.464037] ivtv0: Recommended firmware version is 0x02060039.
[ 17.472094] ivtv0: Decoder revision: 0x02020023
[ 17.540695] ivtv0: Autodetected Hauppauge WinTV PVR-350
[ 17.561657] tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
[ 17.566192] tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
[ 17.632573] saa7115 0-0021: saa7115 found (1f7115d0e100000) @ 0x42
(ivtv i2c driver #0)
[ 17.873437] saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
[ 17.901274] msp3400 0-0040: MSP4418G-B3 found @ 0x80 (ivtv i2c driver #0)
[ 17.901358] ivtv0: Registered device video0 for encoder MPEG (4 MB)
[ 17.901473] ivtv0: Registered device video32 for encoder YUV (2 MB)
[ 17.901601] ivtv0: Registered device vbi0 for encoder VBI (1 MB)
[ 17.901649] ivtv0: Registered device video24 for encoder PCM audio (1 MB)
[ 17.901805] ivtv0: Registered device radio0 for encoder radio
[ 17.901825] ivtv0: Registered device video16 for decoder MPEG (1 MB)
[ 17.901863] ivtv0: Registered device vbi8 for decoder VBI (1 MB)
[ 17.902132] ivtv0: Registered device vbi16 for decoder VOUT
[ 17.902152] ivtv0: Registered device video48 for decoder YUV (1 MB)
[ 17.976424] ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
[ 18.463544] ivtv0: Initialized Hauppauge WinTV PVR-350, card #0
[ 18.463552] ivtv: ==================== END INIT IVTV
====================
[ 18.490481] ivtv0-fb: Framebuffer at 0xf5510000, mapped to
0xfa390000, size 1665k
[ 18.565743] ivtv0-fb: === Validated display mode ===
[ 18.565745] ivtv0-fb: Display size 640x480 (640x480 Virtual) @ 8bpp
[ 18.565746] ivtv0-fb: Display position 41,49
[ 18.565747] ivtv0-fb: Display filter : on
[ 18.565748] ivtv0-fb: Color space : RGB
[ 18.590694] ivtv0-fb: === Display mode change ===
[ 18.590697] ivtv0-fb: Display size 640x480 (640x480 Virtual) @ 8bpp
[ 18.590699] ivtv0-fb: Display position 41,49
[ 18.590701] ivtv0-fb: Display filter : on
[ 18.590702] ivtv0-fb: Color space : RGB
[ 18.614861] ivtv0-fb: Framebuffer registered on ivtv card id 0
[ 43.551436] ivtv0-fb: === Validated display mode ===
[ 43.551439] ivtv0-fb: Display size 640x480 (640x480 Virtual) @ 8bpp
[ 43.551440] ivtv0-fb: Display position 41,49
[ 43.551441] ivtv0-fb: Display filter : on
[ 43.551442] ivtv0-fb: Color space : RGB
[ 43.559209] ivtv0-fb: === Display mode change ===
[ 43.559212] ivtv0-fb: Display size 640x480 (640x480 Virtual) @ 8bpp
[ 43.559214] ivtv0-fb: Display position 41,49
[ 43.559216] ivtv0-fb: Display filter : on
[ 43.559217] ivtv0-fb: Color space : RGB
I am getting very close to a solution, but after many hours of googling
and reading I am kind of stuck here. The documentation on this is mostly
outdated, I feel. Any help would be greatly appreciated (as in... I'll
do your chemistry homework ;) )
Regards,
Crakie
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
