Active threads

I built an unofficial Armbian 6.12.51 (Noble) image using the build tool: Armbian-unofficial_25.11.0-trunk_Nanopiduo_noble_current_6.12.51.img I am trying to get the micro-USB port to work as a USB serial gadget (g_serial / libcomposite). What I have done / observed: g_serial and libcomposite modules are loaded: lsmod | grep g_serial g_serial 12288 0 libcomposite 49152 2 g_serial,usb_f_acm ConfigFS is mounted: mount | grep configfs configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) UDC exists: ls /sys/class/udc/ musb-hdrc.2.auto Gadget folder does not exist: ls /sys/kernel/config/usb_gadget/ # output: empty Trying to manually bind a gadget fails: echo musb-hdrc.2.auto | sudo tee /sys/kernel/config/usb_gadget/g1/UDC # Output: tee: UDC: Device or resource busy Current UDC mode: cat /sys/class/udc/musb-hdrc.2.auto/device/mode b_idle There is no /sys/class/usb_role/usb0/role available to force device mode. This setup works fine on Jammy kernel, same cable, same SD card rootfs. Problem: The OTG controller comes up in b_idle mode, preventing the USB gadget from binding. /dev/ttyACM0 never appears on the host PC. It seems like the device tree / overlay for Noble 6.12.51 is not configuring the OTG port for peripheral mode. What I want: USB serial gadget (g_serial) working over the micro-USB port on Noble 6.12.51 build. Any advice on the correct overlay or device tree modification needed to bring the OTG port into device mode at boot. Extra info: CONFIG_USB_CONFIGFS_SERIAL=y in kernel CONFIG_USB_LIBCOMPOSITE compiled as module Micro-USB cable confirmed working with Jammy kernel Modules: libcomposite, g_serial, usb_f_acm present Thanks in advance for guidance!

Thanks! For @Victor Picinin the temporary working URl is https://stpete-mirror.armbian.com/users.armbian.com/jock/web/rk322x/armbian/beta/Armbian-unofficial_24.11.0-trunk_Rk322x-box_noble_current_6.6.56_xfce_desktop.img.xz

I probably better wait on it, that looks above my skill set unfortunately, I consider myself just a novice user. I can handle burning and image and booting it, if it's fairly straightforward, but I probably shouldn't dig myself any deeper for now LOL I'll be on standby in case anything ever changes or becomes easier in the process!

What version of the kernel is being installed? As yet ZFS only supports up to 6.16.

Thank's for your prompt reply. Attached, you'll find the logs. SD boot fails with Armbian image on SD : bootlogM5Armbian.log SD boot success with ubuntu 20.4 (provided by BPI site) on SD : bootlogM5BPIUbuntu.log Regards Guy bootlogM5Armbian.log bootlogM5BPIUbuntu.log

i too am facing this problem, i bought this box for round 1500 inr with armbian in mind i thought it would be h3 but it was h313 and then i also noticed that the fonts looked different on the soc, well here i am. the main purpose for this purchase was installing armbian to run home assistant server but that aint gonna happen and raspberry pi's and other alternatives are too expensive still not what i bought it for but yeah gotta live with it now btw any updates on this

Hello community Here are the versions I’m using: Kernel: 5.15.48-sunxi OS: Linux nanopineo 5.15.48-sunxi #22.05.3 SMP Wed Feb 19 15:56:03 UTC 2025 armv7l GNU/Linux I’m having a problem. Sometimes, during boot, I see the following log: After this message, the system halts. The only way to fix it is to flash the image again or to boot from an SD card and mount the EMMC which fixes the file system. I noticed that the device doesn’t use the overlay_prefix variable from /boot/armbianEnv.txt. It shows this message: I tried adding the overlay_prefix variable manually in the boot.cmd file, but it didn’t help. Previously, I changed: to Could that be the cause? I changed it back to default but the problem still happens. Do you have any ideas what could be wrong?

I think it's easier than that. I looked into the postinst file for kernel headers on my Ubuntu machine, and I found this: #!/bin/sh set -e version=6.17.0-7-generic if [ "$1" != configure ]; then exit 0 fi if [ -d /etc/kernel/header_postinst.d ]; then DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error --arg=$version \ /etc/kernel/header_postinst.d fi exit 0 The postinst script for the headers package doesn't have anything similar, so we should add it this part related to execute the scripts under `/etc/kernel/header_postinst.d`. Can you do that or should we add someone else to the discussion? EDIT: Debian does something similar. Same goal, just a different code: #!/bin/sh -e version=6.12.48+deb13-amd64 linux-run-hooks headers postinst $version -- "$@" exit 0

Yes That's on us

@Jeeva Kandasamy it’s on this page https://github.com/NickAlilovic/build/tree/v20250306

Latest compile for odroid xu4 does have a desktop. Any reason why?

Same answer and further reasoning as here:

better in which way? performance? driver support? size? from our pov the better the support conditions, the more likely to recommend. https://www.armbian.com/download/?device_support=Standard support Is one platinum? Go for it? If not, check standard support. If one is in this category, go for it. If not, check further down for community support.

I think the upstream kernel has fixed it recently. Could your try the patch? https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a28352cf2d2f8380e7aca8cb61682396dca7a991

Thank you for the answer. @Nick A

Thanks let me try that

Agreed. A check if the package is installed (and if not install it beforehand) would be sufficient too. PRs to fix this are highly appreciated. https://github.com/armbian/build/blob/main/packages/bsp/common/usr/bin/armbian-install

I suggest to retry later

Any comments on this would be welcome.

You'll spend the money once. Then you'll have the result thereafter. I would suggest deciding what you want, then spending whatever it costs. Orange PI is "cheap", not just in price, but in hardware reliability as well as software support. I'm not aware of such issues with Radxa. RK3588 is more powerful than Raspberry PI, but as you say Raspberry PI has great community and support. Perhaps the question is - What do you need it for? Raspberry PI might be powerful enough for your needs.

I have an Orange PI 5 Plus, and both USB-C connectors (including the one used for power delivery) are faulty. Also the second HDMI output is corrupted. Clearly their manufacturer leaves a lot to be desired.

sudo rm -rf /var/lib/apt/lists/* sudo apt clean sudo apt update sudo apt upgrade works for me.

Thank you for your quick answer, Jimbolaya. Yes, I did try different cables all with the same result. I wonder if there is another way to access the serial console, J13 perhaps? Albeit with some required soldering, I suppose. Then remains the question of which headers exactly relate to GND, TX and RX.

I noticed this problem a long time ago, but now I feel it is important to fix it: I get a slim black bar on the left side, and a portion of the pixels on the right get "cropped" because they don't fit in the LCD display area? Do you get the same in your LCD? Do you know a way to fix it? I am talking about this LCD: RED PCB LCD https://www.aliexpress.us/item/3256802847521952.html?

Update: It works now, however the power LED doesn't seem to light up, but the video card is detected in /dev