Jump to content


Photo

Zgemma H9 Twin SE enigma.info


  • Please log in to reply
17 replies to this topic

#1 Dimitrij

  • PLi® Core member
  • 10,434 posts

+359
Excellent

Posted 5 January 2025 - 13:24

WanWizard
stbmodel=H9TwinSE
stbmodel=h9combose
kernelcmdline=root=/dev/mmcblk0p23 rootsubdir=linuxrootfs4 rootfstype=ext4 kernel=/dev/mmcblk0p22 console=ttyAMA0,115200 blkdevparts=mmcblk0:1M(fastboot),1M(bootargs),18M(recovery),2M(bootoptions),2M(deviceinfo),4M(baseparam),4M(pqparam),4M(logo),40M(fastplay),20M(kernel),20M(trustedcore),4M(misc),1024M(system),150M(vendor),306M(e2tv),256M(cache),50M(private),8M(securestore),16M(linuxkernel1),16M(linuxkernel2),16M(linuxkernel3),16M(linuxkernel4),-(userdata) hbcomp=/dev/block/mmcblk0p13 mem=937M mmz=ddr,0,0,60M vmalloc=500M
nimsockets=NIM Socket 0:
imageissue=openpli 9.1-release %h


REMOVE Peer h9combose
REMOVE Peer h9combose
REMOVE Peer h9combose
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Screens/Ci.py", line 351, in ciStateChanged
IndexError: list index out of range
[ePyObject] (CallObject(<bound method CiMessageHandler.ciStateChanged of <Screens.Ci.CiMessageHandler object at 0xb29ab580>>,(1,)) failed)

Problem in enigma2.info

 

stbmodel=H9TwinSE
stbmodel=h9combose


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: Zgemma H9 Twin SE enigma.info #2 WanWizard

  • PLi® Core member
  • 71,093 posts

+1,842
Excellent

Posted 5 January 2025 - 14:19

More info please.

 

What box is this, a Twin SE ( 2 x DVB-S2 ) or a Combo SE ( 1 x DVB-S2 + 1 x DVB-C/T2 ) ?

 

What exactly, which key, is wrong in /usr/lib/enigma.info, and what is the correct value?

 

Runtime model detection happens here: https://github.com/O...ma-info.bb#L503

 

The box model is determined here: https://github.com/O...ma-info.bb#L376


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: Zgemma H9 Twin SE enigma.info #3 Dimitrij

  • PLi® Core member
  • 10,434 posts

+359
Excellent

Posted 5 January 2025 - 17:37

BoxInfo.setItem("CommonInterface", model in ("h9combo", "h9combose", "h10", "pulse4kmini") and 1 or eDVBCIInterfaces.getInstance().getNumOfSlots())

 


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: Zgemma H9 Twin SE enigma.info #4 WanWizard

  • PLi® Core member
  • 71,093 posts

+1,842
Excellent

Posted 6 January 2025 - 00:04

BoxInfo.setItem("CommonInterface", model in ("h9combo", "h9combose", "h10", "pulse4kmini") and 1 or eDVBCIInterfaces.getInstance().getNumOfSlots())

That isn't an answer to my question.


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: Zgemma H9 Twin SE enigma.info #5 Dimitrij

  • PLi® Core member
  • 10,434 posts

+359
Excellent

Posted 6 January 2025 - 06:25

 

openpli-9.1-release-h9combose-20250103_emmc 

zgemma h9 twinse

 
 

-model = BoxInfo.getItem("machine")
+model = BoxInfo.getItem("model")

or

elif [ "$MACHINE" = "h9combose" ]; then
	if [ "$model" = "h9twinse" ]; then
		updateinfo "displaymodel" "H9 TWIN SE"
+               updateinfo "machine" "h9twinse"
      

or


Edited by Dimitrij, 6 January 2025 - 06:32.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: Zgemma H9 Twin SE enigma.info #6 littlesat

  • PLi® Core member
  • 57,675 posts

+714
Excellent

Posted 6 January 2025 - 07:27

Does this box has one or two CI… hardware info indicates one hardcoded via a hack because it looks the box drivers itself seems not correctly identify the number for CI interfaces.

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


Re: Zgemma H9 Twin SE enigma.info #7 ghuss

  • Senior Member
  • 71 posts

0
Neutral

Posted 6 January 2025 - 09:17

Thanks

 

It has :  2 x DVB Common Interface slots


Vu+ Duo 2 


Re: Zgemma H9 Twin SE enigma.info #8 Dimitrij

  • PLi® Core member
  • 10,434 posts

+359
Excellent

Posted 6 January 2025 - 11:05

Thanks

 

It has :  2 x DVB Common Interface slots

+

name H9 TWIN SE


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: Zgemma H9 Twin SE enigma.info #9 WanWizard

  • PLi® Core member
  • 71,093 posts

+1,842
Excellent

Posted 6 January 2025 - 13:26

This can never have worked?

 

That bit still looks like "old" ( = pre BoxInfo ) code, and the model name of the box in /proc/stb is "h9combose", so before introduction of BoxInfo, it would also have limited the number of slots to 1 ?

 

The use of "machine" here is very wrong, as that is OE build MACHINE, that says nothing about the actual box.

 

So  I think two things are needed here:

-model = BoxInfo.getItem("machine")
+model = BoxInfo.getItem("model")

and

+ updateinfo "model" "h9twinse"

or, alternatively, use

-model = BoxInfo.getItem("machine")
+model = BoxInfo.getItem("machinebuild")

as that should correctly reflect the actual machine ( can you double check your enigma.info? ).

 

If we go for the first solution, more boxes need their "model" fixing, as the old code had a massive if structure to deduct the "model" from all sorts of /proc data.


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: Zgemma H9 Twin SE enigma.info #10 littlesat

  • PLi® Core member
  • 57,675 posts

+714
Excellent

Posted 6 January 2025 - 13:53

Then the box does also not have the proper procs to detect the CI…as the setting to 1 was already for ever a work-a-round….

Edited by littlesat, 6 January 2025 - 13:54.

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


Re: Zgemma H9 Twin SE enigma.info #11 WanWizard

  • PLi® Core member
  • 71,093 posts

+1,842
Excellent

Posted 6 January 2025 - 14:20

That is exactly why I remarked it could have never worked.


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: Zgemma H9 Twin SE enigma.info #12 Dimitrij

  • PLi® Core member
  • 10,434 posts

+359
Excellent

Posted 7 January 2025 - 09:23

WanWizard

This problem H9 TWIN SE/H9 TWIN

Maybe really use BoxInfo.getItem("model")

this

HardwareInfo.py

self.device_model = self.machine_name = BoxInfo.getItem("machine")

and

SystemInfo.py

and

RcModel.py


Edited by Dimitrij, 7 January 2025 - 09:34.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: Zgemma H9 Twin SE enigma.info #13 littlesat

  • PLi® Core member
  • 57,675 posts

+714
Excellent

Posted 7 January 2025 - 10:22

My brain explode when I read back this thread.... I understand specific Zgemma boxes have 2 CIs instead of one... they do not have the proper procs to detect them so we hardcoded the number of procs. We have a list of Zgemma boxes that worked around it.... Is this work-a-round not correct? Is the box model not correct detected? I'm going in circles and circles here so I cannot define any solution....


Edited by littlesat, 7 January 2025 - 10:23.

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


Re: Zgemma H9 Twin SE enigma.info #14 salim1965

  • New Member
  • 4 posts

0
Neutral

Posted 8 January 2025 - 16:15

https://cdn.resimupl...50107232933.jpg

 

https://cdn.resimupl...50107232413.jpg



Re: Zgemma H9 Twin SE enigma.info #15 salim1965

  • New Member
  • 4 posts

0
Neutral

Posted 8 January 2025 - 16:24

zgemma h9 twinsSE software was given instead of combeSE software. Twinse is visible in 9.0, combese is visible in 9.1, twinse is visible in 8.3.



Re: Zgemma H9 Twin SE enigma.info #16 salim1965

  • New Member
  • 4 posts

0
Neutral

