jam you need to have two seperate dev files for your two differenct cards.

it looks like your /dev/video1 is being shared by both cards... but i'm wondering if you have a /dev/video or /dev/video0..

i guess you get the drift.. you can't really have two devices sharing the same dev file (or you shouldn't-- lets put it that way).

and i take for granted you've re-read this whole thread.. and remember to test each card independently-- before puting the second card in..

and to look for the newest drivers.. which DON'T always come from the manufacturer or maintainer-- but from individuals like us, who have problems and decide to fix them ourselves and then release the new driver on our own.

Did you tune your ivtv card? I'm just asking, cause I forgot about that when I first tried it cause it's never really mentioned anywhere.

You have to use ivtv-tune. Now depending on where you are located you may just need todo
ivtv-tune -c10 -d /dev/video0

or, if you are in europe you need to do
ivtv-tune -teurope-west -c E2 -d /dev/video0

or something like that. You need to find out what kind of frequency map your TV provider uses.

Tune with ivtv-tune in one terminal window and have mplayer point to your device with mplayer /dev/video0 in another window.

That should work.

OK well I've installed ivtv again.

Before I installed I had at least 40 video devices in /dev/ but now I only have 1 /dev/video0.

Also ivtv-detect can now only see the dvb card (but the card is definitely still fine as it shows in lspci).

So, Barbex, I think I need to have at least a second device showing first and then I will attempt ot tune it.

Halvy, can you explain how i stop /dev/video0 pointing at both cards if that is what is happening?

