Re: Still can't get a clear picture

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Sergio Rui Silva wrote:

Sergio Rui Silva wrote:

Hi all!...

I tried the new bttv driver (version 0.7.102) to try to fix the unclear image bug but with no result. I still got a very unclear picture. Works good with Windows... : (

Here is my dmesg

bttv: driver version 0.7.102 loaded
bttv: using 4 buffers with 2080k (8320k total) for capture
bttv: Host bridge is Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] System Controller
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 17) at 00:0d.0, irq: 5, latency: 32, mmio: 0xee005000
bttv0: detected: Pinnacle PCTV [card=39], PCI subsystem ID is 11bd:0012
bttv0: using: BT878(Pinnacle PCTV Studio/Ra) [card=39,autodetected]
i2c-algo-bit.o: Adapter: bt848 #0 scl: 1  sda: 1 -- testing...
i2c-algo-bit.o:1 scl: 1  sda: 0
i2c-algo-bit.o:2 scl: 1  sda: 1
i2c-algo-bit.o:3 scl: 0  sda: 1
i2c-algo-bit.o:4 scl: 1  sda: 1
i2c-algo-bit.o: bt848 #0 passed test.
tda9887: probing bt848 #0 i2c adapter [id=0x10005]
tda9887: chip found @ 0x86
bttv0: i2c attach [client=tda9887,ok]
i2c-core.o: client [tda9887] registered to adapter [bt848 #0](pos. 0).
msp34xx: init: chip=MSP3450G-B8, has NICAM support
msp3410: daemon started
bttv0: i2c attach [client=MSP3450G-B8,ok]
i2c-core.o: client [MSP3450G-B8] registered to adapter [bt848 #0](pos. 1).
i2c-core.o: adapter bt848 #0 registered as adapter 0.
bttv0: i2c: checking for MSP34xx @ 0x80... found
bttv0: pinnacle/mt: id=2 info="PAL+SECAM / stereo" radio=yes
bttv0: using tuner=33
bttv0: i2c: checking for MSP34xx @ 0x80... found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
i2c-core.o: driver i2c TV tuner driver registered.
tuner: probing bt848 #0 i2c adapter [id=0x10005]
tuner: chip found @ 0xc0
tuner(bttv): type forced to 33 (MT2032 universal) [insmod]
tuner: type already set (33)
bttv0: i2c attach [client=MT2032 universal,ok]
i2c-core.o: client [MT2032 universal] registered to adapter [bt848 #0](pos. 2).
MT2032: Companycode=4d54 Part=04 Revision=04
MT2032 hexdump:
1d 41 20 0f 1f 18 f4 0c  c3 4e ec 18 03 32 2f 00
ff 4d 54 04 04
mt2032: xogc = 0x07
mt2032: xok = 0x00
mt2032: xogc = 0x06
mt2032: xogc = 0x06
mt2032: xok = 0x00
mt2032: xogc = 0x05
mt2032: xogc = 0x05
mt2032: xok = 0x00
mt2032: xogc = 0x04
mt2032: xogc = 0x04
mt2032: xok = 0x00
mt2032: xogc = 0x03
bttv0: PLL: 28636363 => 35468950 .. ok
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: registered device radio0

Sérgio



--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/video4linux-list


Found the problem: bad isolation between the radio antenna input and the tv antenna input that caused interference of the cable tv signal by the signal captured by the radio antena (strong tv stations in my area).

Sérgio



--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/video4linux-list


This is strange though, because it worked on Windows without this problem...

Sérgio





[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux