New rknn detector not working on home assistant add on.

[pedrol3001]

Description

I can`t start the add on on 13 beta-6 version when testing the new rknn detector. I am using an orangepi 5 with a Rockchip RK3588S. But i gives the following error when starting.

The file does exists from a ssh connection to the orangepi, but i don`t know if is really a bug or i am missing any configuration to make the docker container access this file (I already disabled protection mode).

[NickM-27]

thanks for the logs, I hope https://github.com/blakeblackshear/frigate-hass-addons/pull/146 will fix this

[MaBeniu]

Hello, I see the fix is already merged and I was able to re-install updated frigate HA Addon. However I still get the same error as stated above. (using odroid M1 with rockchip 3568)

in addition to this when I try to run it without rknn detector I get ffmpeg failure as also seen in the screenshot bellow:

here is my config ` mqtt: host: 192.168.x.x user: x password: x

birdseye: enabled: false

detectors: coral_pci: type: edgetpu device: pci:0

cameras: stogine: ffmpeg: hwaccel_args: preset-rk-h264 inputs:

• path: rtsp://user:password@192.168.x.x:554/cam/realmonitor?channel=1&subtype=0 roles:
  • record
  • detect detect: width: 640 height: 480 fps: 5 objects: track:
• person
• car
• cat filters: person: min_score: 0.5

  Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)

    threshold: 0.77
  car:
    min_score: 0.5
    # Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
    threshold: 0.70

  snapshots: enabled: true timestamp: false bounding_box: True retain: default: 1 record: enabled: True retain: days: 1 mode: motion events: retain: default: 1 mode: active_objects `

[NickM-27]

It's possible running as an addon may be more complicated due to needing access to the devices hardware

[NickM-27]

@MarcA711 we are going to need to get some more info from users here, based on the addon config docs I think the device tree may be mounted as /device-tree/ in the addon

[NickM-27]

unfortunately the files needed for ffmpeg also seem to be missing, we may need to make the rockchip addon beta only for 0.13 while we work out if the addon will be possible

[pedrol3001]

@MarcA711 we are going to need to get some more info from users here, based on the addon config docs I think the device tree may be mounted as /device-tree/ in the addon

It does mount on the /device-tree folder.

Isn`t it better to mount the volume directly from supervisor.sh ? I dont realy know if it works.

function run_supervisor() {
    mkdir -p /tmp/supervisor_data
    docker run --rm --privileged \
       ...
        -v /proc/device-tree:/proc/device-tree:ro \
       ...
}

[NickM-27]

That's not in the addon's control. If it is mounted in device-tree then the rknn detector should simply check both locations

[MarcA711]

Thank you for reporting.

Unfortunately, I don't have home assistant installed and can't do so, because I have only remote access to my machine.

I wonder why the detector can't find /proc/device-tree/compatible even though the directory was mounted into the container. Maybe it is a permission issue?

[MaBeniu]

I think issue is as Nick shared, addons are very limited to what they can get access to. being an admin user in home assistant if you try to find /proc/device-tree that is not available either. I am able to access it only via SSH with root access which is not available for HA itself. HA doesnt have access to it and probably cannot be even mounted. reference to HA AddOn documentation: https://developers.home-assistant.io/docs/add-ons/configuration#optional-configuration-options

if I understand right frigate addon for rockchip is using "full_access" mode and still seem to have issues.

if I could be of any help to retrieve useful info let me know.

[MarcA711]

Ah, so I got it wrong. The issue is not that the rknn plugin can't open the /proc/device-tree/compatible file. The problem is that docker is not able to mount this file to the container. Is this right?

[pedrol3001]

Ah, so I got it wrong. The issue is not that the rknn plugin can't open the /proc/device-tree/compatible file. The problem is that docker is not able to mount this file to the container. Is this right?

I think is does mount with the flag devicetree: true (added in here #146). The problem is that it is on the folder /device-tree and nor on the folder /proc/device-tree as requests by the rknn plugin.

Any chance of changing the mais frigate code to use the same folder as home assistant ?

[MarcA711]

Ah okay, now I got it.

I could change my code to also check /device-tree/compatible if there is no file in /proc/device-tree/compatible. However, the rknn detector also needs this file and I think it searches only in /proc/device-tree/compatible.

Therefore I propose the following solution:

1. Check if there is a file in /proc/device-tree/compatible. If yes start as usual, if not go to 2.

2. Check if there is a file in /device-tree/compatible. If yes create a symlink to /proc/device-tree/compatible, if not raise an exception.

Is this possibly the way to handle this?

Edit: With the term "rknn detector" that I used above I actually mean the Python API from rockchip (called RKNN-Toolkit-Lite2) to interact with the rockchip NPU. Not the file "rknn.py" that is stored in the frigate/detector/plugin folder.

[pedrol3001]

Ah okay, now I got it.

I could change my code to also check /device-tree/compatible if there is no file in /proc/device-tree/compatible. However, the rknn detector also needs this file and I think it searches only in /proc/device-tree/compatible.

Therefore I propose the following solution:

1. Check if there is a file in /proc/device-tree/compatible. If yes start as usual, if not go to 2.
2. Check if there is a file in /device-tree/compatible. If yes create a symlink to /proc/device-tree/compatible, if not raise an exception.

Is this possibly the way to handle this?

Edit: With the term "rknn detector" that I used above I actually mean the Python API from rockchip (called RKNN-Toolkit-Lite2) to interact with the rockchip NPU. Not the file "rknn.py" that is stored in the frigate/detector/plugin folder.

I think this could work. Any idea if this will get on the 13 beta 6/7 version or just after 13.0 release ?

[pedrol3001]

Looking at home assistant code, they mount a different device-tree folder (/sys/firmware/devicetree/base) . Is it a problem for the "rknn detector" ?

[MarcA711]

Yes, it should also work using this mount.

I will try to update the code to avoid this issue.

[juanjoSanz]

Simbolic link workaround is not working, I cannot overwrite existing one /proc/device-tree and it links a non existing folder into a read only file system.

root@ccab4aaf-frigate-rk-beta:/opt/frigate# ln -sf /device-tree/compatible /proc/device-tree/compatible
ln: failed to create symbolic link '/proc/device-tree/compatible': No such file or directory

root@ccab4aaf-frigate-rk-beta:/opt/frigate# ls -l /device-tree/compatible /proc/device-tree
-r--r--r-- 1 root root 48 Nov 25 18:11 /device-tree/compatible
lrwxrwxrwx 1 root root 29 Nov 27 17:17 /proc/device-tree -> /sys/firmware/devicetree/base

root@ccab4aaf-frigate-rk-beta:/opt/frigate# ls -l /sys/firmware/devicetree/base
ls: cannot access '/sys/firmware/devicetree/base': No such file or directory

root@ccab4aaf-frigate-rk-beta:/opt/frigate# mkdir -p /sys/firmware/devicetree/base
mkdir: cannot create directory '/sys/firmware/devicetree': Read-only file system

Any other option?

[NickM-27]

@juanjoSanz what about ls /proc/device-tree

[pedrol3001]

Simbolic link workaround is not working, I cannot overwrite existing one /proc/device-tree and it links a non existing folder into a read only file system.

root@ccab4aaf-frigate-rk-beta:/opt/frigate# ln -sf /device-tree/compatible /proc/device-tree/compatible
ln: failed to create symbolic link '/proc/device-tree/compatible': No such file or directory

root@ccab4aaf-frigate-rk-beta:/opt/frigate# ls -l /device-tree/compatible /proc/device-tree
-r--r--r-- 1 root root 48 Nov 25 18:11 /device-tree/compatible
lrwxrwxrwx 1 root root 29 Nov 27 17:17 /proc/device-tree -> /sys/firmware/devicetree/base

root@ccab4aaf-frigate-rk-beta:/opt/frigate# ls -l /sys/firmware/devicetree/base
ls: cannot access '/sys/firmware/devicetree/base': No such file or directory

root@ccab4aaf-frigate-rk-beta:/opt/frigate# mkdir -p /sys/firmware/devicetree/base
mkdir: cannot create directory '/sys/firmware/devicetree': Read-only file system

Any other option?

Try creating the symbolic link for the folder instead ln -sf /device-tree /proc/device-tree. The compatible part is the name of a file.

[NickM-27]

@pedrol3001 you can try this as well by the way, just need to run docker exec -it ccab4aaf-frigate-rk-beta /bin/bash to get a shell

[juanjoSanz]

From docker shell this is not modificable:

root@ccab4aaf-frigate-rk-beta:/opt/frigate# ln -sf /device-tree/ /proc/device-tree
ln: failed to create symbolic link '/proc/device-tree': No such file or directory

root@ccab4aaf-frigate-rk-beta:/opt/frigate# rm /proc/device-tree
rm: cannot remove '/proc/device-tree': Permission denied

[juanjoSanz]

I am testing other approach:

docker exec -it <docker-id....> /bin/bash
sed -i "s/\/proc\/device-tree/\/device-tree/g" /opt/frigate/frigate/detectors/plugins/rknn.py

[pedrol3001]

Maybe changing the privileged mode on the confi.yaml enable us to change this file system? I couldn`t find any documentation on what it exactly does.

I can see 2 option here, but none of them works because of the permission inside docker:

• Creating the sym link directly on /sys/firmware/devicetree/base
• Changing the /proc/device-tree (already a sym link to /sys/firmware/devicetree/base) to point to /device-tree.

[NickM-27]

it is documented at https://developers.home-assistant.io/docs/add-ons/configuration#optional-configuration-options

only one I can think of is SYS_ADMIN

[NickM-27]

This can be reopened, I didn't expect that my comment on the PR would close the issue

[NickM-27]

after being sure to update the addon and making sure that protected mode is disabled, would be good to know if anything has changed

[pedrol3001]

Nothing has changed...

[MaBeniu]

Maybe stupid question, but is it required to find device-tree? Could it be that user specifies missing information, what hardware he has in the config instead so program doesn't need access to the dev-tree?

[NickM-27]

@MaBeniu the rknn api also needs the information to be in the correct place according to what was said above

However, the rknn detector also needs this file and I think it searches only in /proc/device-tree/compatible.

[MarcA711]

I guess it is worth trying it out by replacing these lines in rknn.py:

        # create symlink for Home Assistant add on
        if not os.path.isfile("/proc/device-tree/compatible"):
            if os.path.isfile("/device-tree/compatible"):
                os.symlink("/device-tree/compatible", "/proc/device-tree/compatible")

        # find out SoC
        try:
            with open("/proc/device-tree/compatible") as file:
                soc = file.read().split(",")[-1].strip("\x00")
        except FileNotFoundError:
            logger.error("Make sure to run docker in privileged mode.")
            raise Exception("Make sure to run docker in privileged mode.")

with this:

        soc ="rk3588" # or "rk3562", "rk3566", "rk3568" 

[pedrol3001]

I guess it is worth trying it out by replacing these lines in rknn.py:

        # create symlink for Home Assistant add on
        if not os.path.isfile("/proc/device-tree/compatible"):
            if os.path.isfile("/device-tree/compatible"):
                os.symlink("/device-tree/compatible", "/proc/device-tree/compatible")

        # find out SoC
        try:
            with open("/proc/device-tree/compatible") as file:
                soc = file.read().split(",")[-1].strip("\x00")
        except FileNotFoundError:
            logger.error("Make sure to run docker in privileged mode.")
            raise Exception("Make sure to run docker in privileged mode.")

with this:

        soc ="rk3588" # or "rk3562", "rk3566", "rk3568" 

What about the RKNN-Toolkit-Lite2 code that you said it depends on the /proc/device-tree too?

[MarcA711]

@pedrol3001 This is exactly the thing I want to try out. During development, I had to mount /proc/device-tree or use privileged mode, else rknn toolkit complained. Maybe it works on this system differently (maybe rknn really checks the /device-tree directory for example). Just to make sure it really won't work, as I said since we never tested if it really fails.

[pedrol3001]

@MarcA711 The RKNN-Toolkit-Lite2 uses the device-tree only to see if it is compatible (on the compatible file) or to something else ? If this is the only reason, is it possible to remove this folder dependency ?

[MaBeniu]

I get it that Frigate HA Addon for rockchip devices is now probably stuck to infinity but still I would like to add that I was not able to use any of theses: rknn, neither ffmpeg hardware acceleration, neither go2rtc parameters. :(

[NickM-27]

it seems right now the addons do not permit the proper access needed to run rknn as an addon unfortunately

[MarcA711]

@pedrol3001 I don't know this. There is unfortunately no source code available.

I currently don't have access to a rockchip board with HassOS. However, in like 3 weeks I have physical access to my board and can install HassOS. Then I can debug it properly and hopefully find a solution.

[YuryMcv]

    # create symlink for Home Assistant add on
    if not os.path.isfile("/proc/device-tree/compatible"):
        if os.path.isfile("/device-tree/compatible"):
            os.symlink("/device-tree/compatible", "/proc/device-tree/compatible")

    # find out SoC
    try:
        with open("/proc/device-tree/compatible") as file:
            soc = file.read().split(",")[-1].strip("\x00")
    except FileNotFoundError:
        logger.error("Make sure to run docker in privileged mode.")
        raise Exception("Make sure to run docker in privileged mode.")

[mcarbonneaux]

i've ordroid-m1 with haos.

i have link from /proc/device-tree to /sys/firmware/devicetree/base but i don't have file /sys/firmware/devicetree/base in fact...

but on the docker host:

# cat /proc/device-tree/compatible
rockchip,rk3568-odroid-m1rockchip,rk3568
# ls -al /proc/device-tree
lrwxrwxrwx    1 root     root            29 Jan 17 20:14 /proc/device-tree -> /sys/firmware/devicetree/base
# ls -al /sys/firmware/devicetree
total 0
drwxr-xr-x    3 root     root             0 Jan 17 20:14 .
drwxr-xr-x    3 root     root             0 Jan 17 20:14 ..
drwxr-xr-x  154 root     root             0 Jan 17 20:14 base
# cat /sys/kernel/debug/rknpu/load
cat: can't open '/sys/kernel/debug/rknpu/load': No such file or directory
# ls /sys/kernel/debug/
asoc                     devfreq                  extfrag                  iio                      opp                      selftest_ecdh            ulpi
bdi                      device_component         f2fs                     interconnect             pinctrl                  selftest_smp             usb
block                    devices_deferred         fault_around_bytes       kprobes                  pm_genpd                 slab                     virtio-ports
bluetooth                dma_buf                  fe530000.dma-controller  kvm                      psci                     sleep_time               wakeup_sources
cec                      dma_pools                fe550000.dma-controller  lru_gen                  pwm                      spi-nor                  zswap
clear_warn_once          dmaengine                frontswap                lru_gen_full             ras                      split_huge_pages
clk                      dri                      gpio                     memblock                 regmap                   stmmaceth
cma                      dynamic_debug            hid                      mmc0                     regulator                suspend_stats
custom_method            energy_model             hns3                     mmc1                     remoteproc               swiotlb
debug_enabled            error_injection          ieee80211                mtd                      sched                    ufshcd

[MarcA711]

Sorry for the late reply. Unfortunately, I don't have that much time to work on this at the moment.

The last couple weeks, I did some research into the rknn toolkit, but I found no way to avoid it to check /proc/device-tree/compatible. Since \proc is read-only it is also impossible to create a symlink.

I will open an issue in HA to add an option to provide a path for the device-tree. However, I don't know if they will implement this feature. Even if they do, we will have to wait for the next release.

So, we should try to find a workaround. Within the docker container, there seems to be no way to fix this. So, we need to find a way to build an image that correctly links the device-tree to /proc/device-tree/compatible.

[MarcA711]

@mcarbonneaux

within the docker container, there should be a file at /device-tree/compatible. Is it there?

Could you please run these commands on your docker host and post the output: sudo ls -al /sys/firmware/devicetree/base uname -a sudo ls -al /dev/dri/ sudo cat /sys/kernel/debug/rknpu/version

[nyok92]

I did some tests , It seems the addon devicee_tree: true option is indeed working. The docker host /proc/device-tree is indeed "mounted" in container to /device-tree

So I changed rknn.py :

class Rknn(DetectionApi):
    type_key = DETECTOR_KEY

    def __init__(self, config: RknnDetectorConfig):
        # create symlink for Home Assistant add on
        if not os.path.isfile("/proc/device-tree/compatible"):
            if os.path.isfile("/device-tree/compatible"):
                os.symlink("/device-tree/compatible", "/proc/device-tree/compatible")

        # find out SoC
        try:
            with open("/proc/device-tree/compatible") as file:
                soc = file.read().split(",")[-1].strip("\x00")
        except FileNotFoundError:
            logger.error("Make sure to run docker in privileged mode.")
            raise Exception("Make sure to run docker in privileged mode.")

to

class Rknn(DetectionApi):
    type_key = DETECTOR_KEY

    def __init__(self, config: RknnDetectorConfig):
        # create symlink for Home Assistant add on
        if not os.path.isfile("/device-tree/compatible"):
            if os.path.isfile("/proc/device-tree/compatible"):
                os.symlink("/proc/device-tree/compatible", "/device-tree/compatible")

        # find out SoC
        try:
            with open("/device-tree/compatible") as file:
                soc = file.read().split(",")[-1].strip("\x00")
        except FileNotFoundError:
            logger.error("Make sure to run docker in privileged mode.")
            raise Exception("Make sure to run docker in privileged mode.")

Now if i restart the container from docker host (not from HA), there is no error/warning checking the device tree folder but i've got new warnings regarding rknn init:

2024-01-18 13:04:17.991153154  **************************************************
2024-01-18 13:04:17.991164820  !!! It is detected that some necessary files are missing in the container.
2024-01-18 13:04:17.991218194  !!! When starting the container, please use the -v parameter to map the corresponding files in the host to the container.
2024-01-18 13:04:17.991221694  The reference parameters of run container are as follows:
2024-01-18 13:04:17.991281192      -v /dev/dri/renderD129:/dev/dri/renderD129
2024-01-18 13:04:17.991321441      -v /proc/device-tree/compatible:/proc/device-tree/compatible
2024-01-18 13:04:17.991363440  **************************************************
2024-01-18 13:04:17.991714596  E Catch exception when init runtime!
2024-01-18 13:04:17.993822412  E Traceback (most recent call last):
2024-01-18 13:04:17.993827370    File "/usr/local/lib/python3.9/dist-packages/rknnlite/api/rknn_lite.py", line 140, in init_runtime
2024-01-18 13:04:17.993830870      self.rknn_runtime = RKNNRuntime(root_dir=self.root_dir, target=target, device_id=device_id,
2024-01-18 13:04:17.993839911    File "rknnlite/api/rknn_runtime.py", line 305, in rknnlite.api.rknn_runtime.RKNNRuntime.__init__
2024-01-18 13:04:17.993911659    File "rknnlite/api/rknn_runtime.py", line 346, in rknnlite.api.rknn_runtime.RKNNRuntime._check_container
2024-01-18 13:04:17.993915451  RuntimeError
2024-01-18 13:04:17.993917200  
2024-01-18 13:04:17.995437324  [2024-01-18 14:04:17] frigate.detectors.plugins.rknn E       : Error initializing rknn runtime. Do you run docker in privileged mode?

Do I have to install Rknn toolkit2 & MP / RKMPP on host too ? Is privileged SYS_ADMIN enough or should we mount devices to the container?

It seems that container symlink from /device-tree to /proc/device-tree is not working correctly: Is rknn toolkit (inside container) only checking for /proc/device-tree only ? Maybe we could change it to /device-tree ?

root@ccab4aaf-frigate-rk-beta:~# cd /proc
root@ccab4aaf-frigate-rk-beta:/proc# ls
1    147  187  27    31   4373  4463  460  470  89          buddyinfo  consoles     diskstats      filesystems  irq        kpagecgroup  mdstat   mtd           self      sys            tty          zoneinfo
113  15   213  28    32   4437  447   465  478  97          bus        cpuinfo      driver         fs           kallsyms   kpagecount   meminfo  net           slabinfo  sysrq-trigger  uptime
144  150  24   2870  375  4438  449   466  79   98          cgroups    crypto       dynamic_debug  interrupts   key-users  kpageflags   misc     pagetypeinfo  softirqs  sysvipc        version
145  163  25   29    41   4441  457   468  81   asound      cmdline    **device-tree**  execdomains    iomem        keys       loadavg      modules  partitions    stat      thread-self    vmallocinfo
146  17   26   30    42   4442  459   469  82   bootconfig  config.gz  devices      fb             ioports      kmsg       locks        mounts   scsi          swaps     timer_list     vmstat
root@ccab4aaf-frigate-rk-beta:/proc# cd device-tree
bash: cd: device-tree: No such file or directory

Could it help ? Maybe that I am misleading ...

[nyok92]

@MarcA711

root@rock-5b:/dev/dri# sudo ls -al /sys/firmware/devicetree/base
total 0
drwxr-xr-x 201 root root  0 Nov 10 00:25  .
drwxr-xr-x   3 root root  0 Nov 10 00:25  ..
drwxr-xr-x   2 root root  0 Jan 17 21:46  adc@fec10000
-r--r--r--   1 root root  4 Jan 18 12:49 '#address-cells'
drwxr-xr-x   2 root root  0 Jan 17 21:46  aliases
drwxr-xr-x   2 root root  0 Jan 17 21:46  analog-sound
drwxr-xr-x   2 root root  0 Jan 17 21:46  chosen
drwxr-xr-x   2 root root  0 Jan 17 21:46  clock-0
drwxr-xr-x   2 root root  0 Jan 17 21:46  clock-1
drwxr-xr-x   2 root root  0 Jan 17 21:46  clock-2
drwxr-xr-x   2 root root  0 Jan 17 21:46  clock-controller@fd7c0000
-r--r--r--   1 root root 30 Nov 10 00:25  compatible
drwxr-xr-x  21 root root  0 Jan 17 21:46  cpus
drwxr-xr-x   2 root root  0 Jan 17 21:46  crypto@fe370000
drwxr-xr-x   2 root root  0 Jan 17 21:46  dfi@fe060000
drwxr-xr-x   2 root root  0 Jan 17 21:46  display-subsystem
drwxr-xr-x   2 root root  0 Jan 17 21:46  dma-controller@fea10000
drwxr-xr-x   2 root root  0 Jan 17 21:46  dma-controller@fea30000
drwxr-xr-x   2 root root  0 Jan 17 21:46  dma-controller@fed10000
drwxr-xr-x  12 root root  0 Jan 17 21:46  efuse@fecc0000
drwxr-xr-x   6 root root  0 Jan 17 21:46  ethernet@fe1b0000
drwxr-xr-x   6 root root  0 Jan 17 21:46  ethernet@fe1c0000
drwxr-xr-x   4 root root  0 Jan 17 21:46  firmware
drwxr-xr-x   3 root root  0 Jan 17 21:46  hdmi-con
drwxr-xr-x   3 root root  0 Jan 17 21:46  hdmi@fde80000
drwxr-xr-x   3 root root  0 Jan 17 21:46  hdmiphy@fed60000
drwxr-xr-x   4 root root  0 Jan 17 21:46  i2c@fd880000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2c@fea90000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2c@feaa0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2c@feab0000
drwxr-xr-x   3 root root  0 Jan 17 21:46  i2c@feac0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2c@fead0000
drwxr-xr-x   3 root root  0 Jan 17 21:46  i2c@fec80000
drwxr-xr-x   3 root root  0 Jan 17 21:46  i2c@fec90000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2c@feca0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2s@fddc0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2s@fddc8000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2s@fddf0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2s@fddf4000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2s@fddf8000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2s@fddfc000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2s@fde00000
drwxr-xr-x   3 root root  0 Jan 17 21:46  i2s@fe470000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2s@fe480000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2s@fe490000
drwxr-xr-x   2 root root  0 Jan 17 21:46  i2s@fe4a0000
drwxr-xr-x   5 root root  0 Jan 17 21:46  interrupt-controller@fe600000
-r--r--r--   1 root root  4 Jan 18 12:49  interrupt-parent
drwxr-xr-x   2 root root  0 Jan 17 21:46  iommu@fdd97e00
drwxr-xr-x   3 root root  0 Jan 17 21:46  leds
drwxr-xr-x   2 root root  0 Jan 17 21:46  memory
drwxr-xr-x   2 root root  0 Jan 17 21:46  mmc@fe2c0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  mmc@fe2d0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  mmc@fe2e0000
-r--r--r--   1 root root 21 Jan 18 09:48  model
-r--r--r--   1 root root  1 Jan 18 12:49  name
drwxr-xr-x  10 root root  0 Jan 17 21:46  opp-table-cluster0
drwxr-xr-x  12 root root  0 Jan 17 21:46  opp-table-cluster1
drwxr-xr-x  12 root root  0 Jan 17 21:46  opp-table-cluster2
drwxr-xr-x   3 root root  0 Jan 17 21:46  pcie@fe150000
drwxr-xr-x   3 root root  0 Jan 17 21:46  pcie@fe160000
drwxr-xr-x   3 root root  0 Jan 17 21:46  pcie@fe170000
drwxr-xr-x   3 root root  0 Jan 17 21:46  pcie@fe180000
drwxr-xr-x   3 root root  0 Jan 17 21:46  pcie@fe190000
drwxr-xr-x   5 root root  0 Jan 17 21:46  phy@fed80000
drwxr-xr-x   4 root root  0 Jan 17 21:46  phy@fed90000
drwxr-xr-x   2 root root  0 Jan 17 21:46  phy@fee00000
drwxr-xr-x   2 root root  0 Jan 17 21:46  phy@fee10000
drwxr-xr-x   2 root root  0 Jan 17 21:46  phy@fee20000
drwxr-xr-x   2 root root  0 Jan 17 21:46  phy@fee80000
drwxr-xr-x 163 root root  0 Jan 17 21:46  pinctrl
drwxr-xr-x   2 root root  0 Jan 17 21:46  pmu-a55
drwxr-xr-x   2 root root  0 Jan 17 21:46  pmu-a76
drwxr-xr-x   3 root root  0 Jan 17 21:46  power-management@fd8d8000
drwxr-xr-x   2 root root  0 Jan 17 21:46  psci
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm-fan
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@fd8b0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@fd8b0010
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@fd8b0020
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@fd8b0030
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@febd0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@febd0010
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@febd0020
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@febd0030
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@febe0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@febe0010
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@febe0020
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@febe0030
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@febf0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@febf0010
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@febf0020
drwxr-xr-x   2 root root  0 Jan 17 21:46  pwm@febf0030
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf35000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf35200
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf35400
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf35600
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf36000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf39000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf3d800
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf3e000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf3e200
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf3e400
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf3e600
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf40000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf40200
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf40400
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf40500
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf40600
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf40800
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf41000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf41100
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf60000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf60200
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf60400
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf61000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf61200
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf61400
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf62000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf63000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf64000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf66000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf66200
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf66400
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf66600
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf66800
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf66a00
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf66c00
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf66e00
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf67000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf67200
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf70000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf71000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf72000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf72200
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf72400
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf80000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf81000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf81200
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf82000
drwxr-xr-x   2 root root  0 Jan 17 21:46  qos@fdf82200
drwxr-xr-x   2 root root  0 Jan 17 21:46  rng@fe378000
drwxr-xr-x   3 root root  0 Jan 17 21:46  sata@fe210000
drwxr-xr-x   3 root root  0 Jan 17 21:46  sata@fe220000
drwxr-xr-x   3 root root  0 Jan 17 21:46  sata@fe230000
drwxr-xr-x   2 root root  0 Jan 17 21:46  serial@fd890000
drwxr-xr-x   2 root root  0 Jan 17 21:46  serial@feb40000
drwxr-xr-x   2 root root  0 Jan 17 21:46  serial@feb50000
drwxr-xr-x   2 root root  0 Jan 17 21:46  serial@feb60000
drwxr-xr-x   2 root root  0 Jan 17 21:46  serial@feb70000
drwxr-xr-x   2 root root  0 Jan 17 21:46  serial@feb80000
drwxr-xr-x   2 root root  0 Jan 17 21:46  serial@feb90000
drwxr-xr-x   2 root root  0 Jan 17 21:46  serial@feba0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  serial@febb0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  serial@febc0000
-r--r--r--   1 root root 17 Jan 18 12:49  serial-number
-r--r--r--   1 root root  4 Jan 18 12:49 '#size-cells'
drwxr-xr-x   2 root root  0 Jan 17 21:46  spi@fe2b0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  spi@feb00000
drwxr-xr-x   2 root root  0 Jan 17 21:46  spi@feb10000
drwxr-xr-x   3 root root  0 Jan 17 21:46  spi@feb20000
drwxr-xr-x   2 root root  0 Jan 17 21:46  spi@feb30000
drwxr-xr-x   2 root root  0 Jan 17 21:46  spi@fecb0000
drwxr-xr-x   3 root root  0 Jan 17 21:46  sram@10f000
drwxr-xr-x   2 root root  0 Jan 17 21:46  sram@fd600000
drwxr-xr-x   2 root root  0 Jan 17 21:46  sram@ff001000
drwxr-xr-x   2 root root  0 Jan 17 21:46  __symbols__
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd58a000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd58c000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd590000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd592000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5a4000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5a6000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5a8000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5ac000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5b0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5b8000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5bc000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5c0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5c4000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5c8000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5cc000
drwxr-xr-x   3 root root  0 Jan 17 21:46  syscon@fd5d0000
drwxr-xr-x   3 root root  0 Jan 17 21:46  syscon@fd5d4000
drwxr-xr-x   3 root root  0 Jan 17 21:46  syscon@fd5d8000
drwxr-xr-x   3 root root  0 Jan 17 21:46  syscon@fd5dc000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5e0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  syscon@fd5f0000
drwxr-xr-x   9 root root  0 Jan 17 21:46  thermal-zones
drwxr-xr-x   2 root root  0 Jan 17 21:46  timer
drwxr-xr-x   2 root root  0 Jan 17 21:46  timer@feae0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  tsadc@fec00000
drwxr-xr-x   3 root root  0 Jan 17 21:46  usb@fc000000
drwxr-xr-x   2 root root  0 Jan 17 21:46  usb@fc400000
drwxr-xr-x   2 root root  0 Jan 17 21:46  usb@fc800000
drwxr-xr-x   2 root root  0 Jan 17 21:46  usb@fc840000
drwxr-xr-x   2 root root  0 Jan 17 21:46  usb@fc880000
drwxr-xr-x   2 root root  0 Jan 17 21:46  usb@fc8c0000
drwxr-xr-x   2 root root  0 Jan 17 21:46  usb@fcd00000
drwxr-xr-x   2 root root  0 Jan 17 21:46  vcc12v-dcin-regulator
drwxr-xr-x   2 root root  0 Jan 17 21:46  vcc-1v1-nldo-s3-regulator
drwxr-xr-x   2 root root  0 Jan 17 21:46  vcc3v3-pcie2x1l0-regulator
drwxr-xr-x   2 root root  0 Jan 17 21:46  vcc3v3-pcie2x1l2-regulator
drwxr-xr-x   2 root root  0 Jan 17 21:46  vcc3v3-pcie30-regulator
drwxr-xr-x   2 root root  0 Jan 17 21:46  vcc5v0-host-regulator
drwxr-xr-x   2 root root  0 Jan 17 21:46  vcc5v0-sys-regulator
drwxr-xr-x   2 root root  0 Jan 17 21:46  video-codec@fdc70000
drwxr-xr-x   3 root root  0 Jan 17 21:46  vop@fdd90000
drwxr-xr-x   2 root root  0 Jan 17 21:46  watchdog@feaf0000

root@rock-5b:/dev/dri# uname -a
Linux rock-5b 6.7.0-edge-rockchip-rk3588 #3 SMP PREEMPT Sun Jan  7 20:18:38 UTC 2024 aarch64 GNU/Linux

root@rock-5b:/dev/dri# sudo ls -al /dev/dri/
total 0
drwxr-xr-x  3 root root      80 Jan 17 21:46 .
drwxr-xr-x 18 root root    4640 Jan 17 21:46 ..
drwxr-xr-x  2 root root      60 Jan 17 21:46 by-path
crw-rw----  1 root video 226, 0 Jan 17 21:46 card0

root@rock-5b:/dev/dri# sudo cat /sys/kernel/debug/rknpu/version
cat: /sys/kernel/debug/rknpu/version: No such file or directory

[mcarbonneaux]

https://github.com/home-assistant/operating-system/issues/3089 the problem are that haos as no rknpu driver.... because is only on downstream kernel... but i've seen elsewhere rknpu driver frontported to upstream kernel...

[mcarbonneaux]

@MarcA711

i'm on haos 11.4 on odroid-m1.

sudo ls -al /sys/firmware/devicetree/base uname -a sudo ls -al /dev/dri/ sudo cat /sys/kernel/debug/rknpu/version

# ls -al /sys/firmware/devicetree/base
total 0
-r--r--r--    1 root     root             4 Jan 19 22:10 #address-cells
-r--r--r--    1 root     root             4 Jan 19 22:10 #size-cells
drwxr-xr-x  154 root     root             0 Apr  4  2023 .
drwxr-xr-x    3 root     root             0 Apr  4  2023 ..
drwxr-xr-x    2 root     root             0 Jan 19 22:10 __symbols__
drwxr-xr-x    2 root     root             0 Apr  4  2023 aliases
drwxr-xr-x    2 root     root             0 Jan 19 22:10 chosen
drwxr-xr-x    2 root     root             0 Jan 19 22:10 clock-controller@fdd00000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 clock-controller@fdd20000
-r--r--r--    1 root     root            42 Apr  4  2023 compatible
drwxr-xr-x    6 root     root             0 Jan 19 22:10 cpus
drwxr-xr-x    2 root     root             0 Jan 19 22:10 dc-12v-regulator
drwxr-xr-x    2 root     root             0 Jan 19 22:10 display-subsystem
drwxr-xr-x    2 root     root             0 Jan 19 22:10 dma-controller@fe530000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 dma-controller@fe550000
drwxr-xr-x    3 root     root             0 Jan 19 22:10 dsi@fe060000
drwxr-xr-x    3 root     root             0 Jan 19 22:10 dsi@fe070000
drwxr-xr-x    6 root     root             0 Jan 19 22:10 ethernet@fe010000
drwxr-xr-x    6 root     root             0 Apr  4  2023 ethernet@fe2a0000
drwxr-xr-x    3 root     root             0 Jan 19 22:10 firmware
drwxr-xr-x    2 root     root             0 Jan 19 22:10 gpu@fde60000
drwxr-xr-x    3 root     root             0 Jan 19 22:10 hdmi-con
drwxr-xr-x    4 root     root             0 Jan 19 22:10 hdmi-sound
drwxr-xr-x    3 root     root             0 Jan 19 22:10 hdmi@fe0a0000
drwxr-xr-x    4 root     root             0 Jan 19 22:10 i2c@fdd40000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 i2c@fe5a0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 i2c@fe5b0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 i2c@fe5c0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 i2c@fe5d0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 i2c@fe5e0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 i2s@fe400000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 i2s@fe410000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 i2s@fe430000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 interrupt-controller@fd400000
-r--r--r--    1 root     root             4 Jan 19 22:10 interrupt-parent
drwxr-xr-x    2 root     root             0 Jan 19 22:10 iommu@fdea0800
drwxr-xr-x    2 root     root             0 Jan 19 22:10 iommu@fdee0800
drwxr-xr-x    2 root     root             0 Jan 19 22:10 iommu@fe043e00
drwxr-xr-x    2 root     root             0 Jan 19 22:10 ir-receiver
drwxr-xr-x    4 root     root             0 Jan 19 22:10 leds
drwxr-xr-x    2 root     root             0 Jan 19 22:10 memory
drwxr-xr-x    2 root     root             0 Jan 19 22:10 mipi-dphy@fe850000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 mipi-dphy@fe860000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 mmc@fe000000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 mmc@fe2b0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 mmc@fe2c0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 mmc@fe310000
-r--r--r--    1 root     root            21 Jan 19 22:10 model
-r--r--r--    1 root     root             1 Jan 19 22:10 name
drwxr-xr-x   10 root     root             0 Jan 19 22:10 opp-table-0
drwxr-xr-x    8 root     root             0 Jan 19 22:10 opp-table-1
drwxr-xr-x    3 root     root             0 Jan 19 22:10 pcie@fe260000
drwxr-xr-x    3 root     root             0 Jan 19 22:10 pcie@fe270000
drwxr-xr-x    3 root     root             0 Jan 19 22:10 pcie@fe280000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pdm@fe440000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 phy@fe820000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 phy@fe830000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 phy@fe840000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 phy@fe870000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 phy@fe8c0000
drwxr-xr-x  159 root     root             0 Jan 19 22:10 pinctrl
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pmu
drwxr-xr-x    3 root     root             0 Jan 19 22:10 power-management@fdd90000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 psci
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fdd70000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fdd70010
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fdd70020
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fdd70030
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fe6e0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fe6e0010
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fe6e0020
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fe6e0030
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fe6f0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fe6f0010
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fe6f0020
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fe6f0030
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fe700000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fe700010
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fe700020
drwxr-xr-x    2 root     root             0 Jan 19 22:10 pwm@fe700030
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe128000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe138080
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe138100
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe138180
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe148000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe148080
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe148100
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe150000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe158000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe158100
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe158180
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe158200
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe158280
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe158300
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe180000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe190000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe190080
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe190100
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe190200
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe190280
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe190300
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe190380
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe190400
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe198000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe1a8000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe1a8080
drwxr-xr-x    2 root     root             0 Jan 19 22:10 qos@fe1a8100
drwxr-xr-x    4 root     root             0 Jan 19 22:10 rk809-sound
drwxr-xr-x    2 root     root             0 Jan 19 22:10 saradc@fe720000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 sata@fc000000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 sata@fc400000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 sata@fc800000
-r--r--r--    1 root     root            17 Jan 19 22:10 serial-number
drwxr-xr-x    2 root     root             0 Jan 19 22:10 serial@fdd50000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 serial@fe650000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 serial@fe660000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 serial@fe670000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 serial@fe680000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 serial@fe690000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 serial@fe6a0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 serial@fe6b0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 serial@fe6c0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 serial@fe6d0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 spdif@fe460000
drwxr-xr-x    3 root     root             0 Jan 19 22:10 spi@fe300000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 spi@fe610000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 spi@fe620000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 spi@fe630000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 spi@fe640000
drwxr-xr-x    3 root     root             0 Jan 19 22:10 sram@10f000
drwxr-xr-x    3 root     root             0 Jan 19 22:10 syscon@fdc20000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 syscon@fdc50000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 syscon@fdc60000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 syscon@fdc70000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 syscon@fdc80000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 syscon@fdc90000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 syscon@fdca0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 syscon@fdca8000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 syscon@fdcb8000
drwxr-xr-x    4 root     root             0 Jan 19 22:10 thermal-zones
drwxr-xr-x    2 root     root             0 Jan 19 22:10 timer
drwxr-xr-x    2 root     root             0 Jan 19 22:10 tsadc@fe710000
drwxr-xr-x    4 root     root             0 Jan 19 22:10 usb2phy@fe8a0000
drwxr-xr-x    4 root     root             0 Jan 19 22:10 usb2phy@fe8b0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 usb@fcc00000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 usb@fd000000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 usb@fd800000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 usb@fd840000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 usb@fd880000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 usb@fd8c0000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 vcc3v3-pcie-regulator
drwxr-xr-x    2 root     root             0 Jan 19 22:10 vcc3v3-sys-regulator
drwxr-xr-x    2 root     root             0 Jan 19 22:10 vcc5v0-sys-regulator
drwxr-xr-x    2 root     root             0 Jan 19 22:10 vcc5v0-usb-host-regulator
drwxr-xr-x    2 root     root             0 Jan 19 22:10 vcc5v0-usb-otg-regulator
drwxr-xr-x    2 root     root             0 Jan 19 22:10 video-codec@fdea0400
drwxr-xr-x    2 root     root             0 Jan 19 22:10 video-codec@fdee0000
drwxr-xr-x    3 root     root             0 Jan 19 22:10 vop@fe040000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 watchdog@fe600000
drwxr-xr-x    2 root     root             0 Jan 19 22:10 xin24m
drwxr-xr-x    2 root     root             0 Jan 19 22:10 xin32k
# uname -a
Linux homeassistant-video 6.1.71-haos #1 SMP PREEMPT Tue Jan  9 11:20:58 UTC 2024 aarch64 HAOS
# ls -al /dev/dri/
total 0
drwxr-xr-x    3 root     root           120 Apr  4  2023 .
drwxr-xr-x   18 root     root          4740 Apr  4  2023 ..
drwxr-xr-x    2 root     root           100 Jan 19 22:04 by-path
crw-rw----    1 root     video     226,   0 Apr  4  2023 card0
crw-rw----    1 root     video     226,   1 Jan 19 22:04 card1
crw-rw-rw-    1 root     render    226, 128 Apr  4  2023 renderD128
# cat /sys/kernel/debug/rknpu/version
cat: can't open '/sys/kernel/debug/rknpu/version': No such file or directory

[MarcA711]

@nyok92 Yes, this confirms what I said earlier: The rknn-toolkit-lite2 requires the device-tree at /proc/device-tree/. The rknn-toolkit-lite2 is closed source, so that can't be changed. We need to find a way to make HomeAssistant mount the device tree at /proc/device-tree/.

And no, you don't need to install Rknn toolkit2 & MP / RKMPP on host.

[MarcA711]

@nyok92 Moreover, you are using the mainline linux kernel. It does not include the necessary drivers for hardware video decoding or the NPU. So, it wouldn't work on your system even if this mounting issue in the Addon would be fixed. You have two options to enable your hardware:

• Use the rockchip BSP kernel. I recommend this distro, it includes all drivers and works stable.
• The rknpu driver is open source, you could try to compile the mainline kernel including the driver. However, I have not tried this and don't know if it works. Moreover, your hardware video decoding would still not work, I don't know if it can be added to the mainline kernel.

[MarcA711]

@mcarbonneaux yes, the driver in not included in HAOS.

Since HomeAssistant says that they don't plan to include the NPU driver for now, we can close this issue until the rknpu driver finds its way to mainline linux. Currently, I haven't seen any efforts to mainline the npu driver, but collabora works on enabling hardware decoding. This means that hardware video acceleration and npu won't work on HAOS for now.

@NickM-27 This means the frigate rockchip addon has no advantage over the normal frigate addon. The only way to use HomeAssistant and frigate-rockchip on one device is using Home Assistant Container currently.

[YuryMcv]

sudo ls -al /sys/firmware/devicetree/base uname -a sudo ls -al /dev/dri/ sudo cat /sys/kernel/debug/rknpu/version

Home Assistant
Core    2024.1.4
Supervisor   2023.12.2.dev2902

Orange Pi 5 1.1.8 Bookworm with Linux 5.10.160-rockchip-rk3588

root@hass:~ ls -al /sys/firmware/devicetree/base
total 0
drwxr-xr-x 337 root root  0 Jan 20 13:34  .
drwxr-xr-x   3 root root  0 Jan 20 13:34  ..
drwxr-xr-x   6 root root  0 Jan 20 13:34  adc-keys
-r--r--r--   1 root root  4 Jan 20 13:40 '#address-cells'
drwxr-xr-x   2 root root  0 Jan 20 13:34  aliases
drwxr-xr-x   2 root root  0 Jan 20 13:34  arm-pmu
drwxr-xr-x   2 root root  0 Jan 20 13:34  av1d@fdc70000
drwxr-xr-x   2 root root  0 Jan 20 13:34  avsd-plus@fdb51000
drwxr-xr-x   2 root root  0 Jan 20 13:34  backlight
drwxr-xr-x   2 root root  0 Jan 20 13:34  backlight_1
drwxr-xr-x   2 root root  0 Jan 20 13:34  can@fea50000
drwxr-xr-x   2 root root  0 Jan 20 13:34  can@fea60000
drwxr-xr-x   2 root root  0 Jan 20 13:34  can@fea70000
drwxr-xr-x   2 root root  0 Jan 20 13:34  chosen
drwxr-xr-x   2 root root  0 Jan 20 13:34  clock-controller@fd7c0000
drwxr-xr-x  35 root root  0 Jan 20 13:34  clocks
drwxr-xr-x  11 root root  0 Jan 20 13:34  cluster0-opp-table
drwxr-xr-x  16 root root  0 Jan 20 13:34  cluster1-opp-table
drwxr-xr-x  16 root root  0 Jan 20 13:34  cluster2-opp-table
drwxr-xr-x   2 root root  0 Jan 20 13:34  codec-digital@fe500000
drwxr-xr-x   2 root root  0 Jan 20 13:34  combophy-avdd0v85
drwxr-xr-x   2 root root  0 Jan 20 13:34  combophy-avdd1v8
-r--r--r--   1 root root 44 Jan 20 13:34  compatible
drwxr-xr-x   2 root root  0 Jan 20 13:34  cpuinfo
drwxr-xr-x  21 root root  0 Jan 20 13:34  cpus
drwxr-xr-x   2 root root  0 Jan 20 13:34  crypto@fe370000
drwxr-xr-x   3 root root  0 Jan 20 13:34  csi2-dcphy0
drwxr-xr-x   3 root root  0 Jan 20 13:34  csi2-dcphy1
drwxr-xr-x   3 root root  0 Jan 20 13:34  csi2-dphy0
drwxr-xr-x   2 root root  0 Jan 20 13:34  csi2-dphy0-hw@fedc0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  csi2-dphy1
drwxr-xr-x   2 root root  0 Jan 20 13:34  csi2-dphy2
drwxr-xr-x   2 root root  0 Jan 20 13:34  cspmu@fd10c000
drwxr-xr-x   2 root root  0 Jan 20 13:34  debug@fd104000
drwxr-xr-x   2 root root  0 Jan 20 13:34  decompress@fea80000
drwxr-xr-x   2 root root  0 Jan 20 13:34  dfi@fe060000
drwxr-xr-x   3 root root  0 Jan 20 13:34  display-subsystem
drwxr-xr-x   2 root root  0 Jan 20 13:34  dma-controller@fea10000
drwxr-xr-x   2 root root  0 Jan 20 13:34  dma-controller@fea30000
drwxr-xr-x   2 root root  0 Jan 20 13:34  dma-controller@fed10000
drwxr-xr-x   2 root root  0 Jan 20 13:34  dmc
drwxr-xr-x   6 root root  0 Jan 20 13:34  dmc-opp-table
drwxr-xr-x   2 root root  0 Jan 20 13:34  dp0-sound
drwxr-xr-x   3 root root  0 Jan 20 13:34  dp@fde50000
drwxr-xr-x   4 root root  0 Jan 20 13:34  dsi@fde20000
drwxr-xr-x   4 root root  0 Jan 20 13:34  dsi@fde30000
drwxr-xr-x   3 root root  0 Jan 20 13:34  edp@fdec0000
drwxr-xr-x   3 root root  0 Jan 20 13:34  es8388-sound
drwxr-xr-x   6 root root  0 Jan 20 13:34  ethernet@fe1c0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  fiq-debugger
drwxr-xr-x   5 root root  0 Jan 20 13:34  firmware
drwxr-xr-x   3 root root  0 Jan 20 13:34  gpio-leds
drwxr-xr-x   2 root root  0 Jan 20 13:34  gpu@fb000000
drwxr-xr-x  10 root root  0 Jan 20 13:34  gpu-opp-table
drwxr-xr-x   2 root root  0 Jan 20 13:34  hdcp@fde40000
drwxr-xr-x   2 root root  0 Jan 20 13:34  hdcp@fde70000
drwxr-xr-x   2 root root  0 Jan 20 13:34  hdmi0-sound
drwxr-xr-x   3 root root  0 Jan 20 13:34  hdmi@fde80000
drwxr-xr-x   3 root root  0 Jan 20 13:34  hdmiphy@fed60000
drwxr-xr-x   2 root root  0 Jan 20 13:34  hwspinlock@fe5a0000
drwxr-xr-x   4 root root  0 Jan 20 13:34  i2c@fd880000
drwxr-xr-x   2 root root  0 Jan 20 13:34  i2c@fea90000
drwxr-xr-x   8 root root  0 Jan 20 13:34  i2c@feaa0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  i2c@feab0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  i2c@feac0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  i2c@fead0000
drwxr-xr-x   5 root root  0 Jan 20 13:34  i2c@fec80000
drwxr-xr-x  11 root root  0 Jan 20 13:34  i2c@fec90000
drwxr-xr-x   2 root root  0 Jan 20 13:34  i2c@feca0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  i2s@fddc0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  i2s@fddf0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  i2s@fddfc000
drwxr-xr-x   2 root root  0 Jan 20 13:34  i2s@fe470000
drwxr-xr-x   2 root root  0 Jan 20 13:34  i2s@fe480000
drwxr-xr-x   2 root root  0 Jan 20 13:34  i2s@fe490000
drwxr-xr-x   2 root root  0 Jan 20 13:34  i2s@fe4a0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  iep@fdbb0000
drwxr-xr-x   4 root root  0 Jan 20 13:34  interrupt-controller@fe600000
-r--r--r--   1 root root  4 Jan 20 13:40  interrupt-parent
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fc900000
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fcb00000
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdab9000
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdb50800
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdb60f00
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdb70f00
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdb90480
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdba0800
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdba4800
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdba8800
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdbac800
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdbb0800
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdbdf000
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdbef000
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdc38700
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdc48700
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdca0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdcb7f00
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdcc7f00
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdcd0f00
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdcd8f00
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdce0800
drwxr-xr-x   2 root root  0 Jan 20 13:34  iommu@fdd97e00
drwxr-xr-x   2 root root  0 Jan 20 13:34  jpegd@fdb90000
drwxr-xr-x   2 root root  0 Jan 20 13:34  jpege-ccu
drwxr-xr-x   2 root root  0 Jan 20 13:34  jpege-core@fdba0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  jpege-core@fdba4000
drwxr-xr-x   2 root root  0 Jan 20 13:34  jpege-core@fdba8000
drwxr-xr-x   2 root root  0 Jan 20 13:34  jpege-core@fdbac000
drwxr-xr-x   2 root root  0 Jan 20 13:34  mailbox@fec60000
drwxr-xr-x   2 root root  0 Jan 20 13:34  mailbox@fec70000
drwxr-xr-x   2 root root  0 Jan 20 13:34  mailbox@fece0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  memory
drwxr-xr-x   3 root root  0 Jan 20 13:34  mipi0-csi2@fdd10000
drwxr-xr-x   3 root root  0 Jan 20 13:34  mipi1-csi2@fdd20000
drwxr-xr-x   3 root root  0 Jan 20 13:34  mipi2-csi2@fdd30000
drwxr-xr-x   2 root root  0 Jan 20 13:34  mipi3-csi2@fdd40000
drwxr-xr-x   2 root root  0 Jan 20 13:34  mmc@fe2c0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  mmc@fe2d0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  mmc@fe2e0000
-r--r--r--   1 root root 12 Jan 20 13:40  model
drwxr-xr-x   2 root root  0 Jan 20 13:34  mpp-srv
-r--r--r--   1 root root  1 Jan 20 13:40  name
drwxr-xr-x   2 root root  0 Jan 20 13:34  npu@fdab0000
drwxr-xr-x  10 root root  0 Jan 20 13:34  npu-opp-table
drwxr-xr-x  21 root root  0 Jan 20 13:34  otp@fecc0000
drwxr-xr-x   3 root root  0 Jan 20 13:34  pcie@fe180000
drwxr-xr-x   3 root root  0 Jan 20 13:34  pcie@fe190000
drwxr-xr-x   2 root root  0 Jan 20 13:34  pdm@fe4b0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  pdm@fe4c0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  phy@fed60000
drwxr-xr-x   5 root root  0 Jan 20 13:34  phy@fed80000
drwxr-xr-x   2 root root  0 Jan 20 13:34  phy@feda0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  phy@fedb0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  phy@fee00000
drwxr-xr-x   2 root root  0 Jan 20 13:34  phy@fee20000
drwxr-xr-x 146 root root  0 Jan 20 13:34  pinctrl
drwxr-xr-x   3 root root  0 Jan 20 13:34  power-management@fd8d8000
drwxr-xr-x   2 root root  0 Jan 20 13:34  psci
drwxr-xr-x   3 root root  0 Jan 20 13:34  pvtm@fda40000
drwxr-xr-x   3 root root  0 Jan 20 13:34  pvtm@fda50000
drwxr-xr-x   3 root root  0 Jan 20 13:34  pvtm@fda60000
drwxr-xr-x   3 root root  0 Jan 20 13:34  pvtm@fdaf0000
drwxr-xr-x   3 root root  0 Jan 20 13:34  pvtm@fdb30000
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@fd8b0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@fd8b0010
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@fd8b0020
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@fd8b0030
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@febd0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@febd0010
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@febd0020
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@febd0030
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@febe0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@febe0010
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@febe0020
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@febe0030
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@febf0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@febf0010
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@febf0020
drwxr-xr-x   2 root root  0 Jan 20 13:34  pwm@febf0030
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf35000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf35200
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf35400
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf35600
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf36000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf39000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf3d800
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf3e000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf3e200
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf3e400
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf3e600
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf40000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf40200
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf40400
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf40500
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf40600
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf40800
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf41000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf41100
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf60000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf60200
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf60400
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf61000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf61200
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf61400
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf62000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf63000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf64000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf66000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf66200
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf66400
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf66600
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf66800
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf66a00
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf66c00
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf66e00
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf67000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf67200
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf70000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf71000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf72000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf72200
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf72400
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf80000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf81000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf81200
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf82000
drwxr-xr-x   2 root root  0 Jan 20 13:34  qos@fdf82200
drwxr-xr-x   6 root root  0 Jan 20 13:34  reserved-memory
drwxr-xr-x   2 root root  0 Jan 20 13:34  rga@fdb60000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rga@fdb70000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rga@fdb80000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-dvp
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-dvp-sditf
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif@fdce0000
drwxr-xr-x   3 root root  0 Jan 20 13:34  rkcif-mipi-lvds
drwxr-xr-x   3 root root  0 Jan 20 13:34  rkcif-mipi-lvds1
drwxr-xr-x   3 root root  0 Jan 20 13:34  rkcif-mipi-lvds1-sditf
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds1-sditf-vir1
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds1-sditf-vir2
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds1-sditf-vir3
drwxr-xr-x   3 root root  0 Jan 20 13:34  rkcif-mipi-lvds2
drwxr-xr-x   3 root root  0 Jan 20 13:34  rkcif-mipi-lvds2-sditf
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds2-sditf-vir1
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds2-sditf-vir2
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds2-sditf-vir3
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds3
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds3-sditf
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds3-sditf-vir1
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds3-sditf-vir2
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds3-sditf-vir3
drwxr-xr-x   3 root root  0 Jan 20 13:34  rkcif-mipi-lvds-sditf
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds-sditf-vir1
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds-sditf-vir2
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkcif-mipi-lvds-sditf-vir3
drwxr-xr-x   3 root root  0 Jan 20 13:34  rkisp0-vir0
drwxr-xr-x   3 root root  0 Jan 20 13:34  rkisp0-vir1
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkisp0-vir2
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkisp0-vir3
drwxr-xr-x   3 root root  0 Jan 20 13:34  rkisp1-vir0
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkisp1-vir1
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkisp1-vir2
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkisp1-vir3
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkisp@fdcb0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkisp@fdcc0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkispp0-vir0
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkispp1-vir0
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkispp@fdcd0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkispp@fdcd8000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkisp-unite@fdcb0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkisp-unite-mmu@fdcb7f00
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkvdec-ccu@fdc30000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkvdec-core@fdc38000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkvdec-core@fdc48000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkvenc-ccu
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkvenc-core@fdbd0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rkvenc-core@fdbe0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rng@fe378000
drwxr-xr-x   2 root root  0 Jan 20 13:34  rockchip-suspend
drwxr-xr-x   2 root root  0 Jan 20 13:34  rockchip-system-monitor
drwxr-xr-x   2 root root  0 Jan 20 13:34  saradc@fec10000
drwxr-xr-x   2 root root  0 Jan 20 13:34  sata@fe210000
drwxr-xr-x   2 root root  0 Jan 20 13:34  sata@fe230000
drwxr-xr-x   2 root root  0 Jan 20 13:34  serial@fd890000
drwxr-xr-x   2 root root  0 Jan 20 13:34  serial@feb40000
drwxr-xr-x   2 root root  0 Jan 20 13:34  serial@feb50000
drwxr-xr-x   2 root root  0 Jan 20 13:34  serial@feb60000
drwxr-xr-x   2 root root  0 Jan 20 13:34  serial@feb70000
drwxr-xr-x   2 root root  0 Jan 20 13:34  serial@feb80000
drwxr-xr-x   2 root root  0 Jan 20 13:34  serial@feb90000
drwxr-xr-x   2 root root  0 Jan 20 13:34  serial@feba0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  serial@febb0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  serial@febc0000
-r--r--r--   1 root root  4 Jan 20 13:40 '#size-cells'
drwxr-xr-x   2 root root  0 Jan 20 13:34  spdif-rx@fde08000
drwxr-xr-x   2 root root  0 Jan 20 13:34  spdif-tx1-dc
drwxr-xr-x   4 root root  0 Jan 20 13:34  spdif-tx1-sound
drwxr-xr-x   2 root root  0 Jan 20 13:34  spdif-tx@fddb0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  spdif-tx@fdde0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  spdif-tx@fe4e0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  spdif-tx@fe4f0000
drwxr-xr-x   3 root root  0 Jan 20 13:34  spi@fe2b0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  spi@feb00000
drwxr-xr-x   2 root root  0 Jan 20 13:34  spi@feb10000
drwxr-xr-x   3 root root  0 Jan 20 13:34  spi@feb20000
drwxr-xr-x   2 root root  0 Jan 20 13:34  spi@feb30000
drwxr-xr-x   3 root root  0 Jan 20 13:34  spi@fecb0000
drwxr-xr-x   3 root root  0 Jan 20 13:34  sram@10f000
drwxr-xr-x   4 root root  0 Jan 20 13:34  sram@ff001000
drwxr-xr-x   2 root root  0 Jan 20 13:34  __symbols__
drwxr-xr-x   3 root root  0 Jan 20 13:34  syscon@fd588000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd58a000
drwxr-xr-x   3 root root  0 Jan 20 13:34  syscon@fd58c000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd590000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd592000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd594000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd598000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5a0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5a2000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5a4000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5a6000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5a8000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5ac000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5b0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5b4000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5b5000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5bc000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5c4000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5c8000
drwxr-xr-x   3 root root  0 Jan 20 13:34  syscon@fd5d0000
drwxr-xr-x   3 root root  0 Jan 20 13:34  syscon@fd5d8000
drwxr-xr-x   3 root root  0 Jan 20 13:34  syscon@fd5dc000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5e0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5e8000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5ec000
drwxr-xr-x   2 root root  0 Jan 20 13:34  syscon@fd5f0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  test-power
drwxr-xr-x   9 root root  0 Jan 20 13:34  thermal-zones
drwxr-xr-x   2 root root  0 Jan 20 13:34  timer
drwxr-xr-x   2 root root  0 Jan 20 13:34  timer@feae0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  tsadc@fec00000
drwxr-xr-x   2 root root  0 Jan 20 13:34  uio@fe1c0000
drwxr-xr-x   3 root root  0 Jan 20 13:34  usbdrd3_0
drwxr-xr-x   2 root root  0 Jan 20 13:34  usb@fc800000
drwxr-xr-x   2 root root  0 Jan 20 13:34  usb@fc840000
drwxr-xr-x   2 root root  0 Jan 20 13:34  usb@fc880000
drwxr-xr-x   2 root root  0 Jan 20 13:34  usb@fc8c0000
drwxr-xr-x   3 root root  0 Jan 20 13:34  usbhost3_0
drwxr-xr-x   2 root root  0 Jan 20 13:34  vad@fe4d0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  vbus5v0-typec
drwxr-xr-x   2 root root  0 Jan 20 13:34  vcc12v-dcin
drwxr-xr-x   2 root root  0 Jan 20 13:34  vcc-1v1-nldo-s3
drwxr-xr-x   2 root root  0 Jan 20 13:34  vcc3v3-pcie2x1l2
drwxr-xr-x   3 root root  0 Jan 20 13:34  vcc-3v3-sd-s0
drwxr-xr-x   2 root root  0 Jan 20 13:34  vcc5v0-sys
drwxr-xr-x   2 root root  0 Jan 20 13:34  vcc5v0-usb
drwxr-xr-x   2 root root  0 Jan 20 13:34  vcc5v0-usbdcin
drwxr-xr-x   2 root root  0 Jan 20 13:34  vdpu@fdb50400
drwxr-xr-x   3 root root  0 Jan 20 13:34  venc-opp-table
drwxr-xr-x   2 root root  0 Jan 20 13:34  vepu@fdb50000
drwxr-xr-x   3 root root  0 Jan 20 13:34  vop@fdd90000
drwxr-xr-x   2 root root  0 Jan 20 13:34  watchdog@feaf0000
drwxr-xr-x   2 root root  0 Jan 20 13:34  wireless-bluetooth
drwxr-xr-x   2 root root  0 Jan 20 13:34  wireless-wlan
root@hass:~ uname -a
Linux hass 5.10.160-rockchip-rk3588 #1.1.8 SMP Mon Nov 13 11:11:04 CST 2023 aarc                              h64 GNU/Linux
root@hass:~ ls -al /dev/dri/
total 0
drwxr-xr-x   2 root root        120 Jan 20 13:34 .
drwxr-xr-x  18 root root       3700 Jan 20 13:34 ..
crw-rw----+  1 root video  226,   0 Jan 20 13:34 card0
crw-rw----+  1 root video  226,   1 Jan 20 13:34 card1
crw-rw----+  1 root render 226, 128 Jan 20 13:34 renderD128
crw-rw----+  1 root render 226, 129 Jan 20 13:34 renderD129
root@hass:~ cat /sys/kernel/debug/rknpu/version
RKNPU driver: v0.8.8
root@hass:~ 

[YuryMcv]

s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service frigate-log successfully started
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
2024-01-20 19:55:37.118803737  [INFO] Preparing Frigate...
2024-01-20 19:55:37.120275168  [INFO] Starting NGINX...
s6-rc: info: service legacy-services successfully started
2024-01-20 19:55:37.152171842  [INFO] Preparing new go2rtc config...
2024-01-20 19:55:37.165389353  [INFO] Starting Frigate...
2024-01-20 19:55:37.227173736  [INFO] Got IP address from supervisor: 192.168.1.172
2024-01-20 19:55:37.303396817  [INFO] Got WebRTC port from supervisor: 8555
2024-01-20 19:55:37.324739723  2024/01/20 22:55:37 [error] 144#144: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001stats", host: "local-frigate-rk-beta:5000"
2024-01-20 19:55:37.935311563  [INFO] Starting go2rtc...
2024-01-20 19:55:38.052510736  22:55:38.052 INF go2rtc version 1.8.4 linux/arm64
2024-01-20 19:55:38.053432970  22:55:38.053 INF [rtsp] listen addr=:8554
2024-01-20 19:55:38.053784130  22:55:38.053 INF [webrtc] listen addr=:8555
2024-01-20 19:55:38.053794046  22:55:38.053 INF [api] listen addr=:1984
2024-01-20 19:55:39.703226735  [2024-01-20 22:55:39] frigate.app                    INFO    : Starting Frigate (0.13.0-c18beb9)
2024-01-20 19:55:39.703635353  [2024-01-20 22:55:39] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-01-20 19:55:39.736743004  [2024-01-20 22:55:39] peewee_migrate.logs            INFO    : Starting migrations
2024-01-20 19:55:39.757610794  [2024-01-20 22:55:39] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-01-20 19:55:39.759034101  [2024-01-20 22:55:39] frigate.app                    INFO    : Recording process started: 463
2024-01-20 19:55:39.764132634  [2024-01-20 22:55:39] frigate.app                    INFO    : go2rtc process pid: 88
2024-01-20 19:55:39.822295750  [2024-01-20 22:55:39] detector.rknn                  INFO    : Starting detection process: 473
2024-01-20 19:55:39.825432860  [2024-01-20 22:55:39] frigate.app                    INFO    : Output process started: 475
2024-01-20 19:55:39.864202242  [2024-01-20 22:55:39] frigate.app                    INFO    : Camera processor started for cam_1: 480
2024-01-20 19:55:39.886545838  [2024-01-20 22:55:39] frigate.app                    INFO    : Capture process started for cam_1: 482
2024-01-20 19:55:40.228252246  **************************************************
2024-01-20 19:55:40.228501908  !!! It is detected that some necessary files are missing in the container.
2024-01-20 19:55:40.228701988  !!! When starting the container, please use the -v parameter to map the corresponding files in the host to the container.
2024-01-20 19:55:40.228873776  The reference parameters of run container are as follows:
2024-01-20 19:55:40.229023982      -v /dev/dri/renderD129:/dev/dri/renderD129
2024-01-20 19:55:40.229167479      -v /proc/device-tree/compatible:/proc/device-tree/compatible
2024-01-20 19:55:40.229361726  **************************************************
2024-01-20 19:55:40.229751094  E Catch exception when init runtime!
2024-01-20 19:55:40.231009904  E Traceback (most recent call last):
2024-01-20 19:55:40.231013113    File "/usr/local/lib/python3.9/dist-packages/rknnlite/api/rknn_lite.py", line 140, in init_runtime
2024-01-20 19:55:40.231022154      self.rknn_runtime = RKNNRuntime(root_dir=self.root_dir, target=target, device_id=device_id,
2024-01-20 19:55:40.231024196    File "rknnlite/api/rknn_runtime.py", line 305, in rknnlite.api.rknn_runtime.RKNNRuntime.__init__
2024-01-20 19:55:40.231025946    File "rknnlite/api/rknn_runtime.py", line 346, in rknnlite.api.rknn_runtime.RKNNRuntime._check_container
2024-01-20 19:55:40.231051612  RuntimeError
2024-01-20 19:55:40.231052487  
2024-01-20 19:55:40.233070200  [2024-01-20 22:55:40] frigate.detectors.plugins.rknn E       : Error initializing rknn runtime. Do you run docker in privileged mode?
2024-01-20 19:55:41.866995753  [2024-01-20 22:55:41] frigate.video                  ERROR   : cam_1: Unable to read frames from ffmpeg process.
2024-01-20 19:55:41.870624604  [2024-01-20 22:55:41] frigate.video                  ERROR   : cam_1: ffmpeg process is not running. exiting capture thread...
2024-01-20 19:55:47.124820475  [INFO] Starting go2rtc healthcheck service...

[YuryMcv]

The detector is working. The whole problem is that the addon does not launch the container in unprivileged mode. When running from the terminal everything works .

root@hass:~# docker run --privileged -it --rm --publish=5000:5000 -v /usr/share/hassio/addons/local/frigate-rockchipOpi5-dev/config:/config 4d2760446cbd

s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service frigate-log successfully started
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
2024-01-22 17:06:50.832143143  [INFO] Preparing Frigate...
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
2024-01-22 17:06:50.846688315  [INFO] Starting NGINX...
s6-rc: info: service legacy-services successfully started
2024-01-22 17:06:50.862705503  [INFO] Preparing new go2rtc config...
2024-01-22 17:06:50.880131417  [INFO] Starting Frigate...
2024-01-22 17:06:51.445893374  [INFO] Starting go2rtc...
2024-01-22 17:06:51.563266810  17:06:51.563 INF go2rtc version 1.8.4 linux/arm64
2024-01-22 17:06:51.564181170  17:06:51.563 INF [rtsp] listen addr=:8554
2024-01-22 17:06:51.565869891  17:06:51.563 INF [api] listen addr=:1984
2024-01-22 17:06:51.565893808  17:06:51.564 INF [webrtc] listen addr=:8555
2024-01-22 17:06:53.309434855  [2024-01-22 17:06:53] frigate.app                    INFO    : Starting Frigate (0.13.0-fdecad4)
2024-01-22 17:06:53.309613935  [2024-01-22 17:06:53] frigate.app                    INFO    : Creating directory: /media/frigate/recordings
2024-01-22 17:06:53.309941471  [2024-01-22 17:06:53] frigate.app                    INFO    : Creating directory: /media/frigate/clips
2024-01-22 17:06:53.310077969  [2024-01-22 17:06:53] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-01-22 17:06:53.310366131  [2024-01-22 17:06:53] frigate.app                    INFO    : Creating directory: /media/frigate/exports
2024-01-22 17:06:53.343948647  [2024-01-22 17:06:53] peewee_migrate.logs            INFO    : Starting migrations
2024-01-22 17:06:53.352927746  [2024-01-22 17:06:53] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-01-22 17:06:53.386977505  [2024-01-22 17:06:53] frigate.app                    INFO    : Recording process started: 455
2024-01-22 17:06:53.390975021  [2024-01-22 17:06:53] frigate.app                    INFO    : go2rtc process pid: 89
2024-01-22 17:06:53.402213623  2024/01/22 17:06:53 [error] 147#147: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.186, server: , request: "GET /api/config/schema.json HTTP/1.1", upstream: "http://127.0.0.1:5001/config/schema.json", host: "192.168.1.172:5000", referrer: "http://192.168.1.172:5000/assets/yaml.worker.bundle.js"
2024-01-22 17:06:53.402226164  192.168.1.186 - - [22/Jan/2024:17:06:53 +0000] "GET /api/config/schema.json HTTP/1.1" 502 559 "http://192.168.1.172:5000/assets/yaml.worker.bundle.js" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" "-"
2024-01-22 17:06:53.447040283  [2024-01-22 17:06:53] detector.rknn                  INFO    : Starting detection process: 465
2024-01-22 17:06:53.460331018  [2024-01-22 17:06:53] frigate.app                    INFO    : Output process started: 467
2024-01-22 17:06:53.524263856  [2024-01-22 17:06:53] frigate.app                    INFO    : Camera processor started for cam_1: 473
2024-01-22 17:06:53.541149321  [2024-01-22 17:06:53] frigate.app                    INFO    : Capture process started for cam_1: 474
2024-01-22 17:06:53.884779941  I RKNN: [17:06:53.884] RKNN Runtime Information: librknnrt version: 1.5.2 (c6b7b351a@2023-08-23T15:28:22)
2024-01-22 17:06:53.885092311  I RKNN: [17:06:53.884] RKNN Driver Information: version: 0.8.8
2024-01-22 17:06:53.885622843  I RKNN: [17:06:53.885] RKNN Model Information: version: 6, toolkit version: 1.5.2+b642f30c(compiler version: 1.5.2 (c6b7b351a@2023-08-23T07:39:01)), target: RKNPU v2, target platform: rk3588, framework name: ONNX, framework layout: NCHW, model inference type: static_shape
mpp[485]: mpp_info: mpp version: 1844ec5 author: MarcA711       2023-11-12 add -lstdc++ to Libs.private

2024-01-22 17:07:00.837346243  [INFO] Starting go2rtc healthcheck service... 

2024-01-22 17:06:50.832143143  [INFO] Preparing Frigate...
2024-01-22 17:06:50.880131417  [INFO] Starting Frigate...
2024-01-22 17:06:53.309434855  [2024-01-22 17:06:53] frigate.app                    INFO    : Starting Frigate (0.13.0-fdecad4)
2024-01-22 17:06:53.309613935  [2024-01-22 17:06:53] frigate.app                    INFO    : Creating directory: /media/frigate/recordings
2024-01-22 17:06:53.309941471  [2024-01-22 17:06:53] frigate.app                    INFO    : Creating directory: /media/frigate/clips
2024-01-22 17:06:53.310077969  [2024-01-22 17:06:53] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-01-22 17:06:53.310366131  [2024-01-22 17:06:53] frigate.app                    INFO    : Creating directory: /media/frigate/exports
2024-01-22 17:06:53.343948647  [2024-01-22 17:06:53] peewee_migrate.logs            INFO    : Starting migrations
2024-01-22 17:06:53.352927746  [2024-01-22 17:06:53] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-01-22 17:06:53.386977505  [2024-01-22 17:06:53] frigate.app                    INFO    : Recording process started: 455
2024-01-22 17:06:53.390975021  [2024-01-22 17:06:53] frigate.app                    INFO    : go2rtc process pid: 89
2024-01-22 17:06:53.447040283  [2024-01-22 17:06:53] detector.rknn                  INFO    : Starting detection process: 465
2024-01-22 17:06:53.460331018  [2024-01-22 17:06:53] frigate.app                    INFO    : Output process started: 467
2024-01-22 17:06:53.524263856  [2024-01-22 17:06:53] frigate.app                    INFO    : Camera processor started for cam_1: 473
2024-01-22 17:06:53.541149321  [2024-01-22 17:06:53] frigate.app                    INFO    : Capture process started for cam_1: 474
2024-01-22 17:06:53.884779941  I RKNN: [17:06:53.884] RKNN Runtime Information: librknnrt version: 1.5.2 (c6b7b351a@2023-08-23T15:28:22)
2024-01-22 17:06:53.885092311  I RKNN: [17:06:53.884] RKNN Driver Information: version: 0.8.8
2024-01-22 17:06:53.885622843  I RKNN: [17:06:53.885] RKNN Model Information: version: 6, toolkit version: 1.5.2+b642f30c(compiler version: 1.5.2 (c6b7b351a@2023-08-23T07:39:01)), target: RKNPU v2, target platform: rk3588, framework name: ONNX, framework layout: NCHW, model inference type: static_shape 

[MarcA711]

Hey @YuryMcv,

Thank you for all the output that you provided.

You are right, we can develop a frigate-rockchip addon. This will not work on HAOS, but when using a supervised install with the proper kernel.

I will open an issue in the HA repo and will ask, if they can add an option to allow changing the device-tree mount path. I think running the addon in unprivileged mode is not necessary. In your case it works when using unprivileged mode, because this allows the container to access /proc/device-tree/compatible from the host directly.