That is great news. Unfortunately I don’t really understand anything you did!
I am just an ordinary user and was hoping for more of PnP solution.
Is there a simple (and I really mean that - bullet points etc) step by step guide to getting DVB-S working?
My knowledge is limited to being able to SSH into the Vero so is there a basic script I can copy and paste? I am sure this would open up a larger market for the Vero 
It’s all in the post tagged as solution 
It boils down to this:
ssh osmc@vero
wget https://sundtek.de/media/sundtek_netinst.sh
chmod +x ./sundtek_netinst.sh
sudo ./sundtek_netinst.sh -system armsysvhf
sudo reboot
If you have an existing Tvheadend setup on your Vero and the Sundtek adapters don’t show up, go ahead and delete the old Tvheadend config and start from scratch (following the Tvheadend wizard) like this.
Let me know if you’ve further questions.
Thank you very much. I actually think I can do that. I really appreciate you taking the trouble.
Any suggestions on the best place to buy a sundtek DVB-S?
I don’t have Tvheadend installed as I haven’t bothered to buy a DVB-S yet - since I couldn’t find anyone (until you) you had managed to get it working 
. Hopefully a clean install will work.
Thanks again
Any suggestions on the best place to buy a sundtek DVB-S?
Probably best from Sundtek themselves…?
Ha…that should have been obvious. Stressy day and my brain is not engaged. Thanks
There are also Dual DVB-S/S2/S2X USB Tuners available now.
I guess it would have been easier just to ask us about the drivers 
Does this system use a 64bit kernel and 32bit environment?
I wonder why it didn’t detect the system properly, there must be a reason behind that.
Back then in early 2018 we still had tons of driver updates for the current fpga based multituners in the queue.
There are also Dual DVB-S/S2/S2X USB Tuners available now.
Yep, saw that right after ordering two single ones. Oh well…
I guess it would have been easier just to ask us about the drivers
I tried that but no one could be reached via the support chat. I’m also still waiting for my forum account to be activated and, to be honest, the info there is scattered across various places, outdated and riddled with heaps of broken links (404s, due to changed request URL format, could have been converted). I like your hardware but the so called “manual” (forum) is barely usable, in particular for the non-IT pros, I imagine, trying to use your devices.
Does this system use a 64bit kernel and 32bit environment?
I wonder why it didn’t detect the system properly, there must be a reason behind that.
Yes, that’s right. Thus the architecture detection simply finds arm64 and installs that. Also, armsysvhf, the option eventually used here, is completely undocumented in the installers help page. Please add that.
Cheers
The Support Chat is a public IRC channel (#sundtek) on irc.freenode.net, sometimes it takes some time to get an answer since it’s not a direct one to one chat.
arm64 is available since 2016
arm64musl is available since late 2018
If all Vero systems are the same we can add a check to the installer to use the 32bit build automatically instead of 64bit.
arm64 is available since 2016
arm64musl is available since late 2018
Not sure how that’s relevant in this context.
If all Vero systems are the same we can add a check to the installer to use the 32bit build automatically instead of 64bit.
I recommend two things:
armsysvhf and arm64 to the (documented) -system options of the sundtek_netinst.sh installer script (see above)armhf userland if you detected an arm64 kernel. If so install armsysvhf instead, at least optionally.Yet, @sam_nazarko should chime in here for an official recommendation.
grep “osmcdev=vero3” /proc/cmdline should suffice to identify the system
Happy new year @sam_nazarko !
Quick question: I moved to the Vero V a few months ago and I’ve had some issues with the Sundtek SkyTV Ultimate 8 sticks mentioned above ever since - TVH often just loses the two adapters. Are there any relevant changes from the Vero 4k to the Vero 5 with regards to kernel or userspace architectures?
I tried to update the Sundtek driver and installed the latest version using the same method as discovered above. Unfortunately, TVH now isn’t able to use those adapters at all anymore. I already deleted the adapter cache via rm ~/.hts/tvheadend/input/linuxdvb/adapters/* (with stopped TVH service).
Now TVH reports linuxdvb: unable to open /dev/dvb/adapter[0|1]/frontend0 on startup, no idea why. The permissions on the device nodes are 777 (root/root), so that shouldn’t be the problem. Also, Sundtek’s own tool can successfully query the two devices, e.g.
$ /opt/bin/mediaclient -e
**** List of Media Hardware Devices ****
device 0: [ eLight] DVB-S/S2, REMOTE-CONTROL
[INFO]:
STATUS: ACTIVE
[BUS]:
ID: 1-2.4
[SERIAL]:
ID: 1234
[DVB-S/S2]:
FESTATUS: ACTIVE
LNBVOLTAGE: ENABLED
LNBSUPPLY: USBPOWER
LNBSTATUS: OK
FRONTEND: /dev/dvb/adapter0/frontend0
DVR: /dev/dvb/adapter0/dvr0
DMX: /dev/dvb/adapter0/demux0
[REMOTECONTROL]:
INPUT0: /dev/mediainput0
So, the driver installation and the discovered device seem to be ok. Only TVH is unable to use the devices. I even checked whether the devices are busy, but they aren’t:
/opt/bin/mediaclient --lc
**** List of Media Clients ****
/dev/dvb/adapter0/frontend0:
No client connected
/dev/dvb/adapter0/dvr0:
No client connected
/dev/dvb/adapter0/demux0:
No client connected
The only slightly odd thing I can find is via dmesg:
[ 3.564987] usb 1-2.4: New USB device found, idVendor=2659, idProduct=1805
[ 3.564994] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.564996] usb 1-2.4: Product: eLight
[ 3.564999] usb 1-2.4: Manufacturer: Sundtek
[ 3.565001] usb 1-2.4: SerialNumber: 1234
[ 3.577205] usb 1-2.4: Unsupported device <========
That’s kind of “coroborated” by this:
$ cat /dev/dvb/adapter0/frontend0
cat: /dev/dvb/adapter0/frontend0: No such device
Not sure how mediaclient successfully accesses the device…
What am I missing?
Thanks!
Darn, using the latest driver (sundtek_installer_251220.005308.sh) the Vero V now freezes up during or shortly after boot, even without any USB devices attached! Is there any kind of safe mode that would let me remove that driver or do I have to do a full factory reset…? 
Ok, f*ck this, reinstalling…
FYI, the (macOS) installer installed 2025.08, despite 2025.11 being selected 
Hi,
Can you give me a log of this so I can check what the issue may be?
The idea behind @Sundtek drivers is that they are not impacted by kernel changes at all because of their userspace focus.
I only have a single tuner device from them from around 2014. It works well.
If they want to send more hardware I won’t refuse. Likewise for sending them hardware 
Couple of things that come to mind:
Sam
brevilo if you suspect anything wrong with our drivers you can also ping us at our Discord chat Sundtek
Thanks for the prompt response @Sundtek (Markus)
Thanks guys for getting back to me so quickly. Sorry if I c[a|o]me across a bit harsh, but the outlook of having to redo my elaborate setup (in particular TVH) is deeply frustrating.
Can you give me a log of this so I can check what the issue may be?
Of what, the installer? Where to find it? I reckon the installer gets its list of available versions from your server, so that list seems to have a wrong version → file mapping as version 2025.11 points to the 2025.08 release.
The idea behind @Sundtek drivers is that they are not impacted by kernel changes at all because of their userspace focus.
I presume that’s why USB enumeration (see above) reports usb 1-2.4: Unsupported device since there simply is no dedicated kernel support involved? If so, @Sundtek please confirm that this message is expected and ok.
Try a cold boot
How do you define that? Simply unplug device and boot? Sure, that’s what I had to do when the device locked up during or shortly after boot. BTW, that also the reason why I couldn’t analyze the problem any further than what I wrote above: by lock up I mean HDMI freeze and losing SSH access → no further log access and pulling power plug required.
How are the tuners powered?
The tuners have dedicated power supplies and are connected via a powered USB hub. If only the next Vero model could have four USB ports 
Now that I had to wipe my Vero V I’ll try and resurrect parts of my setup from my old Vero 4k as well as Kodi backups. I’ll report back as soon as I have some more reliable clues.
Can you post more output of your system log? Unsupported device is okay (unsupported by kernel drivers), since they have userspace drivers.
If tvheadend loses an adapter, check dmesg if there’s a power issue; on DVB-S/S2/S2X tuner needs around 300mA @ 5V from the system the Powersupply is only responsible to power the LNB - not the tuner itself.
Two tuners = 600mA @ 5V, if you hit a transponder with a poor signal the current can go up a little bit more eg 400mA (in total for the entire USB device), but the video should also be bad. So let’s say in the worst case 5V 1A for both tuners, be sure that your power supply can handle that.
sam_nazarko is your power connection to the USB ports suitable for that? Long term 300mA per port (when active), short term 400mA hike (transponder with poor signal).
If the tuner is not attached to an external power supply the LNB power will be taken from the 5V input - now we can go up to 5V @ 0.8A (two tuners = 1.6A) = 8 Watt
Also be sure that the USB Cables are OK - our cables are OK normally but there’s a wide variety out there which might introduce additional resistance before the power arrives the tuner.
Yes, this should be OK.
0.5A via USB2 and 0.9A via USB3 port.
Not really, due to the above. Also, which one specifically? There where some suspicious entries in the mediaclient.log which I forgot to copy before I wiped the Vero but I hope I’ll get those back in my following repro attempts.
the Powersupply is only responsible to power the LNB - not the tuner itself.
Good to know. But given that I’m purposefully running the two tuners via a powered USB hub, power shouldn’t be an issue. Also, I’ve been running this setup (with the Vero 4K) for almost six years. Yes, I had occasions where THV couldn’t find an adapter anymore, but this problem increased significantly (to almost daily) after I migrated to the Vero V. Sure, that’s only correlation, not necessarily causation but it’s a hint.
if you suspect anything wrong with our drivers
While not entirely clear yet, it seems as if the 251220.005308 driver started to cause the lockups where the 250816.183236 driver (presumably) caused the increased adapters losses with Vero V. So in terms of stability there seems to be a regression between the two. Also, can you please add an option to mediaclient which reports the installed driver version?
Thanks
Where USB2 is the right/black one and USB3 the left/blue one, I presume?