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 - chili

Seiten: 1 [2]
16
So. Seit gestern sind wieder die Satellite Config des VIII Dualtuners weg und kommen auch in TVHeadend nicht wieder.
Bisher habe ich TV-Headend komplett gelöscht (apt remove purge) und neu installiert und konnte dann auch den VIII wieder in Betrieb nehmen.
Jetzt hab ich es mal so gelassen und warte auf Hilfe.

Der VI funktioniert hingegen seid Jahren zuverlässig. Mein Problem ist der VIII Dual an Pi4 mit  Debian

17
Hallo,

ich mache wieder mal ein Thema auf. Obwohl es besser wurde funktioniert es immer noch nicht zuverlässig.
Verbessert hat es sich nachdem ich täglich per Cron in der Nacht reboote.
Aktuell ist im TvHeadend alles ok, Sender kommen trotzdem nicht rein.
Bevor ich neustartete hab ich mal dmesg ausgeführt. Hier die Meldungen:

[    3.394658] random: systemd: uninitialized urandom read (16 bytes read)
[    3.399107] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    3.401448] random: systemd: uninitialized urandom read (16 bytes read)
[    3.402309] systemd[1]: Reached target Swap.
[    3.405218] systemd[1]: Listening on Journal Socket (/dev/log).
[    3.407662] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    3.410116] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    3.413320] systemd[1]: Created slice User and Session Slice.
[    3.417367] systemd[1]: Listening on Syslog Socket.
[    3.522952] i2c /dev entries driver
[    4.144046] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    4.241243] systemd-journald[121]: Received request to flush runtime journal from PID 1
[    4.861016] gpio-fan gpio-fan@0: GPIO fan initialized
[    4.912015] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x00010000
[    4.913136] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0x00001000
[    4.913771] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x00010000
[    4.914303] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x00010000
[    4.984147] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[    4.986752] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[    4.986783] [vc_sm_connected_init]: start
[    4.988169] mc: Linux media interface: v0.10
[    4.988464] vc_sm_cma_vchi_init: failed to open VCHI service (-1)
[    4.988483] [vc_sm_connected_init]: failed to initialize shared memory service
[    5.023923] videodev: Linux video capture interface: v2.00
[    5.102118] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    5.104702] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    5.109824] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[    5.112799] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[    5.120154] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[    5.125125] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
[    5.149918] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
[    5.174868] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
[    5.933336] ads7846 spi0.1: supply vcc not found, using dummy regulator
[    5.934975] ads7846 spi0.1: touchscreen, irq 63
[    5.940447] input: ADS7846 Touchscreen as /devices/platform/soc/fe204000.spi/spi_master/spi0/spi0.1/input/input0
[    7.998800] random: crng init done
[    7.998823] random: 7 urandom warning(s) missed due to ratelimiting
[    8.102476] 8021q: 802.1Q VLAN Support v1.8
[    8.332330] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    8.551905] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    8.614902] Adding 102396k swap on /var/swap.  Priority:-2 extents:4 across:4206588k SSFS
[    8.721091] bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay)
[    8.722470] bcmgenet fd580000.ethernet eth0: Link is Down
[   13.203469] input: Sundtek Remote Control as /devices/virtual/input/input1
[   13.914947] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   13.914975] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   15.919538] ICMPv6: process `dhcpcd' is using deprecated sysctl (syscall) net.ipv6.neigh.eth0.retrans_time - use net.ipv6.neigh.eth0.retrans_time_ms instead
[   16.743668] usb 1-1.2: usbfs: process 524 (mediasrv) did not claim interface 0 before use
[   16.804780] input: Sundtek Remote Control as /devices/virtual/input/input2
[   22.758805] fuse: init (API version 7.32)
[   33.125222] usb 1-1.1: usbfs: process 557 (mediasrv) did not claim interface 2 before use


Konfiguration hier ist: Oben auf dem Boden ein Pi4 mit Sky Ultimate Dual (RaspiOS mit Touchscreen, Pihole und Unbound)
Netzteil bringt stabil 3A das wurde schon vor Monaten gekauft. Seitdem sind der Undervioltage Meldungen weg

Pi4 an 7590 Client-Box, diese per 1Gb Meshlan an 7590 Masterbox (DSL50)
Ebenfalls an dieser Masterbox ist der 2. Pi4 (Libreelec) mit Gbit Lan

Vielleicht helfen ja die dmesg Meldungen vom Pi4 mit dem Sky Uötimate Dual

Aktuell bin ich auch im Chat

18
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Re: Kein Empfang mehr
« am: Februar 24, 2021, 04:40:56 Nachmittag »
Hmm. ich schick mal einen Screenshot hinterher.
Auch wenn ich den Wizard neu starte fehlt der zweite Tuner.
Präzision, die LNB wird nicht gefunden. Zur Probe hab ich die Antennenanschlüsse gewechselt. Dies ändert nichts.
Beide blauen LEDs leuchten am Sky Ultimate


Hmm geht nicht. Ein 24,5 kb Bild wird abgelehnt wegen Speicher voll - Admin kontaktieren

19
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Re: Kein Empfang mehr
« am: Februar 23, 2021, 11:48:02 Nachmittag »
Ich kann mich hier anschliessen. Aktuell habe ich jetzt einen Pi4 mit 3A Netzteil dran und bei dmesg keine Undervolt-Meldungen mehr. Aussetzer kamen trotzdem noch öfter vor, die ich notgedrungen tolerierte.
Seid heute ist aber der adapter1 anscheinend tot. Zur Probe habe ich die Antennenkabel gewechselt aber keine Änderung bekommen.
Anbei der Auszug von Mediaclient -e

**** List of Media Hardware Devices ****
device 0: [             Dual S2]  DVB-S/S2, REMOTE-CONTROL, DVB-S/S2
  [INFO]:
     STATUS: ACTIVE
  [BUS]:
     ID: 1-1.2
  [SERIAL]:
     ID: U200627083240
  [DVB-S/S2]:
     FESTATUS: ACTIVE
     LNBVOLTAGE: ENABLED
     LNBSUPPLY: USBPOWER
     LNBSTATUS: OK
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0
  [DVB-S/S2]:
     FESTATUS: STANDBY
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0

== reading digital TV signal ==
SIGNAL: [..............................   ] ( 91%) SATQUALITY:  80%  SNR:  13  BER:      0 FREQ: 1612000    Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_2_3 MOD: PSK_8 VOLTAGE: H(18V) TONE: OFF
SIGNAL: [..............................   ] ( 91%) SATQUALITY:  83%  SNR:  14  BER:      0 FREQ: 1612000    Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_2_3 MOD: PSK_8 VOLTAGE: H(18V) TONE: OFF
SIGNAL: [..............................   ] ( 91%) SATQUALITY:  83%  SNR:  14  BER:      0 FREQ: 1612000    Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_2_3 MOD: PSK_8 VOLTAGE: H(18V) TONE: OFF
SIGNAL: [..............................   ] ( 91%) SATQUALITY:  80%  SNR:  14  BER:      0 FREQ: 1612000    Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_2_3 MOD: PSK_8 VOLTAGE: H(18V) TONE: OFF
SIGNAL: [..............................   ] ( 91%) SATQUALITY:  83%  SNR:  14  BER:      0 FREQ: 1612000    Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_2_3 MOD: PSK_8 VOLTAGE: H(18V) TONE: OFF
SIGNAL: [..............................   ] ( 91%) SATQUALITY:  83%  SNR:  14  BER:      0 FREQ: 1612000    Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_2_3 MOD: PSK_8 VOLTAGE: H(18V) TONE: OFF
SIGNAL: [..............................   ] ( 91%) SATQUALITY:  80%  SNR:  14  BER:      0 FREQ: 1612000    Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_2_3 MOD: PSK_8 VOLTAGE: H(18V) TONE: OFF
SIGNAL: [..............................   ] ( 91%) SATQUALITY:  83%  SNR:  14  BER:      0 FREQ: 1612000    Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_2_3 MOD: PSK_8 VOLTAGE: H(18V) TONE: OFF
SIGNAL: [..............................   ] ( 91%) SATQUALITY:  83%  SNR:  13  BER:      0 FREQ: 1612000    Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_2_3 MOD: PSK_8 VOLTAGE: H(18V) TONE: OFF
SIGNAL: [..............................   ] ( 91%) SATQUALITY:  80%  SNR:  14  BER:      0 FREQ: 1612000    Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_2_3 MOD: PSK_8 VOLTAGE: H(18V) TONE: OFF
thor@raspberrypi:~ $ /opt/bin/mediaclient --readsignal=10 -d /dev/dvb/adapter1/frontend0
== reading digital TV signal ==
SIGNAL: [                                 ] (  0%) SATQUALITY:   0%  SNR:   0  BER:      0 FREQ: 0          Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%) SATQUALITY:   0%  SNR:   0  BER:      0 FREQ: 0          Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%) SATQUALITY:   0%  SNR:   0  BER:      0 FREQ: 0          Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%) SATQUALITY:   0%  SNR:   0  BER:      0 FREQ: 0          Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%) SATQUALITY:   0%  SNR:   0  BER:      0 FREQ: 0          Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%) SATQUALITY:   0%  SNR:   0  BER:      0 FREQ: 0          Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%) SATQUALITY:   0%  SNR:   0  BER:      0 FREQ: 0          Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%) SATQUALITY:   0%  SNR:   0  BER:      0 FREQ: 0          Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%) SATQUALITY:   0%  SNR:   0  BER:      0 FREQ: 0          Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%) SATQUALITY:   0%  SNR:   0  BER:      0 FREQ: 0          Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF

Eine verdächteige Meldung aus dmesg
[27966.385084] usb 1-1.2: usbfs: process 5916 (mediasrv) did not claim interface 0 before use

So langsam denke ich das Gerät hat eine Macke oder das 4er LNB.

Seiten: 1 [2]