38 replies to this topic

[atilaks]

I have the following problem. When I try to watch a "still in progress" recording (dvb-s2) I get a message "No data on transponder. Timeout reading PAT". Playback is choppy (enigma2 displays spinner for 1-2 secs from time to time). When watching the same recording, after recording is finished playback however is ok.

There is nothing relevant in the log file...

eHdmiCEC: received message
main thread is non-idle! display spinner!
eHdmiCEC: received message
main thread is non-idle! display spinner!
main thread is non-idle! display spinner!
main thread is non-idle! display spinner!

[Erik Slagter]

What box?

[pieterg]

which box?

[Erik Slagter]

lol...

[atilaks]

vuduo newest openpli

edit:
I try to debug it, because it does always happen on the same scheduled recording, but I can't see the problem on other channels...

Edited by skalita, 19 April 2012 - 18:00.

[Erik Slagter]

Recordings are on internal harddisk, external or other? It looks like data transfer to/from the harddisk is slow.

[atilaks]

I am recording on my NAS and I did that for at least 2 years. I am sure it is not caused by slow transfer, cause I can record other HD channels (e.g. 2 in parallel) and watch them at the same time. I didn't have that 'choppy' problem before, it suddenly showed up.

I will try different things, to see where the problem is...

[Erik Slagter]

Can you tell at what date (update) these problems have begun to show? That's because I am seeing similar phenomena on my dm8000 since some time, but I can specify when exactly. If we know at what date (build) the problems started, it's fairly easy to debug from git logging.

[atilaks]

Nope, sorry

[atilaks]

Maybe PAT error is not related to my problem with choppy playback, don't know yet.

However this is output from the log file, when PAT message is shown.

PATready
DVB service failed to tune - error 2
RemovePopup, id = ZapError
AddPopup, id = ZapError
eHdmiCEC: received message
Timeout!

[atilaks]

Well, I give up.
I cannot figure out what is wrong... I hope it gets fixed with time...

When I watch an 'active' recording (in progress) playback is choppy.
When I watch a 'finished' recording (from the same channel, similar bitrate) while the the former recording is still in progress playback is ok.
All recordings are stored on a network drive.

The choppy playback disappears when I record to an usb drive and is related to VuDuo only. Everything is ok on DM500HD with the newest OpenPli.

[Erik Slagter]

Anyway, the fact that I have this problem as well, ensures it won't get left unnoticed within the team

[atilaks]

I went back to the oldest backup I have from 2012-02-26 and there were no problems with playback.
When I tried a backup from 2012-03-26 (and all newer backups) the problem was there.

I cannot say when for the last time I updated the image before I made a backup on 2012-02-26...

[Erik Slagter]

Thanks, that already narrows the problem down to a certain time range.

[pieterg]

I went back to the oldest backup I have from 2012-02-26 and there were no problems with playback.
When I tried a backup from 2012-03-26 (and all newer backups) the problem was there.

I cannot say when for the last time I updated the image before I made a backup on 2012-02-26...

the last driver update perhaps?
http://openpli.git.s...8483542c560f8e4

Please try to copy /lib/modules/3.1.1/extra/*.ko from your 2012-02-26 backup into the current image, reboot, and see whether that helps.

[atilaks]

Too bad my backup from 2012-02 is based on 2.6.18.

I tried all VuDuo drivers for 3.1.1 with no success. Drivers from 2011-12-22 are almost perfect, spinners are showing so rarely I thought the problem is gone.

Reverted to 2.6.18 for now, waiting for new drivers.

Edited by skalita, 21 April 2012 - 07:49.

[Erik Slagter]

So this seems to be another proof that the vuplus' 3.1 kernel's drivers are bogus?

[atilaks]

I am not 100% sure, but it looks like this.

[atilaks]

I do not have the problem on dm500hd, but it is also running on 2.6.

Could it be caused by some incompatibilities between enigma2 and 3.1 kernel? I do not have other boxes running on 3.1, so I cannot test it.

[Erik Slagter]

I do not have the problem on dm500hd, but it is also running on 2.6.
Could it be caused by some incompatibilities between enigma2 and 3.1 kernel? I do not have other boxes running on 3.1, so I cannot test it.

No actually it has nothing to do with enigma or the linux kernel itself. For newer linux versions (always), the api between the kernel and the drivers (as a user or a programmer you will never see this layer) may change and the drivers need to be adjusted accordingly. For some reason this adoption has been less than succesful for vuplus.

Edited by Erik Slagter, 21 April 2012 - 08:50.