tempestuous

Group: Members
Posts: 259
Joined: Aug. 2004 |
 |
Posted: Sep. 30 2005,00:42 |
 |
Damn! I'm determined to fix this. Perhaps I will wait until I get an Intel PRO/Wireless adaptor to test things myself. But if you want to experiment further yourself, I have 3 suggestions -
1. The order of the modules may be important, so try this (from the ipw2200 README) -
sudo su modprobe ieee80211 modprobe firmware_class insmod ipw2200
2. One of the sub-modules being loaded by the ipw2200 module may be causing the problem - the main suspect would be ieee80211_crypt_tkip.o. So you could try deleting each of these sub-modules, before "depmod"
3. Maybe the very latest firmware.agent would help. It's part of the hotplug source .gz from http://sourceforge.net/project/showfiles.php?group_id=17679
|