Hi,
vdr is running fine on my machine except for one strange thing.
I can start/stop vdr perfectly fine, but when I select "Neustart" in the vdr menu (restart), it is coming into an endless loop of restarting itself.
The logfile then says: ov 12 16:31:56 localhost vdr[16858]: loading /var/lib/vdr/remote.conf Nov 12 16:31:56 localhost vdr[16858]: loading /var/lib/vdr/keymacros.conf Nov 12 16:31:56 localhost input.agent[16860]: evdev: already loaded Nov 12 16:31:56 localhost vdr[16858]: no DVB device found
When I say /etc/init.d/vdr restart everything works fine.
What is going wrong here? System details are:
Ubuntu 5.10 kernel 2.6.12-9-k7 vdr 1.3.27 Hauppauge Nexus-s Rev 2.3
Thanks for your help, Matthias
Matthias Bodenbinder wrote:
Hi,
vdr is running fine on my machine except for one strange thing.
I can start/stop vdr perfectly fine, but when I select "Neustart" in the vdr menu (restart), it is coming into an endless loop of restarting itself.
The logfile then says: ov 12 16:31:56 localhost vdr[16858]: loading /var/lib/vdr/remote.conf Nov 12 16:31:56 localhost vdr[16858]: loading /var/lib/vdr/keymacros.conf Nov 12 16:31:56 localhost input.agent[16860]: evdev: already loaded Nov 12 16:31:56 localhost vdr[16858]: no DVB device found
When I say /etc/init.d/vdr restart everything works fine.
What is going wrong here? System details are:
Ubuntu 5.10 kernel 2.6.12-9-k7 vdr 1.3.27 Hauppauge Nexus-s Rev 2.3
Difference is that on initscript restart the drivers will not be reloaded, on restart from menu the drivers will be reloaded. Most probably udev/hotplug takes it time to create the device nodes. This is some seconds on my system, in debian 15 sec's is default waittime after driver reload
HTH
Steffen
Steffen Barszus schrieb:
Difference is that on initscript restart the drivers will not be reloaded, on restart from menu the drivers will be reloaded. Most probably udev/hotplug takes it time to create the device nodes. This is some seconds on my system, in debian 15 sec's is default waittime after driver reload
What does that mean? Can I tell vdr to wait that amount of time? As I said, as of now vdr tries to restart itself forever.
Nov 13 16:57:24 localhost logger: restarting VDR Nov 13 16:57:35 localhost logger: restarting VDR Nov 13 16:57:47 localhost logger: restarting VDR Nov 13 16:57:58 localhost logger: restarting VDR Nov 13 16:58:09 localhost logger: restarting VDR Nov 13 16:58:21 localhost logger: restarting VDR Nov 13 16:58:32 localhost logger: restarting VDR Nov 13 16:58:43 localhost logger: restarting VDR Nov 13 16:58:54 localhost logger: restarting VDR Nov 13 16:59:06 localhost logger: restarting VDR Nov 13 16:59:17 localhost logger: restarting VDR Nov 13 16:59:28 localhost logger: restarting VDR Nov 13 16:59:39 localhost logger: restarting VDR Nov 13 16:59:51 localhost logger: restarting VDR Nov 13 17:00:02 localhost logger: restarting VDR Nov 13 17:00:13 localhost logger: restarting VDR Nov 13 17:00:25 localhost logger: restarting VDR Nov 13 17:00:36 localhost logger: restarting VDR Nov 13 17:00:47 localhost logger: restarting VDR Nov 13 17:00:58 localhost logger: restarting VDR Nov 13 17:01:10 localhost logger: restarting VDR Nov 13 17:01:21 localhost logger: restarting VDR Nov 13 17:01:32 localhost logger: restarting VDR Nov 13 17:01:43 localhost logger: restarting VDR Nov 13 17:01:54 localhost logger: restarting VDR Nov 13 17:02:06 localhost logger: restarting VDR Nov 13 17:02:17 localhost logger: restarting VDR Nov 13 17:02:28 localhost logger: restarting VDR Nov 13 17:02:39 localhost logger: restarting VDR Nov 13 17:02:51 localhost logger: restarting VDR Nov 13 17:03:02 localhost logger: restarting VDR
-
Matthias Bodenbinder -
Steffen Barszus