jeanrhum

Nice possibilities, have you tried something? What are the requirements to do that (kernel version, patchset...)? ps: a more readable version of your link (even if rst is not too bad): https://www.kernel.org/doc/html/latest/devicetree/overlay-notes.html

Hi, Thanks for this great work. I can confirm that PNY 500GB XLR8 CS3030 M.2 NVMe SSD PCIe Gen3 x4 works well, but not Crucial P1 (250GB). Do you know if there are some plans to integrate others nvme drivers like the Crucial ones?

Nice product! It's a variant of the SOM based on the same SOC: https://www.cnx-software.com/2021/03/25/firefly-unveils-core-3568j-ai-core-rockchip-rk3568-system-on-module-devkit/

I tried something: https://github.com/armbian/dl-router/pull/13

I can try to help on some features to port them (obviously the one concerning device tree), but I don't consider that I'm a bash expert (that was my first real bash script). Moreover, I may be quite busy in the coming weeks...

If you want integrated wifi, several sbc can be used and some others will require an usb wifi dongle. The key For instance, the pineH64-B with 2 or 3GB of ram may do the job quite well and you can add an emmc module: https://www.pine64.org/pine-h64-ver-b/ A similar device is Orange Pi Lite 2. If you want something closer to a tv box, station M1 is also a nice choice even if it is only community supported for now: https://www.firefly.store/goods.php?id=130 If you want a stronger cpu, any of the armbian supported sbc based on rk3399 will answer your needs (check for wifi in case it is not integrated on some boards, eg. rock pi 4A).

Armbian community is not developing wifi drivers. You have to ask it from the manufacturer of this chip or the sbc (tv box?). For the supported wifi chips, you just have to install the armbian firmware (full firmware package using armbian-config). If it is not recognized, it'll be quite difficult to make it working without dev and compiling skills and obviously without the driver binary or source codes.

I didn't check recently, but it seems better than the official install, since at the end you get hassio and not just home-assistant . I'll try it for my net install!

For this software, I prefer to use the docker official installation method with standard linux install over docker: https://www.home-assistant.io/docs/installation/docker/

Depending on your use cases, it depends. I use one tv box with this soc as a home server with an "old" armbian custom build of Balbes150. However, he decided to stop amlogic support in his armbianTV builds. You can try to download an old image from his repo available from this topic :

Using sudo is also a good idea if some resources used by armbianmonitor needs root privileges. If I remember well it solves this issue last time I tried.

On my side I prefer to use debian builds on the current boards I currently run at home (edge-v, station M1, pinh64-b). When I update packages, u-boot and kernel may be upgraded as armbian specific packages so that I'm always up-to-date without having to make a fresh install. Concerning your ubuntu specific package upgrade, I can't answer you, but if you system work as expected...

Station M1 is based on a firefly board quite similar to roc-rk3328-cc. However, the M1 has a different layout with all ports on the left or on the right, and it is enclosed in a metal case used also as a heat sink. The device tree is also different (rk3328-roc-pc instead of rk3328-roc-cc) and by default a smooth android 10 system is installed on emmc. Additionally, the powering of this board is ensured by a 5V USB-C port instead of a micro-usb for the roc-cc. You can find official pictures and specifications here. My M1 has 2GB ram and 16GB emmc but variants with 4GB ram and more emmc storage can be bought. Currently, an armbian CSC image can be downloaded (bullseye or focal) or built using armbian buiding system. I tried several images and all boots fine with almost everything working out of the box for a server use case. Here is the log of armbianmonitor with a buster build from the end of january 2021 with kernel 5.10.9: http://ix.io/2Nol Idle the temperature goes under 40°C in a room where the temperature is about 21°C and the metal case is not warm. Running sbc-bench in this context produces these results: http://ix.io/2NoL The temperature never goes over 61°C without any throttling. Compared to some other rk3328 SBCs, the M1 is cooler and this is mainly due to its metal case. After general configuration with armbian-config, installing openmediavault and docker were as easy as possible, since they are also available through armbian-config in the softy menu. After connecting an usb3 drive, I got an efficient nas system for a personal use. It can also be considered as a home-server while running several additional services thanks to docker (home-assistant, zigbee2mqtt, pyload, etc.). With this use case, the 4 A53 cores and 2 GB of ram are more than enough and all is running smoothly. I also use other similar arm boards and here is my comparison: - an amlogic S912 TV box with 3GB ram and GBit ethernet using armbianTV: 2GB is enough in my case and rk3328 is better supported than s912. Moreover, s912 is not officially supported by armbian, and latest armbianTV images are not compatible. The USB3 port on M1 is also a great improvement over USB2 for s912. TV boxes may also have unrecognized wifi chips whereas M1 has working wifi (and bluetooth ? not tested). - Librecomputer lafrite 1GB: it is officially supported by armbian and it works well. Its main drawbacks compared to M1 is only 1GB, USB2 and only 100MBits ethernet, but it is much cheaper. - Pine64 Pineh64 model B: IMO it is the real competitor to the M1. It has similar features with USB3 and GBE. It is officially supported by armbian and it has a more powerful SoC (Allwinner H6: 1.8Ghz 4xA53 with mali 720 gpu). However, this board is much warmer than M1 since in the same room its temperature is greater than 60°C while idle and throttling may occur on moderate to heavy loads. For moderate use case M1 is enough. What to expect in the future: - We can hope that this SBC becomes quickly officially supported, since the CSC release is already very mature (in my opinion). - The main element that can be missing with mainline kernel for some use cases is the GPU (for desktop use) and VPU, but they are available on 4.4 kernel. Another review of the M1 (using also armbian): https://www.thanassis.space/stationm1.html Official forum: https://www.stationpc.com/forum-60-1.html

Hi, I received this week my M1 obtained from the giveaway . I will try to report regularly the images I'll test, but there is 2 kinds of images: csc armbian and armbianTV images. Which one should be preferred?

Hi Christos, Thanks for reporting this issue too. What is your kernel? I suppose that you tried to decompile from fs, but have you tried to decompile from the dtb in use from /boot/dtb ?

I already use it on x86 like some others tools by the same author/team: fd, hyperfind and ripgrep. Their softwares are developped in rust and provide nice features and performances.

ok, the only problem I face was when using dtc with the fs as input.

Sorry, I don't know how to decompile by hand. With a small script, I tested the packaged dtc with all the dtbs from the boot folders of my edge-v (allwinner, amlogic and rockchip) and got no segfaults. With this board, I have much more warnings when decompiling from fs:

Compiling from https://github.com/dgibson/dtc, I'm able to generate a dts file, but using the one installed from apt I got the following output on my pine64h-b: $ dtc -I fs /sys/firmware/devicetree/base -O dts -o custom.dts custom.dts: Warning (unit_address_vs_reg): /cpu-opp-table/opp@480000000: node has a unit name, but no reg property custom.dts: Warning (unit_address_vs_reg): /cpu-opp-table/opp@1704000000: node has a unit name, but no reg property custom.dts: Warning (unit_address_vs_reg): /cpu-opp-table/opp@720000000: node has a unit name, but no reg property custom.dts: Warning (unit_address_vs_reg): /cpu-opp-table/opp@1080000000: node has a unit name, but no reg property custom.dts: Warning (unit_address_vs_reg): /cpu-opp-table/opp@888000000: node has a unit name, but no reg property custom.dts: Warning (unit_address_vs_reg): /cpu-opp-table/opp@816000000: node has a unit name, but no reg property custom.dts: Warning (unit_address_vs_reg): /cpu-opp-table/opp@1800000000: node has a unit name, but no reg property custom.dts: Warning (unit_address_vs_reg): /cpu-opp-table/opp@1608000000: node has a unit name, but no reg property custom.dts: Warning (unit_address_vs_reg): /cpu-opp-table/opp@1320000000: node has a unit name, but no reg property custom.dts: Warning (unit_address_vs_reg): /cpu-opp-table/opp@1488000000: node has a unit name, but no reg property custom.dts: Warning (unit_address_vs_reg): /memory: node has a reg or ranges property, but no unit name custom.dts: Warning (clocks_property): /wifi_pwrseq:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/phy@5100400:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/phy@5100400:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/gpu@1800000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/gpu@1800000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/mmc@4022000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/mmc@4022000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/hdmi@6000000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/hdmi@6000000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/hdmi@6000000:clocks: cell 4 is not a phandle reference custom.dts: Warning (clocks_property): /soc/hdmi@6000000:clocks: cell 6 is not a phandle reference custom.dts: Warning (clocks_property): /soc/hdmi@6000000:clocks: cell 8 is not a phandle reference custom.dts: Warning (clocks_property): /soc/hdmi@6000000:clocks: cell 10 is not a phandle reference custom.dts: Warning (clocks_property): /soc/clock@7010000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/clock@7010000:clocks: cell 1 is not a phandle reference custom.dts: Warning (clocks_property): /soc/clock@7010000:clocks: cell 3 is not a phandle reference custom.dts: Warning (clocks_property): /soc/clock@7010000:clocks: cell 5 is not a phandle reference custom.dts: Warning (clocks_property): /soc/pinctrl@300b000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/pinctrl@300b000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/pinctrl@300b000:clocks: cell 3 is not a phandle reference custom.dts: Warning (clocks_property): /soc/pwm@300a000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/pwm@300a000:clocks: cell 1 is not a phandle reference custom.dts: Warning (clocks_property): /soc/bus@1000000/mixer@100000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/bus@1000000/mixer@100000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/bus@1000000/clock@0:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/bus@1000000/clock@0:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/i2c@5002800:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/rtc@7000000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/phy@5210000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/lcd-controller@6515000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/lcd-controller@6515000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/spdif@5093000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/spdif@5093000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/usb@5311400:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/usb@5311400:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/mmc@4021000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/mmc@4021000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/usb@5101400:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/usb@5101400:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/clock@3001000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/clock@3001000:clocks: cell 1 is not a phandle reference custom.dts: Warning (clocks_property): /soc/clock@3001000:clocks: cell 3 is not a phandle reference custom.dts: Warning (clocks_property): /soc/video-codec@1c0e000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/video-codec@1c0e000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/video-codec@1c0e000:clocks: cell 4 is not a phandle reference custom.dts: Warning (clocks_property): /soc/thermal-sensor@5070400:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/i2c@7081400:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/watchdog@7020400:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/iommu@30f0000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/i2c@5002400:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/spi@5011000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/spi@5011000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/serial@5000800:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/usb@5311000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/usb@5311000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/usb@5311000:clocks: cell 4 is not a phandle reference custom.dts: Warning (clocks_property): /soc/i2c@5002c00:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/i2c@5002c00/mfd@10/phy:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/serial@7080000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/usb@5101000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/usb@5101000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/usb@5101000:clocks: cell 4 is not a phandle reference custom.dts: Warning (clocks_property): /soc/tcon-top@6510000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/tcon-top@6510000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/hdmi-phy@6010000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/hdmi-phy@6010000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/i2c@5002000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/crypto@1904000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/crypto@1904000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/crypto@1904000:clocks: cell 4 is not a phandle reference custom.dts: Warning (clocks_property): /soc/mmc@4020000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/mmc@4020000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/mailbox@3003000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/serial@5000400:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/dma-controller@3002000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/dma-controller@3002000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/ethernet@5020000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/serial@5000c00:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/spi@5010000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/spi@5010000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/pinctrl@7022000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/pinctrl@7022000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/pinctrl@7022000:clocks: cell 3 is not a phandle reference custom.dts: Warning (clocks_property): /soc/ir@7040000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/ir@7040000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/watchdog@30090a0:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/i2s@5091000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/i2s@5091000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/dwc3@5200000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/dwc3@5200000:clocks: cell 2 is not a phandle reference custom.dts: Warning (clocks_property): /soc/dwc3@5200000:clocks: cell 4 is not a phandle reference custom.dts: Warning (clocks_property): /soc/usb@5100000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /soc/serial@5000000:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /cpus/cpu@1:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /cpus/cpu@2:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /cpus/cpu@0:clocks: cell 0 is not a phandle reference custom.dts: Warning (clocks_property): /cpus/cpu@3:clocks: cell 0 is not a phandle reference custom.dts: Warning (cooling_device_property): /thermal-zones/cpu-thermal/cooling-maps/cpu_very_hot_limit_cpu:cooling-device: cell 0 is not a phandle reference custom.dts: Warning (cooling_device_property): /thermal-zones/cpu-thermal/cooling-maps/cpu_warm_limit_cpu:cooling-device: cell 0 is not a phandle reference custom.dts: Warning (cooling_device_property): /thermal-zones/cpu-thermal/cooling-maps/cpu_hot_limit_cpu:cooling-device: cell 0 is not a phandle reference custom.dts: Warning (cooling_device_property): /thermal-zones/cpu-thermal/cooling-maps/cpu_hot_pre_limit_cpu:cooling-device: cell 0 is not a phandle reference custom.dts: Warning (cooling_device_property): /thermal-zones/cpu-thermal/cooling-maps/cpu_very_hot_pre_limit_cpu:cooling-device: cell 0 is not a phandle reference custom.dts: Warning (dmas_property): /soc/spdif@5093000:dmas: cell 0 is not a phandle reference custom.dts: Warning (dmas_property): /soc/spi@5011000:dmas: cell 0 is not a phandle reference custom.dts: Warning (dmas_property): /soc/spi@5011000:dmas: cell 2 is not a phandle reference custom.dts: Warning (dmas_property): /soc/spi@5010000:dmas: cell 0 is not a phandle reference custom.dts: Warning (dmas_property): /soc/spi@5010000:dmas: cell 2 is not a phandle reference custom.dts: Warning (dmas_property): /soc/i2s@5091000:dmas: cell 0 is not a phandle reference custom.dts: Warning (dmas_property): /soc/i2s@5091000:dmas: cell 2 is not a phandle reference custom.dts: Warning (iommus_property): /soc/bus@1000000/mixer@100000:iommus: cell 0 is not a phandle reference custom.dts: Warning (iommus_property): /soc/video-codec@1c0e000:iommus: cell 0 is not a phandle reference custom.dts: Warning (mboxes_property): /scpi:mboxes: cell 0 is not a phandle reference custom.dts: Warning (mboxes_property): /scpi:mboxes: cell 2 is not a phandle reference custom.dts: Warning (phys_property): /soc/hdmi@6000000:phys: cell 0 is not a phandle reference custom.dts: Warning (phys_property): /soc/usb@5311400:phys: cell 0 is not a phandle reference custom.dts: Warning (phys_property): /soc/usb@5311000:phys: cell 0 is not a phandle reference custom.dts: Warning (phys_property): /soc/dwc3@5200000:phys: cell 0 is not a phandle reference custom.dts: Warning (phys_property): /soc/usb@5100000:phys: cell 0 is not a phandle reference custom.dts: Warning (pwms_property): /ac200_clk:pwms: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/phy@5100400:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/phy@5100400:resets: cell 2 is not a phandle reference custom.dts: Warning (resets_property): /soc/gpu@1800000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/mmc@4022000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/hdmi@6000000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/hdmi@6000000:resets: cell 2 is not a phandle reference custom.dts: Warning (resets_property): /soc/pwm@300a000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/bus@1000000/mixer@100000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/bus@1000000/clock@0:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/i2c@5002800:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/phy@5210000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/lcd-controller@6515000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/spdif@5093000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/usb@5311400:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/mmc@4021000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/usb@5101400:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/video-codec@1c0e000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/thermal-sensor@5070400:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/i2c@7081400:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/iommu@30f0000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/i2c@5002400:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/spi@5011000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/serial@5000800:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/usb@5311000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/usb@5311000:resets: cell 2 is not a phandle reference custom.dts: Warning (resets_property): /soc/i2c@5002c00:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/serial@7080000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/usb@5101000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/usb@5101000:resets: cell 2 is not a phandle reference custom.dts: Warning (resets_property): /soc/tcon-top@6510000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/hdmi-phy@6010000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/i2c@5002000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/crypto@1904000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/mmc@4020000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/mailbox@3003000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/serial@5000400:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/dma-controller@3002000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/ethernet@5020000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/serial@5000c00:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/spi@5010000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/ir@7040000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/i2s@5091000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/dwc3@5200000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/usb@5100000:resets: cell 0 is not a phandle reference custom.dts: Warning (resets_property): /soc/serial@5000000:resets: cell 0 is not a phandle reference custom.dts: Warning (sound_dai_property): /hdmi-sound/simple-audio-card,cpu:sound-dai: cell 0 is not a phandle reference custom.dts: Warning (sound_dai_property): /hdmi-sound/simple-audio-card,codec:sound-dai: cell 0 is not a phandle reference custom.dts: Warning (thermal_sensors_property): /thermal-zones/cpu-thermal:thermal-sensors: cell 0 is not a phandle reference custom.dts: Warning (thermal_sensors_property): /thermal-zones/gpu-thermal:thermal-sensors: cell 0 is not a phandle reference custom.dts: Warning (gpios_property): /wifi_pwrseq:reset-gpios: cell 0 is not a phandle reference custom.dts: Warning (gpios_property): /soc/mmc@4020000:cd-gpios: cell 0 is not a phandle reference custom.dts: Warning (gpios_property): /leds/heartbeat:gpios: cell 0 is not a phandle reference custom.dts: Warning (gpios_property): /leds/status:gpios: cell 0 is not a phandle reference custom.dts: Warning (gpios_property): /leds/link:gpios: cell 0 is not a phandle reference custom.dts: Warning (gpios_property): /vbus:gpio: cell 0 is not a phandle reference custom.dts: Warning (gpios_property): /gmac-3v3:gpio: cell 0 is not a phandle reference custom.dts: Warning (graph_child_address): /soc/tcon-top@6510000/ports/port@0: graph node has single child node 'endpoint@0', #address-cells/#size-cells are not necessary custom.dts: Warning (graph_child_address): /soc/tcon-top@6510000/ports/port@4: graph node has single child node 'endpoint@0', #address-cells/#size-cells are not necessary [1] 6806 segmentation fault dtc -I fs /sys/firmware/devicetree/base -O dts -o custom.dts

