Cornelius

@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