LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 11-21-2004, 05:15 AM   #1
addy86
Member
 
Registered: Nov 2004
Location: Germany
Distribution: Debian Testing
Posts: 332

Rep: Reputation: 31
Question BT848 Video capture: picture is irrecognizable


Hi!

I have an old video capture PCI card (chip: BT848) and want to watch videos (or satellite TV) on my computer. So I plugged a SCART-to-SVHS adapter into my satellite receiver and connected this adapter with the PCI card using an S-Video cable.
When I start xawtv (without parameters), I see the picture (within the xawtv-window) three times, side by side. It is mostly black/gray/white with some red/green/blue spots. Difficult to describe; if you want to have a screenshot, I will mail it to you.
It seems like the horizontal synchronization is wrong (?)

I use the PAL norm.

My distribution: Debian (testing)
Kernel: 2.6.7-1-k7

'grep bttv /var/log/messages' gives this:
Nov 21 10:48:51 localhost kernel: bttv: driver version 0.9.14 loaded
Nov 21 10:48:51 localhost kernel: bttv: using 8 buffers with 2080k (520 pages) each for capture
Nov 21 10:48:51 localhost kernel: bttv: Bt8xx card found (0).
Nov 21 10:48:51 localhost kernel: bttv0: Bt848 (rev 18) at 0000:00:0b.0, irq: 10, latency: 32, mmio: 0xee001000
Nov 21 10:48:51 localhost kernel: bttv0: using: *** UNKNOWN/GENERIC *** [card=0,autodetected]
Nov 21 10:48:51 localhost kernel: bttv: readee error
Nov 21 10:48:51 localhost kernel: bttv0: using tuner=-1
Nov 21 10:48:51 localhost kernel: bttv0: i2c: checking for MSP34xx @ 0x80... not found
Nov 21 10:48:51 localhost kernel: bttv0: i2c: checking for TDA9875 @ 0xb0... not found
Nov 21 10:48:51 localhost kernel: bttv0: i2c: checking for TDA7432 @ 0x8a... not found
Nov 21 10:48:51 localhost kernel: bttv0: registered device video0
Nov 21 10:48:51 localhost kernel: bttv0: registered device vbi0


'lspci -vv' gives this:

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Region 0: Memory at e8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: ec000000-edffffff
Prefetchable memory behind bridge: e0000000-e7ffffff
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Region 4: I/O ports at d000 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, Cache Line Size: 0x08 (32 bytes)
Interrupt: pin D routed to IRQ 11
Region 4: I/O ports at d400 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, Cache Line Size: 0x08 (32 bytes)
Interrupt: pin D routed to IRQ 11
Region 4: I/O ports at d800 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin ? routed to IRQ 10
Capabilities: [68] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50)
Subsystem: VIA Technologies, Inc. VT82C686 AC97 Audio Controller
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin C routed to IRQ 11
Region 0: I/O ports at dc00 [size=256]
Region 1: I/O ports at e000 [size=4]
Region 2: I/O ports at e400 [size=4]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at e800 [size=256]
Region 1: Memory at ee000000 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:0b.0 Multimedia video controller: Brooktree Corporation Bt848 Video Capture (rev 12)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+
Latency: 32 (4000ns min, 10000ns max)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at ee001000 (32-bit, prefetchable) [size=4K]

0000:01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1) (prog-if 00 [VGA])
Subsystem: LeadTek Research Inc.: Unknown device d151
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at ec000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at e0000000 (32-bit, prefetchable) [size=128M]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [44] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>


It would be nice if you could help me

Last edited by addy86; 11-21-2004 at 05:19 AM.
 
Old 11-21-2004, 05:54 AM   #2
Draygo
Member
 
Registered: May 2004
Location: Frisco, TX
Distribution: Debian Unstable
Posts: 73

Rep: Reputation: 15
your tuner type is probably set wrong. From what i see its not getting auto detected properly and is defaulting to tuner=1.

try doing this.

rmmod bttv
modprobe bttv tuner=<x>

where X is any number up to i believe 19. After you modprobe try watching the tv again and see if that helps.

Once you find the proper tuner type then edit your /etc/modules file with an appropriate entry. Usually

bttv tuner=<x>

in there will work.
 
Old 11-21-2004, 07:25 AM   #3
addy86
Member
 
Registered: Nov 2004
Location: Germany
Distribution: Debian Testing
Posts: 332

Original Poster
Rep: Reputation: 31
Ok, I will try.

By the way, doesn't "tuner" have something to do with an antenna (I ask this because I do not use an antenna but rather the video recorder as input source. As you can see, I do not know much about that stuff ).
 
Old 11-21-2004, 06:42 PM   #4
Draygo
Member
 
Registered: May 2004
Location: Frisco, TX
Distribution: Debian Unstable
Posts: 73

Rep: Reputation: 15
Somewhat. One thing i know it does is define the frequency table used. Alot of the times you might see people complaining about the wrong channel being displayed. I can guarantee you its because they have the wrong tuner type. Also this explains why the channel is either fuzzy or the color is always shifting.

What you are talking about is the source type. That is where its either a composite in or antenna in.

Let me know if it worked.
 
Old 11-22-2004, 02:55 AM   #5
Lenard Spencer
Member
 
Registered: Sep 2004
Location: Florida
Distribution: Slackware, Linux from Scratch
Posts: 240

Rep: Reputation: 73
Quote:
Originally posted by addy86
Ok, I will try.

By the way, doesn't "tuner" have something to do with an antenna (I ask this because I do not use an antenna but rather the video recorder as input source. As you can see, I do not know much about that stuff ).
This page http://linux.bytesex.org/v4l2/bttv.html has info on the BT84x/87x chipset. Best would be to download the bttv source tarball and read the documentation, especially CARDLIST and TUNERLIST. Then add a line to etc/modprobe.conf "options bttv card=xx tuner=yy" using the numbers from the lists.

Hope this helps.
 
Old 11-27-2004, 01:55 AM   #6
addy86
Member
 
Registered: Nov 2004
Location: Germany
Distribution: Debian Testing
Posts: 332

Original Poster
Rep: Reputation: 31
I tried all possible tuners (from 0 to 45) but none worked. Then I discovered that my card is a CPH031 which seems to be manufactured by Typhoon, so it can be card=36 or card=53 (according to CARDLIST.bttv. Doing
rmmod bttv; modprobe bttv card=53 results in the following log in /var/log/syslog:

Nov 27 08:40:51 localhost kernel: bttv0: unloading
Nov 27 08:40:51 localhost kernel: bttv: driver version 0.9.14 loaded
Nov 27 08:40:51 localhost kernel: bttv: using 8 buffers with 2080k (520 pages) each for capture
Nov 27 08:40:51 localhost kernel: bttv: Bt8xx card found (0).
Nov 27 08:40:51 localhost kernel: bttv0: Bt848 (rev 18) at 0000:00:0b.0, irq: 10, latency: 32, mmio: 0xee001000
Nov 27 08:40:51 localhost kernel: bttv0: using: Typhoon TView RDS + FM Stereo / KNC1 TV Station RDS [card=53,insmod option]
Nov 27 08:40:51 localhost kernel: bttv0: gpio: en=00000000, out=00000000 in=00ffffff [init]
Nov 27 08:40:51 localhost kernel: tuner: chip found at addr 0xc0 i2c-bus bt848 #0 [sw]
Nov 27 08:40:51 localhost kernel: bttv0: using tuner=5
Nov 27 08:40:51 localhost kernel: tuner: type set to 5 (Philips PAL_BG (FI1216 and compatibles)) by bt848 #0 [sw]
Nov 27 08:40:51 localhost kernel: bttv0: i2c: checking for MSP34xx @ 0x80... not found
Nov 27 08:40:51 localhost kernel: bttv0: i2c: checking for TDA9875 @ 0xb0... not found
Nov 27 08:40:51 localhost kernel: bttv0: i2c: checking for TDA7432 @ 0x8a... not found
Nov 27 08:40:51 localhost kernel: bttv0: registered device video0
Nov 27 08:40:51 localhost kernel: bttv0: registered device vbi0
Nov 27 08:40:51 localhost kernel: bttv0: registered device radio0
Nov 27 08:40:51 localhost kernel: bttv0: PLL: 28636363 => 35468950 . ok

When I run xawtv, the following line is added to this log:

Nov 27 08:40:57 localhost kernel: tuner: TV freq (268435455.93) out of range (44-958)

However, although I can now recognize the picture, it is black and white and of a bad quality. I can send you a screenshot if this helps.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Bt848 Video capture card chrisstooss Linux - Hardware 37 12-04-2015 05:13 AM
how to capture a picture of mplayer movie weiweif Linux - Software 1 10-18-2004 11:47 PM
Capture support for dvd and video capture in linux is it even going to be real ever? maximalred Linux - Distributions 3 07-06-2003 07:29 PM
i can't capture a colour picture , i use bt878 on rh8.0. help me. tiejunsoft Linux - Hardware 2 10-24-2002 01:38 AM
Video Camera / Where are picture in my memory darky42 Programming 0 04-04-2002 05:54 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 01:54 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration