** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760108
Title:
Broadcom B43 Wireless Driver Not Functional after Update to Linux
Kernel 4.15
To manage notifications about this
Hey Pascal
I am using 4.15.0-36 but seeing the same issue with your packages, Driver
installs but no network gets scanned under wifi networks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760108
So after rebuilding from the 2 sources talked about above, I can now use
Linux Kernel 4.15.0-13 with the Broadcom network adapter working at last
!
[...]
wl:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing
Another feedback.
After rebuilding package bcmwl-kernel-source from source as a backport
from Bionic 18.04 I have no error on building dkms for linux kernel
4.15, as expected.
Although I still have errors on broadcom-sta for the same reason. So I
will rebuild from source as a backport from
Well, I think I have found the solution. Reading the changelog from
bcmwl source in Launchpad I see for the Bionic package:
https://launchpad.net/ubuntu/+source/bcmwl
bcmwl (6.30.223.271+bdcom-0ubuntu4) bionic; urgency=medium
* debian/dkms.conf.in, (LP: #1737744)
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760108
Title:
Broadcom B43 Wireless Driver Not Functional after Update to Linux
Kernel 4.15
To manage notifications
On Wed, Apr 04, 2018 at 02:04:05PM -, Pascal Mons wrote:
> Next thing I will try is purging and re-installing bcmwl-kernel-source
> package within kernel 4.15, as I installed it in kernel 4.13.
>
> I realized as well that package broadcom-sta-dkms was not installed and
> may have impaired the
Just a comment on your last guess:
The output I posted was really the output from lspci. I noticed as well
this was not the output I get on other kernels for this command. However
on other kernels all pci are claimed so the unclaimed status of one pci
may explain the different output.
Definitely
As for the UNCLAIMED issue, I think maybe you're confusing the output of
lspci and lshw? Because the part in the description which says UNCLAIMED
looks like lshw output and not lspci output.
The bcmwl-kernel-source driver does need updates for 4.15. This will be
done before 4.15 becomes the hwe
Furthermore I would like to know what driver I should use and which to
keep blacklisted. On this webpage:
https://wiki.archlinux.org/index.php/broadcom_wireless
I see the following:
Device inaccessible after kernel upgrade
Since the 3.3.1 kernel the bcma
That's not really the case. For more information on the situation of
Broadcom drivers on my system I will refer you to my Ask Ubuntu
question:
https://askubuntu.com/questions/1012880/suddenly-the-wi-fi-broadcom-5
-ghz-interface-is-shown-out-of-range-permanently/1021178#1021178
You are true that
Okay, so you've installed the bcmwl-kernel-source package and that's the
driver being used with 4.13 (and likely it did blacklist bcma). I
suspect that when you install hwe-edge or the 4.16 kernel you got some
messages about the dkms build for the driver failing, but perhaps you
didn't notice
I don't know how to add a tag on a Bug Report ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760108
Title:
Broadcom B43 Wireless Driver Not Functional after Update to Linux
Kernel 4.15
To
After some deciphering I see that on the Network controller I get:
Capabilities:
Kernel modules: bcma
May it's blacklisted somewhere and upon proper action, I can get a fully
functional Wi-Fi in Kernel 4.16.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Well, I did test the Mainline Build Kernel 4.16 as suggested. Here are
the results:
$ lspci
00:00.0 Host bridge: Intel Corporation Device 3ec2 (rev 07)
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07)
00:08.0 System peripheral: Intel Corporation Sky Lake Gaussian
In addition if I had 'something' blacklisting the module I would find
very strange that it would not do so with Kernel 4.13 ... While doing it
on Kernel 4.15, this is not plausible.
Right now in Kernel 4.13 I have:
$ modprobe --show-depends pci:v14E4d4331sv14E4sd4331bc02sc80i00
I believe I did install the complete set of packages:
linux-generic-hwe-16.04-edge_4.15.0.13.39_amd64.deb
linux-headers-4.15.0-13_4.15.0-13.14~16.04.1_all.deb
linux-headers-4.15.0-13-generic_4.15.0-13.14~16.04.1_amd64.deb
linux-headers-generic-hwe-16.04-edge_4.15.0.13.39_amd64.deb
The pci ids for your device should be handled by the bcma module, but
that module is not loaded. Can you confirm that you have the
corresponding linux-image-extra package installed? If so, please run:
modprobe --show-depends
pci:v14E4d4331sv14E4sd4331bc02sc80i00
and provide the
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
OK. I agree this is a different bug than the one I referred to when initially
filing the bug.
As when I tried to add the referenced patch within file
linux-hwe-edge_4.15.0-13.14~16.04.1.diff, and upon applying the diff patch file
to the source it warned me the patch was already applied
Is there a possibility of dissecting this bug ? I mean try previous
versions / git commit to see from which one the problem appears ? and
see what code changed triggered this bug ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected xenial
** Description changed:
I was upgrading my Ubuntu Xenial 16.04 from linux-hwe kernel 4.13.0-38
to linux-hwe-edge 4.15.0-13.
After reboot my Broadcom network adapter (requiring package
firmware-b43-installer) is not recognized
Also note that the patch you linked to was included in a stable update
from upstream and has been in the bionic kernel since 4.15.0-11.12, and
the CONFIG_SSB_PCIHOST_POSSIBLE is being enbled. So that should not be
the issue causing your problem in linux-hwe-edge 4.15.0-13.
--
You received this
It's understandably difficult to use apport-collect when you don't have
a network connection. If possible use a wired connection, otherwise at
least collect dmesg and attach it to this bug. Please be sure that any
logs are collected while running the 4.15 kernel.
--
You received this bug
24 matches
Mail list logo
