Broadcom wireless card dissapears???

Hi all,
I've been bamboozled by this little issue for a while now. My HP G6000 has an in built broadcom 802.11g wireless adapter, but for a while, I've been having issues with it. It was working one day, then the next, gone. It wasn't detected by anything, not even device manager. I even opened the laptop up to check the card was still there. It was, but for some reason, the computer never picks it up. Occasionally, after resetting the bios or whilst the computer is on, it does start up and become detectable again, but this is such a rare occurrence that I may as well not even bother to get my hopes up. This is just another problem from a laptop with a history riddled with problems, one of which it overheated on boot up and was only useful as a doorstop for 2 whole years...
If anyone has any good ideas or questions, I would be very grateful indeed.
Thanks for your time,
Smileygeckos

The first symptom I had before my gpu went (dv9810) was that my dvd drive disappeared from device manager. This was also intermittent, at first, but eventually it was gone for good. I restored my system using the recovery partition, but the dvd drive never came back.
The reason I mention all this is because, after I baked my motherboard, everything was working again, and I wonder if heating the entire board somehow reflowed the dvd connection also. This is all speculation on my part, but it kind of makes sense.
Anyway, if you get to that "nothin to lose" point, you might want to pop it in the oven.
Good luck
Jeff

Similar Messages

No network and Broadcom wireless card

I'm new to Solaris OS, and I installed Solaris 10 with no network since I'm using a broadcom wireless card. Before installing Solaris10 on this box I had Ubuntu running on it and was able to use the ndiswrapper for the broadcom card.
But... I'm a bit lost now since I installed solaris 10 with no network at all. So my question is, how do I create a new network and get my broadcom card installed?

Solaris is a great OS... welcome to the fold.
First, Broadcom is not a good choice for any alternative OS including Solaris but OpenSolaris does have drivers despite Broadcom's lack of cooperation with other operating systems. I do suggest staying away from this vendor because of their "closed" nature of driver support.
That being said, the HCL at http://www.sun.com/bigadmin/hcl/ can help. As well as Linux and others. While vendors like Broadcom are closed, others are not.
My favorite has been Intel 82557, 82558, 82559-controllers, I bought a bunch of them dirt cheap years back knowing they were supported with Linux, BSD and Solaris. They work well in pairs too, use then for firewalls.
The best thing we can do is only buy hardware that works with all OSes.

New driver for Broadcom wireless cards

Finally there's a driver for Broadcom wireless cards, including 4328 which only worked using ndiswrapper.
http://www.broadcom.com/support/802.11/linux_sta.php
There are discussions about it on the Ubuntu forums
http://ubuntuforums.org/showthread.php?t=914697
on the Debian forums
http://forums.debian.net/viewtopic.php? … 294ad5d3e9
and on the Gentoo wiki
http://gentoo-wiki.com/HARDWARE_Apple_M … Generation
Last edited by cmlr (2008-09-25 14:10:13)

Actually, this driver already has a Wiki page, http://wiki.archlinux.org/index.php/Broadcom_BCM4312. The new information is that it doesn't just work with bcm4312 cards, but all modern 43xx cards. See the forum links in the previous message.
The driver is already available in AUR,
http://aur.archlinux.org/packages.php?ID=19514
Last edited by cmlr (2008-09-25 14:20:50)

Tried every way to install my broadcom wireless card and failed

Hello.. i asked this in the newbie section but didn't get any replies.. i really need help and i don't know where else to go.
i have an hp dv2500 laptop with a Broadcom wireless card.. here is the output of lspci | grep -i net
08:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)
at first, i tried getting it to work with the broadcom-wl driver from AUR as suggested by this wiki page: http://wiki.archlinux.org/index.php/Broadcom_BCM4312
i followed all the steps.. however, i did get an error when i tried to exucute this line:
insmod /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/wl.ko
and the error was:
error inserting 'wl.ko': -1 File exists ...
i continued despite this error and when i was done, i couldn't detect the card with iwconfig or wicd.. the modules named "wl" and "lib80211" are loaded but i still can't detect it..
i uninstalled, re-installed and i got the same behaviour..
so then i tried the BCM43xx driver as described here: http://wiki.archlinux.org/index.php/Wir … up#BCM43XX
i unpacked the firmware and restarted but i still couldn't detect it.. and i couldn't load the bcm43xx module because arch says was not found..
then i tried the driver after that "b43".. followed the steps on the wiki, restarted, and i still couldn't detect the card with iwconfig or wicd..
i have been trying to get this to work for 3 days now.. i appreciate your time and help in this issue..
thanks

thanks for the reply tomk..
so at least we limited the problem to using broadcom-wl..
here is dmesg after modprobe -r wl
Bluetooth: Generic Bluetooth USB driver ver 0.5
usbcore: registered new interface driver btusb
Adding 1895660k swap on /dev/sda4. Priority:-1 extents:1 across:1895660k
forcedeth 0000:00:0a.0: irq 27 for MSI/MSI-X
Clocksource tsc unstable (delta = 4398045793691 ns)
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
eth0: no IPv6 routers present
lib80211_crypt: unregistered algorithm 'NULL'
and after modprobe wl:
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
i'm not that good with gnu/linux, so i'm not sure if something is wrong from these messages... do they point to anything?

Broadcom Wireless Card Setup Problems

Hello there, I'm very new to Archlinux and to linux overall. Since I'm done with my classes for the summer, I had the crazy idea to setup a home web server with my old machine and at the same time use the wireless card as an acess point for my laptop. The problem is that I followed all the steps in the Archlinux wiki about the wireless setups for the B43 driver several times. However, my system seams to ignore all my efforts and keeps making fun of me. According to what I understood, it's not setting up the network interface. (Which is suposed to be done automaticly I think) So here's a bunch of troubleshooting commands results.
iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
lspci | grep -e Network
01:06.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
lshw -C network
*-network
description: Network controller
product: BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 6
bus info: pci@0000:01:06.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=b43-pci-bridge latency=32
resources: irq:16 memory:40000000-40001fff
lsmod| grep -e b43 -e bcm43xx -e ssb -e ndiswrapper
b43 172775 0
ssb 44979 1 b43
mmc_core 52043 2 b43,ssb
pcmcia 29658 2 b43,ssb
mac80211 171331 1 b43
cfg80211 126817 2 b43,mac80211
led_class 2609 1 b43
Here are the links I followed to try to setup and try to troubleshoot my things
For b43 driver:
http://wiki.archlinux.org/index.php/Wireless_Setup
http://ubuntuforums.org/showthread.php?t=780692
http://linuxwireless.org/en/users/Drivers/b43
For ndiswrapper driver
http://ubuntuforums.org/showthread.php?t=780590
(There was an other one that told how to set it up but i can't find it)

Ok, I"ve done it and I got a few errors.
b43-pci-bridge 0000:01:06.0: PCI INT A disabled
cfg80211: Calling CRDA to update world regulatory domain
b43-pci-bridge 0000:01:06.0: PCI INT A -> Link[APC1] -> GSI 16 (level, low) -> IRQ 16
ssb: PCI-ID not in fallback list
ssb: CHIPID not in nrcores fallback list
ssb: Core 0 found: UNKNOWN (cc 0x8FF, rev 0x7F, vendor 0xFFFF)
ssb: WARNING: Invalid SPROM CRC (corrupt SPROM)
ssb: Unsupported SPROM revision 255 detected. Will extract v1
ssb: Sonics Silicon Backplane found on PCI device 0000:01:06.0
Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ]
So, does that mean that I don't use the proper firmware?

Windows 7 driver for GeForce 320m Graphic Card and Broadcom wireless card

I just got my 11" MacAir (2011)and installed Windows 7 on it using Parallel software. Everything works fine except for the driver for the Broadcom BCM 43xx1.0 airport wireless card and for the GeForce 320m graphic card. Windows 7 cannot find the drivers. I have tried everything to find a solution: Downloaded the drivers from the Broadcom and NVIDIA websites, used the drivers that came with bootcamp and made changes to the nvao.inf file for the graphic card problems but nothing works. Does anyone know a solution to these problems? Many thanks.

Hi,
since Parallels is not an Apple product it would be better to use their own Support resources.
However, Parallels does not use the native (real) hardware of your Mac but virtualizes certain hardware.
The video adapter is a "VGA and SVGA with VESA 3.0 compatible Video Adapter" and the WiFi is mapped to a "Ethernet Virtual network card compatible with RTL8029".
For these virtual devices Parallels brings all drivers with it and names them "Parallels Tools" which you have to install manually while in our Parallels Windows virtual machine.
Refer to the Parallels User Guide http://download.parallels.com/desktop/v6/docs/en/ParallelsDesktop_UsersGuide/
Regards
Stefan

Problems with Broadcom wireless card after Kernel Upgrade

After upgrading to version 2.6.39 of the linux kernel, I am having trouble with my Broadcom BCM4312 wireless card. The broadcom-wl driver no longer seems to work, even after reinstalling it from the AUR. The b43 driver seems to be able to connect to unencrypted networks, but can no longer connect to my family's WPA Personal encrypted router. Is anybody else having a similar problem?

As I understand it my laptop has been fine and it uses broadcom-wl, and I just re-yaourt it each time my kernel version changes using a cable in my router. But I believe there is something called dkms and a version of the driver for it, which (I haven't read fully into it) is something like a separate tree, which can (from what little I've read) eliminate this need to recompile every time, however I literally read this 5 minutes ago, from the AUR page for broadcom-wl and a quick google so I wouldn't be surprised if there is more to it than that.

[SOLVED] Broadcom wireless card behaving very strangely

My wireless card has become unusable in an obscure fashion after a reboot. It may have been due to the recent kernel update, but I rebooted once after that update and the card was fine, so I'm not sure. Wireless was working without a hitch for months before this.
I have a Macbook Pro 9,1 with a Broadcom BCM4331 wireless card. I use the b43 firmware.
The firmware is being loaded on boot, but that vague "link is not ready" error appears every time the system attempts to load the firmware:
[ 12.263906] b43-phy0: Broadcom 4331 WLAN found (core revision 29)
[ 12.264337] b43-phy0: Found PHY: Analog 9, Type 7 (HT), Revision 1
[ 12.264864] Broadcom 43xx driver loaded [ Features: PMNLS ]
[ 12.728423] systemd-udevd[210]: renamed network interface wlan0 to wlp3s0
[ 15.801790] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 15.888891] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 186.474169] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 186.561426] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 326.465714] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 326.552778] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 683.592477] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 683.679541] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 1350.060493] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1350.147545] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 1474.360067] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1474.447162] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 1667.887393] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1667.967795] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 2110.770119] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 2110.857285] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
When I try to use netctl to connect to my home network, I get the same error:
-- Unit [email protected] has begun starting up.
Jan 22 18:36:40 tenfoxes network[3072]: Starting network profile 'home'...
Jan 22 18:36:41 tenfoxes kernel: b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Jan 22 18:36:41 tenfoxes kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Jan 22 18:36:56 tenfoxes network[3072]: WPA association/authentication failed for interface 'wlp3s0'
Jan 22 18:36:56 tenfoxes network[3072]: Failed to bring the network up for profile 'home'
Jan 22 18:36:56 tenfoxes systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
Jan 22 18:36:56 tenfoxes systemd[1]: Failed to start Networking for netctl profile home.
If I scan for networks using iw dev wlp3s0 scan, I get no output. Here's the debug output from that if it means anything to anyone—from the docs on netlink I read it doesn't seem to show anything unusual:
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 36
.type = 26 <0x1a>
.flags = 5 <REQUEST,ACK>
.seq = 1390438118
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 33
.version = 0
.unused = 0
[PAYLOAD] 16 octets
08 00 03 00 03 00 00 00 08 00 2d 00 04 00 01 00 ..........-.....
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 36
.type = 2 <ERROR>
.flags = 0 <>
.seq = 1390438118
.port = 3698
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.type = 26 <0x1a>
.flags = 5 <REQUEST,ACK>
.seq = 1390438118
.port = 3698
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438119
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 1
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 116
.type = 16 <genl/family::nlctrl>
.flags = 0 <>
.seq = 1390438119
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 1
.version = 2
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
[ATTR 01] 2 octets
10 00 ..
[PADDING] 2 octets
00 00 ..
[ATTR 03] 4 octets
02 00 00 00 ....
[ATTR 04] 4 octets
00 00 00 00 ....
[ATTR 05] 4 octets
07 00 00 00 ....
[ATTR 06] 20 octets
14 00 01 00 08 00 01 00 03 00 00 00 08 00 02 00 ................
0e 00 00 00 ....
[ATTR 07] 24 octets
18 00 01 00 08 00 02 00 10 00 00 00 0b 00 01 00 ................
6e 6f 74 69 66 79 00 00 notify..
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 36
.type = 2 <ERROR>
.flags = 0 <>
.seq = 1390438119
.port = 3698
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.type = 16 <0x10>
.flags = 5 <REQUEST,ACK>
.seq = 1390438119
.port = 3698
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438120
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 0
.unused = 0
[ATTR 02] 8 octets
6e 6c 38 30 32 31 31 00 nl80211.
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438121
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 1
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 116
.type = 16 <genl/family::nlctrl>
.flags = 0 <>
.seq = 1390438121
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 1
.version = 2
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
[ATTR 01] 2 octets
10 00 ..
[PADDING] 2 octets
00 00 ..
[ATTR 03] 4 octets
02 00 00 00 ....
[ATTR 04] 4 octets
00 00 00 00 ....
[ATTR 05] 4 octets
07 00 00 00 ....
[ATTR 06] 20 octets
14 00 01 00 08 00 01 00 03 00 00 00 08 00 02 00 ................
0e 00 00 00 ....
[ATTR 07] 24 octets
18 00 01 00 08 00 02 00 10 00 00 00 0b 00 01 00 ................
6e 6f 74 69 66 79 00 00 notify..
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 36
.type = 2 <ERROR>
.flags = 0 <>
.seq = 1390438121
.port = 3698
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.type = 16 <0x10>
.flags = 5 <REQUEST,ACK>
.seq = 1390438121
.port = 3698
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438122
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 0
.unused = 0
[ATTR 02] 8 octets
6e 6c 38 30 32 31 31 00 nl80211.
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438123
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 1
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 116
.type = 16 <genl/family::nlctrl>
.flags = 0 <>
.seq = 1390438123
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 1
.version = 2
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
[ATTR 01] 2 octets
10 00 ..
[PADDING] 2 octets
00 00 ..
[ATTR 03] 4 octets
02 00 00 00 ....
[ATTR 04] 4 octets
00 00 00 00 ....
[ATTR 05] 4 octets
07 00 00 00 ....
[ATTR 06] 20 octets
14 00 01 00 08 00 01 00 03 00 00 00 08 00 02 00 ................
0e 00 00 00 ....
[ATTR 07] 24 octets
18 00 01 00 08 00 02 00 10 00 00 00 0b 00 01 00 ................
6e 6f 74 69 66 79 00 00 notify..
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 36
.type = 2 <ERROR>
.flags = 0 <>
.seq = 1390438123
.port = 3698
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.type = 16 <0x10>
.flags = 5 <REQUEST,ACK>
.seq = 1390438123
.port = 3698
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438124
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 0
.unused = 0
[ATTR 02] 8 octets
6e 6c 38 30 32 31 31 00 nl80211.
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438125
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 1
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 116
.type = 16 <genl/family::nlctrl>
.flags = 0 <>
.seq = 1390438125
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 1
.version = 2
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
[ATTR 01] 2 octets
10 00 ..
[PADDING] 2 octets
00 00 ..
[ATTR 03] 4 octets
02 00 00 00 ....
[ATTR 04] 4 octets
00 00 00 00 ....
[ATTR 05] 4 octets
07 00 00 00 ....
[ATTR 06] 20 octets
14 00 01 00 08 00 01 00 03 00 00 00 08 00 02 00 ................
0e 00 00 00 ....
[ATTR 07] 24 octets
18 00 01 00 08 00 02 00 10 00 00 00 0b 00 01 00 ................
6e 6f 74 69 66 79 00 00 notify..
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 36
.type = 2 <ERROR>
.flags = 0 <>
.seq = 1390438125
.port = 3698
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.type = 16 <0x10>
.flags = 5 <REQUEST,ACK>
.seq = 1390438125
.port = 3698
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438126
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 0
.unused = 0
[ATTR 02] 8 octets
6e 6c 38 30 32 31 31 00 nl80211.
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 172
.type = 26 <0x1a>
.flags = 0 <>
.seq = 0
.port = 0
[GENERIC NETLINK HEADER] 4 octets
.cmd = 34
.version = 1
.unused = 0
[PAYLOAD] 152 octets
08 00 01 00 00 00 00 00 08 00 03 00 03 00 00 00 ................
0c 00 99 00 01 00 00 00 00 00 00 00 08 00 2d 00 ..............-.
04 00 00 00 74 00 2c 00 08 00 00 00 6c 09 00 00 ....t.,.....l...
08 00 01 00 71 09 00 00 08 00 02 00 76 09 00 00 ....q.......v...
08 00 03 00 7b 09 00 00 08 00 04 00 80 09 00 00 ....{...........
08 00 05 00 85 09 00 00 08 00 06 00 8a 09 00 00 ................
08 00 07 00 8f 09 00 00 08 00 08 00 94 09 00 00 ................
08 00 09 00 99 09 00 00 08 00 0a 00 9e 09 00 00 ................
08 00 0b 00 a3 09 00 00 08 00 0c 00 a8 09 00 00 ................
08 00 0d 00 b4 09 00 00 ........
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 28
.type = 26 <0x1a>
.flags = 773 <REQUEST,ACK,ROOT,MATCH>
.seq = 1390438127
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 32
.version = 0
.unused = 0
[PAYLOAD] 8 octets
08 00 03 00 03 00 00 00 ........
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 20
.type = 3 <DONE>
.flags = 2 <MULTI>
.seq = 1390438127
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 0
.version = 0
.unused = 0
--------------------------- END NETLINK MESSAGE ---------------------------
If I try to use wpa-supplicant, it will say "Successfully initialized wpa_supplicant" as if it had properly made a connection, but it hasn't. Running iw dev wlp3s0 link will show that the card isn't connected to anything, and of course the internet still doesn't work.
I know it's not a hardware problem because the wireless works fine in Mac OS.
What gives? Is there a way I can investigate this further? It seems like a driver and/or kernel issue but I'm not really sure how to nail that down with confidence. I couldn't find any reports in the kernel bug tracker about this or anything, so maybe it's just me and I'm doing something wrong.
Thanks!
Last edited by tenfoxes (2014-01-24 02:44:16)

Yay, that worked!
I guess I really should've tried that initially, huh? Since the wiki said not to use it unless you had an unsupported wireless card, I figured I shouldn't (b43 officially supports mine). Still, considering that it's easy to install/uninstall drivers, my caution was obviously unwarranted.
Thanks for your help!

Can't get Broadcom wireless card working

Hello everyone. First and foremost, I'm not a newbie to Linux, just to Arch, so I do kinda know what I'm doing
I've got my laptop with a Broadcom BCM4328. I followed the steps on the Wiki page to the letter, but I've got nothing: the wireless doesn't initialize, and I have no interface for the wireless. I've provided my output for a few commands below if it helps. I'm using the latest kernel as I just installed Arch today. Any suggestions would be greatly appreciated.
[joshua@W01-Zeus ~]$ lspci | grep Broadcom
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
0c:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)
[joshua@W01-Zeus ~]$ sudo modprobe wl
[joshua@W01-Zeus ~]$ lsmod | grep wl
wl 1287680 0
lib80211 7172 1 wl
Last edited by djbon2112 (2009-10-27 16:25:15)

the modules that i'm talking about are b43, b43legacy and ssb. but looking at your devices ssb is needed by b44(ethernet module).
your MODULES should look like this:
MODULES=(wl !b43 !b43legacy...)
not that wl is first in this array
Last edited by wonder (2009-10-27 17:20:32)

Configure Solaris 10 with ath wireless card

So I'm in over my head on this one. I got a new laptop to tinker with, put OpenSolaris on it - integrated Broadcom wireless card didn't work, but my old DLink wireless card did. Yay. But I didn't like OpenSolaris. Too linux-y. So I went to something more familiar: Solaris 10. Only now the wireless card (neither of them, actually) doesn't work. I've googled and tried stuff for the past several hours and all I get is this:
"ath: unable to resolve dependency, module misc/net80211"
I've installed the packages. I've installed the 80211 for amd64 (yes, I'm running on an amd64). I've tried downloading the tarballs, extracting them and manually copying the kernel modules. Nothing. I've tried everything I know of (which isn't much, admittedly). I've tried update_drv, used /usr/X11/bin/scanpci, prtconf -pv to check out what all is connected, and everything says that there is an Atheros ethernet device on pci168c ... but I always get an "unable to attach device" error. And when I reboot, I'm bombarded with the aforementioned unable to resolve dependency" harassment.
What stupid thing am I doing wrong?!
Thanks in advance for your help -
Caleb

alan.pae wrote:
Completely remove the driver
pkgrm SUNWatheros
init 6
make sure that there is no ath file in the kernel directory and the same for the net80211 file.
touch /reconfigure
re-add the driver from some as yet undetermined media.
init 6
should work.
alanGot me closer, but it didn't work. I ended up going with Solaris Express Developer edition, and it worked out of the box. I really appreciate your help, though.
Do you have any recommended reading for delving into the depths of Solaris? I know enough to get myself into trouble and that's about it. I picked up the "Unix System Administration Handbook" (by Evi Nemeth, Garth Snyder, Scott Seebass and Trent Hein). I've learned a ton from there, which has really helped me get some of the basics, but it's not necessarily Solaris specific.
Thanks again for your help!!!

BROADCOM Wireless device name switch

Hi all,
i have a broadcom wireless card,
i installed it using instruction on the wiki, and it works fine,
se i have the problem of interfaces swapping every time, i read the solution in the wiki.
But it seems to don't work.
In fact i edited the file /etc/udev/rules.d/10-network.rules
with that:
SUBSYSTEM=="net", ATTR{address}=="00:22:64:7F:E8:7C", NAME="eth0"
SUBSYSTEM=="net", ATTR{address}=="00:21:00:9B:3C:6D", NAME="eth1"
but it seems to ignore it!!!!
I have the interfaces swapped every time.
(i had a similar problem with other udev rules, seems that every rules that i writ is ignored!!!)
Any idea?
Last edited by finarfin (2011-01-30 13:16:20)

