Results 31 to 40 of 44
Actually, with your hardware spec, SLAX was a good choice. I haven't used it in a while, but I recall that wireless support was poor because it uses an older ...
- 07-04-2009 #31
Actually, with your hardware spec, SLAX was a good choice. I haven't used it in a while, but I recall that wireless support was poor because it uses an older style 2.4 kernel. I did get my Broadcom wireless to work with NDISwrapper, though.
There is a thread on the best distro to use on older equipment. As you can guess, no one agrees. But you can get some ideas from it.
http://www.linuxforums.org/forum/cof...re-2009-a.htmlPaul
Please do not send Private Messages to me with requests for help. I will not reply.
- 07-05-2009 #32Just Joined!
- Join Date
- Jul 2009
- Location
- Tyler, Tx
- Posts
- 21
- 07-05-2009 #33
You still need to install the Broadcom firmware before it will work.
When it asks: "Download and install firmware?", answer "Yes" (press enter).Code:sudo apt-get install b43-fwcutter
You will need a wired connection to do this
Edit: OOPS! Sorry, you don't have a Broadcom wireless. I have one.
Paul
Please do not send Private Messages to me with requests for help. I will not reply.
- 07-05-2009 #34
You do need a copy of your firmware installed. On my Ubuntu 9.04 install, there is a copy of isl3887usb_bare in the /lib/firmware folder. Try using that one instaed of the one you made.
Maybe this is a problem with the connection, and not the wireless. Did you check dmesg again for error messages, either firmware or connection errors?Paul
Please do not send Private Messages to me with requests for help. I will not reply.
- 07-05-2009 #35Just Joined!
- Join Date
- Jul 2009
- Location
- Tyler, Tx
- Posts
- 21
Yeah its in dmesg, I took off the security settings on my wifi, and im trying to connect it. It gets connected for like 5 seconds and then it just goes off
- 07-05-2009 #36
Well, there is one other thing to try. I see that there is the option to extract the firmware from a known working Windows driver. Do you have the installer file for a Windows driver?
Go to this web site and follow the instructions for the fwextract source.
The Prism54 Project
Extract it and then compile it with a simple make command. Judging from the instructions, I think that for "basename" you use the name of the firmware, isl3887usb_bare.Paul
Please do not send Private Messages to me with requests for help. I will not reply.
- 07-05-2009 #37Just Joined!
- Join Date
- Jul 2009
- Location
- Tyler, Tx
- Posts
- 21
- 07-05-2009 #38
Read the web site for the p54 project:
The Prism54 Project
Under the section for USB devices with isl38xx chipsets, it says to read this page:
The Prism54 Project
Not only does it say the driver is named islsm, but if you look up the Device ID of yours (0cde:008) it says to use the GW3887 firmware. Take into consideration that this site is old and no longer maintained, but it's all we have to go on.
Since the system is looking for a certain firmware, it will ignore any firmware with a different name. I guess that you would have to rename the different firmware.Last edited by waterhead; 07-05-2009 at 09:36 PM.
Paul
Please do not send Private Messages to me with requests for help. I will not reply.
- 07-05-2009 #39
- 07-05-2009 #40
Does the error message still say that the firmware is not found, or does it now load the firmware but not work.
The more I look, the more firmware versions that I find. You may want to try every firmware that may have a chance of working. Here are some more that you can try:
The prism54 firmwares
I found a debian how-o that says to use s different firmware version. remember, the firmwarte version s dependent on your kernel version.
prism54 - Debian WikiPaul
Please do not send Private Messages to me with requests for help. I will not reply.


Reply With Quote

