SATELLITE SUPPORT - View topic - Faceti cunostiinta cu ... Gigablue Trio 4K (recovery)

Page 1 of 1

[ 9 posts ]

Faceti cunostiinta cu ... Gigablue Trio 4K (recovery)

Author	Message
mihaip Joined: 23 Jun 2009, 10:32 Posts: 157947 Location: On the barrel ...	Faceti cunostiinta cu ... Gigablue Trio 4K (recovery) Gigablue Trio 4K Din greseala am sters topicul original ! asa ca-l incropesc din ce am putut recupera de ici si de colo !!! CPU: ARM Cortex A53, Quad Core 64Bit, (4x 1.6GHz) 15.000 Dmips Chipset : Hisilicon Hi3798MV200 Huawei Memory : 8 GB eMMC Flash / 1 GB Ram DDR3 SD RAM Display : 4 Digit / 7 Segment Audio : S/PDIF Audio Output Optical (Digital) Video : H.265 HEVC 2 x USB (1x USB 3.0 & 1x USB 2.0) 1 x HDMI 2.1 1 x LAN (10/100 MBit/s) 1 x W-LAN 1200Mbps integrated 1 x SD Card Reader 1 x S/C Card Reader Slot 1 x DVB-S2X Tuner, MIS (Multistream) 1 x DVB-C/T2 Tuner H.265 HEVC 1 x RS232 service interface 1 x BT RCU _________________ Ex computer guru !
15 Dec 2024, 15:45

mihaip Joined: 23 Jun 2009, 10:32 Posts: 157947 Location: On the barrel ...	Re: Faceti cunostiinta cu - Gigablue Trio 4K Recovery Trio 4K - cu HiTool Datele problemei : - receptor Gigablue Trio 4K defect + unul functional ! - cel defect pus sub tensiune trecea direct in ... UPDT - @sosozah a adus un cablu serial-jack ... functional ! dar nu si telecomanda ! - am presupus inclusiv ca avem microswitch de "recovery" blocat - seriala ne-a aratat ca Trio porneste in Boot ... lanseaza Kernelul si gata !!! Am tras concluzia ca un "baiat istet" a facut o instalare de imagine ... haiduceasca ! una care a scris un Kernel exotic ... as zice chiar strain ! Am pornit receptorul functional pentru a afla cum s-au alocat partitiile sistem ! si m-am folosit de butoanele din panoul frontal ca sa nevighez prin Enigma2 ! aici mi-a dat o mana de ajutor Linux/Enigma2 ( cat /proc/partitions ) 179 1 1024 mmcblk0p1 - fastboot 179 2 1024 mmcblk0p2 - bootargs 179 3 1024 mmcblk0p3 - bootoptions 179 4 3072 mmcblk0p4 - baseparams 179 5 4096 mmcblk0p5 - pqparam 179 6 4096 mmcblk0p6 - logo 179 7 4096 mmcblk0p7 - deviceinfo 259 0 4096 mmcblk0p8 259 1 4096 mmcblk0p9 259 2 32768 mmcblk0p10 - loader 259 3 8192 mmcblk0p11 - kernel 259 4 16384 mmcblk0p12 259 5 16384 mmcblk0p13 259 6 16384 mmcblk0p14 259 7 16384 mmcblk0p15 259 8 7501824 mmcblk0p16 179 24 512 mmcblk0rpmb 179 16 4096 mmcblk0boot1 179 8 4096 mmcblk0boot0 Orbecaind si facand analogii cu Dinobot am facut alocarea de mai sus !!! Am creat un folder Gigablue Trio 4K pe care l-am populat cu ce am gasit in imaginea OpenATV Recovery !!! si Kernel din imaginea Normala ! Am construit fisierul de configuratie al partitiilor (XML) Code: <Partition_Info ProgrammerFile=""> <Part Sel="1" PartitionName="fastboot" FlashType="emmc" FileSystem="none" Start="0" Length="1M" SelectFile="C:\Users\misup\Desktop\Giga Trio 4k\fastboot.bin"/> <Part Sel="1" PartitionName="bootargs" FlashType="emmc" FileSystem="none" Start="1M" Length="1M" SelectFile="C:\Users\misup\Desktop\Giga Trio 4k\bootargs.bin"/> <Part Sel="1" PartitionName="baseparam" FlashType="emmc" FileSystem="none" Start="2M" Length="4M" SelectFile=""/> <Part Sel="1" PartitionName="pqparam" FlashType="emmc" FileSystem="none" Start="6M" Length="4M" SelectFile=""/> <Part Sel="1" PartitionName="logo" FlashType="emmc" FileSystem="none" Start="10M" Length="4M" SelectFile=""/> <Part Sel="1" PartitionName="deviceinfo" FlashType="emmc" FileSystem="none" Start="14M" Length="4M" SelectFile=""/> <Part Sel="1" PartitionName="loader" FlashType="emmc" FileSystem="none" Start="18M" Length="32M" SelectFile="C:\Users\misup\Desktop\Giga Trio 4k\apploader.bin"/> <Part Sel="1" PartitionName="trustedcore" FlashType="emmc" FileSystem="none" Start="50M" Length="8M" SelectFile=""/> <Part Sel="1" PartitionName="kernel" FlashType="emmc" FileSystem="none" Start="58M" Length="32M" SelectFile="C:\Users\misup\Desktop\Giga Trio 4k\kernel.bin"/> <Part Sel="1" PartitionName="rootfs" FlashType="emmc" FileSystem="ext3/4" Start="90M" Length="512M" SelectFile=""/> </Partition_Info> - am trecut pe receptorul defect cu retea si serial conectate !!! - am dedus IP-ul pe care si l-a luat , search pe router - am pornit TFTPD , serverul de FTP si i-am dat parametrii - am pornit HiTool si i-am dat parametrii Si acum , voiniceste ! am zis ... Burn ! zis si facut ! la final am salvat fisierul de configurare (XML) pentru eternitate !!! siii ... Reboot !!! Gigablue are un sistem de recovery ciudat ! foloseste Kernelul existent in EMMC si nu unul livrat in imaginea de recovery de pe stickul USB ! asa ca daca Kernelul a fost rescris prosteste ... in EMMC el pe ala i-l lanseaza si ramine cracanat ! Ce joaca buna am tras ! am facut si cateva presupuneri norocoase dar m-am bazat masiv pe experienta recovery Amiko Viper 4K V20.30.40 ! _________________ Ex computer guru !
15 Dec 2024, 16:04

mihaip Joined: 23 Jun 2009, 10:32 Posts: 157947 Location: On the barrel ...	Re: Faceti cunostiinta cu - Gigablue Trio 4K Operatia a reusit ! dar din ce spune @sosozah ... pacientul nu se simte prea bine ! asa ca astept ziua lui de teste sa vedem ce si cum ! Ceea ce mi-a fost suspect a fost ca Trio 4K a pornit direct in imaginea de firma ! asta putea sa insemne ca nimeni n-a scris nimic eronat pe el ! ci pur si simplu partitia Kernel nu s-a scris corect initial ! Asta nu este un semn bun ! poate sa insemne o pana hardware EMMC instabil ... si asta ar fi un caz de final trist ! _________________ Ex computer guru !
15 Dec 2024, 16:11

sosozah Joined: 14 Oct 2020, 10:34 Posts: 4	Re: Faceti cunostiinta cu - Gigablue Trio 4K Dupa vreo opt ore de jucat cu HiTool si PuTTY, incep sa cred ca @MihaiP are dreptate: Code: Warning - bad CRC or eMMC, using default environment Mai insist.
15 Dec 2024, 18:24

mihaip Joined: 23 Jun 2009, 10:32 Posts: 157947 Location: On the barrel ...	Re: Faceti cunostiinta cu - Gigablue Trio 4K Zau ca n-am cobit ! Din pacate mesajul tau miroase de la o posta a pana de EMMC ! nu este ceva foarte frecvent ... dar uite ca se intampla ! _________________ Ex computer guru !
16 Dec 2024, 11:12

sosozah Joined: 14 Oct 2020, 10:34 Posts: 4	Re: Faceti cunostiinta cu ... Gigablue Trio 4K (recovery) Baiul pare sa fie totusi altul. Eroarea legatata de EMMC de mai sus am primit-o cand am sters tabela de partitii si am pus doar fastboot in memorie. Din pacate tot se blocheaza la "starting kernel", fie in modul de pornire normal, fie in cel de intrat in recovery. Singurul mod in care am reusit sa-l pornesc a fost sa intrerup procedura de boot (Ctrl+C pentru a ramane in fastboot), sa incarc prin tftp un kernel.bin si sa il lansez. Fastboot are o serie de comenzi de baza, lista lor se poate obtine cu "help" sau "?". Cu comanda "printenv" sunt afisati parametri din bootargs si pot fi modificati cu "setenv", apoi salvati in memorie cu "saveenv". La copierea prin tftp mi-a copiat fisierul la adresa 0x8000 si am folosit comanda "bootm 0x8000" pentru a lansa kernelul. Logul e plin de erori, printre care si ceva legat de unul dintre procesoare, dar aparatul functioneaza stabil pana cand ii dau restart. La comanda dmesg primesc raspunsul acesta: Code: login as: root [email protected]'s password: root@gbtrio4k:~# dmesg Bluetooth: SCO socket layer initialized clocksource: Switched to clocksource hisp804 FS-Cache: Loaded NET: Registered protocol family 2 TCP established hash table entries: 4096 (order: 2, 16384 bytes) TCP bind hash table entries: 4096 (order: 3, 32768 bytes) TCP: Hash tables configured (established 4096 bind 4096) UDP hash table entries: 256 (order: 1, 8192 bytes) UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. PCI: CLS 0 bytes, default 64 NetWinder Floating Point Emulator V0.97 (double precision) hw perfevents: enabled with armv7_cortex_a17 PMU driver, 7 counters available futex hash table entries: 1024 (order: 4, 65536 bytes) squashfs: version 4.0 (2009/01/31) Phillip Lougher NFS: Registering the id_resolver key type Key type id_resolver registered Key type id_legacy registered nfs4filelayout_init: NFSv4 File Layout Driver Registering... Installing knfsd (copyright (C) 1996 [email protected]). FS-Cache: Netfs 'cifs' registered for caching jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. fuse init (API version 7.23) yaffs: yaffs built Installing. bounce: pool size: 64 pages Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) io scheduler noop registered io scheduler deadline registered (default) io scheduler cfq registered hiahci-phy: registered new sata phy driver brd: module loaded loop: module loaded hifmc100: registerd new interface driver hifmc100. hifmc100: Found flash memory controller hifmc100. hifmc100: no found spi-nor device. hifmc100: no found nand device. hifmc100: no found spi-nand device. hieth: /soc/hieth@f9c30000/hieth_phy@0 has invalid PHY address libphy: himii: probed mdio_bus himii: /soc/hieth@f9c30000/hieth_phy@0 PHY address 255 is too large hieth: no dev probed! libphy: higmac_mii_bus: probed attached PHY 3 to driver Generic PHY, PHY_ID=0x11a ETH: rgmii, phy_addr=3 ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-pci: EHCI PCI platform driver ehci-platform: EHCI generic platform driver ehci-platform f9890000.ehci: EHCI Host Controller ehci-platform f9890000.ehci: new USB bus registered, assigned bus number 1 ehci-platform f9890000.ehci: irq 34, io mem 0xf9890000 ehci-platform f9890000.ehci: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver ohci-pci: OHCI PCI platform driver ohci-platform: OHCI generic platform driver ohci-platform f9880000.ohci: Generic Platform OHCI controller ohci-platform f9880000.ohci: new USB bus registered, assigned bus number 2 ohci-platform f9880000.ohci: irq 35, io mem 0xf9880000 hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected xhci-hcd f98a0000.xhci: xHCI Host Controller xhci-hcd f98a0000.xhci: new USB bus registered, assigned bus number 3 xhci-hcd f98a0000.xhci: hcc params 0x0220f06c hci version 0x100 quirks 0x0001001 0 xhci-hcd f98a0000.xhci: irq 37, io mem 0xf98a0000 hub 3-0:1.0: USB hub found hub 3-0:1.0: 1 port detected xhci-hcd f98a0000.xhci: xHCI Host Controller xhci-hcd f98a0000.xhci: new USB bus registered, assigned bus number 4 usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. hub 4-0:1.0: USB hub found hub 4-0:1.0: 1 port detected usbcore: registered new interface driver uas usbcore: registered new interface driver usb-storage mousedev: PS/2 mouse device common for all mice i2c /dev entries driver IR NEC protocol handler initialized IR RC5(x/sz) protocol handler initialized IR RC6 protocol handler initialized IR JVC protocol handler initialized IR Sony protocol handler initialized IR SANYO protocol handler initialized IR Sharp protocol handler initialized IR MCE Keyboard/mouse protocol handler initialized IR XMP protocol handler initialized sp805-wdt f8a2c000.watchdog: registration successful registered new interface driver himciV2.0_4.4.35_20170401 usb 1-1: new high-speed USB device number 2 using ehci-platform hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected mmc0: MAN_BKOPS_EN bit is not set mmc0: new DDR MMC card at address 0001 mmcblk0: mmc0:0001 8GTF4R 7.28 GiB mmcblk0boot0: mmc0:0001 8GTF4R partition 1 4.00 MiB mmcblk0boot1: mmc0:0001 8GTF4R partition 2 4.00 MiB mmcblk0rpmb: mmc0:0001 8GTF4R partition 3 512 KiB mmcblk0: p1(boot) p2(bootargs) p3(bootoptions) p4(baseparam) p5(pqparam) p6(log o) p7(deviceinfo) p8(softwareinfo) p9(loaderdb) p10(loader) p11(trustedcore) p12 (linuxkernel1) p13(linuxkernel2) p14(linuxkernel3) p15(linuxkernel4) p16(userdat a) f9820000.himciv200.SD: eMMC/MMC/SD Device NOT detected! f9c40000.himciv200.SD: eMMC/MMC/SD Device NOT detected! usbcore: registered new interface driver usbhid usbhid: USB HID core driver ashmem: initialized usbcore: registered new interface driver snd-usb-audio oprofile: using timer interrupt. Initializing XFRM netlink socket NET: Registered protocol family 10 NET: Registered protocol family 17 Key type dns_resolver registered Registering SWP/SWPB emulation handler Bluetooth: Starting self testing Bluetooth: ECDH test passed in 25502 usecs Bluetooth: SMP test passed in 70 usecs Bluetooth: Finished self testing ALSA device list: No soundcards found. Freeing unused kernel memory: 568K (c0ae8000 - c0b76000) This architecture does not have kernel memory protection. EXT4-fs (mmcblk0p16): recovery complete EXT4-fs (mmcblk0p16): mounted filesystem with ordered data mode. Opts: (null) Load hi_media.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:28:35]) Load hi_mmz.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:28:35]) virtual device initialization. Load hi_common.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [Jun 26 2018, 14:24:58]) Load hi_pq.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:28]) Load hi_cipher.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:30:22]) Load hi_hdmi.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [Mar 30 2019, 15:16:17]) hisi hdmi CEC Driver, (c) 2018 Define Technologies Load hi_vou.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [Jun 28 2018, 16:48:45]) Load hi_gpio.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:30:40]) Load hi_gpioi2c.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:14]) Load hi_i2c.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:15]) Load hi_tde.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:41]) Load hi_otp.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:23]) Load hi_demux.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [Jul 26 2018, 18:25:22]) Load hi_adec.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:29:59]) Load hi_vfmw.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:53]) Load hi_vpss.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:32:27]) Load hi_vdec.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:44]) Load hi_adsp.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:30:00]) hisi-sndcard hisi-sndcard: aiao-hifi <-> hisi-i2s mapping ok Load hi_aiao.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [Jul 14 2018, 10:00:23]) Load hi_pvr.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:38]) Load hi_tuner.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [Nov 7 2022, 12:17:07]) Load hi_keyled.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [Jul 14 2018, 10:01:39]) virtual DVB adapter driver, version 1.4, (c) 2010-12 Honza Petrous, SmartImp.cz vtunerc: registered /dev/misc/vtuner0 vtunerc: registered /dev/misc/vtuner1 vtunerc: registered /dev/misc/vtuner2 hi_dvb: unknown parameter 'hi_vendor' ignored hi_dvb: unknown parameter 'hi_device' ignored phi HI PCIE bridge driver, Copyright (C) 2005-2018 Micronas DVB: registering new adapter (nHi) si2166 attach success DVB: registering adapter 0 frontend 0 (Si2166D)... [hi_dvb_attach_tsport:740 dmx 0,port 32]0 5 1 0 184 u32DmxNum : 5 u32FilterNum : 64 u32ChannelNum : 96 u32RamPortNum : 3 [07:14:43:338 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6 si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0) [07:14:43:360 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6 si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0) si2166 attach fail! phi: No HI Demod Found! atbm781x2x3x_attach I2C(1) , ADDR: 128(0x80) atbm781x2x3x attach success! DVB: registering adapter 0 frontend 0 (ATBM7821 DVB-T2/C)... [hi_dvb_attach_tsport:740 dmx 1,port 33]0 5 1 0 184 u32DmxNum : 5 u32FilterNum : 64 u32ChannelNum : 96 u32RamPortNum : 3 [07:14:43:818 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6 si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0) [07:14:43:840 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6 si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0) si2166 attach fail! phi: No HI Demod Found! atbm781x2x3x_attach I2C(2) , ADDR: 128(0x80) [07:14:44:072 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6 atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00) [07:14:44:094 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6 atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00) dvb video add event 17 - 7 0 atbm781x2x3x attach fail! phi: No HI Demod Found! atbm781x2x3x_attach I2C(1) , ADDR: 152(0x98) [07:14:44:326 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6 atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00) [07:14:44:348 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6 atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00) atbm781x2x3x attach fail! phi: No HI Demod Found! [hi_dvb_attach_tsport:740 dmx 2,port 34]0 5 1 0 184 u32DmxNum : 5 u32FilterNum : 64 u32ChannelNum : 96 u32RamPortNum : 3 [07:14:44:592 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6 si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0) dvb video add event 17 - 7 0 [07:14:44:614 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6 si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0) si2166 attach fail! phi: No HI Demod Found! atbm781x2x3x_attach I2C(2) , ADDR: 128(0x80) [07:14:44:850 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6 atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00) [07:14:44:872 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6 atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00) atbm781x2x3x attach fail! phi: No HI Demod Found! atbm781x2x3x_attach I2C(1) , ADDR: 152(0x98) [07:14:45:104 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6 atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00) [07:14:45:126 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6 atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00) atbm781x2x3x attach fail! phi: No HI Demod Found! [hi_dvb_attach_tsport:740 dmx 3,port 35]0 5 1 0 184 u32DmxNum : 5 u32FilterNum : 64 u32ChannelNum : 96 u32RamPortNum : 3 [07:14:45:370 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6 si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0) dvb video add event 17 - 7 0 [07:14:45:392 ERROR-HI_I2C]:I2C_DRV_Write[194]:i2c_transfer failed:-6 si2166 I2C(1) write error, ADDR: 202(0xca), DATA: 192(0xc0) si2166 attach fail! phi: No HI Demod Found! atbm781x2x3x_attach I2C(2) , ADDR: 128(0x80) [07:14:45:628 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6 atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00) [07:14:45:650 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6 atbm781x2x3x I2C(2) read error, ADDR: 0(0x0000), DATA: 0(0x00) atbm781x2x3x attach fail! phi: No HI Demod Found! atbm781x2x3x_attach I2C(1) , ADDR: 152(0x98) [07:14:45:882 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6 atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00) [07:14:45:904 ERROR-HI_I2C]:I2C_DRV_Read[260]:i2c_transfer failed:-6 atbm781x2x3x I2C(1) read error, ADDR: 0(0x0000), DATA: 0(0x00) atbm781x2x3x attach fail! phi: No HI Demod Found! No this tuner device u32DmxNum : 5 u32FilterNum : 64 u32ChannelNum : 96 u32RamPortNum : 3 Load hi_fb.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [Nov 17 2020, 17:37:22]) Mali: Mali device driver loaded misc hi_dbe: hi_dbe ready Load hi_jpegdec.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:17]) Load hi_jpegenc.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:17]) Load hi_png.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:26]) Load hi_advca.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:30:01]) Load hi_venc.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:48]) dvb video add event 17 - 7 0 Load hi_aenc.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:30:04]) Load hi_sci.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [Mar 27 2019, 19:29:44]) Load hi_vi.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [May 16 2018, 18:31:55]) get mmc 0 host 8GTF4R Load hi_pmoc.ko success. (SDK_VERSION: [HiSTBLinuxV100R005C00SPC052_20180 124] Build Time: [Nov 11 2022, 14:31:50]) Registered IR keymap rc-hi3798 input: dreambox advanced remote control as /devices/virtual/rc/rc0/input0 rc0: dreambox advanced remote control as /devices/virtual/rc/rc0 [07:14:46:264 ERROR-HI_SYS]:HI_DRV_SYS_SetIrqAffinity[679]:cpu num 2 is offline, irq num is 20,name is ir_std! HI_DRV_SYS_SetIrqAffinity failed. hisi KEYS Driver, (c) 2017 Define Technologies input: Hisi Front Panel Button Controls as /devices/platform/hisi_keys/input/inp ut1 hisi encoder Driver, (c) 2017 Define Technologies dvb video add event 17 - 7 0 tntfs: module license 'Commercial. For support email [email protected].' t aints kernel. Disabling lock debugging due to kernel taint Tuxera NTFS driver 3017.7.4.6 [Flags: R/W MODULE]. Built against headers 4.4.35_hi3798mv2x #1 SMP Tue Dec 12 14:16:24 CST 2017 arm Running on kernel 4.4.35 #1 SMP Sat Feb 11 22:56:28 UTC 2023 armv7l WARNING: Running kernel does not match configured kernel headers the driver was built with! The driver needs to be rebuilt with the correct kernel headers! SGI XFS with ACLs, security attributes, realtime, no debug enabled EXT4-fs (mmcblk0p16): re-mounted. Opts: data=ordered FAT-fs (mmcblk0p3): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [07:14:48:667 ERROR-HI_PM]:c51_GetWakeUpMode[1318]: wakeup mode err! proc_vmpeg_0_dst_apply_write 1 [iframe_confirm:190] iframe confirm video[0] ready to play dvb video add event 17 - 7 0 [iframe_finish:208] iframe finish IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready hi_gmac_v200 f9840000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [iframe_confirm:190] iframe confirm video[0] ready to play [iframe_finish:208] iframe finish dvb video add event 17 - 7 0 [07:15:02:309 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 0 Failed OPS_si2166_init @RDA5815M_Initialize api->spi_download 0 Build Option: Si2183_B60_COMPATIBLE Si2166-D60 Part running 'FW_6_1b4' @si2166_i2c_gate_ctrl @si2166_i2c_gate_ctrl @OPS diseqc tone = 0(22K-OFF) @si2166_diseqc_set_voltage OFF @OPS diseqc tone = 0(22K-OFF) @si2166_diseqc_set_voltage OFF proc_vmpeg_0_dst_apply_write 00000001 UDF-fs: warning (device mmcblk0p1): udf_fill_super: No partition found (2) UDF-fs: warning (device mmcblk0p1): udf_fill_super: No partition found (2) yaffs: dev is 187695105 name is "mmcblk0p1" rw yaffs: passed flags "" yaffs: yaffs: Attempting MTD mount of 179.1,"mmcblk0p1" yaffs: yaffs: MTD device 1 either not valid or unavailable yaffs: dev is 187695105 name is "mmcblk0p1" rw yaffs: passed flags "" yaffs: yaffs: Attempting MTD mount of 179.1,"mmcblk0p1" yaffs: yaffs: MTD device 1 either not valid or unavailable tntfs info (device mmcblk0p1, pid 3282): ntfs_fill_super(): fail_safe is enabled . stStdTiming[h:1280, v:720] stStdTiming[h:1280, v:1024] stStdTiming[h:1280, v:720] stStdTiming[h:1280, v:1024] stStdTiming[h:1280, v:720] stStdTiming[h:1280, v:1024] proc_vmpeg_0_dst_apply_write 1 proc_vmpeg_0_dst_apply_write 1 bestfit panscan panscan panscan panscan proc_video_videomode_50hz_write [1080p50] proc_video_videomode_60hz_write [1080p] proc_video_videomode_24hz_write [1080p24] panscan press key [0x50af12ed] detective O sa incerc sa ii fac un factory reset, dar nu stiu daca nu o sa apeleze la prostiile pe care i le-am tot scris in memorie in joaca cu HiTool. Macar am depistat procedura cu care sa porneasca, deocamdata. LE: dupa factory reset a pornit cu imaginea teamblue 7.3, dar nu am meniul de multiboot activ. Il las asa deocamdata, ca mi-a mancat prea multe zile.
28 Dec 2024, 17:48

