[VU+ Duo] What image are you using during vix period of instability

[zola25]

From what i can see from other forums and my two it seems to be the earlier duos that seem to suffer from the memory leak, i have one from 2010 which is totaly unstable on the newer linux kernel and one from then end of 2011 which is fine.
I just hope they fix the memory leak in the older models and dont just write them off out of interest anyone got any news if the latest betas are making any progress on the memory leak?

 

[Larry-G]

Would it be different versions of DUO.
Mine is Feb 2010.

No idea what date mine Is but I do know it has a v1.3 motherboard. The new ones are v 2.4 I think

 

[andys0506]

Interesting that this memory leak appears to just affect the early models.
I have recently bought a Duo from the site sponsors and its pretty unstable on 3.1.1 build 204.
Added a swapfile which has helped a bit but looking at reverting back to build 133 now.

Now there's no way that the site sponsors would have shipped me an old Duo surely

 

[Rob van der Does]

Would it be different versions of DUO.

No: the affected boxes stem from all H/W-revisions.

 

[dfdream]

Thanks Rob for the Update.

But thats all it takes from a manufacturer who has built up a good reputation to bring out software with these issues and then leave the users in deep Sh*t.
Its 6 months now since this issue was first noted and VU havent done anything.
When VU hit the scene first (when I got mine) they were super helpful and solved issues quickly.
Those days are gone....RIP....

No: the affected boxes stem from all H/W-revisions.

 

[Larry-G]

Thanks Rob for the Update.

But thats all it takes from a manufacturer who has built up a good reputation to bring out software with these issues and then leave the users in deep Sh*t.
Its 6 months now since this issue was first noted and VU havent done anything.
When VU hit the scene first (when I got mine) they were super helpful and solved issues quickly.
Those days are gone....RIP....

I would in no way say that, YES Vu are aware of the problem and are doing their best to remedy it, and to be honest it affects a very small number of Duo's and again it's not even version specific. You have to remember these boxes were never built for the 3.1.1 kernel, which in it self is a very new development for use with STB's but users will always clamour for new features and improvements then complain when things dont quite go their way. I have no doubt it will be fixed it's just a waiting game until then.

 

[andys0506]

Well just to report I went from the unstable 204 to 133 last night, and could not mount the hdd or usb, no matter what I did. As luck would have it the latest OpenVix build came out last night so I went for broke and flashed that one. So far so good...

 

[zola25]

The one thing with 133 is if you changed your HD and USB to ext4 the old kernel can not read it so you need to reformat it to ext3 again which means you loose all your recordings unless you copy them somewhere else first.
I am now going to try the newest ViX so fingers crossed it helps with my instability and i dont have to wait for VU to fix the memory leak

 

[andys0506]

Ah that explains it!

 

[dfdream]

Andy keep us updated on how it goes.
I wont be upgrading till next week so hopefully any issues will be to the fore by then.

Well just to report I went from the unstable 204 to 133 last night, and could not mount the hdd or usb, no matter what I did. As luck would have it the latest OpenVix build came out last night so I went for broke and flashed that one. So far so good...

 

[andys0506]

All pretty good so far. Is much more stable. In 204 the box ground to a halt whenever I tried to go through the EPG, now works a treat.
I would defo recommend you give it a try. Remember that you can't restore your settings though, you need to setup from scratch after flashing.