----- Original Message ----- > From: Mick <michaelkintz...@gmail.com> > On Thursday 08 Sep 2011 04:52:44 BRM wrote: >> ----- Original Message ----- >> >> > From: Mick <michaelkintz...@gmail.com> > >> > Hmm ... what is the error/warning that comes up? >> >> pneumo-martyr wpa_supplicant # /etc/init.d/net.wlan0 start >> * Bringing up interface wlan0 >> * Starting wpa_supplicant on wlan0 ... >> Line 17: WPA-PSK accepted for key management, but no PSK configured. >> Line 17: failed to parse network block. >> Failed to read or parse configuration >> '/etc/wpa_supplicant/wpa_supplicant.conf'. * start-stop-daemon: > failed >> to start >> `/usr/sbin/wpa_supplicant' > >> [ !! ] * ERROR: net.wlan0 failed to start > > Ah! This shows that your /etc/wpa_supplicant/wpa_supplicant.conf has > something wrong with it and it can't be parsed. Please check the file's > > access rights and its contents. This is what it looks like here: > > $ ls -la /etc/wpa_supplicant/wpa_supplicant.conf > -rw-r--r-- 1 root root 33388 Jun 14 15:02 > /etc/wpa_supplicant/wpa_supplicant.conf
That error only comes up when those two lines are commented out. If I return them, then all is fine. >> > # iwlist wlan0 scanning >> >> Simply returns: >> >> wlan0 No scan results > > Your device has not been initiated, therefore it would not be able to scan > until then. True. >> It also returns "0". I have wlan0 logs directed to > /var/log/net/wireless, >> here's the output from the last attempt: >> >> Sep 7 23:01:43 pneumo-martyr NetworkManager: <info> (wlan0): driver >> supports SSID scans (scan_capa 0x01). Sep 7 23:01:43 pneumo-martyr >> NetworkManager: <info> (wlan0): new 802.11 WiFi device (driver: >> 'b43legacy') Sep 7 23:01:43 pneumo-martyr NetworkManager: > <info> >> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1 Sep 7 >> 23:01:43 pneumo-martyr NetworkManager: <info> (wlan0): now managed > Sep 7 >> 23:01:43 pneumo-martyr NetworkManager: <info> (wlan0): device state >> change: 1 -> 2 (reason 2) Sep 7 23:01:43 pneumo-martyr NetworkManager: >> <info> (wlan0): bringing up device. Sep 7 23:01:43 pneumo-martyr > kernel: >> ADDRCONF(NETDEV_UP): wlan0: link is not ready Sep 7 23:01:43 >> pneumo-martyr NetworkManager: <info> (wlan0): preparing device. Sep > 7 >> 23:01:43 pneumo-martyr NetworkManager: <info> (wlan0): deactivating >> device (reason: 2). Sep 7 23:01:43 pneumo-martyr NetworkManager: > <info> >> (wlan0): supplicant interface state: starting -> ready Sep 7 23:01:43 >> pneumo-martyr NetworkManager: <info> (wlan0): device state change: 2 > -> 3 >> (reason 42) >> >> That's about as far as I have been able to get tonight. > > Just in case, can you please check that rfkill lists both soft and hard locks > are *not* on? I have checked rfkill quite a bit. For a while, it was an issue whenever I restarted the wlan0 - I'd have to stop wlan0, rfkill unblock all, then start wlan0 again to get a connection. Very annoying. Using KNetworkManager I have found it on occasion being blocked, but mostly unblocked. > Also, what is your wireless NIC? It may be worth checking that you are still > using the correct driver for your wireless chipset? > http://linuxwireless.org/en/users/Drivers/b43 > and that you are using the latest firmware? > http://linuxwireless.org/en/users/Drivers/b43#Device_firmware_installation Sadly, it's a Dell TrueMobile 1300, which used the BroadCom 4306/Rev2 chipset. There's only one version of the firmware usable for it, and the b43-legacy driver is the only one that supports it. I am still trying to find a good replacement. Since I want a 802.11n capable replacement, finding a new mini-PCI card is hard. (Intel only has mini-PCIe.) Finding a decently supported PCMCIA/PC Card card (Type 1 or 2) is also hard - most that are supported are only the 2.4GHZ range, and I'd like to use the 5GHZ range for 802.11n with the 2.4 GHZ for 802.11g. Simply put, I'd like to take full advantage of 802.11n and finding something capable and supported is proving difficult. The linuxwireless.org website is not very helpful in that respect either. So, yes - I'm full open to replacement suggestions. I'd much rather have a fully supported Atheros-based card, and I'm getting tired of looking too. Ben
