| 1 |
----- Original Message ----- |
| 2 |
|
| 3 |
> From: Mick <michaelkintzios@×××××.com> |
| 4 |
> On Thursday 08 Sep 2011 04:52:44 BRM wrote: |
| 5 |
>> ----- Original Message ----- |
| 6 |
>> |
| 7 |
>> > From: Mick <michaelkintzios@×××××.com> |
| 8 |
> |
| 9 |
>> > Hmm ... what is the error/warning that comes up? |
| 10 |
>> |
| 11 |
>> pneumo-martyr wpa_supplicant # /etc/init.d/net.wlan0 start |
| 12 |
>> * Bringing up interface wlan0 |
| 13 |
>> * Starting wpa_supplicant on wlan0 ... |
| 14 |
>> Line 17: WPA-PSK accepted for key management, but no PSK configured. |
| 15 |
>> Line 17: failed to parse network block. |
| 16 |
>> Failed to read or parse configuration |
| 17 |
>> '/etc/wpa_supplicant/wpa_supplicant.conf'. * start-stop-daemon: |
| 18 |
> failed |
| 19 |
>> to start |
| 20 |
>> `/usr/sbin/wpa_supplicant' |
| 21 |
> |
| 22 |
>> [ !! ] * ERROR: net.wlan0 failed to start |
| 23 |
> |
| 24 |
> Ah! This shows that your /etc/wpa_supplicant/wpa_supplicant.conf has |
| 25 |
> something wrong with it and it can't be parsed. Please check the file's |
| 26 |
> |
| 27 |
> access rights and its contents. This is what it looks like here: |
| 28 |
> |
| 29 |
> $ ls -la /etc/wpa_supplicant/wpa_supplicant.conf |
| 30 |
> -rw-r--r-- 1 root root 33388 Jun 14 15:02 |
| 31 |
> /etc/wpa_supplicant/wpa_supplicant.conf |
| 32 |
|
| 33 |
That error only comes up when those two lines are commented out. If I return them, then all is fine. |
| 34 |
|
| 35 |
>> > # iwlist wlan0 scanning |
| 36 |
>> |
| 37 |
>> Simply returns: |
| 38 |
>> |
| 39 |
>> wlan0 No scan results |
| 40 |
> |
| 41 |
> Your device has not been initiated, therefore it would not be able to scan |
| 42 |
> until then. |
| 43 |
|
| 44 |
True. |
| 45 |
|
| 46 |
>> It also returns "0". I have wlan0 logs directed to |
| 47 |
> /var/log/net/wireless, |
| 48 |
>> here's the output from the last attempt: |
| 49 |
>> |
| 50 |
>> Sep 7 23:01:43 pneumo-martyr NetworkManager: <info> (wlan0): driver |
| 51 |
>> supports SSID scans (scan_capa 0x01). Sep 7 23:01:43 pneumo-martyr |
| 52 |
>> NetworkManager: <info> (wlan0): new 802.11 WiFi device (driver: |
| 53 |
>> 'b43legacy') Sep 7 23:01:43 pneumo-martyr NetworkManager: |
| 54 |
> <info> |
| 55 |
>> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1 Sep 7 |
| 56 |
>> 23:01:43 pneumo-martyr NetworkManager: <info> (wlan0): now managed |
| 57 |
> Sep 7 |
| 58 |
>> 23:01:43 pneumo-martyr NetworkManager: <info> (wlan0): device state |
| 59 |
>> change: 1 -> 2 (reason 2) Sep 7 23:01:43 pneumo-martyr NetworkManager: |
| 60 |
>> <info> (wlan0): bringing up device. Sep 7 23:01:43 pneumo-martyr |
| 61 |
> kernel: |
| 62 |
>> ADDRCONF(NETDEV_UP): wlan0: link is not ready Sep 7 23:01:43 |
| 63 |
>> pneumo-martyr NetworkManager: <info> (wlan0): preparing device. Sep |
| 64 |
> 7 |
| 65 |
>> 23:01:43 pneumo-martyr NetworkManager: <info> (wlan0): deactivating |
| 66 |
>> device (reason: 2). Sep 7 23:01:43 pneumo-martyr NetworkManager: |
| 67 |
> <info> |
| 68 |
>> (wlan0): supplicant interface state: starting -> ready Sep 7 23:01:43 |
| 69 |
>> pneumo-martyr NetworkManager: <info> (wlan0): device state change: 2 |
| 70 |
> -> 3 |
| 71 |
>> (reason 42) |
| 72 |
>> |
| 73 |
>> That's about as far as I have been able to get tonight. |
| 74 |
> |
| 75 |
> Just in case, can you please check that rfkill lists both soft and hard locks |
| 76 |
> are *not* on? |
| 77 |
|
| 78 |
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. |
| 79 |
Using KNetworkManager I have found it on occasion being blocked, but mostly unblocked. |
| 80 |
|
| 81 |
> Also, what is your wireless NIC? It may be worth checking that you are still |
| 82 |
> using the correct driver for your wireless chipset? |
| 83 |
> http://linuxwireless.org/en/users/Drivers/b43 |
| 84 |
> and that you are using the latest firmware? |
| 85 |
> http://linuxwireless.org/en/users/Drivers/b43#Device_firmware_installation |
| 86 |
|
| 87 |
Sadly, it's a Dell TrueMobile 1300, which used the BroadCom 4306/Rev2 chipset. |
| 88 |
There's only one version of the firmware usable for it, and the b43-legacy driver is the only one that supports it. |
| 89 |
|
| 90 |
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.) |
| 91 |
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. |
| 92 |
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. |
| 93 |
|
| 94 |
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. |
| 95 |
|
| 96 |
Ben |
Archives