sure thing, i booted from a default image and found the controller does pair and works just as before. it’s what lead me to looking into BlueZ as the possible issue. so it kinda looks like software not hardware.
was hoping to avoid a fresh install. it’s a system that’s been in daily use since v31 with over 30,000 games / assets / overlays etc. there’s a lot of customisations and other media that I’ve added over a few years. high scores too! lol.
my ASUS NUCs employ M.2 radios but the Intel’s use SMD’s which I find more difficult to relocate. so i tested the same process with the ASUS hardware and found that swapping the radios solved the problem. here’s what i did:
- installed/configured batocera 36 on asus nuc #1
- swapped ssd to identical nuc #2 and booted
- config works but no Bluetooth controller
- shutdown and swapped M.2 radio package (contains wifi and bluetooth interface)
- rebooted, controller paired with no additional action required, prior config applied
in my opinion it would appear that the Bluetooth stack may not be aware of the base hardware change. am not an expert but changing the hardware back just works.
thanks again for the advice however, I appreciate it.