# Raspberry Pi 400 Bluetooth Issue Workaround

**URL:** https://dietpi.com/forum/t/raspberry-pi-400-bluetooth-issue-workaround/24942
**Category:** Community Tutorials
**Tags:** raspberry-pi-4
**Created:** [4 February 2026 22:21 UTC](https://dietpi.com/forum/t/raspberry-pi-400-bluetooth-issue-workaround/24942 "2026-02-04T22:21:51Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![eschaton](https://dietpi.com/forum/user_avatar/dietpi.com/eschaton/32/8735_2.png) [@eschaton](https://dietpi.com/forum/u/eschaton)
#### Post date: [4 February 2026 22:21 UTC](https://dietpi.com/forum/t/raspberry-pi-400-bluetooth-issue-workaround/24942/1 "2026-02-04T22:21:51Z")

</div>

Just a quick note here that I am so happy to have found an issue which was plaguing me on DietPi for my Raspberry Pi 400: the bluetooth wasn’t working. No matter what I tried, it always seemed as though DietPi simply never saw that part of the hardware; it didn’t show up as a usable device at all.

It took me a while to find the answer; in the end someone else had already done the smart bits: [Raspberry PI 400 Bluetooth problem - Raspberry Pi Forums](https://forums.raspberrypi.com/viewtopic.php?t=304141).

I figure I’ll just lay out the quick fix here because I love this distro and I want to add this little bit of knowledge to its community:

Run `cd /etc; ln -s /usr/lib/firmware` in your terminal (you’ll need to have proper permissions) and then reboot. That’s it. The issue seems to be that later versions of Debian are looking for a path called “etc/firmware” when that doesn’t actually exist anymore. Aliasing it to “/usr/lib/firmware”, where the files it needs actually live now, does the trick.

I used bluetoothctl to verify; a good result should look like this:  
 ![image](https://dietpi.com/forum/uploads/default/original/2X/0/00ee4371cccacd88a11f539d935eea5c91739175.png)