Jump to content

Docker support for RK322X TV Boxes


MattWestB

Recommended Posts

In Ubuntu 22.04 is Docker / Portiner broken then missing handles is disabled in the kernel # CONFIG_BPF_SYSCALL is not set.

docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: bpf_prog_query(BPF_CGROUP_DEVICE) failed: function not implemented: unknown.

 

Edit: It can also being problems with docker is using CGroupsV2 and that is not supported in all installations and need patching the system for using V1.

Link to comment
Share on other sites

Running dockers install testing script bash ./check-config.sh and getting:

root@rk322x-box:~# bash ./check-config.sh
warning: /proc/config.gz does not exist, searching other paths for kernel config ...
info: reading kernel config from /boot/config-5.15.25-rk322x ...

Generally Necessary:
- cgroup hierarchy: cgroupv2
  Controllers:
  - cpu: available
  - cpuset: available
  - io: available
  - memory: available
  - pids: available
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: enabled
- CONFIG_CGROUP_FREEZER: enabled
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_CPUSETS: enabled
- CONFIG_MEMCG: enabled
- CONFIG_KEYS: enabled
- CONFIG_VETH: enabled (as module)
- CONFIG_BRIDGE: enabled
- CONFIG_BRIDGE_NETFILTER: enabled (as module)
- CONFIG_IP_NF_FILTER: enabled (as module)
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_IPVS: enabled (as module)
- CONFIG_NETFILTER_XT_MARK: enabled (as module)
- CONFIG_IP_NF_NAT: enabled (as module)
- CONFIG_NF_NAT: enabled (as module)
- CONFIG_POSIX_MQUEUE: enabled
- CONFIG_CGROUP_BPF: missing

Optional Features:
- CONFIG_USER_NS: enabled
- CONFIG_SECCOMP: enabled
- CONFIG_SECCOMP_FILTER: enabled
- CONFIG_CGROUP_PIDS: enabled
- CONFIG_MEMCG_SWAP: enabled
    (cgroup swap accounting is currently enabled)
- CONFIG_BLK_CGROUP: enabled
- CONFIG_BLK_DEV_THROTTLING: enabled
- CONFIG_CGROUP_PERF: enabled
- CONFIG_CGROUP_HUGETLB: missing
- CONFIG_NET_CLS_CGROUP: enabled (as module)
- CONFIG_CGROUP_NET_PRIO: enabled
- CONFIG_CFS_BANDWIDTH: enabled
- CONFIG_FAIR_GROUP_SCHED: enabled
- CONFIG_RT_GROUP_SCHED: enabled
- CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module)
- CONFIG_IP_VS: enabled (as module)
- CONFIG_IP_VS_NFCT: enabled
- CONFIG_IP_VS_PROTO_TCP: enabled
- CONFIG_IP_VS_PROTO_UDP: enabled
- CONFIG_IP_VS_RR: enabled (as module)
- CONFIG_SECURITY_SELINUX: missing
- CONFIG_SECURITY_APPARMOR: missing
- CONFIG_EXT3_FS: enabled
- CONFIG_EXT3_FS_XATTR: missing
- CONFIG_EXT3_FS_POSIX_ACL: enabled
- CONFIG_EXT3_FS_SECURITY: enabled
    (enable these ext3 configs if you are using ext3 as backing filesystem)
- CONFIG_EXT4_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: enabled
- Network Drivers:
  - "overlay":
    - CONFIG_VXLAN: enabled (as module)
    - CONFIG_BRIDGE_VLAN_FILTERING: enabled
      Optional (for encrypted networks):
      - CONFIG_CRYPTO: enabled
      - CONFIG_CRYPTO_AEAD: enabled
      - CONFIG_CRYPTO_GCM: enabled
      - CONFIG_CRYPTO_SEQIV: enabled
      - CONFIG_CRYPTO_GHASH: enabled
      - CONFIG_XFRM: enabled
      - CONFIG_XFRM_USER: enabled (as module)
      - CONFIG_XFRM_ALGO: enabled (as module)
      - CONFIG_INET_ESP: enabled (as module)
  - "ipvlan":
    - CONFIG_IPVLAN: enabled (as module)
  - "macvlan":
    - CONFIG_MACVLAN: enabled (as module)
    - CONFIG_DUMMY: enabled
  - "ftp,tftp client in container":
    - CONFIG_NF_NAT_FTP: enabled (as module)
    - CONFIG_NF_CONNTRACK_FTP: enabled (as module)
    - CONFIG_NF_NAT_TFTP: enabled (as module)
    - CONFIG_NF_CONNTRACK_TFTP: enabled (as module)
- Storage Drivers:
  - "aufs":
    - CONFIG_AUFS_FS: missing
  - "btrfs":
    - CONFIG_BTRFS_FS: enabled
    - CONFIG_BTRFS_FS_POSIX_ACL: enabled
  - "devicemapper":
    - CONFIG_BLK_DEV_DM: enabled
    - CONFIG_DM_THIN_PROVISIONING: enabled
  - "overlay":
    - CONFIG_OVERLAY_FS: enabled (as module)
  - "zfs":
    - /dev/zfs: missing
    - zfs command: missing
    - zpool command: missing

Limits:
- /proc/sys/kernel/keys/root_maxkeys: 1000000

The "zfs" looks not being used in the proviso version but was working OK without it.

But is still little more modules that is missing in the kernel for making docker working OK:-((

Link to comment
Share on other sites

2 hours ago, MattWestB said:

But is still little more modules that is missing in the kernel for making docker working OK:-((

BPF is okay to be enabled for me, which are other modules that are considered blocking to support docker?

Link to comment
Share on other sites

23 hours ago, MattWestB said:

In Ubuntu 22.04 is Docker / Portiner broken then missing handles is disabled in the kernel # CONFIG_BPF_SYSCALL is not set.

docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: bpf_prog_query(BPF_CGROUP_DEVICE) failed: function not implemented: unknown.

 

Edit: It can also being problems with docker is using CGroupsV2 and that is not supported in all installations and need patching the system for using V1.

 

Link to comment
Share on other sites

Very true fedex !!

Also it can being more sub modules BPF that must being enabled if reading post made in some forums.

The Focal was working well also docker was running stable and the 22.04 betas was not stable at all but docker was running on them but its looks like 22.04 GA is up and running for around 2 days and its not crashing so looks great :-)).

 

Have comparing with armbian focal running on one NanoPi with docker running stable and this modules is missing in 22.04 from the docker script is:

 

- CONFIG_CGROUP_BPF: missing
- CONFIG_CGROUP_HUGETLB: missing
- CONFIG_SECURITY_SELINUX: missing
- CONFIG_SECURITY_APPARMOR: missing
- CONFIG_EXT3_FS_XATTR: missing
- Storage Drivers:
  - "aufs":
    - CONFIG_AUFS_FS: missing

 

I think APPARMOR is on must for running Home assistant and many other systems / programs.

The EXT3 can being good for some user but not for my systems.

Also the zfs is in both install not configured but i think (= not knowing) it can being good for not burning the flash so fast so if you think it good enabling it:

 

- Storage Drivers:
  - "zfs":
    - /dev/zfs: missing
    - zfs command: missing
    - zpool command: missing

 

Edit: zfs is normally not supported in Linux kernel and very likely not needed for our devices.

 

Great thanks in for bringing Ubuntu 22.04 for our boxes !!!

Link to comment
Share on other sites

21 hours ago, fedex said:

 

I have the same problem on Armbian_22.05.0-trunk_Rk322x-box_bullseye_current_5.15.25_minimal.img.xz

Is it possible to fix this problem for debian too?
I would like to use the TVBOX to install Home Assistant.
Thank you.

Link to comment
Share on other sites

4 hours ago, fedex said:

I have the same problem on Armbian_22.05.0-trunk_Rk322x-box_bullseye_current_5.15.25_minimal.img.xz

Is it possible to fix this problem for debian too?
I would like to use the TVBOX to install Home Assistant.
Thank you.

Which problem? I see an empty quote there 🧐

Link to comment
Share on other sites

On 4/24/2022 at 11:17 AM, MattWestB said:

In Ubuntu 22.04 is Docker / Portiner broken then missing handles is disabled in the kernel # CONFIG_BPF_SYSCALL is not set.

docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: bpf_prog_query(BPF_CGROUP_DEVICE) failed: function not implemented: unknown.

 

Edit: It can also being problems with docker is using CGroupsV2 and that is not supported in all installations and need patching the system for using V1.

This problem 🙂

Link to comment
Share on other sites

On 4/24/2022 at 11:17 AM, MattWestB said:

In Ubuntu 22.04 is Docker / Portiner broken then missing handles is disabled in the kernel # CONFIG_BPF_SYSCALL is not set.

docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: bpf_prog_query(BPF_CGROUP_DEVICE) failed: function not implemented: unknown.

 

Edit: It can also being problems with docker is using CGroupsV2 and that is not supported in all installations and need patching the system for using V1.

Hello

Is it possible to fix this problem for debian?
Thank you.

Link to comment
Share on other sites

On 4/24/2022 at 11:17 AM, MattWestB said:

In Ubuntu 22.04 is Docker / Portiner broken then missing handles is disabled in the kernel # CONFIG_BPF_SYSCALL is not set.

docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: bpf_prog_query(BPF_CGROUP_DEVICE) failed: function not implemented: unknown.

 

Edit: It can also being problems with docker is using CGroupsV2 and that is not supported in all installations and need patching the system for using V1.

@MattWestB Can I ask you how did you solve it? I am not an expert, I would like to know how I can solve on Debian.
Thank you very much.

Link to comment
Share on other sites

@fedex I was only running the test script and providing the information wot kernel modules that is not configurated in the kernel.

I have one RK3318 and one Nanopi Neo up and running that is having all in place and looks working good with HA with ZHA and OTBR up and running :-))

 

