Tvheadend

Without knowing this stick, I suppose I'd check:

1. Kernel support (the stick sounds old, so 3.10 might be fine or you may need additional drivers)

2. See if those kernel modules are actually loading and are the right ones

3. Any firmware required?

4. Access permissions - can the tvheadend process access the video devices in /dev/dvb or similar

5. Anything in syslog from tvh beyond what you posted

6. Anything in dmesg beyond what you posted

7. What precisely does the tvh web interface tell you - can it see the tuner at all, is it enabled, etc.

1&2. i got all the right kmods for my kernel from an external site and all loaded fine after some tinkering
3. nope, not for the rt2832u (but the myGica T230 i want to use later will do)
4. i have root user only and ran it as root, so yes. and even testwise chmod -R 'ded /dev/dvb/ to 777
5&6 no, neither bash or dmesg throwed anything after completing the package setup and starting tvh
7. it only offers a "IPTV" tab under DVB-devices

You load more modules than necessary.
I'm using the latest kernel 3.18.14 and load only these:

dvb-core.ko
dvb-usb-rtl28xxu.ko
dvb_usb_v2.ko
input-core.ko
r820t.ko
rtl2830.ko
rtl2832.ko
rtl2832_sdr.ko

it loads like this:

[   14.070000] dvb_usb_rtl28xxu 1-1:1.0: no of_node; not parsing pinctrl DT
[   14.070000] usb 1-1: dvb_usb_v2: found a 'Realtek RTL2832U reference design' in warm state
[   14.410000] usb 1-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[   14.430000] DVB: registering new adapter (Realtek RTL2832U reference design)
[   14.440000] i2c i2c-0: Added multiplexed i2c bus 1
[   14.460000] i2c i2c-0: Added multiplexed i2c bus 2
[   14.470000] usb 1-1: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))...
[   14.480000] r820t 0-001a: creating new instance
[   14.510000] r820t 0-001a: Rafael Micro r820t successfully identified
[   14.540000] usb 1-1: dvb_usb_v2: 'Realtek RTL2832U reference design' successfully initialized and connected
[   14.560000] dvb_usb_rtl28xxu 1-1:1.1: no of_node; not parsing pinctrl DT
[   14.560000] usbcore: registered new interface driver dvb_usb_rtl28xxu

And then tvheadend just works.
I start it, hovewer, like this:

tvheadend -C -u root

http://www.tvrouter.org

T C wrote:

So, the stick works, but is not detected. any idea?

Actually, the issue is in the tvheadend binary you use.
It seems that the binary was compiled without "linux-dvb" support.

You can use the version I've just compiled and tested on my TP-Link TL-WDR3600
Find it attached to the post.
ar71xx tvheadend binary ipk

Regards,
Lyu
www.tvrouter.org

I've tried your compiled version for ar71xx (I've tested on TP-Link TL-WDR4300, with BB) and works pretty well with a USB dvb-t dongle with chip IT9135.
On my system I've also an SAT-IP server for DVB-S. With actual binary they get not recognized, I assume because Tvheadend is compiled without SAT-IP, is that corrects? Can you compile with SAT-IP and share?

Thanks
ENina

Hi ENina,

actually the binary I've uploaded is compiled WITH sat-ip support.
these are all the options. Just disabled the decrypting stuff.
I'm happy to recompile with some other options turned on.

CONFIG_CWC = no
CONFIG_CAPMT = no
CONFIG_CONSTCW = no
CONFIG_LINUXDVB = yes
CONFIG_SATIP_SERVER = yes
CONFIG_SATIP_CLIENT = yes
CONFIG_HDHOMERUN_CLIENT = no
CONFIG_HDHOMERUN_STATIC = no
CONFIG_IPTV = yes
CONFIG_TSFILE = yes
CONFIG_DVBSCAN = yes
CONFIG_TIMESHIFT = yes
CONFIG_TRACE = yes
CONFIG_IMAGECACHE = yes
CONFIG_AVAHI = no
CONFIG_ZLIB = yes
CONFIG_LIBAV = no
CONFIG_LIBFFMPEG_STATIC = no
CONFIG_INOTIFY = yes
CONFIG_EPOLL = yes
CONFIG_URIPARSER = no
CONFIG_CCACHE = no
CONFIG_TVHCSA = no
CONFIG_BUNDLE = yes
CONFIG_DVBCSA = no
CONFIG_KQUEUE = no
CONFIG_DBUS_1 = no
CONFIG_ANDROID = no
CONFIG_TSDEBUG = no
CONFIG_LOCKOWNER = yes
CONFIG_QSORT_R = yes
CONFIG_LIBICONV = yes
CONFIG_PY_GZIP = yes
CONFIG_BIN_BZIP2 = yes
CONFIG_SSL = yes
CONFIG_LINUXDVBAPI = yes
CONFIG_UPNP = yes
CONFIG_INOTIFY_H = yes
CONFIG_MPEGTS = yes
CONFIG_MPEGTS_DVB = yes

Regards,
Lyu
www.tvrouter.org

Hello, thanks for the kick replay.

I've dig more on this and found a tread explaining that satip servers can have detection problems and its possible specify them on the command line (I've already tested on a raspberry pi and X86 systems with tvheadend and never had this issue on the detection).

My sat Ip server is a Digibit R1 and the way I overcome this was set/add following command option "--satip_xml http://xxx.xxx.xxx.xxx:8080/desc.xml" to tvheadend start command

Now I've realized and that is in line what you have already commented that decrypting settings are missing.

If you don't mind can you compile with that options activated.

Many thanks for your time.
Best Regards
ENina

Hello,

Did you have problems compiling with decrypting settings?

Best regards
ENina