Re: Comprehensive ndiswrapper troubleshooting guide
Hi!
I just wanted to say thankyou very much for this great HowTo. I read the first post and followed the instructions precisely. After having some problems read the post to SomeSmartGuy (page 2) and finally got my card working (currently posting with the wifi connection). I have rebooted and had no problems.
For the record, I have a Dell C600 with am Airgo Networks AGN300 wifi PCMCIA card (on a Linksys WPC54GX4 card). The PCI ID is 17CB:0002. This specific card is not listed in the sourceforg site as being supported or not supported by ndiswrapper. OS is Ubuntu 8.10. Downloaded the windows drivers from the Linksys website. Ndiswrapper came with the distro so it was already installed.
To make ndiswrapper work and install the drivers I used this tutorial
HTML Code:
https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper
. To troubleshoot the wireless connection I followed this guide
HTML Code:
https://help.ubuntu.com/community/WifiDocs/WirelessTroubleShootingGuide
, although there wasn't really much to troubleshoot.
When I unzipped the windows driver, I found there was one .inf file (tmimo3P.inf) and two .sys files (TMIMO30P.sys and TMIMO31P.sys). When installing the drivers with ndiswrapper I used:
Code:
sudo ndiswrapper -i /your folder/WPC54GX4-V1.00.09-2.0.1.19/tmimo3p.inf
The ndiswrapper module automatically loaded the TMIMO31P.sys file, which should be the correct one to use.
The card was recognized immediately. I then configured the ESSID using Network Configuration (the GUI interface in System/Preferences). My router has WPA2 security (the wpa-supplicant module was loaded with the distro as well) and I use DHCP to get the ip address.
Although it might look really difficult, it adds up to what tattoo-wolf posted in
HTML Code:
http://ubuntuforums.org/showthread.php?t=795817&highlight=airgo+networks+AGN300
(look for post #10). It's as simple as that and the card works. I did not however put the last three lines in the rc.local file. I did modify my /etc/modules file so as for the ndiswrapper module to be loaded on boot. If you do have any problems, do rely on this thread for help.
Thanks once more phyteas22 for an excelent HowTo and all your help to the community.
Re: Comprehensive ndiswrapper troubleshooting guide
Vulkano and Manyette: thanks for the feedback and I'm glad you both got things working. Hope you continue to enjoy Ubuntu :)
Re: Comprehensive ndiswrapper troubleshooting guide
For info only, I should have added that 9.04 loaded the Ubuntu drivers out of the box, but it even offered to install the madwifi drivers as an option if the ubuntu atheros drivers did not work. I found little difference between the two drivers, but is sure was nice to have that option. The Ubuntu troops have really make this a joy.
Don
Re: Comprehensive ndiswrapper troubleshooting guide
Any help would be appreciated! I've been on this for a few weeks now with no luck. Basically wifi was fine for the most part. I've used ubuntu since feisty and through successive upgrades had to tweak the wifi, even Jaunty, though it eventually worked.
I switched to wicd as I was unable to detect networks I had not previously used and even that was fine. I tried playing with it to add a bluetooth headset, but failed, and the wifi still worked. i performed an upgrade, it still worked. Then out of the blue _____!
I know there is no such thing as out of the blue, so if someone can help with this mystery it would be appreciated. I have poured through the forums but can't seem to find enough help.
This guide by the way is excellent and got me further, but still not quite there. Unfortunately with all the modifications, I'm not sure where things lay now, but here's what I have:
:~/Desktop$ lspci -nn | grep 14e4
Code:
03:00.0 Network controller [0280]: Broadcom Corporation BCM4328 802.11a/b/g/n [14e4:4328] (rev 01)
:~/Desktop$ ndiswrapper -l
Code:
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
bcmwl5 : driver installed
device (14E4:4328) present (alternate driver: ssb)
I don't want to lose my ethernet card which is apparently calling ssb (which was also blacklisted). if there was some workaround to play with the order or something that might be helpful.
:~/Desktop$ ndiswrapper -v
Code:
utils version: '1.9', utils version needed by module: '1.9'
module details:
filename: /lib/modules/2.6.28-13-generic/kernel/ubuntu/ndiswrapper/ndiswrapper.ko
version: 1.53
vermagic: 2.6.28-13-generic SMP mod_unload modversions 586
:~/Desktop$ lsmod | grep b43
:~/Desktop$ lsmod | grep ndiswrapper
Code:
ndiswrapper 193436 0
:~/Desktop$ ls -l /etc/rc.local
Code:
-rwxr-xr-x 1 root root 437 2009-07-12 12:24 /etc/rc.local
:~/Desktop$ cat /etc/rc.local
Code:
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
#
#for wl driver?
#rmmod b43
#rmmod ssb
#rmmod wl
#modprobe wl
modprobe -r b44
modprobe -r ssb
modprobe ndiswrapper
modprobe b44
exit 0
:~/Desktop$ lshw -C network
Code:
WARNING: you should run this program as super-user.
*-network
description: Wireless interface
product: BCM4328 802.11a/b/g/n
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 01
serial: 00:19:7d:a6:ed:d3
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.53+Broadcom,02/20/2008, 4.170. latency=0 module=ndiswrapper multicast=yes wireless=IEEE 802.11g
*-network
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: 1
bus info: pci@0000:05:01.0
logical name: eth4
version: 10
serial: 00:1b:38:0b:8d:bb
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=8139too driverversion=0.9.28 ip=192.168.10.101 latency=64 maxlatency=64 mingnt=32 module=8139too multicast=yes
*-network DISABLED
description: Ethernet interface
physical id: 2
logical name: pan0
serial: 8e:73:aa:91:14:d6
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A multicast=yes
:~/Desktop$ ifconfig
Code:
eth4 Link encap:Ethernet HWaddr 00:1b:38:0b:8d:bb
inet addr:192.168.10.101 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::21b:38ff:fe0b:8dbb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:116318 errors:2048 dropped:2052 overruns:2048 frame:0
TX packets:84722 errors:0 dropped:0 overruns:6 carrier:0
collisions:0 txqueuelen:1000
RX bytes:149220048 (149.2 MB) TX bytes:10503491 (10.5 MB)
Interrupt:21 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1691 errors:0 dropped:0 overruns:0 frame:0
TX packets:1691 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:793187 (793.1 KB) TX bytes:793187 (793.1 KB)
wlan0 Link encap:Ethernet HWaddr 00:19:7d:a6:ed:d3
UP BROADCAST RUNNING 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:17 Memory:d0200000-d0204000
wlan0:avahi Link encap:Ethernet HWaddr 00:19:7d:a6:ed:d3
inet addr:169.254.10.217 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:17 Memory:d0200000-d0204000
:~/Desktop$ iwconfig
Code:
lo no wireless extensions.
eth4 no wireless extensions.
wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:270 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
pan0 no wireless extensions.
:~/Desktop$ cat /etc/NetworkManager/nm-system-settings.conf
Code:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=true
:~/Desktop$ iwlist scan #
Code:
lo Interface doesn't support scanning.
eth4 Interface doesn't support scanning.
wlan0 Scan completed :
Cell 01 - Address: 00:24:01:29:C5:D7
ESSID:"dlink"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:18/100 Signal level:-84 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:14:D1:51:03:AA
ESSID:"Home"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:89/100 Signal level:-39 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
pan0 Interface doesn't support scanning.
:~/Desktop$ cat /etc/modules
Code:
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
#snd_bt_sco, sco =BT
lp
sbp2
#ndiswrapper
snd_bt_sco
sco
:~/Desktop$ cat /etc/modprobe.d/blacklist
Code:
blacklist bcm43xx
blacklist b43
blacklist b43legacy
blacklist ssb
:~/Desktop$ dmesg | grep -e ndis -e wlan
Code:
[ 18.572802] ndiswrapper version 1.53 loaded (smp=yes, preempt=no)
[ 19.308508] ndiswrapper: driver bcmwl5 (Broadcom,02/20/2008, 4.170.75.0) loaded
[ 19.308794] ndiswrapper 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 19.308882] ndiswrapper 0000:03:00.0: setting latency timer to 64
[ 19.324017] ndiswrapper: using IRQ 17
[ 19.540910] wlan0: ethernet device 00:19:7d:a6:ed:d3 using NDIS driver: bcmwl5, version: 0x4aa4b00, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4328.5.conf
[ 19.540955] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
[ 19.552302] usbcore: registered new interface driver ndiswrapper
[ 25.022493] ndiswrapper (add_wep_key:841): adding encryption key 1 failed (C0010015)
[ 32.319644] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[16050.738702] ADDRCONF(NETDEV_UP): wlan0: link is not ready
:~/Desktop$ ls /etc/udev/rules.d
Code:
45-libmtp7.rules 50-libfprint0.rules 70-persistent-cd.rules 70-persistent-net.rules 85-brltty.rules README
:~/Desktop$ cat /etc/udev/rules.d/70-persistent-net.rules
Code:
# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.
# PCI device 0x10ec:0x8139 (8139too)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0f:b0:d2:64:40", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x14e4:0x4328 (ndiswrapper)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:19:7d:a6:ed:d3", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
# PCI device 0x1011:0x0019 (tulip)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:a0:0c:90:68:1b", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
# PCI device 0x14e4:0x4328 (wl)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:19:7d:a6:ed:d3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
# PCI device 0x8086:0x1092 (e100)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:36:9b:43:4b", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
# PCI device 0x8086:0x4222 (iwl3945)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:18:de:53:97:3a", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan1"
# PCI device 0x10ec:0x8139 (8139too)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:38:0b:8d:bb", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"
:~/Desktop$ cat /etc/resolv.conf
Code:
domain phub.net.cable.rogers.com
search phub.net.cable.rogers.com
nameserver 192.168.10.1
:~/Desktop$ cat /etc/network/interfaces
Code:
auto lo
iface lo inet loopback
iface wlan0 inet dhcp
wireless-key s:********************
wireless-essid Home
auto wlan0
iface eth4 inet dhcp
auto eth4
Wicd shows no wireless networks available.
Re: Comprehensive ndiswrapper troubleshooting guide
soumo: based on everything you posted (thanks for including so much information, by the way), I suspect the problem is simply that wicd has the wrong name for the wireless interface.
If you click the "Preferences" button in wicd, a dialogue window will open. One of the fields will say something like "wireless interface." Make sure this value is set to "wlan0", then restart wicd and try scanning again. If this doesn't help, please post a screenshot of your wicd preferences window.
Also, I'm not positive, but I think your card would work with the 'wl' driver, obviating the need for ndiswrapper. wl is a driver released by Broadcom last summer that supports certain Broadcom-based wireless cards, and in particular the a/g/n ones, like yours.
If you want to give wl a try, run:
Code:
sudo rmmod ndiswrapper
sudo rmmod b43
sudo rmmod b44
sudo rmmod ssb
sudo rmmod wl
sudo modprobe wl
At this point, your wireless interface will hopefully be up--run "iwconfig" or "lshw -C Network" to check. If it is, we can figure out how to make wl drive the card permanently, if you're interested. wl isn't necessarily better than ndiswrapper, but it might be less fickle.
An important note is that I believe wl will cause your wireless interface to be named eth* instead of wlan*. So you would have to change the preferences in wicd to reflect this if you switch to wl. It looks like your wireless interface would probably be assigned the name eth5 under wl, but I'm not sure (any idea why your wired interface is eth4 instead of eth0?).
Re: Comprehensive ndiswrapper troubleshooting guide
pytheas22: Thank you, thank you, thank you! For the very quick and correct reply! It did the trick. I can now see the networks, and I am still unable to connect but will try to debug further, I think it may be encryption.
I am a bit chicken to try the new driver but will do some reading to figure out the pros & cons.
I can't really guess why it's eth4 but do know the wireless was called eth2 at some point. I'm wondering if I should start playing around now to relabel.
I will message again if I can't get the wireless up, but again thanks!
Your help is very appreciated.
Re: Comprehensive ndiswrapper troubleshooting guide
So still no wifi, but at least the networks are showing up in the wicd gui.
I ran the above steps again and here are the differences:
For ifconfig, the following is missing:
Quote:
wlan0:avahi Link encap:Ethernet HWaddr 00:19:7d:a6:ed:d3
inet addr:169.254.10.217 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:17 Memory:d0200000-d0204000
Under iwconfig, a "nickname has been added" to the first line of wlan0:
Quote:
IEEE 802.11g ESSID:off/any Nickname:"WirelessLibrary"
This is a location I tried earlier today, but am no longer near.
For cat /etc/modules,
is not commented out.
dmesg | grep -e ndis -e wlan
Quote:
ndiswrapper (add_wep_key:841): adding encryption key 1 failed (C0010015)
ADDRCONF(NETDEV_UP): wlan0: link is not ready
these persist and there are more instances of the link not ready messages.
BTW, cat /etc/udev/rules.d/70-persistent-net.rules as above seems to answer the question of why my ethernet card i slisted as eth4 instead of eth0, though I'm not aware of what those other interfaces are (I do have firewire but it's not hooked up to anything).
I just realized that under cat /etc/network/interfaces that the ESSID & passwords do not match up! The password is my home network password, but the ESSID is a different home network...
Ideas?
Re: Comprehensive ndiswrapper troubleshooting guide
soumo: first of all, unless you use static IPs or have other special networking needs, you should edit /etc/network/interfaces and erase everything except the lines:
Code:
auto lo
iface lo inet loopback
Then try rebooting and see if things work better. Conflicting information in the interfaces file could have been the source of your failure to connect.
If that doesn't help, please post the output of the command:
and tell me the name of the network you're trying to connect to (ideally, it will be unsecured or use only WEP encryption). I'll then give you commands to try connecting from the command line, which will help figure out why wicd doesn't want to make the connection.
I'm not sure what the "adding encryption key 1 failed" message means, but I suspect it has to do with the conflicting information in your interfaces file. Otherwise, it's probably a bug in ndiswrapper, in which case you may need to try compiling from ndiswrapper source or trying a different Windows driver. But I'd hold off on that for the time being; hopefully the problem is not that complicated.
I also don't know why udev wanted to rename your ethernet device to eth4, but it shouldn't be hurting anything.
Re: Comprehensive ndiswrapper troubleshooting guide
pytheas22: Thanks again! Quantum leaps are being made.
I did as suggested and this time when trying to connect to the home network, I saw a brief line in the status bar of wicd that mentioned something about 'bad password' (though I am certain it was correct).
Since then the cycling has been to quick to read any such message. Furthermore I tried it on the unsecured network at home as well, no dice.
sudo iwlist scan:
Quote:
lo Interface doesn't support scanning.
eth4 Interface doesn't support scanning.
wlan0 Scan completed :
Cell 01 - Address: 00:14:D1:51:03:AA
ESSID:"Home"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:95/100 Signal level:-35 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:24:01:29:C5:D7
ESSID:"dlink"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:18/100 Signal level:-84 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
pan0 Interface doesn't support scanning.
As you mentioned above, "adding encryption key 1 failed" may be related to the interfaces...
dmesg | grep ndis
Quote:
[ 14.999803] ndiswrapper version 1.53 loaded (smp=yes, preempt=no)
[ 15.835522] ndiswrapper: driver bcmwl5 (Broadcom,02/20/2008, 4.170.75.0) loaded
[ 15.835771] ndiswrapper 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 15.835860] ndiswrapper 0000:03:00.0: setting latency timer to 64
[ 15.850709] ndiswrapper: using IRQ 17
[ 16.085719] usbcore: registered new interface driver ndiswrapper
The message now seems to have disappeared!
I am going ahead manually to save time, but if I did this wrong let me know...to follow after I reboot.
Re: Comprehensive ndiswrapper troubleshooting guide
For the unsecured network:
:~/Desktop$ sudo ifconfig wlan0 down
~/Desktop$ sudo dhclient -r wlan0
Quote:
There is already a pid file /var/run/dhclient.pid with pid 5919
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit
http://www.isc.org/sw/dhcp/
Listening on LPF/wlan0/00:19:7d:a6:ed:d3
Sending on LPF/wlan0/00:19:7d:a6:ed:d3
Sending on Socket/fallback
:~/Desktop$ sudo ifconfig wlan0 up
:~/Desktop$ sudo iwconfig wlan0 essid "dlink"
:~/Desktop$ sudo iwconfig wlan0 mode Managed
:~/Desktop$ sudo dhclient wlan0
Quote:
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit
http://www.isc.org/sw/dhcp/
EBox: status module network: [ DISABLED ]
EBox: status module network: [ DISABLED ]
Listening on LPF/wlan0/00:19:7d:a6:ed:d3
Sending on LPF/wlan0/00:19:7d:a6:ed:d3
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
EBox: status module network: [ DISABLED ]
EBox: status module network: [ DISABLED ]
Take a look at the last line below:
:~/Desktop$ dmesg | grep wlan
Quote:
[ 16.533032] wlan0: ethernet device 00:19:7d:a6:ed:d3 using NDIS driver: bcmwl5, version: 0x4aa4b00, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4328.5.conf
[ 16.533084] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
[ 49.953397] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 175.452646] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 206.326124] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 223.971050] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 234.579393] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 259.675702] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 397.177828] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 435.491820] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
No luck. I'll try the secured network next, rebooting...
