Jump to content


Photo

gigablue Trio support


  • Please log in to reply
19 replies to this topic

#1 thmls

  • Senior Member
  • 51 posts

+3
Neutral

Posted 22 December 2019 - 09:46

If is possible support gigablue Trio?

Re: gigablue Trio support #2 WanWizard

  • PLi® Core member
  • 56,501 posts

+1,174
Excellent

Posted 22 December 2019 - 12:36

If Gigablue adds support for it to the BSP and asks us to make an image for it...


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2+fallback), Octagon SF8008 (S2+T2), Zgemma H9.2H (T2+fallback)

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

Because to health reasons, I will not be active very often anymore.


Re: gigablue Trio support #3 Frenske

  • Forum Moderator
    PLi® Core member
  • 25,175 posts

+286
Excellent

Posted 22 December 2019 - 14:47

The second part has been done for months, the first part hasn’t. The developer that creates / maintains their BSP had no time to do so. At least AFAIK. So be patient. 
 

Attached File  506428FE-B098-437E-9CB1-85D4EE6AEB9E.jpeg   63.26KB   13 downloads

 

Just checked. Still no change unfortunately. At least for those endusers that wait for an OpenPLi image. 


Mijn schotel is een T90 met 10 LNB's. Daarnaast voor de fun nog een draaibaar systeem met een Triax TD 78.

Dreamboxen heb ik niet meer echt actief. Verder heb ik ook nog een een VU+ duo2 met 500Gb harddisk + een VU+ Uno, Zero, Solo 4K, Ultimo 4K, Zero 4K, Uno 4Kse. + ook nog een Xtrend ET7x00. Daarnaast heb ik ook nog diverse andere modellen w.o. een Formuler F4, ET8500, ET7500, Mut@nt 2400HD, Xsarius Fusion HD se en verder nog wel het e.e.a. waarmee op verzoek vanalles wordt getest. Iemand moet het tenslotte doen. ;) :)
Los van de eerder genoemde modellen heb ik nog wel een rits aan testsamples als Mut@nt 2400HD, HD60, GB UE4K, GB Trio4K, Maxitec Multibox combo en Twin, Octagon sf8008, sf8008 mini en last but nog least enkele modellen van het Grieks Duitse Edision.

Voor centrale opslag van media gebruik ik een Qnap 219P 
met tweemaal 2 Tb harddisks + een Synology DS414 met 12 Tb Totale opslag.

-------------------------------------------------------------------------------------------
Many answers to your question can be found in our wiki: Just one click away from this "solutioncentre".

Als ik alles al wist hoefde ik ook niets te vragen. If I had all the knowledge I had no questions at all.


Re: gigablue Trio support #4 thmls

  • Senior Member
  • 51 posts

+3
Neutral

Posted 26 December 2019 - 19:02

would like to ask openvision image based on openpli?

I say this because I followed the guides on the openvision GitHub page and created an openvision image


https://postimg.cc/Q9yT7wty

https://postimg.cc/kRJpVV2c

if openvision is based on openpli then there are sources to build openpli image

Re: gigablue Trio support #5 WanWizard

  • PLi® Core member
  • 56,501 posts

+1,174
Excellent

Posted 26 December 2019 - 19:08

Other images build their own BSP's based on info found on the web, for OpenPLi the manufacturer builds and maintains the BSP.

 

The main difference being guaranteed manufacturer support, for self-builds you're on your own. We don't release images without that support.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2+fallback), Octagon SF8008 (S2+T2), Zgemma H9.2H (T2+fallback)

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

Because to health reasons, I will not be active very often anymore.


Re: gigablue Trio support #6 Frenske

  • Forum Moderator
    PLi® Core member
  • 25,175 posts

+286
Excellent

Posted 26 December 2019 - 19:13

if openvision is based on openpli then there are sources to build openpli image

