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

[Foxylady]

So your saying so i get my head around this,
That the BH image as correct drivers sufficient for the duo whereas the current VIX does not, and that the new VIX to be released will also?
Best wishes

 

[Rob van der Does]

That the BH image as correct drivers sufficient for the duo whereas the current VIX does not, and that the new VIX to be released will also?
Best wishes

As far as I know all images use the latest drivers (the latest VU-drivers are from 28/02).

 

[Larry-G]

Both the current ViX public image and BH are running the exact same Vu hardware drivers there is no difference here. now i dont use the BH image personally but it may be the case that they have different default settings which may lead to a difference in observed PQ. I will however agree with Rob that it is impossible to have so drastic a difference as some claim when all images use the same hardware drivers and the BH team will and have said the exact same thing them selves on many occasions.

 

[pr1s0m]

If im using a ET9000 with latest vix, am i able to sample other images? as im sure i read somewere on here once kernel changed i cant go to any other image!!

Thanks for any info

Over past few weeks ive tried nearly every image out there openpli , open aaf, dbuk and im trying the new XTR 1.0 experimental from rossi2000 at the minute thats using 3.3 kernel and i can flash my vix backup when ever i want with no problems

 

[Braggster]

Over past few weeks ive tried nearly every image out there openpli , open aaf, dbuk and im trying the new XTR 1.0 experimental from rossi2000 at the minute thats using 3.3 kernel and i can flash my vix backup when ever i want with no problems

Thanx a lot for the info m8 any tips on images u been sampling, that your impressed with?

 

[fmlm2001]

Moved from Vix to Blackhole 1.7.3 for VU+ Duo today so far all good

 

[gordyboy]

its a no brainer as I see it. if you are running vix like I was and you are getting constant crashing, recording problems them move to another image, why would you put up with the hassle. Once vix is sorted move back if you want.

 

[andys0506]

Moved from Vix to Blackhole 1.7.3 for VU+ Duo today so far all good

Thinking of doing the same. Is the interface similar? Worried it might not be 'spouse friendly'. I've heard that the epg is not as good?

 

[zola25]

Thinking of doing the same. Is the interface similar? Worried it might not be 'spouse friendly'. I've heard that the epg is not as good?

While we all wait semi patiently for the new ViX image just go back to ViX-2.3.133 it is rock solid and all the menus will be the same for the wife

 

[fintannl]

have sat on image zola says above and its perfect. never did upgrade to the christmas version of vix because of the problems encountered. very happy with my current version of VIX and the only issue I have is the necessity to reboot every couple of weeks as when switching between bouquets/channels the VIX spinner becomes evident. The reboot solves the problem. Waiting for new version of VIX patiently

 

[andys0506]

Do you mean 153, cant find 133?

edited: sorry just found it, but notice it uses the earlier kernel.
Do I need to flash the kernel back to 2.6 from my current 3.1.1.

Out of interest I'm guessing 153 is no better than 204, is the issue the new kernel rather than the image build?

 

[dfdream]

Andy is this what you are looking for.. This is the previous version to the current one.
I have gone back to this one from the current one on my DUO and its solid as a rock. Zero reboots, freezes or lockups.
It looks identical to the latest version. I have the latest version on SOLO and its 110% perfect... So I cant explain why the current version is fine on SOLO but not on the DUO.

http://www.world-of-satellite.com/showthread.php?13173-ViX-Team-Vu-Duo-Image-v2-3-19-10-2011

You need the ViX-2.3.133-vuduo_usb.zip file....

Do you mean 153, cant find 133?

 

[dfdream]

Andy all you need is to load the ViX-2.3.133-vuduo_usb.zip file.
You dont need to do anything else.
D

Do you mean 153, cant find 133?

edited: sorry just found it, but notice it uses the earlier kernel.
Do I need to flash the kernel back to 2.6 from my current 3.1.1.

Out of interest I'm guessing 153 is no better than 204, is the issue the new kernel rather than the image build?

 

[andys0506]

Thanks dfdream Out of interest whats the difference between the 133 file and the GM file?

 

[dfdream]

Dont know. Sorry

 

[Larry-G]

So I cant explain why the current version is fine on SOLO but not on the DUO.

because only the Duo seems to be suffering from the memory leak problems associated with the 3.1.1 linux kernel.

 

[Larry-G]

Thanks dfdream Out of interest whats the difference between the 133 file and the GM file?

GM stands for golden master which is a generic term used by programmers to basically say that their software is now out of the beta testing phase and suitable for the public market, build 133 is a later updated version of that same image but includes all of the fixes and updates that were produced upto that point. build 133 was also the very last linux kernel 2.6.18 image we produced and so will not be updated any longer due to the inability to use the newer linux kernel 3.1.1 hardware drivers etc.

 

[andys0506]

because only the Duo seems to be suffering from the memory leak problems associated with the 3.1.1 linux kernel.

so the issue is related to the 3.1.1 kernel rather than the image itself?

 

[Larry-G]

so the issue is related to the 3.1.1 kernel rather than the image itself?

some Duo's are suffering from memory leak problems which only seems to affect the Duo, now i am in no way saying that all duo's are having these troubles as my own works fantastically on the newest images.

 

[dfdream]

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

some Duo's are suffering from memory leak problems which only seems to affect the Duo, now i am in no way saying that all duo's are having these troubles as my own works fantastically on the newest images.