cann't up majestic server in hi3516ev200

[jiangjianghu]

don't find majestic by ps -ef
and run majestic will fail.

log:

majestic
02:31:31 < majestic> [ main] main@822 Majestic Ultimate for HiSilicon (hi3516ev200), version master+1031662, built on 2026-08-29 01:05
02:31:31 < majestic> [ main] main@833 Loading main configuration: /etc/majestic.yaml
02:31:31 < majestic> [watchdog] watchdog_start@94 Detected Watchdog
02:31:31 < majestic> [watchdog] watchdog_start@115 Watchdog timeout set to 300 seconds
02:31:31 < majestic> [ httpd] start_web_server@680 Set server path: /var/www
02:31:31 < majestic> [ httpd] new_http_server@646 HTTP server started on :::80
02:31:31 < majestic> [ httpd] new_http_server@473 HTTPS port :::443 configured without cert/key; skipping TLS server
02:31:31 < majestic> [sensor_l] sensor_hint@42 SENSOR=gc2053
02:31:31 < majestic> [ sdk] find_sensor_config@5641 matched sensor config: gc2053_i2c_1080p.ini
02:31:31 < majestic> [ sdk] start_sdk@677 Using /etc/sensors/gc2053_i2c_1080p.ini sensor configuration file
02:31:31 < majestic> [ sdk] start_sdk@682 App was built with MPP version: Hi3516EV200_MPP_V1.0.1.2.B030 Release
02:31:31 < majestic> [ sdk] start_sdk@687 Current MPP version: HI_VERSION=Hi3516EV200_MPP_V1.0.1.2 B030 Release
02:31:31 < majestic> [ sdk] start_sdk@722 VB sizing: 3 blocks for the pipeline (0 of them held by the VI path), default 4, isp.blkCnt 4 in effect
02:31:31 < majestic> [ sdk] start_sdk@735 sensor stSnsGc2053Obj
02:31:31 < majestic> [ sdk] start_sdk@739 input_mode MIPI, WDR NONE
02:31:31 < majestic> [ sdk] start_sdk@744 dev [1920x1080]@200x20 25fps, RGGB
02:31:31 < majestic> [ sensor] try_to_load@19 trying to load /usr/lib/sensors/libsns_gc2053.so
02:31:31 < majestic> [ sensor] try_to_load@22 dlopen "/usr/lib/sensors/libsns_gc2053.so" error: Error relocating /usr/lib/sensors/libsns_gc2053.so: GK_API_ISP_GetModParam: symbol not found
02:31:31 < majestic> [ sensor] try_to_load@19 trying to load .//usr/lib/sensors/libsns_gc2053.so
02:31:31 < majestic> [ sensor] try_to_load@22 dlopen ".//usr/lib/sensors/libsns_gc2053.so" error: Error loading shared library .//usr/lib/sensors/libsns_gc2053.so: No such file or directory
02:31:31 < majestic> [ sensor] try_to_load@19 trying to load /usr/lib//usr/lib/sensors/libsns_gc2053.so
02:31:31 < majestic> [ sensor] try_to_load@22 dlopen "/usr/lib//usr/lib/sensors/libsns_gc2053.so" error: Error loading shared library /usr/lib//usr/lib/sensors/libsns_gc2053.so: No such file or directory
02:31:31 < majestic> [ main] init_sdk@85 Cannot start SDK
Segmentation fault

[jiangjianghu]

./ipctool info

chip:
vendor: HiSilicon
model: 3516EV200
id:
board:
vendor: OpenIPC
version: 2.6.08.29
ethernet:
mac: "12:28:1d:df:b1:67"
u-mdio-phyaddr: 1
phy-id: 0x20669903
d-mdio-phyaddr: 0
rom:

• type: nor
  block: 64K
  partitions:
  • name: boot
    size: 0x40000
    sha1: 7bf85f2b
  • name: env
    size: 0x10000
    sha1: 8df8a965
    contains:
    • name: uboot-env
      offset: 0x0
  • name: kernel
    size: 0x300000
    sha1: 992dff53
  • name: rootfs
    size: 0xa00000
    sha1: 6664b452
  • name: rootfs_data
    size: 0x2b0000
    path: /overlay,jffs2,rw
    size: 16M
    addr-mode: 3-byte
    ram:
    total: 64M
    media: 32M
    firmware:
    kernel: "4.9.37 (Sat Aug 29 04:24:03 UTC 2026)"
    toolchain: buildroot-gcc-13.3.0
    sdk: "Hi3516EV200_MPP_V1.0.1.2 B030 Release (Oct 18 2019, 18:21:00)"
    sensors:
• vendor: GalaxyCore
  model: GC2053
  control:
  bus: 0
  type: i2c
  addr: 0x6e
  vicap-state: down
  clocks:
  cpu_pll:
  freq_mhz: 900
  ddr:
  data_rate_mbps: 1200
  hpm:
  bin: mid

[widgetii]

Thanks for the report — the log you posted had everything needed. This is a firmware packaging bug, and it is now fixed.

What was wrong

The line that matters is this one:

dlopen "/usr/lib/sensors/libsns_gc2053.so" error: Error relocating
/usr/lib/sensors/libsns_gc2053.so: GK_API_ISP_GetModParam: symbol not found

GK_API_* is the Goke SDK's naming. On a HiSilicon image nothing provides those symbols — libisp.so exports the HI_MPI_* equivalents instead — so the loader refuses the library outright and the sensor never comes up.

The sensor drivers are built from source in openhisilicon, and that tree already had a compatibility header mapping the Goke names onto the HiSilicon ones. It was just incomplete in two ways, four drivers each: one symbol was never added to the mapping, and four drivers never included the header at all.

Eight of the thirty hi3516ev200 sensor drivers were affected:

gc2053 · f37 · sc2231 · sc500ai · gc4023 · gc5603 · os02g10 · sp2308

The other twenty-two were fine, which is why this survived so long — the sensors in the images most people run are all in the working group. Yours was not.

You can check any camera in one line:

for f in /usr/lib/sensors/*.so; do echo "$(strings $f | grep -c ^GK_API) $f"; done | sort -rn

Any nonzero count is a driver that cannot load on that image.

Fixed

• hi3516ev200: finish the Goke-to-HiSilicon symbol mapping openhisilicon#215 — completes the symbol mapping
• hisilicon-opensdk: pick up the ev200 sensor symbol fix #2340 — picks it up

Verified by building the whole sensor tree both ways: zero drivers left naming GK_API_* for a HiSilicon build, and the Goke build unchanged (it must keep those names — the same sources serve both). On hardware, swapping only the rebuilt libsns_gc2053.so into a running hi3516ev300 turned the relocation error into Sensor driver loaded with the SDK starting normally.

Separately, majestic no longer exits on a sensor driver it cannot load — it stays up with the web interface reachable, so a camera in this state can be repaired remotely instead of needing physical access. That went in alongside the driver fix.

What to do

Both changes are on master. The nightly build with them should be available tomorrow — update to that and your GC2053 should come up normally.

If it still does not, please post the new log and the output of the one-liner above.