This was added to the release notes for Disco: "For secure-boot enabled
systems with Broadcom wireless, even after selecting the proprietary
drivers during the installation, the bcmwl dkms module can end up left
uninstalled after reboot (resulting in no working wifi). This is caused
by a dkms
This bug was fixed in the package dkms - 2.6.1-4ubuntu2
---
dkms (2.6.1-4ubuntu2) disco; urgency=medium
* d/p/revert-removal-of-modules-from-dkms-built-tree.patch:
- Revert the upstream change that caused dkms uninstall remove the modules
from the built tree, as that
Thanks fossfreedom for the verification!
I have also submitted this fix and they were ok with the change (PR has been
merged to master):
https://github.com/dell/dkms/pull/77
So we should be good to go.
--
You received this bug notification because you are a member of Kernel
Packages, which is
On disco.
2.6.1-4ubuntu2
Followed the test case and this reported the results (built)
Then reinstalled with secure boot enabled.
Repeated and enrolled the mok key. Rebooted and wireless was available
** Tags removed: verification-needed verification-needed-disco
** Tags added:
This bug was fixed in the package dkms - 2.6.1-4ubuntu2
---
dkms (2.6.1-4ubuntu2) disco; urgency=medium
* d/p/revert-removal-of-modules-from-dkms-built-tree.patch:
- Revert the upstream change that caused dkms uninstall remove the modules
from the built tree, as that
Hello fossfreedom, or anyone else affected,
Accepted dkms into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.6.1-4ubuntu2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [Impact]
+
+ The dkms version available in disco regressed in behavior in comparison
+ to earlier series, causing `dkms uninstall` removing the module from the
+ built tree instead of only uninstalling it. Per the dkms manpage, an
+ uninstall operation should leave the
I have prepared and uploaded a fix for that into the disco queue. We are
reverting this change as it seems to be a regression from expected
behavior - even man dkms (or checking the manpage on their github
upstream repo) mentions `dkms uninstall` leaving the module in the
'built' state. I suspect
So essentially this is the change that 'broke' dkms:
https://github.com/dell/dkms/commit/0c19129b5d1f8e03498f6f2455ad9f7e14e9e606
I think per expected behavior we should actually *not* be removing
modules from the dkms tree on uninstall, right? This is a regression,
not sure why someone actually
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821823
Title:
No wireless networks displayed for broadcom BCM43142
Status in ubiquity package in
** Attachment added: "installer syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821823/+attachment/5256316/+files/syslog
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which
The log file wasn't actually attached, could you find it again and add
it?
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ok - decided to reopen this.
Have retested todays release candidate ISO
For this laptop - I did not connect via a wired connection.
I did choose the restricted drivers option in the installer and during
the installation I saw that it said it installed the bcmwl-kernel-source
On restart no wifi
Just rerun this on the same iso as above (beta) and this time wireless
was found.
Putting this down as a glitch.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Could you add the ubiquity log file to the bug report or try and the
beta iso image and then include the ubiquity log file?
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
For 19.04 UB did a minimal install. I selected the ubiquity proprietary
option and expected the broadcom driver to be found and installed.
- On reboot I could not see and wireless networks. I went to the
+ On reboot I could not see any wireless networks. I went
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1821823
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages, which
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Odd. That was already installed.
I then ran a apt --reinstall install for that package and this time
wireless started.
Thus it appears the kernel module wasn't successfully installed by
ubiquity?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Please run `sudo apt install bcmwl-kernel-source`.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821823
Title:
No wireless networks displayed for broadcom BCM43142
Status in linux
20 matches
Mail list logo