Posted 10 January 2025 - 23:59

OpenPLi Enigma2 crash log
 
crashdate=Cts Oca 11 01:53:24 2025
compiledate=Jan  5 2025
skin=PLi-FullNightHD/skin.xml
sourcedate=2025-01-04
branch=release-9.1
rev=de1ec82
component=Enigma2
 
stbmodel=H9TwinSE
stbmodel=h9combose
kernelcmdline=root=/dev/mmcblk0p23 rootsubdir=linuxrootfs3 rootfstype=ext4 kernel=/dev/mmcblk0p21 console=ttyAMA0,115200 blkdevparts=mmcblk0:1M(fastboot),1M(bootargs),18M(recovery),2M(bootoptions),2M(deviceinfo),4M(baseparam),4M(pqparam),4M(logo),40M(fastplay),20M(kernel),20M(trustedcore),4M(misc),1024M(system),150M(vendor),306M(e2tv),256M(cache),50M(private),8M(securestore),16M(linuxkernel1),16M(linuxkernel2),16M(linuxkernel3),16M(linuxkernel4),-(userdata) hbcomp=/dev/block/mmcblk0p13 mem=937M mmz=ddr,0,0,60M vmalloc=500M
nimsockets=NIM Socket 0:
imageissue=openpli 9.1-release %h
 
 
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
[eListboxPythonConfigContent] second value of tuple is not a tuple.
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Screens/Ci.py", line 351, in ciStateChanged
IndexError: list index out of range
[ePyObject] (CallObject(<bound method CiMessageHandler.ciStateChanged of <Screens.Ci.CiMessageHandler object at 0xb29520a0>>,(1,)) failed)
 
 
dmesg
 
<6>Booting Linux on physical CPU 0x0
<5>Linux version 4.4.35 (oe-user@oe-host) (gcc version 10.3.0 (GCC) ) #1 SMP Tue Dec 17 12:41:01 UTC 2024
<6>CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
<6>CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
<5>initmrd: found no initmrd.
<6>Machine model: Hisilicon
<6>cma: Reserved 60 MiB at 0x35800000
<6>cma: Reserved 4 MiB at 0x3a400000
<6>Memory policy: Data cache writealloc
<7>-------------Fixed IO Mapping----------
<7>Virt,            Phys,             Size
<7>0xF9000000,    0xF8000000,    0x02000000
<7>--------------------------------------
<7>On node 0 totalpages: 239872
<7>free_area_init_node: node 0, pgdat c0b59100, node_mem_map dfca1000
<7>  Normal zone: 1032 pages used for memmap
<7>  Normal zone: 0 pages reserved
<7>  Normal zone: 132096 pages, LIFO batch:31
<7>  HighMem zone: 107776 pages, LIFO batch:31
<6>PERCPU: Embedded 13 pages/cpu @dfc5d000 s22604 r8192 d22452 u53248
<7>pcpu-alloc: s22604 r8192 d22452 u53248 alloc=13*4096
<7>pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
<6>Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 238840
<5>Kernel command line: root=/dev/mmcblk0p23 rootsubdir=linuxrootfs3 rootfstype=ext4 kernel=/dev/mmcblk0p21 console=ttyAMA0,115200 blkdevparts=mmcblk0:1M(fastboot),1M(bootargs),18M(recovery),2M(bootoptions),2M(deviceinfo),4M(baseparam),4M(pqparam),4M(logo),40M(fastplay),20M(kernel),20M(trustedcore),4M(misc),1024M(system),150M(vendor),306M(e2tv),256M(cache),50M(private),8M(securestore),16M(linuxkernel1),16M(linuxkernel2),16M(linuxkernel3),16M(linuxkernel4),-(userdata) hbcomp=/dev/block/mmcblk0p13 mem=937M mmz=ddr,0,0,60M vmalloc=500M
<6>log_buf_len individual max cpu contribution: 4096 bytes
<6>log_buf_len total cpu_extra contributions: 12288 bytes
<6>log_buf_len min size: 16384 bytes
<6>log_buf_len: 32768 bytes
<6>early log buf free: 14180(86%)
<6>PID hash table entries: 2048 (order: 1, 8192 bytes)
<6>Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>Memory: 863256K/959488K available (7686K kernel code, 669K rwdata, 2148K rodata, 548K init, 521K bss, 30696K reserved, 65536K cma-reserved, 355316K highmem)
<5>Virtual kernel memory layout:
<5>    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
<5>    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
<5>    vmalloc : 0xe0800000 - 0xff800000   ( 496 MB)
<5>    lowmem  : 0xc0000000 - 0xe0400000   ( 516 MB)
<5>    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
<5>    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
<5>      .text : 0xc0008000 - 0xc0789bcc   (7687 kB)
<5>      .init : 0xc0a3b000 - 0xc0ac4000   ( 548 kB)
<5>      .data : 0xc0ac4000 - 0xc0b6b4ac   ( 670 kB)
<5>       .bss : 0xc0b6d000 - 0xc0bef7d0   ( 522 kB)
<6>SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
<6>Hierarchical RCU implementation.
<6> Build-time adjustment of leaf fanout to 32.
<6>NR_IRQS:352
<6>clocksource: hisp804: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
<6>sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
<6>Console: colour dummy device 80x30
<6>Calibrating delay loop... 3170.30 BogoMIPS (lpj=1585152)
<6>pid_max: default: 32768 minimum: 301
<6>Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
<6>Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
<6>CPU: Testing write buffer coherency: ok
<6>ftrace: allocating 26065 entries in 77 pages
<6>CPU0: update cpu_capacity 1024
<6>CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
<6>Setting up static identity map for 0x8280 - 0x82d8
<4>CPU: hi3798mv200
<7>CPU1: powerup
<6>CPU1: update cpu_capacity 1024
<6>CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
<7>CPU2: powerup
<6>CPU2: update cpu_capacity 1024
<6>CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
<7>CPU3: powerup
<6>CPU3: update cpu_capacity 1024
<6>CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
<6>Brought up 4 CPUs
<6>SMP: Total of 4 processors activated (12681.21 BogoMIPS).
<6>CPU: All CPU(s) started in SVC mode.
<6>CPU3: update max cpu_capacity 1024
<6>devtmpfs: initialized
<6>VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
<6>clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
<4>PCIe read alloc area phyaddr 08  size 00000000
<4>PCIe write alloc area phyaddr 08  size 00000000
<6>NET: Registered protocol family 16
<6>DMA: preallocated 256 KiB pool for atomic coherent allocations
<6>CPU1: update max cpu_capacity 1024
<6>hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
<6>hw-breakpoint: maximum watchpoint size is 8 bytes.
<6>Serial: AMBA PL011 UART driver
<6>f8b00000.uart: ttyAMA0 at MMIO 0xf8b00000 (irq = 25, base_baud = 0) is a PL011 rev2
<6>console [ttyAMA0] enabled
<6>f8b02000.uart: ttyAMA1 at MMIO 0xf8b02000 (irq = 26, base_baud = 0) is a PL011 rev2
<6>f8b03000.uart: ttyAMA2 at MMIO 0xf8b03000 (irq = 27, base_baud = 0) is a PL011 rev2
<6>pl061_gpio f8b20000.gpio0: PL061 GPIO chip @0xf8b20000 registered
<6>pl061_gpio f8b21000.gpio1: PL061 GPIO chip @0xf8b21000 registered
<6>pl061_gpio f8b22000.gpio2: PL061 GPIO chip @0xf8b22000 registered
<6>pl061_gpio f8b23000.gpio3: PL061 GPIO chip @0xf8b23000 registered
<6>pl061_gpio f8b24000.gpio4: PL061 GPIO chip @0xf8b24000 registered
<6>pl061_gpio f8004000.gpio5: PL061 GPIO chip @0xf8004000 registered
<6>pl061_gpio f8b26000.gpio6: PL061 GPIO chip @0xf8b26000 registered
<6>pl061_gpio f8b27000.gpio7: PL061 GPIO chip @0xf8b27000 registered
<6>pl061_gpio f8b28000.gpio8: PL061 GPIO chip @0xf8b28000 registered
<6>pl061_gpio f8b29000.gpio9: PL061 GPIO chip @0xf8b29000 registered
<4>hisilicon-pcie: probe of f0001000.pcie failed with error -1
<6>hisi_iommu_ptable_addr:phy 0x1e800000    size:0x400000
<6>hisi_iommu_err_rdaddr :phy 0x1f697600    size:0x200
<6>hisi_iommu_err_wraddr :phy 0x1f697800     size:0x200
<6>in hisi_iommu_domain_init start 
<6>in hisi_iommu_domain_init end 
<6>vgaarb: loaded
<5>SCSI subsystem initialized
<7>libata version 3.00 loaded.
<6>ssp-pl022 f8b1a000.spi: ARM PL022 driver, device ID: 0x00041022
<6>ssp-pl022 f8b1a000.spi: mapped registers from 0xf8b1a000 to f9b1a000
<6>spi_master spi0: will run message pump with realtime priority
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>Linux video capture interface: v2.00
<6>Advanced Linux Sound Architecture Driver Initialized.
<6>clocksource: Switched to clocksource hisp804
<5>FS-Cache: Loaded
<6>NET: Registered protocol family 2
<6>TCP established hash table entries: 4096 (order: 2, 16384 bytes)
<6>TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
<6>TCP: Hash tables configured (established 4096 bind 4096)
<6>UDP hash table entries: 256 (order: 1, 8192 bytes)
<6>UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
<6>NET: Registered protocol family 1
<6>RPC: Registered named UNIX socket transport module.
<6>RPC: Registered udp transport module.
<6>RPC: Registered tcp transport module.
<6>RPC: Registered tcp NFSv4.1 backchannel transport module.
<7>PCI: CLS 0 bytes, default 64
<6>NetWinder Floating Point Emulator V0.97 (double precision)
<6>hw perfevents: enabled with armv7_cortex_a17 PMU driver, 7 counters available
<6>futex hash table entries: 1024 (order: 4, 65536 bytes)
<5>VFS: Disk quotas dquot_6.6.0
<6>VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
<6>squashfs: version 4.0 (2009/01/31) Phillip Lougher
<5>NFS: Registering the id_resolver key type
<5>Key type id_resolver registered
<5>Key type id_legacy registered
<6>nfs4filelayout_init: NFSv4 File Layout Driver Registering...
<6>Installing knfsd (copyright © 1996 okir@monad.swb.de).
<5>FS-Cache: Netfs 'cifs' registered for caching
<6>jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
<6>fuse init (API version 7.23)
<7>yaffs: yaffs built Installing.
<6>bounce: pool size: 64 pages
<6>Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
<6>io scheduler noop registered
<6>io scheduler deadline registered (default)
<6>io scheduler cfq registered
<6>hiahci-phy: registered new sata phy driver
<6>brd: module loaded
<6>loop: module loaded
<6>ahci f9900000.hiahci: SSS flag set, parallel bus scan disabled
<6>ahci f9900000.hiahci: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode
<6>ahci f9900000.hiahci: flags: ncq sntf stag pm led clo only pmp fbs slum part ccc sxs boh 
<6>scsi host0: ahci
<6>ata1: SATA max UDMA/133 mmio [mem 0xf9900000-0xf9900fff] port 0x100 irq 41
<6>hifmc100: registerd new interface driver hifmc100.
<5>hifmc100: Found flash memory controller hifmc100.
<6>FEPHY:addr=2, la_am=0xe, ldo_am=0x3, r_tuning=0x13
<6>libphy: himii: probed
<6>hi_eth: attached port 0 PHY 2 to driver HiSilicon Festa v330
<6>/soc/ethernet@f9840000/ethernet_phy@0 has invalid PHY address=255
<6>PPP generic driver version 2.4.2
<6>PPP BSD Compression module registered
<6>PPP Deflate Compression module registered
<6>usbcore: registered new interface driver asix
<6>usbcore: registered new interface driver ax88179_178a
<6>usbcore: registered new interface driver cdc_ether
<6>usbcore: registered new interface driver dm9601
<6>usbcore: registered new interface driver net1080
<6>usbcore: registered new interface driver cdc_subset
<6>usbcore: registered new interface driver zaurus
<6>usbcore: registered new interface driver cdc_ncm
<6>ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<6>ehci-pci: EHCI PCI platform driver
<6>ehci-platform: EHCI generic platform driver
<6>ehci-platform f9890000.ehci: EHCI Host Controller
<6>ehci-platform f9890000.ehci: new USB bus registered, assigned bus number 1
<6>ehci-platform f9890000.ehci: irq 34, io mem 0xf9890000
<6>ehci-platform f9890000.ehci: USB 2.0 started, EHCI 1.00
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 2 ports detected
<6>ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
<6>ohci-pci: OHCI PCI platform driver
<6>ohci-platform: OHCI generic platform driver
<6>ohci-platform f9880000.ohci: Generic Platform OHCI controller
<6>ohci-platform f9880000.ohci: new USB bus registered, assigned bus number 2
<6>ohci-platform f9880000.ohci: irq 35, io mem 0xf9880000
<6>ata1: SATA link down (SStatus 0 SControl 300)
<6>hub 2-0:1.0: USB hub found
<6>hub 2-0:1.0: 2 ports detected
<6>xhci-hcd f98a0000.xhci: xHCI Host Controller
<6>xhci-hcd f98a0000.xhci: new USB bus registered, assigned bus number 3
<6>xhci-hcd f98a0000.xhci: hcc params 0x0220f06c hci version 0x100 quirks 0x00030010
<6>xhci-hcd f98a0000.xhci: irq 37, io mem 0xf98a0000
<6>hub 3-0:1.0: USB hub found
<6>hub 3-0:1.0: 1 port detected
<6>xhci-hcd f98a0000.xhci: xHCI Host Controller
<6>xhci-hcd f98a0000.xhci: new USB bus registered, assigned bus number 4
<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 usb-storage
<6>usbcore: registered new interface driver usbserial
<6>usbcore: registered new interface driver usbserial_generic
<6>usbserial: USB Serial support registered for generic
<6>usbcore: registered new interface driver usb_debug
<6>usbserial: USB Serial support registered for debug
<6>usbcore: registered new interface driver option
<6>usbserial: USB Serial support registered for GSM modem (1-port)
<6>mousedev: PS/2 mouse device common for all mice
<6>usbcore: registered new interface driver xpad
<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>usb-storage 1-1:1.0: USB Mass Storage device detected
<6>scsi host1: usb-storage 1-1:1.0
<6>mmc0: MAN_BKOPS_EN bit is not set
<4>scan edges:3 p2f:5 f2p:8
<4>mix set temp-phase 2
<4>scan elemnts: startp:129 endp:110
<5>Tuning SampleClock. mix set phase:[03/07] ele:[02/17] 
<6>mmc0: new HS400 MMC card at address 0001
<6>mmcblk0: mmc0:0001 AJTD4R 14.6 GiB 
<6>mmcblk0boot0: mmc0:0001 AJTD4R partition 1 4.00 MiB
<6>mmcblk0boot1: mmc0:0001 AJTD4R partition 2 4.00 MiB
<6>usb 1-2: new high-speed USB device number 3 using ehci-platform
<6>mmcblk0rpmb: mmc0:0001 AJTD4R partition 3 4.00 MiB
<6> mmcblk0: p1(fastboot) p2(bootargs) p3(recovery) p4(bootoptions) p5(deviceinfo) p6(baseparam) p7(pqparam) p8(logo) p9(fastplay) p10(kernel) p11(trustedcore) p12(misc) p13(system) p14(vendor) p15(e2tv) p16(cache) p17(private) p18(securestore) p19(linuxkernel1) p20(linuxkernel2) p21(linuxkernel3) p22(linuxkernel4) p23(userdata)
<5>f9820000.himciv200.SD: eMMC/MMC/SD Device NOT detected!
<6>hub 1-2:1.0: USB hub found
<6>hub 1-2:1.0: 4 ports detected
<6>usb 1-2.3: new high-speed USB device number 4 using ehci-platform
<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>Netfilter messages via NETLINK v0.30.
<6>nfnl_acct: registering with nfnetlink.
<6>ip_tables: © 2000-2006 Netfilter Core Team
<6>arp_tables: © 2002 David S. Miller
<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>ALSA device list:
<6>  No soundcards found.
<3>Warning: unable to open an initial console.
<6>Freeing unused kernel memory: 548K (c0a3b000 - c0ac4000)
<4>This architecture does not have kernel memory protection.
<6>EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mode. Opts: (null)
<30>udevd[948]: starting version 3.2.10
<5>random: udevd: uninitialized urandom read (16 bytes read, 87 bits of entropy available)
<5>random: udevd: uninitialized urandom read (16 bytes read, 87 bits of entropy available)
<5>random: udevd: uninitialized urandom read (16 bytes read, 87 bits of entropy available)
<5>random: udevd: uninitialized urandom read (16 bytes read, 87 bits of entropy available)
<30>udevd[949]: starting eudev-3.2.10
<5>random: udevd: uninitialized urandom read (16 bytes read, 90 bits of entropy available)
<5>scsi 1:0:0:0: Direct-Access     SanDisk  Ultra USB 3.0    1.00 PQ: 0 ANSI: 6
<5>sd 1:0:0:0: [sda] 30031872 512-byte logical blocks: (15.4 GB/14.3 GiB)
<5>sd 1:0:0:0: [sda] Write Protect is off
<7>sd 1:0:0:0: [sda] Mode Sense: 43 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>RTW: module init start
<4>RTW: rtl8192fu v5.8.6.4_37082.20200716_COEX20190910-0d02
<4>RTW: build time: Dec 17 2024 12:47:23
<4>RTW: rtl8192fu BT-Coex version = COEX20190910-0d02
<5>random: nonblocking pool is initialized
<4>RTW: HW EFUSE
<4>RTW: 0x000: 29 81 00 7C  09 16 01 00  A6 3F A5 70  10 A0 12 0B  
<4>RTW: 0x010: 24 24 24 24  23 23 26 26  27 27 27 02  EF EF FF FF  
<4>RTW: 0x020: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x030: FF FF FF FF  FF FF FF FF  FF FF 23 23  22 22 20 20  
<4>RTW: 0x040: 27 27 27 27  27 02 EF EF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x050: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x060: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x070: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x080: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x090: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x0A0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x0B0: FF FF FF FF  FF FF FF FF  20 12 20 00  00 00 FF FF  
<4>RTW: 0x0C0: FF 01 00 10  00 00 00 FF  00 00 01 FF  FF FF FF FF  
<4>RTW: 0x0D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x0E0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x0F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x100: DA 0B 92 F1  43 66 03 60  1D 9D BD 48  F9 09 03 52  
<4>RTW: 0x110: 65 61 6C 74  65 6B 09 03  38 30 32 2E  31 31 6E 00  
<4>RTW: 0x120: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x130: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x140: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x150: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x160: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x170: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x180: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x190: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x1A0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x1B0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x1C0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x1D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x1E0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
<4>RTW: 0x1F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF 10 00  
<4>RTW: hal_com_config_channel_plan chplan:0x20
<4>RTW: [RF_PATH] IC's RF PATH:RF_2T2R, max_tx_cnt:2
<4>RTW: [RF_PATH] PG's trx_path_bmp:0x00, max_tx_cnt:0
<4>RTW: [RF_PATH] Registry's RF PATH:UNKNOWN
<4>RTW: [RF_PATH] HALDATA's trx_path_bmp:0x33, max_tx_cnt:2
<4>RTW: [RF_PATH] HALDATA's RF PATH:RF_2T2R
<4>RTW: [RF_PATH] NumTotalRFPath:2
<4>RTW: [TRX_Nss] HALSPEC - tx_nss :2, rx_nss:2
<4>RTW: [TRX_Nss] Registry - tx_nss :0, rx_nss:0
<4>RTW: [TRX_Nss] HALDATA - tx_nss :2, rx_nss:2
<4>RTW: rtw_regsty_chk_target_tx_power_valid return _FALSE for band:0, path:0, rs:0, t:-1
<4>RTW: rtw_ndev_init(wlan0) if1 mac_addr=60:1d:9d:bd:48:f9
<6>usbcore: registered new interface driver rtl8192fu
<4>RTW: module init ret=0
<6>HI_DRV_SPI_Init success
<6>hisi-sndcard hisi-sndcard: aiao-hifi <-> hisi-i2s mapping ok
<4>spi spi0.0: invalid chip select
<4>hi_spi spi0.0: invalid chip select
<4>hi_spi spi0.0: invalid chip select
<6>input: front panel as /devices/virtual/input/input0
<6>input: dreambox advanced remote control (native) as /devices/virtual/input/input1
<6>input: rc mouse emulation as /devices/virtual/input/input2
<6>DVB: registering new adapter (dvb0)
<4>FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
<6>platform dvb0.0: DVB: registering adapter 0 frontend 0 (DVB-S2)...
<6>platform dvb0.0: DVB: registering adapter 0 frontend 1 (DVB-S2)...
<4>Mali: Mali device driver loaded
<6>EXT4-fs (mmcblk0p23): re-mounted. Opts: (null)
<6>IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
<6>hieth f9c30000.hieth eth0: Link is Up - 100Mbps/Full - flow control off
<6>IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
<4>UDF-fs: warning (device mmcblk0p1): udf_fill_super: No partition found (2)
<6>yaffs: dev is 187695105 name is "mmcblk0p1" rw
<6>yaffs: passed flags ""
<7>yaffs: yaffs: Attempting MTD mount of 179.1,"mmcblk0p1"
<7>yaffs: yaffs: MTD device 1 either not valid or unavailable
<6>yaffs: dev is 187695105 name is "mmcblk0p1" rw
<6>yaffs: passed flags ""
<7>yaffs: yaffs: Attempting MTD mount of 179.1,"mmcblk0p1"
<7>yaffs: yaffs: MTD device 1 either not valid or unavailable
<4>UDF-fs: warning (device mmcblk0p3): udf_fill_super: No partition found (2)
<6>yaffs: dev is 187695107 name is "mmcblk0p3" rw
<6>yaffs: passed flags ""
<7>yaffs: yaffs: Attempting MTD mount of 179.3,"mmcblk0p3"
<7>yaffs: yaffs: MTD device 3 either not valid or unavailable
<6>yaffs: dev is 187695107 name is "mmcblk0p3" rw
<6>yaffs: passed flags ""
<7>yaffs: yaffs: Attempting MTD mount of 179.3,"mmcblk0p3"
<7>yaffs: yaffs: MTD device 3 either not valid or unavailable
<4>FAT-fs (mmcblk0p4): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.


Re: Zgemma H9 Twin SE enigma.info #17 Dimitrij

  • PLi® Core member
  • 10,434 posts

+359
Excellent

Posted 11 January 2025 - 09:23

Ping WanWizard

 

Maybe

elif [ "$MACHINE" = "h9combose" ]; then
	if [ "$model" = "h9twinse" ]; then
		updateinfo "displaymodel" "H9 TWIN SE"
+               updateinfo "machine" "h9twinse"

 


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: Zgemma H9 Twin SE enigma.info #18 Dimitrij

  • PLi® Core member
  • 10,434 posts

+359
Excellent

Posted 12 January 2025 - 11:55

H9 TWIN

root@h9combo:~# grep "" /proc/stb/info/ -r
/proc/stb/info/model:h9combo             
/proc/stb/info/rsacrc:0000               
/proc/stb/info/serial:490000179A25F975   
/proc/stb/info/boxtype:H9Twin             
/proc/stb/info/chipset:hi3798mv200       
/proc/stb/info/release:da19d65           
/proc/stb/info/version:2                 
/proc/stb/info/brandname:Zgemma           
/proc/stb/info/board_revision:1           
root@h9combo:~#     

 


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users