jep danke für den Tipp. Stehe auch mit dem Andrey des PPA "Königs" in Kontakt.
kann ich heute Abend machen wenn - hab den HTPC mit Tevii zZ nicht im Zugriff.
Es kommt aber langsam Licht ins Dunkel.
jep danke für den Tipp. Stehe auch mit dem Andrey des PPA "Königs" in Kontakt.
kann ich heute Abend machen wenn - hab den HTPC mit Tevii zZ nicht im Zugriff.
Es kommt aber langsam Licht ins Dunkel.
Das Problem scheint folgendes zu sein:
Das VDR Start Skript von AAP
irgendetwas geht bei
loadDriver() {
for MODULE in $MODULES
do
modprobe $MODULE >/dev/null 2>&1
done
}
unloadDriver() {
for MODULE in $MODULES
do
rmmod $MODULE >/dev/null 2>&1
wait $(pidof rmmod)
done
}
Display More
offensichtlich in Verbindung mit meiner Tevii schief.
Das skript von ETOBI hingegen rennt wunderbar.
ich hab einfach mal alles was mit den vdr sourcen kam gebaut...
Aber ja, du hast schon recht, das is komisch. Macht aber kein Unterschied... ich kann auch nur mal das vnsi laden...
W_scan geht 1a.
VDR nicht.
Das sagt das XBMC Log
21:22:42 T:2761939776 NOTICE: AddOnLog: VDR VNSI Client: Logged in at '1364242962+3600' to 'VDR-Network-Streaming- Interface (VNSI) Server' Version: '0.9.0' with protocol version '3'
21:22:45 T:2761939776 ERROR: AddOnLog: VDR VNSI Client: ReadResult - request timed out after 3 seconds
21:22:45 T:2761939776 ERROR: AddOnLog: VDR VNSI Client: EnableStatusInterface - Can't get response packed
21:22:47 T:3008509760 NOTICE: DVDPlayer: Opening: pvr://channels/tv/All TV channels/3.pvr
21:22:47 T:3008509760 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
21:22:47 T:3008509760 NOTICE: CXBMCRenderManager::ResetRenderBuffer - using 5 render buffers
21:22:47 T:2726652736 NOTICE: Thread CDVDPlayer start, auto delete: false
21:22:47 T:2726652736 NOTICE: Creating InputStream
21:22:47 T:2726652736 NOTICE: AddOnLog: VDR VNSI Client: Logged in at '1364242967+3600' to 'VDR-Network-Streaming- Interface (VNSI) Server' Version: '0.9.0' with protocol version '3'
21:22:47 T:2726652736 ERROR: AddOnLog: VDR VNSI Client: ReadSuccess - failed with error code '997'
21:22:47 T:2726652736 ERROR: AddOnLog: VDR VNSI Client: SwitchChannel - failed to set channel
21:22:47 T:2726652736 ERROR: CDVDPlayer::OpenInputStream - error opening [pvr://channels/tv/All TV channels/3.pvr ]
21:22:47 T:2726652736 NOTICE: CDVDPlayer::OnExit()
21:22:47 T:2726652736 NOTICE: CDVDPlayer::OnExit() deleting input stream
21:22:47 T:2921331520 NOTICE: [BR-tracker service 1] Playback stopped, trying to kill makemkv
21:22:47 T:2921331520 NOTICE: [BR-makemkvinteraction 1] attempting linux kill of makemkvcon
21:22:47 T:3008509760 NOTICE: CDVDPlayer::CloseFile()
21:22:47 T:3008509760 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
21:22:47 T:3008509760 NOTICE: DVDPlayer: waiting for threads to exit
21:22:47 T:3008509760 NOTICE: DVDPlayer: finished waiting
21:22:47 T:2921331520 NOTICE: [BR-makemkvinteraction 1] Linux call successful
21:22:47 T:2921331520 NOTICE: [BR-makemkvinteraction 1] attempting windows kill of makemkvcon
21:22:47 T:2921331520 NOTICE: [BR-makemkvinteraction 1] Windows call successful
Display More
und das syslog eben passend
Mar 25 20:35:52 ubuntu vdr: [15506] loading /etc/vdr/plugins/vnsiserver/allowed_hosts.conf
Mar 25 20:35:52 ubuntu vdr: [15506] VNSI: Client with ID 1 connected: 127.0.0.1:49200
Mar 25 20:35:52 ubuntu vdr: [15512] VNSI: Welcome client 'XBMC Media Center' with protocol version '3'
Mar 25 20:35:52 ubuntu vdr: [15512] VNSI-Error: Can't get device for channel 1 - Das Erste HD
ok also.
Ich habs nochmal getestet. Ich bekomme folgende Log
Mar 25 20:35:33 ubuntu vdr: [15495] found 2 DVB devices
Mar 25 20:35:33 ubuntu vdr: [15505] section handler thread started (pid=15495, tid=15505, prio=low)
Mar 25 20:35:33 ubuntu vdr: [15495] initializing plugin: dvbhddevice (0.0.9): HD Full Featured DVB device
Mar 25 20:35:33 ubuntu vdr: [15495] initializing plugin: dvbsddevice (0.0.9): SD Full Featured DVB device
Mar 25 20:35:33 ubuntu vdr: [15495] initializing plugin: epgtableid0 (0.0.3): EPG handler for events with table id 0x00
Mar 25 20:35:33 ubuntu vdr: [15495] initializing plugin: hello (0.2.7): A friendly greeting
Mar 25 20:35:33 ubuntu vdr: [15495] initializing plugin: osddemo (0.3.1): Demo of arbitrary OSD setup
Mar 25 20:35:33 ubuntu vdr: [15495] initializing plugin: pictures (0.1.5): A simple picture viewer
Mar 25 20:35:33 ubuntu vdr: [15495] initializing plugin: rcu (0.0.4): Remote Control Unit
Mar 25 20:35:33 ubuntu vdr: [15495] initializing plugin: status (0.3.3): Status monitor test
Mar 25 20:35:33 ubuntu vdr: [15495] initializing plugin: svccli (0.1.4): Service demo client
Mar 25 20:35:33 ubuntu vdr: [15495] initializing plugin: svcsvr (0.1.4): Service demo server
Mar 25 20:35:33 ubuntu vdr: [15495] initializing plugin: svdrpdemo (0.0.5): How to add SVDRP support to a plugin
Mar 25 20:35:33 ubuntu vdr: [15495] initializing plugin: vnsiserver (0.9.0): VDR-Network-Streaming-Interface (VNSI) Server
Mar 25 20:35:33 ubuntu vdr: [15495] setting primary device to 1
Mar 25 20:35:33 ubuntu vdr: [15495] device 1 has no MPEG decoder
Mar 25 20:35:33 ubuntu vdr: [15495] assuming manual start of VDR
Mar 25 20:35:33 ubuntu vdr: [15495] SVDRP listening on port 6419
Mar 25 20:35:33 ubuntu vdr: [15495] setting current skin to "lcars"
Mar 25 20:35:33 ubuntu vdr: [15495] loading /etc/vdr/themes/lcars-default.theme
Mar 25 20:35:33 ubuntu vdr: [15495] starting plugin: dvbhddevice
Mar 25 20:35:33 ubuntu vdr: [15495] starting plugin: dvbsddevice
Mar 25 20:35:33 ubuntu vdr: [15495] starting plugin: epgtableid0
Mar 25 20:35:33 ubuntu vdr: [15495] starting plugin: hello
Mar 25 20:35:33 ubuntu vdr: [15495] starting plugin: osddemo
Mar 25 20:35:33 ubuntu vdr: [15495] starting plugin: pictures
Mar 25 20:35:33 ubuntu vdr: [15495] starting plugin: rcu
Mar 25 20:35:33 ubuntu vdr: [15495] ERROR (rcu.c,83): /dev/ttyS1: Eingabe-/Ausgabefehler
Mar 25 20:35:33 ubuntu vdr: [15495] starting plugin: status
Mar 25 20:35:33 ubuntu vdr: [15495] starting plugin: svccli
Mar 25 20:35:33 ubuntu vdr: [15495] starting plugin: svcsvr
Mar 25 20:35:33 ubuntu vdr: [15495] starting plugin: svdrpdemo
Mar 25 20:35:33 ubuntu vdr: [15495] starting plugin: vnsiserver
Mar 25 20:35:33 ubuntu vdr: [15495] VNSI: VNSI Server started
Mar 25 20:35:33 ubuntu vdr: [15495] VNSI: Channel streaming timeout: 10 seconds
Mar 25 20:35:33 ubuntu vdr: [15495] ERROR: remote control RCU not ready!
Mar 25 20:35:33 ubuntu vdr: [15495] switching to channel 1
Mar 25 20:35:33 ubuntu vdr: [15506] VDR VNSI Server thread started (pid=15495, tid=15506, prio=high)
Mar 25 20:35:33 ubuntu vdr: [15495] status: cStatusTest::ChannelSwitch 0 0 1
Mar 25 20:35:33 ubuntu vdr: [15495] info: Kanal nicht verfügbar!
Mar 25 20:35:33 ubuntu vdr: [15495] ERROR: no OSD provider available - using dummy OSD!
Mar 25 20:35:33 ubuntu vdr: [15495] status: cStatusTest::OsdStatusMessage 'Kanal nicht verfügbar!'
Mar 25 20:35:33 ubuntu vdr: [15506] loading /etc/vdr/plugins/vnsiserver/allowed_hosts.conf
Mar 25 20:35:33 ubuntu vdr: [15506] VNSI: Client with ID 0 connected: 127.0.0.1:49199
Mar 25 20:35:33 ubuntu vdr: [15507] VNSI: Welcome client 'XBMC Media Center' with protocol version '3'
Mar 25 20:35:35 ubuntu vdr: [15495] status: cStatusTest::OsdClear
Mar 25 20:35:35 ubuntu vdr: [15495] status: cStatusTest::SetVolume 255 1
Mar 25 20:35:35 ubuntu vdr: [15495] setting watchdog timer to 60 seconds
Mar 25 20:35:35 ubuntu vdr: [15495] OSD size changed to 720x480 @ 1
Mar 25 20:35:35 ubuntu vdr: [15495] ERROR: no OSD provider available - using dummy OSD!
Mar 25 20:35:35 ubuntu vdr: [15495] status: cStatusTest::OsdChannel 1 Das Erste HD
Mar 25 20:35:40 ubuntu vdr: [15495] status: cStatusTest::OsdClear
Mar 25 20:35:41 ubuntu vdr: [15495] max. latency time 1 seconds
Mar 25 20:35:52 ubuntu vdr: [15506] loading /etc/vdr/plugins/vnsiserver/allowed_hosts.conf
Mar 25 20:35:52 ubuntu vdr: [15506] VNSI: Client with ID 1 connected: 127.0.0.1:49200
Mar 25 20:35:52 ubuntu vdr: [15512] VNSI: Welcome client 'XBMC Media Center' with protocol version '3'
Mar 25 20:35:52 ubuntu vdr: [15512] VNSI-Error: Can't get device for channel 1 - Das Erste HD
Display More
Beim VDR macht es keinen Unterschied ob ich mit -D 0 / -D 1 oder komplettohne diese Option anstarte.-
SVDRP port is 6419
ok danke. Ich hab ihn mal wie empfohlen aktiviert.
QuoteWie schaut es da bei euch aus... habt ihr bei laufendem VDR direkt einen LOCK?
Falls es untergegangen ist. Sollte ich bei korrekt laufendem VDR direkt einen LOCK haben (siehe letzter Post von mir)
gut.
Dennoch läuft es ja wie gesagt auch ohne die Option. Der VDR kommt immer hoch und wenn es einmal läuft läuft es immer - also es ist mir in der Vergangenheit nicht aufgefallen dass die tevii da mal da war mal nicht... je nach dem wer zuerst kommt.
Edit
Was macht der Parameter
# Default port for SVDRP
SVDRP_PORT='0'
genau
Ok also mit Wscan kann ich ganz gut prüfen ob aus TV Karten Sicht alles iO ist. Dem scheint so. Ich versuchs mal heute Abend wenn ich direkt Zugriff auf XBMC hab ob alles passt je nach Parameter.
Mich hatte etwas verwundert, dass die Tevii nie einen
status SCVYL | signal 65% | snr 69% | ber 0 | unc 0 | FE_HAS_LOCK
bringt wenn der VDR läuft.
ich meine das war bei VDR 1.7.28 so... da konnte ich mit Femon direkt testen ob Empfang da ist. Ich dachte ich habe ein FW problem weil ich in XBMC kein Bild hab und des weiteren femon -H nie nen Lock anzeigte.
Wie man hier sieht
root@testhtpc:/home/xbmc# sudo apt-get -y install vdrReading package lists... DoneBuilding dependency treeReading state information... DoneSuggested packages: vdr-plugin-dvbsddeviceThe following NEW packages will be installed: vdr0 upgraded, 1 newly installed, 0 to remove and 11 not upgraded.Need to get 0 B/917 kB of archives.After this operation, 2,712 kB of additional disk space will be used.Preconfiguring packages ...Selecting previously unselected package vdr.(Reading database ... 81511 files and directories currently installed.)Unpacking vdr (from .../archives/vdr_1.7.28-1_i386.deb) ...Processing triggers for ureadahead ...Processing triggers for man-db ...Setting up vdr (1.7.28-1) ...Starting Linux Video Disk Recorder: vdrSearching for plugins (VDR 1.7.28/1.7.28) (cache hit):.root@testhtpc:/home/xbmc# femon -HFE: Montage Technology DS3000/TS2020 (DVBS)status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCKstatus SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCKstatus SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
hab ich unter der VDR 1.7.28 direkt einen FE_HAS_LOCK wenn vdr läuft.
Bei VDR 1.7.41 läuft zwar der VDR, aber das FE_HAS_LOCK fehlt -> kein Bild. Mit wscan bekomm ich aber den FE_HAS_LOCK was wohl bedeutet dass die TV karte an sich iO ist.
Wie schaut es da bei euch aus... habt ihr bei laufendem VDR direkt einen LOCK?
dankeschön. Hast ne PN =)
das Video Verzeichnis ist erstmal nicht so wichtig. Beide Verzeichnisse sollten existieren.
Das ist dann fein-tuning. Das mit dem Port ist natürlich ne Sache der man nachgehen sollte. Vielleicht ist der VDR auch wirklich müll aus dem ppa - aber wie installiere ich ihn selbst am besten (ink init.d. skripte) - kommen die direkt mit oder muss ich die selbst anlegen?
OPTIONS='--vfat -w 60 -D 0'
werde ich umgehend testen sobald @ home.
Edit:
habe meinen HTPC mal booten lassen
Ich schau mal eben wie sich der Parameter schlägt
Startlog VDR:
Mar 25 12:51:07 ubuntu kernel: [ 364.830076] usbcore: deregistering interface driver dw2102Mar 25 12:51:07 ubuntu kernel: [ 364.874274] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.Mar 25 12:51:07 ubuntu kernel: [ 364.921231] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.Mar 25 12:51:07 ubuntu kernel: [ 364.939261] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmwareMar 25 12:51:07 ubuntu kernel: [ 364.940620] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'Mar 25 12:51:07 ubuntu kernel: [ 364.940623] dw2102: start downloading DW210X firmwareMar 25 12:51:07 ubuntu kernel: [ 365.096301] dvb-usb: found a 'TeVii S660 USB' in warm state.Mar 25 12:51:07 ubuntu kernel: [ 365.096350] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.Mar 25 12:51:07 ubuntu kernel: [ 365.096714] DVB: registering new adapter (TeVii S660 USB)Mar 25 12:51:07 ubuntu kernel: [ 365.345911] dvb-usb: MAC address: 00:18:bd:5a:c4:d9Mar 25 12:51:07 ubuntu kernel: [ 365.348903] DS3000 chip version: 0.192 attached.Mar 25 12:51:07 ubuntu kernel: [ 365.349276] dw2102: Attached ds3000+ds2020!Mar 25 12:51:07 ubuntu kernel: [ 365.349276]Mar 25 12:51:07 ubuntu kernel: [ 365.349280] DVB: registering adapter 0 frontend 0 (Montage Technology DS3000/TS2020)...Mar 25 12:51:07 ubuntu kernel: [ 365.350161] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.0/0000:02:00.1/usb3/3-1/input/input26Mar 25 12:51:07 ubuntu kernel: [ 365.350200] dvb-usb: schedule remote query interval to 150 msecs.Mar 25 12:51:07 ubuntu kernel: [ 365.350203] dvb-usb: TeVii S660 USB successfully initialized and connected.Mar 25 12:51:07 ubuntu kernel: [ 365.350220] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmwareMar 25 12:51:07 ubuntu kernel: [ 365.351840] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'Mar 25 12:51:07 ubuntu kernel: [ 365.351844] dw2102: start downloading DW210X firmwareMar 25 12:51:07 ubuntu kernel: [ 365.504209] dvb-usb: found a 'TeVii S660 USB' in warm state.Mar 25 12:51:07 ubuntu kernel: [ 365.504250] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.Mar 25 12:51:07 ubuntu kernel: [ 365.504646] DVB: registering new adapter (TeVii S660 USB)Mar 25 12:51:08 ubuntu kernel: [ 365.754051] dvb-usb: MAC address: 00:18:bd:5a:c4:daMar 25 12:51:08 ubuntu kernel: [ 365.757037] DS3000 chip version: 0.192 attached.Mar 25 12:51:08 ubuntu kernel: [ 365.757405] dw2102: Attached ds3000+ds2020!Mar 25 12:51:08 ubuntu kernel: [ 365.757405]Mar 25 12:51:08 ubuntu kernel: [ 365.757410] DVB: registering adapter 1 frontend 0 (Montage Technology DS3000/TS2020)...Mar 25 12:51:08 ubuntu kernel: [ 365.758214] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.0/0000:02:00.3/usb4/4-1/input/input27Mar 25 12:51:08 ubuntu kernel: [ 365.758251] dvb-usb: schedule remote query interval to 150 msecs.Mar 25 12:51:08 ubuntu kernel: [ 365.758254] dvb-usb: TeVii S660 USB successfully initialized and connected.Mar 25 12:51:08 ubuntu kernel: [ 365.758274] usbcore: registered new interface driver dw2102Mar 25 12:51:08 ubuntu vdr: [2366] VDR version 1.7.42 startedMar 25 12:51:08 ubuntu vdr: [2366] codeset is 'UTF-8' - knownMar 25 12:51:08 ubuntu vdr: [2366] found 28 locales in /usr/share/localeMar 25 12:51:08 ubuntu vdr: [2366] loading plugin: /usr/lib/vdr/plugins/libvdr-vnsiserver4.so.1.7.41Mar 25 12:51:08 ubuntu vdr: [2366] loading plugin: /usr/lib/vdr/plugins/libvdr-wirbelscan.so.1.7.41Mar 25 12:51:08 ubuntu vdr: [2366] loading /etc/vdr/setup.confMar 25 12:51:08 ubuntu vdr: [2366] loading /etc/vdr/sources.confMar 25 12:51:08 ubuntu vdr: [2366] loading /etc/vdr/diseqc.confMar 25 12:51:08 ubuntu vdr: [2366] loading /etc/vdr/scr.confMar 25 12:51:08 ubuntu vdr: [2366] loading /etc/vdr/channels.confMar 25 12:51:08 ubuntu vdr: [2366] deleting duplicate channel EinsPlus;ARD:10744:HC56M2S0:S19.2E:22000:301=2:302=deu@3:304:0:28723:1:1051:0Mar 25 12:51:08 ubuntu vdr: [2366] deleting duplicate channel arte;ARD:10743:HC56M2S0:S19.2E:22000:401=2:402=deu@3,403=fra@3:404:0:28724:1:1051:0Mar 25 12:51:08 ubuntu vdr: [2366] deleting duplicate channel ORF1 HD;ORF:11303:HC23M5O35S1:S19.2E:22000:1920=27:1921=deu@4,1922=eng@4;1923=deu@106:1925:648,D05,D95,1702,1833,9C4:4911:1:1007:0Mar 25 12:51:08 ubuntu vdr: [2366] deleting duplicate channel ORF2 HD;ORF:11303:HC23M5O35S1:S19.2E:22000:2920=27:2921=deu@4,2922=deu@4;2923=deu@106:2925:648,D05,D95,1702,1833,9C4:4912:1:1007:0Mar 25 12:51:08 ubuntu vdr: [2366] loading /etc/vdr/svdrphosts.confMar 25 12:51:08 ubuntu vdr: [2366] loading /etc/vdr/keymacros.confMar 25 12:51:08 ubuntu vdr: [2366] registered source parameters for 'A - ATSC'Mar 25 12:51:08 ubuntu vdr: [2366] registered source parameters for 'C - DVB-C'Mar 25 12:51:08 ubuntu vdr: [2366] registered source parameters for 'S - DVB-S'Mar 25 12:51:08 ubuntu vdr: [2366] registered source parameters for 'T - DVB-T'Mar 25 12:51:08 ubuntu vdr: [2370] video directory scanner thread started (pid=2366, tid=2370, prio=high)Mar 25 12:51:08 ubuntu vdr: [2370] video directory scanner thread ended (pid=2366, tid=2370)Mar 25 12:51:08 ubuntu vdr: [2369] video directory scanner thread started (pid=2366, tid=2369, prio=high)Mar 25 12:51:08 ubuntu vdr: [2369] video directory scanner thread ended (pid=2366, tid=2369)Mar 25 12:51:08 ubuntu vdr: [2366] probing /dev/dvb/adapter0/frontend0Mar 25 12:51:08 ubuntu vdr: [2366] creating cDvbDeviceMar 25 12:51:08 ubuntu vdr: [2366] new device number 1Mar 25 12:51:08 ubuntu vdr: [2371] epg data reader thread started (pid=2366, tid=2371, prio=high)Mar 25 12:51:08 ubuntu vdr: [2371] reading EPG data from /var/cache/vdr/epg.dataMar 25 12:51:08 ubuntu vdr: [2371] epg data reader thread ended (pid=2366, tid=2371)Mar 25 12:51:08 ubuntu vdr: [2366] frontend 0/0 provides DVB-S,DVB-S2 with QPSK ("Montage Technology DS3000/TS2020")Mar 25 12:51:08 ubuntu vdr: [2374] section handler thread started (pid=2366, tid=2374, prio=low)Mar 25 12:51:08 ubuntu vdr: [2366] found 1 DVB deviceMar 25 12:51:08 ubuntu vdr: [2366] initializing plugin: vnsiserver4 (0.9.2): VDR-Network-Streaming-Interface (VNSI) ServerMar 25 12:51:08 ubuntu vdr: [2366] initializing plugin: wirbelscan (0.0.7): DVB and pvrinput channel scan for VDRMar 25 12:51:08 ubuntu vdr: [2366] setting primary device to 1Mar 25 12:51:08 ubuntu vdr: [2366] device 1 has no MPEG decoderMar 25 12:51:08 ubuntu vdr: [2366] assuming manual start of VDRMar 25 12:51:08 ubuntu vdr: [2366] SVDRP listening on port 6419Mar 25 12:51:08 ubuntu vdr: [2366] setting current skin to "lcars"Mar 25 12:51:08 ubuntu vdr: [2366] loading /etc/vdr/themes/lcars-default.themeMar 25 12:51:08 ubuntu vdr: [2366] starting plugin: vnsiserver4Mar 25 12:51:08 ubuntu vdr: [2366] VNSI: VNSI Server startedMar 25 12:51:08 ubuntu vdr: [2366] VNSI: Channel streaming timeout: 10 secondsMar 25 12:51:08 ubuntu vdr: [2366] starting plugin: wirbelscanMar 25 12:51:08 ubuntu vdr: [2366] switching to channel 1Mar 25 12:51:08 ubuntu vdr: [2366] info: Kanal nicht verfügbar!Mar 25 12:51:08 ubuntu vdr: [2366] ERROR: no OSD provider available - using dummy OSD!Mar 25 12:51:08 ubuntu vdr: [2373] tuner on frontend 0/0 thread started (pid=2366, tid=2373, prio=high)Mar 25 12:51:08 ubuntu vdr: [2373] cTimeMs: using monotonic clock (resolution is 1 ns)Mar 25 12:51:08 ubuntu vdr: [2375] VDR VNSI Server thread started (pid=2366, tid=2375, prio=high)Mar 25 12:51:08 ubuntu vdr: [2375] VNSI-Error: Invalid or missing '/etc/vdr/plugins/vnsiserver4/allowed_hosts.conf'. falling back to 'svdrphosts.conf'.Mar 25 12:51:08 ubuntu vdr: [2375] VNSI-Error: Invalid or missing /etc/vdr/plugins/vnsiserver4/../svdrphosts.conf. Adding 127.0.0.1 to list of allowed hosts.Mar 25 12:51:08 ubuntu vdr: [2375] VNSI: Client with ID 0 connected: 127.0.0.1:43898Mar 25 12:51:08 ubuntu vdr: [2379] VNSI: Welcome client 'XBMC Media Center' with protocol version '4'Mar 25 12:51:08 ubuntu vdr: [2375] VNSI: Requesting clients to reload channel listMar 25 12:51:10 ubuntu vdr: [2366] setting watchdog timer to 60 secondsMar 25 12:51:10 ubuntu vdr: [2366] OSD size changed to 720x480 @ 1Mar 25 12:51:10 ubuntu vdr: [2366] ERROR: no OSD provider available - using dummy OSD!Mar 25 12:51:16 ubuntu vdr: [2366] max. latency time 1 seconds
->
[size=8]FE: Montage Technology DS3000/TS2020 (DVBS)
status | signal 90% | snr 0% | ber 0 | unc 768 |
status | signal 90% | snr 0% | ber 0 | unc 768 |
status | signal 90% | snr 0% | ber 0 | unc 768 |
status | signal 90% | snr 0% | ber 0 | unc 768 |[/size]
lasse ich mit wscan scannen hab ich lock. Kann ich ohne GUI schauen ob der VDR Kanäle korrekt ansteuert?
trying 'S2 f = 11303 kHz H SR = 22000 2/3 0,35 8PSK'
(time: 01:32) (time: 01:34) signal ok:
S2 f = 11303 kHz H SR = 22000 2/3 0,35 8PSK
updating transponder:
(S2 f = 11171 kHz H SR = 22000 2/3 0,20 8PSK) 0x4043
to (S2 f = 11170 kHz H SR = 22000 2/3 0,35 8PSK) 0x4043
Info: no data from NIT(actual)
11318: skipped (already known transponder)
trying 'S2 f = 11347 kHz V SR = 22000 2/3 0,35 8PSK'
(time: 01:47) (time: 01:48) signal ok:
S2 f = 11347 kHz V SR = 22000 2/3 0,35 8PSK
trying 'S2 f = 11362 kHz H SR = 22000 2/3 0,35 8PSK'
(time: 02:00) (time: 02:02) signal ok:
Display More
root@ubuntu:/home/xbmc# femon -H
FE: Montage Technology DS3000/TS2020 (DVBS)
status SCVYL | signal 65% | snr 74% | ber 55 | unc 2 | FE_HAS_LOCK
status SCVYL | signal 65% | snr 74% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 65% | snr 74% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 65% | snr 29% | ber -1 | unc 0 | FE_HAS_LOCK
status | signal 65% | snr 99% | ber -1 | unc 58 |
status SCVYL | signal 65% | snr 64% | ber -1 | unc 58 | FE_HAS_LOCK
status SCVYL | signal 65% | snr 69% | ber 57 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 65% | snr 69% | ber 0 | unc 0 | FE_HAS_LOCK
Sieht ja soweit rein von der DVB Karte her okay aus.
oki also bisher wurde mein VDR so gestartet
der neue 1.7.41 vom ppa nimmt
# Config-Directory
CFG_DIR='/etc/vdr'
# Plugin-Directory
PLUGIN_DIR='/usr/lib/vdr/plugins'
# Plugin Config-Directory
PLUGIN_CFG_DIR='/etc/vdr/plugins'
# Commmand executed by vdr to shutdown the system
SHUTDOWNCMD='/sbin/shutdown -h now'
# EPG data file
EPG_FILE='/var/cache/vdr/epg.data'
# Default port for SVDRP
SVDRP_PORT='0'
# Video-Directory
VIDEO_DIR='/var/lib/video.00'
# Environment variables to be set before starting VDR
VDR_ENV=''
# VDR options
OPTIONS='--vfat -w 60'
# Space separated names of plugins to be loaded on VDR startup. To pass any
# arguments to a plugin put them into the $PLUGIN_CFG_DIR/plugin.{name}.conf file.
PLUGINS=$(echo -n $(ls $PLUGIN_DIR/libvdr-*.so.* 2> /dev/null | sed -r 's:.*/libvdr-(.+)\.so\..+:\1:g'))
Display More
hallo... ich schreib das sich gerade just in diesem Moment nicht auf den HTPC zugreifen kann und stellte generelle Fragen. Kein Grund so rumzugiften.
Sag mir wo welches file ich anpassen muss oder ob ich ein /etc/init.d/vdr start -D0 absetzen muss und dann sollts mit Adapter 0 laufen...?
Bitte lass mich wissen wo ich das genau nachprüfe.
Nochmal. Es muss ja nicht VDR sein. Es kann auch mit dem Laden der FW zusammenhängen. Eventuell kann ich diese wie MarMic gemeint hat mal explizit neu laden lassen. Und eine Erklärung für die Kernel Meldungen beim Start von VDR gibts ja auch noch nicht.
Und ja. Der 1.7.41 rennt generell schon aus dem ppa. Nach mehrmaligem purgen und neu installen lief der Testhtps ja auch mit VDR 1.7.41 und Tevii S480. Nur woran es dann lag... keine Ahnung (auch mit nur einem Kabel). Ich bevorzuge deterministische Lösungen / Problemfindungen.
Edit:
gerne kann man heute Abend zusammen drauf schauen. Das geht sicher einfacher und hat auch nen gewissen Lerneffekt bei mir da ich dann sehe was jemand macht. Wenn du ne viertel Stunde zeit mitbringst kann man gerne Software technisch alles abklappern und untersuchen.
hm das funktioniert von VDR 1.6 - 1.7.28 eigentlich immer
Wenn ich den VDR von ppa installiere dann startet der ja automatisch. Muss ich da im init.d script nachschauen oder wo müsste das zu finden sein?
ich meine der Start vom VDR war bei 1.7.28 noch in der /etc/default/vdr definiert - da starte ich mit
echo "ENABLED=1" >> /etc/default/vdr
echo "ENABLE_SHUTDOWN=1" >> /etc/default/vdr
echo "OPTIONS=\"-w 60 --lirc=/dev/null --video=/recordings\"" >> /etc/default/vdr
Ich kann gern eine neue Verkabelung vornehmen. Welche genauen physikalischen und softwaretechnischen Gründe hat es denn?
Edit:
wie gesagt ich wusste das nicht anders beim Verkabeln und es lief / läuft ja. Ich stecke recht oft auf andere Systeme um da ich hier noch 2 weitere HTPCs (Intel / AMD) habe. In einem weiteren Nvidia Test HTPC ist auch eine Tevii S480 verbaut die genauso mit nur einem Anschluss startet
Ich denke wirklich weiter kommen tun wir nur wenn wir mal auf das System schauen. Bis zur neuen Verkabelung könnte man wenn ich euch richtig verstehe wohl mit dem Parameter arbeiten um auf Nummer sicher zu gehen. Wie müsste das aussehen (leider is der HTPC gerade off und ich auf Arbeit)
@ fnu
sorry für nicht einhalten der Designrichtlinien ich schau dass ichs abänder.
Quote
Ok, das ist doch mal eine Ansage, was ich nicht verstehe in der Flut Deiner Romane, nimmst Du mit VDR 1.7.28 einen anderen DVB Kernel-Treiber als mit VDR 1.7.41?
Nein. Weder Firmware noch sonstwas ist anders. ich weiß nicht welche deps der VDR aus dem "aap" repo mit bringt und was der an sich treibt.
https://launchpad.net/~aap/+archive/vdr
Ich meine vorgestern einfach mal folgendes getestet zu haben.
-> quantal setup + die Tevii FW geladen
-> system setup mit 1.7.28 + vnsi3 - läuft, Karte hat Lock und Empfang
-> vdr + plugin gepurged
-> aap repo geadded -> vdr 1.7.41 + vnsi3 installiert -> kein Empfang
-> vdr + plugin gepurged
-> system setup mit 1.7.28 + vnsi3 - läuft, Karte hat Lock und Empfang
kann ich aber heute gern verifizieren.
Erst deshalb dachte ich ja dass der VDR 1.7.41 irgendetwas anders macht und "schuld" ist. =/ auch wenn das auch meinem eigentlichen Gedankengang widerspricht.
Ich wundere mich halt über diese komischen "FW laden" Kernel Messages im syslog.
Ihr seid sicher viel tiefer drin. Ich gestehe dass ich VDR zwar über Jahre nutze, aber mit Startskripten habe ich an sich wenig am Hut, genauso mit der Verkabelung. Bisher tat jede Tuner Karte (und ich hatte einige) wenn ich einfach ein Kabel an einen der beiden Tuner stecke. Bei der Digital Devices cineS2 V6 übrigens genauso (hatte ich mal hier - hat aber schlechteren Empfang als die Tevii - hat den preis jedenfalls nicht gerechtfertigt)...
Aaalso:
Tuner ist eine Tevii S480 V2.1
System 12.10 x86 mit 3.5.0.26 Kernel
Sat Astra 19.2
Lediglich 1 Kabel ist am oberen der 2 Tuner angeschlossen. Der Untere ist leer und war es schon immer und so war / ist die Karte auch schon 2 Jahre in Betrieb
QuoteBeschreibe dein SAT Setup (LNB, Multiswitch, Auf welche Sats ausgerichtet, SCR/Unicable, DeviceBonding)
Da bin ich leider kein Fachmann drin. Es ist ein 4er LNB ausgerichtet auf den Astra 19.2 . im Haus hat jeder Tuner sein eigenen Anschluss an das LNB und bei mir in der Wohnung habe ich nur eine Zuleitung. Es ist eine Trin Karte (genannt) verbaut wird aber wie gesagt nur ein Tuner von genutzt der auch direkt am LNB angeschlossen ist.
Ich installiere immer mittels Skript welches über eine Iso automatisch beim ersten Boot aufgerufen wird. Siehe hier:
http://www.computerbase.de/forum/showthread.php?t=882014
Das eigentliche Installationsskript ist das hier:
ftp://night.dyndns.org/htpc_test/files/install.sh (beim jetzigen Setting)
VDR wurde so installiert:
add-apt-repository -y ppa:aap/vdr
apt-get update
sudo apt-get -y install dvb-apps
sudo apt-get -y install vdr fakeroot git-core
mkdir /home/xbmc/build
cd /home/xbmc/build
apt-get build-dep -y vdr
apt-get source vdr
mv vdr-* vdr
git clone --branch vnsi4 [url]https://github.com/FernetMenta/xbmc-pvr-addons.git[/url]
rm -R vdr/PLUGINS/src/*
ln -s /home/xbmc/build/xbmc-pvr-addons/addons/pvr.vdr.vnsi/vdr-plugin-vnsiserver /home/xbmc/build/vdr/PLUGINS/src/vnsiserver
cd /home/xbmc/build/vdr/
make -j4 VDRDIR=/usr/include/vdr LIBDIR=/usr/lib/vdr/plugins
make install VDRDIR=/usr/include/vdr LIBDIR=/usr/lib/vdr/plugins
/etc/init.d/vdr restart
Ich habe übrigens mehrere Testsysteme hier. Allerdings nur zwei Tevii Karten. Beide laufen auch 1a wenn ich den VDR 1.7.28 aus dem Rebo von Ubuntu nehme und die Firmware direkt installiere
[code]cd /tmp > /dev/null 2>&1
wget $DOWNLOAD_URL/s2_liplianin_1.tar > /dev/null 2>&1
tar xvf s2_liplianin_1.tar > /dev/null 2>&1
cd tevii_s2_liplianin-eb8a914cd499/linux/firmware/ > /dev/null 2>&1
cp dvb-usb-s660.fw /lib/firmware > /dev/null 2>&1
rm /tmp/s2_liplianin_1.tar > /dev/null 2>&1
rm -R /tmp/tevii_s2_liplianin-eb8a914cd499/linux/firmware/ > /dev/null 2>&1
cd /tmp > /dev/null 2>&1
wget -c $DOWNLOAD_URL/tevii_ds3000.tar.gz > /dev/null 2>&1
tar xfv tevii_ds3000.tar.gz > /dev/null 2>&1
sudo cp tevii_ds3000/dvb-fe-ds3000.fw /lib/firmware/ > /dev/null 2>&1
rm /tmp/tevii_ds3000.tar.gz > /dev/null 2>&1
rm -R /tmp/tevii_ds3000 > /dev/null 2>&1
Display More
Was mich wundert sind die Meldungen des Kernels beim Start / Restart von VDR - siehe das log von eben. Bei 1.7.28 habe ich die meines Wissens nicht.
Ich vermute ein Firmware Problem. Die Karte ist an sich ja da, schein aber interen wie aufgehängt zu sein. Ich weiß aber nicht was die Karte dazu veranlasst.
Loggn.de hatte gar mal ein Problem dass er nur über Kaltstart beheben konnte siehe:
Ich gebe heute Abend mal ssl über den router auf den HTPC frei. Gern auch mit Teamviewer aufn Server + weiter zum HTPC mit Putty.
Ich steige nicht dahinter was das problem ist da es mit VDR 1.7.28 wiegesagt tut.
Im News Feed habe ich bereits folgendes gepostet:
QuoteDisplay Moredoch hat es...
So hab ich installiert. Davor gings, Auf 2 systemen
Was verantlast VDR 1.7.41 hier beim start ?
Mar 22 17:02:19 testhtpc vdr: [1355] VNSI: Requesting clients to reload recordings list
Mar 22 17:09:01 testhtpc vdr: [1339] stopping plugin: wirbelscan
Mar 22 17:09:01 testhtpc vdr: [1339] stopping plugin: vnsiserver4
Mar 22 17:09:01 testhtpc vdr: [1355] VDR VNSI Server thread ended (pid=1339, tid=1355)
Mar 22 17:09:05 testhtpc kernel: [ 441.520920] usbcore: deregistering interface driver dw2102
Mar 22 17:09:05 testhtpc kernel: [ 441.556956] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
Mar 22 17:09:05 testhtpc kernel: [ 441.596968] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
Mar 22 17:09:05 testhtpc kernel: [ 441.645050] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 22 17:09:05 testhtpc kernel: [ 441.652561] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 22 17:09:05 testhtpc kernel: [ 441.652569] dw2102: start downloading DW210X firmware
Mar 22 17:09:05 testhtpc kernel: [ 441.804040] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 22 17:09:05 testhtpc kernel: [ 441.804123] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 22 17:09:05 testhtpc kernel: [ 441.804785] DVB: registering new adapter (TeVii S660 USB)
Mar 22 17:09:06 testhtpc kernel: [ 442.077347] dvb-usb: MAC address: 00:18:bd:5a:be:cf
Mar 22 17:09:06 testhtpc kernel: [ 442.082972] DS3000 chip version: 0.192 attached.
Mar 22 17:09:06 testhtpc kernel: [ 442.083576] dw2102: Attached ds3000+ds2020!
Mar 22 17:09:06 testhtpc kernel: [ 442.083576]
Mar 22 17:09:06 testhtpc kernel: [ 442.083585] DVB: registering adapter 0 frontend 0 (Montage Technology DS3000/TS2020)...Es wird irgendwas geladen...
Siehe ganzes Startlog:
Geh ich zurück auf 1.7.28 ...
direkt wieder Empfang
oot@testhtpc:/home/xbmc# femon -H
FE: Montage Technology DS3000/TS2020 (DVBS)
status SCVYL | signal 68% | snr 87% | ber 0 | unc 11 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCKund das passende log
Edit:
der VDR 1.7.41 macht auf jedenfalls irgendwas massiv anders und veranlasst das Laden einer FW die nix taugt.
Das Gerät wird offensichtlich mit anderer FW neu initialisiert beim neueren VDR. Da sieht es dann so aus:
status | signal 56% | snr 0% | ber -1 | unc 1279 |
status | signal 56% | snr 0% | ber -1 | unc 1279 |
status | signal 56% | snr 0% | ber -1 | unc 1279 |
status | signal 56% | snr 0% | ber -1 | unc 1279 |
status | signal 56% | snr 0% | ber -1 | unc 1279 |
status | signal 56% | snr 0% | ber -1 | unc 1279 |
status | signal 56% | snr 0% | ber -1 | unc 1279 |
status | signal 56% | snr 0% | ber -1 | unc 1279 |Edit:
okay ich begebe mich auf die Suche nach einem VDR Fehler Thread. Wenn ich was finde lösch ichs hier raus =) danke
Ist das hier eigentlich normal?
Edit:
Ich werde heute Abend nochmal platt machen. Ohne VDR und Ohne Firmware installieren.
Statt die Sourcen von dem Repo zu nehmen müsste ja auch
git clone git://git.gekrumbel.de/vdr.git
+ bauen wie oben
gehen? Oder?
Vielen herzlichen Dank euch.
Hallo und dnake für die Antwort!
nur Tuner 1, es ist nur ein kabel angeschlossen. Ich nehme an deswegen ist er auch im "warm state" was auch immer das bedeuten soll.
Und ja das tut 100%
nachdem ich nun beim 5. mal aufsetzen das problem wiederholt habe...
...Welcome to Ubuntu 12.10 (GNU/Linux 3.5.0-26-generic i686)...
Das komische... die TV Karte ist da, VDR Startet auch ganz normal aber die Karte an sich bekommt keinen Lock und zeigt ständig dieselben Meldungen bei
femon -H an
FE: Montage Technology DS3000/TS2020 (DVBS)
status | signal 90% | snr 0% | ber 0 | unc 768 |
status | signal 90% | snr 0% | ber 0 | unc 768 |
status | signal 90% | snr 0% | ber 0 | unc 768 |
status | signal 90% | snr 0% | ber 0 | unc 768 |
status | signal 90% | snr 0% | ber 0 | unc 768 |
TV Karte ist eine Tevii S480
more /var/log/syslog | grep dvb
liefert
Mar 25 08:12:16 ubuntu kernel: [ 12.998344] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 25 08:12:16 ubuntu kernel: [ 13.135803] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 25 08:12:16 ubuntu kernel: [ 13.294409] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 25 08:12:16 ubuntu kernel: [ 13.294454] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 25 08:12:16 ubuntu kernel: [ 13.531311] dvb-usb: MAC address: 00:18:bd:5a:c4:d9
Mar 25 08:12:16 ubuntu kernel: [ 13.539298] dvb-usb: schedule remote query interval to 150 msecs.
Mar 25 08:12:16 ubuntu kernel: [ 13.539300] dvb-usb: TeVii S660 USB successfully initialized and connected.
Mar 25 08:12:16 ubuntu kernel: [ 13.539316] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 25 08:12:16 ubuntu kernel: [ 13.540369] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 25 08:12:17 ubuntu kernel: [ 13.694325] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 25 08:12:17 ubuntu kernel: [ 13.694387] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 25 08:12:17 ubuntu kernel: [ 13.936089] dvb-usb: MAC address: 00:18:bd:5a:c4:da
Mar 25 08:12:17 ubuntu kernel: [ 13.940308] dvb-usb: schedule remote query interval to 150 msecs.
Mar 25 08:12:17 ubuntu kernel: [ 13.940311] dvb-usb: TeVii S660 USB successfully initialized and connected.
Mar 25 08:12:20 ubuntu kernel: [ 17.220345] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
Mar 25 08:12:20 ubuntu kernel: [ 17.226237] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
Mar 25 08:12:20 ubuntu kernel: [ 17.237999] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 25 08:12:20 ubuntu kernel: [ 17.239037] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 25 08:12:20 ubuntu kernel: [ 17.393535] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 25 08:12:20 ubuntu kernel: [ 17.393591] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 25 08:12:21 ubuntu kernel: [ 17.628303] dvb-usb: MAC address: 00:18:bd:5a:c4:d9
Mar 25 08:12:21 ubuntu kernel: [ 17.632898] dvb-usb: schedule remote query interval to 150 msecs.
Mar 25 08:12:21 ubuntu kernel: [ 17.632901] dvb-usb: TeVii S660 USB successfully initialized and connected.
Mar 25 08:12:21 ubuntu kernel: [ 17.632915] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 25 08:12:21 ubuntu kernel: [ 17.634032] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 25 08:12:21 ubuntu kernel: [ 17.785429] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 25 08:12:21 ubuntu kernel: [ 17.785499] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 25 08:12:21 ubuntu kernel: [ 18.026832] dvb-usb: MAC address: 00:18:bd:5a:c4:da
Mar 25 08:12:21 ubuntu kernel: [ 18.031170] dvb-usb: schedule remote query interval to 150 msecs.
Mar 25 08:12:21 ubuntu kernel: [ 18.031172] dvb-usb: TeVii S660 USB successfully initialized and connected.
Mar 25 08:12:21 ubuntu vdr: [1269] probing /dev/dvb/adapter0/frontend0
Mar 25 08:12:21 ubuntu vdr: [1269] probing /dev/dvb/adapter1/frontend0
VDR Start funzt
root@ubuntu:/home/xbmc# /etc/init.d/vdr restart
Stopping VDR
Starting VDR with plugins: vnsiserver4 wirbelscan
root@ubuntu:/home/xbmc# /etc/init.d/vdr status
* VDR is running
root@ubuntu:/home/xbmc#
Der Neustart von VDR hat im Syslog folgendes Ergebnis
Mar 25 08:17:01 ubuntu CRON[2089]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 25 08:18:34 ubuntu vdr: [1269] stopping plugin: wirbelscan
Mar 25 08:18:34 ubuntu vdr: [1269] stopping plugin: vnsiserver4
Mar 25 08:18:34 ubuntu vdr: [1281] VDR VNSI Server thread ended (pid=1269, tid=1281)
Mar 25 08:18:39 ubuntu kernel: [ 395.849385] usbcore: deregistering interface driver dw2102
Mar 25 08:18:39 ubuntu kernel: [ 395.868757] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
Mar 25 08:18:39 ubuntu kernel: [ 395.896212] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
Mar 25 08:18:39 ubuntu kernel: [ 395.907320] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 25 08:18:39 ubuntu kernel: [ 395.909163] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 25 08:18:39 ubuntu kernel: [ 395.909166] dw2102: start downloading DW210X firmware
Mar 25 08:18:39 ubuntu kernel: [ 396.063491] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 25 08:18:39 ubuntu kernel: [ 396.063535] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 25 08:18:39 ubuntu kernel: [ 396.063851] DVB: registering new adapter (TeVii S660 USB)
Mar 25 08:18:39 ubuntu kernel: [ 396.308780] dvb-usb: MAC address: 00:18:bd:5a:c4:d9
Mar 25 08:18:39 ubuntu kernel: [ 396.314031] DS3000 chip version: 0.192 attached.
Mar 25 08:18:39 ubuntu kernel: [ 396.314401] dw2102: Attached ds3000+ds2020!
Mar 25 08:18:39 ubuntu kernel: [ 396.314401]
Mar 25 08:18:39 ubuntu kernel: [ 396.314410] DVB: registering adapter 0 frontend 0 (Montage Technology DS3000/TS2020)...
Mar 25 08:18:39 ubuntu kernel: [ 396.315253] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.0/0000:02:00.1/usb3/3-1/input/input24
Mar 25 08:18:39 ubuntu kernel: [ 396.315319] dvb-usb: schedule remote query interval to 150 msecs.
Mar 25 08:18:39 ubuntu kernel: [ 396.315324] dvb-usb: TeVii S660 USB successfully initialized and connected.
Mar 25 08:18:39 ubuntu kernel: [ 396.315351] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 25 08:18:39 ubuntu kernel: [ 396.319939] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 25 08:18:39 ubuntu kernel: [ 396.319943] dw2102: start downloading DW210X firmware
Mar 25 08:18:39 ubuntu kernel: [ 396.471644] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 25 08:18:39 ubuntu kernel: [ 396.471707] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 25 08:18:39 ubuntu kernel: [ 396.472041] DVB: registering new adapter (TeVii S660 USB)
Mar 25 08:18:40 ubuntu kernel: [ 396.718827] dvb-usb: MAC address: 00:18:bd:5a:c4:da
Mar 25 08:18:40 ubuntu kernel: [ 396.722100] DS3000 chip version: 0.192 attached.
Mar 25 08:18:40 ubuntu kernel: [ 396.722598] dw2102: Attached ds3000+ds2020!
Mar 25 08:18:40 ubuntu kernel: [ 396.722598]
Mar 25 08:18:40 ubuntu kernel: [ 396.722607] DVB: registering adapter 1 frontend 0 (Montage Technology DS3000/TS2020)...
Mar 25 08:18:40 ubuntu kernel: [ 396.724865] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.0/0000:02:00.3/usb4/4-1/input/input25
Mar 25 08:18:40 ubuntu kernel: [ 396.724982] dvb-usb: schedule remote query interval to 150 msecs.
Mar 25 08:18:40 ubuntu kernel: [ 396.724988] dvb-usb: TeVii S660 USB successfully initialized and connected.
Mar 25 08:18:40 ubuntu kernel: [ 396.725027] usbcore: registered new interface driver dw2102
Mar 25 08:18:40 ubuntu vdr: [2157] VDR version 1.7.42 started
Mar 25 08:18:40 ubuntu vdr: [2157] codeset is 'UTF-8' - known
Mar 25 08:18:40 ubuntu vdr: [2157] found 28 locales in /usr/share/locale
Mar 25 08:18:40 ubuntu vdr: [2157] loading plugin: /usr/lib/vdr/plugins/libvdr-vnsiserver4.so.1.7.41
Mar 25 08:18:40 ubuntu vdr: [2157] loading plugin: /usr/lib/vdr/plugins/libvdr-wirbelscan.so.1.7.41
Mar 25 08:18:40 ubuntu vdr: [2157] loading /etc/vdr/setup.conf
Mar 25 08:18:40 ubuntu vdr: [2157] loading /etc/vdr/sources.conf
Mar 25 08:18:40 ubuntu vdr: [2157] loading /etc/vdr/diseqc.conf
Mar 25 08:18:40 ubuntu vdr: [2157] loading /etc/vdr/scr.conf
Mar 25 08:18:40 ubuntu vdr: [2157] loading /etc/vdr/channels.conf
Mar 25 08:18:40 ubuntu vdr: [2157] deleting duplicate channel EinsPlus;ARD:10744:HC56M2S0:S19.2E:22000:301=2:302=deu@3:304:0:28723:1:1051:0
Mar 25 08:18:40 ubuntu vdr: [2157] deleting duplicate channel arte;ARD:10743:HC56M2S0:S19.2E:22000:401=2:402=deu@3,403=fra@3:404:0:28724:1:1051:0
Mar 25 08:18:40 ubuntu vdr: [2157] deleting duplicate channel ORF1 HD;ORF:11303:HC23M5O35S1:S19.2E:22000:1920=27:1921=deu@4,1922=eng@4;1923=deu@106:1925:648,D05,D95,1702,1833,9C4:4911:1:1007:0
Mar 25 08:18:40 ubuntu vdr: [2157] deleting duplicate channel ORF2 HD;ORF:11303:HC23M5O35S1:S19.2E:22000:2920=27:2921=deu@4,2922=deu@4;2923=deu@106:2925:648,D05,D95,1702,1833,9C4:4912:1:1007:0
Mar 25 08:18:40 ubuntu vdr: [2157] loading /etc/vdr/svdrphosts.conf
Mar 25 08:18:40 ubuntu vdr: [2157] loading /etc/vdr/keymacros.conf
Mar 25 08:18:40 ubuntu vdr: [2157] registered source parameters for 'A - ATSC'
Mar 25 08:18:40 ubuntu vdr: [2157] registered source parameters for 'C - DVB-C'
Mar 25 08:18:40 ubuntu vdr: [2157] registered source parameters for 'S - DVB-S'
Mar 25 08:18:40 ubuntu vdr: [2157] registered source parameters for 'T - DVB-T'
Mar 25 08:18:40 ubuntu vdr: [2157] probing /dev/dvb/adapter0/frontend0
Mar 25 08:18:40 ubuntu vdr: [2157] creating cDvbDevice
Mar 25 08:18:40 ubuntu vdr: [2157] new device number 1
Mar 25 08:18:40 ubuntu vdr: [2159] video directory scanner thread started (pid=2157, tid=2159, prio=high)
Mar 25 08:18:40 ubuntu vdr: [2159] video directory scanner thread ended (pid=2157, tid=2159)
Mar 25 08:18:40 ubuntu vdr: [2158] video directory scanner thread started (pid=2157, tid=2158, prio=high)
Mar 25 08:18:40 ubuntu vdr: [2158] video directory scanner thread ended (pid=2157, tid=2158)
Mar 25 08:18:40 ubuntu vdr: [2160] epg data reader thread started (pid=2157, tid=2160, prio=high)
Mar 25 08:18:40 ubuntu vdr: [2160] reading EPG data from /var/cache/vdr/epg.data
Mar 25 08:18:40 ubuntu vdr: [2160] epg data reader thread ended (pid=2157, tid=2160)
Mar 25 08:18:40 ubuntu vdr: [2157] frontend 0/0 provides DVB-S,DVB-S2 with QPSK ("Montage Technology DS3000/TS2020")
Mar 25 08:18:40 ubuntu vdr: [2162] tuner on frontend 0/0 thread started (pid=2157, tid=2162, prio=high)
Mar 25 08:18:40 ubuntu vdr: [2163] section handler thread started (pid=2157, tid=2163, prio=low)
Mar 25 08:18:40 ubuntu vdr: [2162] cTimeMs: using monotonic clock (resolution is 1 ns)
Mar 25 08:18:40 ubuntu vdr: [2157] probing /dev/dvb/adapter1/frontend0
Mar 25 08:18:40 ubuntu vdr: [2157] creating cDvbDevice
Mar 25 08:18:40 ubuntu vdr: [2157] new device number 2
Mar 25 08:18:40 ubuntu vdr: [2157] frontend 1/0 provides DVB-S,DVB-S2 with QPSK ("Montage Technology DS3000/TS2020")
Mar 25 08:18:40 ubuntu vdr: [2165] tuner on frontend 1/0 thread started (pid=2157, tid=2165, prio=high)
Mar 25 08:18:40 ubuntu vdr: [2157] found 2 DVB devices
Mar 25 08:18:40 ubuntu vdr: [2157] initializing plugin: vnsiserver4 (0.9.2): VDR-Network-Streaming-Interface (VNSI) Server
Mar 25 08:18:40 ubuntu vdr: [2166] section handler thread started (pid=2157, tid=2166, prio=low)
Mar 25 08:18:40 ubuntu vdr: [2157] initializing plugin: wirbelscan (0.0.7): DVB and pvrinput channel scan for VDR
Mar 25 08:18:40 ubuntu vdr: [2157] setting primary device to 1
Mar 25 08:18:40 ubuntu vdr: [2157] device 1 has no MPEG decoder
Mar 25 08:18:40 ubuntu vdr: [2157] assuming manual start of VDR
Mar 25 08:18:40 ubuntu vdr: [2157] setting current skin to "lcars"
Mar 25 08:18:40 ubuntu vdr: [2157] loading /etc/vdr/themes/lcars-default.theme
Mar 25 08:18:40 ubuntu vdr: [2157] starting plugin: vnsiserver4
Mar 25 08:18:40 ubuntu vdr: [2157] VNSI: VNSI Server started
Mar 25 08:18:40 ubuntu vdr: [2157] VNSI: Channel streaming timeout: 10 seconds
Mar 25 08:18:40 ubuntu vdr: [2157] starting plugin: wirbelscan
Mar 25 08:18:40 ubuntu vdr: [2167] VDR VNSI Server thread started (pid=2157, tid=2167, prio=high)
Mar 25 08:18:40 ubuntu vdr: [2157] switching to channel 1
Mar 25 08:18:40 ubuntu vdr: [2157] info: Kanal nicht verfügbar!
Mar 25 08:18:40 ubuntu vdr: [2157] ERROR: no OSD provider available - using dummy OSD!
Mar 25 08:18:40 ubuntu vdr: [2167] VNSI-Error: Invalid or missing '/etc/vdr/plugins/vnsiserver4/allowed_hosts.conf'. falling back to 'svdrphosts.conf'.
Mar 25 08:18:40 ubuntu vdr: [2167] VNSI-Error: Invalid or missing /etc/vdr/plugins/vnsiserver4/../svdrphosts.conf. Adding 127.0.0.1 to list of allowed hosts.
Mar 25 08:18:40 ubuntu vdr: [2167] VNSI: Client with ID 0 connected: 127.0.0.1:41031
Mar 25 08:18:40 ubuntu vdr: [2170] VNSI: Welcome client 'XBMC Media Center' with protocol version '4'
Mar 25 08:18:40 ubuntu vdr: [2167] VNSI: Requesting clients to reload channel list
Mar 25 08:18:42 ubuntu vdr: [2157] setting watchdog timer to 60 seconds
Mar 25 08:18:42 ubuntu vdr: [2157] OSD size changed to 720x480 @ 1
Mar 25 08:18:42 ubuntu vdr: [2157] ERROR: no OSD provider available - using dummy OSD!
Mar 25 08:18:48 ubuntu vdr: [2157] max. latency time 1 seconds
Hallo Zusammen. Meine Tevii zickt mit neuer VDR Version - kein Signal. Es scheint als wird eine andere Firmware beim Start geladen noch bevor der VDR was ausspuckt.
https://dl.dropbox.com/u/21136636/syslog
TV Karte bekommt kein Lock. VDR Startet (ohne jedes Plugin)
Mar 22 19:16:45 ubuntu kernel: [ 106.655657] usbcore: deregistering interface driver dw2102
Mar 22 19:16:45 ubuntu kernel: [ 106.678652] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
Mar 22 19:16:45 ubuntu kernel: [ 106.718057] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
Mar 22 19:16:45 ubuntu kernel: [ 106.728180] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 22 19:16:45 ubuntu kernel: [ 106.729075] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 22 19:16:45 ubuntu kernel: [ 106.729078] dw2102: start downloading DW210X firmware
Mar 22 19:16:45 ubuntu kernel: [ 106.877611] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 22 19:16:45 ubuntu kernel: [ 106.877656] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 22 19:16:45 ubuntu kernel: [ 106.878009] DVB: registering new adapter (TeVii S660 USB)
Mar 22 19:16:45 ubuntu kernel: [ 107.119846] dvb-usb: MAC address: 00:18:bd:5a:c4:d9
Mar 22 19:16:45 ubuntu kernel: [ 107.124696] DS3000 chip version: 0.192 attached.
Mar 22 19:16:45 ubuntu kernel: [ 107.125070] dw2102: Attached ds3000+ds2020!
Mar 22 19:16:45 ubuntu kernel: [ 107.125070]
Mar 22 19:16:45 ubuntu kernel: [ 107.125075] DVB: registering adapter 0 frontend 0 (Montage Technology DS3000/TS2020)...
Mar 22 19:16:45 ubuntu kernel: [ 107.125918] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.0/0000:02:00.1/usb3/3-1/input/input24
Mar 22 19:16:45 ubuntu kernel: [ 107.125984] dvb-usb: schedule remote query interval to 150 msecs.
Mar 22 19:16:45 ubuntu kernel: [ 107.125991] dvb-usb: TeVii S660 USB successfully initialized and connected.
Mar 22 19:16:45 ubuntu kernel: [ 107.126021] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 22 19:16:45 ubuntu kernel: [ 107.129866] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 22 19:16:45 ubuntu kernel: [ 107.129869] dw2102: start downloading DW210X firmware
Mar 22 19:16:45 ubuntu kernel: [ 107.281545] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 22 19:16:45 ubuntu kernel: [ 107.281610] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 22 19:16:45 ubuntu kernel: [ 107.281922] DVB: registering new adapter (TeVii S660 USB)
Mar 22 19:16:46 ubuntu kernel: [ 107.528855] dvb-usb: MAC address: 00:18:bd:5a:c4:da
Mar 22 19:16:46 ubuntu kernel: [ 107.532091] DS3000 chip version: 0.192 attached.
Mar 22 19:16:46 ubuntu kernel: [ 107.532455] dw2102: Attached ds3000+ds2020!
Mar 22 19:16:46 ubuntu kernel: [ 107.532455]
Mar 22 19:16:46 ubuntu kernel: [ 107.532463] DVB: registering adapter 1 frontend 0 (Montage Technology DS3000/TS2020)...
Mar 22 19:16:46 ubuntu kernel: [ 107.533682] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.0/0000:02:00.3/usb4/4-1/input/input25
Mar 22 19:16:46 ubuntu kernel: [ 107.533752] dvb-usb: schedule remote query interval to 150 msecs.
Mar 22 19:16:46 ubuntu kernel: [ 107.533758] dvb-usb: TeVii S660 USB successfully initialized and connected.
Mar 22 19:16:46 ubuntu kernel: [ 107.533797] usbcore: registered new interface driver dw2102
Vorschläge? Wie kann ich noch detaillierter mitloggen?
Beim zweiten System scheint sich das Problem durch wiederholtes deinstallen - Springen zu 1.7.28 und erneuter 1.7.41 install verflüchtigt zu haben.
Edit: 1.7.41 gepurged, 1.7.28 installiert
https://dl.dropbox.com/u/21136636/syslog_altvdr
Selber Restart
Mar 22 19:39:51 ubuntu vdr: [1371] retuning due to modification of channel 1
Mar 22 19:39:51 ubuntu vdr: [1371] switching to channel 1
Mar 22 19:39:54 ubuntu ntpdate[2179]: adjust time server 91.189.94.4 offset 0.110708 sec
Mar 22 19:40:05 ubuntu vdr: [1371] saved setup to /var/lib/vdr/setup.conf
Mar 22 19:40:05 ubuntu vdr: [1578] section handler thread ended (pid=1371, tid=1578)
Mar 22 19:40:05 ubuntu vdr: [1577] tuner on frontend 0/0 thread ended (pid=1371, tid=1577)
Mar 22 19:40:06 ubuntu vdr: [1581] section handler thread ended (pid=1371, tid=1581)
Mar 22 19:40:06 ubuntu vdr: [1580] tuner on frontend 1/0 thread ended (pid=1371, tid=1580)
Mar 22 19:40:06 ubuntu vdr: [1371] max. latency time 1 seconds
Mar 22 19:40:06 ubuntu vdr: [1371] caught signal 15
Mar 22 19:40:06 ubuntu vdr: [1371] exiting, exit code 0
Mar 22 19:40:10 ubuntu vdr: [2269] VDR version 1.7.28 started
Mar 22 19:40:10 ubuntu vdr: [2269] switched to user 'vdr'
Mar 22 19:40:10 ubuntu vdr: [2269] codeset is 'UTF-8' - known
Mar 22 19:40:10 ubuntu vdr: [2269] found 28 locales in /usr/share/locale
Mar 22 19:40:10 ubuntu vdr: [2269] loading /var/lib/vdr/setup.conf
Mar 22 19:40:10 ubuntu vdr: [2269] loading /var/lib/vdr/sources.conf
Mar 22 19:40:10 ubuntu vdr: [2269] loading /var/lib/vdr/diseqc.conf
Mar 22 19:40:10 ubuntu vdr: [2269] loading /var/lib/vdr/scr.conf
Mar 22 19:40:10 ubuntu vdr: [2269] loading /var/lib/vdr/channels.conf
Mar 22 19:40:10 ubuntu vdr: [2269] loading /var/lib/vdr/commands.conf
Mar 22 19:40:10 ubuntu vdr: [2269] loading /var/lib/vdr/reccmds.conf
Mar 22 19:40:10 ubuntu vdr: [2269] loading /var/lib/vdr/svdrphosts.conf
Mar 22 19:40:10 ubuntu vdr: [2269] loading /var/lib/vdr/keymacros.conf
Mar 22 19:40:10 ubuntu vdr: [2269] registered source parameters for 'A - ATSC'
Mar 22 19:40:10 ubuntu vdr: [2269] registered source parameters for 'C - DVB-C'
Mar 22 19:40:10 ubuntu vdr: [2271] video directory scanner thread started (pid=2269, tid=2271)
Mar 22 19:40:10 ubuntu vdr: [2270] video directory scanner thread started (pid=2269, tid=2270)
Mar 22 19:40:10 ubuntu vdr: [2269] registered source parameters for 'S - DVB-S'
Mar 22 19:40:10 ubuntu vdr: [2271] video directory scanner thread ended (pid=2269, tid=2271)
Mar 22 19:40:10 ubuntu vdr: [2269] registered source parameters for 'T - DVB-T'
Mar 22 19:40:10 ubuntu vdr: [2270] video directory scanner thread ended (pid=2269, tid=2270)
Mar 22 19:40:10 ubuntu vdr: [2272] epg data reader thread started (pid=2269, tid=2272)
Mar 22 19:40:10 ubuntu vdr: [2272] reading EPG data from /var/cache/vdr/epg.data
Mar 22 19:40:10 ubuntu vdr: [2269] probing /dev/dvb/adapter0/frontend0
Mar 22 19:40:10 ubuntu vdr: [2269] creating cDvbDevice
Mar 22 19:40:10 ubuntu vdr: [2269] new device number 1
Mar 22 19:40:10 ubuntu vdr: [2272] epg data reader thread ended (pid=2269, tid=2272)
Mar 22 19:40:10 ubuntu vdr: [2269] frontend 0/0 provides DVB-S,DVB-S2 with QPSK ("Montage Technology DS3000/TS2020")
Mar 22 19:40:10 ubuntu vdr: [2275] section handler thread started (pid=2269, tid=2275)
Mar 22 19:40:10 ubuntu vdr: [2274] tuner on frontend 0/0 thread started (pid=2269, tid=2274)
Mar 22 19:40:10 ubuntu vdr: [2274] cTimeMs: using monotonic clock (resolution is 1 ns)
Mar 22 19:40:10 ubuntu vdr: [2269] probing /dev/dvb/adapter1/frontend0
Mar 22 19:40:10 ubuntu vdr: [2269] creating cDvbDevice
Mar 22 19:40:10 ubuntu vdr: [2269] new device number 2
Mar 22 19:40:10 ubuntu vdr: [2269] frontend 1/0 provides DVB-S,DVB-S2 with QPSK ("Montage Technology DS3000/TS2020")
Mar 22 19:40:10 ubuntu vdr: [2277] tuner on frontend 1/0 thread started (pid=2269, tid=2277)
Mar 22 19:40:10 ubuntu vdr: [2269] found 2 DVB devices
Mar 22 19:40:10 ubuntu vdr: [2278] section handler thread started (pid=2269, tid=2278)
Mar 22 19:40:10 ubuntu vdr: [2269] setting primary device to 1
Mar 22 19:40:10 ubuntu vdr: [2269] device 1 has no MPEG decoder
Mar 22 19:40:10 ubuntu vdr: [2269] assuming manual start of VDR
Mar 22 19:40:10 ubuntu vdr: [2269] SVDRP listening on port 6419
Mar 22 19:40:10 ubuntu vdr: [2269] setting current skin to "sttng"
Mar 22 19:40:10 ubuntu vdr: [2269] loading /var/lib/vdr/themes/sttng-default.theme
Mar 22 19:40:10 ubuntu vdr: [2269] ERROR (lirc.c,48): /dev/null: Verbindungsaufbau abgelehnt
Mar 22 19:40:10 ubuntu vdr: [2269] ERROR: remote control LIRC not ready!
Mar 22 19:40:10 ubuntu vdr: [2269] switching to channel 1
Mar 22 19:40:10 ubuntu vdr: [2269] setting watchdog timer to 60 seconds
Mar 22 19:40:10 ubuntu vdr: [2269] OSD size changed to 720x480 @ 1
Mar 22 19:40:10 ubuntu vdr: [2269] ERROR: no OSD provider available - using dummy OSD!
Mar 22 19:40:11 ubuntu vdr: [2275] changing pids of channel 1 from 163+163=2:104=deu@4;106=deu@106:0:105 to 163+163=2:104=deu@3;106=deu@106:110=deu:105
Mar 22 19:40:11 ubuntu vdr: [2269] retuning due to modification of channel 1
Mar 22 19:40:11 ubuntu vdr: [2269] switching to channel 1
Mar 22 19:40:12 ubuntu vdr: [2275] changing name of channel 25 from 'Super RTL,S RTL;RTL World' to 'SUPER RTL,;RTL World'
Mar 22 19:40:12 ubuntu vdr: [2275] creating new channel 'Channel 21,;RTL World' on S19.2E transponder 112187 with id 1-1089-12080-0
Mar 22 19:40:12 ubuntu vdr: [2275] creating new channel 'SUPER RTL CH,;RTL' on S19.2E transponder 112187 with id 1-1089-12041-0
Mar 22 19:40:12 ubuntu vdr: [2275] creating new channel 'RTLNITRO,;RTL' on S19.2E transponder 112187 with id 1-1089-12061-0
Mar 22 19:40:12 ubuntu vdr: [2275] creating new channel 'RTL HB NDS,;RTL World' on S19.2E transponder 112187 with id 1-1089-12005-0
Mar 22 19:40:12 ubuntu vdr: [2275] creating new channel 'RTL Regional NRW,;RTL World' on S19.2E transponder 112187 with id 1-1089-12004-0
Mar 22 19:40:12 ubuntu vdr: [2275] creating new channel 'RTL FS,;RTL World' on S19.2E transponder 112187 with id 1-1089-12006-0
Mar 22 19:40:12 ubuntu vdr: [2275] creating new channel 'RTL Living,;RTL' on S19.2E transponder 112187 with id 1-1089-12030-0
Mar 22 19:40:12 ubuntu vdr: [2275] creating new channel 'Channel 21 ALT,;CBC' on S19.2E transponder 112187 with id 1-1089-12095-0
Mar 22 19:40:12 ubuntu vdr: [2275] changing pids of channel 4 from 166+166=2:128=deu@4:0:68 to 166+166=2:128=deu@3:0:68
Mar 22 19:40:12 ubuntu vdr: [2275] changing pids of channel 1003 from 0+0=0:0:0:0 to 163+163=2:104=deu@3:0:105
Mar 22 19:40:13 ubuntu vdr: [2275] changing pids of channel 1005 from 0+0=0:0:0:0 to 163+163=2:104=deu@3:0:105
Mar 22 19:40:14 ubuntu vdr: [2275] changing pids of channel 1006 from 0+0=0:0:0:0 to 301+301=2:303=deu@3:0:0
Mar 22 19:40:14 ubuntu vdr: [2275] changing caids of channel 1006 from 0 to 1702,1833,9C4,1837,D05,D95,648,98C
Mar 22 19:40:14 ubuntu vdr: [2275] changing pids of channel 25 from 165+165=2:120=deu@4:0:65 to 165+165=2:120=deu@3:0:65
Mar 22 19:40:15 ubuntu vdr: [2275] changing pids of channel 1001 from 0+0=0:0:0:0 to 172+172=2:145=deu@3:0:82
Mar 22 19:40:15 ubuntu vdr: [2275] changing pids of channel 26 from 167+167=2:136=deu@4:0:71 to 167+167=2:136=deu@3:74=deu:71
Mar 22 19:40:16 ubuntu vdr: [2275] changing pids of channel 1002 from 0+0=0:0:0:0 to 173+173=2:146=deu@3:0:84
Mar 22 19:40:16 ubuntu vdr: [2269] max. latency time 1 seconds
Mar 22 19:40:16 ubuntu vdr: [2275] changing pids of channel 1000 from 0+0=0:0:0:0 to 168+168=2:137=@3:0:70
Mar 22 19:40:17 ubuntu vdr: [2275] changing pids of channel 38 from 169+169=2:73=deu@4:0:80 to 169+169=2:73=deu@3:0:80
Mar 22 19:40:17 ubuntu vdr: [2275] changing pids of channel 1007 from 0+0=0:0:0:0 to 168+168=2:137=deu@3:0:70
Mar 22 19:40:19 ubuntu vdr: [2275] changing pids of channel 1004 from 0+0=0:0:0:0 to 163+163=2:104=deu@3:0:105
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 1 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 4 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 25 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 26 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 38 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 1000 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 1001 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 1002 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 1003 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 1004 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 1005 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 1006 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:25 ubuntu vdr: [2275] changing transponder data of channel 1007 from 12187:hC34:S19.2E:27500 to 12187:HC34M2S0:S19.2E:27500
Mar 22 19:40:26 ubuntu vdr: [2269] retuning due to modification of channel 1
Mar 22 19:40:26 ubuntu vdr: [2269] switching to channel 1
Mar 22 19:40:28 ubuntu udevd[447]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00000102sv000019DAsd0000A186bc03sc80i00' [471]
Mar 22 19:40:28 ubuntu udevd[447]: '/sbin/modprobe -bv pci:v00008086d00000102sv000019DAsd0000A186bc03sc80i00' [471] terminated by signal 9 (Killed)
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel 'ORF SPORT+,;ORF' on S1.0W transponder 111261 with id 1-1003-13221-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel 'VOLKS TV,;-' on S1.0W transponder 111261 with id 1-1003-13222-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel 'ATV2,;ATV' on S1.0W transponder 111261 with id 1-1003-13223-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel 'Service 13224,;ORS' on S1.0W transponder 111261 with id 1-1003-13224-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel 'Schau TV,;-' on S1.0W transponder 111261 with id 1-1003-13225-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel 'Starparadies AT,;-' on S1.0W transponder 111261 with id 1-1003-13226-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel 'DAF Neu,;-' on S1.0W transponder 111261 with id 1-1003-13227-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel 'TELE 5 Austria,;ATV' on S1.0W transponder 111261 with id 1-1003-13228-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel 'MELODIE Express,;ORS' on S1.0W transponder 111261 with id 1-1003-13229-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel 'Service 13230,;ORS' on S1.0W transponder 111261 with id 1-1003-13230-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel '.,;ORS' on S1.0W transponder 111261 with id 1-1003-13231-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel '.,;ORS' on S1.0W transponder 111261 with id 1-1003-13232-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel '.,;ORS' on S1.0W transponder 111261 with id 1-1003-13233-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel '.,;ORS' on S1.0W transponder 111261 with id 1-1003-13234-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel '.,;ORS' on S1.0W transponder 111261 with id 1-1003-13235-0
Mar 22 19:41:13 ubuntu vdr: [2275] creating new channel 'Service 13236,;ORS' on S1.0W transponder 111261 with id 1-1003-13236-0
Mar 22 19:41:13 ubuntu vdr: [2275] changing pids of channel 1008 from 0+0=0:0:0:0 to 2210+2210=2:2211=deu@4:0:2215
Mar 22 19:41:13 ubuntu vdr: [2275] changing caids of channel 1008 from 0 to D95,648,D05,9C4,1702,1833,98C
Mar 22 19:41:14 ubuntu vdr: [2275] changing pids of channel 1009 from 0+0=0:0:0:0 to 2220+2220=2:0:0:0
Mar 22 19:41:15 ubuntu vdr: [2275] changing pids of channel 1010 from 0+0=0:0:0:0 to 2230+2230=2:2231=deu@4:0:2235
Mar 22 19:41:15 ubuntu vdr: [2275] changing caids of channel 1010 from 0 to D05,D95,648,9C4,1702,1833,98C
Mar 22 19:41:15 ubuntu vdr: [2275] changing pids of channel 1012 from 0+0=0:0:0:0 to 2250+2250=2:2251=deu@3:0:2255
Mar 22 19:41:16 ubuntu vdr: [2275] changing pids of channel 1013 from 0+0=0:0:0:0 to 2260+2260=2:2261=deu@4:0:0
Mar 22 19:41:16 ubuntu vdr: [2275] changing pids of channel 1014 from 0+0=0:0:0:0 to 2270+2270=2:2271=deu@4:0:0
Mar 22 19:41:17 ubuntu vdr: [2275] changing pids of channel 1015 from 0+0=0:0:0:0 to 2280+2280=2:2281=deu@4:0:2285
Mar 22 19:41:17 ubuntu vdr: [2275] changing pids of channel 1016 from 0+0=0:0:0:0 to 2290+2290=2:2291=deu@4:0:0
Mar 22 19:41:20 ubuntu vdr: [2277] frontend 1/0 timed out while tuning to channel 101, tp 111389
und
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 68% | snr 87% | ber 0 | unc 0 | FE_HAS_LOCK
@seahawk
https://dl.dropbox.com/u/21136636/syslog
das ist das ganze Syslog.
Kann ich noch mehr mitloggen?
Edit: Ich mach nen eigenen Thread für auf
VDR 1.7.41 - Tevii / FW Problem beim Start
Hilfe wird dankend entgegengenommen
okay... jetzt bin ich wieder an dem Punkt von Vorher...
VDR kommt hoch, aber das System baut Scheiße.
Stoppe ich VDR mit /etc/init.d/vdr stop
so kommt
Mar 22 19:01:15 ubuntu vdr: [2319] stopping plugin: wirbelscan
Mar 22 19:01:15 ubuntu vdr: [2319] stopping plugin: vnsiserver4
Mar 22 19:01:15 ubuntu vdr: [2334] VDR VNSI Server thread ended (pid=2319, tid=2334)
Starte ich den VDR steigt er direkt noch vor der ersten log ausgabe von VDR selbst mit
Mar 22 19:01:37 ubuntu kernel: [ 316.183819] usbcore: deregistering interface driver dw2102
Mar 22 19:01:37 ubuntu kernel: [ 316.215974] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
Mar 22 19:01:37 ubuntu kernel: [ 316.259992] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
Mar 22 19:01:37 ubuntu kernel: [ 316.272037] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 22 19:01:37 ubuntu kernel: [ 316.273328] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 22 19:01:37 ubuntu kernel: [ 316.273331] dw2102: start downloading DW210X firmware
Mar 22 19:01:37 ubuntu kernel: [ 316.419574] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 22 19:01:37 ubuntu kernel: [ 316.419620] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 22 19:01:37 ubuntu kernel: [ 316.419980] DVB: registering new adapter (TeVii S660 USB)
Mar 22 19:01:37 ubuntu kernel: [ 316.656416] dvb-usb: MAC address: 00:18:bd:5a:c4:d9
Mar 22 19:01:37 ubuntu kernel: [ 316.660298] DS3000 chip version: 0.192 attached.
Mar 22 19:01:37 ubuntu kernel: [ 316.660668] dw2102: Attached ds3000+ds2020!
Mar 22 19:01:37 ubuntu kernel: [ 316.660668]
ein...
Edit: Das macht er auch ohne irgendwelche Plugins.
Hier mal der Auszug. Ich habe etwas pause gelasen ziwschen dem Stoppen und Starten des VDR. Die Ubuntu Kernel Sachen kommen direkt beim VDR 1.7.41 Start
QuoteDisplay More
Mar 22 19:07:05 ubuntu vdr: [2712] new device number 2
Mar 22 19:07:05 ubuntu vdr: [2712] frontend 1/0 provides DVB-S,DVB-S2 with QPSK ("Montage Technology DS3000/TS2020")
Mar 22 19:07:05 ubuntu vdr: [2720] tuner on frontend 1/0 thread started (pid=2712, tid=2720, prio=high)
Mar 22 19:07:05 ubuntu vdr: [2712] found 2 DVB devices
Mar 22 19:07:05 ubuntu vdr: [2721] section handler thread started (pid=2712, tid=2721, prio=low)
Mar 22 19:07:05 ubuntu vdr: [2712] setting primary device to 1
Mar 22 19:07:05 ubuntu vdr: [2712] device 1 has no MPEG decoder
Mar 22 19:07:05 ubuntu vdr: [2712] assuming manual start of VDR
Mar 22 19:07:05 ubuntu vdr: [2712] setting current skin to "lcars"
Mar 22 19:07:05 ubuntu vdr: [2712] loading /etc/vdr/themes/lcars-default.theme
Mar 22 19:07:05 ubuntu vdr: [2712] switching to channel 1
Mar 22 19:07:05 ubuntu vdr: [2712] info: Kanal nicht verfügbar!
Mar 22 19:07:05 ubuntu vdr: [2712] ERROR: no OSD provider available - using dummy OSD!
Mar 22 19:07:07 ubuntu vdr: [2712] setting watchdog timer to 60 seconds
Mar 22 19:07:07 ubuntu vdr: [2712] OSD size changed to 720x480 @ 1
Mar 22 19:07:07 ubuntu vdr: [2712] ERROR: no OSD provider available - using dummy OSD!
Mar 22 19:07:13 ubuntu vdr: [2712] max. latency time 1 seconds
Mar 22 19:07:29 ubuntu vdr: [2712] saved setup to /etc/vdr/setup.conf
Mar 22 19:07:29 ubuntu vdr: [2718] section handler thread ended (pid=2712, tid=2718)
Mar 22 19:07:29 ubuntu vdr: [2717] tuner on frontend 0/0 thread ended (pid=2712, tid=2717)
Mar 22 19:07:30 ubuntu vdr: [2721] section handler thread ended (pid=2712, tid=2721)
Mar 22 19:07:30 ubuntu vdr: [2720] tuner on frontend 1/0 thread ended (pid=2712, tid=2720)
Mar 22 19:07:30 ubuntu vdr: [2712] max. latency time 1 seconds
Mar 22 19:07:30 ubuntu vdr: [2712] caught signal 15
Mar 22 19:07:30 ubuntu vdr: [2712] exiting, exit code 0
Mar 22 19:07:52 ubuntu kernel: [ 691.266951] usbcore: deregistering interface driver dw2102
Mar 22 19:07:52 ubuntu kernel: [ 691.302497] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
Mar 22 19:07:52 ubuntu kernel: [ 691.349609] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
Mar 22 19:07:52 ubuntu kernel: [ 691.361374] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 22 19:07:52 ubuntu kernel: [ 691.362297] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 22 19:07:52 ubuntu kernel: [ 691.362300] dw2102: start downloading DW210X firmware
Mar 22 19:07:52 ubuntu kernel: [ 691.513191] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 22 19:07:52 ubuntu kernel: [ 691.513245] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 22 19:07:52 ubuntu kernel: [ 691.513575] DVB: registering new adapter (TeVii S660 USB)
Mar 22 19:07:52 ubuntu kernel: [ 691.746853] dvb-usb: MAC address: 00:18:bd:5a:c4:d9
Mar 22 19:07:52 ubuntu kernel: [ 691.750341] DS3000 chip version: 0.192 attached.
Mar 22 19:07:52 ubuntu kernel: [ 691.750710] dw2102: Attached ds3000+ds2020!
Mar 22 19:07:52 ubuntu kernel: [ 691.750710]
Mar 22 19:07:52 ubuntu kernel: [ 691.750715] DVB: registering adapter 0 frontend 0 (Montage Technology DS3000/TS2020)...
Mar 22 19:07:52 ubuntu kernel: [ 691.751517] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.0/0000:02:00.1/usb3/3-1/input/input34
Mar 22 19:07:52 ubuntu kernel: [ 691.751552] dvb-usb: schedule remote query interval to 150 msecs.
Mar 22 19:07:52 ubuntu kernel: [ 691.751556] dvb-usb: TeVii S660 USB successfully initialized and connected.
Mar 22 19:07:52 ubuntu kernel: [ 691.751573] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 22 19:07:52 ubuntu kernel: [ 691.753729] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 22 19:07:52 ubuntu kernel: [ 691.753732] dw2102: start downloading DW210X firmware
Mar 22 19:07:53 ubuntu kernel: [ 691.900924] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 22 19:07:53 ubuntu kernel: [ 691.900968] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 22 19:07:53 ubuntu kernel: [ 691.901338] DVB: registering new adapter (TeVii S660 USB)
Mar 22 19:07:53 ubuntu kernel: [ 692.134897] dvb-usb: MAC address: 00:18:bd:5a:c4:da
Mar 22 19:07:53 ubuntu kernel: [ 692.137640] DS3000 chip version: 0.192 attached.
Mar 22 19:07:53 ubuntu kernel: [ 692.138009] dw2102: Attached ds3000+ds2020!
Mar 22 19:07:53 ubuntu kernel: [ 692.138009]
Mar 22 19:07:53 ubuntu kernel: [ 692.138014] DVB: registering adapter 1 frontend 0 (Montage Technology DS3000/TS2020)...
Mar 22 19:07:53 ubuntu kernel: [ 692.138823] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.0/0000:02:00.3/usb4/4-1/input/input35
Mar 22 19:07:53 ubuntu kernel: [ 692.138867] dvb-usb: schedule remote query interval to 150 msecs.
Mar 22 19:07:53 ubuntu kernel: [ 692.138871] dvb-usb: TeVii S660 USB successfully initialized and connected.
Mar 22 19:07:53 ubuntu kernel: [ 692.138897] usbcore: registered new interface driver dw2102
Mar 22 19:07:53 ubuntu vdr: [2793] VDR version 1.7.41 started
Mar 22 19:07:53 ubuntu vdr: [2793] codeset is 'UTF-8' - known
Mar 22 19:07:53 ubuntu vdr: [2793] found 28 locales in /usr/share/locale
Mar 22 19:07:53 ubuntu vdr: [2793] loading /etc/vdr/setup.conf
Mar 22 19:07:53 ubuntu vdr: [2793] loading /etc/vdr/sources.conf
Mar 22 19:07:53 ubuntu vdr: [2793] loading /etc/vdr/diseqc.conf
Mar 22 19:07:53 ubuntu vdr: [2793] loading /etc/vdr/scr.conf
Mar 22 19:07:53 ubuntu vdr: [2793] loading /etc/vdr/channels.conf
Mar 22 19:07:53 ubuntu vdr: [2793] deleting duplicate channel EinsPlus;ARD:10744:HC56M2S0:S19.2E:22000:301=2:302=deu@3:304:0:28723:1:1051:0
Mar 22 19:07:53 ubuntu vdr: [2793] deleting duplicate channel arte;ARD:10743:HC56M2S0:S19.2E:22000:401=2:402=deu@3,403=fra@3:404:0:28724:1:1051:0
Mar 22 19:07:53 ubuntu vdr: [2793] deleting duplicate channel ORF1 HD;ORF:11303:HC23M5O35S1:S19.2E:22000:1920=27:1921=deu@4,1922=eng@4;1923=deu@106:1925:648,D05,D95,1702,1833,9C4:4911:1:1007:0
Mar 22 19:07:53 ubuntu vdr: [2793] deleting duplicate channel ORF2 HD;ORF:11303:HC23M5O35S1:S19.2E:22000:2920=27:2921=deu@4,2922=deu@4;2923=deu@106:2925:648,D05,D95,1702,1833,9C4:4912:1:1007:0
Mar 22 19:07:53 ubuntu vdr: [2793] loading /etc/vdr/svdrphosts.conf
Mar 22 19:07:53 ubuntu vdr: [2793] loading /etc/vdr/keymacros.conf
Läd das VDR Startscript die DVB Treiber?
cu
installiere ich den VDR 1.7.41 + vnsiserver3 vom genannten PPA sieht es so aus:
Da scheint alles zu klappen.
Ich wollte allerdings vnsiserver4 bauen
mkdir /home/xbmc/build
cd /home/xbmc/build
apt-get build-dep -y vdr
apt-get source vdr
mv vdr-* vdr
git clone --branch vnsi4 https://github.com/FernetMenta/xbmc-pvr-addons.git
rm -R vdr/PLUGINS/src/*
ln -s /home/xbmc/build/xbmc-pvr-addons/addons/pvr.vdr.vnsi/vdr-plugin-vnsiserver /home/xbmc/build/vdr/PLUGINS/src/vnsiserver
cd /home/xbmc/build/vdr/
make -j4 VDRDIR=/usr/include/vdr LIBDIR=/usr/lib/vdr/plugins
make install VDRDIR=/usr/include/vdr LIBDIR=/usr/lib/vdr/plugins
Das sieht nun auch soweit gut aus:
Nur steh ich nun etwas aufm Schlauch was vorher nicht geklappt hat.
Trotzdem vielen Dank. Ich versuche das mal an Kiste 2.
hm ich komme der Sache etwas näher.
Kannst du mal einen Blick darauf werfen:
Gibts dafür ne Erklärung?
Schmeiß ich VDR Runter -> kein Lock
Mach ich ihn drauf -> Lock
Beim 1.7.41 hab ich dann auch lock
Normal?
Hm Ich meine eigentlich dass VDR 1.7.41 auch gestartet wäre, aber dann ist die Sache wohl doch klar (wie du vermutet hast) der VDR kam nicht hoch (aber ich emine doch) denn XBMC und VNSI hat sich ja auch korrekt verbunden, ich hab Channels gelistet etc