[shoutbox]

Howdy!
I wonder if anybody is able to help!

I had this stick working flawlessly for ages, then something happened. Not one single linux distro or backend software is able to show the dvb-c input

It so happens that neither the drivers that come with kernel nor v4ldvb drivers are able to show this "multi standard" adapter right.
I use to have frontend 0/1 under /dev/dvb/adapter0 and those frontends were available.

My last resort, tvheadend, that was working just 2 weeks ago stopped co-operation with me after the update. Mythtv alike. vdr is too complicated for me to install, since I'm always unlucky with vdr/plugin/xbmc/plugin versions and I always get a mismatch.

I've tried different distros/kernel-versions/backend solutions . What happened? Is it possible that someone programmed a feature out of the software?

Thanks for comments and thoughts about this./shoutbox

[Prof Yaffle]

stopped co-operation with me after the update

Update of what? Certain kernel versions seem to break this stick, so is that a common pattern with what you've tried? What about OpenElec or Ubuntu 12.04 LTS, which use newer and older kernels than most distributions respectively?

https://bugzilla.kernel.org/show_bug.cgi?id=66861

What does uname -a say?

What does dmesg say about the stick as it loads?

[shoutbox]

Thanks many for the effort Prof!

I do run this backend in a virtualized environment. Kernels have been from 3.2-3.13.
I've trien yaVDR, MythBuntu and also OpenELEC.

At the moment I try to dig deeper, trying somthing new: rebooting the host/unplugging nanostick/ trying v4l-dvb drivers equipped with full kernel-source, not just headers. yaVDR0.50A...

uname -a:
Linux pvr64 3.2.0-59-generic #90-Ubuntu SMP Tue Jan 7 22:43:51 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

dmesg
[ 373.148542] DVB: registering adapter 0 frontend 0 (Sony CXD2820R (DVB-T/T2))...
[ 373.148759] DVB: registering adapter 0 frontend 1 (Sony CXD2820R (DVB-C))...
[ 373.149504] em28xx #0: Successfully loaded em28xx-dvb

Looks like bingo with this 3.2 kernel+ v4l-dvb drivers/firmware. will be doing some w_scanning...

Will be reporting soon! But since this is under tvheadend this kind of turned into off-topic.

[Prof Yaffle]

It does suggest that it's a kernel/firmware/driver problem than anything tvheadend-specific, doesn't it...

See how you get on and post your findings back here for posterity. If nothing else, someone might stumble in here one day with a similar problem!

