Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

VU+ Solo 2 - VIX image Hades / VIX 3.2 - Crashing

  • Thread starter Thread starter scar0x
  • Start date Start date
Status
Not open for further replies.
CCcam 2.3 I think it is.

also is one of the feeds down its showing no plugins to download.
Please continue testing with the Hades image.

According to your logs your box is low on memory. Set up a swap file and report back how you get on.
 
You think??? How do you expect anyone to reproduce an issue with so little info & so little effort on your part.


Please stick to the thread topic, this thread has already gone too far off track to follow properly.

Pardon? im completely new to this im 99.9% sure it is i just couldn't remember at the time. I have re flashed already to new vix image 3.2.16 and its been fine for about 15 hours now.

What is a swap file? if the box stays fine now for another 7 hours or so i will install soft cams cccam 2.3 as this is the longest the box has gone without crashing.

The time i had it running hades it crashed and wouldn't let me ftp into the box or anything.
 
How old is your Duo?
Is it 100% genuine?
Can you try re-flashing again, this time adding a swap file. Blue button > ViX > Swapfile manager.

The box is just over a year old 1n half at most. and what is a swap file ? I have just re flashed my box again and left it without anything extra.
 
You didn't answer is it 100% genuine? Where did u purchase? This may have bugger all to do with vix, you could have a faulty receiver.


Sent from my iPhone using Tapatalk
 
You didn't answer is it 100% genuine? Where did u purchase? This may have bugger all to do with vix, you could have a faulty receiver.


Sent from my iPhone using Tapatalk

I bought from ebay from a place called rainbow computers, 100% genuine. How can they be faulty now both at the same time? i bought two vu duo boxes and they have both done the same since the updates around 3.2.09/ 3.2.10. they have worked perfectly fine for a year and a half i purchased these 9th june 2014. and only two weeks ago i have had a problem.
 
The Duo is one of the most commonly cloned receivers there is and a lot of sellers claim to sell originals when in fact they are clones, regardless of that If I were you i'd stick to slightly older images for the Duo as its getting on in years now (it's over 5 years old and thats a lot in tech terms) and it just does not handle the newer images that well any more.

in fact i'm amazed image teams are still pushing images for this box, if it were from any other manufacturer support would have been dropped a long time ago by at least three quarters of image teams.
 
Let's look at the bigger picture here, there's probably hundreds, if not thousands of duo owners using openvix, how many other duo owners do u see posting the same issue? I personally have an old duo on test with zero issues. So at some point we have to say it's either something your doing or your receiver is faulty. Pointless this thread going round in circles.


Sent from my iPhone using Tapatalk
 
The Duo is one of the most commonly cloned receivers there is and a lot of sellers claim to sell originals when in fact they are clones, regardless of that If I were you i'd stick to slightly older images for the Duo as its getting on in years now (it's over 5 years old and thats a lot in tech terms) and it just does not handle the newer images that well any more.

in fact i'm amazed image teams are still pushing images for this box, if it were from any other manufacturer support would have been dropped a long time ago by at least three quarters of image teams.

So what would you suggest to do now then ? as im out of ideas it seems strange how it can work one minute then all of a sudden not....
 
Its using your hard drive/usb stick as virtual memory. The Duo has limited memory and even downloading epg data can crash the box without a swap file.
 
After extensive hours of testing I've managed to constantly replicate this issue with a Duo2. Duo2 connected direct to Asus Router experienced the crash described in this thread. Connected through a network switch no issue found. Tested this on two differant networks, other network had a Buffalo router.

What a switch does, is only let network traffic through that is specific to the device.

A router on the other hand works like a network hub and lets all traffic reachall devices, and the individual devices each have to filter the entire network traffic to find packets that correspond to the device.

So one of two things, either there is something on that network producing packets that are not compatible with the Duo2, or the Duo2 is simply not capable of handling the volume of trafic that is flowing through the network.

Thanks go to Huevos for the info above.

So anyone having this issue best invest in a network switch.
 
Good job, finally something positive.

I've just installed a switch and OpenVPN and wait and see what happens just to validate in my case.

Now I want to go a step further and ask:
1) Is it normal for a box to crash on a few packets on a very small network on which all other devices are running flawlessly?
2) Couldn't be the box network drivers having some problem?
3) When were the network drives updated for the last time?
4) Couldn't be an OE core problem?
5) Couldn't be a Vu+ drivers problem?

What I can say is that the problem happens also with Black Hole and OpenPLI, even if it traduces differently probably because of differences in error handling.
 
Good job, finally something positive.

I've just installed a switch and OpenVPN and wait and see what happens just to validate in my case.

Now I want to go a step further and ask:
1) Is it normal for a box to crash on a few packets on a very small network on which all other devices are running flawlessly?
2) Couldn't be the box network drivers having some problem?
3) When were the network drives updated for the last time?
4) Couldn't be an OE core problem?
5) Couldn't be a Vu+ drivers problem?

No idea to all your questions if I'm being honest. I've seen the same crash reported on Solo2, Duo2, Zero and Xpeed LX2 by only a few users.

One thing you could do your us if you have time, connect the Duo back to your router. Disconnect ALL other devices from your network and see if you get a crash with the Duo being the only device connected to your router. If it don't crash, connect 1 device at a time back. This would tell us if it simply don't like your router.

What I can say is that the problem happens also with Black Hole and OpenPLI, even if it traduces differently probably because of differences in error handling.

Good to know, thank you.
 
I tested this in the past and yesterday again: nothing in the network but the box and it also crashed.

But this doesn't means the router is crashing the box... A network cannot crash a device (excluding hardware). If the device crashes is because the device does not process the packets and/or errors correctly.
This doesn't seem to be a specific OpenVIX problem because as reported I get crashes with BH and OpenPLI (their crash logs also shown they couldn't find something in /tmp/).
And what is common to OpenVIX, BH and OpenPLI?: Core and drivers.
 
Crashed with an external switch.
I've just verified in specs but my router (as all modern routers) has already its ports switched (integrated switch).
 
Status
Not open for further replies.

OpenViX Feeds Status

Back
Top