Hallo
ich wollte mich mal erkundigen, ob ich mir ob dieser Fehler meldung sorgen machen sollte:
Code
root@vdr4:~# grep "bonding" vdrbootstop.log
:22:35 vdr4 vdr: [950] ERROR: device '2' in device bondings '1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0' is not a cDvbDevice
:22:37 vdr4 vdr: [950] ERROR: device '2' in device bondings '1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0' is not a cDvbDevice
:22:37 vdr4 vdr: [950] ERROR: device '3' in device bondings '1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0' is not a cDvbDevice
:22:39 vdr4 vdr: [950] ERROR: device '4' in device bondings '1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0' is not a cDvbDeviceDas triit offenbar immer beim Neustart auf.
Ist das nur ne Nebenwirkung von Dynamite?
So geht's weiter:
Code
...
Dec 16 14:22:39 vdr4 vdr: [950] ERROR: device '4' in device bondings '1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0' is not a cDvbDevice
Dec 16 14:22:39 vdr4 vdr: [950] dynamite: /dev/dvb/adapter3/frontend0 is a dvb adapter trying to set card index to 3
Dec 16 14:22:39 vdr4 vdr: [950] new sub-device number 4
Dec 16 14:22:39 vdr4 vdr: [950] frontend 3/0 provides DVB-S,DVB-S2 with QPSK ("TurboSight TBS 6984 DVBS/S2 frontend")
Dec 16 14:22:39 vdr4 vdr: [950] dynamite: attached device /dev/dvb/adapter3/frontend0 to dynamic device slot 4
Dec 16 14:22:39 vdr4 vdr: [1289] tuner on frontend 3/0 thread started (pid=950, tid=1289)
Dec 16 14:22:39 vdr4 vdr: [1290] section handler thread started (pid=950, tid=1290)
Dec 16 14:22:39 vdr4 vdr: [950] tuner 0/0 unbonded from tuner 2/0
Dec 16 14:22:39 vdr4 vdr: [950] device 1 unbonded from device 3
Dec 16 14:22:39 vdr4 vdr: [950] tuner 1/0 unbonded from tuner 2/0
Dec 16 14:22:39 vdr4 vdr: [950] device 2 unbonded from device 3
Dec 16 14:22:39 vdr4 vdr: [950] tuner 1/0 bonded with tuner 0/0
Dec 16 14:22:39 vdr4 vdr: [950] device 2 bonded with device 1
Dec 16 14:22:40 vdr4 vdr: [950] tuner 2/0 bonded with tuner 1/0
Dec 16 14:22:40 vdr4 vdr: [950] device 3 bonded with device 2
Dec 16 14:22:40 vdr4 vdr: [950] tuner 3/0 bonded with tuner 2/0
Dec 16 14:22:40 vdr4 vdr: [950] device 4 bonded with device 3
Dec 16 14:22:40 vdr4 vdr: [950] dynamite: /dev/dvb/adapter0/frontend0 is a dvb adapter trying to set card index to 0
Dec 16 14:22:40 vdr4 vdr: [950] dynamite: /dev/dvb/adapter0/frontend0 is already attached
Dec 16 14:22:40 vdr4 vdr: [950] dynamite: /dev/dvb/adapter1/frontend0 is a dvb adapter trying to set card index to 1
Dec 16 14:22:40 vdr4 vdr: [950] dynamite: /dev/dvb/adapter1/frontend0 is already attached
Dec 16 14:22:40 vdr4 vdr: [950] dynamite: /dev/dvb/adapter2/frontend0 is a dvb adapter trying to set card index to 2
Dec 16 14:22:40 vdr4 vdr: [950] dynamite: /dev/dvb/adapter2/frontend0 is already attached
Dec 16 14:22:40 vdr4 vdr: [950] dynamite: /dev/dvb/adapter3/frontend0 is a dvb adapter trying to set card index to 3
Dec 16 14:22:40 vdr4 vdr: [950] dynamite: /dev/dvb/adapter3/frontend0 is already attached
Dec 16 14:22:40 vdr4 vdr: [950] setting primary device to 10
Dec 16 14:22:40 vdr4 vdr: [950] [softhddev]MakePrimaryDevice: 1
Dec 16 14:22:40 vdr4 vdr: [950] [softhddev]SetVideoFormat: 0
Dec 16 14:22:40 vdr4 vdr: [950] [softhddev]SetVideoDisplayFormat: 1Das scheint ja geklappt zu haben, trotz der Fehlermeldung.