As we felt and still feel that a BSP layer should be created and maintained by the manufacturer which still hasn’t been done, at least not for the Trio, we will not support the Trio. As any model can be added in the BSP in a simple way, at least by someone with proper knowledge, it seems that the GigaBlue developer doesn’t feel like adding the Trio into the BSP. The request to add the Trio has been done for months and the result is still zilch. :(


Mijn schotel is een T90 met 10 LNB's. Daarnaast voor de fun nog een draaibaar systeem met een Triax TD 78.

Dreamboxen heb ik niet meer echt actief. Verder heb ik ook nog een een VU+ duo2 met 500Gb harddisk + een VU+ Uno, Zero, Solo 4K, Ultimo 4K, Zero 4K, Uno 4Kse. + ook nog een Xtrend ET7x00. Daarnaast heb ik ook nog diverse andere modellen w.o. een Formuler F4, ET8500, ET7500, Mut@nt 2400HD, Xsarius Fusion HD se en verder nog wel het e.e.a. waarmee op verzoek vanalles wordt getest. Iemand moet het tenslotte doen. ;) :)
Los van de eerder genoemde modellen heb ik nog wel een rits aan testsamples als Mut@nt 2400HD, HD60, GB UE4K, GB Trio4K, Maxitec Multibox combo en Twin, Octagon sf8008, sf8008 mini en last but nog least enkele modellen van het Grieks Duitse Edision.

Voor centrale opslag van media gebruik ik een Qnap 219P 
met tweemaal 2 Tb harddisks + een Synology DS414 met 12 Tb Totale opslag.

-------------------------------------------------------------------------------------------
Many answers to your question can be found in our wiki: Just one click away from this "solutioncentre".

Als ik alles al wist hoefde ik ook niets te vragen. If I had all the knowledge I had no questions at all.


Re: gigablue Trio support #7 thmls

  • Senior Member
  • 51 posts

+3
Neutral

Posted 28 December 2019 - 15:20

I'll ask at gigablue

Re: gigablue Trio support #8 thmls

  • Senior Member
  • 51 posts

+3
Neutral

Posted 2 December 2020 - 19:43

Hello
how do I set the front panel display to always display the clock? I have installed the permanentenvfdclock 2.0 plugin in openpli 7.3 it worked properly, in openpli 8.0 it does not work it show only one number. Is it difficult to set up the front panel display like openatv or hdfeaks?

Re: gigablue Trio support #9 WanWizard

  • PLi® Core member
  • 56,501 posts

+1,174
Excellent

Posted 2 December 2020 - 19:51

You need a display skin for that, or adapt the installed display skin.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2+fallback), Octagon SF8008 (S2+T2), Zgemma H9.2H (T2+fallback)

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

Because to health reasons, I will not be active very often anymore.


Re: gigablue Trio support #10 thmls

  • Senior Member
  • 51 posts

+3
Neutral

Posted 2 December 2020 - 20:04

I do not understand GB trio4k has only a small screen that shows the clock or the channel number
Hdfeaks have this option


Screenshot-20201202-205103.jpg

Re: gigablue Trio support #11 WanWizard

  • PLi® Core member
  • 56,501 posts

+1,174
Excellent

Posted 2 December 2020 - 21:08

We don't.

 

We work with display skins, similar to the skins you install for the GUI, which you can find on the box as skin_display.xml (containing https://github.com/O..._gbtrio4k.xml).

 

As you can see, the "<!-- main-->" section is used when the box is on, the "<!-- standby -->" when the box is in standby. So if you want a clock while the box is on, you can copy the standby section to the main section.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2+fallback), Octagon SF8008 (S2+T2), Zgemma H9.2H (T2+fallback)

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

Because to health reasons, I will not be active very often anymore.


Re: gigablue Trio support #12 thmls

  • Senior Member
  • 51 posts

+3
Neutral

Posted 2 December 2020 - 23:44

it work thanks

