em28xx in v4l-dvb destroyed my USB TV card

em28xx in v4l-dvb destroyed my USB TV card

[Marius Bjørnstad]

[-- Attachment #1.1: Type: text/plain, Size: 2415 bytes --]

Hi all,

A problem with the em28xx driver was brought up in June by Thorsten
Hirsch: http://www.spinics.net/lists/linux-media/msg20588.html . I also
have a "TerraTec Cinergy Hybrid T USB XS". When I used my device with
Linux, it would take a long time to be recognised by the OS, and this
would get worse. At this point, the device is not recognised, and almost
completely dead.

When I plug it in, I get errors like
---------------------------------------------
Oct 17 14:34:55 muon kernel: [ 7111.324875] hub 1-1:1.0: unable to
enumerate USB device on port 2
Oct 17 14:34:55 muon kernel: [ 7111.580618] hub 1-1:1.0: unable to
enumerate USB device on port 2
Oct 17 14:34:55 muon kernel: [ 7111.840481] hub 1-1:1.0: unable to
enumerate USB device on port 2
Oct 17 14:34:55 muon kernel: [ 7112.092358] hub 1-1:1.0: unable to
enumerate USB device on port 2
----------------------------------------------
and these keep coming until the device is removed. The device is also
not available in windows.

I have attached an excerpt from /var/log/messages , when the device was
connected, before it was destroyed. Here is some more contextual info:

uname -a:
Linux muon 2.6.32-24-generic #41-Ubuntu SMP Thu Aug 19 01:38:40 UTC 2010
x86_64 GNU/Linux

Driver: v4l-dvb. The install process from linuxtv.org leaves me
oblivious of the version number, but I used the most recent version as
of a few weeks ago.

Firmware: I have "linux-firmware-nonfree" from Ubuntu installed, but I
don't know if v4l-dvb replaces the firmware file.


I have a different version of the stick than what was mentioned in the
above link: USB ID 0ccd:005e. In the post at
http://ubuntuforums.org/showpost.php?p=7832485&postcount=3 , it is
stated that this version requires a different firmware: . In my kernel
log it says that
xc3028-v27.fw is loaded, I think this could be the problem.

I was hoping someone could provide insight, or an explanation, and maybe
(but not likely) a way to resurrect my device. I hope that someone could
either 1) refute this problem with their own anecdotal evidence, or 2)
actually remove support for 0ccd:005e from the driver, to prevent this
from happening to anyone else.

I know this is a bit off topic, but if anyone could recommend a cheap
replacement DVB-C card for a laptop, that definitely works with Linux,
that would be great.

Many thanks,
Marius

