Pity about the motorised dish bug.
New tuner Si2166D- Mut@nt 51HD
Re: New tuner Si2166D- Mut@nt 51HD #41
Re: New tuner Si2166D- Mut@nt 51HD #42
Re: New tuner Si2166D- Mut@nt 51HD #43
Re: New tuner Si2166D- Mut@nt 51HD #44
Re: New tuner Si2166D- Mut@nt 51HD #45
Re: New tuner Si2166D- Mut@nt 51HD #46
Posted 14 January 2018 - 10:07
Fails to obtain tuner lock after moving the dish. Needs a zap to sort it out. Or wait for some timeout to elapse.
Bug appeared May 2017. Reported July 2017.
Hi Huevos,
Does the box poll for lock during its journey?
[eDVBFrontend] rotor locked step 0 failed (not locked) [eDVBFrontend] set sequence pos -3 [eDVBFrontend] sleep 250ms [eDVBFrontend] rotor locked step 0 failed (not locked) [eDVBFrontend] set sequence pos -3 [eDVBFrontend] sleep 250ms [eDVBFrontend] rotor locked step 0 failed (not locked) [eDVBFrontend] set sequence pos -3 [eDVBFrontend] sleep 250ms [eDVBFrontend] rotor locked step 0 failed (not locked) [eDVBFrontend] set sequence pos -3 [eDVBFrontend] sleep 250ms [eDVBFrontend] locked step 0 ok [eDVBFrontend] set sequence pos -3 [eDVBFrontend] sleep 250ms
ET9000, OpenPLi 4.0, 13E, 19E
HD51, OpenPLi 6.2, 75E - 30W
Re: New tuner Si2166D- Mut@nt 51HD #47
Re: New tuner Si2166D- Mut@nt 51HD #48
Re: New tuner Si2166D- Mut@nt 51HD #49
Re: New tuner Si2166D- Mut@nt 51HD #50
Re: New tuner Si2166D- Mut@nt 51HD #51
Posted 14 January 2018 - 14:40
Just look on the various forums. It is widely confirmed. Here is a quote from another forum: "anyway, move sat and it sits there on the channel doing naff all for about 40 seconds or more before it decides to display the channel, SD, unencrypted.....awful".
Edited by Huevos, 14 January 2018 - 14:42.
Re: New tuner Si2166D- Mut@nt 51HD #52
Re: New tuner Si2166D- Mut@nt 51HD #53
Posted 14 January 2018 - 16:03
Yes it does lock eventually. Here is another quote: "when I move from a channel on one sat to a channel on another, I fail to get tuning lock immediately after the dish ceases moving to the new position. If I switch channel on the new sat I get immediate lock. If I don't switch channel then the lock occurs after about 60-70 seconds".
Re: New tuner Si2166D- Mut@nt 51HD #54
Posted 14 January 2018 - 16:16
It is very disappointing.
I was just wondering if every HD51 has this issue as cristo4 does not seem to be aware of it at all.
Perhaps it only affects some configurations or some tuners?
Nowadays few people have motorised systems so there are not many people who can test.
ET9000, OpenPLi 4.0, 13E, 19E
HD51, OpenPLi 6.2, 75E - 30W
Re: New tuner Si2166D- Mut@nt 51HD #55
Posted 14 January 2018 - 16:59
Now just maybe, we are comparing Apple & Oranges here ?
e.g Cristo4 is perhaps using the s2x tuner?? (and doesn't see the issue with his motorised setup) and the other reports are using the s2 tuner?
Just a thought!
Gigablue Quad 4K & UE 4K, Vu+Uno4KSE, DM900
.........FBC Tuners:
------------------> GT-SAT unicable lnb to 1.5M dish(28.2E)
------------------> Gigablue unicable lnb to 80 cm dish(19.2E)
Octagon sf8008, AX HD61, Edision Osmio 4K+, Zgemma H9Combo using Legacy ports on multiswitches
Zgemma H9twin & Zgemma H9 C/S mode into Giga4K
Re: New tuner Si2166D- Mut@nt 51HD #56
Re: New tuner Si2166D- Mut@nt 51HD #57
Re: New tuner Si2166D- Mut@nt 51HD #58
Re: New tuner Si2166D- Mut@nt 51HD #59
Posted 16 January 2018 - 14:52
I am one of the users / testers on Vix who @Huevos refers to as having the issue. I have the S2 tuner. The issue is exactly as @Robinson posted in #47 above. It has been going on since about December 2016. If I restore an image prior to that date the problem does not happen. It occurs on Vix and ATV. I "work around" the delay by zapping to another transponder after the motor has moved from one sat to another.
Re: New tuner Si2166D- Mut@nt 51HD #60
Posted 25 January 2018 - 23:14
Fails to obtain tuner lock after moving the dish. Needs a zap to sort it out. Or wait for some timeout to elapse.
Bug appeared May 2017. Reported July 2017.
I can now confirm the bug is there even with DVB-S2X tuner!
I wonder how it is possible that it does not affect everybody with a motorised dish.
Several other questions and observations:
1) What is CONTEXT button on the remote used for?
2) Isn't MOVIE folder created now? Are recordings now saved to /hdd folder by default?
3) When I do "ps" in telnet I get a very suspicious process:
1453 root 0 SW [ddddddddddddddd]
What is it?
Here is the complete "ps" output:
root@hd51:~# ps PID USER VSZ STAT COMMAND 1 root 1580 S init [3] 2 root 0 SW [kthreadd] 3 root 0 SW [kworker/0:0] 4 root 0 SW< [kworker/0:0H] 5 root 0 SW [kworker/u4:0] 6 root 0 SW [ksoftirqd/0] 7 root 0 SW [rcu_sched] 8 root 0 SW [rcu_bh] 9 root 0 SW [migration/0] 10 root 0 SW< [lru-add-drain] 11 root 0 SW [watchdog/0] 12 root 0 SW [cpuhp/0] 13 root 0 SW [cpuhp/1] 14 root 0 SW [watchdog/1] 15 root 0 SW [migration/1] 16 root 0 SW [ksoftirqd/1] 17 root 0 SW [kworker/1:0] 18 root 0 SW< [kworker/1:0H] 19 root 0 SW [kdevtmpfs] 20 root 0 SW [kworker/u4:1] 343 root 0 SW [oom_reaper] 344 root 0 SW< [writeback] 346 root 0 SW [kcompactd0] 347 root 0 SW< [crypto] 348 root 0 SW [kworker/1:1] 349 root 0 SW< [bioset] 351 root 0 SW< [kblockd] 354 root 0 SW< [ata_sff] 471 root 0 SW< [rpciod] 472 root 0 SW< [xprtiod] 486 root 0 SW [kswapd0] 487 root 0 SW< [vmstat] 488 root 0 SW< [bioset] 489 root 0 SW< [nfsiod] 490 root 0 SW< [cifsiod] 1060 root 0 SW< [bioset] 1061 root 0 SW< [bioset] 1062 root 0 SW< [bioset] 1063 root 0 SW< [bioset] 1064 root 0 SW< [bioset] 1065 root 0 SW< [bioset] 1066 root 0 SW< [bioset] 1067 root 0 SW< [bioset] 1068 root 0 SW< [bioset] 1069 root 0 SW< [bioset] 1070 root 0 SW< [bioset] 1071 root 0 SW< [bioset] 1072 root 0 SW< [bioset] 1073 root 0 SW< [bioset] 1074 root 0 SW< [bioset] 1075 root 0 SW< [bioset] 1109 root 0 SW< [bioset] 1112 root 0 SW< [bioset] 1115 root 0 SW< [bioset] 1118 root 0 SW< [bioset] 1121 root 0 SW< [bioset] 1124 root 0 SW< [bioset] 1127 root 0 SW< [bioset] 1130 root 0 SW< [bioset] 1145 root 0 SW [scsi_eh_0] 1146 root 0 SW< [scsi_tmf_0] 1149 root 0 SW [scsi_eh_1] 1150 root 0 SW< [scsi_tmf_1] 1153 root 0 SW [kworker/u4:2] 1154 root 0 SW [kworker/u4:3] 1200 root 0 SW< [bioset] 1201 root 0 SW [kworker/1:2] 1211 root 0 SW [kworker/u4:4] 1216 root 0 SW [kworker/0:1] 1240 root 0 SW [irq/46-mmc0] 1262 root 0 SW< [bioset] 1263 root 0 SW [mmcqd/0] 1264 root 0 SW< [bioset] 1265 root 0 SW [mmcqd/0boot0] 1266 root 0 SW< [bioset] 1267 root 0 SW [mmcqd/0boot1] 1268 root 0 SW< [bioset] 1269 root 0 SW [mmcqd/0rpmb] 1287 root 0 SW< [kworker/0:1H] 1288 root 0 SW [jbd2/mmcblk0p3-] 1289 root 0 SW< [ext4-rsv-conver] 1393 root 0 SW< [kworker/1:1H] 1394 root 0 SW [jbd2/sda1-8] 1395 root 0 SW< [ext4-rsv-conver] 1453 root 0 SW [ddddddddddddddd] 1454 root 0 SW [nxsched] 1455 root 0 SW [nxsched] 1456 root 0 SW [nxsched] 1457 root 0 SW [nxsched] 1458 root 0 SW [nxsched] 1459 root 0 SW [nxsched] 1460 root 0 SW [nxsched] 1461 root 0 SW [nxsched] 1476 root 0 SW< [pp_work] 1479 root 0 SW< [rp_work] 1546 root 0 SW< [reboot_work] 1548 root 0 SW< [ci_work] 1552 root 0 SW [sci0] 1555 root 0 SW [cec-hdmi_cec] 1724 root 2360 S udhcpc -b -H hd51 -p /var/run/udhcpc.eth0.pid -i eth0 1735 messageb 2736 S /usr/bin/dbus-daemon --system 1741 root 0 SW< [ipv6_addrconf] 1742 root 2184 S /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22 1746 rpc 2060 S /usr/sbin/rpcbind 1751 rpcuser 2660 S /usr/sbin/rpc.statd 1761 root 2716 S /usr/sbin/inetd 1764 root 28424 S /usr/sbin/smbd 1766 root 26972 S {smbd-notifyd} /usr/sbin/smbd 1767 root 26964 S {cleanupd} /usr/sbin/smbd 1769 root 18736 S /usr/sbin/nmbd 1773 root 2360 S /sbin/syslogd -n -O /var/log/messages 1776 root 2360 S /sbin/klogd -n 1783 avahi 3280 S avahi-daemon: running [hd51.local] 1784 avahi 3280 S avahi-daemon: chroot helper 1792 root 2360 S {enigma2.sh} /bin/sh /usr/bin/enigma2.sh 1797 root 89272 S /usr/bin/enigma2 1805 root 0 SW [kworker/0:2] 1811 root 0 SW [kdvb-ad-0-fe-0] 1829 root 2596 R telnetd 1830 root 3408 S /bin/login 1831 root 2592 S -sh 1855 root 2592 R ps root@hd51:~#
ET9000, OpenPLi 4.0, 13E, 19E
HD51, OpenPLi 6.2, 75E - 30W
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users