Hi All, Hopefully you guys can be of assistance.
I have a Linksys wireless USB adater which I downloaded the drivers for here http://www.linksys.com/download/driver.asp?dlid=51&osid=7 I have read the readme file which comes with it, which brings me to my question.. This is a fresh install with generic/default options.. I am curious to know if I need to make a kernel to do this install or if I can just un tar the file and follow the instructions in the USB section which are inserted next.. Thanks for the help here. A new user to redhat again... One day I will make the switch completely. Mike TAKEN FROM README FILE. ------------------------------ FOR USB USERS: A) Make sure your kernel USB support is running B) Plug in the Prism2.x USB device C) Run 'modprobe prism2_usb prism2_doreset=1' to load the driver into memory. D) Run 'wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable' to initialize the driver+MAC functions. E) Run 'wlanctl-ng wlan0 lnxreq_autojoin ssid=<your ssid> authtype=opensystem' to enable the MAC in Infrastructure Station mode. F) Run 'ifconfig wlan0 <your IP address>' NOTE: USB devices can use the /etc/init.d/wlan script for initialization. Integration with usbmgr/hotplug is still a TODO item. IMPORTANT: Due to an issue with the current firmware in Prism USB devices, the driver must usually do a port reset (which is normally handled by usbcore). Some usb low-level drivers don't like this, they see the reset as a new device connect (of something that's _already_ in the connected state). When that happens things go very awry, possibly crashing and/or hanging the machine. Some low-level drivers handle it just fine. Since it appears to be a combination of the underlying USB host hardware _and_ the usb low-level driver _and_ the linux usb version, I haven't been able to put together a description of precisely which hardware/software will work. Some of my hardware here in the lab works, some hardware (with exactly the same software) does not. You will have to experiment on your own. Unfortunately, there's nothing we can do about it until new firmware becomes available. The good news is that the firmware developers are aware of the problem, they have a fix, and the new firmware is coming, we just don't know precisely when it will be available. It all depends on how quickly they can get it through their QA process. When it does become available, install it in your device using the Windows firmware update utility, remove the "prism2_doreset" on the modprobe command line above and everything will work just peachy. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
