42 replies to this topic

[christophecvr]

The config setting

 

config.Nims.1.configMode=loopthrough
config.Nims.0.diseqcA=130
config.Nims.0.diseqcMode=diseqc_a_b_c_d
config.Nims.0.diseqcC=235
config.Nims.0.diseqcD=282
config.Nims.0.diseqcB=192

 

Is not reader anymore at enigma2 start.

[Beeker]

Yes indeed.

 

https://github.com/O...5532115562a97d8

 

Not good.

[christophecvr]

Indeed if I revert that commit al works back ok.

 

commit which needs to be reverted :

 

https://github.com/O...5532115562a97d8

[christophecvr]

I now builded for dm8000 and vuduo2 enigma2 with this revert patch.

 

All works back ok .

Attached Files

•  revert-tuner-config.patch   1KB   81 downloads

Edited by christophecvr, 18 December 2015 - 22:22.

[christophecvr]

Even with a fresh flash. Full new reconfigure. Same issue in despit the fact that the tuner configs are set after reboot or restart off e2

 

Message service not found check sat config.

 

User must then set tuner config then it works till next reboot or e2 restart.

 

The revert is required.

[christophecvr]

Here two enigma2 start logs on vuduo2.

 

With last enigma2 commit fe6804e83c238fc5db0cf99459f567216cdce793

 

The not ok log is like it is on the current e2 and tuner configs are NOT loaded.

Message on screen service not found , check tuner config.

 

The ok log is just same enigma2 commit fe6804e83c238fc5db0cf99459f567216cdce793.

 

But with revert commit 70745dfeb997998e02a6359cf5532115562a97d8 aplied.

 

 

Attached Files

•  e2-start-log-tuner-config-nok.txt   15.12KB   18 downloads
•  e2-start-log-tuner-with-revert-patch-ok.txt   24.47KB   18 downloads

[christophecvr]

in the above log can clearly be seen what happens. By the not ok the tuner one is set disabled.

<   398.558958> [eDVBFrontend] setSlotInfo for dvb frontend 0 to slotid 0, descr Vuplus DVB-S NIM(AVL6222), need rotorworkaround No, enabled No, DVB-S2 Yes
<   398.559271> [eDVBFrontend] setSlotInfo for dvb frontend 1 to slotid 1, descr Vuplus DVB-S NIM(AVL6222), need rotorworkaround No, enabled Yes, DVB-S2 Yes

By the second log with just the revert the tuner is set as enabled like it should and is.

<  1063.589814> [eDVBFrontend] setSlotInfo for dvb frontend 0 to slotid 0, descr Vuplus DVB-S NIM(AVL6222), need rotorworkaround No, enabled Yes, DVB-S2 Yes
<  1063.590094> [eDVBFrontend] setSlotInfo for dvb frontend 1 to slotid 1, descr Vuplus DVB-S NIM(AVL6222), need rotorworkaround No, enabled Yes, DVB-S2 Yes

lines 94 95 in log.

 

same issue by dm8000.

[Erik Slagter]

I think the actual problem is that enigma2 only writes entries in the log that differ to the default. Now if you change the default and you don't modify the settings accordingly, enigma2 will use wrong values for entries that are left out of the config (because they were equal to the default). So if you have tuners set to "simple" they now will  be "nothing connected".

 

I still the support the patch from dimitrij, but it needs a workaround for this effect.

[christophecvr]

In the mean time already 5 persons hit dreambox and vu+

 

This list will grow pretty fast now depending when users upgrade there stb system.

 

Perhaps it's maybe happening if You use more the 1 lnb but I Do not think thats the case.

 

At this time it's a real blocker (higher then a severe bug ) just simply unusable.

[Pedro_Newbie]

I updated this morning and I have (had) also this issue on a Solo2 and an ET8000. My config is simple:

A nothing connected

B 28.2

C 23.5

D 19.2

 

Until it is solved I restored my back-up from last night

[charlesduco]

Same problem on Vu+ Duo.
Many thanks to christophecvr for the patch.
 
 

At this time it's a real blocker (higher then a severe bug ) just simply unusable.

+100000000000000000000000000

[christophecvr]

Yes the list grows and now also by et which seems logic to me the

 

commit 70745dfeb997998e02a6359cf5532115562a97d8 just request nothing and then you have nothing.

[athoik]

>>> def safeint(val):
... try:
... val = int(val)
... except:
... val = 0
... return val
...
>>>
>>>
>>> safeint("simple")
0
>>> safeint("123")
123
>>> safeint("")
0

if len(nimmanager.getTransponders(safeint(self.tuning_sat.value))) < 1: #

Or just..
 

if len(nimmanager.getTransponders(self.tuning_sat.value and self.tuning_sat.value or 0) < 1: #

Anyone can confirm?

Edited by athoik, 19 December 2015 - 11:28.

[christophecvr]

which modules and where in the module ?

[dog-man]

I have the same issue on my vuduo after just updating.

 

So, is there a fix I can apply available yet?

 

Was hoping to watch some football this afternoon.

[Beeker]

I have the same issue on my vuduo after just updating.

 

So, is there a fix I can apply available yet?

 

Was hoping to watch some football this afternoon.

 

Just restore your setting in tunerconfiguration after a restart enigma/reboot for the time being.

[Dimitrij]

You just have to set the settings again.
This is done once and for all.

[christophecvr]

You just have to set the settings again.
This is done once and for all.

Now after each reboot or e2 restart You need to set tunerconfigs again.

 

unless commit :

https://github.com/O...5532115562a97d8

 

is reverted.

[Dimitrij]

Default value 'simple' and not satellite(s) is nonsense.

[Dimitrij]

I got it.
Erik please revert this.
I'll find another way.