1 |
On Monday, 29 August 2022 22:23:00 BST Walter Dnes wrote: |
2 |
> 1) the output of "dmesg | grep iwlwifi" is... |
3 |
> |
4 |
> [ 0.640780] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have |
5 |
> ASPM control [ 0.641112] Loading firmware: iwlwifi-5000-5.ucode |
6 |
> [ 0.641332] iwlwifi 0000:03:00.0: loaded firmware version 8.83.5.1 build |
7 |
> 33692 5000-5.ucode op_mode iwldvm [ 0.641360] iwlwifi 0000:03:00.0: |
8 |
> CONFIG_IWLWIFI_DEBUG disabled [ 0.641364] iwlwifi 0000:03:00.0: |
9 |
> CONFIG_IWLWIFI_DEBUGFS disabled [ 0.641367] iwlwifi 0000:03:00.0: |
10 |
> CONFIG_IWLWIFI_DEVICE_TRACING disabled [ 0.641370] iwlwifi 0000:03:00.0: |
11 |
> Detected Intel(R) WiFi Link 5100 AGN, REV=0x54 [ 17.311014] iwlwifi |
12 |
> 0000:03:00.0: Radio type=0x1-0x2-0x0 |
13 |
> [ 17.424989] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 |
14 |
> |
15 |
> Nice to see that it detects the 5100 AGN just like lspci. As the old |
16 |
> saying goes, "use it or lose it"; I used to be able to run wifi on this |
17 |
> machine manually (command line) in the past, but now I've completely |
18 |
> forgotten how. I've emerged "iw" and "wpa_supplicant". "iw dev" shows |
19 |
> |
20 |
> phy#0 |
21 |
> Interface wlan0 |
22 |
> ifindex 3 |
23 |
> wdev 0x1 |
24 |
> addr 00:26:c6:4a:b4:92 |
25 |
> type managed |
26 |
> txpower 15.00 dBm |
27 |
> |
28 |
> Questions... |
29 |
> 1) what do I do to scan and get a list of available networks? |
30 |
|
31 |
If you have emerged wpa_supplicant with USE="qt5" you will have a GUI to |
32 |
launch its client and click on Scan to find and select a desired AP. |
33 |
|
34 |
If not, you can run wpa_cli in a terminal. Something like 'wpa_cli scan' and |
35 |
'wpa_cli scan_results' should show you what's available. If you run just |
36 |
'wpa_cli' it will launch an interactive shell from which you can run: |
37 |
|
38 |
> scan |
39 |
> scan_results |
40 |
|
41 |
'wpa_cli --help' for more subcommands and options. |
42 |
|
43 |
|
44 |
> 2) how do I connect to one of the listed networks (assuming either |
45 |
> it's public, or I have the password) ? |
46 |
|
47 |
With wpa_supplicant's GUI, or with wpa_cli, but the latter is more tedious. |
48 |
|
49 |
Run wpa_cli to get an interactive shell. Then, |
50 |
|
51 |
> scan |
52 |
> scan_results |
53 |
|
54 |
> add_network |
55 |
0 (if there is no other network yet configured) |
56 |
> set_network 0 ssid "My_blah_AP" <== From the results |
57 |
> set_network 0 psk "My_secret_passphrase" |
58 |
> enable_network 0 |
59 |
0K |
60 |
|
61 |
If you managed to authenticate and get an IP address you may want to save your |
62 |
settings - assuming you have enabled 'update_config=1' in your |
63 |
wpa_supplicant.conf: |
64 |
|
65 |
> save config |
66 |
OK |
67 |
|
68 |
For permanent associations you can add BSSID and authentication credentials |
69 |
into /etc/wpa_supplicant/wpa_supplicant.conf. Have a look at '/usr/share/doc/ |
70 |
wpa_supplicant-*/wpa_supplicant.conf.bz2' for examples. |
71 |
|
72 |
|
73 |
> 3) minor detail... The Google hits I've found all show both DVM and |
74 |
> MVM support enabled. Given that dmesg output shows "op_mode iwldvm", |
75 |
> can I safely get rid of MVM support ? |
76 |
|
77 |
I don't know what works with your wireless adaptor, but I tend to experiment |
78 |
initially by building such options as modules and see what is loaded or not |
79 |
and any warnings in dmesg. |