To getting it working you must compiling your own kernel or waiting and hoping @jock is fixing one upgraded kernel for us that is having all modules compelled OK.

 

Link to the docker test script you can finding here: https://docs.docker.com/engine/install/linux-postinstall/#kernel-compatibility

Link to comment
Share on other sites

@MattWestB @fedex Hello, I enabled BPF filters and various other related options.

I built an experimental kernel you can install with dpkg taking packages from here

 

I didn't enable other cgroups options except for the one related to BPF, let me know if docker works for you or still there is the need for something else.

Link to comment
Share on other sites

@jock I was trying installing the updated kernel but it was not working on my RK3228 box then i have focal installed on one USB stick and Jermy on the EMMC but after removing the USB stick and updating the system docker is staring OK and i can installing HA and it running but the fix for audio lock that is burning 400% CPU is not working but i thing its not problem in the host OS more that i is reusing the SC-card for docker data and its some bad written in it then being mounted with other versions.

Shall doing one clean install and reformatting the "internal" SD-card so its no getting old junk in the system and reporting back.

 

So for docker is your test kernel very OK then i have 8 container inclusive portainer and portainer agent running on it :-))

 

Great thanks for fixing the problems and hope more users can getting docker it working on there boxes !!!

 

Mvh  Mattias

Link to comment
Share on other sites

@jock Docker looks working OK buzt i have problem with the sound in HA container that is eating 200% of all CPUs.

Its one fix for it by loading one addon that is tricking the system but its cant being loaded.

My theory is that is appamor that is missing and cant forcing the security for doing the patching.

 

May i request adding appamor module being added in the kernel and in the normal armbian kernels (if the module its compiled armbian is having it disabled by default and need being activated in the kernel comandline for getting it loaded so it shall being safe) ?

 

Thanks in advance !!

Link to comment
Share on other sites

 @fedex Install HA as raspberry pi 2 (= 32 bits) and its not working.

Then do this: 

Quote

To solve this issue comment the lines concerning grub + cgroup in /var/lib/dpkg/info/homeassistant-supervised.postinst.
Then just run apt autoremove and the installation will successfully conclude and stop nagging.

And puls audio is using 200% CPU so set CPU usage to minimum for the HA container and its only using 25% CPU.

Need do the CPU patching after every restart of docker / the system.

Its one addon that fixing the sound problem but its not working in me new Armbian (perhaps its the missing appamor that is doing it).

Link to comment
Share on other sites

@MattWestB This modules is missing:

Optional Features:
- CONFIG_CGROUP_HUGETLB: missing
- CONFIG_SECURITY_SELINUX: missing
- CONFIG_SECURITY_APPARMOR: missing
- CONFIG_EXT3_FS_XATTR: missing
- Storage Drivers:
  - "aufs":
    - CONFIG_AUFS_FS: missing
  - "zfs":
    - /dev/zfs: missing
    - zfs command: missing
    - zpool command: missing

Link to comment
Share on other sites

@fedex My test script is showing the same and i can installing portainer and / or docker agent and its working OK.

What is HA complaining then you is trying installing it ?

Also the CPU is 32 bits so need using installing the "armv7l" version by selecting "raspberrypi2" or its failing.

 

@jock I think we shall not hijacking the thread with no Armbian things and you must saying if we shall stop spamming it with HA problems.

Link to comment
Share on other sites

@jockYour kernel with extra settings looks working OK with docker and i have not have any problems running some (13) containers with it for some weeks !

But Home assistant is needing  APPARMOR being enabled in the kernel (i can installing the packages but its not working then the kernel is not supporting it) and i think it shall not being any problems with other programs doing it then its more or less standard in all Linux "modern" distributions. Also the "standard" armbian is having it enabled (in the Nanopi neo core its enabled and HA is working OK and dont complaining about missing it and is using it).

 

Pleas cooking one updated kernel with apparmor enable for testing then you have time doing one fast patching.

 

Great thanks for your work on our Boxes for getting real OS working great on them !!!

Link to comment
Share on other sites

Hi, I have a RK322a board with eMMC flash memory and I am unable to use any kernel other than the Legacy one. I get boot loops if I install the Bullseye version with the current kernel, or if I update to any newer one from armbian-config (tried various current and edge versions). I was under the impression that only NAND boxes had to use the Legacy kernel. Am I missing something?

 

This is a problem because I am unable to install/start Docker containers because the 4.4 kernel doesn't have support for  cgroup v2; something which Docker apparently needs to work properly. It was introduce in version 4.5 of the kernel. So anything greater or equal to that would work for me.

 

Is there anything I can try to do to get a newer kernel working properly on my eMMC box? Or perhaps someone found a way to get cgroup v2 working with the 4.4 kernel? That would work as well.

 

Thanks in advance and please let me know If I need to provide more information.

 

 

P.S. Unsure if this plays any role in the problem, but AIDA 64 said I had a RK3229, but when I run RK322x-config it says I have a RK3228A/B chip with max freq of 1.2 GHz instead, so I have chosen the RK3228A (max 1.2 Ghz) in rk322x-config as I believe that is more accurate than AIDA 64.

Edited by Bandar
added P.S.
Link to comment
Share on other sites

17 hours ago, Bandar said:

Hi, I have a RK322a board with eMMC flash memory and I am unable to use any kernel other than the Legacy one. I get boot loops if I install the Bullseye version with the current kernel, or if I update to any newer one from armbian-config (tried various current and edge versions). I was under the impression that only NAND boxes had to use the Legacy kernel. Am I missing something?

 

This is a problem because I am unable to install/start Docker containers because the 4.4 kernel doesn't have support for  cgroup v2; something which Docker apparently needs to work properly. It was introduce in version 4.5 of the kernel. So anything greater or equal to that would work for me.

 

Is there anything I can try to do to get a newer kernel working properly on my eMMC box? Or perhaps someone found a way to get cgroup v2 working with the 4.4 kernel? That would work as well.

 

Thanks in advance and please let me know If I need to provide more information.

 

 

P.S. Unsure if this plays any role in the problem, but AIDA 64 said I had a RK3229, but when I run RK322x-config it says I have a RK3228A/B chip with max freq of 1.2 GHz instead, so I have chosen the RK3228A (max 1.2 Ghz) in rk322x-config as I believe that is more accurate than AIDA 64.

 

Hello,

 

Try to run the script in my previous post using legacy kernel 4.4...

 

Docker works fine on my box and here is results from the script:

 

info: reading kernel config from /proc/config.gz ...

Generally Necessary:
- cgroup hierarchy: properly mounted [/sys/fs/cgroup]
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: enabled
- CONFIG_CGROUP_FREEZER: enabled
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_CPUSETS: enabled
- CONFIG_MEMCG: enabled
- CONFIG_KEYS: enabled
- CONFIG_VETH: enabled
- CONFIG_BRIDGE: enabled
- CONFIG_BRIDGE_NETFILTER: enabled
- CONFIG_IP_NF_FILTER: enabled (as module)
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_IPVS: enabled (as module)
- CONFIG_NETFILTER_XT_MARK: enabled
- CONFIG_IP_NF_NAT: enabled (as module)
- CONFIG_NF_NAT: enabled
- CONFIG_POSIX_MQUEUE: enabled
- CONFIG_DEVPTS_MULTIPLE_INSTANCES: enabled
- CONFIG_NF_NAT_IPV4: enabled (as module)
- CONFIG_NF_NAT_NEEDED: enabled

Optional Features:
- CONFIG_USER_NS: enabled
- CONFIG_SECCOMP: enabled
- CONFIG_SECCOMP_FILTER: enabled
- CONFIG_CGROUP_PIDS: enabled
- CONFIG_MEMCG_SWAP: enabled
- CONFIG_MEMCG_SWAP_ENABLED: enabled
    (cgroup swap accounting is currently enabled)
- CONFIG_MEMCG_KMEM: enabled
- CONFIG_IOSCHED_CFQ: enabled
- CONFIG_CFQ_GROUP_IOSCHED: enabled
- CONFIG_BLK_CGROUP: enabled
- CONFIG_BLK_DEV_THROTTLING: enabled
- CONFIG_CGROUP_PERF: enabled
- CONFIG_CGROUP_HUGETLB: missing
- CONFIG_NET_CLS_CGROUP: enabled (as module)
- CONFIG_CGROUP_NET_PRIO: enabled
- CONFIG_CFS_BANDWIDTH: enabled
- CONFIG_FAIR_GROUP_SCHED: enabled
- CONFIG_RT_GROUP_SCHED: enabled
- CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module)
- CONFIG_IP_VS: enabled (as module)
- CONFIG_IP_VS_NFCT: enabled
- CONFIG_IP_VS_PROTO_TCP: enabled
- CONFIG_IP_VS_PROTO_UDP: enabled
- CONFIG_IP_VS_RR: enabled (as module)
- CONFIG_SECURITY_SELINUX: missing
- CONFIG_SECURITY_APPARMOR: missing
- CONFIG_EXT3_FS: enabled
- CONFIG_EXT3_FS_XATTR: missing
- CONFIG_EXT3_FS_POSIX_ACL: enabled
- CONFIG_EXT3_FS_SECURITY: enabled
    (enable these ext3 configs if you are using ext3 as backing filesystem)
- CONFIG_EXT4_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: enabled
- Network Drivers:
  - "overlay":
    - CONFIG_VXLAN: enabled
    - CONFIG_BRIDGE_VLAN_FILTERING: missing
      Optional (for encrypted networks):
      - CONFIG_CRYPTO: enabled
      - CONFIG_CRYPTO_AEAD: enabled
      - CONFIG_CRYPTO_GCM: enabled
      - CONFIG_CRYPTO_SEQIV: enabled
      - CONFIG_CRYPTO_GHASH: enabled
      - CONFIG_XFRM: enabled
      - CONFIG_XFRM_USER: enabled
      - CONFIG_XFRM_ALGO: enabled
      - CONFIG_INET_ESP: enabled
      - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled
  - "ipvlan":
    - CONFIG_IPVLAN: enabled
  - "macvlan":
    - CONFIG_MACVLAN: enabled
    - CONFIG_DUMMY: enabled
  - "ftp,tftp client in container":
    - CONFIG_NF_NAT_FTP: enabled (as module)
    - CONFIG_NF_CONNTRACK_FTP: enabled (as module)
    - CONFIG_NF_NAT_TFTP: enabled (as module)
    - CONFIG_NF_CONNTRACK_TFTP: enabled (as module)
