Board index Linux Hardware

bttv tuner problem with Hauppauge WinTV (model 190)

bttv tuner problem with Hauppauge WinTV (model 190)

Post by Mark Prusinows » Wed, 04 Jun 2003 14:09:37



Hi,

I'm having problems getting the bttv tuner to work with my WinTV card.
 The composite input is working fine with xawtv but when I switch to
Television input, I get this error msg:

tuner: TV freq (0.-6) out of range (44-958)

I've looked through newsgroup archives and based on similar problems
from the past tried specifying various tuner/driver types as options
to bttv and tuner modules. Nothin is working.  Here is my present
modules.conf:

pre-install bttv        modprobe -k tuner
options bttv  radio=0 card=10 tuner=2
options tuner type=2

As far as I know this is the correct setup for the model 190
Hauppauge.  The tuner on the card is the Philips FI1236 (#2).  This is
running on 2.4.20 smp and xfree86 4.1.  Does anyone have any
suggestions?

As far as I can tell the driver has detected everything correctly.
Below is the relevant syslog output from bttv:

tuner: ignoring Philips Parallel port adapter i2c adapter [id=0x10000]
bttv: driver version 0.7.96 loaded
bttv: using 4 buffers with 2080k (8320k total) for capture
bttv: Host bridge is Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host
bridge
bttv: Host bridge needs ETBF enabled.
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 17) at 00:11.0, irq: 17, latency: 64, mmio:
0xfc9fe000
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is
0070:13eb
bttv0: using: BT878(Hauppauge (bt878)) [card=10,insmod option]
bttv0: enabling ETBF (430FX/VP3 compatibilty)
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
i2c-dev.o: Registered 'bt848 #0' as minor 1
tuner: probing bt848 #0 i2c adapter [id=0x10005]

