schwar3kat

orangepi-r1plus-lts works. iperf values as expected: Armbian_22.11.0_Orangepi-r1plus-lts_jammy_current_5.15.79.img.xz Armbian_22.11.0_Orangepi-r1plus-lts_bullseye_current_5.15.79.img.xz RC testing form submitted

Using Armbian build: If creating a patch for u-boot, the dts will go in build/cache/sources/u-boot/v2022.07/arch/arm/dts/ Or similar depending on uboot version. If creating a patch for kernel, the dts will go in build/cache/sources/linux-mainline/6.0/arch/arm64/boot/dts/rockchip/ Or similar depending on kernel version and architecture. Don't forget to modify the Makefile's

orangepi-r1 works. iperf values as expected: Armbian_22.11.0_Orangepi-r1_jammy_current_5.15.79.img.xz Armbian_22.11.0_Orangepi-r1_bullseye_current_5.15.79.img.xz RC testing form submitted

orangepizeroplus works: Armbian_22.11.0_Orangepizeroplus_jammy_current_5.15.79.img.xz Armbian_22.11.0_Orangepizeroplus_bullseye_current_5.15.79.img.xz RC testing form submitted

This topic may be of interest. It sounds similar to your issue. Perhaps ask how what they solved it and if it fixes the HDMI and WiFi. Perhaps you can get the DTB from them and try it on your board. Seems that there might be other boards with the same issue... if this is the same issue. It seems that there are different variants of the boards, and that AXP805 regulator control is different. I see a solution for the above problem for a different board here. It's a device tree change to use i2c instead of RSB. https://github.com/armbian/build/pull/3964

You could perhaps use armbian-config System Nightly switch to the nightly build to see if the issues have been fixed.

Hi Gabriel, I just checked the config for your legacy kernel. CAN is not available, nor is the driver. I suspect that you will need to use current kernel for this driver. You can search these forums to see if there are issues with the current kernel and if there are perhaps ways to get it working. It may be that issues with the new kernel have not been resolved for your board, or you may find that someone has got it working. If you want to learn and get involved then the Armbian build system is an ideal platform for you to develop solutions, providing an easy way to apply patches and stream improvements into the build via Github pull requests. I don't have your board, so won't be of much help.

You appear to be using a legacy kernel and a custom build. Where did you get it? It is unlikely that legacy kernels support gs_usb otb. I don't know of a way to add this after compile. I suggest that you try https://www.armbian.com/orange-pi-zero-2/ Armbian 22.05 Jammy Kernel 5.15.y

Hi Gabriel, You haven't given much information.... I don't own the same board as you and I know nothing about your CAN module. The current Armbian builds include the kernel gs_usb driver module which is apparently required for your CAN module. If you are using a current build then it is probable that you can activate the kernel driver module with "sudo modprobe gs_usb". This should enable the module, unless it needs some options configured (Google it). To confirm that the driver is loaded "sudo modprobe gs_usb --first-time" should return "modprobe: ERROR: could not insert 'gs_usb': Module already in kernel" After this you should be able to use the driver. Not required.... but using the Armbian build system, it is possible to include the driver module permanently into the kernel if you compile it after modifying CONFIG_CAN_GS_USB=m to CONFIG_CAN_GS_USB=y in your board's kernel config file. If you did this then it wouldn't need modprobe to activate it. Good luck Kat