Re: gigablue Trio support #13 thmls

  • Senior Member
  • 51 posts

+3
Neutral

Posted 28 December 2020 - 22:32

Hello

I use openpli 8.0 and usb fat32 and ntfs do not appear

Re: gigablue Trio support #14 WanWizard

  • PLi® Core member
  • 56,501 posts

+1,174
Excellent

Posted 28 December 2020 - 22:40

Does not appear where? Did you flash the latest image? Mount related issues where fixed recently, but need to to flash again.

 

p.s. this is a release candidate, a test image. It is NOT openpli 8.0.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2+fallback), Octagon SF8008 (S2+T2), Zgemma H9.2H (T2+fallback)

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

Because to health reasons, I will not be active very often anymore.


Re: gigablue Trio support #15 thmls

  • Senior Member
  • 51 posts

+3
Neutral

Posted 29 December 2020 - 22:10

I had openpli 8.0 installed from the first day it was released and I did a software update every week and usb did not appear. finally install last image with (flash image) and usb appear. Another problem I have is with the tunein radio plugin if I click on station I have a green screen I do not know if the problem is with the plugin or something in the software

Re: gigablue Trio support #16 thmls

  • Senior Member
  • 51 posts

+3
Neutral

Posted 29 December 2020 - 22:16

OpenPLi Enigma2 crash log

crashdate=Πεμ Ιαν 1 03:17:34 1970
compiledate=Dec 27 2020
skin=PLi-FullNightHD/skin.xml
sourcedate=2020-12-26
branch=rc
rev=d424f53
component=Enigma2

stbmodel=gbtrio4k
stbmodel=dm8000
kernelcmdline=console=ttyAMA0,115200 root=/dev/mmcblk0p16 rootsubdir=linuxrootfs1 rootfstype=ext4 kernel=/dev/mmcblk0p12 blkdevparts=mmcblk0:1M(boot),1M(bootargs),1M(bootoptions),3M(baseparam),4M(pqparam),4M(logo),4M(deviceinfo),4M(softwareinfo),4M(loaderdb),32M(loader),8M(trustedcore),16M(linuxkernel1),16M(linuxkernel2),16M(linuxkernel3),16M(linuxkernel4),-(userdata) coherent_pool=2M mem=1G mmz=ddr,0,0,72M vmalloc=500M MACHINEBUILD=gbtrio4k OEM=gigablue MODEL=gbtrio4k
nimsockets=NIM Socket 0:
imageissue=openpli 8.0-rc %h


REMOVE Peer gbtrio4k
REMOVE Peer gbtrio4k
Traceback (most recent call last):
File "/usr/lib/enigma2/python/Components/ActionMap.py", line 57, in action
File "/usr/lib/enigma2/python/Plugins/Extensions/TuneinRadio/main.py", line 1177, in ok_clicked
self.newscreen(self.action_params)
File "/usr/lib/enigma2/python/Plugins/Extensions/TuneinRadio/main.py", line 1263, in newscreen
self.loadscreen()
File "/usr/lib/enigma2/python/Plugins/Extensions/TuneinRadio/main.py", line 1307, in loadscreen
self.session.openWithCallback(self.updateindex,TSRadioplayer, serviceRef=None,serviceUrl=str(param),serviceName=name,serviceIcon='', playlist = self.playlist, playindex =self.index,process_item=self.process_item)
File "/usr/lib/enigma2/python/mytest.py", line 290, in openWithCallback
dlg = self.open(screen, *arguments, **kwargs)
File "/usr/lib/enigma2/python/mytest.py", line 300, in open
dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
File "/usr/lib/enigma2/python/mytest.py", line 243, in instantiateDialog
return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
File "/usr/lib/enigma2/python/mytest.py", line 267, in doInstantiateDialog
dlg.applySkin()
File "/usr/lib/enigma2/python/Screens/Screen.py", line 234, in applySkin
TypeError: setTitle() takes exactly 1 argument (2 given)
[ePyObject] (CallObject(<bound method ActionMap.action of <Components.ActionMap.ActionMap instance at 0xb0897328>>,('OkCancelActions', 'ok')) failed)


dmesg

<6>usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
<6>hub 4-0:1.0: USB hub found
<6>hub 4-0:1.0: 1 port detected
<6>usbcore: registered new interface driver uas
<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/sz) protocol handler initialized
<6>IR RC6 protocol handler initialized
<6>IR JVC protocol handler initialized
<6>IR Sony protocol handler initialized
<6>IR SANYO protocol handler initialized
<6>IR Sharp protocol handler initialized
<6>IR MCE Keyboard/mouse protocol handler initialized
<6>IR XMP protocol handler initialized
<6>sp805-wdt f8a2c000.watchdog: registration successful
<4>registered new interface driver himciV2.0_4.4.35_20170401
<6>usb 1-1: new high-speed USB device number 2 using ehci-platform
<6>hub 1-1:1.0: USB hub found
<6>hub 1-1:1.0: 4 ports detected
<6>mmc0: MAN_BKOPS_EN bit is not set
<6>mmc0: new DDR MMC card at address 0001
<6>mmcblk0: mmc0:0001 8GTF4R 7.28 GiB
<6>mmcblk0boot0: mmc0:0001 8GTF4R partition 1 4.00 MiB
<6>mmcblk0boot1: mmc0:0001 8GTF4R partition 2 4.00 MiB
<6>mmcblk0rpmb: mmc0:0001 8GTF4R partition 3 512 KiB
<6> mmcblk0: p1(boot) p2(bootargs) p3(bootoptions) p4(baseparam) p5(pqparam) p6(logo) p7(deviceinfo) p8(softwareinfo) p9(loaderdb) p10(loader) p11(trustedcore) p12(linuxkernel1) p13(linuxkernel2) p14(linuxkernel3) p15(linuxkernel4) p16(userdata)
<6>usb 1-2: new high-speed USB device number 3 using ehci-platform
<5>f9820000.himciv200.SD: eMMC/MMC/SD Device NOT detected!
<6>usb-storage 1-2:1.0: USB Mass Storage device detected
<6>scsi host0: usb-storage 1-2:1.0
<6>usb 1-1.3: new high-speed USB device number 4 using ehci-platform
<6>usb-storage 1-1.3:1.0: USB Mass Storage device detected
<6>scsi host1: usb-storage 1-1.3:1.0
<5>f9c40000.himciv200.SD: eMMC/MMC/SD Device NOT detected!
<6>usbcore: registered new interface driver usbhid
<6>usbhid: USB HID core driver
<6>ashmem: initialized
<6>usbcore: registered new interface driver snd-usb-audio
<6>oprofile: using timer interrupt.
<6>Initializing XFRM netlink socket
<6>NET: Registered protocol family 10
<6>NET: Registered protocol family 17
<5>Key type dns_resolver registered
<5>Registering SWP/SWPB emulation handler
<6>Bluetooth: Starting self testing
<6>Bluetooth: ECDH test passed in 25649 usecs
<6>Bluetooth: SMP test passed in 68 usecs
<6>Bluetooth: Finished self testing
<6>ALSA device list:
<6> No soundcards found.
<6>Freeing unused kernel memory: 568K (c0ad2000 - c0b60000)
<4>This architecture does not have kernel memory protection.
<6>EXT4-fs (mmcblk0p16): mounted filesystem with ordered data mode. Opts: (null)
<4>Load hi_media.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:28:35])
<4>Load hi_mmz.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:28:35])
<4>virtual device initialization.
<4>Load hi_common.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [Jun 26 2018, 14:24:58])
<4>Load hi_pq.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:31:28])
<4>Load hi_cipher.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:30:22])
<4>Load hi_hdmi.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [Mar 30 2019, 15:16:17])
<4>hisi hdmi CEC Driver, © 2018 Define Technologies
<4>Load hi_vou.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [Jun 28 2018, 16:48:45])
<4>Load hi_gpio.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:30:40])
<4>Load hi_gpioi2c.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:31:14])
<4>Load hi_i2c.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:31:15])
<5>scsi 0:0:0:0: Direct-Access SanDisk Ultra 1.00 PQ: 0 ANSI: 6
<4>Load hi_tde.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:31:41])
<4>print parent bus[usb], bus_id[1-2:1.0]
<4>allocate index 0 for non sdcard, try again
<4>print parent bus[usb], bus_id[1-2:1.0]
<4>allocate index 1 for usb20, try again
<4>print parent bus[usb], bus_id[1-2:1.0]
<4>allocate index 2 for usb30, try again
<5>sd 0:0:0:0: Attached scsi generic sg0 type 0
<5>sd 0:0:0:0: [sdd] 60751872 512-byte logical blocks: (31.1 GB/29.0 GiB)
<5>sd 0:0:0:0: [sdd] Write Protect is off
<7>sd 0:0:0:0: [sdd] Mode Sense: 43 00 00 00
<5>sd 0:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
<6> sdd: sdd1
<5>sd 0:0:0:0: [sdd] Attached SCSI removable disk
<4>Load hi_otp.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:31:23])
<4>Load hi_demux.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [Jul 26 2018, 18:25:22])
<4>Load hi_adec.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:29:59])
<5>scsi 1:0:0:0: Direct-Access Generic STORAGE DEVICE 1404 PQ: 0 ANSI: 6
<4>print parent bus[usb], bus_id[1-1.3:1.0]
<4>already got sdcard index 0
<4>print parent bus[usb], bus_id[1-1.3:1.0]
<5>sd 1:0:0:0: Attached scsi generic sg1 type 0
<4>Load hi_vfmw.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:31:53])
<4>Load hi_vpss.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:32:27])
<4>Load hi_vdec.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:31:44])
<4>Load hi_adsp.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:30:00])
<6>hisi-sndcard hisi-sndcard: aiao-hifi <-> hisi-i2s mapping ok
<4>Load hi_aiao.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [Jul 14 2018, 10:00:23])
<5>sd 1:0:0:0: [sda] 249737216 512-byte logical blocks: (128 GB/119 GiB)
<5>sd 1:0:0:0: [sda] Write Protect is off
<7>sd 1:0:0:0: [sda] Mode Sense: 21 00 00 00
<5>sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
<6> sda: sda1
<5>sd 1:0:0:0: [sda] Attached SCSI removable disk
<4>Load hi_pvr.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:31:38])
<4>Load hi_tuner.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [May 16 2018, 18:30:30])
<5>random: nonblocking pool is initialized
<4>Load hi_keyled.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180124] Build Time: [Jul 14 2018, 10:01:39])
<6>virtual DVB adapter driver, version 1.4, © 2010-12 Honza Petrous, SmartImp.cz
<5>vtunerc: registered /dev/misc/vtuner0
<5>vtunerc: registered /dev/misc/vtuner1
<5>vtunerc: registered /dev/misc/vtuner2
<4>hi_dvb: unknown parameter 'hi_vendor' ignored
<4>hi_dvb: unknown parameter 'hi_device' ignored
<6>phi
<6>HI PCIE bridge driver, Copyright © 2005-2018 Micronas
<6>DVB: registering new adapter (nHi)
<4>si2166 attach success
<6>DVB: registering adapter 0 frontend 0 (Si2166D)...
<6>[hi_dvb_attach_tsport:740 dmx 0,port 32]0 5 1 0 184
<4>u32DmxNum : 5 u32FilterNum : 64 u32ChannelNum : 96 u32RamPortNum : 3
<4>[00:00:03:279 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6
<4>si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
<4>[00:00:03:301 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6
<4>si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
<4>si2166 attach fail!
<3>phi: No HI Demod Found!
<4>atbm781x2x3x_attach I2C(1) , ADDR: 128(0x80)
<4>atbm781x2x3x attach success!
<6>DVB: registering adapter 0 frontend 0 (ATBM7821 DVB-T2/C)...
<6>[hi_dvb_attach_tsport:740 dmx 1,port 33]0 5 1 0 184
<4>u32DmxNum : 5 u32FilterNum : 64 u32ChannelNum : 96 u32RamPortNum : 3
<4>[00:00:03:759 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6
<4>si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
<4>[00:00:03:781 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6
<4>si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
<4>si2166 attach fail!
<3>phi: No HI Demod Found!
<4>atbm781x2x3x_attach I2C(2) , ADDR: 128(0x80)
<4>[00:00:04:013 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6
<4>atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00)
<4>[00:00:04:036 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6
<4>atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00)
<4>[1;32mdvb video add event 17 - 7 0
<4>[matbm781x2x3x attach fail!
<3>phi: No HI Demod Found!
<4>atbm781x2x3x_attach I2C(1) , ADDR: 152(0x98)
<4>[00:00:04:272 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6
<4>atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00)
<4>[00:00:04:294 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6
<4>atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00)
<4>atbm781x2x3x attach fail!
<3>phi: No HI Demod Found!
<6>[hi_dvb_attach_tsport:740 dmx 2,port 34]0 5 1 0 184
<4>u32DmxNum : 5 u32FilterNum : 64 u32ChannelNum : 96 u32RamPortNum : 3
<4>[00:00:04:538 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6
<4>[1;32mdvb video add event 17 - 7 0
<4>[msi2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
<4>[00:00:04:564 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6
<4>si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0)
<4>si2166 attach fail!
<3>phi: No HI Demod Found!
<4>atbm781x2x3x_attach I2C(2) , ADDR: 128(0x80)
<4>[00:00:04:796 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6
<4>atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00)
<4>[00:00:04:818 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6
<4>atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00)
<4>atbm781x2x3x atta

Re: gigablue Trio support #17 WanWizard

  • PLi® Core member
  • 56,501 posts

+1,174
Excellent

Posted 29 December 2020 - 22:33

Some fixes are in the OS, and require a flash. The mount issue was one of them. RC versions are test versions, and ideally should be flashed, not updated.

 

The green screen is a bug in the screen definition in plugin, so the plugin author needs to fix that.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2+fallback), Octagon SF8008 (S2+T2), Zgemma H9.2H (T2+fallback)

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

Because to health reasons, I will not be active very often anymore.


Re: gigablue Trio support #18 thmls

  • Senior Member
  • 51 posts

+3
Neutral

Posted 30 December 2020 - 23:18

thank you very much. sorry for the questions. it's all about learning

Re: gigablue Trio support #19 WanWizard

  • PLi® Core member
  • 56,501 posts

+1,174
Excellent

Posted 31 December 2020 - 00:42

No problem, there are no stupid questions, just stupid answers...


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2+fallback), Octagon SF8008 (S2+T2), Zgemma H9.2H (T2+fallback)

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

Because to health reasons, I will not be active very often anymore.


Re: gigablue Trio support #20 Dorfkind

  • Senior Member
  • 103 posts

+2
Neutral

Posted 31 December 2020 - 09:06

@thmls

 

And pls look here what Frenske wrote:

 

@Dorfkind and all other members. Please post a crashlog and not the full content of the crashlog in the future.This makes it much easier to read the board. I just edit your posting and put all the text in one specific crashlog.

 

Thank for your understanding and cooperation in the future..

Thank you!


Mutant HD51 OpenPli 7.3 Wohnzimmer

Edision Osmini OpenPli 8.0 Schlafzimmer

Bier lecker 20.0 Kühlschrank :D





2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users