Issue: Dapper with 2.6.15-xx kernel and Linksys Wireless USB Adapter WUSB54G version 1 (do a lsusb and you should see a device ID 1915:2234). Upon boot, the adapter would be listed as eth1 (or above) and would not accept commands properly.
Under a 386 kernel, waiting to plug in the device until after booting would let it run properly as wlan0 and accept commands and connect to the internet.
Fix: Edited /etc/modprobe.d/blacklist and added the following line to end. Saved and rebooted.
blacklist islsm_usb.
After reboot, all wlan0 commands in /etc/network/interfaces (essid, key, etc) worked fine.
Cause: Dapper kept trying to use the prism_54 islsm driver which did not work properly and would interfere with ndiswrapper when it was loaded at boot.
Continuing issues: The 686 based kernels (tested 2.6.15-23 and -26 tested) *will* cause a system lock (kernel panic?) after a short amount of use (time varies from a few sec to several minutes). This is with and without Hyperthreading on.
Anyone have any ideas on why it works flawlessly with a 386 kernel but panics with a 686 one?
Beemer
Under a 386 kernel, waiting to plug in the device until after booting would let it run properly as wlan0 and accept commands and connect to the internet.
Fix: Edited /etc/modprobe.d/blacklist and added the following line to end. Saved and rebooted.
blacklist islsm_usb.
After reboot, all wlan0 commands in /etc/network/interfaces (essid, key, etc) worked fine.
Cause: Dapper kept trying to use the prism_54 islsm driver which did not work properly and would interfere with ndiswrapper when it was loaded at boot.
Continuing issues: The 686 based kernels (tested 2.6.15-23 and -26 tested) *will* cause a system lock (kernel panic?) after a short amount of use (time varies from a few sec to several minutes). This is with and without Hyperthreading on.
Anyone have any ideas on why it works flawlessly with a 386 kernel but panics with a 686 one?
Beemer