Well, that looks OK to me: you do have the microcode file iwlwifi-5000-5.ucode (plus iwlwifi-5000-2.ucode and iwlwifi-5000-1.ucode) in /lib/firmware/
Regarding your first post:
harmon wrote:- Code: Select all
sabayon harmon # lsmod | grep iwl
iwlagn 180153 0
mac80211 165909 1 iwlagn
cfg80211 119001 2 iwlagn,mac80211
On PCLinuxOS WiFi works fine:
- Code: Select all
[root@localhost ~]# lsmod | grep iwl
iwlagn 170878 0
iwlcore 52621 1 iwlagn
mac80211 189461 2 iwlagn,iwlcore
cfg80211 126787 3 iwlagn,iwlcore,mac80211
I'll bet your PCLinuxPOS installation is using an earlier kernel than 2.6.39. You can check on both installations by using the
uname -a command. My installation using the 2.6.37 kernel has the following Intel WiFi modules loaded:
- Code: Select all
$ lsmod | grep iwl
iwlagn 160149 0
iwlcore 47364 1 iwlagn
mac80211 167330 2 iwlagn,iwlcore
cfg80211 119308 3 iwlagn,iwlcore,mac80211
In the 2.6.39 kernel the iwlcore module is for the legacy 3945/4965 devices (see
[PATCH 4/4] iwlwifi: split the drivers for agn and legacy devices 3945/4965), whereas the iwlagn module covers the Intel WiFi devices listed (as I also mentioned in an earlier post).
However, if you look back at one of my earlier posts, you'll notice that the Sabayon 2.6.39-r7 kernel config has:
- Code: Select all
meshedgedx src # cat linux-2.6.39-sabayon/.config | grep IWL
CONFIG_IWLAGN=m
# CONFIG_IWLWIFI_DEBUG is not set
CONFIG_IWL_P2P=y
CONFIG_IWLWIFI_LEGACY=m
# CONFIG_IWLWIFI_LEGACY_DEBUG is not set
CONFIG_IWL4965=m
CONFIG_IWL3945=m
meshedgedx src #
so I would have expected iwlcore to show up in the output from lsmod because the config has CONFIG_IWLWIFI_LEGACY=m, CONFIG_IWL4965=m and CONFIG_IWL3965=m. So I'm not sure what is happening. Although I can't see why it would help in your case, I suppose you could try loading the iwlcore module just to see what happens:
- Code: Select all
# modprobe iwlcore