79 replies to this topic

[athoik]

What is permanent in this world?

[fidelcastro54]

I know, but dreaming is allowed.

Gesendet von meinem SM-T813 mit Tapatalk

Edited by fidelcastro54, 22 April 2017 - 08:40.

[athoik]

Can you try to install those two ipk and see if input2/3_choices now created?

Place them on /tmp and install them like that:
 

cd /tmp
opkg install *.ipk
reboot

Then after reboot provide the following command again.
 

grep -r "" /proc/stb/tsmux/

Attached Files

•  boxinput_1.0-r0_vuduo2.ipk   724bytes   311 downloads
•  kernel-module-boxinput_1.0-r0_vuduo2.ipk   2.34KB   225 downloads

[fidelcastro54]

What about the script? Should i delete it?

Gesendet von meinem SM-T813 mit Tapatalk

[athoik]

No script reuired with above "trick".

Edited by athoik, 22 April 2017 - 17:00.

[fidelcastro54]

OK. Script ist deleted and your fix is working!

 

 

openpli 4 VUDUO2

root@VUDUO2:~# cd /tmp
root@VUDUO2:/var/volatile/tmp# opkg install *.ipk
Installing boxinput (1.0-r0) on root.
Installing kernel-module-boxinput (1.0-r0) on root.
Package kernel-module-boxinput (1.0-r0) installed in root is up to date.
Configuring kernel-module-boxinput.
Configuring boxinput.
root@VUDUO2:/var/volatile/tmp# reboot

Broadcast message from root@VUDUO2 (pts/0) (Sat Apr 22 17:59:57 2017):

The system is going down for reboot NOW!
root@VUDUO2:/var/volatile/tmp#

openpli 4 VUDUO2

root@VUDUO2:~# grep -r "" /proc/stb/tsmux/
/proc/stb/tsmux/input3_choices:FIXME!
/proc/stb/tsmux/input2_choices:FIXME!
/proc/stb/tsmux/input1_choices:CI0 CI1 A B
/proc/stb/tsmux/input0_choices:CI0 CI1 A B
/proc/stb/tsmux/input3:D
/proc/stb/tsmux/input2:C
/proc/stb/tsmux/input1:B
/proc/stb/tsmux/input0:A
/proc/stb/tsmux/ci1_tsclk_choices:normal high
/proc/stb/tsmux/ci0_tsclk_choices:normal high
/proc/stb/tsmux/ci1_tsclk:high
/proc/stb/tsmux/ci0_tsclk:high
/proc/stb/tsmux/ci1_input_choices:CI0 A B
/proc/stb/tsmux/ci0_input_choices:CI1 A B
/proc/stb/tsmux/ci1_input:A
/proc/stb/tsmux/ci0_input:A
root@VUDUO2:~#

 

Will this be used in future updates to avoid the problem?

Edited by fidelcastro54, 22 April 2017 - 17:07.

[julion]

Can you try to install those two ipk and see if input2/3_choices now created?

Place them on /tmp and install them like that:
 

cd /tmp
opkg install *.ipk
reboot

Then after reboot provide the following command again.
 

grep -r "" /proc/stb/tsmux/

It works on my VU+ Duo2

Thanks

Edited by julion, 25 April 2017 - 10:34.

[Peacock]

Can you try to install those two ipk and see if input2/3_choices now created?

Place them on /tmp and install them like that:
 

cd /tmp
opkg install *.ipk
reboot

Then after reboot provide the following command again.
 

grep -r "" /proc/stb/tsmux/

Worked like a charm here too. Finally!

 

Have 2x dual S2 tuners, tried everything: swapping cards, take one out, retried manual configuration endless times, etc.

AutoDiseqc just gave : Tunerstatus LOCKED and then a series of fails...

I'm just typing the stuff I tried and looked for on internet until I finally found this post... Maybe these breadcrumbs bring in more victims ;-)

 

Thanks for all the work!

[Teesi]

Same problem on Ultimo ?

(OpenPLi 4.0 (2017-04-26)) :

 

root@vuultimo:~# grep -r "" /proc/stb/tsmux/
/proc/stb/tsmux/input1_choices:CI0 CI1 A B
/proc/stb/tsmux/input0_choices:CI0 CI1 A B
/proc/stb/tsmux/input3:A
/proc/stb/tsmux/input2:A
/proc/stb/tsmux/input1:B
/proc/stb/tsmux/input0:A
/proc/stb/tsmux/ci1_tsclk_choices:normal high
/proc/stb/tsmux/ci0_tsclk_choices:normal high
/proc/stb/tsmux/ci1_tsclk:high
/proc/stb/tsmux/ci0_tsclk:high
/proc/stb/tsmux/ci1_input_choices:CI0 A B
/proc/stb/tsmux/ci0_input_choices:CI1 A B
/proc/stb/tsmux/ci1_input:A
/proc/stb/tsmux/ci0_input:A
root@vuultimo:~#

 

Can I apply the *vuduo2.ipk fixes ?

[athoik]

Hi,


Try with attached files (place under /tmp and install using opkg install *.ipk then reboot).

Attached Files

•  vuinput_1.0-r0_vuultimo.ipk   740bytes   53 downloads
•  kernel-module-vuinput_1.0-r0_vuultimo.ipk   2.3KB   47 downloads

[Teesi]

Done. (Renamed *.bin to *.ipk first.) Now:

 

root@vuultimo:~# grep -r "" /proc/stb/tsmux/
/proc/stb/tsmux/input3_choices:FIXME!
/proc/stb/tsmux/input2_choices:FIXME!
/proc/stb/tsmux/input1_choices:CI0 CI1 A B
/proc/stb/tsmux/input0_choices:CI0 CI1 A B
/proc/stb/tsmux/input3:D
/proc/stb/tsmux/input2:C
/proc/stb/tsmux/input1:B
/proc/stb/tsmux/input0:A
/proc/stb/tsmux/ci1_tsclk_choices:normal high
/proc/stb/tsmux/ci0_tsclk_choices:normal high
/proc/stb/tsmux/ci1_tsclk:high
/proc/stb/tsmux/ci0_tsclk:high
/proc/stb/tsmux/ci1_input_choices:CI0 A B
/proc/stb/tsmux/ci0_input_choices:CI1 A B
/proc/stb/tsmux/ci1_input:A
/proc/stb/tsmux/ci0_input:A
root@vuultimo:~#
 

Hmm...

"FIXME"-lines do not look nice.

And I have three tuners .

 

But I will test this. Thank You !

[Huevos]

Which commit is the one incompatible with the duo2?

[arnask]

So as i understand, this issue is not solved by VU+? We still need to install these ipk files after re-flashing?

[littlesat]

Y-E-P

[arnask]

is that something that can be added to regular updates until VU+ will fix this?

I just can't understand why we need to do some manual work for something that can be solved easily by openpli until vu will fix this

[Erik Slagter]

It's a workaround, not a fix. We're awaiting the fix from VU+.

[stick50jr]

is that something that can be added to regular updates until VU+ will fix this?

I just can't understand why we need to do some manual work for something that can be solved easily by openpli until vu will fix this

I agree that it would be nice to have a 'non - manual' work around until Vu+ fix their drivers... but that is not the way OpenPLi have worked in the past.  I think that OpenPLi would rather suffer the 'manual' workaround until a Vu+ fix arrives.  The rationale is that an automatic workaround in OpenPLi would encourage Vu+ to do nothing, and that over time other such workarounds would accumulate and make it difficult to maintain enigma2.  I can understand where OpenPLi are coming from, but it does mean that you might have to suffer the manual work around for quite a while yet.

 

(Apparently this change to enigma2 means that the DM7025 Common Interface will no longer work , such is life.  Enigma2 moves on and some boxes are left behind... hopefully not Vu+ boxes)

[arnask]

It's a workaround, not a fix. We're awaiting the fix from VU+.

ok, so implement this workaround until its fixed by VU+

i can understand your position, but end-users are suffering from this

[Huevos]

Does this output look correct? Blacked out recordings on this box.

 

sf4008 login: root
root@sf4008:~# grep -r "" /proc/stb/tsmux/
/proc/stb/tsmux/input0:A
/proc/stb/tsmux/input1:B
/proc/stb/tsmux/input2:C
/proc/stb/tsmux/ci0_input:A
/proc/stb/tsmux/ci0_tsclk:high
/proc/stb/tsmux/ci1_input:A
/proc/stb/tsmux/ci1_tsclk:normal
/proc/stb/tsmux/input0_choices:CI0 A B C
/proc/stb/tsmux/input1_choices:CI0 A B C
/proc/stb/tsmux/input2_choices:CI0 A B C
/proc/stb/tsmux/ci0_input_choices:CI0 CI1 A B C D
/proc/stb/tsmux/ci0_tsclk_choices:normal high
/proc/stb/tsmux/ci1_input_choices:CI0 CI1 A B C D
/proc/stb/tsmux/ci1_tsclk_choices:normal high
root@sf4008:~#
 

Edited by Huevos, 16 May 2017 - 08:14.

[athoik]

@Huevos,

Are you sure you have trace it down to initializing input2 with C?

Because the input2_choices name C as valid input! (although we don't validate those yet, just checking inputX_choices to initialize now inputX)