[SOLVED]Wireless card (Broadcom) issue

I've just finished installing arch on my new laptop. I've been using it already for quite some time, even if i'm far from being an expert.
The installation went flawlessy. Now when i try to get my wireless interface up, messages show telling that some firmware files are missing (b43). Now i don't have any other os installed and getting a wired connection will require some time at best.
I read on this same forum that i' d probably resolve it by installing the b43 firmaware package from AUR.
I was wondering tho, since it was working well during the installation (did a net install), and since i'm not gonna be able to get a connection on the same machine for a while, if there is something i could do with the installation to include such required firmware.
Thanks in advance.
Last edited by northerw (2011-11-18 18:29:15)

Will post the output later, since i havent got a graphical interface yet on my arch system.
And yes that was wierd to me too, couldnt find a connection between the base-devel and the firmware missing files (was something along the lines of b43/ucode16_mimo.fw and one more), but i did the exact same steps both times except the host name which i changed the second time, and ofc the base-devel pkg.
Anyways if i find something else out i will post here the findings
EDIT: Following is the output of the lspci -vv and the loaded modules on the working system:
03:00.0 Network controller: Broadcom Corporation BCM43225 802.11b/g/n (rev 01)
mac80211 221931 1 brcmsmac
brcmutil 6912 1 brcmsmac
cfg80211 165636 2 brcmsmac,mac80211
EDIT2: Adding this for everyone that might need it in the future.
For the sake of understanding it, i did even try a third installation, redoing exacly the same steps i did in my 2nd 'working' one. This time tho, surprise, the issue was back in (no clue why, seems incredibly random).
I checked the loaded modules and saw that the b43 module was loaded this time. So, as vacant suggested i procedeed to blacklist the 'bcma' module, restarted and the system was back working as it should.
Last edited by northerw (2011-11-21 10:01:54)

Similar Messages

[SOLVED] Wireless card works, but configuration and software doesn't

Hi,
I could manage to activate my Atheros wireless card using the madwifi drivers. I wanted to use knetworkmanager, but unfortunatly i doesn't recognize any of my network devices. I've read the other networkmanager threads, changed the daemons order, disabled the network daemon and the routing entry in rc.conf, but still (k)networkmanager doesn't know anything about my devices.
I tried to use knetworkmanager-svn from the AUR. Initially it doesn't work because the SVN URLs inside the PKGBUILD script a wrong, but even after I fixed them I couldn't compile the source, because there is no configure and no Makefile in the svn head. I'm really a noob when it comes to the linux build system, so I had to give it up.
Now I use wifi-radar. It is terribly slow to connect, but it works. However, when I disconnect with wifi-radar, then do 'ifconfig ath0 down && ifconfig eth0 up' the DNS requests fail. I checked /etc/resolv.conf and the default route (set to eth0), but they are right; the interface just doesn't use the name servers. The only way to get it working is to restart the laptop. How does Linux chose a "default interface"?
I'm not afraid of editing text files, but I'd like change networks fast and easy. I don't want to spend hours to adapt to a new access point... I'm really looking forward to the new wlan stack; maybe things will be getting easier then.
kei
Last edited by Kei (2007-05-04 12:36:00)

Okay, now KNetworkManager works (I forgot adding my user to the HAL group :] ).
There is still a problem - I know it's networkmanager related: At home I'm not using a DHCP server. KNetworkManager cannot handle static IP configuration. However, if I issue the command 'ifconfig ath0 192.168.0.12 subnet 255.255.255.0' while KNetworkManager is searching for a DHCP server I can even ping my gateway, so there is definitely a connection. Unfortunatly KNetworkManager closes this connections after a short period (dhcp timeout). Is there a quick'n'dirty workaround for this issue?
Another problem with KNetworkManager: When switching back to wired network, the DNS server is there :-) but the default gateway is not
Thanks for suggestions..
kei
//EDIT: In Debian there is a configuration file called /etc/network/interfaces. KNetworkManager uses the static IP information I enter there. However, when I modify /etc/rc.conf accordingly in ArchLinux, KNetworkManager does NOT use it.
//EDIT 2: After '/etc/rc.d/networkmanager restart' the static IP setting from /etc/rc.conf are used. The problem with the default gateway only occurs when the connection to one of the networks FAILS. After that failure the configuration is kind of messed up.
Altough it seems more like a dirty hack than a definite solution, I'm quite happy with the way it works now.
[CLOSED] <-- maybe I'm blind, but how can I change the topic to "[SOLVED] $Topic" ?
Last edited by Kei (2007-05-03 23:26:04)

Fans intermittently run @ full speed - problem solved - wireless card was culprit

I hope this helps someone in the future with this odd problem, that I see is rare but not unknown.
I have a P7-1222 which from new, would on about 1 in 10 powerups (i.e., random) have both CPU and case fans running full speed (several thousand RPM) making the machine very loud. They would reset to more normal speeds of ~ 1000 on a cold or hot reset.
TMPIN1 at time this occurred at powerup would, via HWMONITOR or SIW, show 99C (which was impossible), making the fans race.
Two motherboard replacements, PS substitution, CPU swap etc. did nothing. The intermittent problem persisted.
Now the culprit has been identified. I replaced the wireless LAN/Bluetooth combo PCI mini card with an identical unit from eBay (in this machine, an HP COMPAQ 615939-001 652279-001 WIRELESS N BLUETOOTH COMBO WLAN MINICARD). The problem of intermittent fan racing is now gone.
The wireless card in the machine seems to have been the culprit, perhaps occasionally sending a noise spike on powerup as it initialized onto the bus, thus affecting the Fintek F71858 LPCIO TMPIN1 reading and making it 99C, causing fans to race via BIOS thinking the machine was burning up!
Doing some investigating, I had found the following in the Data Sheet for the Fintek F71858 LPCIO chip ("Hardware KBC with ACPI, Temp. and Fan Control") used on numerous HP/Pegatron motherboards, including the Carmel/Carmel2 and other HP boards that use the same basic circuit layout:
=======================
8. PCB Layout Guide
F71858 adopts Current Mode measure method to do temperature detected. The measure data will not be affected by different process of CPU due to use current mode technology. This technology measures mini-voltage from the remote sensor so a good PCB layout must be cared about noise minimizing. The noises often come from circuit trace which is a track from remote sensor (CPU side) to detect circuit input (F71858 side). The signal on this track will be inducted mini-noises when it passes through a high electromagnetic area. Those effects will result in the mini-noises and show in the detected side. It will be reported a wrong data which you want to measure. Please pay attention and follow up the check list below in order to get an actual and real temperature inside the chip.
... Place the F71858 as close as practical to the remote sensor diode. In noisy environments, such as a computer main-board, the distance can be 4 to 8 inches. (typ). This length can be increased if the worst noise sources are avoided.
Noise sources generally include clock generators, CRTs, memory buses and PCI/ISA bus etc
=======================
And defective wireless cards can be a noise source too, it seems.

The issue was what I expected. I picked a new reader last night and everything works fine. My old card reader just didn't work with the new card.

[SOLVED] Wireless card not detected after upgrade

After running a pacman update today, my wireless card is no longer being detected. 'ip link' and 'iw dev' show no sign of it. My ethernet port is detected just fine.
I downgraded linux and systemd with no luck, thinking that they were the most likely culprits. Also, I dealt with the new /etc/passwd.pacnew and /etc/group.pacnew files created by the filesystem upgrade and ran the syslinux-install_update script to go along with the new version of syslinux. Besides a new mirrorlist, these were the only special cases pacman warned about when upgrading.
Here are the packages that were upgraded. I apologize for the long list but I'm finding myself out of options after several hours of struggling with this. Maybe somebody will see something I'm missing.
readline (6.3.005-1 -> 6.3.006-1)
bash (4.3.011-1 -> 4.3.018-1)
cairo (1.12.16-1 -> 1.12.16-2)
cpupower (3.14-2 -> 3.14-3)
e2fsprogs (1.42.9-2 -> 1.42.10-1)
gcc-libs (4.9.0-2 -> 4.9.0-3)
libtasn1 (3.4-1 -> 3.6-1)
gnutls (3.3.2-1 -> 3.3.4-1)
x264 (1:142.20140311-1 -> 1:142.20140311-4)
xvidcore (1.3.2-3 -> 1.3.3-1)
ffmpeg (1:2.2.2-3 -> 1:2.2.3-1)
filesystem (2013.05-2 -> 2014.05-2)
gcc (4.9.0-2 -> 4.9.0-3)
libx11 (1.6.2-1 -> 1.6.2-2)
gdk-pixbuf2 (2.30.7-1 -> 2.30.8-1)
perl (5.18.2-2 -> 5.20.0-2)
openssl (1.0.1.g-1 -> 1.0.1.h-1)
git (1.9.3-1 -> 2.0.0-1)
gnupg (2.0.22-2 -> 2.0.23-1)
gpgme (1.4.3-1 -> 1.5.0-1)
imagemagick (6.8.9.1-2 -> 6.8.9.1-3)
inputproto (2.3-1 -> 2.3.1-1)
lib32-gcc-libs (4.9.0-2 -> 4.9.0-3)
libcups (1.7.2-1 -> 1.7.3-3)
libproxy (0.4.11-2 -> 0.4.11-3)
libsystemd (212-3 -> 213-5)
libxcursor (1.1.14-1 -> 1.1.14-2)
linux (3.14.4-1 -> 3.14.5-1)
linux-headers (3.14.4-1 -> 3.14.5-1)
man-pages (3.67-1 -> 3.68-1)
mpfr (3.1.2.p5-1 -> 3.1.2.p8-1)
pacman-mirrorlist (20140405-1 -> 20140531-1)
perl-xml-parser (2.41-4 -> 2.41-5)
python-setuptools (3.6-1 -> 4.0.1-1)
python2 (2.7.6-3 -> 2.7.7-1)
rxvt-unicode-terminfo (9.20-1 -> 9.20-2)
rxvt-unicode (9.20-1 -> 9.20-2)
seabios (1.7.3.1-2 -> 1.7.5-1)
shared-mime-info (1.2-2 -> 1.3-1)
syslinux (6.02-8 -> 6.03pre12-3)
systemd (212-3 -> 213-5)
systemd-sysvcompat (212-3 -> 213-5)
transmission-cli (2.83-2 -> 2.83-3)
tzdata (2014c-1 -> 2014d-1)
xkeyboard-config (2.11-2 -> 2.12-1)
Last edited by zcal (2014-06-07 06:26:59)

I'll ask the standard issue questions. Did you perform a partial upgrade? If so, perform a pacman -Syu and try again.
Also, is the running kernel the same kernel that is installed? Compare the versions provided by uname -a and pacman -Qi linux and ensure they are exactly they are exactly the same revision.
Last edited by ewaller (2014-06-06 23:26:35)

[SOLVED]Wireless Card troubles

I am an absolute beginner trying to install Arch for the first time. Because of reasons, I am required to do this via Wireless. This is my only option. The computer I am using does not have an internal wireless card, so I purchased a Medialink USB dongle. When plugged in, the dongle recognizes my network, but connection to the network fails. The dongle uses an RT3070 chipset if I'm not mistaken, and the website has a driver available for Linux. Unfortunately, the instructions to install said driver are written for bash and I am not competent enough with Arch to handle this. I have the driver on a separate flash drive. Can you guys help?
URL to Medialink instructions: http://www.medialinkproducts.com/docs/M … _Linux.pdf
Last edited by Coltergeist (2013-07-19 17:57:25)

What I mean by that is, when I run the command iw dev I see the device, and then when I run wifi-menu _____, I see my wifi network. However, when I try to connect to it, the connection fails. I presume this is because I do not have the correct driver installed.
The output of dmesg tail is the same when the USB is attached versus not attached, but I didn't try to reboot with the device not attached, I'll warrant. I will not try to type out everything it says, because it's about 50 lines. It talks about the driver, says if there's an ACPI driver available I should use it instead of the native driver, and recognizes that it has an RT3070 chipset. At the end of all the info, it says the link is not ready.
The output of ip link when the device is attached is:
1: lo: <LOOPBACK,UP,LOWER_UP> MTU 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s8 <NO-CARRIER,BROADCAST,MULTICAST,UP> MTU 1500 qdisc mq state DOWN mode DEFAULT qlen 1000
link/ether 00:15:f2:a1:34:27 brd ff:ff:ff:ff:ff:ff
4: wlp0s29f7u4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT qlen 1000
link/ether 14:35:8b:0b:ad:8f brd ff:ff:ff:ff:ff:ff:ff
wlp0s29f7u4 is my device. It is the one that disappears from the list when I unplug the USB. It is also what appears when I use iw dev.
dmesg | grep firmware produces a message that informs me it's loading firmware file 'rt2870.bin' and then Firmware detected - version 0.29.
I've tried to supply as much info as possible. Let me know if there's anything else you need.
I do not have a smartphone, unfortunately.

