fever_wits

Hello, Today I upgraded from 24.5.0-trunk.231 to 24.5.0-trunk.318, for now everything is working normally. But I had to recompile the zfs module again. It has zfs-dkms installed, shouldn't it just recompile the module? If there is a need to upload a log or provide other information, I am available. Regards,

Hello, I don't have any issues with the CPU, I'm saying if I had to choose I'd go with the CPU, not the internal drive. Otherwise, I'm currently with kernel linux-image-vendor-rk35xx:arm64 24.5.0-trunk.231 and everything works fine. This kernel was installed via apt dist-upgrade. lscpu says everything normal but cpu-info keeps seeing things wrong. I'm not sure where the problem is. Regards,

Hello, My mistake. The image I use was published on 13.03.2024. Up until this point I was working with a personal kernel build based on armbian. From personal memory, I think it is 24.5.0-trunk.211 This is bad news for me. Apparently I won't touch the kernel. I already had a case, in a personal build, I used armbian-config to see a 5.10 kernel version, then I also put 6.1.43. Then the script removed kernel 5.10 and did not install 6.1.43. And everything started anew. That's how I found out that it was posted on 13.03.2024 image For me, it's more important to have a working CPU than an internal drive. Otherwise, I use the built-in disk to backup boot and the OS. In the source of the Edge version, at least until recently, most of the governors were missing. Now I've run and see that's fixed. I can't use Edge because of ZFS.

