Re: ntrollIf Network Controller Chipset handles Wi-Fi, then shouldn't it handle Bluetooth too? Advice required on "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" for controlling Laptop Bluetooth unit and devices
On Sat, Oct 21, 2023 at 08:18:30AM +0530, Susmita/Rajib wrote:
> To,
> The Team User,
> debian-user@lists.debian.org,
> Debian.org
>
> My dear illustrious Team Leaders,
>
> Good morning.
>
> May please my first post at
> https://lists.debian.org/debian-user/2019/10/msg00493.html with the
> subject, "Appears to be a problem with Debian Stretch 9.11.0 regarding
> WAN non-allocation ..." be perused.
>
Hi Rajib,
> Following the short post by Mr. Curt at:
> https://lists.debian.org/debian-user/2019/10/msg00497.html, a solution
> was found and the Complete Solution was posted at:
> http://forums.debian.net/viewtopic.php?f=7&t=143930
>
The above posts don't give much information. As requested beFore, please
don't refer to forum posts without giving the information here on the
mailing list.
> In Brief:
> I used Debian wiki page of wl. Added the sources.list line:
> deb http://deb.debian.org/debian bullseye contrib non-free
> Updated. Uninstalled broadcom installed package. Installed
> broadcom-sta-dkms package.from synaptic. After the rest steps the
> Wi-Fi worked, and works, perfectly.
>
> For example:
>
> (1) # dmesg | grep -e "wl"
>
> [output]
> [ 0.000000] DMI: Hewlett-Packard HP Notebook/80C4, BIOS F.02 03/24/2015
> [ 15.567967] wl: loading out-of-tree module taints kernel.
> [ 15.567973] wl: module license 'MIXED/Proprietary' taints kernel.
> [ 15.571378] wl: module verification failed: signature and/or
> required key missing - tainting kernel
> [ 15.607781] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless
> Controller 6.30.223.271 (r587334)
> [ 15.751248] wl 0000:04:00.0 wlp4s0: renamed from wlan0
> [ 44.867147] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [ 436.593766] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [ 7107.206153] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [10536.901498] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [10791.043627] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [17994.815848] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [/output]
>
I'm assuming that you are using Debian 11 bullseye.
Check your /etc/apt/sources.list file - I assume that it has main contrib and
non-free.
The usual method of installing broadcom wifi firmware has been to use the
b43-fwcutter package I think.
e (2) # dmesg | grep -e "bluetooth"
>
> [output]
> [ 17.284222] bluetooth hci0: firmware: failed to load
> brcm/BCM43142A0-0a5c-216d.hcd (-2)
> [ 17.284331] bluetooth hci0: firmware: failed to load
> brcm/BCM-0a5c-216d.hcd (-2)
> [ 6815.629661] bluetooth hci0: firmware: failed to load
> brcm/BCM43142A0-0a5c-216d.hcd (-2)
> [ 6815.629675] bluetooth hci0: firmware: failed to load
> brcm/BCM-0a5c-216d.hcd (-2)
> [/output]
>
> # dmesg | grep -e "broadcom" has not output.
>
> With my inability to pair my bluetooth headphone following
> instructions at https://wiki.debian.org/BluetoothUser,
> /usr/share/doc/bluez/README.Debian.gz and installing the necessary
> packages, like bluetooth, bluez and blueman my doubt again arises.
>
> So my Necessary Question: Has the broadcom and wl created a
> conflicting situation?
>
Possibly, yes. I would suggest getting hold of the broadcom firmware using
the b43 package. For various reasons, the original Broadcom firmware is not
distributable by Debian - the fwcutter downloads a file and extracts the
requisite firmware
You might find it worthwhile to update to Debian 12 bookworm at some point.
The installer includes most firmware and you can adapt the apt/sources.list
to include the non-free firmware repository but I think the B43 series
firmware can still not be included directly.
> Best wishes,
> Rajib
> Etc.
>
With every good wish,
Andy Cater
Reply to: