Lars Hanisch d...@flensrocker.de writes:
Am 07.03.2012 21:43, schrieb Udo Richter:
Am 07.03.2012 21:19, schrieb Richard Scobie:
I have found that adding a sleep 5 to my startup script, between
loading the drivers and starting vdr, has caused it to successfully
survive five reboots.
I'm
Am 08.03.2012 12:52, schrieb syrius...@no-log.org:
Lars Hanischd...@flensrocker.de writes:
Am 07.03.2012 21:43, schrieb Udo Richter:
Am 07.03.2012 21:19, schrieb Richard Scobie:
I have found that adding a sleep 5 to my startup script, between
loading the drivers and starting vdr, has caused
On 07.03.2012 06:33, Richard Scobie wrote:
For the past few weeks, I have been running the current 1.7.XX version of vdr
with an S2-6400 card, using only one tuner, which is connected to a 4 x 1
diseqc switch, without any problems.
The startup command has been:
/usr/local/bin/vdr -L
Klaus Schmidinger wrote:
Are you using the latest driver [1] and firmware [2]?
[1] http://powarman.dyndns.org/hgwebdir.cgi/v4l-dvb-saa716x/
[2] http://aregel.de/
Hi Klaus,
Have the latest firmware - drivers were a week old so have just updated
them and the result is the same.
Seems to
Richard Scobie wrote:
DVB-T'
Mar 8 08:34:40 atom vdr: [751] probing /dev/dvb/adapter1/frontend0
Mar 8 08:34:40 atom vdr: [751] creating cDvbDevice
Mar 8 08:34:40 atom vdr: [751] new device number 2
Mar 8 08:34:40 atom vdr: [758] epg data reader thread started (pid=751,
tid=758)
Mar 8
I have found that adding a sleep 5 to my startup script, between
loading the drivers and starting vdr, has caused it to successfully
survive five reboots.
Regards,
Richard
___
vdr mailing list
vdr@linuxtv.org
Am 07.03.2012 21:19, schrieb Richard Scobie:
I have found that adding a sleep 5 to my startup script, between
loading the drivers and starting vdr, has caused it to successfully
survive five reboots.
I'm doing an udevadm settle --timeout=30 after load/unload, haven't had
any issues with that.
Am 07.03.2012 21:43, schrieb Udo Richter:
Am 07.03.2012 21:19, schrieb Richard Scobie:
I have found that adding a sleep 5 to my startup script, between
loading the drivers and starting vdr, has caused it to successfully
survive five reboots.
I'm doing an udevadm settle --timeout=30 after
For the past few weeks, I have been running the current 1.7.XX version
of vdr with an S2-6400 card, using only one tuner, which is connected to
a 4 x 1 diseqc switch, without any problems.
The startup command has been:
/usr/local/bin/vdr -L /home/rs/vdr/PLUGINS/lib -D 1 -P dvbhddevice -P