(And I didn't know that the 290e had a DVB-C frontend... mine hasn't... or, at least, not one that's ever been enabled... but I don't have cable anyway, so I'm not missing anything of use to me).

[shoutbox]

https://bugzilla.kernel.org/show_bug.cgi?id=66861

...With 3.10.22-1, and with 3.10.23-1, dmesg has /NOT/ reported "em28174 #0: Successfully loaded em28xx-dvb," an adapter has not been created, and no TV reception has been possible...

at the moment this pet-beef of mine will get the form of gentoo and some more control over what is going on.

This road means overalys in portage emerges and multi-kernel-compile efforts

I will get there sooner or later. If one of you is allready there then why not share?

[negge]

I learned long ago that the number one rule when it comes to custom kernel modules is to never update your kernel unless you prepare for a battle.

[shoutbox]

yes, Kernel 3.2 LTS, Ubuntu 12.04.1 all updated off

basically one line of apt-get and it's all done just tune in and up!

thanks tvheadend for software that understands me and my stick

[shoutbox]

I would ask one more guestion:

How will I make tvheadend persistent so that it can recover from reboot?

This is no problem since uptimes have been weeks, but I wouldn't mind having it all tuned up on boot.

/shoutbox

[Prof Yaffle]

If you've installed from .deb, it should auto-start as an upstart job on 'buntu systems. Your only challenge is that USB tuners can move about, so you need to play with /etc/modprobe.d/options-dvb.conf or udev to force it to load into a particular place - particularly a problem with multiple tuners.

http://www.mythtv.org/wiki/Device_Filenames_and_udev

[tvjon]

...If nothing else, someone might stumble in here one day with a similar problem!

(And I didn't know that the 290e had a DVB-C frontend... mine hasn't... or, at least, not one that's ever been enabled... but I don't have cable anyway, so I'm not missing anything of use to me).

Hello. I've stumbled in as I still haven't found a fix. I reported the demodulator problem on Github several weeks ago, but specifically wrt Raspberry-Pi, as that's my main goal for the 290e.

Here's my dmesg:

[ 3910.121078] em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0)
[ 3910.121110] em28xx: DVB interface 0 found: isoc
[ 3910.121498] em28xx: chip ID is em28174
[ 3910.469350] em28174 #0: i2c eeprom 0000: 26 00 01 00 02 09 d8 85 80 80 e5 80 f4 f5 94 90
[ 3910.469411] em28174 #0: i2c eeprom 0010: 78 0d e4 f0 f5 46 12 00 5a c2 eb c2 e8 30 e9 03
[ 3910.469486] em28174 #0: i2c eeprom 0020: 12 09 de 30 eb 03 12 09 10 30 ec f1 12 07 72 80
[ 3910.469528] em28174 #0: i2c eeprom 0030: ec 00 60 00 e5 f5 64 01 60 09 e5 f5 64 09 60 03
[ 3910.469570] em28174 #0: i2c eeprom 0040: c2 c6 22 e5 f7 b4 03 13 e5 f6 b4 87 03 02 09 92
[ 3910.469610] em28174 #0: i2c eeprom 0050: e5 f6 b4 93 03 02 07 e6 c2 c6 22 c2 c6 22 12 09
[ 3910.469650] em28174 #0: i2c eeprom 0060: cf 02 06 19 1a eb 67 95 13 20 4f 02 c0 13 6b 10
[ 3910.469691] em28174 #0: i2c eeprom 0070: a0 1a ba 14 ce 1a 39 57 00 5c 18 00 00 00 00 00
[ 3910.469730] em28174 #0: i2c eeprom 0080: 00 00 00 00 44 36 00 00 f0 10 02 00 00 00 00 00
[ 3910.469769] em28174 #0: i2c eeprom 0090: 5b 23 c0 00 00 00 20 40 20 80 02 20 01 01 00 00
[ 3910.469809] em28174 #0: i2c eeprom 00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3910.469849] em28174 #0: i2c eeprom 00b0: c6 40 00 00 00 00 a7 00 00 00 00 00 00 00 00 00
[ 3910.469887] em28174 #0: i2c eeprom 00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 38 32
[ 3910.469929] em28174 #0: i2c eeprom 00d0: 34 31 30 31 31 36 36 30 31 37 31 33 31 31 59 5a
[ 3910.469970] em28174 #0: i2c eeprom 00e0: 43 37 00 4f 53 49 30 30 33 30 38 44 30 31 31 30
[ 3910.470010] em28174 #0: i2c eeprom 00f0: 59 5a 43 37 00 00 00 00 00 00 00 00 00 00 31 30
[ 3910.470052] em28174 #0: i2c eeprom 0100: ... (skipped)
[ 3910.470078] em28174 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x39b824ad
[ 3910.470089] em28174 #0: EEPROM info:
[ 3910.470101] em28174 #0: microcode start address = 0x0004, boot configuration = 0x01
[ 3910.499850] em28174 #0: No audio on board.
[ 3910.499886] em28174 #0: 500mA max power
[ 3910.499904] em28174 #0: Table at offset 0x39, strings=0x1aa0, 0x14ba, 0x1ace
[ 3910.500206] em28174 #0: Identified as PCTV nanoStick T2 290e (card=78)
[ 3910.500240] em28174 #0: v4l2 driver version 0.2.0
[ 3910.512528] em28174 #0: V4L2 video device registered as video0
[ 3910.512566] em28174 #0: dvb set to isoc mode.
[ 3910.529568] gpiochip_find_base: cannot find free range
[ 3910.529608] gpiochip_add: gpios -1..1 (cxd2820r) failed to register
[ 3910.529659] em28174 #0: /2: frontend initialization failed
[ 3910.530623] Registered IR keymap rc-pinnacle-pctv-hd
[ 3910.531316] input: em28xx IR (em28174 #0) as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.1/rc/rc1/input4
[ 3910.531938] rc1: em28xx IR (em28174 #0) as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.1/rc/rc1

So, no frontend /dev tree generated since about kernel 3.10.25

The RPi has several improvements with later kernels so it's a pain to revert to an old one.