Package is not being installed if you install from a usb pendrive created from disks

[Dave Morley]

WORKAROUND:
The issue here is that the driver is not able to be automatically installed, you can however install it manually.

From the usbkey used to install the system copy the following files to your home directory:
Ubuntu 15.10 amd64/pool/main/d/dkms dkms_2.2.0.3-2ubuntu2_all.deb
Ubuntu 15.10 amd64/pool/restricted/b/bcmwl bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu6_amd64.deb

Now open terminal and from the home directory run sudo dpkg -i dkms_2.2.0.3-2ubuntu2_all.deb bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu6_amd64.deb

You should see a message to say networks available from the network-indicator and then be able to connect to wifi.

STEPS:
Pre-requisite: Laptop with bcmwl supported chipset, intel based macs or dell xps for example.

1. Grab the latest 15.10 daily image from cdimages
2. Plug a usb pendrive into the system
3. Open Disks
4. Format the pendrive
5. Select restore image to drive
6. Select the image you just downloaded
7. Click on okay if the install is happening on the pendrive
8. Click on okay again to confirm
9. Add the user password for permission to write to the drive
10. Insert the written image into the laptop you want to install on
11. In the uefi menu select the pendrive
12. Select the live session
13. Open system settings
14. Open Software and updates
15. Tap on the Additional Drivers tab

EXPECTED:
I expect to the bcmwl driver available to install

ACTUAL:
I see only micro code driver for the cpu (see screenshot)

Included files:
Screenshot
/etc/apt/sources.list

[Dave Morley (davmor2)]

It was initially assumed the issue here was an out of sync archive with the cd showing 0ubuntu4.1 and online archive 0ubuntu5 however after a sync to get the archives straight on this morning image both show as 6.30.223.248+bcom-0ubuntu5 and sudo ubuntu-drivers still only shows intel-microcode.

[Martin Wimpress  (flexiondotorg)]

Is this related?

  * https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212

[Dave Morley (davmor2)]

Okay so the macbook pro that normally has the same issue as the xps is actually showing the bcmwl package as installable. So this could be an issue specific to the xps13 it seems.

[Dave Morley (davmor2)]

I can however at least install the package in the live session now with sudo apt install bcmwl-kernel-sources

[Dave Morley (davmor2)]

So running sudo lsmod

I see b43 so it looks like the b43 driver is trying to be installed which it can't as it needs to bcmwl driver :( Is there a way to blacklist b43 for this chipset and have the bcmwl install for it instead?

[Launchpad Janitor (janitor)]

This bug was fixed in the package bcmwl - 6.30.223.248+bdcom-0ubuntu6

---------------
bcmwl (6.30.223.248+bdcom-0ubuntu6) wily; urgency=medium

  * debian/bcmwl-kernel-source.modaliases: add 43b1 as a matched model in
    modalises; https://wireless.wiki.kernel.org/en/users/Drivers/b43 says it
    is supported by the wl driver (this is BCM4352). (LP: #1498074, #1173761)

 -- Mathieu Trudel-Lapierre <email address hidden> Tue, 22 Sep 2015 09:52:45 -0400

[Dave Morley (davmor2)]

Mathieu didn't fix it b43 is still owning the driver for the card:

ubuntu@ubuntu:~$ sudo lsmod | grep b43
b43 417792 0
mac80211 724992 1 b43
cfg80211 536576 2 b43,mac80211
ssb 65536 1 b43
bcma 53248 1 b43
ubuntu@ubuntu:~$ apt-cache policy bcmwl-kernel-source
bcmwl-kernel-source:
  Installed: (none)
  Candidate: 6.30.223.248+bdcom-0ubuntu6
  Version table:
     6.30.223.248+bdcom-0ubuntu6 0
        500 cdrom://Ubuntu 15.10 _Wily Werewolf_ - Alpha amd64 (20150922.1)/ wily/restricted amd64 Packages
        500 http://archive.ubuntu.com/ubuntu/ wily/restricted amd64 Packages
ubuntu@ubuntu:~$

[Dave Morley (davmor2)]

sudo ubuntu-drivers list still only shows intel-microcode too

I'll hang around tonight and and see if we can get it resolved.

[Ubuntu QA Website (ubuntuqa)]

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/1498074

[Launchpad Janitor (janitor)]

This bug was fixed in the package bcmwl - 6.30.223.248+bdcom-0ubuntu7

---------------
bcmwl (6.30.223.248+bdcom-0ubuntu7) wily; urgency=medium

  * debian/bcmwl-kernel-source.modaliases: really fix matching for model 43b1,
    apparently modaliases are case-sensitive, and changing ubuntu-drivers
    to remove that limitation looks like it would negatively affect its
    performance. (LP: #1498074)

 -- Mathieu Trudel-Lapierre <email address hidden> Mon, 28 Sep 2015 15:46:13 -0400

[Adam Conrad (adconrad)]

Hello Dave, or anyone else affected,

Accepted bcmwl into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.271+bdcom-0ubuntu1~0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Ubuntu Foundations Team Bug Bot (crichton)]

The fix for this bug has been awaiting testing feedback in the -proposed repository for trusty for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository.

[Dave Morley (davmor2)]

Will look into this today but I though it had been resolved already, let me confirm it though.

[Dave Morley (davmor2)]

Tested via live session and via install all seems to be working as expected.

[Bryan Quigley (bryanquigley)]

Trusty release has gone end of support for this package, so marking this as such.

Newer releases will have this fix though.