[SOLVED] wireless card finds networks, but unable to connect

Hi,
I have a notebook with the wireless card "Intel Centrino Wireless-N 1000". According to this site, the drivers are part of the iwlwifi project, so it should be included in the kernel.
I installed wpa_supplicant and wireless_tools, and the interface wlan0 showed up:
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
link/ether 04:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT qlen 1000
link/ether 74:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
So, I configured my wifi-network without any encryption. I installed netcfg and copied /etc/network.d/examples/wireless-open to /etc/network.d/, changed the essid and enabled debugging:
DESCRIPTION='A simple opened wireless connection'
INTERFACE='wlan0'
SECURITY='none'
ESSID='wrt'
IP='dhcp'
# Uncomment this if your ssid is hidden
#HIDDEN=yes
WPA_OPTS="-f/home/sigma/log"
then I did
# netcfg wireless-open
:: wireless-open up
> WPA Authentication/Association failed
The debug file of netcfg says:
Trying to authenticate with f4:xx:xx:xx:xx:xx (SSID='wrt' freq=2462 MHz)
Trying to authenticate withf4:xx:xx:xx:xx:xx (SSID='wrt' freq=2462 MHz)
Trying to authenticate with f4:xx:xx:xx:xx:xx (SSID='wrt' freq=2462 MHz)
So I tried another wifi usb card, which works fine. I used the same netcfg profile as before and just changed INTERFACE='wlan0' to INTERFACE='wlan1'.
The debug file says:
Trying to authenticate with f4:xx:xx:xx:xx:xx (SSID='wrt' freq=2462 MHz)
Trying to associate with f4:xx:xx:xx:xx:xx (SSID='wrt' freq=2462 MHz)
Associated with f4:xx:xx:xx:xx:xx
CTRL-EVENT-CONNECTED - Connection to f4:xx:xx:xx:xx:xx completed (auth) [id=0 id_str=]
So, the settings seem to be fine, it's probably some problem with the driver or a missing module. Any kind of advice is appreciated.
Thanks in advance.
Last edited by sigma91 (2012-05-12 15:10:26)

The driver indeed has been troublesome lately for that card one reads. Have a try, if the following gets it working:
rmmod iwlwifi
modprobe iwlwifi 11n_disable=1 swcrypto=1
Then try to connect with your profile.

[solved] wireless - card generic netlink not found - iwlist scanning

I am usually able to connect over wireless networks using netcfg, but the following message that is appreciated since I upgraded my kernel to 3.x
> netcfg cesupa
:: cesupa up [BUSY]
nl80211: 'nl80211' generic netlink not found
nl80211: 'nl80211' generic netlink not found
I remember that once you updated the kernel, I had to redo the driver installation of wireless network card:
02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
and realized that if I use too much network scanning command the wireless network card seems to stop working suddenly.
> iwlist eth1 scan
eth1 Failed to read scan data : Invalid argument
the place where I always use the wireless network, there are 10 active networks in signal quality between 2/5 - 3/5
where the other laptops (Windows, Macs, and other distros) can see the normal way these networks
I've read the page for the configuration of my wireless network card on the wiki, but did not find any solution to my problem. any other ideas?
Last edited by abarahc (2011-09-21 12:18:49)

Why are you scanning eth1? I would think your wireless device would be wlan0. What is the output of:
# ifconfig wlan0 up
If this brings you back to the prompt and does not display an error then try running iwlist against wlan0.
The new kernel should have had no effect on your wireless configuration. Any reason why you are using netcfg instead of wicd or network-manager?
All the best,
Ian

[SOLVED] Wireless card disconnects