[-- Attachment #1.2: terratec.txt --]
[-- Type: text/plain, Size: 8272 bytes --]

Oct 10 12:14:07 muon kernel: [  243.458871] usb 1-1.2: new high speed USB device using ehci_hcd and address 10
Oct 10 12:14:07 muon kernel: [  243.592097] usb 1-1.2: configuration #1 chosen from 1 choice
Oct 10 12:14:07 muon kernel: [  243.665278] IR NEC protocol handler initialized
Oct 10 12:14:07 muon kernel: [  243.672512] IR RC5(x) protocol handler initialized
Oct 10 12:14:07 muon kernel: [  243.675282] IR RC6 protocol handler initialized
Oct 10 12:14:07 muon kernel: [  243.694576] em28xx: New device TerraTec Electronic GmbH Cinergy Hybrid T USB XS (2882) @ 480 Mbps (0ccd:005e, interface 0, class 0)
Oct 10 12:14:07 muon kernel: [  243.694680] em28xx #0: chip ID is em2882/em2883
Oct 10 12:14:07 muon kernel: [  243.695521] IR JVC protocol handler initialized
Oct 10 12:14:07 muon kernel: [  243.698768] IR Sony protocol handler initialized
Oct 10 12:14:07 muon kernel: [  243.898418] em28xx #0: i2c eeprom 00: 1a eb 67 95 cd 0c 5e 00 d0 12 5c 03 9e 40 de 1c
Oct 10 12:14:07 muon kernel: [  243.898430] em28xx #0: i2c eeprom 10: 6a 34 27 57 46 07 01 00 00 00 00 00 00 00 00 00
Oct 10 12:14:07 muon kernel: [  243.898441] em28xx #0: i2c eeprom 20: 46 00 01 00 f0 10 31 00 b8 00 14 00 5b 1e 00 00
Oct 10 12:14:07 muon kernel: [  243.898451] em28xx #0: i2c eeprom 30: 00 00 20 40 20 6e 02 20 10 01 00 00 00 00 00 00
Oct 10 12:14:07 muon kernel: [  243.898461] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Oct 10 12:14:07 muon kernel: [  243.898470] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Oct 10 12:14:07 muon kernel: [  243.898480] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 34 03 54 00 65 00
Oct 10 12:14:07 muon kernel: [  243.898490] em28xx #0: i2c eeprom 70: 72 00 72 00 61 00 54 00 65 00 63 00 20 00 45 00
Oct 10 12:14:07 muon kernel: [  243.898500] em28xx #0: i2c eeprom 80: 6c 00 65 00 63 00 74 00 72 00 6f 00 6e 00 69 00
Oct 10 12:14:07 muon kernel: [  243.898510] em28xx #0: i2c eeprom 90: 63 00 20 00 47 00 6d 00 62 00 48 00 00 00 40 03
Oct 10 12:14:07 muon kernel: [  243.898520] em28xx #0: i2c eeprom a0: 43 00 69 00 6e 00 65 00 72 00 67 00 79 00 20 00
Oct 10 12:14:07 muon kernel: [  243.898530] em28xx #0: i2c eeprom b0: 48 00 79 00 62 00 72 00 69 00 64 00 20 00 54 00
Oct 10 12:14:07 muon kernel: [  243.898539] em28xx #0: i2c eeprom c0: 20 00 55 00 53 00 42 00 20 00 58 00 53 00 20 00
Oct 10 12:14:07 muon kernel: [  243.898549] em28xx #0: i2c eeprom d0: 28 00 32 00 38 00 38 00 32 00 29 00 00 00 1c 03
Oct 10 12:14:07 muon kernel: [  243.898559] em28xx #0: i2c eeprom e0: 30 00 36 00 31 00 31 00 30 00 32 00 30 00 30 00
Oct 10 12:14:07 muon kernel: [  243.898569] em28xx #0: i2c eeprom f0: 33 00 34 00 35 00 34 00 00 00 00 00 00 00 00 00
Oct 10 12:14:07 muon kernel: [  243.898580] em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0x3513bdbe
Oct 10 12:14:07 muon kernel: [  243.898583] em28xx #0: EEPROM info:
Oct 10 12:14:07 muon kernel: [  243.898585] em28xx #0:	AC97 audio (5 sample rates)
Oct 10 12:14:07 muon kernel: [  243.898586] em28xx #0:	500mA max power
Oct 10 12:14:07 muon kernel: [  243.898589] em28xx #0:	Table at 0x27, strings=0x409e, 0x1cde, 0x346a
Oct 10 12:14:07 muon kernel: [  243.899748] em28xx #0: Identified as Terratec Hybrid XS (em2882) (card=55)
Oct 10 12:14:07 muon kernel: [  243.904977] tvp5150 8-005c: chip found @ 0xb8 (em28xx #0)
Oct 10 12:14:07 muon kernel: [  243.914266] tuner 8-0061: chip found @ 0xc2 (em28xx #0)
Oct 10 12:14:07 muon kernel: [  243.938302] xc2028 8-0061: creating new instance
Oct 10 12:14:07 muon kernel: [  243.938307] xc2028 8-0061: type set to XCeive xc2028/xc3028 tuner
Oct 10 12:14:07 muon kernel: [  243.938318] usb 1-1.2: firmware: requesting xc3028-v27.fw
Oct 10 12:14:07 muon kernel: [  243.973963] xc2028 8-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7
Oct 10 12:14:08 muon kernel: [  244.031263] xc2028 8-0061: Loading firmware for type=BASE MTS (5), id 0000000000000000.
Oct 10 12:14:09 muon kernel: [  245.076321] xc2028 8-0061: Loading firmware for type=MTS (4), id 000000000000b700.
Oct 10 12:14:09 muon kernel: [  245.093165] xc2028 8-0061: Loading SCODE for type=MTS LCD NOGD MONO IF SCODE HAS_IF_4500 (6002b004), id 000000000000b700.
Oct 10 12:14:09 muon kernel: [  245.284941] Registered IR keymap rc-terratec-cinergy-xs
Oct 10 12:14:09 muon kernel: [  245.285059] input: em28xx IR (em28xx #0) as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/rc/rc0/input16
Oct 10 12:14:09 muon kernel: [  245.285167] rc0: em28xx IR (em28xx #0) as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/rc/rc0
Oct 10 12:14:09 muon kernel: [  245.285627] em28xx #0: Config register raw data: 0xd0
Oct 10 12:14:09 muon kernel: [  245.286368] em28xx #0: AC97 vendor ID = 0xffffffff
Oct 10 12:14:09 muon kernel: [  245.286744] em28xx #0: AC97 features = 0x6a90
Oct 10 12:14:09 muon kernel: [  245.286747] em28xx #0: Empia 202 AC97 audio processor detected
Oct 10 12:14:09 muon kernel: [  245.485014] tvp5150 8-005c: tvp5150am1 detected.
Oct 10 12:14:09 muon kernel: [  245.585465] em28xx #0: v4l2 driver version 0.1.2
Oct 10 12:14:09 muon kernel: [  245.691471] em28xx #0: V4L2 video device registered as video1
Oct 10 12:14:09 muon kernel: [  245.691476] em28xx #0: V4L2 VBI device registered as vbi0
Oct 10 12:14:09 muon kernel: [  245.692108] usbcore: registered new interface driver em28xx
Oct 10 12:14:09 muon kernel: [  245.692468] em28xx driver loaded
Oct 10 12:14:09 muon kernel: [  245.707723] em28xx_alsa: disagrees about version of symbol snd_pcm_new
Oct 10 12:14:09 muon kernel: [  245.707728] em28xx_alsa: Unknown symbol snd_pcm_new
Oct 10 12:14:09 muon kernel: [  245.707898] em28xx_alsa: disagrees about version of symbol snd_card_register
Oct 10 12:14:09 muon kernel: [  245.707902] em28xx_alsa: Unknown symbol snd_card_register
Oct 10 12:14:09 muon kernel: [  245.708059] em28xx_alsa: disagrees about version of symbol snd_card_free
Oct 10 12:14:09 muon kernel: [  245.708062] em28xx_alsa: Unknown symbol snd_card_free
Oct 10 12:14:09 muon kernel: [  245.708356] em28xx_alsa: disagrees about version of symbol snd_pcm_lib_ioctl
Oct 10 12:14:09 muon kernel: [  245.708359] em28xx_alsa: Unknown symbol snd_pcm_lib_ioctl
Oct 10 12:14:09 muon kernel: [  245.708757] em28xx_alsa: disagrees about version of symbol snd_pcm_set_ops
Oct 10 12:14:09 muon kernel: [  245.708760] em28xx_alsa: Unknown symbol snd_pcm_set_ops
Oct 10 12:14:09 muon kernel: [  245.709064] em28xx_alsa: disagrees about version of symbol snd_pcm_hw_constraint_integer
Oct 10 12:14:09 muon kernel: [  245.709068] em28xx_alsa: Unknown symbol snd_pcm_hw_constraint_integer
Oct 10 12:14:09 muon kernel: [  245.709632] em28xx_alsa: disagrees about version of symbol snd_card_create
Oct 10 12:14:09 muon kernel: [  245.709635] em28xx_alsa: Unknown symbol snd_card_create
Oct 10 12:14:09 muon kernel: [  245.709783] em28xx_alsa: disagrees about version of symbol snd_pcm_period_elapsed
Oct 10 12:14:09 muon kernel: [  245.709786] em28xx_alsa: Unknown symbol snd_pcm_period_elapsed
Oct 10 12:14:09 muon kernel: [  245.838092] tvp5150 8-005c: tvp5150am1 detected.
Oct 10 12:14:10 muon kernel: [  246.040731] xc2028 8-0061: attaching existing instance
Oct 10 12:14:10 muon kernel: [  246.040734] xc2028 8-0061: type set to XCeive xc2028/xc3028 tuner
Oct 10 12:14:10 muon kernel: [  246.040735] em28xx #0: em28xx #0/2: xc3028 attached
Oct 10 12:14:10 muon kernel: [  246.040738] DVB: registering new adapter (em28xx #0)
Oct 10 12:14:10 muon kernel: [  246.040740] DVB: registering adapter 0 frontend 0 (Zarlink ZL10353 DVB-T)...
Oct 10 12:14:10 muon kernel: [  246.040987] em28xx #0: Successfully loaded em28xx-dvb
Oct 10 12:14:10 muon kernel: [  246.040992] Em28xx: Initialized (Em28xx dvb Extension) extension
Oct 10 12:14:40 muon kernel: [  276.174469] xc2028 8-0061: Loading firmware for type=BASE F8MHZ MTS (7), id 0000000000000000.
Oct 10 12:14:41 muon kernel: [  277.233983] xc2028 8-0061: Loading firmware for type=D2633 DTV7 (90), id 0000000000000000.
Oct 10 12:14:41 muon kernel: [  277.247977] xc2028 8-0061: Loading SCODE for type=DTV6 QAM DTV7 DTV78 DTV8 ZARLINK456 SCODE HAS_IF_4760 (620003e0), id 0000000000000000.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: em28xx in v4l-dvb destroyed my USB TV card

[Németh Márton]

Hi,
Marius Bjørnstad wrote:
> A problem with the em28xx driver was brought up in June by Thorsten
> Hirsch: http://www.spinics.net/lists/linux-media/msg20588.html . I also
> have a "TerraTec Cinergy Hybrid T USB XS". When I used my device with
> Linux, it would take a long time to be recognised by the OS, and this
> would get worse. At this point, the device is not recognised, and almost
> completely dead.
> 
> When I plug it in, I get errors like
> ---------------------------------------------
> Oct 17 14:34:55 muon kernel: [ 7111.324875] hub 1-1:1.0: unable to
> enumerate USB device on port 2
> Oct 17 14:34:55 muon kernel: [ 7111.580618] hub 1-1:1.0: unable to
> enumerate USB device on port 2
> Oct 17 14:34:55 muon kernel: [ 7111.840481] hub 1-1:1.0: unable to
> enumerate USB device on port 2
> Oct 17 14:34:55 muon kernel: [ 7112.092358] hub 1-1:1.0: unable to
> enumerate USB device on port 2
> ----------------------------------------------
> and these keep coming until the device is removed. The device is also
> not available in windows.

The "unable to enumerate USB device on port ..." error message usually means that
the USB hardware what you connect itself is damaged. At that time the v4l-dvb driver
is not yet started, only the low level USB enumeration is running. It is also possible
that the USB cable causes the problem, if any. I had an USB device which had wrong
soldering and that one gave the same error message. That device was degraded as time
passed.

You might want to try the device on different USB port, different USB cable, or even
on different computer to see exactly which hardware component is not working properly.

	Márton Németh