It has been awhile since I cared what the kernel has in it. But as I thought "lsmod" will list everything in the kernel and it still does. I did a lsmod and found the modules for WiFi were not in the kernel. The kernel I am using on the laptop is supposed to have all the WiFi modules.
So I did a modprobe ipw2100 and it seemed to work. I looked with lsmod and sure enough the it and ieee81102 was also in the kernel. It didn't start WiFi working yet. I looked at /var/log/messages and it showed both modules loading properly but for some reason NetworkManager was not interested in finding WiFi. I need to do something else.
Be aware that if you modprobe a module into the kernel it goes away with a reboot.
Karl
aKarl Larsen wrote:
It has been awhile since I cared what the kernel has in it. But as I
thought "lsmod" will list everything in the kernel and it still does. I did a lsmod and found the modules for WiFi were not in the kernel. The kernel I am using on the laptop is supposed to have all the WiFi modules.
lsmod lists the modules that are loaded. In the case of distribution kernels this is a tiny proportion of the modules in (or with) the kernel.
So I did a modprobe ipw2100 and it seemed to work. I looked with
lsmod and sure enough the it and ieee81102 was also in the kernel. It didn't start WiFi working yet. I looked at /var/log/messages and it showed both modules loading properly but for some reason NetworkManager was not interested in finding WiFi. I need to do something else.
This is a minority opinion, but I am not a great fan of NM (NetworkManager).
If WiFi is working then NM isn't really necessary; and if it is not working then NM just adds another layer of confusion to an already confused situation.
Personally, I would stop NM, look at the entries in /etc/sysconfig/network-scripts/ifcfg-* and make sure they are reasonable, and then say "service network restart".
Be aware that if you modprobe a module into the kernel it goes away
with a reboot.
You can probably make an entry in modprobe.conf to make sure it is loaded.
Timothy Murphy wrote:
aKarl Larsen wrote:
It has been awhile since I cared what the kernel has in it. But as I
thought "lsmod" will list everything in the kernel and it still does. I did a lsmod and found the modules for WiFi were not in the kernel. The kernel I am using on the laptop is supposed to have all the WiFi modules.
lsmod lists the modules that are loaded. In the case of distribution kernels this is a tiny proportion of the modules in (or with) the kernel.
So I did a modprobe ipw2100 and it seemed to work. I looked with
lsmod and sure enough the it and ieee81102 was also in the kernel. It didn't start WiFi working yet. I looked at /var/log/messages and it showed both modules loading properly but for some reason NetworkManager was not interested in finding WiFi. I need to do something else.
This is a minority opinion, but I am not a great fan of NM (NetworkManager).
I am becoming less of a NM fan. I had it running on this computer and from /var/log/messages I learned it turned off eth0. What I saw was the Internet stopped working :-(
If WiFi is working then NM isn't really necessary; and if it is not working then NM just adds another layer of confusion to an already confused situation.
It is sure not a clear system. And I will try doing this without NM.
Personally, I would stop NM, look at the entries in /etc/sysconfig/network-scripts/ifcfg-* and make sure they are reasonable, and then say "service network restart".
I will try that. The kernel 3232 has a lot of different modules and I expect I need to find the right one for my WiFi hardware.
Be aware that if you modprobe a module into the kernel it goes away
with a reboot.
You can probably make an entry in modprobe.conf to make sure it is loaded.
Maybe after I figure out which module works.
Karl