CinergyT2 not working with newer alternative driver

CinergyT2 not working with newer alternative driver

[Jason Harvey]

I have been successfully using VDR with two CinergyT2s for 18 months.
After adding a Hauppage NOVA-S2-HD I updated my v4l-dvb drivers hoping 
to get S2 capability and test a newer VDR for HD reception.

The CinergyT2s stopped working. The kernel module loads, the blue leds 
flash as expected but they don't lock on to a signal for long.
Signal strength shown in femon is erratic and a lock only rarely achieved.

I checked through the mercurial tree to see what had changed.
It looks like the following change is the one that stops the CinergyT2s 
working on my system.
http://git.kernel.org/?p=linux/kernel/git/mchehab/devel.git;a=commit;h=986bd1e58b18c09b753f797df19251804bfe3e84

I deleted the newer version of the module and replace it with the 
previous deleted code.
Make'd and installed the old version works as expected.

Machine they're plugged into is running Fedora 10, 
2.6.27.12-170.2.5.fc10.i686
I downloaded the current v4l-dvb today (31Jan2009) and tried it all 
again before posting this message.

Not sure where to look next, I did start to capture the USB traffic to 
see if I could spot the difference...

Thanks,
Jason

Re: CinergyT2 not working with newer alternative driver

[Thierry Merle]

Hi Jason,
Jason Harvey wrote:
> I have been successfully using VDR with two CinergyT2s for 18 months.
> After adding a Hauppage NOVA-S2-HD I updated my v4l-dvb drivers hoping
> to get S2 capability and test a newer VDR for HD reception.
> 
> The CinergyT2s stopped working. The kernel module loads, the blue leds
> flash as expected but they don't lock on to a signal for long.
> Signal strength shown in femon is erratic and a lock only rarely achieved.
> 
> I checked through the mercurial tree to see what had changed.
> It looks like the following change is the one that stops the CinergyT2s
> working on my system.
> http://git.kernel.org/?p=linux/kernel/git/mchehab/devel.git;a=commit;h=986bd1e58b18c09b753f797df19251804bfe3e84
> 
> 
> I deleted the newer version of the module and replace it with the
> previous deleted code.
> Make'd and installed the old version works as expected.
> 
> Machine they're plugged into is running Fedora 10,
> 2.6.27.12-170.2.5.fc10.i686
> I downloaded the current v4l-dvb today (31Jan2009) and tried it all
> again before posting this message.
> 
> Not sure where to look next, I did start to capture the USB traffic to
> see if I could spot the difference...
>
Please take a look at the message logs (dmesg).
You can follow the instructions described here http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
and report where it fails.

I use tzap like this: tzap -c $HOME/.tzap/channels.conf -s -t 120 -r -o output.mpg "SomeChannel"
I am able to play with mplayer too.
Regards,
Thierry

Re: CinergyT2 not working with newer alternative driver

[Jason Harvey]

Thierry Merle wrote:
> Hi Jason,
> Jason Harvey wrote:
>   
>> I have been successfully using VDR with two CinergyT2s for 18 months.
>> After adding a Hauppage NOVA-S2-HD I updated my v4l-dvb drivers hoping
>> to get S2 capability and test a newer VDR for HD reception.
>>
>> The CinergyT2s stopped working. The kernel module loads, the blue leds
>> flash as expected but they don't lock on to a signal for long.
>> Signal strength shown in femon is erratic and a lock only rarely achieved.
>>
>> I checked through the mercurial tree to see what had changed.
>> It looks like the following change is the one that stops the CinergyT2s
>> working on my system.
>> http://git.kernel.org/?p=linux/kernel/git/mchehab/devel.git;a=commit;h=986bd1e58b18c09b753f797df19251804bfe3e84
>>
>>
>> I deleted the newer version of the module and replace it with the
>> previous deleted code.
>> Make'd and installed the old version works as expected.
>>
>> Machine they're plugged into is running Fedora 10,
>> 2.6.27.12-170.2.5.fc10.i686
>> I downloaded the current v4l-dvb today (31Jan2009) and tried it all
>> again before posting this message.
>>
>> Not sure where to look next, I did start to capture the USB traffic to
>> see if I could spot the difference...
>>
>>     
> Please take a look at the message logs (dmesg).
> You can follow the instructions described here http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
> and report where it fails.
>
> I use tzap like this: tzap -c $HOME/.tzap/channels.conf -s -t 120 -r -o output.mpg "SomeChannel"
> I am able to play with mplayer too.
> Regards,
> Thierry
>   
Hi Thierry,

Thank you for the quick reply.
I should have looked in dmesg before...
Checking dmesg before I used tzap shows a problem. dvb-usb: recv bulk 
message failed: -110

**** Extract of dmesg ****

dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm 
state.
dvb-usb: will pass the complete MPEG2 transport stream to the software 
demuxer.
DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T 
Receiver)
DVB: registering adapter 0 frontend 0 (TerraTec/qanu USB2.0 Highspeed 
DVB-T Receiver)...
input: IR-receiver inside an USB DVB receiver as 
/devices/pci0000:00/0000:00:1a.7/usb1/1-1/input/input8
dvb-usb: schedule remote query interval to 50 msecs.
dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully 
initialized and connected.
dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm 
state.
dvb-usb: will pass the complete MPEG2 transport stream to the software 
demuxer.
DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T 
Receiver)
DVB: registering adapter 1 frontend 0 (TerraTec/qanu USB2.0 Highspeed 
DVB-T Receiver)...
input: IR-receiver inside an USB DVB receiver as 
/devices/pci0000:00/0000:00:1d.7/usb2/2-5/input/input9
dvb-usb: schedule remote query interval to 50 msecs.
dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully 
initialized and connected.
usbcore: registered new interface driver cinergyT2

dvb-usb: recv bulk message failed: -110
dvb-usb: recv bulk message failed: -110

****

Running tzap fails to tune/lock

#tzap -a 0 -c channels.conf_dvbt -s -t 120 -r -o output.mpg "BBC ONE"

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file 'channels.conf_dvbt'
tuning to 505833330 Hz
video pid 0x0258, audio pid 0x0259
status 01 | signal c11f | snr 0000 | ber ffffffff | unc ffffffff |

No more messages in dmesg.

I shut down the PC, removed all power, unplugged the CinergyT2s, gave it 
twenty seconds and powered back up.
Once it had booted I plugged in one of the devices and the dmesg output 
below.


usb 2-5: new high speed USB device using ehci_hcd and address 3
usb 2-5: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid 
maxpacket 64
usb 2-5: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has 
invalid maxpacket 64
usb 2-5: configuration #1 chosen from 1 choice
usb 2-5: New USB device found, idVendor=0ccd, idProduct=0038
usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-5: Product: Cinergy T?
usb 2-5: Manufacturer: TerraTec GmbH
dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm 
state.
dvb-usb: will pass the complete MPEG2 transport stream to the software 
demuxer.
DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T Receiver)
DVB: registering adapter 1 frontend 0 (TerraTec/qanu USB2.0 Highspeed 
DVB-T Receiver)...
input: IR-receiver inside an USB DVB receiver as 
/devices/pci0000:00/0000:00:1d.7/usb2/2-5/input/input9
dvb-usb: schedule remote query interval to 50 msecs.
dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully 
initialized and connected.
usbcore: registered new interface driver cinergyT2
dvb-usb: recv bulk message failed: -110

Cannot tzap or scan.

With the old version of the driver I don't have any trouble at all.

Hope this helps.

Regards, Jason

Re: CinergyT2 not working with newer alternative driver

[Thierry Merle]

Jason Harvey wrote:
> Thierry Merle wrote:
>> Hi Jason,
>> Jason Harvey wrote:
>>  
>>> I have been successfully using VDR with two CinergyT2s for 18 months.
>>> After adding a Hauppage NOVA-S2-HD I updated my v4l-dvb drivers hoping
>>> to get S2 capability and test a newer VDR for HD reception.
>>>
>>> The CinergyT2s stopped working. The kernel module loads, the blue leds
>>> flash as expected but they don't lock on to a signal for long.
>>> Signal strength shown in femon is erratic and a lock only rarely
>>> achieved.
>>>
>>> I checked through the mercurial tree to see what had changed.
>>> It looks like the following change is the one that stops the CinergyT2s
>>> working on my system.
>>> http://git.kernel.org/?p=linux/kernel/git/mchehab/devel.git;a=commit;h=986bd1e58b18c09b753f797df19251804bfe3e84
>>>
>>>
>>>
>>> I deleted the newer version of the module and replace it with the
>>> previous deleted code.
>>> Make'd and installed the old version works as expected.
>>>
>>> Machine they're plugged into is running Fedora 10,
>>> 2.6.27.12-170.2.5.fc10.i686
>>> I downloaded the current v4l-dvb today (31Jan2009) and tried it all
>>> again before posting this message.
>>>
>>> Not sure where to look next, I did start to capture the USB traffic to
>>> see if I could spot the difference...
>>>
>>>     
>> Please take a look at the message logs (dmesg).
>> You can follow the instructions described here
>> http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
>> and report where it fails.
>>
>> I use tzap like this: tzap -c $HOME/.tzap/channels.conf -s -t 120 -r
>> -o output.mpg "SomeChannel"
>> I am able to play with mplayer too.
>> Regards,
>> Thierry
>>   
> Hi Thierry,
> 
> Thank you for the quick reply.
> I should have looked in dmesg before...
> Checking dmesg before I used tzap shows a problem. dvb-usb: recv bulk
> message failed: -110
> 
> **** Extract of dmesg ****
> 
> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
> state.
> dvb-usb: will pass the complete MPEG2 transport stream to the software
> demuxer.
> DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T
> Receiver)
> DVB: registering adapter 0 frontend 0 (TerraTec/qanu USB2.0 Highspeed
> DVB-T Receiver)...
> input: IR-receiver inside an USB DVB receiver as
> /devices/pci0000:00/0000:00:1a.7/usb1/1-1/input/input8
> dvb-usb: schedule remote query interval to 50 msecs.
> dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
> initialized and connected.
> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
> state.
> dvb-usb: will pass the complete MPEG2 transport stream to the software
> demuxer.
> DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T
> Receiver)
> DVB: registering adapter 1 frontend 0 (TerraTec/qanu USB2.0 Highspeed
> DVB-T Receiver)...
> input: IR-receiver inside an USB DVB receiver as
> /devices/pci0000:00/0000:00:1d.7/usb2/2-5/input/input9
> dvb-usb: schedule remote query interval to 50 msecs.
> dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
> initialized and connected.
> usbcore: registered new interface driver cinergyT2
> 
> dvb-usb: recv bulk message failed: -110
> dvb-usb: recv bulk message failed: -110
> 
> ****
> 
> Running tzap fails to tune/lock
> 
> #tzap -a 0 -c channels.conf_dvbt -s -t 120 -r -o output.mpg "BBC ONE"
> 
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> reading channels from file 'channels.conf_dvbt'
> tuning to 505833330 Hz
> video pid 0x0258, audio pid 0x0259
> status 01 | signal c11f | snr 0000 | ber ffffffff | unc ffffffff |
> 
> No more messages in dmesg.
> 
> I shut down the PC, removed all power, unplugged the CinergyT2s, gave it
> twenty seconds and powered back up.
> Once it had booted I plugged in one of the devices and the dmesg output
> below.
> 
> 
> usb 2-5: new high speed USB device using ehci_hcd and address 3
> usb 2-5: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid
> maxpacket 64
> usb 2-5: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has
> invalid maxpacket 64
> usb 2-5: configuration #1 chosen from 1 choice
> usb 2-5: New USB device found, idVendor=0ccd, idProduct=0038
> usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> usb 2-5: Product: Cinergy T?
> usb 2-5: Manufacturer: TerraTec GmbH
> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
> state.
> dvb-usb: will pass the complete MPEG2 transport stream to the software
> demuxer.
> DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T
> Receiver)
> DVB: registering adapter 1 frontend 0 (TerraTec/qanu USB2.0 Highspeed
> DVB-T Receiver)...
> input: IR-receiver inside an USB DVB receiver as
> /devices/pci0000:00/0000:00:1d.7/usb2/2-5/input/input9
> dvb-usb: schedule remote query interval to 50 msecs.
> dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
> initialized and connected.
> usbcore: registered new interface driver cinergyT2
> dvb-usb: recv bulk message failed: -110
> 
> Cannot tzap or scan.
> 
> With the old version of the driver I don't have any trouble at all.
> 
I do have this bulk message error too, sometimes (this is a timeout on recv).
I can tune channels but I think I have a particular version of the CinergyT2 (there are several).
You can turn on the debug infos:
modprobe dvb-core dvbdev_debug=1 debug=1
modprobe dvb-usb-cinergyT2 debug=7
and see again dmesg...

> Hope this helps.
> 
> Regards, Jason
Hope this helps too :)
Thierry

Re: CinergyT2 not working with newer alternative driver

[Jason Harvey]

