Beiträge anzeigen

Diese Sektion erlaubt es ihnen alle Beiträge dieses Mitglieds zu sehen. Beachten sie, dass sie nur solche Beiträge sehen können, zu denen sie auch Zugriffsrechte haben.


Nachrichten - marco

Seiten: [1]
1
Vielen Dank für deine Mühen und den super Support!!!

2
Bin im Chat :)

3
Der SAT Tuner hat keine Fehlermeldung mit dem Demodulator, aber auch der bekommt kein Lock und folglich kein Signal

root@7d4a98424ac2:/# /opt/bin/mediaclient --testastra -d /dev/dvb/adapter1/frontend0
Testing Astra 19.2 Frequencies
DVBS
LO Band / 18V:
Checking for lock:
..........
LO Band / 13V:
Checking for lock:
..........
HI Band / 18V:
Checking for lock:
..........
HI Band / 13V:
Checking for lock:
..........
DVB-S2 ZDF HD / 18V
Checking for lock:
..........

4
Bin jetzt im Chat.

Welches Tool bevorzugt ihr für Remote Access? Am besten etwas mit Bildschirmfreigabe und Remote Stuerungsmöglichkeit.

5
Kann es ein Problem sein, dass die sundtek.conf gar nicht im Container vorhanden ist?
root@7d4a98424ac2:/# ps aux | grep mediasrv
root       326  0.7  0.0  14512   884 ?        Sl   23:21   0:00 /opt/bin/mediasrv -d --wait-for-devices --config=/etc/sundtek.conf --pluginpath=/opt/bin
root       327  1.4  0.0   5860   172 ?        S    23:21   0:00 /opt/bin/mediasrv -d --wait-for-devices --config=/etc/sundtek.conf --pluginpath=/opt/bin
root       405  0.0  0.0   1292     4 pts/0    S+   23:22   0:00 grep mediasrv
root@7d4a98424ac2:/# ls -al /etc/sundtek.conf
ls: cannot access '/etc/sundtek.conf': No such file or directory

6
Ja die Sticks sind alt, aber ohne Docker funktionieren beide 1a :)

Zur Klärung, ich hatte den Post oben noch editiert, aber hier nochmal vollständig:

Shell1
root@7d4a98424ac2:/# /opt/bin/mediaclient -m DVBC -f 554000000 -M Q256 -S 6900000 -d /dev/dvb/adapter0/frontend0
Using device: /dev/dvb/adapter0/frontend0
Checking for lock:
..........
root@7d4a98424ac2:/# /opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0
== reading digital TV signal ==
SIGNAL: [                                 ] (  0%) BER:      0 FREQ: 554000000  Hz LOCKED:  NO MER: 0 SYM: 6900000 MOD: QAM256
SIGNAL: [                                 ] (  0%) BER:      0 FREQ: 554000000  Hz LOCKED:  NO MER: 0 SYM: 6900000 MOD: QAM256
SIGNAL: [                                 ] (  0%) BER:      0 FREQ: 554000000  Hz LOCKED:  NO MER: 0 SYM: 6900000 MOD: QAM256
SIGNAL: [                                 ] (  0%) BER:      0 FREQ: 554000000  Hz LOCKED:  NO MER: 0 SYM: 6900000 MOD: QAM256
SIGNAL: [                                 ] (  0%) BER:      0 FREQ: 554000000  Hz LOCKED:  NO MER: 0 SYM: 6900000 MOD: QAM256
SIGNAL: [                                 ] (  0%) BER:      0 FREQ: 554000000  Hz LOCKED:  NO MER: 0 SYM: 6900000 MOD: QAM256
SIGNAL: [                                 ] (  0%) BER:      0 FREQ: 554000000  Hz LOCKED:  NO MER: 0 SYM: 6900000 MOD: QAM256

Shell2
2020-10-14 23:15:35 [771] Waking up device
2020-10-14 23:15:35 [771] SETTING DVB-C
2020-10-14 23:15:35 [771] reinitializing previous digital TV parameters
2020-10-14 23:15:35 [771] Setting Frequency: 554000000
2020-10-14 23:15:35 [771] Setting Symbolrate: 6900000
2020-10-14 23:15:35 [771] Setting Modulation: 5
failure: error retrieving lock status
2020-10-14 23:15:35 [771] Setting Frequency: 554000000
2020-10-14 23:15:35 [771] Setting Symbolrate: 6900000
2020-10-14 23:15:35 [771] Setting Modulation: 5
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
2020-10-14 23:15:36 [771] Enabling standby
2020-10-14 23:15:39 [771] Waking up device
2020-10-14 23:15:40 [771] SETTING DVB-C
2020-10-14 23:15:40 [771] reinitializing previous digital TV parameters
2020-10-14 23:15:40 [771] Setting Frequency: 554000000
2020-10-14 23:15:40 [771] Setting Symbolrate: 6900000
2020-10-14 23:15:40 [771] Setting Modulation: 5
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
2020-10-14 23:15:40 [771] Enabling standby

Das ist ja genau das Problem, aber warum kommt er im Docker nicht in den lock state? :/

Wann und wo genau soll ich den Chat kommen?

7
Hatte den Pi schon mehrmals neugestartet, somit dürfte auf dem Host nichts mehr laufen.

Im Container habe ich den killall durchgeführt. Danach kommt folgender Output
root@7d4a98424ac2:/# /opt/bin/mediasrv -v
2020-10-14 22:53:02 [660] UID: 0 SUID 0
2020-10-14 22:53:02 [660] Alsa Blocking on (default)
2020-10-14 22:53:02 [660] Starting up Multimedia Framework (Oct  9 2020 10:07:48)
2020-10-14 22:53:02 [660] Semaphore exists, removing and reallocating it
2020-10-14 22:53:02 [660] Detected DVB version.h
2020-10-14 22:53:02 [661] Starting service processor (PID 661)
2020-10-14 22:53:02 [660] API Version: 5.11
2020-10-14 22:53:02 [660] Running on Linux (5.4.51-v7+)
2020-10-14 22:53:02 [660] scanning devices
2020-10-14 22:53:02 [660] scanning for drivers
2020-10-14 22:53:02 [660] scanning for plugins
2020-10-14 22:53:02 [660] Starting up device manager
2020-10-14 22:53:02 [660] registering ID: 0
2020-10-14 22:53:02 [660] Memory mapped transfers are not available
2020-10-14 22:53:02 [660] disconnecting kernel driver
2020-10-14 22:53:02 [660] scanning devices done
2020-10-14 22:53:02 [660] attached devices:
2020-10-14 22:53:03 [660] attaching DVB-T, DVB-C
2020-10-14 22:53:03 [660] Using second generation demodulator
error opening demodulator
2020-10-14 22:53:03 [660] Initializing SYSV-IPC
2020-10-14 22:53:03 [660] Allocation using pg for type 65678
2020-10-14 22:53:03 [660] requesting to attach tuner(s) now
2020-10-14 22:53:03 [661] Autostarting scripts in /etc/sundtek/
2020-10-14 22:53:04 [661] executed all available items
2020-10-14 22:53:05 [660] registering: adapter0/0
2020-10-14 22:53:05 [660] registered virtual: /dev/dvb/adapter0/frontend0
2020-10-14 22:53:05 [660] registered virtual: /dev/dvb/adapter0/demux0
2020-10-14 22:53:05 [660] registered virtual: /dev/dvb/adapter0/dvr0
2020-10-14 22:53:05 [660] Setting RC Protocol to NEC
2020-10-14 22:53:05 [660] Unable to create /dev/mediainput0 (17/File exists)
2020-10-14 22:53:05 [660] registered virtual: /dev/mediainput0
2020-10-14 22:53:05 [660] Remote Control Layout: 0
2020-10-14 22:53:05 [661] trying to load uinput module
2020-10-14 22:53:05 [661] loading uinput kernel extention failed, remote control will not work with lirc
2020-10-14 22:53:05 [660] No remote control support available
2020-10-14 22:53:05 [660]
2020-10-14 22:53:05 [660] Sundtek MediaTV Driver loaded. This driver is licensed for non-commercial use
2020-10-14 22:53:05 [660] with Sundtek MediaTV only
2020-10-14 22:53:05 [660] Driver loaded within -910167276291050599 milliseconds
2020-10-14 22:53:05 [660] Serial(0): U121211082239
2020-10-14 22:53:05 [660] Enabling standby
2020-10-14 22:53:05 [660] Waking up device
2020-10-14 22:53:05 [660] registering ID: 1
2020-10-14 22:53:05 [660] Memory mapped transfers are not available
2020-10-14 22:53:05 [660] disconnecting kernel driver
2020-10-14 22:53:05 [660] unhandled videostandard 1185 0
2020-10-14 22:53:05 [660] SETTING DVB-C
2020-10-14 22:53:05 [660] Setting Frequency: 0
2020-10-14 22:53:05 [660] Setting Frequency: 0
2020-10-14 22:53:05 [660] Setting Symbolrate: 0
2020-10-14 22:53:05 [660] Setting Modulation: 0
2020-10-14 22:53:05 [660] requested QAM Modulation not supported
failure: error retrieving lock status
2020-10-14 22:53:05 [660] DMX_SET_SOURCE not implemented
2020-10-14 22:53:05 [660] DMX_SET_SOURCE not implemented
2020-10-14 22:53:07 [660] attaching second generation DVB-S/S2 demodulator
2020-10-14 22:53:09 [660] demodulator successfully attached (DVB_S/S2)!
2020-10-14 22:53:09 [660] Allocation using pg for type 65678
2020-10-14 22:53:09 [660] requesting to attach tuner(s) now
2020-10-14 22:53:09 [660] registering: adapter1/0
2020-10-14 22:53:09 [660] registered virtual: /dev/dvb/adapter1/frontend0
2020-10-14 22:53:09 [660] registered virtual: /dev/dvb/adapter1/demux0
2020-10-14 22:53:09 [660] registered virtual: /dev/dvb/adapter1/dvr0
2020-10-14 22:53:09 [660] Setting RC Protocol to NEC
2020-10-14 22:53:09 [660] Unable to create /dev/mediainput1 (17/File exists)
2020-10-14 22:53:09 [660] registered virtual: /dev/mediainput1
2020-10-14 22:53:09 [660] Remote Control Layout: 0
2020-10-14 22:53:09 [661] trying to load uinput module
2020-10-14 22:53:09 [661] loading uinput kernel extention failed, remote control will not work with lirc
2020-10-14 22:53:09 [660] No remote control support available
2020-10-14 22:53:09 [660]
2020-10-14 22:53:09 [660] Sundtek MediaTV Driver loaded. This driver is licensed for non-commercial use
2020-10-14 22:53:09 [660] with Sundtek MediaTV only
2020-10-14 22:53:09 [660] Driver loaded within -1429600621069289599 milliseconds
2020-10-14 22:53:09 [660] Serial(1): U130417144838
2020-10-14 22:53:09 [660] Enabling standby
2020-10-14 22:53:09 [660] Device is now in standby
2020-10-14 22:53:09 [660] Waking up device
2020-10-14 22:53:09 [660] Initial devicescan done, switching detection mode
2020-10-14 22:53:09 [660] Enabling standby
2020-10-14 22:53:10 [660] voltage is off
2020-10-14 22:53:10 [660] Setting Frequency: 0
2020-10-14 22:53:10 [660] Frequency: 0
2020-10-14 22:53:10 [660] Symbolrate: 0
2020-10-14 22:53:11 [660] Enabling standby
2020-10-14 22:53:11 [660] Device is now in standby
2020-10-14 22:53:11 [660] Waking up device
2020-10-14 22:53:12 [660] voltage is off
2020-10-14 22:53:12 [660] DMX_SET_SOURCE not implemented
2020-10-14 22:53:12 [660] Enabling standby
2020-10-14 22:53:12 [660] Device is now in standby

Habe ich es richtig verstanden, dass "mediasrv -v" den Treiber im Debug startet? Es kommen folgende Ausgaben, wenn ich versuche auf eine Freq zu tunen und dann das signal zu lesen:

2020-10-14 23:07:17 [771] Waking up device
2020-10-14 23:07:17 [771] SETTING DVB-C
2020-10-14 23:07:17 [771] reinitializing previous digital TV parameters
2020-10-14 23:07:17 [771] Setting Frequency: 554000000
2020-10-14 23:07:17 [771] Setting Symbolrate: 6900000
2020-10-14 23:07:17 [771] Setting Modulation: 5
failure: error retrieving lock status
2020-10-14 23:07:17 [771] Setting Frequency: 554000000
2020-10-14 23:07:17 [771] Setting Symbolrate: 6900000
2020-10-14 23:07:17 [771] Setting Modulation: 5
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
2020-10-14 23:07:17 [771] Enabling standby
2020-10-14 23:07:24 [771] Waking up device
2020-10-14 23:07:24 [771] SETTING DVB-C
2020-10-14 23:07:24 [771] reinitializing previous digital TV parameters
2020-10-14 23:07:24 [771] Setting Frequency: 554000000
2020-10-14 23:07:24 [771] Setting Symbolrate: 6900000
2020-10-14 23:07:24 [771] Setting Modulation: 5
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
failure: error retrieving lock status
2020-10-14 23:07:25 [771] Enabling standby

p.s.: Probeweise habe ich mittlerweile den nicht mehr benötigten DVB-S2 Stick zusätzlich dran. Sorry für die Verwirrung

8
Danke für die Rückmeldung!

Ich hatte den Treiber anfangs auf dem Host, hab ihn aber da mit ./sundtek_netinst.sh -u gelöscht! Ist das alles was ich machen muss?

Nachdem ich dann die Karte erfolgreich im Container und auch im TVH gefunden habe, musste ich feststellen, dass ich kein signal im docker habe.

Um zu verifizieren, dass der TV Stick funktioniert habe ich den Treiber wieder im Host installiert und da mit Signal.

root@7d4a98424ac2:/# /opt/bin/mediasrv -v
2020-10-14 22:35:14 [464] UID: 0 SUID 0

Was wäre hier das erwartete Ergebnis?

9
Moin zusammen,

ich habe einen Raspberry 3 mit Raspberry Pi OS Buster / Kernel 5.4 installiert und direkt am USB Port eine [Sundtek MediaTV Digital Home (USB 2.0)]  DVB-C, DVB-T, REMOTE-CONTROL.

Ziel ist tvheadend im Docker Container (linuxserver/tvheadend) zu betreiben.
pi@raspberrypi:/docker/tvheadend $ cat docker-compose.yml
version: "2.1"
services:
  tvheadend:
    image: linuxserver/tvheadend
    container_name: tvheadend
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Berlin
    volumes:
      - /docker/tvheadend/conf:/config
      - /docker/tvheadend/rec:/recordings
    ports:
      - 9981:9981
      - 9982:9982
    devices:
      - /dev/dvb:/dev/dvb
      - /dev/bus/usb:/dev/bus/usb
    restart: unless-stopped

Treiber habe ich erfolgreich in dem Container installiert, Karte wird erkannt, aber ich bekomme kein lock auf eine Frequenz und auch kein Signal:

root@8cd84b71c655:/# /opt/bin/mediaclient -e
**** List of Media Hardware Devices ****
device 0: [Sundtek MediaTV Digital Home (USB 2.0)]  DVB-C, DVB-T, REMOTE-CONTROL
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 1-1.4
  [SERIAL]:
     ID: U121211082239
  [DVB-C,DVB-T]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0


root@8cd84b71c655:/# /opt/bin/mediaclient -m DVBC -f 554000000 -M Q256 -S 6900000 -d /dev/dvb/adapter0/frontend0
Using device: /dev/dvb/adapter0/frontend0
Checking for lock:
..........

root@8cd84b71c655:/# /opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0
== reading digital TV signal ==
SIGNAL: [                                 ] (  0%) BER:      0 FREQ: 554000000  Hz LOCKED:  NO MER: 0 SYM: 6900000 MOD: QAM256
SIGNAL: [                                 ] (  0%) BER:      0 FREQ: 554000000  Hz LOCKED:  NO MER: 0 SYM: 6900000 MOD: QAM256

Wenn ich den Treiber nachträglich zusätzlich auf dem Pi direkt installiere, bekomme ich sowohl lock bei der Frequenz als auch Signal. Habe ich was im docker-compose vergessen zum Container durchzuschleifen, so dass der Container die Karte nicht steuern kann?

pi@raspberrypi:~ $ /opt/bin/mediaclient -m DVBC -f 554000000 -M Q256 -S 69000000
Using device: /dev/dvb/adapter0/frontend0
Checking for lock:
. [LOCKED]
pi@raspberrypi:~ $ /opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0
== reading digital TV signal ==
SIGNAL: [.................................] (100%) BER:      1 FREQ: 554000000  Hz LOCKED: YES MER: 381 SYM: 69000000 MOD: QAM256
SIGNAL: [.................................] (100%) BER:      1 FREQ: 554000000  Hz LOCKED: YES MER: 378 SYM: 69000000 MOD: QAM256
SIGNAL: [.................................] (100%) BER:      1 FREQ: 554000000  Hz LOCKED: YES MER: 376 SYM: 69000000 MOD: QAM256
SIGNAL: [.................................] (100%) BER:      1 FREQ: 554000000  Hz LOCKED: YES MER: 378 SYM: 69000000 MOD: QAM256

Seiten: [1]