Here is my situation, i have the following rules in /etc/udev/rules.d:
-rw-r--r-- 1 root root 104 Oct 26 05:39 10-cups-usb.rules
-rw-r--r-- 1 root root 132 Jan 30 20:10 10-network.rules
-rw-r--r-- 1 root root 462 Jan 3 23:14 75-cd-aliases-generator.rules.optional
-rw-r--r-- 1 root root 3981 Jan 3 23:14 75-persistent-net-generator.rules.optional
The rule 10-network.rules is the one that i created following the example on the wiki.
here is the code:
SUBSYSTEM=="net", ATTR{address}=="00:22:64:7f:e8:7c", NAME="eth1"
SUBSYSTEM=="net", ATTR{address}=="00:21:00:9b:3c:6d", NAME="eth0"
And the actual ifconfig is:
eth0 Link encap:Ethernet HWaddr 00:21:00:9B:3C:6D
inet addr:192.168.1.237 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::221:ff:fe9b:3c6d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24016 errors:0 dropped:0 overruns:0 frame:2481
TX packets:16701 errors:6 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:30104092 (28.7 Mb) TX bytes:1935694 (1.8 Mb)
Interrupt:17
eth1 Link encap:Ethernet HWaddr 00:22:64:7F:E8:7C
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16
As you can see the two device are switched.
Maybe the rule should have the executable flag set?

Dell Vostro V13 wireless card issue

Hello. First of all sorry for posting this, because I'm quite sure that it has been asked before. For some weird reason, everytime I use the forum search engine, I get an 500 error.
I'm having troubles to configure my wireless card on my Dell Vostro V13. The wireless card is present on the interfaces list, but I can't put it up.
I installed wicd following wiki steps, but without any luck.
iwconfig wlan0:
wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
ifconfig -a:
eth0 Link encap:Ethernet HWaddr 00:26:6C:10:9C:93
inet addr:192.168.77.108 Bcast:192.168.77.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:68428 errors:0 dropped:0 overruns:0 frame:0
TX packets:41438 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:99765655 (95.1 Mb) TX bytes:3044573 (2.9 Mb)
Interrupt:41 Base address:0x8000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:756 (756.0 b) TX bytes:756 (756.0 b)
wlan0 Link encap:Ethernet HWaddr 70:F1:A1:2D:D8:41
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lspci -vnn | grep 14e4:
09:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
I read the wiki entrance for Broadcom Wireless cards, but I'm not sure whether I must use broadcom-wl driver or not.
Any thoughts?
Thank you and sorry for my lousy English :X

Gusar wrote:
Assuming you're using the kernel b43 driver... did you install the firmware? There's a b43-firmware package in AUR.
If that won't work, then the wl driver is an alternative.
Gusar,
The wiki says "brcm80211
The brcm80211 driver is included in the kernel since 2.6.37. No further action is necessary on the part of the user."
...so I didn't installed anything besides wicd.

Need Advice on a Laptop Wireless Card For Arch

I have Arch running on my desktop and I'm loving it. I'm thinking about putting it on my laptop too. The problem there is that my laptop has a Broadcom wireless card that the Linux kernel doesn't recognize by default. The last time I tried to use Arch on my laptop, I had to reinstall the wireless driver every time the kernel was updated.
Is there a internal wireless mini card I can buy and put in my laptop that Arch/Linux will be able to use without compiling anything? I'll buy whatever is needed to replace my Broadcom card and make my Linux experience better if you have any recommendations.

http://cgi.ebay.com/Wifi-108Mbps-super- … 27a987d09d
( Wifi 108Mbps super g Wireless PC Card CardBus Atheros
Model Number: WLG-1103)
I bought one of these about 2 months ago and it works great on my two laptops. Dirt cheap (~10 bucks, no shipping) and no fidgeting involved. Just put it in the card bus thingo, turn on the laptop, it's all good. I think the drivers are in the kernel, as I don't recall installing any driver packages on either laptop at install-time, but I definitely didn't have to do anything manually. Atheros tends to work nicely in linux in my experience, and this is no exception.
Last edited by FrozenFox (2009-10-20 20:08:48)

1802 Error Message on installation of Broadcom Mini-PCI Wireless Card

I am getting an 1802 error message on boot when I install the Broadcom Mini-PCI wireless card. I know it has something to do with some code IBM put into the BIOS or CMOS to check the cards for manufacturer or something like that. Is there anyway around this message or do I have to try and find an IBM mini-PCI wireless card for this machine?
Solved!
Go to Solution.

All depends on how one defines success...
To put it this way: A3x machines are very unpredictable and moody when it comes to these issues, and you're talking to someone who has owned over a hundred A31p ThinkPads, not counting A30/p and A31 units along the way. More than once I've faced a scenario where the card that worked "out of the box" in one machine required a hack in the next one...
But to answer your question:
Can it be done? Absolutely.
Do I recommend it? Absolutely not.
IBM-issued (with a proper FRU number) Intel 2200BG should work in your machine with no hack. Some people have reported this experience even with generic card of the same type.
Hope this helps.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

B43 won't recognise Broadcom 4312 wireless card

I've had a Dell XPS M1530 laptop for a few weeks now. It's got a Dell 1395 wireless card, which is actually a disguised Broadcom 4312 card.
lspci recognises it as such:
[sander@lappy686 ~]$ lspci | grep -i broadcom
0b:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
The card works fine with the properietary broadcom-wl drivers. I'm using these right now, in fact.
However, I'd like to use b43 if at all possible, because:
- b43 supports monitor mode;
- broadcom-wl drivers are proprietary, whereas the b43 ones are open.
I have followed the guide on the wiki to extract the firmware from the proprietary drivers:
[sander@lappy686 ~]$ sudo ls /lib/firmware/b43/
a0g0bsinitvals4.fw a0g0initvals9.fw a0g1initvals5.fw b0g0bsinitvals9.fw lp0bsinitvals13.fw lp0initvals15.fw pcm5.fw ucode4.fw
a0g0bsinitvals5.fw a0g1bsinitvals13.fw a0g1initvals9.fw b0g0initvals13.fw lp0bsinitvals14.fw n0absinitvals11.fw ucode11.fw ucode5.fw
a0g0bsinitvals9.fw a0g1bsinitvals5.fw b0g0bsinitvals13.fw b0g0initvals4.fw lp0bsinitvals15.fw n0bsinitvals11.fw ucode13.fw ucode9.fw
a0g0initvals4.fw a0g1bsinitvals9.fw b0g0bsinitvals4.fw b0g0initvals5.fw lp0initvals13.fw n0initvals11.fw ucode14.fw
a0g0initvals5.fw a0g1initvals13.fw b0g0bsinitvals5.fw b0g0initvals9.fw lp0initvals14.fw pcm4.fw ucode15.fw
when I insert the b43 module (sudo modprobe b43), the following shows up in /var/log/everything.log:
Nov 7 20:58:36 lappy686 Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ]
... and nothing more. I was told that this isn't normal
The actual problem is that no network interface shows up in ifconfig / iwconfig. The only ones that are there are lo and eth0 (wired ethernet). When I use broadcom-wl, the wireless interface shows up as "eth1".
I have also tried to extract the firmware from some older versions of the driver, but the same thing happens. What's curious is that it'll still say "Firmware-ID: FW13" in /var/log/everything.log...
So, anybody have any clues? I guess it's not that urgent, but it sucks that I have to use a proprietary driver. The only other option I haven't tried is ndiswrapper, and frankly, I'm not sure I want to

On my machine:
lspci | grep -i broadcom
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
0b:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)
dmesg | grep -i broadcom
b43-phy0: Broadcom 4311 WLAN found
Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ]
grep MODULES /etc/rc.conf
MODULES=(b43 !b44 !pcspkr !snd_pcsp)
I wanted to look at the MODULES section on your machine because, indeed, I was planning to suggest something along the lines of "b43 !wl". Now I suppose that it would not work (as you seem to have already tried it).

Broadcom wireless card dissapears???

Similar Messages

Maybe you are looking for