Jump to content


Photo

vu+duo2 loop steeds vast op de nieuwe image

Vuduo2

  • Please log in to reply
95 replies to this topic

Re: vu+duo2 loop steeds vast op de nieuwe image #81 WanWizard

  • PLi® Core member
  • 70,381 posts

+1,807
Excellent

Posted 22 November 2018 - 12:12

Weer niks bijzonders in de logs, ik verdenk steeds meer de voeding van die box... 


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: vu+duo2 loop steeds vast op de nieuwe image #82 snowman.nl

  • Senior Member
  • 189 posts

+2
Neutral

Posted 22 November 2018 - 16:37

kun je de voeding testen of aan zijn grenzen testen ??



Re: vu+duo2 loop steeds vast op de nieuwe image #83 WanWizard

  • PLi® Core member
  • 70,381 posts

+1,807
Excellent

Posted 22 November 2018 - 16:53

Je zou er eens naar kunnen kijken, of er nergens Elco's bol staan. Electronica heb ik na mijn MTS niks meer mee gedaan, dus dat is meer dan roestig... ;)


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: vu+duo2 loop steeds vast op de nieuwe image #84 snowman.nl

  • Senior Member
  • 189 posts

+2
Neutral

Posted 22 November 2018 - 17:20

heb net de kap los gehad even de stof er afgeblazen is nou weer mooi schoon ook de elco's bij langs geweest zien er allemaal super uit kon ook verder geen gekke dingen aan het bord :huh:



Re: vu+duo2 loop steeds vast op de nieuwe image #85 snowman.nl

  • Senior Member
  • 189 posts

+2
Neutral

Posted 22 November 2018 - 17:23

deze kwam ik nog tegen van gister

 

 

OpenPLi Enigma2 crash log

crashdate=wo nov 21 17:58:02 2018
compiledate=Nov 16 2018
skin=PLi-FullNightHD/skin.xml
sourcedate=2018-11-15
branch=rc
rev=8b21072
component=Enigma2

stbmodel=duo2
stbmodel=dm8000
kernelcmdline=libata.force=1:1.5Gbps bmem=192M@64M bmem=220M@512M memc1=788M ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs rw rootflags=sync
nimsockets=NIM Socket 0:
imageissue=openpli 7.0-rc %h


ADD Peer vuuno4kse=vuuno4kse.local:8001
ADD Peer vuuno4kse=vuuno4kse.local:8001
ADD Peer vuduo2=vuduo2.local:8001
REMOVE Peer vuuno4kse
REMOVE Peer vuduo2-2
REMOVE Peer vuuno4kse
REMOVE Peer vuduo2
REMOVE Peer vuduo2-2
ADD Peer vuuno4kse=vuuno4kse.local:8001
ADD Peer vuuno4kse=vuuno4kse.local:8001
ADD Peer vuduo2=vuduo2.local:8001
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 49, in action
  File "/usr/lib/enigma2/python/Plugins/Extensions/XCplugin/plugin.py", line 2662, in runList
    path = self.Movies[idx]#config.plugins.XCplugin.pthmovie.value# + 'movie/'
IndexError: list index out of range


dmesg

<6>hub 4-0:1.0: USB hub found
<6>hub 4-0:1.0: 1 port detected
<6>ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
<6>ohci-brcm ohci-brcm.0: Broadcom STB OHCI
<6>ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 5
<6>ohci-brcm ohci-brcm.0: irq 68, io mem 0x10480400
<6>hub 5-0:1.0: USB hub found
<6>hub 5-0:1.0: 1 port detected
<6>ohci-brcm ohci-brcm.1: Broadcom STB OHCI
<6>ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 6
<6>ohci-brcm ohci-brcm.1: irq 69, io mem 0x10480600
<6>ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
<6>ata2.00: ATA-8: WDC WD2500AAJS-75B4A0, 01.03A01, max UDMA/133
<6>ata2.00: 488281250 sectors, multi 0: LBA48 NCQ (depth 31/32)
<6>hub 6-0:1.0: USB hub found
<6>ata2.00: configured for UDMA/133
<5>scsi 1:0:0:0: Direct-Access     ATA      WDC WD2500AAJS-7 01.0 PQ: 0 ANSI: 5
<5>sd 1:0:0:0: [sda] 488281250 512-byte logical blocks: (250 GB/232 GiB)
<5>sd 1:0:0:0: [sda] Write Protect is off
<7>sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
<5>sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<5>sd 1:0:0:0: Attached scsi generic sg0 type 0
<6> sda: sda1
<5>sd 1:0:0:0: [sda] Attached SCSI disk
<6>hub 6-0:1.0: 1 port detected
<6>ohci-brcm ohci-brcm.2: Broadcom STB OHCI
<6>ohci-brcm ohci-brcm.2: new USB bus registered, assigned bus number 7
<6>ohci-brcm ohci-brcm.2: irq 73, io mem 0x10490400
<6>hub 7-0:1.0: USB hub found
<6>hub 7-0:1.0: 1 port detected
<6>ohci-brcm ohci-brcm.3: Broadcom STB OHCI
<6>ohci-brcm ohci-brcm.3: new USB bus registered, assigned bus number 8
<6>ohci-brcm ohci-brcm.3: irq 74, io mem 0x10490600
<6>usb 4-1: new high-speed USB device number 2 using ehci-brcm
<6>hub 8-0:1.0: USB hub found
<6>hub 8-0:1.0: 1 port detected
<6>usbcore: registered new interface driver usb-storage
<6>mousedev: PS/2 mouse device common for all mice
<6>i2c /dev entries driver
<6>IR NEC protocol handler initialized
<6>IR RC5(x) protocol handler initialized
<6>IR RC6 protocol handler initialized
<6>IR JVC protocol handler initialized
<6>IR Sony protocol handler initialized
<6>IR RC5 (streamzap) protocol handler initialized
<6>IR SANYO protocol handler initialized
<6>IR MCE Keyboard/mouse protocol handler initialized
<6>sdhci: Secure Digital Host Controller Interface driver
<6>sdhci: Copyright© Pierre Ossman
<6>sdhci-pltfm: SDHCI platform and OF driver helper
<6>hidraw: raw HID events driver © Jiri Kosina
<6>usbcore: registered new interface driver usbhid
<6>usbhid: USB HID core driver
<6>TCP: cubic registered
<6>NET: Registered protocol family 17
<5>Key type dns_resolver registered
<6>PM: CP0 COUNT/COMPARE frequency does not depend on divisor
<6>EBI CS0: setting up NAND flash (primary)
<6>NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)
<6>NAND device: 1024MiB, SLC, page size: 2048, OOB size: 64
<6>brcmnand brcmnand.0: 1024MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, Hamming ECC
<6>Bad block table found at page 524224, version 0x01
<6>Bad block table found at page 524160, version 0x01
<6>nand_read_bbt: bad block at 0x000027500000
<5>Creating 4 MTD partitions on "brcmnand.0":
<5>0x000002700000-0x000040000000 : "rootfs"
<5>0x000002700000-0x000040000000 : "rootfs(redundant)"
<5>0x000000200000-0x000000900000 : "kernel"
<5>0x000000900000-0x000000b00000 : "mac"
<5>UBI: attaching mtd0 to ubi0
<5>random: nonblocking pool is initialized
<5>UBI: scanning is finished
<5>UBI: attached mtd0 (name "rootfs", size 985 MiB) to ubi0
<5>UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
<5>UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
<5>UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
<5>UBI: good PEBs: 7875, bad PEBs: 5, corrupted PEBs: 0
<5>UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
<5>UBI: max/mean erase counter: 530/127, WL threshold: 4096, image sequence number: 1327819132
<5>UBI: available PEBs: 0, total reserved PEBs: 7875, PEBs reserved for bad PEB handling: 155
<5>UBI: background thread "ubi_bgt0d" started, PID 52
<6>ALSA device list:
<6>  No soundcards found.
<5>UBIFS: parse sync
<5>UBIFS: background thread "ubifs_bgt0_0" started, PID 55
<5>UBIFS: mounted UBI device 0, volume 0, name "rootfs"
<5>UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
<5>UBIFS: FS size: 978350080 bytes (933 MiB, 7705 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
<5>UBIFS: reserved for root: 0 bytes (0 KiB)
<5>UBIFS: media format: w4/r0 (latest is w4/r0), UUID 534C2B4F-B6ED-4BEA-B896-F0F10261A371, small LPT model
<6>VFS: Mounted root (ubifs filesystem) on device 0:12.
<6>devtmpfs: mounted
<6>Freeing unused kernel memory: 248K (80742000 - 80780000)
<6>EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
<4>procmk_init
<4>dvb_bcm7424: module license 'Proprietary' taints kernel.
<4>Disabling lock debugging due to kernel taint
<6>DVB: registering new adapter (_vuplus_duo2_)
<4>Booted !
<4>Booted !
<4>bcm7424: hotplug_callback():
<4>Hotplug - status.connected 1:0:0
<4>bcm7424: hotplug_callback():
<4>Hotplug - connecting HDMI to display 0xe
<4>[GPIO]Default
<4>[GP]:brcm_pwm_init
<4>
<4>bcm7424: hotplug_callback():
<4>Hotplug - status.connected 1:1:2
<6>brcm_demux_init: $Id: bcm_demux.c,v 0.7 $
<4>[MPVR]: >> misc_pvr_init
<4>[VID]: 6bcm7335_video_init
<4>[AUD]: 6bcm7335_audio_init
<6>BRCM brcm_dvb0: DVB: registering adapter 0 frontend 0 (Vuplus FE)...
<6>BRCM brcm_dvb0: DVB: registering adapter 0 frontend 0 (Vuplus FE)...
<4>bcm7424: bcm7335_frontend_init(): vtuner1 : 3
<4>BKNI_P_GetTrackAllocEntry_resize: resizing from 5376->8704
<4>BKNI_Malloc(linuxkernel) top users:
<4>    blocks,   bytes, filename:line
<4>      1024,  176128, portinginterface/hsm/src/common/bhsm.c:500
<4>       412,   94952, BSEAV/lib/utils/balloc.c:31
<4>       399,   28728, magnum/commonutils/mrc/src/bmrc_monitor.c:666
<4>  KSEG1 : 0x80000000
<4>lcr 0x3
<4>irq : 63 ret : 0
<6>input: dreambox advanced remote control (native) as /devices/virtual/input/input0
<4>Resistor Div: 0x0
<4>Duo2 LCD initialized 0
<6>[LCD]: registered
<6>[CI]: registered ci0 250
<6>[CI]: registered ci1 249
<6>[CI]: CI interface initialised
<6>
<6>[DFP]: registered dbox fp
<6>[DFP]: Scart 9597 is found 0
<6>
<6>[SC]: registered sci0
<6>[SC]: registered sci1
<4>system_time_set wakeup mode get
<4>system_time_set wakeup mode get 0xc4
<4>FP Update Driver Loaded
<4>VFDController Update Driver Loaded
<4>BKNI_P_GetTrackAllocEntry_resize: resizing from 8704->14080
<4>BKNI_Malloc(linuxkernel) top users:
<4>    blocks,   bytes, filename:line
<4>      1734,  373104, BSEAV/lib/utils/balloc.c:31
<4>      1024,  176128, portinginterface/hsm/src/common/bhsm.c:500
<4>fpga update driver loaded
<6>usb 4-1: reset high-speed USB device number 2 using ehci-brcm
<6>ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5392, rev 0223 detected
<6>ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5372 detected
<7>ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
<6>usbcore: registered new interface driver rt2800usb
<4>[VID]: VIDEO_SET_STREAMTYPE 1
<4>[VID]: VIDEO_SELECT_SOURCE 1  0
<4>[VID]: VIDEO_PLAY 1  5 0
<4>[VID]: VIDEO_CONTINUE 1  1
<4>[VID]: VIDEO_CLEAR_BUFFER 1  1 0
<4>[VID]: VIDEO_STOP 0  1
<4>[VID]: VIDEO_SELECT_SOURCE 0  0
<7>__clk_enable: network [1]
<7>bcm7425_pm_network_enable 00
<7>__clk_enable: enet [1]
<7>bcm40nm_pm_genet_enable 00
<6>bcmgenet bcmgenet.0 eth0: link up, 100 Mbps, full duplex
<6>NET: Registered protocol family 10
<4>[VID]: VIDEO_SET_STREAMTYPE 1
<4>[VID]: VIDEO_SELECT_SOURCE 1  0
<4>[VID]: VIDEO_PLAY 1  5 0
<4>[VID]: VIDEO_CONTINUE 1  1
<4>[VID]: VIDEO_CLEAR_BUFFER 1  1 0
<4>[VID]: VIDEO_STOP 0  1
<4>[VID]: VIDEO_SELECT_SOURCE 0  0
<3>UBI error: ubi_open_volume: cannot open device 0, volume 0, error -16
<4>[AUD]: AUDIO_SET_MUTE 0
<4>[AUD]: AUDIO_SET_MIXER -815759888
<4>[AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0
<4>[AUD]: AUDIO_SET_MIXER : next left volume 0, right volume 0
<4>[AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
<4>[AUD]: AUDIO_SET_MIXER -815759888
<4>[AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0
<4>[AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
<4>[AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
<4>FE tune
<4>[AUD]: AUDIO_SELECT_SOURCE 0
<4>[AUD]: AUDIO_SET_BYPASS_MODE 0
<4>[AUD]: AC3 downmix 0  state : 0
<4>[AUD]: AUDIO_PAUSE 0
<4>[AUD]: AUDIO_PLAY 0 decoder start : 0
<4>[VID]: VIDEO_SELECT_SOURCE 0  0
<4>[VID]: VIDEO_GET_SIZE src w: 1920 h:1080 display w:1920 h:1080
<4>[VID]: VIDEO_GET_SIZE aspect: 1 6
<4>[VID]: VIDEO_SET_STREAMTYPE 1
<4>[VID]: VIDEO_FREEZE 2145480768  0
<4>[VID]: VIDEO_PLAY 2145480768  5 2
<4>[VID]: VIDEO_SLOWMOTION 0    1
<4>[VID]: VIDEO_FAST_FORWARD 0    1
<4>[VID]: VIDEO_CONTINUE 0  1
<4>[AUD]: AUDIO_CONTINUE 0 1 aph=0xce2fbc00
<4>[AUD]: Mute : 0
<4>[AUD]: AUDIO_CHANNEL_SELECT 0
<4>[VID]: VIDEO_STOP 1  1
<4>[AUD]: AUDIO_STOP -2
<4>[AUD]: AUDIO_CONTINUE -2 0 aph=0x0
<4>[AUD]: AUDIO_CONTINUE aph=0 0 0
<4>[AUD]: AUDIO_SELECT_SOURCE 0
<4>[AUD]: AUDIO_SET_BYPASS_MODE 0
<4>[AUD]: AC3 downmix 0  state : 0
<4>[AUD]: AUDIO_PAUSE 0
<4>[AUD]: AUDIO_PLAY 0 decoder start : 0
<4>[VID]: VIDEO_SELECT_SOURCE 0  0
<4>[VID]: VIDEO_SET_STREAMTYPE 1
<4>[VID]: VIDEO_FREEZE 2145477792  0
<4>[VID]: VIDEO_PLAY 2145477792  5 2
<4>[VID]: VIDEO_SLOWMOTION 0    1
<4>[VID]: VIDEO_FAST_FORWARD 0    1
<4>[VID]: VIDEO_CONTINUE 0  1
<4>[AUD]: AUDIO_CONTINUE 0 1 aph=0xce311f80
<4>[AUD]: Mute : 0
<4>[VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
<4>[VID]: VIDEO_GET_SIZE aspect: 1 0
<4>[VID]: VIDEO_STOP 1  1
<4>[AUD]: AUDIO_STOP -2
<4>[AUD]: AUDIO_CONTINUE -2 0 aph=0x0
<4>[AUD]: AUDIO_CONTINUE aph=0 0 0
<4>[AUD]: AUDIO_SELECT_SOURCE 0
<4>[AUD]: AUDIO_SET_BYPASS_MODE 0
<4>[AUD]: AC3 downmix 0  state : 0
<4>[AUD]: AUDIO_PAUSE 0
<4>[AUD]: AUDIO_PLAY 0 decoder start : 0
<4>[VID]: VIDEO_SELECT_SOURCE 0  0
<4>[VID]: VIDEO_SET_STREAMTYPE 1
<4>[VID]: VIDEO_FREEZE 2145477792  0
<4>[VID]: VIDEO_PLAY 2145477792  5 2
<4>[VID]: VIDEO_SLOWMOTION 0    1
<4>[VID]: VIDEO_FAST_FORWARD 0    1
<4>[VID]: VIDEO_CONTINUE 0  1
<4>[AUD]: AUDIO_CONTINUE 0 1 aph=0xce325e00
<4>[AUD]: Mute : 0
<4>[VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
<4>[VID]: VIDEO_GET_SIZE aspect: 1 0
<4>[VID]: VIDEO_STOP 1  1
<4>[AUD]: AUDIO_STOP -2
<4>[AUD]: AUDIO_CONTINUE -2 0 aph=0x0
<4>[AUD]: AUDIO_CONTINUE aph=0 0 0
<4>[AUD]: AUDIO_SELECT_SOURCE 0
<4>[AUD]: AUDIO_SET_BYPASS_MODE 0
<4>[AUD]: AC3 downmix 0  state : 0
<4>[AUD]: AUDIO_PAUSE 0
<4>[AUD]: AUDIO_PLAY 0 decoder start : 0
<4>[VID]: VIDEO_SELECT_SOURCE 0  0
<4>[VID]: VIDEO_SET_STREAMTYPE 1
<4>[VID]: VIDEO_FREEZE 2145477792  0
<4>[VID]: VIDEO_PLAY 2145477792  5 2
<4>[VID]: VIDEO_SLOWMOTION 0    1
<4>[VID]: VIDEO_FAST_FORWARD 0    1
<4>[VID]: VIDEO_CONTINUE 0  1
<4>[AUD]: AUDIO_CONTINUE 0 1 aph=0xce311f80
<4>[AUD]: Mute : 0
<4>[VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
<4>[VID]: VIDEO_GET_SIZE aspect: 1 0

 



Re: vu+duo2 loop steeds vast op de nieuwe image #86 littlesat

  • PLi® Core member
  • 57,118 posts

+698
Excellent

Posted 22 November 2018 - 17:25

XC plugin waar heb je die vandaan.... daar zit de bug in!

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: vu+duo2 loop steeds vast op de nieuwe image #87 snowman.nl

  • Senior Member
  • 189 posts

+2
Neutral

Posted 22 November 2018 - 17:35

XC plugin van een een of andere site die hier niet genoemd mag worden

 

zal de boel schoon maken en met een schone lei beginnen



Re: vu+duo2 loop steeds vast op de nieuwe image #88 mimisiku

  • Senior Member
  • 5,516 posts

+115
Excellent

Posted 22 November 2018 - 17:59

En allemaal problemen die naar OpenPli geporteerd worden omdat de gebruiker zonodig van zijn/haar ontvanger per sé een multimedia speler wil maken (lees eist). Wanneer accepteren die personen nu eens dat het gewoon een STB is die gemaakt is om TV beeld weer te geven. Hetzij via de tuner, hetzij via een opgenomen bestand..
Wegwezen met die Kodi/XBMC/IPTV en weet niet wat meer.... Koop dan lekker een Shuttle-PC o.i.d.
Met één been in het graf..... Helaas

Re: vu+duo2 loop steeds vast op de nieuwe image #89 snowman.nl

  • Senior Member
  • 189 posts

+2
Neutral

Posted 23 November 2018 - 09:50

oké duidelijk verhaal

 

maar is er Geen Kodi/XBMC/IPTV player dan die geschikt is om in open pli te gebruiken ?



Re: vu+duo2 loop steeds vast op de nieuwe image #90 littlesat

  • PLi® Core member
  • 57,118 posts

+698
Excellent

Posted 23 November 2018 - 10:57

Looks like the movie list is empty... likely the credentials are not correct... Contact your illegal IPTV provider... This is NOT OPENPLI related.


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: vu+duo2 loop steeds vast op de nieuwe image #91 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 24 November 2018 - 11:59

maar is er Geen Kodi/XBMC/IPTV player dan die geschikt is om in open pli te gebruiken ?

Kennelijk niet, die wordt per model door de leverancier wel of niet aangeboden.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: vu+duo2 loop steeds vast op de nieuwe image #92 snowman.nl

  • Senior Member
  • 189 posts

+2
Neutral

Posted 31 December 2018 - 09:40

hoi Jongnes

 

 

ik kreeg weer een vast loper in eens valt de verbinding weg alles vast  werkt alllen weer als harde reboot box

 

] finished: ('/sbin/ip', '/sbin/ip', '-o', 'addr', 'show', 'dev', 'wlan0')
[Console] command: route -n | grep wlan0
[eConsoleAppContainer] Starting /bin/sh
[Console] finished: ('/bin/ping', '/bin/ping', '-c', '1', 'www.openpli.org')
[Console] finished: ('/bin/ping', '/bin/ping', '-c', '1', 'www.google.nl')
[Console] finished: ('/bin/ping', '/bin/ping', '-c', '1', 'www.google.com')
[Avahi] timeout elapsed
[Avahi] Resolving service 'vuuno4kse' of type '_e2stream._tcp'
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free

[Avahi] avahi_timeout_update

[Console] finished: route -n | grep eth0
0.0.0.0
192.168
[Avahi] timeout elapsed
[Avahi] Resolving service 'vuduo2' of type '_e2stream._tcp'
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free

[Avahi] avahi_timeout_update

[Console] finished: route -n | grep wlan0
nameservers: [[195, 121, 1, 34], [195, 121, 1, 66]]
read configured interface: {'lo': {'dhcp': False}, 'wlan0': {'dhcp': True}, 'eth0': {'dhcp': False}}
self.ifaces after loading: {'wlan0': {'preup': False, 'predown': False, 'ip': [0, 0, 0, 0], 'up': False, 'mac': '78:44:76:b0:05:98', 'dhcp': True, 'netmask': [0, 0, 0, 0], 'gateway': [0, 0, 0, 0]}, 'eth0': {'preup': False, 'predown': False, 'ip': [192, 168, 2, 30], 'up': True, 'mac': '00:1d:ec:0a:b7:30', 'dhcp': False, 'netmask': [255, 255, 255, 0], 'gateway': [192, 168, 2, 254]}}
SerienRecorder plugin not found
EPG Refresh Plugin not found
[OpenWebif] failed to listen on Port 80
[Avahi] timeout elapsed
[Avahi] Resolving service 'vuduo2-2' of type '_e2stream._tcp'
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free

[Avahi] avahi_timeout_update

[Avahi] watch activated: 0x1
[Avahi] timeout elapsed
[Avahi] avahi_timeout_update

[Avahi] timeout elapsed
[Avahi] avahi_timeout_update

[Avahi] timeout elapsed
[Avahi] avahi_timeout_update

[Avahi] timeout elapsed
[Avahi] avahi_timeout_update

[Avahi] timeout elapsed
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free

[Avahi] avahi_timeout_update

[Avahi] watch activated: 0x1
[Avahi] avahi_timeout_update

[Avahi] timeout elapsed
[Avahi] ADD Service 'vuuno4kse' of type '_e2stream._tcp' at vuuno4kse.local:8001
ADD Peer vuuno4kse=vuuno4kse.local:8001
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free

[Avahi] avahi_timeout_update

[Avahi] watch activated: 0x1
[Avahi] avahi_timeout_update

[Avahi] timeout elapsed
[Avahi] ADD Service 'vuduo2' of type '_e2stream._tcp' at vuduo2.local:8001
ADD Peer vuduo2=vuduo2.local:8001
[Avahi] avahi_timeout_new
[Avahi] avahi_timeout_free

[Avahi] avahi_timeout_update

[Console] command: ('hdparm', 'hdparm', '-y', '/dev/sda')
[eConsoleAppContainer] Starting hdparm
[Console] finished: ('hdparm', 'hdparm', '-y', '/dev/sda')
 



Re: vu+duo2 loop steeds vast op de nieuwe image #93 WanWizard

  • PLi® Core member
  • 70,381 posts

+1,807
Excellent

Posted 31 December 2018 - 13:58

Die log zegt in ieder geval niks...


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: vu+duo2 loop steeds vast op de nieuwe image #94 snowman.nl

  • Senior Member
  • 189 posts

+2
Neutral

Posted 30 January 2019 - 16:53

Hoi Jongens daar ben ik weer

 

ik zie nou deze melding staan wat kan dat zijn

 

 

vicePlay] timeshift
[eDVBServicePlay] timeshift
[eDVBServicePMTHandler] PATready
[eDVBServicePMTHandler] no PAT entry found.. start delay
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=0
[eDVBServicePlay] DVB service failed to tune - error 3
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift

[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift
[eDVBServicePMTHandler] PATready
[eDVBServicePMTHandler] no PAT entry found.. start delay
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=0
[eDVBServicePlay] DVB service failed to tune - error 3
[eDVBServicePMTHandler] PATready
[eDVBServicePMTHandler] no PAT entry found.. start delay
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=0
[eDVBServicePlay] DVB service failed to tune - error 3
[eDVBServicePMTHandler] PATready
[eDVBServicePMTHandler] no PAT entry found.. start delay
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=0
[eDVBServicePlay] DVB service failed to tune - error 3
[eDVBServicePMTHandler] PATready
[eDVBServicePMTHandler] no PAT entry found.. start delay
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=0
[eDVBServicePlay] DVB service failed to tune - error 3
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift
[eDVBServicePMTHandler] PATready
[eDVBServicePMTHandler] no PAT entry found.. start delay
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=0
[eDVBServicePlay] DVB service failed to tune - error 3

 

ineens was beeld weg

 

deze ook

 

nou ineens was beeld weer terug

 

 

[eDVBSectionReader] DMX_SET_FILTER pid=0
[eDVBServicePlay] DVB service failed to tune - error 3
[eDVBServicePlay] timeshift
[eDVBServicePlay] timeshift
[eDVBServicePMTHandler] PATready
[eDVBServicePMTHandler] use pmtpid 0a82 for service_id 5280
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=2690
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=0
[eDVBServicePlay] eventNewProgramInfo timeshift_enabled=0 timeshift_active=0
[eDVBServicePlay] have 1 video stream(s) (0230), and 1 audio stream(s) (0082), and the pcr pid is 0230, and the text pid is 003c
[eTSMPEGDecoder] decoder state: play, vpid=0230, apid=0082
[eDVBCIInterfaces] gotPMT
[eDVBCAService] don't build/send the same CA PMT twice
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=2690
[eDVBServicePlay] timeshift
 

 

 

 

 

 


Edited by snowman.nl, 30 January 2019 - 16:56.


Re: vu+duo2 loop steeds vast op de nieuwe image #95 WanWizard

  • PLi® Core member
  • 70,381 posts

+1,807
Excellent

Posted 30 January 2019 - 17:37

"Failed to tune" = Slecht of geen signaal.

 

En dat kan allerlei oorzaken hebben, van een duif op de schotel tot schotel gestolen. ;)


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: vu+duo2 loop steeds vast op de nieuwe image #96 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 30 January 2019 - 18:06

Als je uitrichting al niet optimaal is, dan kan zelfs de spreekwoordelijke vogelpoep van die Duif al de druppel zijn.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.




7 user(s) are reading this topic

0 members, 7 guests, 0 anonymous users