Your welcome! It's a pleasure to contribute to armbian. I also tried your proposition with the reading of the device-tree folder with this command: dtc -I fs -O dts /sys/firmware/devicetree/base -o custom.dts But on my edge-v (kernel 5.9), pine64h-b and opi1 with kernel 5.8, it generates a segmentation fault, whereas on my gt1 ultimate running armbianTV with kernel 4.20 it works.

Testers needed. More especially, people with samsung, nexell or even marvell are expected. The main issue for now is the way the dtb is named and located in the boot folder. I tried to infer it using the comptible property of the device tree, but I don't own all supported hardware . I already tested sucessfully on several kernels (aml 4.20, rk and aw on 5.8, 5.9).

First pull request for me: https://github.com/armbian/config/pull/123 It is a basic implementation with my humble knowledge in bash. It may be improved by experts if possible. I tested on my armbian dev config and it seems to work. I hope to have follow the right way to make a PR since it is my first one.

I don't see real questions in your post, but here is my personal experience. I run armbian on sbcs since 2016 and used it on one of them for home server. My current server is based on a s912 tv box with a 4.20 kernel installed maybe two years ago (I don't remember exactly ): Welcome to ARMBIAN 5.75 user-built Debian GNU/Linux 9 (stretch) 4.20.5-aml-s912 System load: 0.03 0.02 0.00 Up time: 135 days The system is amazingly stable and the only improvement I'm looking at, is maybe upgrading to a board/sbc having usb3 or sata(but since my local network is only 100MB, no real need for now). On my next install, I plan to use docker for several applications that I installed the classic way. Why: - no more problems with package dependencies not available or not update to date: I use home-assistant and I'm stuck on v 0.96 since after python 3.5 is mandatory and it is not easily available on stretch. - easily upgrade the applications: remove the container, upgrade the image and launch it again! - easily install and remove applications you want to test. The main drawback I see, is the disk space and the memory consumption that may be more important. I've used several test configs to replace my current server, but they mainly failed on the stability criterion, but my last try with pineh64-b seems promising. I also want to switch from armbianTV's Balbes images to official Armbian, since support for amlogic SoCs stops and also upgrade seems more robust with official Armbian builds (maybe true before but now armbianTv builds are more similar than original armbian). What I've installed on docker is: - home-assistant (official image) - zigbee2mqtt (official image) - pyload (linuxserver.io image) - jellyfin (linuxserver.io image) (previously plex) - airsonic (linuxserver.io image) I'm looking to use again openmediavault, but no official container image seems available and I didn't take time to look for it. I'm also looking at linuxerver.io images to check possible additional services to host, since their images seems well "packaged". For me now, the main objective is to use a board that can be "basic" (but with enough memory and GBE), then to install and configure a "basic" and robust host system easy to maintain, finally to launch containers for which I have just the necessary config to set in dedicated folders (easy to save).

I think this could be an interesting soc, but in how many months (or years)? This soc is not referenced in sunxi status matrix and nothing is planned in kernel 5.11, so I fear that support is not even started from their side. Maybe it's close enough to h6, but I didn't see any information about somebody able to start linux with it and it has a different gpu.

I think you refer to JMCC work, but it only works with kernel 4.4 if I'm right. The problem is to be able to compile rkmpp with mainline and then ffmeg or gstreamer.