Hi Jerry. Another small reporting and one or two things that I'm not clear.
In: 3.4 Network
you write:
Internet connections are handled by Network Manager; click the applet in the Notification Area to see status, connect and explore options.
Right-click the applet > Edit Connections to open up a Settings box with five tabs.
Following update, the Settings box no longer contains 5 tabs. My Network Manager applet (MX linux 15; network-manager version 0.9.10.0-7) contains 3 main types: Hardware, Virtual, VPN.
Perhaps the last sentence could be corrected with something like this:
Right-click the applet > Edit Connections to open up a Settings box with some type of connection; the main ones are: (or those which be needed a normal user are: ...or something similar)
In 3.4.2 Wireless access - Basic Wireless Steps
you write:
Code: Select all
2 The found network does not function after the completion of Step 1.
Find out basic information by opening a terminal and entering one at a time:
lspci
lsusb
Become root in that open terminal and enter:
iwconfig -a
The output from the first commands (example below) will give you the exact name, model and version (if any) of your wireless chipset, as well as the associated driver and the mac address; from the second, the name of the access point (AP) you are linked to and other connection information.
Network
Card-2: Intel Ultimate N WiFi Link 5300 driver: iwlwifi
IF: wlan0 state: up mac: 00:21:6a:81:8c:5a
Use the information you have gathered in one of the following ways:
Do a web search using that information. Some examples using the above lspci output.
1) linux Intel Ultimate N WiFi Link 5300 (rev 03)
2) debian stable 00:21:6a:81:8c:5a
Consult the Linux Wireless site below to find out which driver your chipset needs, what conflicts might exist, and whether it needs firmware installed separately.
Post your information on the Forum and ask for help.
The first two commands: lspci and lsusb, presented like this, in my opinion are not comfortable.
They are more practical so:
$ lsusb | grep -i net
lspci | grep -i net
Ok, for a newbby it is more reassuring give the terminal a single word command (there is also less risk of errors writing command) but then the output that comes out is very uncomfortable and difficult to understand.
The third command:
iwconfig -a
returns me this output :
-a No such device
instead
iwconfig
works.
You write:
The output from the first commands (example below) will give you the exact name, model and version (if any) of your wireless chipset, as well as the associated driver and the mac address; from the second, the name of the access point (AP) you are linked to and other connection information.
Network
Card-2: Intel Ultimate N WiFi Link 5300 driver: iwlwifi
IF: wlan0 state: up mac: 00:21:6a:81:8c:5a
This type of output is not returned by the first two commands, but by:
inxi -n
Instead this is the type of output of
lspci | grep -i net
03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
ok, it is not much different but it isn't correct to write that the output will give you
“as well as the associated driver and the mac address” (in
inxi -n yes, in
lspci no)
When you write:
the first commands (example below) will give you the exact name, model and version (if any) of your wireless chipset
are you sure it is correct chipset rather than wireless card? I don't know, I'm no expert, it's just a question, it is probably correct as you have written, however the information that I have are that the exact name, model and version of wireless chipset, in my case they are defined as :
[168c:0034]
I can graphically see this through MX Broadcom Manager where, after the hardware scan, shows me this:
03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01)
I can have the same output, via cli, typing this :
lspci | grep -i net
and then, using the output I got, I write this command:
lspci -n | grep xx:xx.x
example:
lspci | grep -i net
03:00.0 Network controller: Qualcomm Ather.................
lspci -n | grep 03:00.0
03:00.0 0280: 168c:0034 (rev 01)
then, to see which driver I need, I do a web search using something like this:
Linux 0x168c 0x0034
or debian stable 0x168c 0x0034
You write:
Do a web search using that information. Some examples using the above lspci output.
2) debian stable 00:21:6a:81:8c:5a
Why should I do a web search using the access point mac?
Did you mean that you could try to do ping and traceroute to check if there is a problem in the intermediate routers a connection must pass through to get to its destination?
I do not know if something is wrong in this sub-paragraph or if I didn't understand something. Or may be that I didn't understand something and something is wrong. I hope not to be too annoying with my small details, in any case I hope that my questions and my doubts are useful to improve the manual.