Bug 8372 - [Package Request] dkms-hybrid-bcm
: [Package Request] dkms-hybrid-bcm
Status: RESOLVED WORKSFORME
Product: Desktop Bugs
Classification: ROSA Desktop
Component: Package Requests
: Fresh
: All Linux
: Normal normal
: ---
Assigned To: ROSA Linux Bugs
: ROSA Linux Bugs
https://www.broadcom.com/support/down...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-29 17:44 MSD by Zombie Ryushu
Modified: 2017-09-30 18:33 MSD (History)
3 users (show)

See Also:
RPM Package: dkms-hybrid-bcm
ISO-related:
Bad POT generating:
Upstream:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zombie Ryushu 2017-09-29 17:44:48 MSD
I request that the dkms-hybrid-bcm driver be imported into Rosa as a DKMS module if that is all possible


These packages contain Broadcom's IEEE 802.11a/b/g/n hybrid Linux.. device driver for use with Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware. There are different tars for 32-bit and 64-bit x86 CPU architectures. Make sure that you download the appropriate tar because the hybrid binary file must be of the appropriate architecture type. The hybrid binary file is agnostic to the specific version of the Linux. kernel because it is designed to perform all interactions with the operating system through operating-system-specific files and an operating system abstraction layer file. All Linux. operating-system-specific code is provided in source form, making it possible to retarget to different kernel versions and fix operating system related issues. NOTE: You must read the LICENSE.TXT file in the lib directory before using this software. Support questions for the latest version of these drivers may be directed to linux.-wlan-client-support-list@broadcom.com.

https://www.broadcom.com/support/download-search/?pf=Wireless+LAN+Infrastructure
Comment 1 Zombie Ryushu 2017-09-29 17:45:58 MSD
This module will be considered non-Free.
Comment 2 Eugene Shatokhin 2017-09-29 18:32:15 MSD
We already have it: https://abf.io/import/broadcom-wl. The package is called dkms-broadcom-wl.

It is even included into our ISO images.
Comment 3 Zombie Ryushu 2017-09-29 18:52:39 MSD
It has been tried with that driver, and the driver does not power the Bluetooth Aspect of the card, only its 802.11 aspect.
Comment 4 Zombie Ryushu 2017-09-29 18:54:24 MSD
Is it possible that a version bump to another newer edition of the driver may be required to get the Bluetooth Aspect working?
Comment 5 Eugene Shatokhin 2017-09-29 19:29:48 MSD
(In reply to comment #4)
> Is it possible that a version bump to another newer edition of the driver
> may be required to get the Bluetooth Aspect working?

No. We already have the latest version and a number of patches on top of that, similar to what Ubuntu has.
Comment 6 Zombie Ryushu 2017-09-29 19:46:42 MSD
How do you reccomend I proceed?
Comment 7 Eugene Shatokhin 2017-09-30 18:33:55 MSD
(In reply to comment #6)
> How do you reccomend I proceed?

I don't know what you have already done to investigate the issue. When I dig into something like that, I usually do the following first.

0. Remove the proprietary driver (dkms-broadcom-wl), reboot and see how the system works without it.

1. Check if the device is recognized (see dmesg and the output of lspci -vnn). The system may or may not see the bluetooth module as a separate device even if it is physically on the same chip as WiFi.

Using hw-probe to upload the data to linux-hardware.org helps too - web UI makes it easier to see the logs there.

2. Check if Bluetooth is enabled in BIOS and by a hardware switch (if the laptop has that). In one of the cases I debugged, the Bluetooth was disabled in BIOS but the system saw the device somehow, although it could now use it.

3. Check dmesg for the complaints about firmware (and probably other Bluetooth-related errors).
Another common problem with the combined WiFi+Bluetooth modules is that some of these require separate firmware files for WiFi and Bluetooth.

4. See what 'rfkill list' shows. If the device is marked as soft-blocked, try 'rfkill unblock all'.

5. Try the newest available kernel. For ROSA R9 x64, we also have kernels 4.13.0-x based on the sources from Ubuntu: http://abf-downloads.rosalinux.ru/kernels_stable_personal/repository/rosa2016.1/x86_64/kernel_desktop_4_13/release/

These kernels may have better support for some hardware than our stock kernels.

Here is the build of broadcom-wl (currently - in QA) suitable for these newer kernels: https://abf.io/build_lists/2892713

If nothing of the above gives a clue about the problem, trying some other recent Linux distro (e.g. Ubuntu 17.10) in Live mode may also help.