Difference between revisions of "Bttv devices (bt848, bt878)"

From LinuxTVWiki
Jump to: navigation, search
Line 1: Line 1:
I'm new to v4l so take these comments with a grain of salt.  If you find that I'm wrong about something, please create an account for yourself, login, and edit my comments so as to correct them.
+
===Introduction===
  
From the 2.6.11 kernel documentation (see /usr/src/linux/Documentation/video4linux/CARDLIST.bttv), the bttv driver in v4l supports the following devices:
+
===Supported devices===
  
<ol>
+
* [[Cardlist.BTTV | List of bttv devices supported in the linux kernel]]
<li>card=1 - MIRO PCTV
+
<li>card=2 - Hauppauge (bt848)
+
<li>card=3 - STB, Gateway P/N 6000699 (bt848)
+
<li>card=4 - Intel Create and Share PCI/ Smart Video Recorder III
+
<li>card=5 - Diamond DTV2000
+
<li>card=6 - AVerMedia TVPhone
+
<li>card=7 - MATRIX-Vision MV-Delta
+
<li>card=8 - Lifeview FlyVideo II (Bt848) LR26 / MAXI TV Video PCI2 LR26
+
<li>card=9 - IMS/IXmicro TurboTV
+
<li>card=10 - Hauppauge (bt878)
+
<li>card=11 - MIRO PCTV pro
+
<li>card=12 - ADS Technologies Channel Surfer TV (bt848)
+
<li>card=13 - AVerMedia [[TVCapture 98]]
+
<li>card=14 - Aimslab Video Highway Xtreme (VHX)
+
<li>card=15 - Zoltrix TV-Max
+
<li>card=16 - Prolink Pixelview PlayTV (bt878)
+
<li>card=17 - Leadtek WinView 601
+
<li>card=18 - AVEC Intercapture
+
<li>card=19 - Lifeview FlyVideo II EZ /FlyKit LR38 Bt848 (capture only)
+
<li>card=20 - CEI Raffles Card
+
<li>card=21 - Lifeview FlyVideo 98/ Lucky Star Image World ConferenceTV LR50
+
<li>card=22 - Askey CPH050/ Phoebe Tv Master + FM
+
<li>card=23 - Modular Technology MM201/MM202/MM205/MM210/MM215 PCTV, bt878
+
<li>card=24 - Askey CPH05X/06X (bt878) [many vendors]
+
<li>card=25 - Terratec TerraTV+ Version 1.0 (Bt848)/ Terra TValue Version 1.0/ Vobis TV-Boostar
+
<li>card=26 - Hauppauge WinCam newer (bt878)
+
<li>card=27 - Lifeview FlyVideo 98/ MAXI TV Video PCI2 LR50
+
<li>card=28 - Terratec TerraTV+ Version 1.1 (bt878)
+
<li>card=29 - Imagenation PXC200
+
<li>card=30 - Lifeview FlyVideo 98 LR50
+
<li>card=31 - Formac iProTV, Formac ProTV I (bt848)
+
<li>card=32 - Intel Create and Share PCI/ Smart Video Recorder III
+
<li>card=33 - Terratec TerraTValue Version Bt878
+
<li>card=34 - Leadtek WinFast 2000/ WinFast 2000 XP
+
<li>card=35 - Lifeview FlyVideo 98 LR50 / Chronos Video Shuttle II
+
<li>card=36 - Lifeview FlyVideo 98FM LR50 / Typhoon TView TV/FM Tuner
+
<li>card=37 - Prolink PixelView PlayTV pro
+
<li>card=38 - Askey CPH06X TView99
+
<li>card=39 - Pinnacle PCTV Studio/Rave
+
<li>card=40 - STB TV PCI FM, Gateway P/N 6000704 (bt878), 3Dfx VoodooTV 100
+
<li>card=41 - AVerMedia TVPhone 98
+
<li>card=42 - ProVideo PV951
+
<li>card=43 - Little OnAir TV
+
<li>card=44 - Sigma TVII-FM
+
<li>card=45 - MATRIX-Vision MV-Delta 2
+
<li>card=46 - Zoltrix Genie TV/FM
+
<li>card=47 - Terratec TV/Radio+
+
<li>card=48 - Askey CPH03x/ Dynalink Magic TView
+
<li>card=49 - IODATA GV-BCTV3/PCI
+
<li>card=50 - Prolink PV-BT878P+4E / PixelView PlayTV PAK / Lenco MXTV-9578 CP
+
<li>card=51 - Eagle Wireless Capricorn2 (bt878A)
+
<li>card=52 - Pinnacle PCTV Studio Pro
+
<li>card=53 - Typhoon TView RDS + FM Stereo / KNC1 TV Station RDS
+
<li>card=54 - Lifeview FlyVideo 2000 /FlyVideo A2/ Lifetec LT 9415 TV [LR90]
+
<li>card=55 - Askey CPH031/ BESTBUY Easy TV
+
<li>card=56 - Lifeview FlyVideo 98FM LR50
+
<li>card=57 - GrandTec 'Grand Video Capture' (Bt848)
+
<li>card=58 - Askey CPH060/ Phoebe TV Master Only (No FM)
+
<li>card=59 - Askey CPH03x TV Capturer
+
<li>card=60 - Modular Technology MM100PCTV
+
<li>card=61 - AG Electronics GMV1
+
<li>card=62 - Askey CPH061/ BESTBUY Easy TV (bt878)
+
<li>card=63 - ATI TV-Wonder
+
<li>card=64 - ATI TV-Wonder VE
+
<li>card=65 - Lifeview FlyVideo 2000S LR90
+
<li>card=66 - Terratec TValueRadio
+
<li>card=67 - IODATA GV-BCTV4/PCI
+
<li>card=68 - 3Dfx VoodooTV FM (Euro), VoodooTV 200 (USA)
+
<li>card=69 - Active Imaging AIMMS
+
<li>card=70 - Prolink Pixelview PV-BT878P+ (Rev.4C,8E)
+
<li>card=71 - Lifeview FlyVideo 98EZ (capture only) LR51
+
<li>card=72 - Prolink Pixelview PV-BT878P+9B (PlayTV Pro rev.9B FM+NICAM)
+
<li>card=73 - Sensoray 311
+
<li>card=74 - RemoteVision MX (RV605)
+
<li>card=75 - Powercolor MTV878/ MTV878R/ MTV878F
+
<li>card=76 - Canopus WinDVR PCI (COMPAQ Presario 3524JP, 5112JP)
+
<li>card=77 - GrandTec Multi Capture Card (Bt878)
+
<li>card=78 - Jetway TV/Capture JW-TV878-FBK, Kworld KW-TV878RF
+
<li>card=79 - DSP Design TCVIDEO
+
<li>card=80 - Hauppauge WinTV PVR
+
<li>card=81 - IODATA GV-BCTV5/PCI
+
<li>card=82 - Osprey 100/150 (878)
+
<li>card=83 - Osprey 100/150 (848)
+
<li>card=84 - Osprey 101 (848)
+
<li>card=85 - Osprey 101/151
+
<li>card=86 - Osprey 101/151 w/ svid
+
<li>card=87 - Osprey 200/201/250/251
+
<li>card=88 - Osprey 200/250
+
<li>card=89 - Osprey 210/220
+
<li>card=90 - Osprey 500
+
<li>card=91 - Osprey 540
+
<li>card=92 - Osprey 2000
+
<li>card=93 - IDS Eagle
+
<li>card=94 - Pinnacle PCTV Sat
+
<li>card=95 - Formac ProTV II (bt878)
+
<li>card=96 - MachTV
+
<li>card=97 - Euresys Picolo
+
<li>card=98 - ProVideo PV150
+
<li>card=99 - AD-TVK503
+
<li>card=100 - Hercules Smart TV Stereo
+
<li>card=101 - Pace TV & Radio Card
+
<li>card=102 - IVC-200
+
<li>card=103 - Grand X-Guard / Trust 814PCI
+
<li>card=104 - Nebula Electronics DigiTV
+
<li>card=105 - ProVideo PV143
+
<li>card=106 - PHYTEC VD-009-X1 MiniDIN (bt878)
+
<li>card=107 - PHYTEC VD-009-X1 Combi (bt878)
+
<li>card=108 - PHYTEC VD-009 MiniDIN (bt878)
+
<li>card=109 - PHYTEC VD-009 Combi (bt878)
+
<li>card=110 - IVC-100
+
<li>card=111 - IVC-120G
+
<li>card=112 - pcHDTV HD-2000 TV
+
<li>card=113 - Twinhan DST + clones
+
<li>card=114 - Winfast VC100
+
<li>card=115 - Teppro TEV-560/InterVision IV-560
+
<li>card=116 - SIMUS GVC1100
+
<li>card=117 - NGS NGSTV+
+
<li>card=118 - LMLBT4
+
<li>card=119 - Tekram M205 PRO
+
<li>card=120 - Conceptronic CONTVFMi
+
</ol>
+
  
 +
