I have newly istalled Ubuntu 8.04 with ubuntu packaged vdr 1.6.0. Output is with libxineoutput-plugin.
System works fine, but after some time (many hours, don't know how many) system stops receiving. Setting 'Min. User inactivity' is set to zero, so system won't say anything about shutting down. It just stops receiving, and selcting channel doesn't show any program. If there is some timer for recording, on timer system does restart, and most likely reloads DVB card drivers, and everything works. Also doing restart from menu salvages system.
System has two DVB cards, one for DVB-C (Terratec Cynergy 1200C) (not in use now, but used in final destination) and one DVB-T (Technisat SkyStar2) for testing in my place.
Any idea what might be reason for this? How to solve problem?
Markku Tavasti wrote:
I have newly istalled Ubuntu 8.04 with ubuntu packaged vdr 1.6.0. Output is with libxineoutput-plugin.
System works fine, but after some time (many hours, don't know how many) system stops receiving. Setting 'Min. User inactivity' is set to zero, so system won't say anything about shutting down. It just stops receiving, and selcting channel doesn't show any program. If there is some timer for recording, on timer system does restart, and most likely reloads DVB card drivers, and everything works. Also doing restart from menu salvages system.
I run a similar system, but without libxine. I have two dvb-cards, one FF Technotrend DVB-S (which outputs the video and sound), and one budget Technotrend dvb-t card.
Today in the morning I had my vdr "frozen" to the last sat-channel I was watching yesterday, and when trying to swap to dvb-t channel, I got the "channel unavailable". The sat-channels worked normally, but the dvb-t card did not. Restarting VDR and reloading the drivers did not help. I had to do a full reboot to get the dvt-t channels to work...
This happens to me a couple of times per week, and it's really annoying cause I miss recordings because of this :-(
I run also the latest Ubuntu 8.04, but with fairly recent drivers from linuxtv.org...
Could this be some kind of conflict with the Ubuntu-kernel and the HG-drivers?
René