Boardcon-Liuy

Hello, I am testing vendor kernel + Ubuntu 24.04 on my board and found an issue with the Bluetooth desktop application. The Bluetooth adapter itself works normally. After enabling Bluetooth from the desktop UI, hciconfig -a shows the Bluetooth device correctly. However, when I click the Bluetooth device in the Blueman interface to open the device window, the Blueman window becomes stuck and stops responding. The strange thing is that if I restart Blueman manually using: killall blueman-manager export DISPLAY=:0 blueman-manager the Bluetooth manager window opens normally, and device scanning works correctly. However, after closing it and trying to open the device window again from the desktop Bluetooth icon, the problem happens again. I also tested the Bluetooth function using bluetoothctl, and pairing/scanning operations work normally, so I believe the Bluetooth hardware, BlueZ service, and kernel driver are working correctly. Could this issue be related to the desktop session, XFCE login environment, DBus session, or Blueman autostart process? What would be the recommended way to debug this issue? Thanks

The network connection is confirmed to be normal. I can successfully download the kernel source using git clone, with a download speed of around 3–5 MB/s. However, during the Armbian build process, the kernel source fetching stage always fails. I have tried both full git mode and shallow clone mode, but neither can complete successfully. Is there any recommended solution for this issue? Is it possible to configure Armbian to reuse an existing local kernel source tree or adjust the kernel git download process? Thanks.

Hi, Got it. Thank you very much for your reply and guidance. Best regards.

Hello Armbian community, I am working on adding support for a new RK3568 board to Armbian. Besides the board support, there are some hardware-specific kernel driver patches, for example: - RS485 driver modifications - TP2815 related driver changes - GT9xx touchscreen driver changes - Other hardware-specific drivers These drivers are only required for this hardware platform. What is the recommended way to maintain these driver patches in Armbian? Should they be submitted together with the board support? Or should they be maintained separately and applied through: userpatches/kernel/rk35xx-vendor-6.1/ before building Armbian? How do other board maintainers usually handle hardware-specific kernel drivers? Thanks.