You are not logged in.

#1 2013-12-07 23:50:43

replabrobin
Member
Registered: 2010-05-06
Posts: 232

[SOLVED] ...... problem with pctv 290e usb devices

I have an up to date x64 system; when I upgraded to linux-3.12.3-1-x86_64.pkg.tar.xz this morning my pctv 290e usb devices stopped working.

I see this in my kernel log

Dec 07 18:33:35 bunyip kernel: media: Linux media interface: v0.10
Dec 07 18:33:35 bunyip systemd[1]: Found device Hitachi_HTS543216L9A300.
Dec 07 18:33:35 bunyip systemd[1]: Activating swap /dev/disk/by-uuid/6ea19458-0015-4b1f-b2f5-8f3dea92a88a...
Dec 07 18:33:35 bunyip kernel: Linux video capture interface: v2.00
Dec 07 18:33:35 bunyip kernel: ath: EEPROM regdomain: 0x65
Dec 07 18:33:35 bunyip kernel: ath: EEPROM indicates we should expect a direct regpair map
Dec 07 18:33:35 bunyip kernel: ath: Country alpha2 being used: 00
Dec 07 18:33:35 bunyip kernel: ath: Regpair used: 0x65
Dec 07 18:33:35 bunyip kernel: ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Dec 07 18:33:35 bunyip kernel: ath5k: phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
Dec 07 18:33:35 bunyip kernel: em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0)
Dec 07 18:33:35 bunyip kernel: em28xx: DVB interface 0 found: isoc
Dec 07 18:33:35 bunyip kernel: em28xx: chip ID is em28174
Dec 07 18:33:35 bunyip kernel: usbcore: registered new interface driver usbserial
Dec 07 18:33:35 bunyip kernel: usbcore: registered new interface driver usbserial_generic
Dec 07 18:33:35 bunyip kernel: usbserial: USB Serial support registered for generic
Dec 07 18:33:35 bunyip kernel: usbcore: registered new interface driver ftdi_sio
Dec 07 18:33:35 bunyip kernel: usbserial: USB Serial support registered for FTDI USB Serial Device
Dec 07 18:33:35 bunyip kernel: usb 2-4: Ignoring serial port reserved for JTAG
Dec 07 18:33:35 bunyip kernel: ftdi_sio 2-4:1.1: FTDI USB Serial Device converter detected
Dec 07 18:33:35 bunyip kernel: usb 2-4: Detected FT2232C
Dec 07 18:33:35 bunyip kernel: usb 2-4: Number of endpoints 2
Dec 07 18:33:35 bunyip kernel: usb 2-4: Endpoint 1 MaxPacketSize 64
Dec 07 18:33:35 bunyip kernel: usb 2-4: Endpoint 2 MaxPacketSize 64
Dec 07 18:33:35 bunyip kernel: usb 2-4: Setting MaxPacketSize 64
Dec 07 18:33:35 bunyip kernel: usb 2-4: FTDI USB Serial Device converter now attached to ttyUSB0
Dec 07 18:33:35 bunyip kernel: usb 2-4: Ignoring serial port reserved for JTAG
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 0000: 26 00 01 00 02 09 d8 85 80 80 e5 80 f4 f5 94 90
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 0010: 78 0d e4 f0 f5 46 12 00 5a c2 eb c2 e8 30 e9 03
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 0020: 12 09 de 30 eb 03 12 09 10 30 ec f1 12 07 72 80
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 0030: ec 00 60 00 e5 f5 64 01 60 09 e5 f5 64 09 60 03
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 0040: c2 c6 22 e5 f7 b4 03 13 e5 f6 b4 87 03 02 09 92
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 0050: e5 f6 b4 93 03 02 07 e6 c2 c6 22 c2 c6 22 12 09
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 0060: cf 02 06 19 1a eb 67 95 13 20 4f 02 c0 13 6b 10
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 0070: a0 1a ba 14 ce 1a 39 57 00 5c 18 00 00 00 00 00
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 0080: 00 00 00 00 44 36 00 00 f0 10 02 00 00 00 00 00
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 0090: 5b 23 c0 00 00 00 20 40 20 80 02 20 01 01 00 00
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 00b0: c6 40 00 00 00 00 a7 00 00 00 00 00 00 00 00 00
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 38 32
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 00d0: 34 31 30 31 31 36 36 30 31 37 31 31 33 35 31 32
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 00e0: 38 36 00 4f 53 49 30 30 33 30 38 44 30 31 31 30
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 00f0: 31 32 38 36 00 00 00 00 00 00 00 00 00 00 31 30
Dec 07 18:33:35 bunyip kernel: em28174 #0: i2c eeprom 0100: ... (skipped)
Dec 07 18:33:35 bunyip kernel: em28174 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x9de637c6
Dec 07 18:33:35 bunyip kernel: em28174 #0: EEPROM info:
Dec 07 18:33:35 bunyip kernel: em28174 #0:         microcode start address = 0x0004, boot configuration = 0x01
Dec 07 18:33:35 bunyip kernel: em28174 #0:         No audio on board.
Dec 07 18:33:35 bunyip kernel: em28174 #0:         500mA max power
Dec 07 18:33:35 bunyip kernel: em28174 #0:         Table at offset 0x39, strings=0x1aa0, 0x14ba, 0x1ace
Dec 07 18:33:35 bunyip kernel: em28174 #0: Identified as PCTV nanoStick T2 290e (card=78)
Dec 07 18:33:35 bunyip kernel: em28174 #0: v4l2 driver version 0.2.0
Dec 07 18:33:35 bunyip kernel: em28174 #0: V4L2 video device registered as video0
Dec 07 18:33:35 bunyip kernel: em28174 #0: dvb set to isoc mode.
Dec 07 18:33:35 bunyip kernel: em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0)
Dec 07 18:33:35 bunyip kernel: em28xx: DVB interface 0 found: isoc
Dec 07 18:33:35 bunyip kernel: em28xx: chip ID is em28174
Dec 07 18:33:35 bunyip kernel: input: HDA NVidia HDMI/DP,pcm=3 Phantom as /devices/pci0000:00/0000:00:08.0/sound/card0/input9
Dec 07 18:33:35 bunyip kernel: input: HDA NVidia Headphone as /devices/pci0000:00/0000:00:08.0/sound/card0/input8
Dec 07 18:33:35 bunyip kernel: input: HDA NVidia Mic as /devices/pci0000:00/0000:00:08.0/sound/card0/input7
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 0000: 26 00 01 00 02 09 d8 85 80 80 e5 80 f4 f5 94 90
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 0010: 78 0d e4 f0 f5 46 12 00 5a c2 eb c2 e8 30 e9 03
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 0020: 12 09 de 30 eb 03 12 09 10 30 ec f1 12 07 72 80
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 0030: ec 00 60 00 e5 f5 64 01 60 09 e5 f5 64 09 60 03
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 0040: c2 c6 22 e5 f7 b4 03 13 e5 f6 b4 87 03 02 09 92
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 0050: e5 f6 b4 93 03 02 07 e6 c2 c6 22 c2 c6 22 12 09
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 0060: cf 02 06 19 1a eb 67 95 13 20 4f 02 c0 13 6b 10
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 0070: a0 1a ba 14 ce 1a 39 57 00 5c 18 00 00 00 00 00
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 0080: 00 00 00 00 44 36 00 00 f0 10 02 00 00 00 00 00
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 0090: 5b 23 c0 00 00 00 20 40 20 80 02 20 01 01 00 00
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 00b0: c6 40 00 00 00 00 a7 00 00 00 00 00 00 00 00 00
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 38 32
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 00d0: 34 31 30 31 31 36 36 30 31 37 31 32 34 37 56 30
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 00e0: 4d 39 00 4f 53 49 30 30 33 30 38 44 30 31 31 30
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 00f0: 56 30 4d 39 00 00 00 00 00 00 00 00 00 00 31 30
Dec 07 18:33:35 bunyip kernel: em28174 #1: i2c eeprom 0100: ... (skipped)
Dec 07 18:33:35 bunyip kernel: em28174 #1: EEPROM ID = 26 00 01 00, EEPROM hash = 0x924125c8
Dec 07 18:33:35 bunyip kernel: em28174 #1: EEPROM info:
Dec 07 18:33:35 bunyip kernel: em28174 #1:         microcode start address = 0x0004, boot configuration = 0x01
Dec 07 18:33:35 bunyip kernel: em28174 #1:         No audio on board.
Dec 07 18:33:35 bunyip kernel: em28174 #1:         500mA max power
Dec 07 18:33:35 bunyip kernel: em28174 #1:         Table at offset 0x39, strings=0x1aa0, 0x14ba, 0x1ace
Dec 07 18:33:35 bunyip kernel: em28174 #1: Identified as PCTV nanoStick T2 290e (card=78)
Dec 07 18:33:35 bunyip kernel: em28174 #1: v4l2 driver version 0.2.0
Dec 07 18:33:35 bunyip kernel: em28174 #1: V4L2 video device registered as video1
Dec 07 18:33:35 bunyip kernel: em28174 #1: dvb set to isoc mode.
Dec 07 18:33:35 bunyip kernel: usbcore: registered new interface driver em28xx
Dec 07 18:33:35 bunyip kernel: tda18271 3-0060: creating new instance
Dec 07 18:33:35 bunyip kernel: tda18271_read_regs: [3-0060|M] ERROR: i2c_transfer returned: -19
Dec 07 18:33:35 bunyip kernel: Error reading device ID @ 3-0060, bailing out.
Dec 07 18:33:35 bunyip kernel: tda18271_attach: [3-0060|M] error -5 on line 1285
Dec 07 18:33:35 bunyip kernel: tda18271 3-0060: destroying instance
Dec 07 18:33:35 bunyip systemd[1]: Activated swap /dev/disk/by-uuid/6ea19458-0015-4b1f-b2f5-8f3dea92a88a.
Dec 07 18:33:35 bunyip systemd[1]: Starting Swap.
Dec 07 18:33:35 bunyip systemd[1]: Reached target Swap.
Dec 07 18:33:35 bunyip systemd[1]: Starting System Initialization.
Dec 07 18:33:35 bunyip kernel: tda18271 5-0060: creating new instance
Dec 07 18:33:35 bunyip kernel: tda18271_read_regs: [5-0060|M] ERROR: i2c_transfer returned: -19
Dec 07 18:33:35 bunyip kernel: Error reading device ID @ 5-0060, bailing out.
Dec 07 18:33:35 bunyip kernel: tda18271_attach: [5-0060|M] error -5 on line 1285
Dec 07 18:33:35 bunyip kernel: tda18271 5-0060: destroying instance
Dec 07 18:33:35 bunyip kernel: Em28xx: Initialized (Em28xx dvb Extension) extension
Dec 07 18:33:35 bunyip kernel: Registered IR keymap rc-pinnacle-pctv-hd
Dec 07 18:33:35 bunyip kernel: input: em28xx IR (em28174 #0) as /devices/pci0000:00/0000:00:04.1/usb1/1-3/1-3.1/rc/rc0/input10
Dec 07 18:33:35 bunyip kernel: rc0: em28xx IR (em28174 #0) as /devices/pci0000:00/0000:00:04.1/usb1/1-3/1-3.1/rc/rc0
Dec 07 18:33:35 bunyip kernel: Registered IR keymap rc-pinnacle-pctv-hd
Dec 07 18:33:35 bunyip kernel: input: em28xx IR (em28174 #1) as /devices/pci0000:00/0000:00:04.1/usb1/1-3/1-3.2/rc/rc1/input11
Dec 07 18:33:35 bunyip kernel: rc1: em28xx IR (em28174 #1) as /devices/pci0000:00/0000:00:04.1/usb1/1-3/1-3.2/rc/rc1
Dec 07 18:33:35 bunyip kernel: Em28xx: Initialized (Em28xx Input Extension) extension

downgrading to linux-3.12.2-1-x86_64.pkg.tar.xz and nvidia-331.20-1-x86_64.pkg.tar.xz fixed the issue.

Edit: I tried updating to 3.12.4-1, but that still has the problem.
Edt: linux 3.12.6-1 fixes the issue for me.

Last edited by replabrobin (2013-12-26 14:09:00)

Offline

#2 2013-12-10 22:28:46

Gosi
Member
From: Vienna, Austria
Registered: 2010-02-25
Posts: 100

Re: [SOLVED] ...... problem with pctv 290e usb devices

Confirmed.

Sorry that I have no solution, but I have the same device and the exact same issue.

Disconnect - connect does not help.

tda18271_read_regs: [10-0060|M] ERROR: i2c_transfer returned: -19

Error -19 means ENODEV,but there is no indication that there was a problem creating a device (/dev/videoX is there).

Offline

#3 2013-12-10 22:32:44

tghe-retford
Member
From: Retford, United Kingdom
Registered: 2011-12-08
Posts: 23

Re: [SOLVED] ...... problem with pctv 290e usb devices

I can't help much other than to say me too. My PCTV 290e USB stick has also stopped working with the latest LInux package. Have you sent a bug report?

I note DVB-S2 support was added to the em28xx module within Linux six days ago by Antti Palosaari - has that broken something with DVB-T(2)? If so, might be worth letting the Linux developers know.

Offline

#4 2013-12-11 14:42:18

replabrobin
Member
Registered: 2010-05-06
Posts: 232

Re: [SOLVED] ...... problem with pctv 290e usb devices

I have just reported this issue to the linux-media@vger.kernel.org list.

Offline

#5 2013-12-12 08:54:10

replabrobin
Member
Registered: 2010-05-06
Posts: 232

Re: [SOLVED] ...... problem with pctv 290e usb devices

tghe-retford, I think the code in 3.12.3-1 comes from November so the S2 support is probably not relevant. I looked at the changes between the two kernels and there was some reference to the tda modules,specifically  drivers/media/dvb-frontends/tda18271dd.c that looks relevant to the i2c stuff. So perhaps that's the change that broke the 290e.

Offline

#6 2013-12-14 13:48:57

replabrobin
Member
Registered: 2010-05-06
Posts: 232

Re: [SOLVED] ...... problem with pctv 290e usb devices

I have applied a patch http://git.kernel.org/cgit/linux/kernel … 4afc0cc1d4 recommended by Mauro Carvalho Chehab on the linux-media@vger.kernel.org list to the latest Arch 3.12.4-1 kernel and built the result with makepkg. I'm happy to say that the error is gone and my pctv 290e devices work again.

Offline

#7 2013-12-14 14:14:21

Thaodan
Member
From: Dortmund, Nordrein-Westfalen
Registered: 2012-04-28
Posts: 448

Re: [SOLVED] ...... problem with pctv 290e usb devices

would you like to open a task about this in fs?


Linux odin 3.13.1-pf #1 SMP PREEMPT Wed Mar 5 21:47:28 CET 2014 x86_64 GNU/Linux

Offline

#8 2013-12-14 14:46:01

replabrobin
Member
Registered: 2010-05-06
Posts: 232

Re: [SOLVED] ...... problem with pctv 290e usb devices

Thaodan wrote:

would you like to open a task about this in fs?

Thaodan, I am probably really stupid, but I don't understand that at all. What is fs and what are tasks in fs? From fs I only get File System which doesn't seem right.

Offline

#9 2013-12-14 14:58:12

replabrobin
Member
Registered: 2010-05-06
Posts: 232

Re: [SOLVED] ...... problem with pctv 290e usb devices

replabrobin wrote:

Thaodan, I am probably really stupid,.....

duh sad It seems FS is the prefix of a bug report in the Arch bug reporting system. So what kind of task is appropriate here. I assume the patch is in the kernel git repo somewhere and presumably will make its way out eventually. Looking at the linux PKGBUILD I don't seem to see specific patches for fixes etc so I think it unlikely that the cored maintainers would want to add a small patch to fix one driver.

Offline

#10 2013-12-18 13:34:54

geekinthesticks
Member
From: England
Registered: 2011-09-21
Posts: 143
Website

Re: [SOLVED] ...... problem with pctv 290e usb devices

I am thinking of buying one of these cards. Does anyone know if the patch has made it into 3.12.5-1-ARCH, which is my current kernel?

Offline

#11 2013-12-23 11:37:29

cleanrock
Member
Registered: 2008-11-17
Posts: 109

Re: [SOLVED] ...... problem with pctv 290e usb devices

I am pretty sure this is fixed now in 3.12.6 and 3.10.25 since they contain the patch/changes that replabrobin mentioned above.

Offline

#12 2013-12-23 11:49:52

geekinthesticks
Member
From: England
Registered: 2011-09-21
Posts: 143
Website

Re: [SOLVED] ...... problem with pctv 290e usb devices

OK thanks for the information. I don't want to maintain my own patched kernel if I can avoid it.

Offline

#13 2013-12-26 14:06:58

replabrobin
Member
Registered: 2010-05-06
Posts: 232

Re: [SOLVED] ...... problem with pctv 290e usb devices

geekinthesticks wrote:

OK thanks for the information. I don't want to maintain my own patched kernel if I can avoid it.

I can confirm that 3.12.6-1 solves this problem; my pctv 290e devices work again without patching.

Offline

Board footer

Powered by FluxBB