Werner

Hm does not contain 7.1.0 dmesg boot log

Seems like the same "issue" like here. tl;dr: upstream uses "otg" to allow user to change the usb port behaviour as they like. https://forum.armbian.com/topic/59094-usb-2-port-not-available/#comment-237191

The upstream default seems to be "otg" to allow users in userspace to change the usb port behavior. Try this and use armbian-add-overlay /dts-v1/; /plugin/; / { fragment@0 { target = <&usb_host0_xhci>; __overlay__ { dr_mode = "host"; }; }; };

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

must be specific to this board. rock-3a which also uses RK3568 is not affected. btw. bleedingedge is intended to be used by developers only since breakage just like you noticed, is very much expected.

For those who want to follow the linux-sunxi mailing list but not as plain emails but in patchwork format, feel free to use https://patchwork.armbian.eu/project/patchwork/list/

Multiple options: - wait for upcoming 26.05 release which will most likely have an updated kernel package including a fix for this - as suggested use nightly - use the build framework to build an most up-to-date kernel package set by yourself (its very easy) which then can be installed via dpkg -i However since "dirty frag" just showed up, there is more to fix anyway... Edit: looks like fix for dirty frag hit upstream earlier today

you chould check the device tree which mode is there by default. I assume it is not "host" but something else. I believe the device tree follows upstream and is not altered by Armbian. Not sure though, needs research

You posted in the wrong sub-forum. Your topic is about the orangepizero2w which for once has nothing to do with orangepizero2 and for the other is unsupported by Armbian. Therefore the topic was moved (and the tag adjusted) to the unsupported/community supported section of the forums, also known as staging. Latter do not offer dedicated sub-forums for each individual board.

I don't know the names either. I suggest to look at the original device tree by decompiling it: dtc -I dtb -O dts /boot/dtb/allwinner/whateverthenameofthezero3devicetreewas.dtb

Check uboot logs if the overlay has been loaded correctly. You may need an usb uart adapter for this.

I suggest to create a device tree overlay to disable both.

moved to staging

Well if you want to live on the edge, then use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } egde as branch instead of code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } current

Newer kernel packages may not have hit apt repo yet. Use the build framework to generate a set of kernel packages to be installed via dpkg -i by yourself: https://docs.armbian.com/Developer-Guide_Overview/ code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh BOARD=rpi4b BRANCH=current kernel

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Our resources are limited so we cannot provide images for each board with each kernel and each desktop environment. Feel free to use the framework to build the combination you want by yourself. https://docs.armbian.com/Developer-Guide_Overview/

moved to staging

Armbian does not have things like "vendor-lockin" or something and descriptions like "does not work" aren't much helpful as well. Either way, we cannot help with 3rd party OS since we neither know them nor deal with them, so I suggest to ask at the place where you got the image you are attempting to use get from, like http://friendlyarm.com/

Ah, this board has n out of tree dt as well which most likely overwrites the patch. Try adjusting this file: ~/build/patch/kernel/archive/rockchip64-6.18/dt/rk3576-nanopi-r76s.dts

Hm, the sub-folder in userpatches might be wrong, not sure though. If in doubt just copy your patch directly into patch/kernel/archive/rockchip64-6.18/ Then it should be applied

At the very end of each compile.sh run there is a "curl" command which allows to upload the full build log to a paste service. This can also be done automatically by adding "SHARE_LOG=yes" to the command line. The URL is present at the very end of the process.

Full build logs?

https://github.com/armbian/build/pull/9724

Confirmed. From first glance it looks like dts files are missing.