Cornelius

I'll start by saying I don't own the board, but as this has come up and seems to be a problem across many boards using the same SoC and bits, it would appear on its face that the fix is probably generally the same across them all. Give or take a few differences?
 
My github reference to the issue: https://github.com/armbian/build/issues/1352#issuecomment-952077351
 
I've included two patches you could test that I made for 5.10.y as that appears to be the kernel ur using.
 
One thing I do not mention in the github issue is I also include the following to /etc/modules
# /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. bluetooth hidp rfcomm bnep hci_uart  
 
002-sun50i-h5-orangepi-zero-plus2-rfkill-gpio.patch 001-sun50i-h5-orangepi-zero-plus2-bluetooth-support.patch

I can't be 100% sure, but I believe I saw a pull request for this some time ago where some one removed some things related to the reboot issue. I haven't scanned through the patch set as of late, but in my testing the following is needed.
 
Need to revert:
drivers/gpu/drm/meson/meson_drv.c
https://github.com/pyavitz/debian-image-builder/blob/feature/patches/amlogic/odroid/002-linux-odroid-patch-set.patch#L524
https://github.com/pyavitz/debian-image-builder/blob/feature/patches/amlogic/odroid/002-linux-odroid-patch-set.patch#L542
 
Add Odroid reboot:
https://github.com/pyavitz/debian-image-builder/blob/feature/patches/amlogic/odroid/002-linux-odroid-patch-set.patch#L2323
https://github.com/pyavitz/debian-image-builder/blob/feature/patches/amlogic/odroid/002-linux-odroid-patch-set.patch#L2533
 
If you review the pull request, you can see where the revert and odroid power reset patch was removed: https://github.com/armbian/build/pull/3154/files
 
As for mainline u-boot the only thing of real importance is the following revert: https://github.com/armbian/build/pull/3154/files#diff-65100acf19e202ac3f3980da554c205752ea3c67d08fc4a3b445d4397189d12fR36
 
With out it, the boards "especially the N2/+ will kernel panic, as the reserved memory "CMA pool won't be set correctly".  So the patch forces the boards to be marked nomap, hence populated after uboot hands off to the kernel.
 

I believe what is required is this commit added to the meson64 patch set. https://github.com/tobetter/linux/commit/a026e2e9f55116e81ed49f48d918fdb91e28eff6

I created a script to set the trip point, which can then be run at boot with a service or by placing it in /etc/rc.local
 
# Script sudo wget https://raw.githubusercontent.com/pyavitz/scripts/master/fan-ctrl -P /usr/local/bin sudo chmod +x /usr/local/bin/fan-ctrl # Service sudo tee /etc/systemd/system/odroid-fan-ctrl.service <<EOF [Unit] Description=Odroid Fan Control ConditionPathExists=/usr/local/bin/fan-ctrl [Service] ExecStart=/usr/local/bin/fan-ctrl -r &>/dev/null Type=oneshot RemainAfterExit=yes [Install] WantedBy=multi-user.target EOF sudo systemctl enable odroid-fan-ctrl # Options Odroid N2 Trip Point Usage: fan-ctrl -h -1 65°C -2 55°C -3 45°C -4 35°C -r Run -u Update The systemd service runs 'fan-ctrl -r' during boot.  
One down side is that it requires sudo to work, so you would need to either edit the script to your needs or setup sudo, so that you don't need a password to execute. But then again, it shouldn't matter when being run as a service, as root shouldn't care about sudo?

I haven't noticed any eth related problems on 5.13.y and RK3399, but when moving to 5.14.y I also found that eth no longer worked. I corrected the issue by reverting the following commit: https://github.com/torvalds/linux/commit/2d26f6e39afb88d32b8f39e76a51b542c3c51674
 
I understand its not a true fix. This was tested on the NanoPC-T4.
 
--- a/drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c 2021-09-12 03:01:00.000000000 -0400 +++ b/drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c 2021-09-14 07:19:24.402736613 -0400 @@ -21,6 +21,7 @@ #include <linux/delay.h> #include <linux/mfd/syscon.h> #include <linux/regmap.h> +#include <linux/pm_runtime.h> #include "stmmac_platform.h" @@ -1528,6 +1529,9 @@ return ret; } + pm_runtime_enable(dev); + pm_runtime_get_sync(dev); + if (bsp_priv->integrated_phy) rk_gmac_integrated_phy_powerup(bsp_priv); @@ -1536,9 +1540,14 @@ static void rk_gmac_powerdown(struct rk_priv_data *gmac) { + struct device *dev = &gmac->pdev->dev; + if (gmac->integrated_phy) rk_gmac_integrated_phy_powerdown(gmac); + pm_runtime_put_sync(dev); + pm_runtime_disable(dev); + phy_power_on(gmac, false); gmac_clk_enable(gmac, false); }  

Other than the suggestion I made before I see nothing really wrong with it. It's way more complicated than my approach and written better, but that would be expected. This is Armbian after all. 
I see some variables I don't understand such as $MAKE and $SRCARCH, but I'm going to assume that makes sense in the builder somewhere.
 
I also notice that none of the pre/post scripts define what they are..? Such as #!/bin/bash or #!/bin/sh, but that would only be relative during the kernel install and have nothing to really do with creation.
 
Only major difference I see, is you appear to be using the builddeb/mkdebian files from 5.10.y, where as I use the 5.4.y files and patch them accordingly to the SoC I am building for. I find it to be a more simplistic builddeb script and less of hassle to deal with and the kernel doesn't complain when I replace the ones it comes with. 
 
Example packaging I use for my test builds. https://github.com/pyavitz/debian-image-builder/tree/feature/patches/packaging
Disclaimer: I don't recommend anyone using that builder, it's mostly a pet project and learning tool for myself. 
 
As for the slow down you are getting in the VM, I really have no ideas as to why that would be. I never use a VM when building, although I do use Docker sometimes.
 
 

@NanoP
 
I don't own a M4, but I do have a T4 and whilst testing on that my drive came up as it should. My own personal experience with Rockchip and USB3 ports hasn't really been a good one and because of that, I do not use them as a NAS. Which is and I'm just guessing here, what ur trying to do.
 
If it is power related, may i suggest getting a small USB powered hub?

@NanoP
 
I don't own a M4, but I do have a T4 and whilst testing on that my drive came up as it should. My own personal experience with Rockchip and USB3 ports hasn't really been a good one and because of that, I do not use them as a NAS. Which is and I'm just guessing here, what ur trying to do.
 
If it is power related, may i suggest getting a small USB powered hub?

@Darius
 
I'm not sure how much more I can tell you about it, but I can try and help you. Using the same server image (or headless? which ever you prefer) start the board and login. Once in, run the following command - sudo lsmod
 
My Renegade lsmod:
sudo lsmod Module Size Used by zram 24576 4 rk_vcodec 65536 0 uio_pdrv_genirq 16384 0 uio 20480 1 uio_pdrv_genirq ip_tables 24576 0 x_tables 28672 1 ip_tables autofs4 40960 2 That should present you with a list of all the loaded modules and "hopefully" something that is not on my list that looks audio related.
 
Once said module is found, we can then unload it and place it in a blacklist. 
 
Example:
sudo rmmod pesky_rk3328_codec
 
Now with it unloaded, let us add it to the blacklist.
sudo echo pesky_rk3328_codec > /etc/modprobe.d/blacklist.conf
 
For that to take full effect we will need to reboot, but before we do that lets tackle the Wifi.
 
As for your Wifi troubles, let us try running - sudo nmtui
That should present you with three options, one being "Activate a connection" and from there you should see your available Wifi. Make your selection, enter your passkey and connect.
 
If anyone else has some suggestions, thoughts or corrections. Please feel free to interject.

In my experience this is caused by the Alsa for SoC audio support > Codec Drivers: X Rockchip RK3328 Codec
When that is enabled in the kernel config, the sdcard will get read/write errors during boot and throw you into readonly mode.
As a temp solution you could try to blacklist the module or build ur own img and disable it in the kernel config.
 
This by the way, does not happen when using an eMMC and yes, I believe TonyMac32 is already on the case.

In my experience this is caused by the Alsa for SoC audio support > Codec Drivers: X Rockchip RK3328 Codec
When that is enabled in the kernel config, the sdcard will get read/write errors during boot and throw you into readonly mode.
As a temp solution you could try to blacklist the module or build ur own img and disable it in the kernel config.
 
This by the way, does not happen when using an eMMC and yes, I believe TonyMac32 is already on the case.

In my case the USB3 port comes up as 006 001 when checking with lsusb and if I do the following it resets the port.
 
sudo sh -c 'echo 6-1 > /sys/bus/usb/drivers/usb/unbind' sudo sh -c 'echo 6-1 > /sys/bus/usb/drivers/usb/bind'  

... which is delivered in parts