surenz

Is there a way to enable this port again as usb host for 6.1+ kernels? I was using before a custom overlay but it's not working anymore. I'm using Orange Pi One with Allwinner H3 and before with 5.15 kernel I was getting this: dmesg | grep musb [ 3.589043] musb-hdrc musb-hdrc.4.auto: MUSB HDRC host driver [ 3.589082] musb-hdrc musb-hdrc.4.auto: new USB bus registered, assigned bus number 9 [ 3.589483] usb usb9: Manufacturer: Linux 5.15.93-sunxi musb-hcd [ 3.589491] usb usb9: SerialNumber: musb-hdrc.4.auto Now with 6.1+ kernels I get this musb-sunxi 1c19000.usb: Disabling musb host side code due to re-routed phy I don't find any g_serial with lsmod so no need to disable the module. Neither it's present in /etc/modules.

Just as update I can say that the cosmetic issues in my previous question 3 are resolved with the change of BOARD_NAME and BOARD in /etc/armbian-release to comply with the real board. The only problem I see is the message at the top of the file PLEASE DO NOT EDIT THIS FILE and if the file is updated during some of the regular updates.

The u-boot can be reflashed very easily and secure with the armbian-config but it takes the image from some package which is downloaded from apt repo. Of course those packages are still not updated so they don't change even if flashed.

I'll try to hijack this topic with my problems migrating a working Armbian from one SBC to another - Orange Pi One to Orange Pi PC and vice a versa. The SBCs have very small differences but at least they have so it's a good and (almost) safe experiment. So far I succeeded to use the appropriate dtb file for every SBC as easy as adding the parameter fdtfile= to the file /boot/armbianEnv.txt It works on the level to detecting the right hardware in the linux but u-boot is still detecting the old model board. In the linux the /proc/device-tree/model is showing the right model and the hardware is working as it should. But some cosmetic issues exist - armbian-config is still showing the old board and the MOTD on ssh login has the wrong model banner (I suspect that this info is taken from the file armbian-release). So my questions: 1. Do you know what I have to do to change the u-boot to show the right board? (I tried menu config but saveenv failed) 2. What is exactly the process of detecting the right board (perhaps it's done in the linux image which is downloaded in ready state and compiled for that specific board) either in first run or in the compile image stage? 3. Can we make changes to already installed linux to change those small discrepancies for more comfortable feeling (as more issues seem cosmetic than real)? The changes between the SBCs I mentioned are small (at least the SoC is same) but some of them are important: - the ports are different (OPi One has two USBs instead of 4 in OPi PC, audio and IR connectors are missing) - voltage regulator is missing on OPi One

I think this repo has complete answer to your question: https://github.com/kelebek333/rtl8188fu/tree/arm I have installed that driver many times without issues. The only caveat is that you have to reinstall it on every kernel update (could be done before reboot to not loose connectivity with dkms autoinstall -k x.xx)

I see in the docker install script get-docker.sh) the following text: # The channel to install from: # * nightly # * test # * stable # * edge (deprecated) so I think that stable is OK instead of edge . At least on my armbian buster it installed the docker correctly and I'm currently trying Home assistant supervised install.

@IgorI'm not quite sure if this is the problem but the current docker install script which I followed from your link above: https://docs.docker.com/engine/install/debian/#install-using-the-convenience-script leads to download a script that differs from the script used in procedure install_docker in armbian-config. Thus errors 404 on docker install. On armbian-config script the expression echo "deb [arch=$(dpkg --print-architecture)] https://download.docker.com/linux/${family,,} $distribution edge" returns the broken value of deb [arch=armhf] https://download.docker.com/linux/ edge which leads to error when doing apt update for docker.list so unable to install docker-ce The script from the link I stated above puts this in the docker.list: deb [arch=armhf] https://download.docker.com/linux/debian buster stable which seems ok and the install goes further and installs the docker-ce.

Hi, I've been struggling also with all the info in this thread but finally succeeded to make decompile/edit/compile the dtb file (assume this file as BIOS for ARM ) I'm putting all commands here as reference for me as well : cd /boot/dtb sudo cp sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dtb.old sudo dtc -I dtb -O dts -o sun8i-h3-orangepi-one.dts sun8i-h3-orangepi-one.dtb sudo sed -i -e 's/dr_mode = "otg";/dr_mode = "host";/g' sun8i-h3-orangepi-one.dts sudo dtc -I dts -O dtb -o sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dts Explanation of different lines: 1. go to dtb directory 2. make backup of the compiled file in case something goes wrong 3. decompile the file to be able to alter it with text editor 4. change the string from "otg" to "host" 5. compile the altered file back to binary format dtb The only bad thing with all this above is that if you upgrade your kernel the info will be lost so you have to do it again. I don't get why this parameter is set by default to "otg"?