Thierry Merle wrote:
> Jason Harvey wrote:
>   
>> Thierry Merle wrote:
>>     
>>> Hi Jason,
>>> Jason Harvey wrote:
>>>  
>>>       
>>>> I have been successfully using VDR with two CinergyT2s for 18 months.
>>>> After adding a Hauppage NOVA-S2-HD I updated my v4l-dvb drivers hoping
>>>> to get S2 capability and test a newer VDR for HD reception.
>>>>
>>>> The CinergyT2s stopped working. The kernel module loads, the blue leds
>>>> flash as expected but they don't lock on to a signal for long.
>>>> Signal strength shown in femon is erratic and a lock only rarely
>>>> achieved.
>>>>
>>>> I checked through the mercurial tree to see what had changed.
>>>> It looks like the following change is the one that stops the CinergyT2s
>>>> working on my system.
>>>> http://git.kernel.org/?p=linux/kernel/git/mchehab/devel.git;a=commit;h=986bd1e58b18c09b753f797df19251804bfe3e84
>>>>
>>>>
>>>>
>>>> I deleted the newer version of the module and replace it with the
>>>> previous deleted code.
>>>> Make'd and installed the old version works as expected.
>>>>
>>>> Machine they're plugged into is running Fedora 10,
>>>> 2.6.27.12-170.2.5.fc10.i686
>>>> I downloaded the current v4l-dvb today (31Jan2009) and tried it all
>>>> again before posting this message.
>>>>
>>>> Not sure where to look next, I did start to capture the USB traffic to
>>>> see if I could spot the difference...
>>>>
>>>>     
>>>>         
>>> Please take a look at the message logs (dmesg).
>>> You can follow the instructions described here
>>> http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
>>> and report where it fails.
>>>
>>> I use tzap like this: tzap -c $HOME/.tzap/channels.conf -s -t 120 -r
>>> -o output.mpg "SomeChannel"
>>> I am able to play with mplayer too.
>>> Regards,
>>> Thierry
>>>   
>>>       
>> Hi Thierry,
>>
>> Thank you for the quick reply.
>> I should have looked in dmesg before...
>> Checking dmesg before I used tzap shows a problem. dvb-usb: recv bulk
>> message failed: -110
>>
>> **** Extract of dmesg ****
>>
>> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
>> state.
>> dvb-usb: will pass the complete MPEG2 transport stream to the software
>> demuxer.
>> DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T
>> Receiver)
>> DVB: registering adapter 0 frontend 0 (TerraTec/qanu USB2.0 Highspeed
>> DVB-T Receiver)...
>> input: IR-receiver inside an USB DVB receiver as
>> /devices/pci0000:00/0000:00:1a.7/usb1/1-1/input/input8
>> dvb-usb: schedule remote query interval to 50 msecs.
>> dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
>> initialized and connected.
>> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
>> state.
>> dvb-usb: will pass the complete MPEG2 transport stream to the software
>> demuxer.
>> DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T
>> Receiver)
>> DVB: registering adapter 1 frontend 0 (TerraTec/qanu USB2.0 Highspeed
>> DVB-T Receiver)...
>> input: IR-receiver inside an USB DVB receiver as
>> /devices/pci0000:00/0000:00:1d.7/usb2/2-5/input/input9
>> dvb-usb: schedule remote query interval to 50 msecs.
>> dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
>> initialized and connected.
>> usbcore: registered new interface driver cinergyT2
>>
>> dvb-usb: recv bulk message failed: -110
>> dvb-usb: recv bulk message failed: -110
>>
>> ****
>>
>> Running tzap fails to tune/lock
>>
>> #tzap -a 0 -c channels.conf_dvbt -s -t 120 -r -o output.mpg "BBC ONE"
>>
>> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
>> reading channels from file 'channels.conf_dvbt'
>> tuning to 505833330 Hz
>> video pid 0x0258, audio pid 0x0259
>> status 01 | signal c11f | snr 0000 | ber ffffffff | unc ffffffff |
>>
>> No more messages in dmesg.
>>
>> I shut down the PC, removed all power, unplugged the CinergyT2s, gave it
>> twenty seconds and powered back up.
>> Once it had booted I plugged in one of the devices and the dmesg output
>> below.
>>
>>
>> usb 2-5: new high speed USB device using ehci_hcd and address 3
>> usb 2-5: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid
>> maxpacket 64
>> usb 2-5: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has
>> invalid maxpacket 64
>> usb 2-5: configuration #1 chosen from 1 choice
>> usb 2-5: New USB device found, idVendor=0ccd, idProduct=0038
>> usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
>> usb 2-5: Product: Cinergy T?
>> usb 2-5: Manufacturer: TerraTec GmbH
>> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
>> state.
>> dvb-usb: will pass the complete MPEG2 transport stream to the software
>> demuxer.
>> DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T
>> Receiver)
>> DVB: registering adapter 1 frontend 0 (TerraTec/qanu USB2.0 Highspeed
>> DVB-T Receiver)...
>> input: IR-receiver inside an USB DVB receiver as
>> /devices/pci0000:00/0000:00:1d.7/usb2/2-5/input/input9
>> dvb-usb: schedule remote query interval to 50 msecs.
>> dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
>> initialized and connected.
>> usbcore: registered new interface driver cinergyT2
>> dvb-usb: recv bulk message failed: -110
>>
>> Cannot tzap or scan.
>>
>> With the old version of the driver I don't have any trouble at all.
>>
>>     
> I do have this bulk message error too, sometimes (this is a timeout on recv).
> I can tune channels but I think I have a particular version of the CinergyT2 (there are several).
> You can turn on the debug infos:
> modprobe dvb-core dvbdev_debug=1 debug=1
> modprobe dvb-usb-cinergyT2 debug=7
> and see again dmesg...
>   

Dmesg on plugging in the device as follows :-

    usb 2-5: new high speed USB device using ehci_hcd and address 3
    usb 2-5: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has
    invalid maxpacket 64
    usb 2-5: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has
    invalid maxpacket 64
    usb 2-5: configuration #1 chosen from 1 choice
    usb 2-5: New USB device found, idVendor=0ccd, idProduct=0038
    usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    usb 2-5: Product: Cinergy T?
    usb 2-5: Manufacturer: TerraTec GmbH
    dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in
    warm state.
    dvb-usb: will pass the complete MPEG2 transport stream to the
    software demuxer.
    DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T
    Receiver)
    DVB: register adapter1/demux0 @ minor: 4 (0x04)
    DVB: register adapter1/dvr0 @ minor: 5 (0x05)
    DVB: register adapter1/net0 @ minor: 6 (0x06)
    DVB: registering adapter 1 frontend 0 (TerraTec/qanu USB2.0
    Highspeed DVB-T Receiver)...
    DVB: register adapter1/frontend0 @ minor: 7 (0x07)
    input: IR-receiver inside an USB DVB receiver as
    /devices/pci0000:00/0000:00:1d.7/usb2/2-5/input/input9
    dvb-usb: schedule remote query interval to 50 msecs.
    dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
    initialized and connected.
    usbcore: registered new interface driver cinergyT2


tzap -a 1 -c channels.conf_dvbt -s -t 120 -r -o output.mpg "BBC ONE"
only puts the following two lines into dmesg :-

function : dvb_dvr_open
cinergyt2_fe_sleep() Called

Not much there really!

Regards, Jason

Re: CinergyT2 not working with newer alternative driver

[Thierry Merle]

