The control centre allows you to configure a T2 tuner, and it will work ok.
The E2 tuner config no longer has this option (old driver, new driver).....
Ok after update I now receive Cannot read data when scanning sky uk in autobouquetsmaker. In Automatic scan I I receive Scan Tuner I ( (Combined DVB-S2/C)Originally Posted by dsayers
1_0_19_A2C_1A_F020_FFFF0000_0_0_0_20191222043833.jpg
I scan tuner I and receive odd channel names instead of the actual names.
autoscan.jpg
Automatic scan only tunes DVB-S
This is the last scanned bouquet with odd names
userbouquet.LastScanned.tv.zip it looks likes it's naming them via the sid
I'm not sure why I haven't noticed this before. Maybe because I already have tuned services but ABM normally leaves the errors on till someone sees after auto update
Last edited by dsayers; 22-12-19 at 06:19.
I have installed 5.0 032 so that there is no chance of updating Enigma2 components when installing something that depends on it. I then updated Sundtek drivers. I was still able to change the mode of the Tuner within Enigma2.
To me, it is is something in Enigma2 and not the Sundtek drivers.
Really need to fix the non-vu arm detection and 64bit detection to deal with this properly.
There is very little control in Automatic scan. Better to use manual scan. Also, some TK users advocate using Virgin All areas whichc is the wrong thing to do.
I've just tried 5.1.031, and I can't change the tuner mode within Enigma2. (nb reboot required first)
So it's either something that has happened between 5.0.032 and 5.1.031, or it's the latest Sundek driver.
My money is on the Sundek driver, as the one dated 02/10/2019 doesn't have a problem.
There will be a few more updates within the next few days. Once that's set we'll have a look at the integration. I guess the issue is the installer itself (since there was no other update on the corresponding drivers).
That issue needs to be checked carefully since it might break the support for the previously fixed ARM STB.
The side effects are unexpected if they're related to that update (of course we try to avoid them but when they happen they have to be corrected carefully to not cause more issues...)
@Sundtek
The main difference is that the tuner is not being recognised as a switchable one. Can you confirm if it should still be? If so, we will need to adapt code to cater for it.
Hi,
we have figured out the issue already it's indeed caused by the update of the installer (not by the driver itself). But reverting the modification will break it for some other boxes;
So we know how to get it work for both groups but need to add some hardware-detection for the boxes which need a different setup.
I'm waiting for the person with the other settopbox who requires the latest changes so we can sort it out for both groups.
abu baniaz (24-12-19),Andy_Hazza (24-12-19),ccs (24-12-19),tappari (24-12-19)
My GigaBlue is not detecting the tuner. Whenever I go into the plugin, it says the driver is not installed. Drivers have been installed from within the plugin (20180605-02).
Doing it by command line locks up the box until I reboot. You had fixed this last year.
dmesg ouput attached as well as results ofCode:Welcome to OpenViX for gbue4k openvix 5.3 gbue4k gbue4k login: root root@gbue4k:~# sudo -s -bash: sudo: command not found root@gbue4k:~# cd /tmp root@gbue4k:/tmp# wget http://sundtek.de/media/sundtek_netinst.sh --2019-12-25 21:36:45-- http://sundtek.de/media/sundtek_netinst.sh Resolving sundtek.de... 85.10.198.106 Connecting to sundtek.de|85.10.198.106|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 128668 (126K) [application/octet-stream] Saving to: ‘sundtek_netinst.sh’ sundtek_netinst.sh 100%[=============================================================================================================>] 125.65K 802KB/s in 0.2s 2019-12-25 21:36:46 (802 KB/s) - ‘sundtek_netinst.sh’ saved [128668/128668] root@gbue4k:/tmp# chmod 777 sundtek_netinst.sh root@gbue4k:/tmp# ./sundtek_netinst.sh Busybox installation Welcome to the Sundtek linux / freebsd driver setup (C)opyright 2008-2019 Sundtek <kontakt@sundtek.de> Legal notice: This software comes without any warranty, use it at your own risk Please note it's only allowed to use this driver package with devices from authorized distributors or from Sundtek Germany The Virtual analogTV Grabber (vivi) might be used freely for testing purpose Do you want to continue [Y/N]: Nutzungsbedingungen: Sundtek übernimmt keinerlei Haftung für Schäden welche eventuell durch das System oder die angebotenen Dateien entstehen können. Dieses Softwarepaket darf ausschließlich mit Geraeten von autorisierten Distributoren oder Sundtek Deutschland verwendet werden Der Virtuelle AnalogTV Treiber (vivi) kann für Testzwecke ohne jegliche Restriktionen verwendet werden Wollen Sie fortfahren [J/N]: y adding /opt/bin to environment paths unpacking... checking system... installing (netinstall mode) ... Downloading architecture specific driver ... armsysvhf Download finished, installing now ... installing remote control support finalizing configuration... (can take a few seconds) Settopbox Detected Starting driver... done. root@gbue4k:/tmp#
Code:opkg update && opkg install v4l-utils dvb-fe-tool -a1 find /dev/dvb/adapter* cat /proc/bus/nim_sockets
A new driver/loader appeared here this morning...but my ET10K doesn't see it.Code:http://sundtek.de/media/
I eventually did an update anyway - see 2 attachments - before and after the update. Neither make any sense and the outcome is the same as post #1. Ignore the timestamps of the screenshots, I took them in the wrong order.
There's another update just appeared on sundtek.de/media, my ET10K still can't see it, I'll have a try tomorrow.
Can't see the USB device or can't see update?
Can't see the latest driver update - I still see screenshot 1 in post #40.
Perhaps the date is entered incorrectly by mistake. The last two posts are saying 2019
Probably wasting my time, but I tried again - exactly the same as post #40,
apart from the "current driver" now showing as 2020-01-07 21:56:39 and the "latest driver" still 2019-12-13 17:21:40.
Maybe the new decade is a problem.
Posting Permissions
Reply With Quote