All Activity

@ebin-dev good idea, I can try that. For the moment I seem to have a stable system running 25.11.2 with the 6.12.58 kernel and the l2-cache and op1-opp patches loaded as kernel overlays. My use case for the Helios64 is as a NAS with OMV8 and ZFS. Who is the maintainer of this board now ? I'm happy to test images on my hardware and it would be good if the latest builds worked out of the gate without having to patch them.

@Werner The overlay solution worked - thank you ! Is armbian-add-overlay a separate package/command ? I managed to enable it by creating a rockchip-rk3588-usb-host.dts file in the /boot//dtb-7.0.5-edge-rockchip64/rockchip/overlay folder, compiling it to ockchip-rk3588-usb-host.dtbo with the device tree compiler (dtc) and then using armbian-config to enable the loading of the usb-host overlay.

I have just cleaned-up / changed (again) things w.r.t. network names for my Nanopi-R6C. Same as Nanopi-R4S, it has 'wan' and 'lan', where wan is on-chip ethernet and lan is external PCIe connected. Double check for the R4S, but I am almost sure. So a mainline kernel in principle just numbers them eth<x> depending on timing and other things. New kernel behavior is that the on-chip gets named end0 and for my Nanopi-R6C the external gets named enP3p49s0, as that represents how it is HW connected via PCI-e. That is 7.0.<x-flavor> generic distro kernel. Then Armbian has 2 udev rules to rename to wan? and lan?. That is where the problem was and is for me as I use various different bootloader/firmware. I removed those udev rules as I run standard main distros as well and I need the names for bridges and vlans etc future proof and I don't care about names wan and lan (not using it as router). But if you want to keep that naming, check bootloader version (U-Boot I guess for you) and also udev rules and maybe other patches for RK3399 and/or R4S.

@Werner Do you think Armbian Edge with Linux 7.1 is available and works on OrangePI RV2 already? If so I'd love to get that image. As I understand it the SoC's support has been fully mainlined in Linux 7. (By the way request to admin to lift my messaging quota. Will edit this request away in a few hours.) I just checked inside Armbian Imager, and Armbian Edge is not available there - the same two images as are on https://armbian.com/boards/orangepirv2 are in there, that's all.

Support for 7.1 has been merged yesterday https://github.com/armbian/build/pull/9784

I verified the overlay above working with diy kernel 7.1.0-rc1 and kernel 6.18.10 from apt repo.

@sven-ola Hi sven-ola! Thanks a ton for making RV2 work on Armbian! I'll go about trying to make an RV2 start for the first time shortly. Interfacing it via the serial port is fine, and equally fine is connecting it via HDMI and USB to screen and keyboard, right? As for boot media, will booting the Armbian Debian image from a USB storage device work out of the box or must I install some image on an onboard flash chip first, if so what's the URL to that? And then: Do you think it makes any sense for me to use the Armbian Edge which has kernel 6.19 right now, does it seem stable? If so can you provide an URL to it (upload it on armbian.org or mega.nz etc.) On SpaceMIT's mainlining page https://github.com/spacemit-com/linux/wiki#user-content-K1_SoC I see that the PCI support got an update in 6.19, would this be a reason to use Armbian Edge. This URL is linked: https://lore.kernel.org/all/20251013153526.2276556-1-elder@riscstar.com/ . I have no idea if this update has been backported to the 6.18 kernel used. The 6.19 and 6.18 kernels used, where are they taken from actually? At least for 6.18 I think the repo is https://github.com/jmontleon/linux-spacemit/ or https://github.com/spacemit-com/linux-k1x , do you use it? And for clarity, there is no Armbian with Linux 7.1 yet right? Otherwise just downloading the Armbian with 6.18 from https://armbian.com/boards/orangepirv2 . For CLI and packages and no desktop, the Debian flavour is preferable I guess. At this point do you think PCI and USB interfaces are stable in Armbian or Armbian Edge? Thanks!

OK, I checked and the USB port is already set to host: The USB-A port is still not functional, but - as said in my previous reply - the USB-C port is working fine.

Not really. The USB-C port does work, I actually connected an USB hub to be able to add a keyboard/mouse to the SBC and it worked without issue. I'll try this , thank you for the instructions. The USB-C port does work though if I connect a hub to it, I'm able to use the devices connected to the HUB without issue.

I prefer to stay on stable release. I updated an old version because of copy fail CVE . It's very strange that i'm the only one with this bug. Can I update only the uboot part?

After upgrading armbian to 26.2.1 with kernel 6.18.10 performances on WAN interface dropped to 20Mbps for a single TCP connection. The interface is end0, renamed from eth1, driver from ethtool -i is "st_gmac". I used armbian-config to rollback to kernel 6.12.58 and performances are ok now. Will it be fixed in the future kernels ?

Today I realized a higher version of zfs-dkms(2.4.1) was actually offered in the Armbian repository. So I entered the command below to upgrade zfs-dkms to 2.4.1 and it was successful:

Maybe because it's a "zombie" system with systemd removed and the monitor tools fails to address Here's the dmesg of current system https://paste.armbian.com/zuyaxiwugo.yaml

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

blank

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"; }; }; };

Thanks for your update. I checked rk3588-orangepi-5-plus.dtb after decompiling, it says: It seems line dr_mode = "otg" does On The Go, they seem to switched it from the 6.1.115-vendor-rk35xx dtb. What could be the use case? As I understand you can set it to dr_mode = "peripheral" ?

In mainline kernel 6.18 or above, the USB 2.0 port (and USB-C port) is configured as device mode. You can use following cmd to change to host mode to connect other USB devices, but you need to do it again after reboot. sudo bash -c "echo host > /sys/kernel/debug/usb/fc000000.usb/mode" It could be done by dtb overlay but there is no one available now.

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

No problem, just to let you guys know Everything else is working Cheers !

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.

Connecting a usb keyboard doesn't seem to work with 7.1 .. [ 2.836541] usb 7-1: new full-speed USB device number 2 using ohci-platform [ 3.024538] usb 7-1: device descriptor read/64, error -62 [ 3.304535] usb 7-1: device descriptor read/64, error -62 [ 3.596542] usb 7-1: new full-speed USB device number 3 using ohci-platform [ 3.780527] usb 7-1: device descriptor read/64, error -62 [ 4.076543] usb 7-1: device descriptor read/64, error -62 [ 4.180566] usb usb7-port1: attempt power cycle [ 4.372529] usb 7-1: new full-speed USB device number 4 using ohci-platform [ 4.780541] usb 7-1: device not accepting address 4, error -62 [ 4.964529] usb 7-1: new full-speed USB device number 5 using ohci-platform [ 5.372526] usb 7-1: device not accepting address 5, error -62 [ 5.372569] usb usb7-port1: unable to enumerate USB device

Search root for this motherboard. The device is tvbox Fobem Duo

Bleedingedge Kernel 7.1 rc2 fixed it [ 12.686942] panfrost fde60000.gpu: clock rate = 594000000 [ 12.686994] panfrost fde60000.gpu: bus_clock rate = 500000000 [ 12.710029] panfrost fde60000.gpu: mali-g52 id 0x7402 major 0x1 minor 0x0 status 0x0 [ 12.710053] panfrost fde60000.gpu: features: 00000000,00000df7, issues: 00000000,00000400 [ 12.710062] panfrost fde60000.gpu: Features: L2:0x07110206 Shader:0x00000002 Tiler:0x00000209 Mem:0x1 MMU:0x00002823 AS:0xff JS:0x7 [ 12.710070] panfrost fde60000.gpu: shader_present=0x1 l2_present=0x1