12 replies to this topic

[nautilus7]

Hi, I have an Xtrend 4000 using openpli software.

 

I have been using openpli since I bought the receiver 1,5 year ago. My setup/installation is a disecq motor, so in tuner configuration I have set "advanced"  with several satellite positions set to disecq 1.2 with usals or or off depending the position.

 

Everything was working just fine. Since last month or two my receiver froze and would not start up again, no matter how many times i rebooted it. Everytime it seems to reboot, load pli etc, but just at the time it is about to tune to the the last channel, it freezes again. And again, and again after every reboot. Only way to overcome this freezing is to re-flash the image! After reflashing, everything is working fine until one day it 'll  freeze again and only a re-flash would overcome the freezing. These 1-2 months I have flashed the receiver 3-4 times...

 

At first I was not able to figure out what was the cause of this issue. I suspected a hardware issue. But then I found this: http://www.xtrend-al...ration-problem/

 

It seems that this is the situation with me aswell. When my receiver is tuned at an horizontal freq transponder and I make a reboot, it will freeze and only reflashing would heal it. If last tuned channel is in vertical freq transponder and I make a reboot, it will start up fine.

 

Seems like there's a tuner driver related update that was done in these last one or two months that causes this issue. Last flashed image in my receiver is dated 2 days ago. I am going to flash todays image now, since it's frozen again. So the problem is still there.

 

[nautilus7]

Hi, why isn't anyone from the pli team concern by this problem? It's clearly a bug introduced during the last months. Something has to be done. Please!

[Frenske]

Hi, I assume that the cause of your problem is local. Otherwise more users would have experienced identical issues and they would have put a message too. In case it is a tuner driver related issue, you should contact Xtrend. As you know we do not develop the drivers. I'm sorry I haven't got any better news.

Hi thanks for your report
I will try to replicate the issue if successful I will send the report to driver engineer

The problem should be known by Xtrend.

[Erik Slagter]

Either that or a hardware defect.

[bril]

You can also try to disconnect the power line for a few seconds, that was helping me if the device gives to low lnb values.

Looks like the memory is not reset complete or some hardware parts are still locked with only reboot.

Edited by bril, 24 February 2015 - 14:41.

[nautilus7]

Hi, thanks for the answers guys.

 

I don't believe this is a local issue. Maybe it is caused only in advanced configuration. Perhaps many users have xtrend 4000, but not much have set it with advanced conf?

 

I made this issue known to you (openpli team) because i thought that you- despite you don't make the drivers - have open communication with xtrend (for getting new drivers, support, etc).

 

Anyway, i ll try to contact xtrend. Do you have a mail or something?

[birdiebnl]

Hi, thanks for the answers guys.

 

I don't believe this is a local issue. Maybe it is caused only in advanced configuration. Perhaps many users have xtrend 4000, but not much have set it with advanced conf?

 

I made this issue known to you (openpli team) because i thought that you- despite you don't make the drivers - have open communication with xtrend (for getting new drivers, support, etc).

 

Anyway, i ll try to contact xtrend. Do you have a mail or something?

 

Hello,

 

same problem here with my xtrend et4000, since end 2014/ begin 2015.

 

Do you have any solution yet? Just had to reboot mine yesterday, and have to flash it again.

[birdiebnl]

 

Hello,

 

same problem here with my xtrend et4000, since end 2014/ begin 2015.

 

Do you have any solution yet? Just had to reboot mine yesterday, and have to flash it again.

 

 

Fixed it without flashing. Power on the et4x00, then try to telnet to the box before it freezes. After logging in, just give "init 4", to prevent enigma from starting.

Then go to /etc/enigma2 and edit (vi) the file "settings".

Remove the line beginning with "config.tv.lastroot".

 

Give "init 3", and engima starts without any problem.

[WanWizard]

That config key only defines the default bouquet as far as I can see. It would be a serious bug if that would cause it the freeze?

That would also mean all boxes would freeze as soon as you replace a setting list causing this entry to point to a non-existing bouquet?

[birdiebnl]

That config key only defines the default bouquet as far as I can see. It would be a serious bug if that would cause it the freeze?

That would also mean all boxes would freeze as soon as you replace a setting list causing this entry to point to a non-existing bouquet?

 

My fault.... It is the config.tv.lastservice line.  (Is there a way to edit the post?)

 

Problem is that the box freezes when it it is tuned to a horizontal polarized service directly after booting.

By removing the config line, that won't happen.

I've now also set a startup channel which isn't horizontal polarized, so hopefully that is a workaround for the problem.

Edited by birdiebnl, 29 January 2016 - 12:39.

[WanWizard]

Same comment, still very weird that a box would freeze because of that, so if that is a bug it must be looked at.

[patzi]

This problem has existed since 2015. When using usals Xtrend 4000 freezes . I am forced to use the old image of 2014. There is a problem with your open ATV and ETC...Help

[Erik Slagter]

And what would you like us to do about it? It has already been reported to Xtrend.