PDA

View Full Version : Missing Firmware for wireless usb adaptor



ought-6
2013-04-26, 04:57
I have an old Linksys WUSB54G adaptor that I am trying to connect with. I ran the code dsmeg | tail and it output the following:

usb 1-2 Loading firmware file isl3886usb
usbcore registered new interface driver p54usb
usb1-2 firmware agent aborted loading isl3886usb (not found?)
usb1-2 failed to initialize device (-2)

How do I load the firmware for this?

Any help is appreciated.

Mistwraith
2013-04-26, 09:05
I have an old Linksys WUSB54G adaptor that I am trying to connect with. I ran the code dsmeg | tail and it output the following:

usb 1-2 Loading firmware file isl3886usb
usbcore registered new interface driver p54usb
usb1-2 firmware agent aborted loading isl3886usb (not found?)
usb1-2 failed to initialize device (-2)

How do I load the firmware for this?

Any help is appreciated.

Is that adapter compatible with Linux is the first question you need to ask yourself. I am not sure Debian Wheezy 7.0 native drivers are loaded for it.

You need to locate the exact drivers based upon your exact model, there's a useful tool for this called...ndiswrapper .. http://sourceforge.net/apps/mediawiki/ndiswrapper/index.php?title=Main_Page That's the wiki and you can start troubleshooting. The info. is there you will need to research it. I searched under "USB Device Database".

http://i.imgur.com/DshD3U5.jpg

Article here on a guy trying to install that same adapter to his lappy on the Ubuntu system, http://www.linuxcompatible.org/Installing_Linksys_WUSB54G_t32624.html You can use that a base for research see what his results were. Loading drivers on Linux has come along way but can still be a headache.

The rest is a learning experience.

maverik35
2013-04-26, 16:31
Your chipset is isl3886 and it uses the p54 driver which is trying to load for the isl3886 USB.

In the post I do not see any info about not supported or not finding driver..The info claerly states that driver was found but could not be loaded. Also stated the chipset isl3886.

It just aborted the load of module, so then the device could not be initialized in consecuence.

Try to load it manually: modprobe p54usb

ought-6
2013-04-29, 05:27
Do I need to navigate to a certain path or can I just open a fresh terminal and type modprobe p54usb?

root-boy
2013-04-29, 10:55
i think you need to load the rt2800usb driver. You don't need to navigate to any path, just run modprobe "the_driver_to_load" in a terminal

maverik35
2013-04-29, 18:10
Do I need to navigate to a certain path or can I just open a fresh terminal and type modprobe p54usb?

Yes...

Please refer here to clear out some issues: http://wikidevi.com/wiki/Linksys_WUSB54G_v2
Version 1 and 2 have the Intersil Chipset
Version 4 has the Ralink chipset.

I quote:
usb 1-2 Loading firmware file isl3886usb
usbcore registered new interface driver p54usb
usb1-2 firmware agent aborted loading isl3886usb (not found?)

Your chipset is Intersil, so driver to Intersil is p54b in both version 1 and 2. For the Ralink chipset is the rt2500usb. All is in the web page referred above.

Luck.

ought-6
2013-04-30, 02:55
Thanks for the replies guys. I have done modprobe p54usb but it still does not activate the wireless. I will continue researching or consider buying an up to date usb adapter.

m86
2013-05-01, 23:44
Er.. you will need the isl3886usb firmware for the device to work. The log output indicates it is bailing out after failing to load it.

The firmware is linked to on the p54 page on the Linux Wireless wiki (http://wireless.kernel.org/en/users/Drivers/p54). It can be downloaded here (http://daemonizer.de/prism54/prism54-fw/fw-usb/2.13.1.0.lm86.arm) for non-ancient kernels (see the wiki page for kernels >= 2.6.28).

Download the FW file, rename it to isl3886usb, and then move it to wherever the Kali distro keeps the firmware (presumably /lib/firmware).. or wget the file with the output to /lib/firmware/isl3886usb. It should then work to some extent.

ought-6
2013-05-02, 01:13
I installed WICD and magically the WLAN0 activated itself. Not sure what happened, but it works.