Wireless disabled in Debian after MacOS use (stuck)
I had the wireless (AirPort) working on my MacBook Pro 8.1 with a
dual boot MacOS/Debian setup without any difficulty for a couple of years.
A couple of days ago, I decided to try MacOS to configure a new modem,
as the wired connection in Debian would just show "connecting"... and
sit there. I very very rarely use MacOS... but I figured I'd try it for this.
To my surprise, the wired connection worked in MacOS, and I also connected
with the wireless to a router in MacOS. I rebooted into
Debian... and since that the wireless has not worked. The wireless
continues to work in MacOS. I am currently connecting with a wired
connection (in Debian).
I previously had the wireless configured with the b43 driver.
The install of the b43 driver is straight forward:
# apt-get install b43-fwcutter firmware-b43-installer
COMMENT:
I tried un-installing and re-installing. It didn't help.
I am running out of ideas of what to try. The situation is
unusual... as I had the wireless working previously.
I have only found one vaguely similar description related
to VMware (
http://askubuntu.com/questions/260209/networking-disabled-under-vmware-fusion-on-mac-os-x
).
I am not using VMware. The dual boot is done with rEFIt.
Here are a few things I tried/looked at:
---------
# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
COMMENT:
No blocks appear to be present.
I vaguely remember reading that MacOS puts network cards into some sort of
suspended mode... and they don't work afterward. I read this a couple of
years ago. I also have a MacMini... not sure it is in association with that.
In any case, I can't find anything for this vague recollection... possibly
imaginary problem.
Working the theory that MacOS screwed the network card... which is my
working theory (due to the temporal association):
I booted into MacOS -- and disabled the AirPort... rebooted into
Debian. Wireless still broken.
networksetup -setairportpower en1 off
Described here:
http://osxdaily.com/2011/05/31/enable-disable-airport-wireless-connections-command-line/
I booted into MacOS -- enabled the AirPort... rebooted into Debian.
Wireless still broken.
It should be noted that I rarely booted into MacOS into the past.
Preceding said, this is the first time since upgrading to Debian
'jessie'.
Any thoughts on reseting the wireless card from MacOS?
I did find something on that here:
http://macosx.com/threads/howto-reset-the-wireless-airport-card-settings-in-os-x-10-7-x-10-8-x.321879/
---------
# lshw -C Network
*-network
description: Ethernet interface
product: NetXtreme BCM57765 Gigabit Ethernet PCIe
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 10
serial: 3c:07:54:05:c6:0d
size: 100Mbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd
autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3
driverversion=3.137 duplex=full firmware=57765-v1.37 ip=192.168.0.194
latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
resources: irq:16 memory:b0400000-b040ffff memory:b0410000-b041ffff
*-network
description: Network controller
product: BCM4331 802.11a/b/g/n
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
version: 02
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=bcma-pci-bridge latency=0
resources: irq:17 memory:b0600000-b0603fff
*-network DISABLED
description: Wireless interface
physical id: 1
logical name: wlan0
serial: b8:8d:12:1c:a4:c4
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=b43
driverversion=3.16.0-4-686-pae firmware=N/A link=no multicast=yes
wireless=IEEE 802.11bg
COMMENT:
The above shows the network DISABLED. It show the driver as b43.
---------
# lsmod |grep b43
b43 362085 0
mac80211 421532 1 b43
cfg80211 350041 2 b43,mac80211
ssb 51408 1 b43
rng_core 12645 1 b43
pcmcia 44245 2 b43,ssb
bcma 36446 1 b43
mmc_core 91803 4 b43,ssb,sdhci,sdhci_pci
COMMENT:
The driver b43 loads.
---------
# lspci -vnn -d 14e4:
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme
BCM57765 Gigabit Ethernet PCIe [14e4:16b4] (rev 10)
Subsystem: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet
PCIe [14e4:16b4]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at b0400000 (64-bit, prefetchable) [size=64K]
Memory at b0410000 (64-bit, prefetchable) [size=64K]
Capabilities: [48] Power Management version 3
Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable+ Count=6 Masked-
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Device Serial Number 00-00-3c-07-54-05-c6-0d
Capabilities: [150] Power Budgeting <?>
Capabilities: [160] Virtual Channel
Kernel driver in use: tg3
02:00.1 SD Host controller [0805]: Broadcom Corporation BCM57765/57785
SDXC/MMC Card Reader [14e4:16bc] (rev 10) (prog-if 01)
Subsystem: Broadcom Corporation Device [14e4:0000]
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at b0420000 (64-bit, prefetchable) [size=64K]
Capabilities: [48] Power Management version 3
Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Power Budgeting <?>
Capabilities: [160] Virtual Channel
Kernel driver in use: sdhci-pci
03:00.0 Network controller [0280]: Broadcom Corporation BCM4331
802.11a/b/g/n [14e4:4331] (rev 02)
Subsystem: Broadcom Corporation BCM4331 802.11a/b/g/n [14e4:4331]
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at b0600000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-00-ff-ff-00-00-00
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: bcma-pci-bridge
COMMENT:
I am somewhat confused that "lspci -vnn -d 14e4:" shows "Kernel driver
in use: bcma-pci-bridge".
At least one other person seems confused about this:
http://www.linux.com/community/forums/drivers/bcma-pci-bridge-instead-of-b43-is-assigned-to-my-wireless-card
---------
# iwconfig
wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
COMMENT:
'iwconfig' detects the wireless card.
FURTHER COMMENTS:
-I also tried the 'wl' driver -- as described in detail
here: https://wiki.debian.org/wl
I did get the 'wl' driver installed and had purged the
'b43' driver. The wireless didn't work.
-I re-started the network between with: /etc/init.d/networking restart
---------
# cat /var/lib/NetworkManager/NetworkManager.state
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
COMMENT:
When I first looked at the file
(/var/lib/NetworkManager/NetworkManager.state) it showed
'WirelessEnabled=false'. I changed it to 'WirelessEnabled=true'. It
has stayed as 'true'...
even after reboots.
---------
# nm-applet
(nm-applet:4241): nm-applet-WARNING **: Failed to initialize D-Bus:
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.
Any suggestions would be much appreciated!
Thanks,
Michael
---------
System details:
Linux version 3.16.0-4-686-pae (debian-kernel@lists.debian.org) (gcc
version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1
(2015-05-24)
Debian version: 8.1
Reply to: