Neueste Beiträge

Seiten: 1 ... 7 8 [9] 10
81
Sundtek MediaTV Pro / Re: DVB-S2 UsbStick defekt Hardware?
« Letzter Beitrag von HannMuell am März 03, 2026, 03:40:00 Nachmittag »
stick ist beim schwiegervater angekommen:
leider funktioniert er dort nicht:

Code: [Auswählen]
:/opt/bin# /opt/bin/mediaclient --tsscan /dev/dvb/adapter0/dvr0
media scan tp: 0
Timed out after 1 seconds
Total found: 0 PMTs (incl. unknown 0x0000)
Scan finished after 0 packets (0 bytes)
root@ThinkCentre:/opt/bin# /opt/bin/mediaclient --testastra -d /dev/dvb/adapter0/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:
..........

82
Sundtek MediaTV Pro / Re: DVB-S2 UsbStick defekt Hardware?
« Letzter Beitrag von Sundtek am Februar 25, 2026, 12:44:04 Nachmittag »
Bitte beachten, auf dem Host müssen auch /dev/dvb/adapterN nodes vorhanden sein bevor das Docker System gestartet wird.
Da alle Docker Systeme etwas unterschiedlich sind sollte man eventuell den Docker-Author benachrichtigen oder man muss halt selber einige Modifikationen vornehmen.

Der Treiber kann das auf dem Host erstellen.
cd /tmp
wget http://sundtek.de/media/sundtek_netinst.sh
chmod +x sundtek_netinst.sh
./sundtek_netinst.sh -dockerhost
83
Sundtek MediaTV Pro / Re: DVB-S2 UsbStick defekt Hardware?
« Letzter Beitrag von HannMuell am Februar 25, 2026, 12:39:32 Nachmittag »
Okay. Dann schicke ich dem Schwiegervater den Stick zurück und versuche aus der Ferne den Stick mit TVHeadend und docker wieder zum laufen zu bekommen.
Vielleicht hat sich im docker image auch irgendwas geänder warum er nicht mehr richtig tunen konnte.

Muss ich debuggen. Melde mich dann wenn ich mehr weiß.
BTW: gibt es einen offiziellen weg TVHeadend Docker zu nutzen?

ich hatte immer ein custom image generiert - das hat eigentlich immer funktioniert:
DOCKERFILE
Code: [Auswählen]
FROM linuxserver/tvheadend:latest
COPY sundtek/sundtek_netinst.sh /sundtek/
RUN yes Y | sh /sundtek/sundtek_netinst.sh -docker -use-custom-path=/sundtek
compose:
Code: [Auswählen]
  tvheadend:
    container_name: tvheadend
    build: ./tvheadend
    privileged: true
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Berlin
    volumes:
      - /home/xxx/.docker/tvheadend/config:/config
      - /home/xxx/.docker/tvheadend/picons:/picons
      - /mnt/recordings:/recordings
      - /etc/localtime:/etc/localtime:ro
    ports:
      - 9981:9981
      - 9982:9982
    devices:
      - /dev/dvb:/dev/dvb
      - /dev/bus/usb
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/dri/card0:/dev/dri/card0
    restart: unless-stopped
84
Sundtek MediaTV Pro / Re: DVB-S2 UsbStick defekt Hardware?
« Letzter Beitrag von Sundtek am Februar 25, 2026, 12:33:25 Nachmittag »
Ok also der Tuner funktioniert, das waren die technischen Standard-Tests um die Funktionalität des Tuners zu testen.

Womit hast Du jetzt Probleme?
85
Sundtek MediaTV Pro / Re: DVB-S2 UsbStick defekt Hardware?
« Letzter Beitrag von HannMuell am Februar 25, 2026, 12:32:32 Nachmittag »
Code: [Auswählen]
/opt/bin/mediaclient --testastra -d /dev/dvb/adapter0/frontend0
Testing Astra 19.2 Frequencies
DVBS
LO Band / 18V:
Checking for lock:
. [LOCKED]
LO Band / 13V:
Checking for lock:
. [LOCKED]
HI Band / 18V:
Checking for lock:
. [LOCKED]
HI Band / 13V:
Checking for lock:
. [LOCKED]
DVB-S2 ZDF HD / 18V
Checking for lock:
. [LOCKED]


/opt/bin/mediaclient --tsscan /dev/dvb/adapter0/dvr0
Code: [Auswählen]
media scan tp: 0
** NO GROUP GIVEN **
** NO GROUP GIVEN **
** NO GROUP GIVEN **
** NO GROUP GIVEN **
** NO GROUP GIVEN **
** NO GROUP GIVEN **
PMT PID: 0x17d4
  Program Number: 0x2b66
  TransportstreamID: 1011
  Encrypted: No
  Service type: 19
  Service running: Yes
  Provider Name: ZDFvision
  Service Name: ZDF HD
    --> 0x17f3 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x17f4 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x181a (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections)
    --> 0x181b (ISO/IEC 13818-6 type B)
    --> 0x181c (ISO/IEC 13818-6 type C)
    --> 0x17de (27)
    --> 0x17e8 (ISO/IEC 11172 Audio)
    --> 0x17e9 (ISO/IEC 11172 Audio)
    --> 0x17eb (ISO/IEC 11172 Audio)
    --> 0x17ea (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x17f2 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
PMT PID: 0x189c
  Program Number: 0x2b7a
  TransportstreamID: 1011
  Encrypted: No
  Service type: 19
  Service running: Yes
  Provider Name: ZDFvision
  Service Name: zdf_neo HD
    --> 0x18bb (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x18e2 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections)
    --> 0x18e3 (ISO/IEC 13818-6 type B)
    --> 0x18e4 (ISO/IEC 13818-6 type C)
    --> 0x18a6 (27)
    --> 0x18b0 (ISO/IEC 11172 Audio)
    --> 0x18b1 (ISO/IEC 11172 Audio)
    --> 0x18b3 (ISO/IEC 11172 Audio)
    --> 0x18b2 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x18ba (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
PMT PID: 0x1af4
  Program Number: 0x2bb6
  TransportstreamID: 1011
  Encrypted: No
  Service type: 2
  Service running: Yes
  Provider Name: ZDFvision
  Service Name: Dlf Kultur
    --> 0x1af5 (ISO/IEC 11172 Audio)
    --> 0x1afb (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections)
PMT PID: 0x1afe
  Program Number: 0x2bb7
  TransportstreamID: 1011
  Encrypted: No
  Service type: 2
  Service running: Yes
  Provider Name: ZDFvision
  Service Name: Dlf
    --> 0x1aff (ISO/IEC 11172 Audio)
    --> 0x1b05 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections)
PMT PID: 0x1b08
  Program Number: 0x2bb8
  TransportstreamID: 1011
  Encrypted: No
  Service type: 2
  Service running: Yes
  Provider Name: ZDFvision
  Service Name: Dlf Nova
    --> 0x1b09 (ISO/IEC 11172 Audio)
    --> 0x1b0f (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections)
PMT PID: 0x1b12
  Program Number: 0x2bb9
  TransportstreamID: 1011
  Encrypted: No
  Service type: 2
  Service running: Yes
  Provider Name: ZDFvision
  Service Name: DRadio Dok&Deb
    --> 0x1b13 (ISO/IEC 11172 Audio)
Total found: 6 PMTs (incl. unknown 0x0000)
Scan finished after 35 packets (6580 bytes)
86
Sundtek MediaTV Pro / Re: DVB-S2 UsbStick defekt Hardware?
« Letzter Beitrag von Sundtek am Februar 25, 2026, 12:29:47 Nachmittag »
Ah sehr gut, ich habe das falsche Gerät angegeben, mein Fehler

Es sollte frontend0 sein und nicht dvr0, dvr0 versteht die Steuerbefehle nicht:

/opt/bin/mediaclient --testastra -d /dev/dvb/adapter0/frontend0
/opt/bin/mediaclient --tsscan /dev/dvb/adapter0/dvr0

dvr0 = da kommen die Daten raus
frontend0 = Steuerung des Tuners
87
Sundtek MediaTV Pro / Re: DVB-S2 UsbStick defekt Hardware?
« Letzter Beitrag von HannMuell am Februar 25, 2026, 12:27:49 Nachmittag »
wenn ich parrallel zum verbose start von mediasrv einen testscan mache kommt das bei medisrv:
Code: [Auswählen]
2026-02-25 11:25:42 [270529] IR Setup
2026-02-25 11:25:42 [270529] Initializing Remote Control Support (interrupt)
2026-02-25 11:25:42 [270529] registered virtual: /dev/mediainput0
2026-02-25 11:25:42 [270529] registering: adapter0/0
2026-02-25 11:25:42 [270529] registered virtual: /dev/dvb/adapter0/frontend0
2026-02-25 11:25:42 [270529] registered virtual: /dev/dvb/adapter0/demux0
2026-02-25 11:25:42 [270529] registered virtual: /dev/dvb/adapter0/dvr0
2026-02-25 11:25:42 [270529] Driver loaded within 2373 milliseconds
2026-02-25 11:25:47 [270529] Initial devicescan done, switching detection mode
2026-02-25 11:25:57 [270529] [FE0] . o ( Enabling Standby ) o .
2026-02-25 11:25:57 [270529] [FE0] Set Voltage off
2026-02-25 11:26:30 [270529] [FE0] . o ( Waking up from standby ) o .
2026-02-25 11:26:30 [270529] [FE0] Set Voltage off
2026-02-25 11:26:30 [270529] INIT_DTV: 0
2026-02-25 11:26:30 [270529] Starting transfer
2026-02-25 11:26:30 [270529] ignoring dvr cmd: 40106f52
2026-02-25 11:26:30 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:30 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:30 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 40106f52
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 40106f52
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:31 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 40106f52
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 40106f52
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:32 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:33 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:33 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:33 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:33 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:33 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:33 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:33 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:33 [270529] ignoring dvr cmd: 80046f45
2026-02-25 11:26:33 [270529] INIT_DTV: 0
2026-02-25 11:26:33 [270529] Starting transfer
2026-02-25 11:26:50 [270529] [FE0] . o ( Enabling Standby ) o .
2026-02-25 11:26:50 [270529] [FE0] Set Voltage off
88
Sundtek MediaTV Pro / Re: DVB-S2 UsbStick defekt Hardware?
« Letzter Beitrag von HannMuell am Februar 25, 2026, 12:25:53 Nachmittag »
Code: [Auswählen]
/opt/bin# ./mediasrv -v
2026-02-25 11:24:31 [270299] UID: 0 SUID 0
2026-02-25 11:24:31 [270299] Alsa Blocking on (default)
2026-02-25 11:24:31 [270299] Starting up Multimedia Framework (Jan 24 2026 00:58:34)
2026-02-25 11:24:31 [270299] Semaphore exists, removing and reallocating it
2026-02-25 11:24:31 [270299] Detected DVB version.h
2026-02-25 11:24:31 [270300] Starting service processor (PID 270300)
2026-02-25 11:24:31 [270299] API Version: 5.12
2026-02-25 11:24:31 [270299] Running on Linux (6.12.69+deb13-amd64)
2026-02-25 11:24:31 [270299] Detected: AuthenticAMD
2026-02-25 11:24:31 [270299] This CPU supports: MMX, SSE, SSE2
2026-02-25 11:24:31 [270299] scanning devices
2026-02-25 11:24:31 [270299]
2026-02-25 11:24:31 [270299] Scanning for drivers
2026-02-25 11:24:31 [270299] found lib: libdrv_fm.so
2026-02-25 11:24:31 [270299] found lib: libdrv_fm_dab_dabplus.so
2026-02-25 11:24:31 [270299] found lib: libdrv_net.so
2026-02-25 11:24:31 [270299] found lib: libdrv_tntdvb.so
2026-02-25 11:24:31 [270299] found lib: libdrv_vivi.so
2026-02-25 11:24:31 [270299] found lib: libdrv_hikarisoft_isdb.so
2026-02-25 11:24:31 [270299] found lib: libdrv_ngTV.so
2026-02-25 11:24:31 [270299] found lib: libdrv_em28xx.so
2026-02-25 11:24:31 [270299] found lib: libdrv_eLight.so
2026-02-25 11:24:31 [270299]
2026-02-25 11:24:31 [270299] Scanning for plugins
2026-02-25 11:24:31 [270299]
2026-02-25 11:24:31 [270299] Starting up device manager
2026-02-25 11:24:32 [270299] registering ID: 0
2026-02-25 11:24:32 [270299] Memory mapped transfers are not available
2026-02-25 11:24:32 [270299] Board config found: Sundtek SkyTV 8 (eLight)
2026-02-25 11:24:32 [270299] This board provides 1 frontends
2026-02-25 11:24:32 [270299]
2026-02-25 11:24:32 [270299] registering bandwidth report
2026-02-25 11:24:32 [270299] Initializing SYSV-IPC
2026-02-25 11:24:32 [270299] Allocation using pg for type 65678
2026-02-25 11:24:32 [270299] scanning devices done
2026-02-25 11:24:32 [270299] attached devices:
2026-02-25 11:24:32 [270300] Autostarting scripts in /etc/sundtek/
2026-02-25 11:24:32 [270300] executed all available items
2026-02-25 11:24:34 [270299] demodulator successfully attached (DVB_S/S2)!
2026-02-25 11:24:34 [270299]
2026-02-25 11:24:34 [270299] Vertical Polarisation is set to 13.00 Volt
2026-02-25 11:24:34 [270299] Horizontal Polarisation is set to 19.80 Volt
2026-02-25 11:24:34 [270299] Current limit is set to 400 mA
2026-02-25 11:24:34 [270299]
2026-02-25 11:24:34 [270299] Using Sundtek remote control layout
2026-02-25 11:24:34 [270299]
2026-02-25 11:24:34 [270299] IR Setup
2026-02-25 11:24:34 [270299] Initializing Remote Control Support (interrupt)
2026-02-25 11:24:34 [270299] Unable to create /dev/mediainput0 (17/File exists)
2026-02-25 11:24:34 [270299] registered virtual: /dev/mediainput0
2026-02-25 11:24:34 [270299] registering: adapter0/0
2026-02-25 11:24:34 [270299] registered virtual: /dev/dvb/adapter0/frontend0
2026-02-25 11:24:34 [270299] registered virtual: /dev/dvb/adapter0/demux0
2026-02-25 11:24:34 [270299] registered virtual: /dev/dvb/adapter0/dvr0
2026-02-25 11:24:34 [270299] Driver loaded within 2425 milliseconds
2026-02-25 11:24:39 [270299] Initial devicescan done, switching detection mode
2026-02-25 11:24:49 [270299] [FE0] . o ( Enabling Standby ) o .
2026-02-25 11:24:49 [270299] [FE0] Set Voltage off
89
Sundtek MediaTV Pro / Re: DVB-S2 UsbStick defekt Hardware?
« Letzter Beitrag von Sundtek am Februar 25, 2026, 12:22:19 Nachmittag »
Du kannst den Treiber auch mal manuell starten und schauen ob es Fehlermeldungen gibt. Die Grüne LED ist eigentlich schon mal gut.

sudo -s
cd /opt/bin
killall -9 mediasrv
./mediaclient --shutdown # falls es auf dem System kein killall gibt
./mediasrv -v

90
Sundtek MediaTV Pro / Re: DVB-S2 UsbStick defekt Hardware?
« Letzter Beitrag von HannMuell am Februar 25, 2026, 12:17:33 Nachmittag »
Also LNB Signal kann ich ausschliessen.
Koax habe ich am Fernseher entnommen. Das Signal funktioneirt vorher noch am TV.
12V Habe ich das alte gemesse, hatte 12V.
Habe gestern ein neues 12V umgebaut (also alter Stecker auf neues 12V Netzteil) - weil ich dachte dass evtl zu wenig Strom fließt / Netzteil defekt ist.
Also auch dass neue Netzteil führt zu dem selben Verhalten.
Netzteil kann ich mit sehr hoher Wahrscheinlichkeit also auch ausschliessen

Während dem ausführen der beiden Befehle leuchtet die LED grün.

Seiten: 1 ... 7 8 [9] 10