42 replies to this topic

[KvM1950]

It's now the 14th of July and I still have this problem.

 

I don't think it's not the manufacturer who has to solve the problem.

 

I've got no problems with original Vu+ and VTi software, so it's a bug or whatever in Open PLi.

[WanWizard]

No.

 

It is a bug in de VU+ drivers. Which VU+ has to fix in their BSP, we don't manage that (we don't even have access to it).

 

The reason that VU+ doesn't have the issue is that they've worked around their own bugs in their Enigma version. They always do. And VTI is a VU+ copy. We don't do that, and we can't, it would break the image for all other brands.

 

To help you, we have published a workaround as well (see https://forums.openp...e-3#entry701207), that is not dependent on hacks in Enigma. Install it to fix your problem.

[ROMAN42]

Hmmm    so finally somebody explain this annoying issue , i have to try it but i think that should be clear marking last working version PLI and still available to download.Not anyone right now will be doing this workaround So VU+ doesn't care for your clients ???

[WanWizard]

Appearently not. They already have your money.

 

We've been pushing them to fix it, and will continue to do so. 

[ROMAN42]

If the don't, i 'll never buy Ultimo 4K

[WanWizard]

Usually eventually it happens, but they aren't the quickest in their response.

 

Maybe because unlike most manufacturers, VU+ spends development effort on an own image, and maybe they prefer that you use that. Having said that, there are manufacturers that don't support open images at all...

[athoik]

I don't think that Ultimo4K suffers from that issue!!!

Also there are new drivers from Vu+ that fix the problem (yes new drivers, you hear well), but unfortunately not in OpenPLi BSP layer yet.

[ROMAN42]

Vu + own image IMO is verv very silly and lack many needful things and nobody  buy that receiver.Only open software's made by the teams make those tuners top over silly, hopeless receiver's deliver by pay operators .As long user ( 7 years) of Humax Icord HD , must say that software was very good and only two things like: to little sat positions and lack of multi stream decoding , was annoying, rest was very useful.Drivers problem ? any of that

Edited by ROMAN42, 14 June 2017 - 17:34.

[Teesi]

On Ultimo, openpli 6.0 (2017-12-11) (yesterday, newest), this problem is back:

 

openpli 6.0-release vuultimo

vuultimo login: root
Password:  
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:~# date
Tue Dec 12 10:55:23 EET 2017
root@vuultimo:~# 

 

 

 Using more than two tuners causes total system freeze.

[WanWizard]

That can't be related to yesterday's build, that was just an updated of the tuxbox and the hanssettings list.

 

I've checked, the VU+ BSP in 6.0-release is over 2 months old. The Ultimo drivers in that BSP as from 24/11/2015. Besides, this issue was specific to the Duo2, so it must be something else.

[Teesi]

Problem is specific to duo AND ultimo. Months ago a fix was given for both separately.

 

I have had freezes since many days and a couple of updates. (When Openpli 6.0 first came out, this worked. (I think.))

 

Clearly tuner C is uninitialized.

[WanWizard]

For the Duo2, it was fixed by VU+ in the drivers. Clearly there hasn't been a driver update for the Ultimo since 2015.

 

I think you'll have to wait for Athoik to respond, he knows a lot better what is going on than I do.

[Teesi]

Allright, this is not the reason. 

 

Now the ultimo froze even after 

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

Now I do not know what to do.

 

I must go now.

[echolite]

Hello All.. 

 

the PLi 7.0 RC has this issue again, with duo2    DVBT  is not on D  but shows on C-    i try the solutions above, and from other forums- useless..   

 

Just an info. 

 

T.

[WanWizard]

What is again? Where was this reported earlier?

 

The issue about with the Duo2 (for which the above applies, is for missing both C and D tuners, regardless of the type).

 

You seem to have a different issue. A Duo2 has three tuner slots and support a maximum of 4 tuners, what is your specific setup? Which tuners in the box? What kind of DVB-T tuner is this? 

[Abu Baniaz]

Duo 2 actually has two tuner slots. The third is just a blank because they used the same casing as Ultimo.

There have been odd posts by people where it is finally established that the tuner card is faulty. Hardware issue, not software.

Sent from my Moto G (5S) using Forum Fiend v1.3.3.

[WanWizard]

Lol, I didn't actually check. I should have known, I recently removed the dual tuner to add it to my Solo 4K...

[echolite]

What is again? Where was this reported earlier?

 

The issue about with the Duo2 (for which the above applies, is for missing both C and D tuners, regardless of the type).

 

You seem to have a different issue. A Duo2 has three tuner slots and support a maximum of 4 tuners, what is your specific setup? Which tuners in the box? What kind of DVB-T tuner is this? 

 

No different issue, i have a usb dvbt - RT chipset-  due that i have multiboot, i can see that its perfectly works in 6.2 pli..  it was always work with 6.xx  some 4.xx fw had a same tuner C/D issue, what i fixed trought tlenet command.  ( found here in this forum)   but unfortulatly the same old telenet scipt and drivers  ISNT work in 7.xx RC      

Somehow, the PLI solved this issue in 6.xx versions..  also working nicely in BH. .   images-   

 

Thats from me..   no special setup.    A sat  Bsat   C DVBC D DVBT (should be) but its not its remain grey.    

[WanWizard]

I only have one dual tuner for my Duo2, which I just removed from my Solo 4K and put back into my Duo2, so I now have A, B and C. Don't have anything to produce a D, but that shouldn't matter as C also doesn't work for you?

 

Just flashed the latest 7.0-rc. And C works fine here.

 

I've checked, I have no plugins running or installed related to this, and no actions done on the commandline. 

 

Are you sure it is not an issue with your USB tuner and/or driver, instead of a VU+ driver issue?

[Pr2]

... it was always work with 6.xx  some 4.xx fw had a same tuner C/D issue, what i fixed trought tlenet command.  ( found here in this forum)   but unfortulatly the same old telenet scipt and drivers  ISNT work in 7.xx RC      

...

 

Please show us which special telnet command is working in other OpenPLi versions so we can have an idea on where to look at. Or give us the link to the post on this forum.

USB tuner is always a challenge to have it working properly.

 

And how many USB tuner do you have?  A single USB tuner is either configured to work in DVB-T or in DVB-C mode, so you cannot have the same unique USB tuner configured to work both as DVB-T and DVB-C at the same time.