===Installation===
  
If you don't have one of these devices, then it might be a rather difficult challenge to get your card working with the bttv driver because there are a number of parameters (set in drivers/media/video/bttv-cards.c) to set for each card and they tend to be different for each card and learning what those parameters need to be for each card is not trivialSometimes you must run your video software in windoze as well as some monitoring software like BtSpy in order to determine the correct hardware settings used in windoze and then use that information to modify bttv-cards.c and create a new card= entry for your cardMake sure you post your findings here and on the video4linux mailing list (video4linux-list@redhat.com) if you do thatYou could also try loading the bttv module with the card= parameter set to each one of the cards listed above just to see if you'll get lucky and find one that works for your cardAgain, if you are successful, then share your results with the rest of us via this wiki and the list.
+
From Gerd Knorr's "README.bttv" distributed in packages such as motv.
 +
 
 +
====Some hints to get the bttv driver up and running====
 +
 
 +
=====General hints=====
 +
 
 +
1. Make sure if your board is recognized correctly. The bttv driver
 +
should print a line like this one (Use the 'dmesg' command to see the kernel messages):
 +
 
 +
bttv0: model: BT848(Hauppauge old)
 +
 
 +
If your card isn't autodetected correctly, you have to specify the
 +
board type as insmod argument (card=n).  You might also have to specify tuner=x and pll=x.
 +
 
 +