mihaip Joined: 23 Jun 2009, 10:32 Posts: 157947 Location: On the barrel ...	Re: Faceti cunostiinta cu ... Gigablue Trio 4K (recovery) Imaginea de firma nu are optiunea de recovery ! pui imaginea de recovery de la OpenATV dupa care vei avea un meniu de activare multiboot ! _________________ Ex computer guru !
28 Dec 2024, 19:09

sosozah Joined: 14 Oct 2020, 10:34 Posts: 4	Re: Faceti cunostiinta cu ... Gigablue Trio 4K (recovery) Cum se poate scrie imaginea recovery daca nu imi intra in meniul de update/recovery la start?
28 Dec 2024, 19:19

mihaip Joined: 23 Jun 2009, 10:32 Posts: 157947 Location: On the barrel ...	Re: Faceti cunostiinta cu ... Gigablue Trio 4K (recovery) Trebuie sa refaci imaginea mea de recovery cea pentru HiTool !!! Nu intra in recovery pentru ca incearca sa foloseasca kernelul deja scris in flash ... si cu ala este o problema ! uneori se citeste alteori nu ! La mine dupa ce am scris imaginea de mai dus ... a pornit normal ! Dupa un start normal ! trebuie facut un stick recovery OpenATV si incercata procedura de recovery ! daca aceea merge , se rescrie inclusiv Kernelul si ... cine stie ! Pentru mine este limpede ca avem in fata un "bolnav" ! ar putea sa functioneze acceptabil dupa un start normal cu un minim de canale si pluginuri instalate ! si de acolo in colo ... doar vizionare ! _________________ Ex computer guru !
28 Dec 2024, 20:31

Display posts from previous: Sort by

Page 1 of 1

[ 9 posts ]

Faceti cunostiinta cu ... Gigablue Trio 4K (recovery)

Who is online