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
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