I have searched the existing open and closed issues
Required Information
DietPi version | G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=11
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
Distro version | bookworm
Kernel version | Linux Opi5 6.1.84-vendor-rk35xx #1 SMP Sun Jan 5 09:09:31 UTC 2025 aarch64 GNU/Linux
Architecture | arm64
SBC model | Orange Pi 5 Max (aarch64)
Power supply used | 5V 4A
SD card used | Crucial P5 Plus NVME
Steps to reproduce
dietpi-config → Advanced options → Bluetooth [ON]
sudo bluetoothctl
show
Expected behaviour
Display BT controller info
Actual behaviour
Was seeing “no default controller”
Tried various tweaks found by searching for similar reports, now am seeing:
Waiting to connect to bluetoothd…
Extra details
Originally had serial ports disabled, then enabled (ttyS7)
And changed /dev/ttyBT0 to /dev/ttyS7 in sprd-bluetooth.service
since ls /dev/tty* did not list ttyBT0
So the missing ttyBT0 is probably root cause, but not sure why it’s not there.
so who knows if the stock kernel has the drivers for that particular chipset…or if they need to be built and then modprobed in at boot
Sparklan driver here
Maybe build a DKMS automatic module build when kernels get upgraded
Lol…I used duck.ai to generate a convoluted “howto”
Do not follow this simple and incorrect…but it get’s you in the “ballpark” I guess
User prompt 2 of 2 - 3/22/2025, 10:06:08 AM:
AP6611 dkms kernel module build for dietpi
GPT-4o mini:
To build the AP6611 DKMS kernel module on DietPi, you can follow these steps:
Update Your System: Make sure your DietPi system is up to date.
sudo apt update
sudo apt upgrade
Install Required Packages: You need to install DKMS and the kernel headers for your current kernel.
sudo apt install dkms linux-headers-$(uname -r)
Download the AP6611 Driver: You may need to download the driver source code for the AP6611. This can often be found on the manufacturer’s website or a repository like GitHub. For example:
git clone https://github.com/your-repo/ap6611.git
cd ap6611
Create a DKMS Configuration File: You need to create a DKMS configuration file. This is usually named dkms.conf and should be placed in the root of the driver source directory. Here’s a basic example of what it might look like: