@Ryzer pcduino definitely works fine with dwc2. I cannot get OTG to work without it. I am not qulified to make any comments on whether this makes sense or is a coincidence, but if I don't load the module, it's doesn't work. For some reason, the mass storage gadget is still a little unstable in Windows (sometimes the File Explorer window shuts down for no reason), but on a Linux laptop, it is rock stable. It has also been running for two days in my car and doesn't seem to miss a beat there either (Linux host).

I'm putting together a build for a 3D printer, rk3308b-s board that has no ethernet, just a Fn-link wifi chip that is a knock-off of an rtl8192fs. I pulled the OEM dts and it describes the chip as an rtl8192cs. I'm pretty sure this is an out of kernel driver and my searches indicate I put source in userpatches. What do I need to add in the board/*.csc file to build to an image with the kernel module(s)? I do have a ralink ra2400, a mt7201 and some supported realtek dongles and If connected, I could git the code build and moprobe the module to test. Ideally, I would like to incorporate the driver via dkms in a armbian build. Can someone point me to the process?

I found a solution: downgrade the kernel to version 5.10.218 on SD-card_images by Johang Gunarsson in sweden. I used his Bookworm image. It does require a bit of work: Rsync is often broken on his images for pcduino (it looks for a libcryto.1 module but that module is obsolete), so you may need to downoad and compile rsync if you need it. The wifi is also unstable with the main line driver. I fixed the issue by installing morrownr's driver, but it takes ages to compile on the old lady (about 45 mins). I took the kernel and headers from this archive: https://archive.debian.org/debian/pool/main/l/linux/ Apparently, the big change between kernel 5 and 6 wrt OTG is usb-role-switch. Pcduino can support this new requirement, but someone with the right knowledge needs to take the time to update the device tree, and since the board is old, this may take time, or at this stage, may never happen.

It really is as simple as possible on Armbian. Pretty good documentation too, I posted it before, but here you go again: https://docs.armbian.com/ All you have to do is to login as root from an ssh client following standards. I do not have access to a windows installation where I can confirm if what you say is true, that the ssh client does not let you login with "ssh root@xxx.xxx.xxx.xxx", so maybe you are correct, but it sounds very unlikely to me. But what I can guarantee is using an ssh client from another unix system will definitely let you connect. So use a mac or a linux computer to access. Or install wsl on windows and do it from there. https://learn.microsoft.com/en-us/windows/wsl/install Edit: I actually forgot, but I had putty installed on my system. I used it to check colors in a script I maintain and it exists in the extras repo on arch. Downloaded latest minimal image for rpi (so not same hardware as you) and... No settings changed in putty, just a standard root@192.168.99.60 that I added into the "Host Name (or IP address)" field and clicked "open". Name : putty Version : 0.83-1 So I don't know what to tell you...

This seems like an excellent question for a lawyer. That said, the Armbian Build system is GPL v2, which Wikipedia has an excellent Article on, and has the following to say: That said, even if you're not distributing modifications of the build system, the final image still has GPL components.