Hello, I will use the NanoPC-T6 for a micro server. The main thing it will run on is LibreNMS (currently my LibreNMS is on a NanoPi R6S) I will also use ZFS, tftp, bond, vlan and others. The reason I use the NanoPC-T6 is the 16GB ram as well as the PCIe slot. I am attaching 2 pictures if anyone is curious about what I have created. It's not very pretty, but it's functional. What I have further configured in /boot/armbianEnv.txt verbosity=7 - I prefer to see the OS loading extraargs=net.ifnames=0 biosdevname=0 consoleblanl=0 brd.rd_nr=0 mitigations=off brd.rd_nr=0 stops all Ram Block Devices mitigations=off - this is on an internal network and since I don't know if I'll lose performance I just stop everything console=serial - console output only serial port docker_optimizations=off - I don't use docker I only use the memory card for /boot The OS is on the SSD in raid1 (about 16GB), the rest is raid1 in a zfs array, for 3 pools (mysql, librenms, storage) I have installed ZFS like this: apt install linux-headers-vendor-rk35xx zfsutils-linux zfs-dkms zfs-zed From the kernels offered by Armbian 5.10, 6.1 and 6.8, I use 6.1 I removed the network-manager wpasupplicant packages, instead of network-manager I use ifupdown2 The control of the fan is through the dts file. The steering has 5 levels. 1st degree is at 50 degrees, then 2nd degree - 60 and so on With installed fan and stress-ng more than 55 degrees I can not lift. At linux-image-vendor-rk35xx_24.5.0-trunk.226_arm64 ZFS - compiles normally. governor - on CPU works, has all modes of operation governor for dmc, gpu and npu - only ondeman. Network cards work normally. FAN - management through the dts file works normally. At linux-image-vendor-rk35xx_24.5.0-trunk.231_arm64 Installed from apt dist-upgrade, ZFS doesn't compile, had to do aptitude reinstall zfsutils-linux zfs-dkms zfs-zed governor - on CPU works, has all modes of operation governor at dmc, gpu and npu - , has all modes of operation Network cards work normally. FAN - management through the dts file works normally. On this build, one core is constantly at 100% (probably ZFS, but not sure about top and htop doesn't show which one is causing the IO) I am using the 13.03 image, in this version in install linux-headers does not work, I installed it by hand. While writing this I saw in armbian-config that there is already a version linux-image-vendor-rk35xx_24.5.0-trunk.244_arm64 but I can't find what is fixed and will wait for it to appear with apt. I have further increased the size of /boot to 2GB like this: aptitude install fatresize umount /boot/ fatresize -v -p -s 2G /dev/mmcblk1p1 mount -a Before using armbian kernel I had compiled 6.1 with these optimizations. General setup ---> Preemption Model (Voluntary Kernel Preemption (Desktop)) ---> No Forced Preemption (Server) General setup ---> Compiler optimization level (Optimize for performance (-O2)) ---> Optimize for performance (-O2) Kernel Features ---> Timer frequency (300 HZ) ---> (X) 100 HZ As a positive effect, the system is a little more "agile". Negative effect, slightly warmer is the housing of the box. What I would like fixed. My version of NanoPC-T6 is 16GB ram and 256GB internal disk. In this case I don't see the internal disk. The other thing I want is to keep the old versions of the kernel. Currently, when I install a new version of the kernel, the old version of the kernel is uninstalled, and if the OS does not start, I have to do everything from the beginning. It could be a setting, but I can't find where it is. Regarding what I used like FAN, PCIe to Sata and SSD cage, I don't know if it is allowed to post links, not to be considered as advertising. I hope this is useful to someone. Regards,

Hello, Thanks to @ALIGMSTEN and @SteeMan, these days I will write what I have tested. Regards,

Hello, At the moment I am working with an image that is from the site. Many of the things work OK, but there are some that have reservations. I don't know if it's appropriate to comment in the tickets or address someone specifically or write elsewhere. That's what the last comment was about. I am happy with what has been done, but I would like to share impressions if anyone is interested. I know we are all busy with work, family, etc. And in order not to waste the time of many people, I asked like this. Regards,

Hello, I saw that on March 13 you released an image with kernel 6.1.XX. using the image, I would like to share feedback. Should I write here or can I address someone specifically? Regards,

Hello, I downloaded the source from the git repository. The configurator and compiler are very intuitive. They are easy to work with. Saved a lot of time and nerves Thanks for what has been done as a configurator and the documentation. Because I don't know if my problem is in the dtb file or in the kernel. I compiled three versions edge 6.8.0-rc7 - this does not work correctly. legacy 5.10.160 - everything works here. vendor 6.1.43 - everything works here. And I was pleasantly surprised to find out that the fan control is also active. CPU frequency scaling - works correctly on "legacy" and "vendor". CPUs are successfully overclocked to factory frequencies. For now, I'm still experimenting with compiling the kernel. I'm open to suggestions and tests. I hope this information was helpful. Regards,

Hello, I apologize for my bad English. I have a NanoPi R6S and a NanoPC T6. Both Nano devices have Armbian images. Both devices use a processor: CPU Model: Rockchip RK3588 Number of Cores: Quad-core ARM Cortex-A76 + Quad Core Cortex-A55 Frequency: Cortex-A76 (up to 2.4GHz), Cortex-A55 (up to 1.8GHz) A few things struck me On NanoPi R6S in the dts file, the frequency of A76 cores is up to 2.4GHz you can see the frequencies at which each core works cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 2016000 2208000 2352000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 2016000 2208000 2352000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 2016000 2208000 2256000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 2016000 2208000 2256000 governors: cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_governors conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil On NanoPi T6 in the dts file, the frequency of A76 cores is up to 2.2GHz - I fixed it /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies - this is missing. /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_governors - this is missing, having instead cat /sys/devices/system/cpu/cpuidle/available_governors ladder menu teo NanoPi R6S is currently running kernel 5.10.110-rockchip-rk3588 NanoPC T6 is currently running kernel 6.8.0-rc6-edge-rockchip-rk3588 I also noticed differences in CPU cache. NanoPI R6S Architecture: aarch64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 3 Vendor ID: ARM Model: 0 Model name: Cortex-A55 Stepping: r2p0 CPU max MHz: 2352.0000 CPU min MHz: 408.0000 BogoMIPS: 48.00 L1d cache: 256 KiB L1i cache: 256 KiB L2 cache: 1 MiB L3 cache: 3 MiB Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Vulnerability Spectre v1: Mitigation; __user pointer sanitization Vulnerability Spectre v2: Vulnerable: Unprivileged eBPF enabled Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp NanoPC T6 Architecture: aarch64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: ARM Model name: Cortex-A55 Model: 0 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 Stepping: r2p0 BogoMIPS: 48.00 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp Model name: Cortex-A76 Model: 0 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 Stepping: r4p0 BogoMIPS: 48.00 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp Caches (sum of all): L1d: 384 KiB (8 instances) L1i: 384 KiB (8 instances) L2: 2.5 MiB (8 instances) L3: 3 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-7 Vulnerabilities: Gather data sampling: Not affected Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec rstack overflow: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1: Mitigation; __user pointer sanitization Spectre v2: Vulnerable: Unprivileged eBPF enabled Srbds: Not affected Tsx async abort: Not affected When using the command: cpufreq-info NanoPI R6S cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:76.72%, 600 MHz:6.69%, 816 MHz:0.31%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:16.29% (11087717) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:76.72%, 600 MHz:6.69%, 816 MHz:0.31%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:16.29% (11087717) analyzing CPU 2: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:76.72%, 600 MHz:6.69%, 816 MHz:0.31%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:16.29% (11087717) analyzing CPU 3: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:76.72%, 600 MHz:6.69%, 816 MHz:0.31%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:16.29% (11087717) analyzing CPU 4: driver: cpufreq-dt CPUs which run at the same hardware frequency: 4 5 CPUs which need to have their frequency coordinated by software: 4 5 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.35 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.35 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.35 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:85.33%, 600 MHz:1.13%, 816 MHz:0.40%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:0.00%, 2.21 GHz:0.00%, 2.35 GHz:13.14% (2586948) analyzing CPU 5: driver: cpufreq-dt CPUs which run at the same hardware frequency: 4 5 CPUs which need to have their frequency coordinated by software: 4 5 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.35 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.35 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.35 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:85.33%, 600 MHz:1.13%, 816 MHz:0.40%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:0.00%, 2.21 GHz:0.00%, 2.35 GHz:13.14% (2586948) analyzing CPU 6: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.26 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:92.30%, 600 MHz:0.44%, 816 MHz:0.16%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:0.00%, 2.21 GHz:0.00%, 2.26 GHz:7.10% (1012245) analyzing CPU 7: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.26 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:92.30%, 600 MHz:0.44%, 816 MHz:0.16%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:0.00%, 2.21 GHz:0.00%, 2.26 GHz:7.10% (1012245) NanoPC T6 cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 4: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 5: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 6: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 7: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. The CPU driver appears to be missing. When using the command: cpu-info NanoPI R6S cpu-info Packages: 0: Unknown Microarchitectures: 4x Cortex-A76 4x Cortex-A55 Cores: 0: 1 processor (0), ARM Cortex-A76 1: 1 processor (1), ARM Cortex-A76 2: 1 processor (2), ARM Cortex-A76 3: 1 processor (3), ARM Cortex-A76 4: 1 processor (4), ARM Cortex-A55 5: 1 processor (5), ARM Cortex-A55 6: 1 processor (6), ARM Cortex-A55 7: 1 processor (7), ARM Cortex-A55 NanoPC T6 cpu-info Packages: 0: Unknown Microarchitectures: 8x Cortex-A55 Cores: 0: 1 processor (0), ARM Cortex-A55 1: 1 processor (1), ARM Cortex-A55 2: 1 processor (2), ARM Cortex-A55 3: 1 processor (3), ARM Cortex-A55 4: 1 processor (4), ARM Cortex-A55 5: 1 processor (5), ARM Cortex-A55 6: 1 processor (6), ARM Cortex-A55 7: 1 processor (7), ARM Cortex-A55 My question is the following. Are the differences because of the dts file or because of the kernel. Anyone else using a NanoPC T6 and would like to help fix this? At the moment, I'm not using NanoPC T6 as a server yet, and I have the opportunity to experiment. It will be used as a small server for graphics, tftp and others. Is there any additional information needed. Regards,

Hello, I got a nanopc-t6, when trying to install mdadm or another package that regenerates initramfs or installs a new kernel, I get an error that there is no space in /boot. Can it be increased and how? Regards,

Hello, I made several attempts and all failed. I think without the correct u-boot.img (to boot from a card if I'm not mistaken) and idbloader.img for the NanoPi R6S that it will be able to boot any OS. The good news is that kernel 6 already has most of Rochchip's processors supported. dts file that seems to work I found on the internet. If someone can help with u-boot.img and idbloader.img or tell me how to do it (this is dark matter for me) I can try to run debian 12. I have a NanoPi R6S, although I use it, I can stop it for a while for a test. Regards,

Hello, After a long internet search I finally found a clean image for the NanoPi R5S. Debian 12 (testing), kernel 6.1.0-6-arm64, kernel is from repo. I have successfully installed and configured zfs and mdadm I have successfully moved / (OS) onto the software raid. Memory card left only for /boot/ Here's a link if anyone needs a working debian linux https://github.com/inindev/nanopi-r5 Regards,

Hello, Thanks for the links, but I was looking for an image of any possibility to install ZFS. I tried to compile ZFS but the image is with kernel: 5.10.110 And in repositories there is only linux-headers-5.10.0-21-arm64 I will try to make a micro storage server with 2 SSD drives connected directly to the NanoPI. I don't use USB to Sata. There are two reasons why I like the NanoPi series I have NanoPi R4SE, R5S, R6S 1. More than 1 physical network port, I know there is a USB to LAN, but I've had problems with such a card, on a RaspberyPi 4 2. The fact that they have a factory passive cooler. I use them as micro servers and I really hope Armbian make images for them. (R5S and R6S) So far I have tested several options - OpenWRT - I ran into a missing modules issue there, it was from a snapshot. - DietPi - this is actually from friendlyelec, the only thing more is that it supports discard/trim on the memory card. Extremely cluttered with supporting scripts that I don't know if they can be removed. - To one of the developers, but there, no matter how much I delete the built-in flash, it refuses to load from the memory card. - And accordingly friendlyelec - The problem is that you cannot redo the initrd. Or at least I didn't understand how. As well as the lack of linux-headers for the kernel it comes with. And I want to thank the Team who made armbian for NanoPi R4S(E), you did an amazing job. I think it's the only image I've tested where I was able to run everything I needed while testing. I was especially very pleasantly surprised to see that the brd module is not compiled inside the kernel, but as a module. Which allowed me to do raid1 tests between ram drive and iscsi. I also have the following question, what exactly needs to be done to get a kernel image to which a module can be compiled. I'm willing to waste time and energy to help, I just don't have experience with these kind of processors. If it needs to be compiled I have somewhere to use a compilation resource. Regards,

Hello, I have a nanopi R5S, ram 4G. Can anyone share a working image. And if there is a working image, should it be used from external or internal MMc? Regards,

Hello, Please Just be careful when choosing the voltages, power consumption or amps and speed (Network) of the PoE modules, no matter which vendor it is from. Regards,