I've got the Encore ENLWI-N, according to lspci, it uses the RaLink RT2800 controller. However, after less than a second of acquire an IP, it sort of disconnects. Wicd still lists me as connected, but I can't ping anything, not even the router. Signal shows the strength to be 100%. My modules section in rc.conf doesn't have any explicit loading or blacklisting, but this is what lsmod shows:
rt2800pci 9248 0
rt2800lib 21550 1 rt2800pci
rt2x00usb 7572 1 rt2800lib
rt2x00pci 4949 1 rt2800pci
crc_ccitt 1315 2 rt2860sta,rt2800pci
rt2x00lib 25109 4 rt2800pci,rt2800lib,rt2x00usb,rt2x00pci
led_class 2347 1 rt2x00lib
mac80211 182791 3 rt2x00usb,rt2x00pci,rt2x00lib
cfg80211 141568 2 rt2x00lib,mac80211
eeprom_93cx6 1328 1 rt2800pci
I also left my PC for a while without starting X, and I got this traceback:
Pid: 3372, comm: ifconfig Tainted: P C 2.6.34-ARCH #1 A8N32-SLI-Deluxe/System Product Name
RIP: 0010:[<ffffffffa10b5f0e>] [<ffffffffa10b5f0e>] rt2x00queue_init_queues+0x6e/0xb0 [rt2x00lib]
RSP: 0018:ffff88007b26fb98 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000030
RDX: 0000000000000000 RSI: 0000000000000286 RDI: 0000000000000286
RBP: ffff88007b26fbb8 R08: 000000000000fff5 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000008 R12: ffff88007b630000
R13: ffff88007b04d380 R14: ffff88007b630038 R15: ffff88007b04d048
FS: 00007fab43097700(0000) GS:ffff880001900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 000000007c5ab000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process ifconfig (pid: 3372, threadinfo ffff88007b26e000, task ffff88007b101c80)
Stack:
ffff88007b04d380 0000000000000000 ffff88007b6bf6c0 0000000000000000
<0> ffff88007b26fbd8 ffffffffa10b3d95 ffff88007b04d380 ffff88007b04c480
<0> ffff88007b26fc08 ffffffffa10b3e68 ffff88007b26fc28 ffffffffa10300d1
Call Trace:
[<ffffffffa10b3d95>] rt2x00lib_probe_dev+0x475/0x4f0 [rt2x00lib]
[<ffffffffa10b3e68>] rt2x00lib_start+0x58/0xd0 [rt2x00lib]
[<ffffffffa10300d1>] ? cfg80211_netdev_notifier_call+0xb1/0x4b0 [cfg80211]
[<ffffffffa10b46ad>] rt2x00mac_start+0x1d/0x30 [rt2x00lib]
[<ffffffffa1081203>] ieee80211_open+0x3b3/0x7d0 [mac80211]
[<ffffffff812bcabf>] __dev_open+0xaf/0x100
[<ffffffff812bd0fc>] __dev_change_flags+0x9c/0x180
[<ffffffff812bd293>] dev_change_flags+0x23/0x70
[<ffffffff81317548>] devinet_ioctl+0x668/0x800
[<ffffffff810f7e53>] ? handle_mm_fault+0x1c3/0xab0
[<ffffffff81318b88>] inet_ioctl+0x78/0x90
[<ffffffff812a526b>] sock_do_ioctl+0x2b/0x70
[<ffffffff812a5561>] sock_ioctl+0x71/0x2d0
[<ffffffff811318cc>] vfs_ioctl+0x3c/0xd0
[<ffffffff81131ecc>] do_vfs_ioctl+0x7c/0x540
[<ffffffff810b4b40>] ? call_rcu_sched+0x10/0x20
[<ffffffff810b4b59>] ? call_rcu+0x9/0x10
[<ffffffff81132411>] sys_ioctl+0x81/0xa0
[<ffffffff81009ec2>] system_call_fastpath+0x16/0x1b
Code: 49 39 c4 74 5f 4c 89 e7 e8 70 ef ff ff 66 41 83 7c 24 1c 00 74 3f 31 db 0f 1f 44 00 00 89 d8 49 8b 54 24 08 83 c3 01 48 8d 04 80 <48> c7 04 c2 00 00 00 00 48 8d 3c c5 00 00 00 00 49 8b 45 08 49
RIP [<ffffffffa10b5f0e>] rt2x00queue_init_queues+0x6e/0xb0 [rt2x00lib]
RSP <ffff88007b26fb98>
CR2: 0000000000000000
---[ end trace f5324da0dac64f6b ]---
I'm not sure what else I can do. Help me, Archlinux Forums, you're my only hope.
Last edited by Berticus (2010-08-19 16:30:40)

I'll ask the standard issue questions. Did you perform a partial upgrade? If so, perform a pacman -Syu and try again.
Also, is the running kernel the same kernel that is installed? Compare the versions provided by uname -a and pacman -Qi linux and ensure they are exactly they are exactly the same revision.
Last edited by ewaller (2014-06-06 23:26:35)

G500 Driver_Power_State_Failure problem most likely related to Wireless Card

I recently upgraded my Lenovo G500 laptop to 8.1.
After that, I've been constantly getting BSOD every time I modify some settings on my WIreless card (Broadcom 802.11n Network Adapter). For instance, changing my MAC under the"Locally Administered MAC Address" causes the Wireless configuration window to stop responding, then my wireless adapter becomes permanently disabled (I try to enable it and it says that it is enabling but the adapter remains faded out and locked in a disabled state) unless I restart or power down my laptop. If I restart, the laptop hangs for 3-5 minutes and then a BSOD comes up and suggests that I look online for DRIVER_POWER_STATE_FAILURE.
I have updated the adapter as well as most, if not all outdated drivers on my laptop with the 8.1 drivers offered on Lenovo's support pages (This includes power management, BIOS, LAN, Audio, etc.). Even attempting to voluntarily disable my wireless card causes the BSOD.
As long as I don't touch/modify such settings, I have wireless internet and all seems fine but once I do what I stated above, my laptop crashes with a BSOD. I have looked up and searched about such a BSOD but my laptop has zero problems when I put it to sleep or wake it up. My laptop functions practically flawless except for when changing/modifying settings on my wireless card.
For instance, on Whocrashed.exe:
On Thu 11/7/2013 9:33:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110713-17031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150B36)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00000EB5040, 0xFFFFD000205F8860)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 11/7/2013 9:33:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00000EB5040, 0xFFFFD000205F8860)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time
On bluescreenview:
Bug check string: DRIVER_POWER_STATE_FAILURE
Bug check code: 0x0000009f
Parameter 1: 00000000`00000004
Parameter 2: 00000000`0000012c
Parameter 3: ffffe000`00eb8040
Parameter 4: ffffd000`20472860
Processor: x64
Caused by driver: NETIO.SYS
Caused by address: NETIO.SYS+1ddb2
Crash address: ntoskrnl.exe+150b36
I ran SFC /scannow and it did detect corrupted files but that has been resolved using the Restorehealth command prompt. I have tried booting to safe mode, uninstalling the adapter and then updating straight to the most current 8.1 driver and that still causes the BSOD.
I'm almost certain that my wireless card probably is defective, or the laptop is defective. I'm still under warranty but I'm hoping to fix this issue before resorting to what I deem as last resorts of factory restoring the laptop or calling Lenovo support.
I am also providing minidumps, driver lists and a whole ton of useful information on my Skydrive:
http://sdrv.ms/17OIYda
Any suggestions or help on this matter would be greatly appreciated as I feel like I've exhausted all other methods.
Moderator Note; subject edited; system type added

"If I restart, the laptop hangs for 3-5 minutes and then a BSOD comes up and suggests that I look online for DRIVER_POWER_STATE_FAILURE."
I had the exact same problem on a Thinkpad Helix after upgrading to Windows 8.1, although I do not know if it was in anyway related to the wireless hardware as you described. However, I noted that in the Device Manager many wireless hardware components had been highlighted with an exclamation mark since the problem had occured (e.g. Bluetooth, Geolocation, Broadband). Here is how I fixed it:
1. I went to System Settings / Device Manager.
2. Disabled all devices that were highlighted with an exclamation mark. I noted that the Device Manager would not respond after disabling so I closed it and then chose to not wait (i.e. forced the Device Manager to close).
3. Repeated step (2.) until all devices highlighted with an exclamation mark were disabled.
4. Restarted the laptop (I don't know if I had to force the shut down via power off at that time, but it may be necessary or you wait for the BSOD).
5. Repeated step (1.) and uninstalled all the drivers of the devices disabled in steps (2.) to (3.), enabling the option to remove the driver from the system, where possible.
6. Restarted the system. This time the shutdown should only take a few seconds.
So far, everything works fine again and I cannot identify any limitations through the disabling and uninstalling of devices (esp. wireless devices do work flawlessly).
Hope this works for some of you guys out there as well. Let me know.
Good luck!
neophilos

[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!

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.

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?

Fujitsu Amlio Li 2735 Wireless card issues

Hello,
I have a laptop that I want to run Arch Linux but I have a issue that I do run into with many Linux distros, not just Arch in particular. The issue is that Fujitsu have made it that my wireless card does not automatically start on boot and it does not have a physical switch on the laptop, what you have to do (For windows at least) is have a application installed that allows you to enable the card. Now this software is only avalible on Windows, not Linux but, Ubuntu and Debian based distros seem to be able to automatically enable the card on boot. This does not happen however in other distros like CentOs.
So I know that it is possible to get the drivers working under linux but I have no idea how to get them working in Arch and preferably in the live cd install although, I can install the base system through other means but I would like to use the internal card.
From lspci | grep -i net it is identified as:
Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 04)
And from iwconfig
wlp8s0 IEEE 802.11bg ESSID:off/any
Mode: Managed Access Point: Not-Associated Tx-Power=off
Retry long limit:7 RTS thr:off FragmentL thr:off
Encryption key:off
Power Management:off
ip link set wlp8s0 up does nothing and dmesg | grep firmware produces no output.
(I do know there is a hardware 'modification' that you can perform to break contact with one of the pins on the wireless card but I would rather leave that as a last resort)
Any help is appreciated and I hope you can solve my issue.
Last edited by Nimphina (2013-02-06 21:46:54)

the sad clown wrote:
The easiest way to figure it out is to boot a Ubuntu live cd, and check dmesg for what is enabling your wireless card, then check the configurations associated with that event and translate them to your arch setup.
Edit: You might want to also run "rfkill list" and see if it really is a hard lock that is preventing the card from working.
The card seems to have a soft lock on it.
I did today somehow manage to get the card to work on Arch but I am not 100% how or why is started enabled, I'm guessing it was somehow enabled from this morning when I used a liveUSB LMDE.
Anyway, this is the dmesg I get under that live USB:
[ 14.395332] Registered led device: ath5k-phy0::rx
[ 14.395356] Registered led device: ath5k-phy0::tx
[ 14.395369] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
[ 14.619395] cfg80211: World regulatory domain updated:
[ 14.619400] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 14.619404] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 14.619407] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 14.619411] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 14.619414] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 14.619418] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 14.619437] cfg80211: Calling CRDA for country: AM
[ 14.626874] cfg80211: Regulatory domain changed to country: AM
[ 14.626879] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 14.626883] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 14.626886] cfg80211: (5170000 KHz - 5250000 KHz @ 20000 KHz), (N/A, 1800 mBm)
[ 14.626889] cfg80211: (5250000 KHz - 5330000 KHz @ 20000 KHz), (N/A, 1800 mBm)
(Full dmesg is here https://dl.dropbox.com/u/47430381/dsmeg.txt)
EDIT:
Regarding the softblock, I spent the last hour or two trying to get it working and found I could just run: rfkill unblock 0
Excuse my Linux noobines, I don't usually spend a lot of time getting my wifi working via CLI.
But on a final note, it there a way to get this to work on start up? Via bash scripts of similar?
Last edited by Nimphina (2013-02-07 22:14:15)

Ralink RT3290 802.11bgn Wifi Card - Possible Issues [SOLVED]

Dear Lucky owners of such a card, At least from my experience I realized it is not that bad card, even if most probably many production pieces were faulty or not working properly, and many issues can be resolved. Let me list in order of time the issues I faced and solved about this wifi card: 0) First issue is not about RT3290 card itself but it is related to 802.11w encryption compatibility in between Windows8 and Cisco not allowing 802.11n speed rates so failing to G speeds only. - SOLUTIONS: a. As first test I would recommend trying another router from different brand to see if connecting at 802.11n speed rates b. If you prove point a issue, then try to fix the issue based on following post (in which you can see the reply from myself Emanuele on the 29th of Nov 2014): https://supportforums.cisco.com/document/113836/windows-8-clients-cant-associate-cisco-unified-wireless 1) Signal strenght issue: original wifi card RT3290 installed on my HP laptop was having really bad antenna, with signal fluctuating and sometimes bad even really close to any Router I tried. - SOLUTION: Replace the RT3290 card even with same new card. (In my case as laptop was under warranty, I proved the issue via screenshots and they replaced with new card solving my signal strenght issue). 2) Original issue (1) was actually resolved after HP replaced the wifi card with same model, but with the latest driver installed 5.0.45 seems like wifi rates change too frequently based on high sensitivity of the driver itself, so that suggested me issue was still there, so making me re-testing anything from scratch. - SOLUTION: Install 5.0.37 Driver - frequent rate changes issue (with driver 5.0.45) disappears and sensitivity of signal to rate changes seems to be a really good compromise to have good throughput. 3) To check out 2nd issue above I started again using a third party software inSSIDer free version to check signal while I was doing speedtest on web.
- RESOLUTION:
inSSIDer normally works on Windows7 without any issue but on Windows8 (at least tested with RT3290) I have just discovered somehow this software was slowing down wifi card performance drastically showing a speed up to 0.1Mbps rather than 40Mbps. Simply closing the application issue was not recurring, so uninstalled it and after solving all the other issues above this card works perfectly (at least so far ) Hope this post will be informative and will help other about-to-get-mad guys as me

Hye. After I read up your solutions, I am quite impressive and really want to try out those solutions. However, I am not very computer wise and I really appreciate if you make a video on solving this problem. Up to you if you want to upload it on the youtube (so that others with similar problem can view it and solve the problem too) or you want to direct email to me ( [email protected] ). I really hope you can help me because I am stuck with this problem since last year. Thank you!!!

Wireless card (RTL8188CE) on Thinkpad L530? [seems solved]

I recently bought a Thinkpad and now am in the process of configuring Arch on it.. But the wireless card doesn't work as it should...
lspci says that the card is:
06:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01)
The driver used is rtl8192ce, which should be fine as far as I know... and I'm on Kernel 3.4.4-2..
Now the thing is, it works, but very unstable... wpa_supplicant connects without problems, it works the same way with dhcpd or static, which is :
At one moment, it works perfectly fine, downloads packages I want to install, etc,
one minute later it can not find any host (Unknown error).
When I ping something - sometimes it works instantly with normal time (about 50ms), sometimes not at all, sometimes with time of over 1000ms(!!!) and about 40% packet loss.
What is interesting is that it seems like pinging the router itself works without problems all the time (but with initial lag). But the router can't be the problem, the card itself is fine too... So I suppose the driver is broken somehow? (The wifi on the same laptop works fine with Windows and the same network)
I don't know what to do...
Thanks in advance!
Update:
I started using networkmanager and strangely the problems vanished I hope it'll stay that way...
Last edited by icetonic (2012-08-05 19:56:22)

Yeah, I had the bios whitelist removed for my E430. I searched the thread, and you seem to be right that flashing the bios seems to be somewhat difficult. Though I think that the references there then to be for the x230 tablet. I didn't search all that hard, but the few posts I viewed were all the tablet.
I think what bricked my laptop was the UEFI bug. I got a kernel panic, and the dump was all funky looking. Normally you can somewhat decipher what caused the panic and whatnot, nothing of the sort here, I could barely tell it was a kernel panic. After that I couldn't boot. I couldn't even get a POST, which is what made me suspicious of the UEFI thing. Apparently what is happening when those Samsungs were bricked was that the NVRAM was being written to with garbage. So I thought that maybe that is where the missing info from the kernel panic went. Again, this is pure speculation, as I have no way of confirming, but I contacted Matthew Garrett and he said that my report was similar to a few other ThinkPad brickings that had also been reported to him.
The way my problem was "solved" was warranty repair. Essentially my warranty was voided when I flashed the modified bios, but if the bios is unreachable, they have no way of telling that (and I also think that my issue was totally unrelated to having a modified bios anyway), so they replaced my motherboard.
So now I have a Windows 8 bios, which is fast to POST, as this is one of the specifications for the windows 8 certification. But Serg008 from that thread I linked to told me that although he can modify the bios itself, it is again a case of being unable to flash the then modified bios to the machine. So I was stuck with the RTL8188CE until I figured out the relevant FRU for the Intel card that was an option with my machine. I found one of them on ebay just the other day and it works amazingly. Though now I have a top of the line 2x2 Intel card that I can't use (6235) and apparently has to have a very recent chipset to use. So I cannot even put it in an older machine either... I'll find a use for it eventually though.
So good luck with your issue. I'd say take a look at the FRU parts list for your machine. The list for teh E430 didn't include the Intel card for some reason, so a bit of hunting was necessary. But it might be included in your machine's list. When you find it, you can at least go to this page to see how much IBM or Lenovo will charge you for it.

[SOLVED]Wireless card (Broadcom) issue

Similar Messages

Maybe you are looking for