Linux NanoSauna 6.12.57-current-sunxi #1 SMP Sun Nov 2 13:15:23 UTC 2025 armv7l GNU/Linux
Architecture | dpkg --print-architecture
armhf
SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
NanoPi NEO Air (armv7l)
Power supply used | (EG: 5V 1A RAVpower)
5V 1A RAVpower
SD card used | (EG: SanDisk ultra)
SanDisk Ultra 32GB
Additional Information (if applicable)
Software title | (EG: Nextcloud)
systemctl status bluetooth
Was the software title installed freshly or updated/migrated?
Fresh installation
Can this issue be replicated on a fresh installation of DietPi?
Yes, I have 2 NanoPi Neo Air's both acts same way
← If you sent a “dietpi-bugreport”, please paste the ID here →
Bug report ID | echo $G_HW_UUID
42c47349-19cf-45bb-9307-e27f385027d6
Steps to reproduce
…
dietpi-config -> enable bluetooth
systemctl status bluetooth
root@NanoSauna:~# systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Active: active (running) since Sun 2025-11-30 18:52:43 EET; 3min 15s ago
Invocation: 8f784919a7ad4a77b7a0e345cc8627db
Docs: man:bluetoothd(8)
Main PID: 8196 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 875)
Memory: 900K (peak: 1.8M)
CPU: 214ms
CGroup: /system.slice/bluetooth.service
└─8196 /usr/libexec/bluetooth/bluetoothd
Nov 30 18:52:43 NanoSauna systemd[1]: Starting bluetooth.service - Bluetooth service...
Nov 30 18:52:43 NanoSauna (uetoothd)[8196]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Nov 30 18:52:43 NanoSauna bluetoothd[8196]: Bluetooth daemon 5.82
Nov 30 18:52:43 NanoSauna bluetoothd[8196]: Starting SDP server
Nov 30 18:52:43 NanoSauna bluetoothd[8196]: profiles/network/bnep.c:bnep_init() kernel lacks bnep-protocol support
Nov 30 18:52:43 NanoSauna systemd[1]: Started bluetooth.service - Bluetooth service.
Nov 30 18:52:43 NanoSauna bluetoothd[8196]: Bluetooth management interface 1.23 initialized
Nov 30 18:53:29 NanoSauna systemd[1]: Started bluetooth.service - Bluetooth service.
root@NanoSauna:~# hcitool dev
Devices:
root@NanoSauna:~# rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
root@NanoSauna:~#
Expected behaviour
Bluetooth-command hcitool lescan or dev should work like on older DietPi version.
Older version, same HW (NanoPi Neo Air):
miha@Vardel:~$ uname --all
Linux Vardel 6.6.44-current-sunxi #1 SMP Sat Aug 3 06:54:42 UTC 2024 armv7l GNU/Linux
miha@Vardel:~$ hcitool dev
Devices:
hci0 50:41:1C:83:09:CB
miha@Vardel:~$ cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=11
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
Tried with, in total, THREE different NanoPi Neo Air’s and each time BT fails to work. Unfortunately older DietPi-versions are no longer available for DL, with older versions the BT worked perfectly.
[Sun Dec 28 13:42:49 2025] systemd[1]: Started systemd-journald.service - Journal Service.
[Sun Dec 28 13:42:49 2025] EXT4-fs (mmcblk0p1): re-mounted 98784886-2490-4836-abf1-c885d61bae95 r/w.
[Sun Dec 28 13:42:50 2025] Adding 1602556k swap on /var/swap. Priority:-2 extents:13 across:1703936k SS
[Sun Dec 28 13:42:51 2025] random: crng init done
[Sun Dec 28 13:42:51 2025] systemd-journald[233]: Received client request to flush runtime journal.
[Sun Dec 28 13:42:52 2025] ------------[ cut here ]------------
[Sun Dec 28 13:42:52 2025] WARNING: CPU: 1 PID: 295 at net/rfkill/core.c:999 rfkill_alloc+0xdd/0xec [rfkill]
[Sun Dec 28 13:42:52 2025] Modules linked in: rfkill_gpio(+) rfkill cpufreq_dt uio_pdrv_genirq uio nfnetlink ip_tables x_tables autofs4 sunxi phy_generic pwrseq_simple
[Sun Dec 28 13:42:52 2025] CPU: 1 UID: 0 PID: 295 Comm: (udev-worker) Not tainted 6.12.58-current-sunxi #1
[Sun Dec 28 13:42:52 2025] Hardware name: Allwinner sun8i Family
[Sun Dec 28 13:42:52 2025] Call trace:
[Sun Dec 28 13:42:52 2025] unwind_backtrace from show_stack+0x11/0x14
[Sun Dec 28 13:42:52 2025] show_stack from dump_stack_lvl+0x37/0x42
[Sun Dec 28 13:42:52 2025] dump_stack_lvl from __warn+0xbf/0xe8
[Sun Dec 28 13:42:52 2025] __warn from warn_slowpath_fmt+0x113/0x118
[Sun Dec 28 13:42:52 2025] warn_slowpath_fmt from rfkill_alloc+0xdd/0xec [rfkill]
[Sun Dec 28 13:42:52 2025] rfkill_alloc [rfkill] from rfkill_gpio_probe+0x11b/0x184 [rfkill_gpio]
[Sun Dec 28 13:42:52 2025] rfkill_gpio_probe [rfkill_gpio] from platform_probe+0x43/0x80
[Sun Dec 28 13:42:52 2025] platform_probe from really_probe+0x91/0x280
[Sun Dec 28 13:42:52 2025] really_probe from __driver_probe_device+0x69/0x160
[Sun Dec 28 13:42:52 2025] __driver_probe_device from driver_probe_device+0x31/0x94
[Sun Dec 28 13:42:52 2025] driver_probe_device from __driver_attach+0x8d/0x128
[Sun Dec 28 13:42:52 2025] __driver_attach from bus_for_each_dev+0x4f/0x88
[Sun Dec 28 13:42:52 2025] bus_for_each_dev from bus_add_driver+0xb7/0x180
[Sun Dec 28 13:42:52 2025] bus_add_driver from driver_register+0x3d/0xa8
[Sun Dec 28 13:42:52 2025] driver_register from do_one_initcall+0x3d/0x1b4
[Sun Dec 28 13:42:52 2025] do_one_initcall from do_init_module+0x45/0x190
[Sun Dec 28 13:42:52 2025] do_init_module from init_module_from_file+0x5f/0x88
[Sun Dec 28 13:42:52 2025] init_module_from_file from sys_finit_module+0x153/0x23c
[Sun Dec 28 13:42:52 2025] sys_finit_module from __sys_trace_return+0x1/0xc
[Sun Dec 28 13:42:52 2025] Exception stack(0xe0c8dfa8 to 0xe0c8dff0)
[Sun Dec 28 13:42:52 2025] dfa0: b56e8d73 00000000 00000017 b56ede10 00000000 024aa708
[Sun Dec 28 13:42:52 2025] dfc0: b56e8d73 00000000 51167900 0000017b 02497e90 024ac0a0 00000000 00000000
[Sun Dec 28 13:42:52 2025] dfe0: beae9638 beae9628 b56e96e9 b6b73312
[Sun Dec 28 13:42:52 2025] ---[ end trace 0000000000000000 ]---
[Sun Dec 28 13:42:52 2025] rfkill_gpio rfkill_bt: probe with driver rfkill_gpio failed with error -12
[Sun Dec 28 13:42:52 2025] mc: Linux media interface: v0.10
[Sun Dec 28 13:42:52 2025] videodev: Linux video capture interface: v2.00
[Sun Dec 28 13:42:52 2025] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[Sun Dec 28 13:42:52 2025] lima 1c40000.gpu: gp - mali400 version major 1 minor 1
[Sun Dec 28 13:42:52 2025] lima 1c40000.gpu: pp0 - mali400 version major 1 minor 1
[Sun Dec 28 13:42:52 2025] lima 1c40000.gpu: pp1 - mali400 version major 1 minor 1
[Sun Dec 28 13:42:52 2025] lima 1c40000.gpu: l2_cache0 64K, 4-way, 64byte cache line, 64bit external bus
[Sun Dec 28 13:42:52 2025] sunxi_cedrus: module is from the staging directory, the quality is unknown, you have been warned.
[Sun Dec 28 13:42:52 2025] lima 1c40000.gpu: bus rate = 200000000
[Sun Dec 28 13:42:52 2025] lima 1c40000.gpu: mod rate = 297000000
[Sun Dec 28 13:42:52 2025] lima 1c40000.gpu: Failed to register cooling device
[Sun Dec 28 13:42:52 2025] [drm] Initialized lima 1.1.0 for 1c40000.gpu on minor 0
[Sun Dec 28 13:42:52 2025] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[Sun Dec 28 13:42:52 2025] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[Sun Dec 28 13:42:52 2025] cedrus 1c0e000.video-codec: Device registered as /dev/video1
[Sun Dec 28 13:42:52 2025] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[Sun Dec 28 13:42:53 2025] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[Sun Dec 28 13:42:53 2025] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2021 01:12:21 version 7.45.98.118 (7d96287 CY) FWID 01-32059766
[Sun Dec 28 13:42:54 2025] warning: `iwconfig' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[Sun Dec 28 18:06:21 2025] Bluetooth: Core ver 2.22
[Sun Dec 28 18:06:21 2025] NET: Registered PF_BLUETOOTH protocol family
[Sun Dec 28 18:06:21 2025] Bluetooth: HCI device and connection manager initialized
[Sun Dec 28 18:06:21 2025] Bluetooth: HCI socket layer initialized
[Sun Dec 28 18:06:21 2025] Bluetooth: L2CAP socket layer initialized
[Sun Dec 28 18:06:21 2025] Bluetooth: SCO socket layer initialized
[Sun Dec 28 18:06:21 2025] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[Sun Dec 28 18:06:21 2025] Bluetooth: BNEP filters: protocol multicast
[Sun Dec 28 18:06:21 2025] Bluetooth: BNEP socket layer initialized
[Sun Dec 28 18:06:21 2025] Bluetooth: RFCOMM TTY layer initialized
[Sun Dec 28 18:06:21 2025] Bluetooth: RFCOMM socket layer initialized
[Sun Dec 28 18:06:21 2025] Bluetooth: RFCOMM ver 1.11
[Sun Dec 28 18:06:21 2025] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[Sun Dec 28 18:06:21 2025] Bluetooth: HIDP socket layer initialized
Hmm, an rfkill-related kernel module fails to load. But it should not be needed if no locks are enabled .
[Sun Dec 28 13:42:52 2025] warn_slowpath_fmt from rfkill_alloc+0xdd/0xec [rfkill]
[Sun Dec 28 13:42:52 2025] rfkill_alloc [rfkill] from rfkill_gpio_probe+0x11b/0x184 [rfkill_gpio]
[Sun Dec 28 13:42:52 2025] rfkill_gpio_probe [rfkill_gpio] from platform_probe+0x43/0x80
Bottom-up is the chronologic direction.
Bluetooth is internally attached via UART3 pins: Making sure you're not a bot!
So the rfkill_gpio module makes sense. You have no potentially conflicting overlay enabled, do you?
Are there any other kernel errors or output related to this?
dmesg -l 0,1,2,3
dmesg | grep rfkill
Amd reloading that driver throws the same call trace, right?
.