bttv0: i2c attach [client=Philips NTSC (FI1236 and compati,ok]
i2c-core.o: client [Philips NTSC (FI1236 and compati] registered to
adapter [bt8
48 #0](pos. 0).
i2c-core.o: adapter bt848 #0 registered as adapter 1.
bttv0: Hauppauge eeprom: model=38101, tuner=Philips FI1236 MK2 (2),
radio=no
bttv0: using tuner=2



tvaudio: TV audio decoder + audio/video mux driver
tvaudio: known chips:
tda9840,tda9873h,tda9874h/a,tda9850,tda9855,tea6300,tea642
0,tda8425,pic16c54 (PV951)
i2c-core.o: driver generic i2c audio driver registered.
bttv0: registered device video0
bttv0: registered device vbi0

Thanks for your help,

Mark

 
 
 
Top

bttv tuner problem with Hauppauge WinTV (model 190)

Post by Mark Prusinows » Thu, 05 Jun 2003 11:44:04


Well, I fixed the issues.
For the benefit of others who might experience a similar problem, the
culprit was the xawtv itself and not the tuner or bttv drivers.
Apparently xawtv does not like it one bit when you don't specify
channels in your $HOME/.xawtv.  It gets totally confused, seems to
ignore us-cable freq list and specifies bogus frequency to the tuner.
When all else fails you can always do v4lctl setfreq n, where n is the
desired freq you want to tune to.  Hope this helps.

> Hi,

> I'm having problems getting the bttv tuner to work with my WinTV card.
>  The composite input is working fine with xawtv but when I switch to
> Television input, I get this error msg:

> tuner: TV freq (0.-6) out of range (44-958)

> I've looked through newsgroup archives and based on similar problems
> from the past tried specifying various tuner/driver types as options
> to bttv and tuner modules. Nothin is working.  Here is my present
> modules.conf:

> pre-install bttv        modprobe -k tuner
> options bttv  radio=0 card=10 tuner=2
> options tuner type=2

> As far as I know this is the correct setup for the model 190
> Hauppauge.  The tuner on the card is the Philips FI1236 (#2).  This is
> running on 2.4.20 smp and xfree86 4.1.  Does anyone have any
> suggestions?

> As far as I can tell the driver has detected everything correctly.
> Below is the relevant syslog output from bttv:

> tuner: ignoring Philips Parallel port adapter i2c adapter [id=0x10000]
> bttv: driver version 0.7.96 loaded
> bttv: using 4 buffers with 2080k (8320k total) for capture
> bttv: Host bridge is Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host
> bridge
> bttv: Host bridge needs ETBF enabled.
> bttv: Bt8xx card found (0).
> bttv0: Bt878 (rev 17) at 00:11.0, irq: 17, latency: 64, mmio:
> 0xfc9fe000
> bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is
> 0070:13eb
> bttv0: using: BT878(Hauppauge (bt878)) [card=10,insmod option]
> bttv0: enabling ETBF (430FX/VP3 compatibilty)
> bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
> i2c-dev.o: Registered 'bt848 #0' as minor 1
> tuner: probing bt848 #0 i2c adapter [id=0x10005]

> bttv0: i2c attach [client=Philips NTSC (FI1236 and compati,ok]
> i2c-core.o: client [Philips NTSC (FI1236 and compati] registered to
> adapter [bt8
> 48 #0](pos. 0).
> i2c-core.o: adapter bt848 #0 registered as adapter 1.
> bttv0: Hauppauge eeprom: model=38101, tuner=Philips FI1236 MK2 (2),
> radio=no
> bttv0: using tuner=2



> tvaudio: TV audio decoder + audio/video mux driver
> tvaudio: known chips:
> tda9840,tda9873h,tda9874h/a,tda9850,tda9855,tea6300,tea642
> 0,tda8425,pic16c54 (PV951)
> i2c-core.o: driver generic i2c audio driver registered.
> bttv0: registered device video0
> bttv0: registered device vbi0

> Thanks for your help,

> Mark


 
 
 
Top

1. WinTV Hauppauge Model 495 / BTTV Sound Problem

Re: WinTV Hauppauge Model 495 / BTTV Sound Problem

I've  picked  up the new WinTV Theater card from Hauppauge (Model
495),  the  newest  bttv  distribution  and the latest kwintv and
xawtv packages.

I've  been  able  to  get  video  capture  to  work fine and I've
successfully  run  the  radio application (for FM) that came with
the  xawtv-3.0beta8 distribution. Sound works for this radio app,
but  I  have  not  been able to get sound working with any of the
video capture apps.

My  sound  card  works  fine  (AWE64)  and the mixer settings are
reasonable.

I have only silent TV, at the moment. (Works fine in Win98)

I'm using kernel 2.2.10.

When I loaded the bttv modules, I noticed the following:

=====
Linux video capture interface: v0.01 ALPHA
i2c: initialized
i2c: driver registered: tda8425
i2c: driver registered: tuner
bttv0: Brooktree Bt878 (rev 2) bus: 0, devfn: 88, irq: 9, memory: 0xe7003000.
PCI: Enabling bus mastering for device 00:58
bttv: 1 Bt8xx card(s) found.
bttv0: Hauppauge eeprom: tuner=Philips FM1236 (2)
bttv0: audio chip: TDA9840
bttv0: model: BT878(Hauppauge new (bt878))
i2c: bus registered: bt848-0
i2c: device attached: tuner (addr=0xc2, bus=bt848-0, driver=tuner)
bttv0: PLL: 28636363 => 35468950 ... ok
bttv0: PLL: switching off
=====

[ bttv0: audio chip: TDA9840 ] is the line that concerns me.

I'm wondering if this is a new audio chip, not yet supported?

Related /etc/module.conf entries are:

alias   char-major-81   bttv
pre-install bttv        modprobe -k tda8425; modprobe -k tuner
options bttv            radio=1 card=0
options msp3400         debug=0
options tda8425         debug=0
options tuner           type=2

I would be willing to do some work in the next couple of weeks to
help  with  this,  if  needed.  If this isn't supported yet, does
anyone have or know where I can obtain information on this chip?


+---------------------------------------------------------------------+



+---------------------------------------------------------------------+

2. weird mail problem

3. Help with bttv and tuner options for Hauppauge WinTV board

4. msdos fs module wth 1.3.58

5. Help with bttv and tuner options for Hauppauge WinTv card

6. bootpd n stuff

7. WinTV-Go (model 190) under Linux

8. SysVinit 2.50 - rc.local -doesn't load daemons

9. bttv problems: xawtv, matrox mil 2, hauppauge wintv

10. bttv + hauppauge + ntsc + tuner = problem

11. WinTV Go model 607 Problem with BTTV

12. Using bttv module with Hauppauge WinTV/pci

13. Help with bttv and tuner options for Hauppauge card


All times are UTC
Board index