Search Criteria
Package Details: bcm4350c5-firmware 1201710-8
Package Actions
Git Clone URL: | https://aur.archlinux.org/bcm20702a1-firmware.git (read-only, click to copy) |
---|---|
Package Base: | bcm20702a1-firmware |
Description: | Broadcom bluetooth firmware for BCM4350C5 based devices. |
Upstream URL: | http://asus.com |
Licenses: | custom |
Conflicts: | bcm4350-firmware |
Submitter: | Sonic-Y3k |
Maintainer: | None |
Last Packager: | Sonic-Y3k |
Votes: | 44 |
Popularity: | 0.083869 |
First Submitted: | 2015-10-10 09:48 (UTC) |
Last Updated: | 2017-07-10 18:12 (UTC) |
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 Next › Last »
RogueGirl commented on 2021-05-19 01:01 (UTC)
I tried it, it works fine there's no 404, the problem might be duo to their network or something
ulidtko commented on 2021-05-13 14:58 (UTC)
Worked great for me despite the outdated flag. Has turned this kernel log:
into this:
Following that, bluetooth A2DP has been rolling flawlessly for hours, while I couldn't hear two songs without bluetooth dropping out before. Thanks a lot!
DiV21dSREL commented on 2021-02-10 07:18 (UTC)
This package tries to install a range of bcm firmware packages. I only needed the
bcm20702a1
package - the other, later 4X-series ones, were already installed. However, if any of the packages are already present in /lib/firmware/brcm/, the installation fails. By manually commenting out the other firmware packages, such that I was left withpkgname=('bcm20702a1-firmware')
only on line 5 ofPKGBUILD
, everything worked.Perhaps a protection against partially-installed packages should be added?
(many thanks, this was exactly what I needed to get my headset microphone working with an old bt adapter, by the way!)
mirh commented on 2021-01-29 21:34 (UTC)
Sounds like this problem? https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1859223
MasinAD commented on 2021-01-27 19:50 (UTC)
I don't get HSP working. I have a BCM20702A0 based chip (Dell Latitude E6430 integrated USB Bluetooth adapter, USB ID 413c:8197). I don't know if a firmware would change anything with my problem. I fetched the driver package from Dell, unpacked it and found a lot of BCM20702A0.*.hex files, similar to those in Asus's package.
To adapt your package to my needs I assume I'd need to put my hex files where the PKGBUILD would expect them. But in filelist.txt there are USB IDs at the beginning of each line, and my USB ID is already present for a BCM20702A1 hex file. I cannot see how the IDs and the filenames relate to each other. Is there some kind of secret knowledge? Try and error? Or don't I need those firmware files anymore because the A0 chip is supported by the kernel or linux-firmware package while the A1 and B0 chips are not? At least, neither HFP nur HSP work at the moment.
programegg commented on 2020-11-09 21:17 (UTC) (edited on 2020-11-09 21:28 (UTC) by programegg)
@Carlosgrr, its flagged because the PKGBUILD URL 404s sometimes. @ludwhe's link to
https://dlcdnets.asus.com/pub/ASUS/wireless/USB-BT400/DR_USB_BT400_${pkgver}_Windows.zip
is the current working URL and is also where the ASUS driver download webpage redirects to.Carlosgrr commented on 2020-11-08 13:37 (UTC)
I don't know the reason why this package was flagged as outdated, but I just tested my P8Z77-v Deluxe, (BCM20702A1) and the PKGBUILD worked perfectly. Kernel 5.9.6-arch1-1.
nTia89 commented on 2020-11-07 16:19 (UTC)
With latest kernel versions (starting from 5.9) have you experienced issues connecting Bluetooth devices?
Ilgaz commented on 2020-08-23 20:31 (UTC)
Also enables ID 0a5c:216c Broadcom Corp. BCM43142A0 Bluetooth Device (HP) . Thank you.
« First ‹ Previous 1 2 3 4 5 6 Next › Last »