- Storage Drivers:
  - "aufs":
    - CONFIG_AUFS_FS: missing
  - "btrfs":
    - CONFIG_BTRFS_FS: enabled
    - CONFIG_BTRFS_FS_POSIX_ACL: enabled
  - "devicemapper":
    - CONFIG_BLK_DEV_DM: enabled
    - CONFIG_DM_THIN_PROVISIONING: enabled
  - "overlay":
    - CONFIG_OVERLAY_FS: enabled (as module)
  - "zfs":
    - /dev/zfs: missing
    - zfs command: missing
    - zpool command: missing

Limits:
- /proc/sys/kernel/keys/root_maxkeys: 1000000

 

 

Link to comment
Share on other sites

Hello @Bandar, if your system is not stable with mainline kernel, try to append cpu-stability to overlays= line in /boot/armbianEnv.txt. Don't remove the existing entries, just add the new one; note also the if you run rk322x-config, it will remove cpu-stability overlay and you have to add it manually again.

 

You can use the multitool to access the eMMC partition, if you installed armbian in internal flash.

 

Also you can set verbosity=7  to show more kernel details during boot so you can report where the boot process fails.

If you have a serial UART, you can log the kernel boot process as well.

 

It is important that you provide logs and details, otherwise helping is hard

Link to comment
Share on other sites

9 hours ago, jock said:

try to append cpu-stability to overlays= line in /boot/armbianEnv.txt.

...

It is important that you provide logs and details...

 

Thanks for for your answer @jock, I didn't know which logs to include or how to get them, the instructions you provided are helpful. Now, to accomplish the above, would I need to reinstall an image to flash or is there a way to test this from the SD card?

To append cpu-stability, is the separator a space or a comma?

 

-------

 

@primoitt I am very happy to hear that docker works on the Legacy kernel. Was that an "out of the box" installation or did you have to tweak afterwards to get it working? On my first try I installed Docker from softy in armbian-config. This time around I ran the CasaOS script and I think it pulled docker from apt. Both methods resulted in the same issue though.

 

This is the difference between your script output and mine respectively: https://www.diffchecker.com/xo7fdDFO

 

Edited by Bandar
grammar
Link to comment
Share on other sites

8 hours ago, Bandar said:

Now, to accomplish the above, would I need to reinstall an image to flash or is there a way to test this from the SD card?

To append cpu-stability, is the separator a space or a comma?

Just edit that file on the device your armbian installation is living, no matter internal flash or sdcard...

If your installation is on sdcard, you can just plug the sdcard in your computer and modify the file.

If the installation is on your internal flash, you can use the multitool to mount the internal flash and modify the file.

 

The separator is space, just add the line overlays=cpu-stability if there is no overlays= line yet in the file.

Link to comment
Share on other sites

@jock I did what you instructed, I flashed the Bullseye img with current kernel to the SD card and edited /boot/armbianEnv.txt adding cpu-stability and setting verbosity to 7. It still keeps boot looping.

 

I managed to take these two photos of the text that stays long enough in the screen to be seen. First image is right at the start and, the last image is really just about when the box reboots. The last picture doesn't show the last line that is displayed very quickly right before it reboots; it is: [   OK   ]  Found device /dev/ttyS2  The box ten reboots immediately afterwards and the process starts anew.

 

I recorded a video of the process as well in decent quality, though most of what is legible from it is in those pictures. If you'd like, I could upload it somewhere and include the link here. Just let me know.

 

This is the content of the edited armbianEnv.txt file:

Spoiler
verbosity=7
extraargs=coherent_pool=2M
bootlogo=false
overlay_prefix=rk322x 
overlays=cpu-stability
fdtfile=rk322x-box.dtb
rootdev=UUID=31798217-04e3-40f9-8ebe-859ef0732ddf
rootfstype=ext4

 

 

PXL_20220617_165352009.thumb.jpg.8255504892bb45221d951762ce77072a.jpgPXL_20220617_165220669.thumb.jpg.74a8c6667e3aceb7f93f72684d62b3b4.jpg

Edited by Bandar
clarity
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines