79 replies to this topic

[athoik]

Is is so hard to run it once and confirm that it fixes your problem?

Tommorow, i guess images will become available that contain the fix. No need for script.

[fidelcastro54]

Sorry for the question. ???? But how should i know that the fix is in the update tomorrow? It was only a question. ????

[athoik]

If there is an update, and images on site.

Today build server had an issue.

But the question remain, the echo commands fix the problem temporarily?

[arshavir]

In the meanwhile the following commands should fix the issue with A on input 3/4.
 

echo -n C >  /proc/stb/tsmux/input2
echo -n D >  /proc/stb/tsmux/input3

PS. The drivers expect from Enigma2 to initialize to correct input 0->A 1->B 2->C 3->D. It seems that they default to A.

 

YES, I confirm, it working now with these echo commands, thanks again

[athoik]

In the meanwhile the following commands should fix the issue with A on input 3/4.

echo -n C >  /proc/stb/tsmux/input2
echo -n D >  /proc/stb/tsmux/input3

PS. The drivers expect from Enigma2 to initialize to correct input 0->A 1->B 2->C 3->D. It seems that they default to A.

YES, I confirm, it working now with these echo commands, thanks again

Nice, as it was expected.

Once updates become available they will fix the issue. Until then, use the echo command to set the correct input.

[ghuss]

In the meanwhile the following commands should fix the issue with A on input 3/4.
 

echo -n C >  /proc/stb/tsmux/input2
echo -n D >  /proc/stb/tsmux/input3

PS. The drivers expect from Enigma2 to initialize to correct input 0->A 1->B 2->C 3->D. It seems that they default to A.

 

YES, working after applying the commands.

 

Thank You very Much

[dragnan]

I'm back from my vacation and updated. Now it works perfectly again. Thanks

[fidelcastro54]

I'm back from my vacation and updated. Now it works perfectly again. Thanks

I've got this issue again with update from 21.4. and vu+ duo2 and the commands doesn't work after reboot. Then it is ABAA again.

Gesendet von meinem SM-T813 mit Tapatalk

Edited by fidelcastro54, 21 April 2017 - 21:35.

[athoik]

Yes, its only VU+ again!!!


What the following command returns?

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

[fidelcastro54]

root@et8000:~# 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@et8000:~#

Gesendet von meinem SM-T813 mit Tapatalk

[athoik]

Ok its et8000! I thought it was VU+ because previously VU+ suffered from an issue with tsmux.

Anywy the input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.

/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

A simple solution is to initialize them manually.

echo -n C >  /proc/stb/tsmux/input2
echo -n D >  /proc/stb/tsmux/input3

Manufaturer should add input2_choices and input3_choices nodes.

If it takes too long for manufacturer to fix, the solution is to create a script that will initialize them.

Anyway the echo commands, solve the issue?

[fidelcastro54]

No. Its vu+ duo2. Its a wrong name. The commands fix the issue until i restart. Makes a sense to write a permanent script in openpli because the issue is the second time?

Gesendet von meinem SM-T813 mit Tapatalk

Edited by fidelcastro54, 21 April 2017 - 21:59.

[fidelcastro54]

How can i change the name?

Gesendet von meinem SM-T813 mit Tapatalk

[athoik]

I think you should workaround the issue, the tsmux handling should be one and followed by all.

Add the following into a file named fixin.sh and place it in /etc/init.d/

#!/bin/sh

echo -n C >  /proc/stb/tsmux/input2
echo -n D >  /proc/stb/tsmux/input3

exit 0

Then type the following to automatically start

update-rc.d fixin.sh defaults

[fidelcastro54]

Is this still available after a later update?

Gesendet von meinem SM-T813 mit Tapatalk

[athoik]

It will remail available as long as you don't reflash.

At least we know that vuduo2 doesn't have choices nodes although expects something.

[fidelcastro54]

Thx. It works. Will there be a fix in a future Update?

Edited by fidelcastro54, 21 April 2017 - 22:22.

[athoik]

I guess the manufacturer should be informed and aksed to add missing inputX_choices.

Adding workarounds to Enigma2 is something we are trying hardly to avoid.

[fennec]

Ok its et8000! I thought it was VU+ because previously VU+ suffered from an issue with tsmux.

Anywy the input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.
 

/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

A simple solution is to initialize them manually.

echo -n C >  /proc/stb/tsmux/input2
echo -n D >  /proc/stb/tsmux/input3

Manufaturer should add input2_choices and input3_choices nodes.

If it takes too long for manufacturer to fix, the solution is to create a script that will initialize them.

Anyway the echo commands, solve the issue?

 

Thanks a lot !!!!

[fidelcastro54]

@athoik
I guess thats the best solution, but will it be permanent then?

Gesendet von meinem SM-T813 mit Tapatalk