So, I got myself a Vero 4K. So far, very happy with it! It runs sooo smoothly, design is nice, and managed to get pretty much everything set up the way I had my rpi3. Very good experience (though I dislike the clicking sound of the remote controller, but I’m using my tv remote anyway, so no biggie).
The only thing I can’t get to work is my tv tuner, a Terratec Cinergy USB XS DVB-C. When I insert the cable to the Vero and reboot, I’m seeing a “Please stand by”, and within 10 seconds, it reboots - and keeps looping.
It worked nicely on my RPI3 - when I coped the dvb-usb-terratec-htc-stick-drxk.fw from the OpenELEC dvb-firmware library to lib/firmware. So I tried the same thing here on the Vero 4K, but to no avail.
@sam_nazarko, do you have any idea if I can get this to work somehow? Or will it never be supported? If not, can you provide me with a list of nicely working and fully supported DVB-C tuners?
Can you run lsusb on the working Pi 3 so I can see the device information?
If the Please Standby splash loops, then it sounds like the kernel is panicking early on. Do you also get
a reboot if you plug the device in after the system has booted?
I will run lsusb tonight, once I get back from work. Just managed to get everything set up, so I’ll have to fiddle around with some cables.
The Vero doesn’t reboot if I plug the device in after the system has booted (though I didn’t try the actual tuning, figured it’d be pointless if it didn’t work after booting anyway).
Well if the Vero doesn’t crash if you plug the stick in after it booted no need to switch back to the Pi. You should be able to share the lsusb from the Vero.
Also after you plug it in provide dmesg via dmesg | paste-log
Here’s my lsusb (Vero 4K) with the Terratec Cinergy USB XS tv tuner plugged in:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bc2:3312 Seagate RSS LLC
Bus 001 Device 006: ID 0ccd:008e TerraTec Electronic GmbH Cinergy HTC XS
Bus 001 Device 005: ID 2252:1037
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The stick seems to be found correctly and driver loaded but no tuner found. In that case it might be interesting to see what the dmesg says on the Pi but I let @sam_nazarko comment first.
[ 1417.098694] usb 1-1.2: new high-speed USB device number 6 using xhci-hcd
[ 1417.199594] usb 1-1.2: New USB device found, idVendor=0ccd, idProduct=008e
[ 1417.199607] usb 1-1.2: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[ 1417.199612] usb 1-1.2: Product: Cinergy HTC USB XS
[ 1417.199617] usb 1-1.2: Manufacturer: TerraTec Electronic GmbH
[ 1417.199623] usb 1-1.2: SerialNumber: 100102001728
[ 1417.240422] em28xx 1-1.2:1.0: New device TerraTec Electronic GmbH Cinergy HTC USB XS @ 480 Mbps (0ccd:008e, interface 0, class 0)
[ 1417.240436] em28xx 1-1.2:1.0: Audio interface 0 found (Vendor Class)
[ 1417.240443] em28xx 1-1.2:1.0: Video interface 0 found: isoc
[ 1417.240448] em28xx 1-1.2:1.0: DVB interface 0 found: isoc
[ 1417.240541] em28xx 1-1.2:1.0: chip ID is em2884
[ 1417.304567] em28xx 1-1.2:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x58369b8e
[ 1417.304579] em28xx 1-1.2:1.0: EEPROM info:
[ 1417.304585] em28xx 1-1.2:1.0: microcode start address = 0x0004, boot configuration = 0x01
[ 1417.310776] em28xx 1-1.2:1.0: I2S audio, 5 sample rates
[ 1417.310791] em28xx 1-1.2:1.0: 500mA max power
[ 1417.310798] em28xx 1-1.2:1.0: Table at offset 0x36, strings=0x269c, 0x326a, 0x1ac2
[ 1417.310997] em28xx 1-1.2:1.0: Identified as Terratec Cinergy HTC USB XS (card=87)
[ 1417.311006] em28xx 1-1.2:1.0: Currently, V4L2 is not supported on this model
[ 1417.311011] em28xx 1-1.2:1.0: dvb set to isoc mode.
[ 1417.311184] usbcore: registered new interface driver em28xx
[ 1417.320209] em28xx 1-1.2:1.0: Binding audio extension
[ 1417.320230] em28xx 1-1.2:1.0: em28xx-audio.c: Copyright (C) 2006 Markus Rechberger
[ 1417.320235] em28xx 1-1.2:1.0: em28xx-audio.c: Copyright (C) 2007-2016 Mauro Carvalho Chehab
[ 1417.320268] em28xx 1-1.2:1.0: Endpoint 0x83 high-speed on intf 0 alt 7 interval = 8, size 196
[ 1417.320275] em28xx 1-1.2:1.0: Number of URBs: 1, with 64 packets and 192 size
[ 1417.321077] em28xx 1-1.2:1.0: Audio extension successfully initialized
[ 1417.321091] em28xx: Registered (Em28xx Audio Extension) extension
[ 1417.343521] WARNING: You are using an experimental version of the media stack.
As the driver is backported to an older kernel, it doesn’t offer
enough quality for its usage in production.
Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
a83dbc951051ded0ec728f65cc918b7320600b55 Remove unused stv6120 headers.
[ 1417.351069] em28xx 1-1.2:1.0: Binding DVB extension
I think I know what you meant now, Sam. When I plug in the tuner, I do get a folder inside /dev/dvb, named adapter0. Tried to copy the files to my pc, but I couldn’t. Filenames inside it are: net0, frontend0, dvr0, demux0. I hope that was what you meant. Otherwise, let me know.
I tried plugging it in to my RPi3 again, to see what the dmesg said. Here you are (if that’s any help at all): https://paste.osmc.tv/amenixozel
So, am I reading this correctly, that you’re working on what might be the solution? And do you think it is something that will come within the next months? If so, I’ll just leave the tuner unplugged until then.
Let me know if there’s anything else I can do to help or diagnose the problem.
I compared the two dmesg (Vero and Pi) and they look similar.
Actually I understand you initial problem is the Vero crashes when you boot with the stick plugged in.
But did you actually try to use the stick when you plug it in after you booted the Vero. From what I read in the dmesg it is detected and should actually work.
No, I didn’t try using it on my Vero, as I thought it’d be a waste of time if I couldn’t use it after a reboot anyway (turning off my Vero every night).
Thanks, both of you, for replying so fast. Fingers crossed for a solution next month, then. But no rush. And yes, please let me know if you need anything else!
Hi Sam, any news on this? Not trying to put pressure on you, just curious. Tried to boot up this morning with the tuner plugged in, and still the same thing happens.
Thanks for the fast reply. As I wrote in the original post, the problem only occurs when I have the Cinergy USB tuner plugged in, and it goes in a constant reboot loop.
Didn’t have this problem with the RPI3 – and it’s actually the only thing I miss from the Rpi.
I think I’ve misunderstood your request.
We do not have DVB backports presently. It’s unclear if the dongle works for you after boot. Yes – it will work when we have newer DVB drivers. We hope we can do this before a mainline kernel.
However I’m not sure what the cause of the boot loop is. If it’s a kernel panic caused by an issue with the driver that will be fixed indirectly as a result.
But no rush. And yes, please let me know if you need anything else!