Check the driver documentation for details and a list of supported
 +
cards.  The standard kernel has the bttv documentation in the
 +
Documentation/video4linux/bttv directory.
 +
 
 +
2. [It's recommended you use a recent kernel.]
 +
 
 +
3. If you have problems with xawtv, you should open a xterm (or
 +
whatever your favorite terminal app is) and start xawtv from
 +
there. This way you'll see any error messages xawtv might print on
 +
stderr which should help to find the source of the problems.
 +
 
 +
4. If something broke after an update, have a look at the changelog.
 +
It might be mentioned there.
 +
 
 +
=====Common problems=====
 +
 
 +
?: I have a black screen in overlay mode
 +
 
 +
!: The driver was not initialized correctly, v4l-conf (or the
 +
X-Server) has to configure the bttv driver with the current video
 +
mode and framebuffer address first.  Check if v4l-conf is installed
 +
suid root, it needs root priviliges to do this.  You can also start
 +
v4l-conf from a terminal and check the messages it prints.
 +
 
 +
?: I have a blue screen.
 +
!: Good, the overlay is workingA blue screen is what you get if the
 +
grabber chip has no input signal.  You are probably using the wrong
 +
video source, pick another.  Also happens sometimes if the tuner
 +
type is wrong, check the driver configuration.
 +
 
 +
?: I have a noisy screen and/or can't tune (some) stations.
 +
!: Most likely the tuner types is wrong, check the driver configuration.
 +
It's no problem to do trial-and-error here.
 +
 
 +
?: The video is outside the window and spread in thin lines over the
 +
screen.
 +
I: xawtv / v4l-conf didn't autodetect the color depth for your screen
 +
correctlyYou can fix that with xawtv's -bpp switch.
 +
 
 +
?: Only the left part of the window is updated, the right one is updated
 +
never / sometimes / only if the window is small.
 +
!: Your graphics card and/or motherboard can't deal with the data rate
 +
going over the PCI bus, leading to canceled PCI transfersReduce
 +
the color depth, with 16 bpp instead of 32 bpp should work much
 +
better.
 +
 
 +
 
 +
=====Hardware specific problems=====
 +
 
 +
* bttv + DRI seem not to play nicely together with some cards (ATI Rage128). The linux box just freezes. Don't know why. Suspect it's either a hardware problem or a bug somewhere in DRI (either kernel or xfree86). The only workaround I know of is to turn off DRI.
 +
 
 +
* Some motherboard chipsets have PCI bugs, especially with PCI-PCI transfers which are used for video overlayThe bt848/878 chips have some bug compatibility options, which can be enabled to workaround these problems. Have a look at the triton1 and vsfx insmod options. For some known-buggy chipsets these are enabled automagically.
 +
 
 +
* Sometimes IRQ sharing causes trouble. It works most of the time, but in combination with some hardware and/or drivers it doesn't work. Especially graphic cards are known to cause trouble due to the lack of a IRQ handler. Try disabling the VGA IRQ in the BIOS. Try moving cards to another PCI slot.  Your motherboard manual should tell you which PCI slots share IRQ's.

Revision as of 04:20, 9 May 2005

Introduction

Supported devices

Installation

From Gerd Knorr's "README.bttv" distributed in packages such as motv.

Some hints to get the bttv driver up and running

General hints

1. Make sure if your board is recognized correctly. The bttv driver should print a line like this one (Use the 'dmesg' command to see the kernel messages):

bttv0: model: BT848(Hauppauge old)

If your card isn't autodetected correctly, you have to specify the board type as insmod argument (card=n). You might also have to specify tuner=x and pll=x.

Check the driver documentation for details and a list of supported cards. The standard kernel has the bttv documentation in the Documentation/video4linux/bttv directory.

2. [It's recommended you use a recent kernel.]

3. If you have problems with xawtv, you should open a xterm (or whatever your favorite terminal app is) and start xawtv from there. This way you'll see any error messages xawtv might print on stderr which should help to find the source of the problems.

4. If something broke after an update, have a look at the changelog. It might be mentioned there.

Common problems

?: I have a black screen in overlay mode

!: The driver was not initialized correctly, v4l-conf (or the X-Server) has to configure the bttv driver with the current video mode and framebuffer address first. Check if v4l-conf is installed suid root, it needs root priviliges to do this. You can also start v4l-conf from a terminal and check the messages it prints.

?: I have a blue screen. !: Good, the overlay is working. A blue screen is what you get if the grabber chip has no input signal. You are probably using the wrong video source, pick another. Also happens sometimes if the tuner type is wrong, check the driver configuration.

?: I have a noisy screen and/or can't tune (some) stations. !: Most likely the tuner types is wrong, check the driver configuration. It's no problem to do trial-and-error here.

?: The video is outside the window and spread in thin lines over the screen. I: xawtv / v4l-conf didn't autodetect the color depth for your screen correctly. You can fix that with xawtv's -bpp switch.

?: Only the left part of the window is updated, the right one is updated never / sometimes / only if the window is small. !: Your graphics card and/or motherboard can't deal with the data rate going over the PCI bus, leading to canceled PCI transfers. Reduce the color depth, with 16 bpp instead of 32 bpp should work much better.


Hardware specific problems
  • bttv + DRI seem not to play nicely together with some cards (ATI Rage128). The linux box just freezes. Don't know why. Suspect it's either a hardware problem or a bug somewhere in DRI (either kernel or xfree86). The only workaround I know of is to turn off DRI.
* Some motherboard chipsets have PCI bugs, especially with PCI-PCI transfers which are used for video overlay.  The bt848/878 chips have some bug compatibility options, which can be enabled to workaround these problems. Have a look at the triton1 and vsfx insmod options. For some known-buggy chipsets these are enabled automagically.
  • Sometimes IRQ sharing causes trouble. It works most of the time, but in combination with some hardware and/or drivers it doesn't work. Especially graphic cards are known to cause trouble due to the lack of a IRQ handler. Try disabling the VGA IRQ in the BIOS. Try moving cards to another PCI slot. Your motherboard manual should tell you which PCI slots share IRQ's.