1 |
On 10/02/2014 09:39 PM, J. Roeleveld wrote: |
2 |
> |
3 |
> On Thursday, October 02, 2014 10:24:51 PM Alec Ten Harmsel wrote: |
4 |
>> On 10/02/2014 10:05 PM, walt wrote: |
5 |
>>> I did some googling and enabled the "appropriate" kernel drivers, then |
6 |
>>> rebooted and now the output from ifconfig includes this interface: |
7 |
>>> |
8 |
>>> wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 |
9 |
>>> |
10 |
>>> ether b8:a3:86:99:a8:d8 txqueuelen 1000 (Ethernet) |
11 |
>>> RX packets 0 bytes 0 (0.0 B) |
12 |
>>> RX errors 0 dropped 0 overruns 0 frame 0 |
13 |
>>> TX packets 0 bytes 0 (0.0 B) |
14 |
>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
15 |
>>> |
16 |
>>> My yes-or-no question: does the appearance of "wlan0" imply that |
17 |
>>> my new kernel drivers are the right ones for this particular D-Link |
18 |
>>> WiFi adapter? |
19 |
>> |
20 |
>> It's certainly a great sign, but it may or may not be enough. I'm by no |
21 |
>> means an expert, but I believe I have to install some extra firmware |
22 |
>> (b43-firmware) to use on my laptop as it's not in the kernel (unless I'm |
23 |
>> clueless with kernel config). Without b43-firmware, the interface shows |
24 |
>> up and is recognized, but can't be used iirc. |
25 |
> |
26 |
> In my experience, when it shows in "ifconfig", it is loaded. |
27 |
> You might want to check the "dmesg" output to see if it is missing firmware |
28 |
> somewhere. |
29 |
> Did you try "dhcpcd wlan0" to see if it gets an IP-address? |
30 |
|
31 |
That doesn't work (yet). An error message said that /etc/wpa_supplicant.conf |
32 |
was missing, so I copied this example from a man page: |
33 |
|
34 |
#cat /etc/wpa_supplicant.conf |
35 |
ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel |
36 |
|
37 |
network={ |
38 |
ssid="myhomewireless" |
39 |
scan_ssid=1 |
40 |
key_mgmt=WPA-PSK |
41 |
psk="mypsk" |
42 |
} |
43 |
|
44 |
#dhcpcd wlan0 |
45 |
dhcpcd[1415]: version 6.4.7 starting |
46 |
dhcpcd[1415]: wlan0: adding address fe80::f45c:642e:a392:f47c |
47 |
dhcpcd[1415]: if_addaddress6: Permission denied |
48 |
dhcpcd[1423]: wlan0: starting wpa_supplicant |
49 |
dhcpcd[1415]: wlan0: waiting for carrier |
50 |
dhcpcd[1415]: timed out |
51 |
dhcpcd[1415]: allowing 8 seconds for IPv4LL timeout |
52 |
dhcpcd[1415]: timed out |
53 |
dhcpcd[1415]: exited |
54 |
|
55 |
NetworkManager gets wlan0 working normally, but the problem is the |
56 |
network doesn't come up until I log in and use the NetworkManager |
57 |
panel applet to enter the psk manually. Ugh. |
58 |
|
59 |
So, the hardware works but I need to configure the network properly. |
60 |
Anyone have an idea how I can get the connection working automatically |
61 |
during boot? |
62 |
|
63 |
Thanks. |
64 |
|
65 |
BTW, this is ifconfig after NetworkManager brings wlan0 up: |
66 |
|
67 |
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 |
68 |
inet 192.168.1.75 netmask 255.255.255.0 broadcast 192.168.1.255 |
69 |
inet6 fe80::baa3:86ff:fe99:a8d8 prefixlen 64 scopeid 0x20<link> |
70 |
inet6 2602:306:c4d4:cf40:baa3:86ff:fe99:a8d8 prefixlen 128 scopeid 0x0<global> |
71 |
ether b8:a3:86:99:a8:d8 txqueuelen 1000 (Ethernet) |
72 |
RX packets 317 bytes 18320 (17.8 KiB) |
73 |
RX errors 0 dropped 0 overruns 0 frame 0 |
74 |
TX packets 82 bytes 38743 (37.8 KiB) |
75 |
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |