Autor Thema: w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."  (Gelesen 20902 mal)

grandefuturo

  • Newbie
  • *
  • Beiträge: 11
    • Profil anzeigen
Hallo SundTek Team,

habe mich eben registriert, bin also neu hier. Vor einigen Tagen wurden meine beiden mediatv digital home III geliefert. Hier meine Problembeschreibung:

System:
ZOTAC Intel Atom D525 ION2
openSuSE 13.2 64-bit
Linux 3.16.7-24-desktop
vdr 2.2.0
vnsiserver
kodi 15.1

Bisher mit einer Hauppauge Nova-T USB2 erfolgreich im Einsatz.
Will jetzt auf DVB-C (KD/Vodafone München) umsteigen

1. SundTek Treiber erfolgreich installiert:
mediaclient -e
**** List of Media Hardware Devices ****
device 0: [MediaTV Digital Home III (EU)]  DVB-C, DVB-T, DVB-T2, REMOTE-CONTROL
  [INFO]:
     STATUS: ACTIVE
  [BUS]:
     ID: 4-1
  [SERIAL]:
     ID: U140310153439
  [DVB-C]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [DVB-T]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [DVB-T2]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0

2. Der Stick wird auf DVB-C gestellt:
mediaclient -d /dev/dvb/adapter1/frontend1 -D DVBC
3. DVB Device wird im vdr nur nach einem rcvdr restart erkannt. Hierzu gibt es diverse Threads hier im Forum, was die Reihenfolge von SundTek Stick und VDR betrifft, werde dieses Problem zunächst zurückstellen, da es gravierenderes gibt....

4. Nach dem VDR restart leuchtet die blaue LED am SundTek Stick. Ein mediaclient --lc listet den VDR auch auf. Kodi zeigt leider kein Bild ("no data"). Dasselbe bei kaffeine, mplayer, xine-ui.

5. Fehlersuche:
der VDR wird gestoppt
rcvdr stop
6. Ein w_scan wird durchgeführt
w_scan -fc -c DE -o 21 > channels.conf    
w_scan version 20141122 (compiled for DVB API 5.10)
using settings for GERMANY
DVB cable
DVB-C
scan type CABLE, channellist 7
output format vdr-2.1
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
        /dev/dvb/adapter0/frontend0 -> "DiBcom 3000MC/P" doesnt support CABLE -> SEARCH NEXT ONE.
        /dev/dvb/adapter1/frontend0 -> CABLE "Sundtek DVB-C (III)": good :-)
Using CABLE frontend (adapter /dev/dvb/adapter1/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.10
frontend 'Sundtek DVB-C (III)' supports
INVERSION_AUTO
QAM_AUTO not supported, trying QAM_64 QAM_256.
FEC_AUTO
FREQ (42.00MHz ... 1002.00MHz)
SRATE (0.520MSym/s ... 7.233MSym/s)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
searching QAM64...
73000: sr6900 (time: 00:06.481) sr6875 (time: 00:08.256)
81000: sr6900 (time: 00:10.030) sr6875 (time: 00:11.807)
113000: sr6900 (time: 00:13.584) sr6875 (time: 00:15.362)
121000: sr6900 (time: 00:17.137) sr6875 (time: 00:18.915)
129000: sr6900 (time: 00:20.690) sr6875 (time: 00:22.467)
137000: sr6900 (time: 00:24.242) sr6875 (time: 00:26.019)
145000: sr6900 (time: 00:27.794) sr6875 (time: 00:29.572)
153000: sr6900 (time: 00:31.345) sr6875 (time: 00:33.121)
161000: sr6900 (time: 00:34.896) sr6875 (time: 00:36.675)
169000: sr6900 (time: 00:38.447) sr6875 (time: 00:40.222)
314000: sr6900 (time: 00:41.998) sr6875 (time: 00:43.772)
322000: sr6900 (time: 00:45.547) sr6875 (time: 00:47.322)
330000: sr6900 (time: 00:49.099) sr6875 (time: 00:50.866)
338000: sr6900 (time: 00:52.645) sr6875 (time: 00:54.424)
346000: sr6900 (time: 00:56.202) sr6875 (time: 00:57.968)
354000: sr6900 (time: 00:59.746) sr6875 (time: 01:01.524)
362000: sr6900 (time: 01:03.304) sr6875 (time: 01:05.060)
370000: sr6900 (time: 01:06.835) sr6875 (time: 01:08.611)
378000: sr6900 (time: 01:10.393) sr6875 (time: 01:12.153)
386000: sr6900 (time: 01:13.929) sr6875 (time: 01:15.706)
394000: sr6900 (time: 01:17.480) sr6875 (time: 01:19.242)
402000: sr6900 (time: 01:21.018) sr6875 (time: 01:22.794)
410000: sr6900 (time: 01:24.569) sr6875 (time: 01:26.346)
418000: sr6900 (time: 01:28.128) sr6875 (time: 01:29.905)
426000: sr6900 (time: 01:31.683) sr6875 (time: 01:33.463)
434000: sr6900 (time: 01:35.240) sr6875 (time: 01:37.016)
442000: sr6900 (time: 01:38.784) sr6875 (time: 01:40.563)
450000: sr6900 (time: 01:42.339) sr6875 (time: 01:44.117)
458000: sr6900 (time: 01:45.893) sr6875 (time: 01:47.670)
466000: sr6900 (time: 01:49.446) sr6875 (time: 01:51.223)
474000: sr6900 (time: 01:52.995) sr6875 (time: 01:54.774)
482000: sr6900 (time: 01:56.552) sr6875 (time: 01:58.332)
490000: sr6900 (time: 02:00.101) sr6875 (time: 02:01.876)
498000: sr6900 (time: 02:03.651) sr6875 (time: 02:05.432)
506000: sr6900 (time: 02:07.211) sr6875 (time: 02:08.989)
514000: sr6900 (time: 02:10.763) sr6875 (time: 02:12.538)
522000: sr6900 (time: 02:14.316) sr6875 (time: 02:16.091)
530000: sr6900 (time: 02:17.870) sr6875 (time: 02:19.636)
538000: sr6900 (time: 02:21.410) sr6875 (time: 02:23.184)
546000: sr6900 (time: 02:24.961) sr6875 (time: 02:26.739)
554000: sr6900 (time: 02:28.519) sr6875 (time: 02:30.295)
562000: sr6900 (time: 02:32.067) sr6875 (time: 02:33.843)
570000: sr6900 (time: 02:35.619) sr6875 (time: 02:37.398)
578000: sr6900 (time: 02:39.165) sr6875 (time: 02:40.943)
586000: sr6900 (time: 02:42.721) sr6875 (time: 02:44.500)
594000: sr6900 (time: 02:46.270) sr6875 (time: 02:48.048)
602000: sr6900 (time: 02:49.824) sr6875 (time: 02:51.591)
610000: sr6900 (time: 02:53.370)         signal ok:     QAM_64   f = 610000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_64   f = 610000 kHz S6900C999  (0:0:0))
618000: sr6900 (time: 02:55.820) sr6875 (time: 02:57.605)
626000: sr6900 (time: 02:59.374) sr6875 (time: 03:01.152)
634000: sr6900 (time: 03:02.933) sr6875 (time: 03:04.702)
642000: sr6900 (time: 03:06.481) sr6875 (time: 03:08.255)
650000: sr6900 (time: 03:10.035) sr6875 (time: 03:11.805)
658000: sr6900 (time: 03:13.586) sr6875 (time: 03:15.366)
666000: sr6900 (time: 03:17.140) sr6875 (time: 03:18.917)
674000: sr6900 (time: 03:20.690) sr6875 (time: 03:22.499)
682000: sr6900 (time: 03:24.273) sr6875 (time: 03:26.050)
690000: sr6900 (time: 03:27.825) sr6875 (time: 03:29.603)
698000: sr6900 (time: 03:31.372)         signal ok:     QAM_64   f = 698000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_64   f = 698000 kHz S6900C999  (0:0:0))
706000: sr6900 (time: 03:34.833)         signal ok:     QAM_64   f = 706000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_64   f = 706000 kHz S6900C999  (0:0:0))
714000: sr6900 (time: 03:38.832)         signal ok:     QAM_64   f = 714000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_64   f = 714000 kHz S6900C999  (0:0:0))
722000: sr6900 (time: 03:41.831)         signal ok:     QAM_64   f = 722000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_64   f = 722000 kHz S6900C999  (0:0:0))
730000: sr6900 (time: 03:44.838)         signal ok:     QAM_64   f = 730000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_64   f = 730000 kHz S6900C999  (0:0:0))
738000: sr6900 (time: 03:47.779)         signal ok:     QAM_64   f = 738000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_64   f = 738000 kHz S6900C999  (0:0:0))
746000: sr6900 (time: 03:50.795)         signal ok:     QAM_64   f = 746000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_64   f = 746000 kHz S6900C999  (0:0:0))
754000: sr6900 (time: 03:53.829) sr6875 (time: 03:55.612)
762000: sr6900 (time: 03:57.383) sr6875 (time: 03:59.160)
770000: sr6900 (time: 04:00.935) sr6875 (time: 04:02.705)
778000: sr6900 (time: 04:04.481) sr6875 (time: 04:06.255)
786000: sr6900 (time: 04:08.034) sr6875 (time: 04:09.800)
794000: sr6900 (time: 04:11.576) sr6875 (time: 04:13.351)
802000: sr6900 (time: 04:15.131) sr6875 (time: 04:16.898)
810000: sr6900 (time: 04:18.673) sr6875 (time: 04:20.452)
818000: sr6900 (time: 04:22.221) sr6875 (time: 04:23.999)
826000: sr6900 (time: 04:25.777)         signal ok:     QAM_64   f = 826000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_64   f = 826000 kHz S6900C999  (0:0:0))
834000: sr6900 (time: 04:28.811) sr6875 (time: 04:30.590)
842000: sr6900 (time: 04:32.367) sr6875 (time: 04:34.147)
850000: sr6900 (time: 04:35.917) sr6875 (time: 04:37.692)
858000: sr6900 (time: 04:39.472) sr6875 (time: 04:41.250)
searching QAM256...
73000: sr6900 (time: 04:43.024) sr6875 (time: 04:44.803)
81000: sr6900 (time: 04:46.583) sr6875 (time: 04:48.348)
113000: sr6900 (time: 04:50.125) sr6875 (time: 04:51.902)
121000: sr6900 (time: 04:53.678) sr6875 (time: 04:55.447)
129000: sr6900 (time: 04:57.222) sr6875 (time: 04:59.002)
137000: sr6900 (time: 05:00.781) sr6875 (time: 05:02.551)
145000: sr6900 (time: 05:04.326)         signal ok:     QAM_256  f = 145000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 145000 kHz S6900C999  (0:0:0))
153000: sr6900 (time: 05:06.841)         signal ok:     QAM_256  f = 153000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 153000 kHz S6900C999  (0:0:0))
161000: sr6900 (time: 05:09.849) sr6875 (time: 05:11.628)
169000: sr6900 (time: 05:13.405)         signal ok:     QAM_256  f = 169000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 169000 kHz S6900C999  (0:0:0))
314000: sr6900 (time: 05:16.871)         signal ok:     QAM_256  f = 314000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 314000 kHz S6900C999  (0:0:0))
322000: sr6900 (time: 05:19.839)         signal ok:     QAM_256  f = 322000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 322000 kHz S6900C999  (0:0:0))
330000: sr6900 (time: 05:22.836)         signal ok:     QAM_256  f = 330000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 330000 kHz S6900C999  (0:0:0))
338000: sr6900 (time: 05:25.832)         signal ok:     QAM_256  f = 338000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 338000 kHz S6900C999  (0:0:0))
346000: sr6900 (time: 05:28.833)         signal ok:     QAM_256  f = 346000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 346000 kHz S6900C999  (0:0:0))
354000: sr6900 (time: 05:31.829)         signal ok:     QAM_256  f = 354000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 354000 kHz S6900C999  (0:0:0))
362000: sr6900 (time: 05:34.815)         signal ok:     QAM_256  f = 362000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 362000 kHz S6900C999  (0:0:0))
370000: sr6900 (time: 05:37.833)         signal ok:     QAM_256  f = 370000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 370000 kHz S6900C999  (0:0:0))
378000: sr6900 (time: 05:40.841)         signal ok:     QAM_256  f = 378000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 378000 kHz S6900C999  (0:0:0))
386000: sr6900 (time: 05:43.823)         signal ok:     QAM_256  f = 386000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 386000 kHz S6900C999  (0:0:0))
394000: sr6900 (time: 05:46.791)         signal ok:     QAM_256  f = 394000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 394000 kHz S6900C999  (0:0:0))
402000: sr6900 (time: 05:49.819)         signal ok:     QAM_256  f = 402000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 402000 kHz S6900C999  (0:0:0))
410000: sr6900 (time: 05:52.831)         signal ok:     QAM_256  f = 410000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 410000 kHz S6900C999  (0:0:0))
418000: sr6900 (time: 05:55.814)         signal ok:     QAM_256  f = 418000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 418000 kHz S6900C999  (0:0:0))
426000: sr6900 (time: 05:58.849)         signal ok:     QAM_256  f = 426000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 426000 kHz S6900C999  (0:0:0))
434000: sr6900 (time: 06:01.818)         signal ok:     QAM_256  f = 434000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 434000 kHz S6900C999  (0:0:0))
442000: sr6900 (time: 06:04.825)         signal ok:     QAM_256  f = 442000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 442000 kHz S6900C999  (0:0:0))
450000: sr6900 (time: 06:07.821)         signal ok:     QAM_256  f = 450000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 450000 kHz S6900C999  (0:0:0))
458000: sr6900 (time: 06:10.828)         signal ok:     QAM_256  f = 458000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 458000 kHz S6900C999  (0:0:0))
466000: sr6900 (time: 06:13.830)         signal ok:     QAM_256  f = 466000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 466000 kHz S6900C999  (0:0:0))
474000: sr6900 (time: 06:16.819)         signal ok:     QAM_256  f = 474000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 474000 kHz S6900C999  (0:0:0))
482000: sr6900 (time: 06:20.843)         signal ok:     QAM_256  f = 482000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 482000 kHz S6900C999  (0:0:0))
490000: sr6900 (time: 06:23.853)         signal ok:     QAM_256  f = 490000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 490000 kHz S6900C999  (0:0:0))
498000: sr6900 (time: 06:26.859)         signal ok:     QAM_256  f = 498000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 498000 kHz S6900C999  (0:0:0))
506000: sr6900 (time: 06:29.831) sr6875 (time: 06:31.610)
514000: sr6900 (time: 06:33.381) sr6875 (time: 06:35.154)
522000: sr6900 (time: 06:36.929)         signal ok:     QAM_256  f = 522000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 522000 kHz S6900C999  (0:0:0))
530000: sr6900 (time: 06:39.826)         signal ok:     QAM_256  f = 530000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 530000 kHz S6900C999  (0:0:0))
538000: sr6900 (time: 06:42.828)         signal ok:     QAM_256  f = 538000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 538000 kHz S6900C999  (0:0:0))
546000: sr6900 (time: 06:45.820)         signal ok:     QAM_256  f = 546000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 546000 kHz S6900C999  (0:0:0))
554000: sr6900 (time: 06:49.797)         signal ok:     QAM_256  f = 554000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 554000 kHz S6900C999  (0:0:0))
562000: sr6900 (time: 06:52.808)         signal ok:     QAM_256  f = 562000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 562000 kHz S6900C999  (0:0:0))
570000: sr6900 (time: 06:55.833)         signal ok:     QAM_256  f = 570000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 570000 kHz S6900C999  (0:0:0))
578000: sr6900 (time: 06:58.816)         signal ok:     QAM_256  f = 578000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 578000 kHz S6900C999  (0:0:0))
586000: sr6900 (time: 07:01.835)         signal ok:     QAM_256  f = 586000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 586000 kHz S6900C999  (0:0:0))
594000: sr6900 (time: 07:04.816)         signal ok:     QAM_256  f = 594000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 594000 kHz S6900C999  (0:0:0))
602000: sr6900 (time: 07:08.835)         signal ok:     QAM_256  f = 602000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 602000 kHz S6900C999  (0:0:0))
610000: sr6900 (time: 07:11.832) sr6875 (time: 07:13.601)
618000: sr6900 (time: 07:15.377)         signal ok:     QAM_256  f = 618000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 618000 kHz S6900C999  (0:0:0))
626000: sr6900 (time: 07:17.820)         signal ok:     QAM_256  f = 626000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 626000 kHz S6900C999  (0:0:0))
634000: sr6900 (time: 07:20.829) sr6875 (time: 07:22.607)
642000: sr6900 (time: 07:24.387)         signal ok:     QAM_256  f = 642000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 642000 kHz S6900C999  (0:0:0))
650000: sr6900 (time: 07:26.830)         signal ok:     QAM_256  f = 650000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 650000 kHz S6900C999  (0:0:0))
658000: sr6900 (time: 07:29.821)         signal ok:     QAM_256  f = 658000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 658000 kHz S6900C999  (0:0:0))
666000: sr6900 (time: 07:32.810)         signal ok:     QAM_256  f = 666000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 666000 kHz S6900C999  (0:0:0))
674000: sr6900 (time: 07:35.820)         signal ok:     QAM_256  f = 674000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 674000 kHz S6900C999  (0:0:0))
682000: sr6900 (time: 07:38.793)         signal ok:     QAM_256  f = 682000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 682000 kHz S6900C999  (0:0:0))
690000: sr6900 (time: 07:41.821)         signal ok:     QAM_256  f = 690000 kHz S6900C999  (0:0:0)
        Info: no data from PAT after 2 seconds
        deleting (QAM_256  f = 690000 kHz S6900C999  (0:0:0))
