broadcom b43 driver not working

Bug #1755034 reported by hcmeyer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
b43-fwcutter (Ubuntu)
New
Undecided
Unassigned

Bug Description

Problem is actually with cfg80211 and CRDA:

Dmesg output:

[ 108.370194] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 108.381953] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 108.416481] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 108.416488] cfg80211: failed to load regulatory.db
[ 108.643561] Broadcom 43xx driver loaded [ Features: NL ]

I have spent a day putzing about with this, it was working on Xeniel, now Bionic has broken it.

I am trying to save an old lenovo laptop from the scrap heap. Maybe it belongs there.

I only have ethernet in the basement. It is cold down here.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firmware-b43-installer 1:019-3
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic i686
ApportVersion: 2.20.8-0ubuntu10
Architecture: i386
CurrentDesktop: XFCE
Date: Sun Mar 11 18:02:20 2018
InstallationDate: Installed on 2018-03-09 (2 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
JournalErrors:
 -- Logs begin at Sat 2018-03-10 23:57:05 EST, end at Sun 2018-03-11 17:54:51 EDT. --
 Mar 11 17:53:40 hostname spice-vdagent[1051]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
 Mar 11 17:53:41 hostname pulseaudio[1091]: [pulseaudio] pid.c: Daemon already running.
 Mar 11 17:54:06 hostname pulseaudio[1065]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
PackageArchitecture: all
SourcePackage: b43-fwcutter
UpgradeStatus: Upgraded to bionic on 2018-03-11 (0 days ago)

Revision history for this message
hcmeyer (hcmeyer) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.