public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Harvey <softdevice@jasonline.co.uk>
To: linux-media@vger.kernel.org
Cc: Thierry Merle <thierry.merle@free.fr>
Subject: Re: CinergyT2 not working with newer alternative driver
Date: Sun, 01 Feb 2009 12:49:53 +0000	[thread overview]
Message-ID: <49859A71.70701@jasonline.co.uk> (raw)
In-Reply-To: <49857A09.9020302@free.fr>

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

  reply	other threads:[~2009-02-01 12:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31 23:55 CinergyT2 not working with newer alternative driver Jason Harvey
2009-02-01 10:31 ` Thierry Merle
2009-02-01 12:49   ` Jason Harvey [this message]
2009-02-02  6:27     ` Thierry Merle
2009-02-02  6:50       ` Jason Harvey
2009-02-08 21:37         ` Thierry Merle
2009-02-09 18:12           ` Jason Harvey
2009-02-09 20:11             ` Thierry Merle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49859A71.70701@jasonline.co.uk \
    --to=softdevice@jasonline.co.uk \
    --cc=linux-media@vger.kernel.org \
    --cc=thierry.merle@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox