Re: [linux-dvb] DVICO HDTV Dual Express2

2011-04-05 Thread Nathan Stitt
I know I shouldn't have quoted mythtv to identify a problem, so I've tinkered with this a little more and can reproduce it using the dvb utilities. I can reproduce the problem using tzap and cat'ing /dev/dvb/adapter[23]/dvr0 to files. When one of the tuners tunes the the bad transponder, the files

Re: [linux-dvb] DVICO HDTV Dual Express2

2011-04-04 Thread Nathan Stitt
I have this card. It had been working fine on 2.6.32 kernels, even using both tuners. Only complaint was that the stream from one transponder was always rubbish (but that channel had rubbish shows mostly anyway, so, meh). Upgrading to a 2.6.35 kernel in an attempt to have a newly added card suppo

Re: [linux-dvb] DVICO HDTV Dual Express2

2011-04-04 Thread Daniel O'Connor
On 05/04/2011, at 8:18, Vincent McIntyre wrote: > On 4/4/11, Daniel O'Connor wrote: >> >> I take it you use both tuners? I find I can only use one otherwise one of >> them hangs whatever app is using it. >> > > I do. I haven't tested very carefully that I can use both tuners at > once successf

Re: [linux-dvb] DVICO HDTV Dual Express2

2011-04-04 Thread Vincent McIntyre
On 4/4/11, Daniel O'Connor wrote: > > I take it you use both tuners? I find I can only use one otherwise one of > them hangs whatever app is using it. > I do. I haven't tested very carefully that I can use both tuners at once successfully but I am pretty sure there have been times when both have

Re: [linux-dvb] DVICO HDTV Dual Express2

2011-04-04 Thread Daniel O'Connor
On 04/04/2011, at 20:01, Vincent McIntyre wrote: Could you post the output of > lspci -vvv -nn > for the device in question - you'll also need to give the -s argument, > eg -s 02:00.0 > or whatever. > > This is so it is clear what chips your example of the card is using - > a given card may be i

Re: [linux-dvb] DVICO HDTV Dual Express2

2011-04-04 Thread Vincent McIntyre
Hi Nick, Could you post the output of lspci -vvv -nn for the device in question - you'll also need to give the -s argument, eg -s 02:00.0 or whatever. This is so it is clear what chips your example of the card is using - a given card may be implemented with different chipsets over time dependin