By the way mplayer "dvb://BBC ONE" (I'm in the UK) still plays the digital card fine!

Thanks again.

/dev/video0 can not and will not point at both cards. /dev/video1....255 are not files. They are device nodes.

If /dev/video0 comes up but not /dev/video1 is because a problem loading a module (driver). If you want to make sure the PVR card is at /dev/video0 and DVB card is on /dev/video1 is to an option. For my saa7134 module, I pass video_nr to do this. I suggest running /sbin/modinfo on the module.

What I read setting up a card has extra steps to take for UK than countries that uses NTSC. You will have to load up the tdaXXXX module to handle audio and specify a port.

What I suggest taking out the DVB card and try to get the PVR card to work. Before you put in the DVB card, specify what video device node the PVR should be at. When the PVR and DVB cards are in, both should work. If you want a GUI program to help you change channels easier, look up ptune-ui.pl on the internet or use find to search for it in your computer.

I recommend checking the logs. Do not use dmesg because it summarizes the logs too much. Read through /var/log/messages as root.

Gentoo makes installing and setting up ivtv modules with ease. Sorry, I have installed the ivtv modules and set the them up on Slackware, but Gentoo does make it easier. However, finding what firmware version for the PVR cards will be stable is a trial and error process with all distributions.

Yes I remember that, I had that too. Nothing to worry about.

I can only say how it worked for me, I had the dvb card under /dev/dvb/adapter0 and the PVR card under /dev/video0. So there is no sharing of the device nodes.


Since you can still watch TV with "dvb://BBC ONE", I would say everything is fine with your dvb card. I would suggest to take it out and get the PVR card working with ivtv first.

Then, when that works, put the dvb card back in. I have noticed that it was important to have ivtv load before dvb_bt8xx in modules.

Keep it up, you are close!

Hi Guys,

I don't have dvb_bt8xx in /etc/modules at all! Should I have?

Yes that's pretty much what I thought. I had not heard of two devices sharing the same node before.

Yeah I read that too but I have had the card working before without this so I have ignored it this time

Thanks all for your continuing support!

I'm not sure, for my dvb card "modprobe dvb_bt8xx" was the only thing necessary to install the card and then I put it in modules to have it loaded at boot-time.
To my knowledge dvb_bt8xx calls the following modules: bttv, bt878, dst, dst_ca, dvb_bt8xx.

Things may be different for your dvb card.

Hi all,
I'm also fighting with two cards: an Avermedia 771 with dvb v4l drivers and a PVR150 with ivtv drivers. I use Suse 9.3 with kernel 2.6.11.4. That is what I think I discovered:
My ivtv drivers substitute several drivers in the standard distribution ( for example tveeprom ). I saved the original drivers with .orig extension.
The first errors
bttv: disagrees about version of symbol tveeprom_hauppauge_analog[ 45.888986] bttv: Unknown symbol tveeprom_hauppauge_analog
is due to the fact that the driver tveeprom is not the orignal but the one that comes with ivtv.

If I substitute tveeprom.ko coming from ivtv drivers with the original one I'm able to load correctly all the drivers needed by avermedia card ( modprobe dvb-bt8xx ) and the pvr150 continue to work ( with mythtv ).
Apr 2 23:28:41 vigor10 kernel: bttv: driver version 0.9.15 loaded
Apr 2 23:28:41 vigor10 kernel: bttv: using 8 buffers with 2080k (520 pages) each for capture
Apr 2 23:28:41 vigor10 kernel: bttv: Bt8xx card found (0).
Apr 2 23:28:41 vigor10 kernel: ACPI: PCI interrupt 0000:00:0c.0[A] -> GSI 17 (level, low) -> IRQ 209
Apr 2 23:28:41 vigor10 kernel: bttv0: Bt878 (rev 17) at 0000:00:0c.0, irq: 209, latency: 64, mmio: 0xebe00000
Apr 2 23:28:41 vigor10 kernel: bttv0: detected: AVermedia AverTV DVB-T 771 [card=123], PCI subsystem ID is 1461:0771
Apr 2 23:28:41 vigor10 kernel: bttv0: using: Hauppauge WinTV PVR [card=80,insmod option]
Apr 2 23:28:41 vigor10 kernel: bttv0: gpio: en=00000000, out=00000000 in=00f0ff0f [init]
Apr 2 23:28:42 vigor10 udevd[2285]: move seq 1031 with timeout 10 to exec queue
Apr 2 23:28:42 vigor10 kernel: bttv0: no altera firmware [via hotplug]
Apr 2 23:28:42 vigor10 kernel: i2c-algo-bit.o: (0) scl=1, sda=1
Apr 2 23:28:42 vigor10 kernel: i2c-algo-bit.o: (1) scl=1, sda=0
Apr 2 23:28:42 vigor10 kernel: i2c-algo-bit.o: (2) scl=1, sda=1
Apr 2 23:28:42 vigor10 kernel: i2c-algo-bit.o: (3) scl=0, sda=1
Apr 2 23:28:42 vigor10 kernel: i2c-algo-bit.o: (4) scl=1, sda=1
Apr 2 23:28:42 vigor10 kernel: i2c-algo-bit.o: bt878 #0 [sw] passed test.
Apr 2 23:28:42 vigor10 kernel: tveeprom: Encountered bad packet header [ff]. Corrupt or not a Hauppauge eeprom.
Apr 2 23:28:42 vigor10 kernel: bttv0: using tuner=-1
Apr 2 23:28:42 vigor10 kernel: bttv0: i2c: checking for MSP34xx @ 0x80... not found
Apr 2 23:28:42 vigor10 kernel: bttv0: i2c: checking for TDA9875 @ 0xb0... not found
Apr 2 23:28:42 vigor10 kernel: bttv0: i2c: checking for TDA7432 @ 0x8a... not found
Apr 2 23:28:42 vigor10 kernel: tvaudio: TV audio decoder + audio/video mux driver
Apr 2 23:28:42 vigor10 udevd[2285]: move seq 1032 with timeout 10 to exec queue
Apr 2 23:28:42 vigor10 kernel: tvaudio: known chips: tda9840,tda9873h,tda9874h/a,tda9850,tda9855,tea6300,tea6320,tea6420,tda8425,pic16c54 (PV951),ta8874z
Apr 2 23:28:42 vigor10 kernel: bttv0: i2c: checking for TDA9887 @ 0x86... not found
Apr 2 23:28:42 vigor10 kernel: bttv0: registered device video1
Apr 2 23:28:42 vigor10 kernel: bttv0: registered device vbi1
Apr 2 23:28:42 vigor10 kernel: bttv0: registered device radio1
Apr 2 23:28:42 vigor10 kernel: bttv0: PLL: 28636363 => 35468950 .. ok
Apr 2 23:28:42 vigor10 kernel: bt878: AUDIO driver version 0.0.0 loaded
Apr 2 23:28:42 vigor10 kernel: bt878: Bt878 AUDIO function found (0).
Apr 2 23:28:42 vigor10 kernel: ACPI: PCI interrupt 0000:00:0c.1[A] -> GSI 17 (level, low) -> IRQ 209
Apr 2 23:28:42 vigor10 kernel: bt878(0): Bt878 (rev 17) at 00:0c.1, irq: 209, latency: 64, memory: 0xebf00000

But at this point I'm not able to scan the channels because I got the error
./scan dvb-t/it-torino
scanning dvb-t/it-torino
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
main:1882: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 19 No such device.

If we can help each other with some tests or discovering info on the net we could try to solve the problem

Sandro

Here is some confirmation from the ivtv wiki http://ivtvdriver.org/index.php/Howto for using the original kernel module tveeprom.ko with the two cards:

Well that is exactly what I did and it has worked (something else broke it in the meantime and I'm reinstalling right now), so this is the way to go, I think.