698000: sr6900 (time: 07:44.806) sr6875 (time: 07:46.576)
706000: sr6900 (time: 07:48.356) sr6875 (time: 07:50.132)
714000: sr6900 (time: 07:51.898) sr6875 (time: 07:53.674)
722000: sr6900 (time: 07:55.457) sr6875 (time: 07:57.243)
730000: sr6900 (time: 07:59.015) sr6875 (time: 08:00.794)
738000: sr6900 (time: 08:02.574) sr6875 (time: 08:04.352)
746000: sr6900 (time: 08:06.127) sr6875 (time: 08:07.903)
754000: sr6900 (time: 08:09.679) sr6875 (time: 08:11.458)
762000: sr6900 (time: 08:13.225) sr6875 (time: 08:15.000)
770000: sr6900 (time: 08:16.777) sr6875 (time: 08:18.550)
778000: sr6900 (time: 08:20.327) sr6875 (time: 08:22.102)
786000: sr6900 (time: 08:23.883) sr6875 (time: 08:25.653)
794000: sr6900 (time: 08:27.434) sr6875 (time: 08:29.212)
802000: sr6900 (time: 08:30.991) sr6875 (time: 08:32.761)
810000: sr6900 (time: 08:34.535) sr6875 (time: 08:36.310)
818000: sr6900 (time: 08:38.087) sr6875 (time: 08:39.861)
826000: sr6900 (time: 08:41.636) sr6875 (time: 08:43.414)
834000: sr6900 (time: 08:45.179) sr6875 (time: 08:46.956)
842000: sr6900 (time: 08:48.730) sr6875 (time: 08:50.508)
850000: sr6900 (time: 08:52.287) sr6875 (time: 08:54.062)
858000: sr6900 (time: 08:55.838) sr6875 (time: 08:57.617)

ERROR: Sorry - i couldn't get any working frequency/transponder
 Nothing to scan!!

7. Ein readsignal wird durchgeführt
mediaclient -d /dev/dvb/adapter1/frontend0 --readsignal=20
== reading digital TV signal ==
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
SIGNAL: [.................................] ( 99%)  BER:      0 CNR: 0.00 FREQ: 370000000  Hz LOCKED:  NO SYM: 6900000 MOD: QAM64
alles OK, oder?

8. Das zum w_scan gehörende mediasrv.log (mit loglevel=max)
2015-09-29 10:19:06 [4656] RC: detached remote control
2015-09-29 10:19:06 [1011] restarting logging
2015-09-29 10:19:06 [1011] clearing id: 0
2015-09-29 10:19:06 [1011] removing devices
2015-09-29 10:19:06 [1011] Shutting down driver now
2015-09-29 10:19:06 [1011] Waiting for service thread to complete
2015-09-29 10:19:16 [4676] RC: IR Event /dev/input/event17
2015-09-29 10:19:16 [4685] RC: IR Event /dev/input/event17
2015-09-29 10:22:02 [4778] RC: detached remote control
2015-09-29 10:22:54 [1236] RC: IR Event /dev/input/event17
2015-09-29 10:22:54 [1245] RC: IR Event /dev/input/event17
2015-09-29 10:26:57 [985] Waking up device
2015-09-29 10:26:57 [985] Waking up in digital TV mode
2015-09-29 10:26:58 [985] Power up demodulator
2015-09-29 10:27:03 [985] SETTING DVB-C
2015-09-29 10:27:03 [985] Setting Frequency: 81000000
2015-09-29 10:27:03 [985] Setting Symbolrate: 6900000
2015-09-29 10:27:03 [985] Setting Modulation: 3
2015-09-29 10:27:03 [985] setting symbolrate: 6900
2015-09-29 10:27:03 [985] Tuning DVB-C Frequency: 81000000
2015-09-29 10:27:04 [985] Setting Frequency: 73000000
2015-09-29 10:27:04 [985] Setting Frequency: 73000000
2015-09-29 10:27:04 [985] Setting Symbolrate: 6900000
2015-09-29 10:27:04 [985] Setting Modulation: 3
2015-09-29 10:27:04 [985] setting symbolrate: 6900
2015-09-29 10:27:04 [985] Tuning DVB-C Frequency: 73000000
2015-09-29 10:27:05 [985] Setting Frequency: 73000000
2015-09-29 10:27:05 [985] Setting Frequency: 73000000
2015-09-29 10:27:05 [985] Setting Symbolrate: 6875000
2015-09-29 10:27:05 [985] Setting Modulation: 3
2015-09-29 10:27:05 [985] re-writing symbolrate to 6900KSym (please report if it causes problems!)
2015-09-29 10:27:05 [985] setting symbolrate: 6875
2015-09-29 10:27:05 [985] Tuning DVB-C Frequency: 73000000
2015-09-29 10:27:07 [985] Setting Frequency: 81000000
2015-09-29 10:27:07 [985] Setting Frequency: 81000000
2015-09-29 10:27:07 [985] Setting Symbolrate: 6900000
2015-09-29 10:27:07 [985] Setting Modulation: 3
2015-09-29 10:27:07 [985] setting symbolrate: 6900
...
2015-09-29 10:30:30 [985] Resetting TS Port
2015-09-29 10:30:30 [985] TS Sync byte not aligned, realigning stream (0 // 104)
2015-09-29 10:30:30 [985] TS Sync byte not aligned, realigning stream (208 // 104)
2015-09-29 10:30:33 [985] Setting Frequency: 706000000
2015-09-29 10:30:33 [985] Setting Frequency: 706000000
2015-09-29 10:30:33 [985] Setting Symbolrate: 6900000
2015-09-29 10:30:33 [985] Setting Modulation: 3
2015-09-29 10:30:33 [985] setting symbolrate: 6900
2015-09-29 10:30:33 [985] Tuning DVB-C Frequency: 706000000
2015-09-29 10:30:36 [985] Resetting TS Port
2015-09-29 10:30:36 [985] TS Sync byte not aligned, realigning stream (0 // 40)
2015-09-29 10:30:37 [985] Setting Frequency: 714000000
2015-09-29 10:30:37 [985] Setting Frequency: 714000000
2015-09-29 10:30:37 [985] Setting Symbolrate: 6900000
2015-09-29 10:30:37 [985] Setting Modulation: 3
2015-09-29 10:30:37 [985] setting symbolrate: 6900
2015-09-29 10:30:37 [985] Tuning DVB-C Frequency: 714000000
2015-09-29 10:30:40 [985] Resetting TS Port
2015-09-29 10:30:40 [985] TS Sync byte not aligned, realigning stream (0 // 104)
2015-09-29 10:30:41 [985] Setting Frequency: 722000000
2015-09-29 10:30:41 [985] Setting Frequency: 722000000
2015-09-29 10:30:41 [985] Setting Symbolrate: 6900000
2015-09-29 10:30:41 [985] Setting Modulation: 3
2015-09-29 10:30:41 [985] setting symbolrate: 6900
2015-09-29 10:30:41 [985] Tuning DVB-C Frequency: 722000000
2015-09-29 10:30:44 [985] Setting Frequency: 730000000
2015-09-29 10:30:44 [985] Setting Frequency: 730000000
2015-09-29 10:30:44 [985] Setting Symbolrate: 6900000
2015-09-29 10:30:44 [985] Setting Modulation: 3
2015-09-29 10:30:44 [985] setting symbolrate: 6900
2015-09-29 10:30:44 [985] Tuning DVB-C Frequency: 730000000
2015-09-29 10:30:46 [985] Resetting TS Port
2015-09-29 10:30:46 [985] TS Sync byte not aligned, realigning stream (0 // 104)
2015-09-29 10:30:47 [985] Setting Frequency: 738000000
2015-09-29 10:30:47 [985] Setting Frequency: 738000000
2015-09-29 10:30:47 [985] Setting Symbolrate: 6900000
2015-09-29 10:30:47 [985] Setting Modulation: 3
2015-09-29 10:30:47 [985] setting symbolrate: 6900
2015-09-29 10:30:47 [985] Tuning DVB-C Frequency: 738000000
...
2015-09-29 10:36:21 [985] Enabling Standby

Ich denke mal, die "no data from PAT" des w_scan sind auf die "Resetting TS Port, TS Sync byte not aligned" zurückzuführen?

Was ist an meinem Setup falsch?
Übrigens, dasselbe Verhalten habe ich, wenn ich den SundTek auf DVB-T umstelle und diesselbe Antenne wie für die Hauppauge verwende...

Liegt es am USB?

Liegt es an anderen Skripts? Hier sind noch einige beigefügt:
/usr/lib/systemd/system/sundtek.service
[Unit]
Description=Sundtek MediaTV
Wants=graphical.target

[Service]
Type=oneshot
ExecStart=/opt/bin/mediaclient --start=4
ExecStop=/opt/bin/mediaclient --shutdown
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

/etc/sundtek.conf
ir_disabled=1
initial_dvb_mode=DVBC

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #1 am: September 29, 2015, 06:04:53 Nachmittag »
Hallo,

versuche erst mal den USB 2.0 Port damit zu verwenden, USB 3.0 Ports funktionieren unter Linux nicht ordentlich.
Der Tuner hat hier auch noch ein paar Einstellungsmöglichkeiten die je nachdem wie gut oder schlecht ein USB Controller von Linux unterstützt wird das Ganze beeinflussen kann.

Vielleicht funktioniert bei Dir auch einer dieser beiden Modis mit USB 3:
BULK (default):
/opt/bin/mediaclient --transfermode=bulk -d /dev/dvb/adapter1/frontend0
ISO:
/opt/bin/mediaclient --transfermode=iso -d /dev/dvb/adapter1/frontend0
« Letzte Änderung: September 29, 2015, 06:15:57 Nachmittag von Sundtek »
Failure is a good thing! I'll fix it

grandefuturo

  • Newbie
  • *
  • Beiträge: 11
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #2 am: September 30, 2015, 11:56:14 Vormittag »
USB3.0 wird nicht verwendet, daran kann es nicht liegen.

Spielt evlt. die Stromversorgung des DVB Sticks eine Rolle?

Erfolgreiche Meldungen beziehen sich auf den Einsatz eines Hubs:
http://support.sundtek.com/index.php?topic=1765.0;wap2

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #3 am: September 30, 2015, 11:59:46 Vormittag »
Nein.

Was zeigt denn lsusb -t an?

Sobald der Tuner unter xhci gelistet wird - wird er effektiv mit dem USB 3.0 Controller verwendet.

Da es unter Windows und MacOSX mit USB 3.0 (XHCI) keine Probleme gibt - gibt es aktuell ein Problem mit dem Linux XHCI USB Controller Treiber.
Failure is a good thing! I'll fix it

grandefuturo

  • Newbie
  • *
  • Beiträge: 11
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #4 am: September 30, 2015, 06:10:12 Nachmittag »
lsusb -t liefert
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
    |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
    |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 1: Dev 3, If 1, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 1: Dev 3, If 2, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 1: Dev 3, If 3, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 1: Dev 3, If 4, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
der Sundtek ist hier gar nicht dabei?

Der Device ist aber vorhanden.
mediaclient -e liefert:
**** List of Media Hardware Devices ****
device 0: [MediaTV Digital Home III (EU)]  DVB-C, DVB-T, DVB-T2, REMOTE-CONTROL
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 2-1
  [SERIAL]:
     ID: U140310153439
  [DVB-C]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [DVB-T]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [DVB-T2]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0

grandefuturo

  • Newbie
  • *
  • Beiträge: 11
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #5 am: September 30, 2015, 07:26:29 Nachmittag »
nach einem rcvdr start erscheinen folgende Verbindungen:
/dev/dvb/adapter0/frontend0:
  5293 ... vdr
/dev/dvb/adapter0/dvr0:
  No client connected
/dev/dvb/adapter0/demux0:
  5293 ... vdr (0012)
  5293 ... vdr (0014)
  5293 ... vdr (0000)
  5293 ... vdr (0011)
  5293 ... vdr (0010)
/dev/mediainput0:
  No client connected

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #6 am: September 30, 2015, 07:51:20 Nachmittag »
Überprüfe das mit lsusb nochmal.

lsusb (ohne Parameter sollte auch "Sundtek" anzeigen)

lsusb -t sollte dann noch weitere Informationen für jeden Tuner anzeigen.

Was VDR anzeigt ist eigentlich egal, wenn der Treiber im Hintergrund Aufgrund eines USB Controller Problems nicht auf den Tuner zugreifen kann dann werden keine Daten durchgeleitet.

Die Einstellungen des Tuners z.B Frequenzscan funktionieren selbst mit USB 1.1, dort sind die Anforderungen nicht so ein zeitkritisches Problem.
« Letzte Änderung: September 30, 2015, 08:47:58 Nachmittag von Sundtek »
Failure is a good thing! I'll fix it

grandefuturo

  • Newbie
  • *
  • Beiträge: 11
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #7 am: September 30, 2015, 09:17:24 Nachmittag »
lsusb ohne Parameter liefert ein Sundtek
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 05a4:9881 Ortek Technology, Inc. IR receiver [VRC-1100 Vista MCE Remote Control]
Bus 002 Device 006: ID 2659:1401 Sundtek
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 04d9:2519 Holtek Semiconductor, Inc.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

« Letzte Änderung: September 30, 2015, 09:29:46 Nachmittag von grandefuturo »

grandefuturo

  • Newbie
  • *
  • Beiträge: 11
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #8 am: September 30, 2015, 10:58:14 Nachmittag »
Der Sundtek kommt mit USB 1.1 hoch.
Habe ihn an ein USB 3.0 Port gesteckt, dort kommt er mit USB 2.0 hoch, jetzt funktioniert alles.

Muss mal meine BIOS Einstellungen überprüfen.....

Gibt es noch eine Empfehlung, wie ich den VDR Start verzögern kann, bis der Sundtek bereit ist?
Habe von diversen Plugins gelesen....ist das der richtige Weg?

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #9 am: Oktober 01, 2015, 12:55:47 Vormittag »
Du kannst eine Konfiguration anlegen:

/etc/sundtek.conf

device_attach=service vdr restart


Laut der Ausgabe war kein EHCI Treiber geladen? Vielleicht ist dass das Problem.
Failure is a good thing! I'll fix it

grandefuturo

  • Newbie
  • *
  • Beiträge: 11
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #10 am: Oktober 01, 2015, 10:58:41 Vormittag »
könnte der Stick nicht eine Meldung im mediasrv.log ausgeben, dass er mit einer nicht ausreichenden USB speed verbunden ist?

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #11 am: Oktober 01, 2015, 03:07:26 Nachmittag »
Wir werden das bei /opt/bin/mediaclient -e nachpflegen.
Failure is a good thing! I'll fix it

grandefuturo

  • Newbie
  • *
  • Beiträge: 11
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #12 am: Oktober 19, 2015, 02:32:21 Nachmittag »
das mit "device_attach=service vdr start" funktioniert...allerdings habe ich erst jetzt festgestellt, dass vdr nur mit einem adapter hochfährt....kann ich das device_attach verzögern bis auch der zweite stick da ist?

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #13 am: Oktober 19, 2015, 03:02:50 Nachmittag »
Hi,

ich denke dazu musst du in /etc/sundtek.conf

bulk_notification=on


hinzufügen

device_attach wird ja für jeden Tuner ausgeführt, bulk_notification heißt das alle angeschlossenen Geräte erst mal gesammelt werden und zum Schluss nur noch ein Callback aufgerufen wird.
Failure is a good thing! I'll fix it

grandefuturo

  • Newbie
  • *
  • Beiträge: 11
    • Profil anzeigen
Re:w_scan: "no data from PAT", mediasrv: "Resetting TS Port, TS Sync byte not ..."
« Antwort #14 am: Oktober 28, 2015, 08:23:19 Nachmittag »
danke für den Tipp.
Hat zunächst auch funktioniert. VDR kam mit 2 adaptern hoch.
Allerdings musste ich jetzt nach einiger Zeit feststellen, dass Timeraufnahmen fehlen....habe im syslog gesehen, dass einige Male der VDR mit "no DVB device found" hoch kam...und sich dann wieder verabschiedet hat. Wenn ich im /etc/sundtek.conf die bulk_notification wieder herausnehme, startet VDR verlässlich, aber eben mit nur einem Adapter.

Müsste jetzt zum debuggen im mediasrv das loglevel hochsetzen, und den obigen Fall nochmal abwarten.
Das Starten des VDR über init.d ist deaktiviert, er wird nur über device_attach gestartet.

Oder habt ihr schon eine Idee, was das sein könnte?