After updates bluetooth sound stops running very frequently. “rfkill” shows bluetooth is now blocked. bluetooth manager shows a red X.
“rfkill unblock bluetooth” unblocks bluetooth. After a reboot bluetooth sound starts again. The stopping of bluetooth has been correlated to the install of any new broadcom module. A broadcom module update seems, strangely, to be almost a daily occurrence.
Questions are:
Why does update of a broadcom module “block” bluetooth?
Why is a broadcom module in the updates almost daily, i.e., 4 of the last 5 days in recent history?
@tckosvic It’s not from a standard repository, ask the third party provider…
Good point. Never looked at where it came from. It is uploaded from packman as I now see.
I will get info to the developer.
thanks, tom kosvic
And just to prove me wrong, there was another broadcom module updated today and bluetooth kept working. There was no reboot required by this update. FYI the network card on my ASUS mb is by broadcom.
I guess my correlation was inaccurate. I thought the info might help anyone else with frequent bluetooth issues but now maybe not.
Still don’t know why there is a broadcom update nearly every day. They can’t be doing that much work on their code. I think they are, somehow, getting their nightly builds into packman repo as an update
tom kosvic
@tckosvic you need to define what packages are being updated… nothing has changed in 8 months for the likes of broadcom-wl.
Likewise, if it’s an issue you need to follow up on their Mailing List…