Jason Harvey wrote:
> Thierry Merle wrote:
>> Jason Harvey wrote:
>>  
>>> Thierry Merle wrote:
>>>    
>>>> Hi Jason,
>>>> Jason Harvey wrote:
>>>>  
>>>>      
>>>>> I have been successfully using VDR with two CinergyT2s for 18 months.
>>>>> After adding a Hauppage NOVA-S2-HD I updated my v4l-dvb drivers hoping
>>>>> to get S2 capability and test a newer VDR for HD reception.
>>>>>
>>>>> The CinergyT2s stopped working. The kernel module loads, the blue leds
>>>>> flash as expected but they don't lock on to a signal for long.
>>>>> Signal strength shown in femon is erratic and a lock only rarely
>>>>> achieved.
>>>>>
>>>>> I checked through the mercurial tree to see what had changed.
>>>>> It looks like the following change is the one that stops the
>>>>> CinergyT2s
>>>>> working on my system.
>>>>> http://git.kernel.org/?p=linux/kernel/git/mchehab/devel.git;a=commit;h=986bd1e58b18c09b753f797df19251804bfe3e84
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> I deleted the newer version of the module and replace it with the
>>>>> previous deleted code.
>>>>> Make'd and installed the old version works as expected.
>>>>>
>>>>> Machine they're plugged into is running Fedora 10,
>>>>> 2.6.27.12-170.2.5.fc10.i686
>>>>> I downloaded the current v4l-dvb today (31Jan2009) and tried it all
>>>>> again before posting this message.
>>>>>
>>>>> Not sure where to look next, I did start to capture the USB traffic to
>>>>> see if I could spot the difference...
>>>>>
>>>>>             
>>>> Please take a look at the message logs (dmesg).
>>>> You can follow the instructions described here
>>>> http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
>>>> and report where it fails.
>>>>
>>>> I use tzap like this: tzap -c $HOME/.tzap/channels.conf -s -t 120 -r
>>>> -o output.mpg "SomeChannel"
>>>> I am able to play with mplayer too.
>>>> Regards,
>>>> Thierry
>>>>         
>>> Hi Thierry,
>>>
>>> Thank you for the quick reply.
>>> I should have looked in dmesg before...
>>> Checking dmesg before I used tzap shows a problem. dvb-usb: recv bulk
>>> message failed: -110
>>>
>>> **** Extract of dmesg ****
>>>
>>> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
>>> state.
>>> dvb-usb: will pass the complete MPEG2 transport stream to the software
>>> demuxer.
>>> DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T
>>> Receiver)
>>> DVB: registering adapter 0 frontend 0 (TerraTec/qanu USB2.0 Highspeed
>>> DVB-T Receiver)...
>>> input: IR-receiver inside an USB DVB receiver as
>>> /devices/pci0000:00/0000:00:1a.7/usb1/1-1/input/input8
>>> dvb-usb: schedule remote query interval to 50 msecs.
>>> dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
>>> initialized and connected.
>>> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
>>> state.
>>> dvb-usb: will pass the complete MPEG2 transport stream to the software
>>> demuxer.
>>> DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T
>>> Receiver)
>>> DVB: registering adapter 1 frontend 0 (TerraTec/qanu USB2.0 Highspeed
>>> DVB-T Receiver)...
>>> input: IR-receiver inside an USB DVB receiver as
>>> /devices/pci0000:00/0000:00:1d.7/usb2/2-5/input/input9
>>> dvb-usb: schedule remote query interval to 50 msecs.
>>> dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
>>> initialized and connected.
>>> usbcore: registered new interface driver cinergyT2
>>>
>>> dvb-usb: recv bulk message failed: -110
>>> dvb-usb: recv bulk message failed: -110
>>>
>>> ****
>>>
>>> Running tzap fails to tune/lock
>>>
>>> #tzap -a 0 -c channels.conf_dvbt -s -t 120 -r -o output.mpg "BBC ONE"
>>>
>>> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
>>> reading channels from file 'channels.conf_dvbt'
>>> tuning to 505833330 Hz
>>> video pid 0x0258, audio pid 0x0259
>>> status 01 | signal c11f | snr 0000 | ber ffffffff | unc ffffffff |
>>>
>>> No more messages in dmesg.
>>>
>>> I shut down the PC, removed all power, unplugged the CinergyT2s, gave it
>>> twenty seconds and powered back up.
>>> Once it had booted I plugged in one of the devices and the dmesg output
>>> below.
>>>
>>>
>>> usb 2-5: new high speed USB device using ehci_hcd and address 3
>>> usb 2-5: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid
>>> maxpacket 64
>>> usb 2-5: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has
>>> invalid maxpacket 64
>>> usb 2-5: configuration #1 chosen from 1 choice
>>> usb 2-5: New USB device found, idVendor=0ccd, idProduct=0038
>>> usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
>>> usb 2-5: Product: Cinergy T?
>>> usb 2-5: Manufacturer: TerraTec GmbH
>>> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
>>> state.
>>> dvb-usb: will pass the complete MPEG2 transport stream to the software
>>> demuxer.
>>> DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T
>>> Receiver)
>>> DVB: registering adapter 1 frontend 0 (TerraTec/qanu USB2.0 Highspeed
>>> DVB-T Receiver)...
>>> input: IR-receiver inside an USB DVB receiver as
>>> /devices/pci0000:00/0000:00:1d.7/usb2/2-5/input/input9
>>> dvb-usb: schedule remote query interval to 50 msecs.
>>> dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
>>> initialized and connected.
>>> usbcore: registered new interface driver cinergyT2
>>> dvb-usb: recv bulk message failed: -110
>>>
>>> Cannot tzap or scan.
>>>
>>> With the old version of the driver I don't have any trouble at all.
>>>
>>>     
>> I do have this bulk message error too, sometimes (this is a timeout on
>> recv).
>> I can tune channels but I think I have a particular version of the
>> CinergyT2 (there are several).
>> You can turn on the debug infos:
>> modprobe dvb-core dvbdev_debug=1 debug=1
>> modprobe dvb-usb-cinergyT2 debug=7
>> and see again dmesg...
>>   
> 
> Dmesg on plugging in the device as follows :-
> 
>    usb 2-5: new high speed USB device using ehci_hcd and address 3
>    usb 2-5: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has
>    invalid maxpacket 64
>    usb 2-5: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has
>    invalid maxpacket 64
>    usb 2-5: configuration #1 chosen from 1 choice
>    usb 2-5: New USB device found, idVendor=0ccd, idProduct=0038
>    usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
>    usb 2-5: Product: Cinergy T?
>    usb 2-5: Manufacturer: TerraTec GmbH
>    dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in
>    warm state.
>    dvb-usb: will pass the complete MPEG2 transport stream to the
>    software demuxer.
>    DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T
>    Receiver)
>    DVB: register adapter1/demux0 @ minor: 4 (0x04)
>    DVB: register adapter1/dvr0 @ minor: 5 (0x05)
>    DVB: register adapter1/net0 @ minor: 6 (0x06)
>    DVB: registering adapter 1 frontend 0 (TerraTec/qanu USB2.0
>    Highspeed DVB-T Receiver)...
>    DVB: register adapter1/frontend0 @ minor: 7 (0x07)
>    input: IR-receiver inside an USB DVB receiver as
>    /devices/pci0000:00/0000:00:1d.7/usb2/2-5/input/input9
>    dvb-usb: schedule remote query interval to 50 msecs.
>    dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
>    initialized and connected.
>    usbcore: registered new interface driver cinergyT2
> 
> 
> tzap -a 1 -c channels.conf_dvbt -s -t 120 -r -o output.mpg "BBC ONE"
> only puts the following two lines into dmesg :-
> 
> function : dvb_dvr_open
> cinergyt2_fe_sleep() Called
> 
> Not much there really!
> 
> Regards, Jason
Another thing, do you know the firmware version of your tuner?
I have the 1.06 version.
Look at lsusb -vvv, this is the "bcdDevice" line for the CinergyT2 device.
Sorry but I have no idea of the origin of the problem.
If I had time I would compare USB dumps between the old driver and the new one for the same tuning operation.

Regards,
Thierry

Re: CinergyT2 not working with newer alternative driver

[Jason Harvey]

Thierry Merle wrote:
> Another thing, do you know the firmware version of your tuner?
> I have the 1.06 version.
>   
Both are running on firmware 1.08
Wonder if I can downgrade them... will look into that.
> Look at lsusb -vvv, this is the "bcdDevice" line for the CinergyT2 device.
> Sorry but I have no idea of the origin of the problem.
> If I had time I would compare USB dumps between the old driver and the new one for the same tuning operation.
>   
I'll try and get the USB dumps and a comparison done myself within the 
next week or two.
Think I have a spare PC around with an older Fedora on it with a kernel 
that worked.
I did see another posting to this mail list from someone with the same 
problem which I'll take as confirmation that it is not just me :)

Regards,
Jason

Re: CinergyT2 not working with newer alternative driver

[Thierry Merle]

Jason Harvey wrote:
> Thierry Merle wrote:
>> Another thing, do you know the firmware version of your tuner?
>> I have the 1.06 version.
>>   
> Both are running on firmware 1.08
> Wonder if I can downgrade them... will look into that.
Yes, and I will try to find time to upgrade mine.
>> Look at lsusb -vvv, this is the "bcdDevice" line for the CinergyT2
>> device.
>> Sorry but I have no idea of the origin of the problem.
>> If I had time I would compare USB dumps between the old driver and the
>> new one for the same tuning operation.
>>   
> I'll try and get the USB dumps and a comparison done myself within the
> next week or two.
OK thanks; I will be able to help you by doing some perl scripts.
> Think I have a spare PC around with an older Fedora on it with a kernel
> that worked.
> I did see another posting to this mail list from someone with the same
> problem which I'll take as confirmation that it is not just me :)
> 
Yes I know, but the user did not answer the last time so we committed the redesign and we expect to find another user with the problem :)
Regards,
Thierry