Er zijn 12 reacties in dit onderwerp

[BoxFreak]

Hello,

I have tried to follow the [NL] thread of htis issue, but with google translator its bit difficult. I am suffering from the driver
issue (Stuck when timed recording is supposed to start with 0 size file in internal disk). Could someone make an short english update on the issue? I noticed some workarounds that were tried, but I am not quite sure of the results. Also someone was mentioning older drivers that could work better, if it is so then I would very much like to try those (where to find them and how to install?).

Thanks in advance for the information.

[Trial]

Hi,
for older driver you need an image with kernel 2.6 which must be dated around november or start of december last year.

ciao

[Pedro_Newbie]

To be short. Some people are suffering with freezing VU+ Duo's, others have no problem at all. The problems seems to be caused by a memory leak in the drivers. Having an internal harddisk in the Duo seems worsening the problem. There were some workarounds of which preserving/reserving some memory. This helps a little, I personally don't have too much trouble any more.
An trouble free release is the release of 28-12-2011 with the old kernel. It can be downloaded here on the board at: http://downloads.pli...0111228_usb.zip
VU+ is working (they say) on the problem but it is very quit and still no news from Korea.

[BoxFreak]

Thanks for the update. Would not want to go for old 2.6 kernel anymore. So could you tell those workarounds that help the situation? While waiting for Vu to correct the leaking drivers.

[Pedro_Newbie]

The workarounds aren't solutions but, in my case, helps prevent the VU+ freezing in most cases. Why don't you want to use the old kernel, this kernel works without any freezes?
One workaround is to give the following commands in telnet

echo 'vm.min_free_kbytes=8192' >> /etc/sysctl.conf
and
echo 8192 >> /proc/sys/vm/min_free_kbytes

another one is to load a minimum of EPG data

[malakudi]

If there is memory leak in the VM space, does the usage of a swap file help?

[littlesat]

does the usage of a swap file help?

A swap file may slow down your box... and will delay the time of the issue...

[Trial]

Hi,
has anybody tried rebooting the box on a regular basis? I have programmed several timer.
1. set my box in deepstandby at 1:30am
2. set my box to standby at 6:45am
3. set my box to deepstandby at 7:45am
4. set my box to standby at 4:45pm

If it help it also has the bennefit that you save around 104KWh whith the equivalent of €26/year in Germany.

ciao

[Rob van der Does]

Or use the auto standby plugin for that.
But as to the original problem: that also is only a work-around a bug, not a solution.

[BoxFreak]

Why don't you want to use the old kernel, this kernel works without any freezes?

Well because it would mean reflashing and setting up the box with DVB-T USB stick that needs manual installation... and to do it again after the fixed drivers are available i.e. simply because I am lazy . Also I dont see the kernel 2 base OpenPLi updated anymore for Vu+ DUO, no new builds since december 2011.
Thanks for the workarounds, will try to survive with those.

[pop_eye]

You could try following version - which is working satisfactory with internal EPG and usbtuner.

A friend of mine which had problems with Samsung 3D Plasma 51"  told me his issues were solved with this one.

Previous drivers were not detecting it properly @60Hz over the HDMI connection.

 

20130111
 - Fix CI problem in dual tuner(ultimo)
 - Support bypass edid
 - Improve graphics2D
 - Support hardware audio PCM codec(will be used in the upcoming new OE)
 - Fix EOS detection in media playback

20130125
 - Improve vtuner performance.
 - Fix USB DVB-S/S2 vtuner lock failure problem.

 

http://archive.vuplu...20130125.tar.gz

Veranderd door pop_eye, 9 juli 2013 - 18:18

[BoxFreak]

Thanks pop_eye, but the problems were back in 2012 (as can be seen in post    ) no need to restart anymore this old thread. Works even with the latest drivers....

[pop_eye]

You are welcome, I only mention it because of similar issues experiencing and was not finding solution until this year with the HDMI. Someone will maybe use it.