View Issue Details
|Fixed in Version
|0007577: Bluetooth module does not load or work with latest kalipi-kernel on RPi4
The kernel packages dated after 5.4.83-20210516 do not load the bluetooth module on boot, output from 'lsmod|grep bluetooth' is empty. Manually loading hci_uart, 'sudo modprobe hci_uart' works in that it loads the hciuart and bluetooth modules. However starting hciuart service still errors, bluetooth service is able to start though. Unfortunately this still leaves system unable to pair any bluetooth devices. 'bluetoothctl devices' shows 'No default controller available'.
I thought the kali-2021.4 image would solve this issue but it exists there as well.
|Steps To Reproduce
Upgrade kalipi-bootloader, kalipi-kernel, kalipi-kernel-headers, kalipi-re4son-firmware to version past 5.4.83-20210516
In the meantime to keep my RPi4 'working' I have apt-mark hold the following packages
Output from dpkg --list on working system,
I am not technical enough to resolve this but will run any commands and upload output as requested to solve this issue.
Hm, let me look. We added back some dtbo files to the kernel that we had removed, but that shouldn't have affected the bluetooth functionality, but you're right, I can reproduce it here. I didn't re-check things after we added the dtbos back, but this was definitely working previously.
I went down a rabbit hole a week ago trying to solve it and came across this, https://github.com/Re4son/kalipi-firmware/releases/tag/20211127kali but I am not sure how that repo and kali itself are connected? I am not a programmer or kernel expert so I am not sure. But i thought the BCM43436 might have had something to do with Bluetooth? At least the date this was added seemed to be about the time Bluetooth on my RPi4 broke? But as I have said many times, I'm not sure.
No, that's the wireless firmware for the wireless device on the rpi zero 2 w. The bluetooth firmware comes from the bluez-firmware package.
Curious as to whether or not this is going to get resolved or should I just assume Kali and Bluetooth are a no go going forward?
The fix is to
sudo sed -I 's/ttyAMA0/serial0/g' /boot/cmdline.txt
echo 'dtparam=krnbt=on' | sudo tee -a /boot/config.txt
The other option would be to downgrade the boot loader package (kalipi-bootloader) to an older version and then apt-mark hold that version so it doesn't upgrade. They changed the serial device on us in it.
It will be in the next release which should be out soon. This fell through the cracks as I was on vacation when the bug report came in.
I tried your fix and then tried upgrading kalipi-kernel from 5.4.83-20210516 to the (latest) 5.4.83-20211204 but it errors. Let me know if I you want me to post the output from the sudo apt get upgrade kalipi-kernel. It is quite long.
Seems like I need to keep my apt-mark in place for kalipi-bootloader, kalipi-kernel, kalipi-kernel-headers and kalipi-re4son-firmware
Please do show the errors, I have not run into any - which fix did you try exactly? You should either do the sed and tee, OR downgrade boot loader, not both.
Here is exactly what I did,
After reboot, I did
Afterwards it looks like the kernel does not update.
I am going to keep my apt-mark hold for now
As a quick workaround, try rm-ing that file - /boot/overlays/dwc2.dtbo - I'll have to get with re4son to figure out why that diversion isn't in place to cause the error.
Ok, I rm'ed that file and get an error on another one.
Should I just keep rm'ing them until it works?
Yes, unfortunately. Is this a 2021.4 install that you are upgrading? I didn't think there was an upgrade after 2021.4, so is it a 2021.3 image that you started from so I can reproduce the issue here? (also please note down all of the dtbos that you need to remove)
Yes. I believe it was a 2021.3 image that I started from. Would this work if I started from a 2021.4 image? I think I can try that. Just want to keep all my settings if you know what I mean.
The bluetooth will still need the two commands above, it's fine to keep just rm-ing the files (alternatively, if you don't care enough... just rm -rf /boot/overlays)
Thanks for all your help. I went with the nuclear option of 'rm -rf /boot/overlays' and it worked. You can re-close this ticket.
I'll try switching to a 2021.4 base image. Any idea when to expect the 2022.1 image?
Duplicate of 0007480, why did you clone this issue?
|Issue generated from: 0007480
|Note Added: 0017124
|assigned => resolved
|reopened => duplicate
|duplicate of 0007480