ImpactVCB 64405 low-profile PCI problem

ImpactVCB 64405 low-profile PCI problem

[Eric Schwartz]

Hi all,

I'm having a frustrating problem with getting a brand new Hauppauge card
to work with v4l, of the ImpactVCB 64405 low-profile PCI variety. I have
a basic NTSC camera that I want to hook up to one of the composite
inputs. And yes, during my troubleshooting efforts I succumbed to the
temptation of plugging it into an XP box (gasp!) and verified that the
hardware works perfectly fine.

Vanilla kernel versions 2.6.21, 2.6.24, and 2.6.28 all detect the
presence of the card and painlessly load the bttv module. According to
dmesg, it audodetects the type of card and even reads the exact model
string off the eeprom. (see dmesg output pasted below)

So far so good, eh? When I plug the camera into each of the inputs, I
get nothing on /dev/video0. Not exactly all zeroes, to be precise, but
close. A hexdump shows that there are occasional "c0"s mixed in with the
"00"s. Using "dov4l -i" lets me change the inputs as expected -- no
errors when the input number is in range, error when it's > 3.

Searching Google, I found that some people extracted firmware from a
Windows driver for a similar card and passed the "firm_altera=fwfile"
parameter to modprobe. I got the firmware file in question (from another
driver disk; it wasn't on the one that came with the card) but the
module balks at accepting that parameter at all. (bttv: Unknown
parameter firm_altera)

Anyone have experience with getting this card to work? What I thought
was going to be an easy project has quickly turned into a nightmare. Any
help will be appreciated.

Thanks,
Eric Schwartz

--

sunset:~# dmesg | grep bttv
bttv: driver version 0.9.17 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv 0000:02:0a.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
bttv0: Bt878 (rev 17) at 0000:02:0a.0, irq: 11, latency: 64, mmio:
0xf6001000
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: Hauppauge (bt878) [card=10,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00ffffff [init]
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
bttv0: Hauppauge eeprom indicates model#64405
bttv0: tuner absent
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: PLL: 28636363 => 35468950 .. ok

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

Re: ImpactVCB 64405 low-profile PCI problem

[CityK]

Eric Schwartz wrote:
> Hi all,
>
> I'm having a frustrating problem with getting a brand new Hauppauge card
> to work with v4l, of the ImpactVCB 64405 low-profile PCI variety. I have
> a basic NTSC camera that I want to hook up to one of the composite
> inputs. And yes, during my troubleshooting efforts I succumbed to the
> temptation of plugging it into an XP box (gasp!) and verified that the
> hardware works perfectly fine.
>
> Vanilla kernel versions 2.6.21, 2.6.24, and 2.6.28 all detect the
> presence of the card and painlessly load the bttv module. According to
> dmesg, it audodetects the type of card and even reads the exact model
> string off the eeprom. (see dmesg output pasted below)
>
> So far so good, eh? When I plug the camera into each of the inputs, I
> get nothing on /dev/video0. Not exactly all zeroes, to be precise, but
> close. A hexdump shows that there are occasional "c0"s mixed in with the
> "00"s. Using "dov4l -i" lets me change the inputs as expected -- no
> errors when the input number is in range, error when it's > 3.
>
> Searching Google, I found that some people extracted firmware from a
> Windows driver for a similar card and passed the "firm_altera=fwfile"
> parameter to modprobe. I got the firmware file in question (from another
> driver disk; it wasn't on the one that came with the card) but the
> module balks at accepting that parameter at all. (bttv: Unknown
> parameter firm_altera)
>
> Anyone have experience with getting this card to work? What I thought
> was going to be an easy project has quickly turned into a nightmare. Any
> help will be appreciated.
>
> Thanks,
> Eric Schwartz
>
> --
>
> sunset:~# dmesg | grep bttv
> bttv: driver version 0.9.17 loaded
> bttv: using 8 buffers with 2080k (520 pages) each for capture
> bttv: Bt8xx card found (0).
> bttv 0000:02:0a.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
> bttv0: Bt878 (rev 17) at 0000:02:0a.0, irq: 11, latency: 64, mmio:
> 0xf6001000
> bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
> bttv0: using: Hauppauge (bt878) [card=10,autodetected]
> bttv0: gpio: en=00000000, out=00000000 in=00ffffff [init]
> bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
> bttv0: Hauppauge eeprom indicates model#64405
> bttv0: tuner absent
> bttv0: i2c: checking for MSP34xx @ 0x80... not found
> bttv0: i2c: checking for TDA9875 @ 0xb0... not found
> bttv0: i2c: checking for TDA7432 @ 0x8a... not found
> bttv0: registered device video0
> bttv0: registered device vbi0
> bttv0: PLL: 28636363 => 35468950 .. ok
>
> --

I don't know the device, but I don't think it requires a firmware -- from the pic on Hauppauge's website, it looks to be a plain jane bt878 card (http://www.hauppauge.com/site/products/data_impactvcb.html).

I do notice that there are two entries in the bttv cardlist (http://linuxtv.org/hg/v4l-dvb/file/tip/linux/Documentation/video4linux/CARDLIST.bttv) for that particular subsystem ID, a rather generic Hauppauge entry for card 10 (which your device is apparently being autodetected as) and what looks to be the actual specific entry for your device, card 143.    

Try using the later card number (in your relevant modprobe config file or via command line loading) and see if that has any impact.