Skip to contentSkip to conversation

dvb-usb-cinergyT2

DISCUSSION Johannes Engel 2 participants 3 messages Feb 6, 2009 – Feb 11, 2009 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

Hello!

Switching to the new kernel 2.6.28 including the new driver for my Terratec Cinergy T² made the thing almost unusable.
Neither mplayer nor scan resp. w_scan is able to tune the card anymore, not even the led lights up anymore. Sometimes tzap manages to get out a proper signal, but not reliably.

The kernel logs says the following:

dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
deinitialized and disconnected.
usbcore: deregistering interface driver cinergyT2
usb 5-1: new high speed USB device using ehci_hcd and address 13
usb 5-1: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 usb 5-1: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 usb 5-1: configuration #1 chosen from 1 choice
usb 5-1: New USB device found, idVendor=0ccd, idProduct=0038
usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 5-1: Product: Cinergy T�
usb 5-1: 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 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:1d.7/usb5/5-1/input/input17
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

Do you need any further information? Please CC me, since I am not subscribed to the list.

Cheers, Johannes

#1 lore raw

Hello Johannes,

Quoted 27 lines · Johannes Engel

Hello!

Switching to the new kernel 2.6.28 including the new driver for my Terratec Cinergy T² made the thing almost unusable.
Neither mplayer nor scan resp. w_scan is able to tune the card anymore, not even the led lights up anymore. Sometimes tzap manages to get out a proper signal, but not reliably.

The kernel logs says the following:

dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully
deinitialized and disconnected.
usbcore: deregistering interface driver cinergyT2
usb 5-1: new high speed USB device using ehci_hcd and address 13
usb 5-1: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 usb 5-1: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 usb 5-1: configuration #1 chosen from 1 choice
usb 5-1: New USB device found, idVendor=0ccd, idProduct=0038
usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 5-1: Product: Cinergy T�
usb 5-1: 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 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:1d.7/usb5/5-1/input/input17
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

Quoted 2 lines

Do you need any further information? Please CC me, since I am not subscribed to the list.

another user has got the same problem, except that the led still lights up. Can you tell us what it the firmware version in your device?
You can see it by doing lsusb -vvv, for the Cinergy T2 entry this is the "bcdDevice" line. I have the 1.06 firmware version and it works.
Cheers,
Thierry

#2 lore raw
Quoted 7 lines · Thierry Merle

another user has got the same problem, except that the led still lights up. Can you tell us what it the firmware version in your device?
You can see it by doing lsusb -vvv, for the Cinergy T2 entry this is the "bcdDevice" line. I have the 1.06 firmware version and it works.
Cheers,
Thierry

Hi Thierry,

thanks for your message! I just tried again and miraculously enough it seems to work now. In the meantime I only did a kernel upgrade to 2.6.28.4. So maybe that was the trick. :)

Nonetheless I attach the lsusb output for further reference, my firmware version though seems to be the same as yours: 1.06.

Cheers, Johannes

Bus 005 Device 002: ID 0ccd:0038 TerraTec Electronic GmbH Cinergy T^2 DVB-T Receiver Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00

  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  idVendor           0x0ccd TerraTec Electronic GmbH
  idProduct          0x0038 Cinergy T^2 DVB-T Receiver
  bcdDevice            1.06
  iManufacturer           1 TerraTec GmbH
  iProduct                2 Cinergy T�
  iSerial                 0 
  bNumConfigurations      1

Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 476mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 0
iInterface 3 Highspeed Bulk Transfer
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00

  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol

bMaxPacketSize0 64
bNumConfigurations 1