View Full Version : [ubuntu] WG511 wireless card not available as network device
bratman91
February 22nd, 2011, 12:31 PM
I have just installed Ubuntu 10.10 on a Dell Laptop. It has a Netgear WG511 (made in China) PCI wireless card but I cannot see any connections other than the wired one. Entering in lspci in the terminal mode and removing/replacing the WG511 shows (I think) that something is being detected in the PCI slot "Network Controller: Intersil Corporation ISL 3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] rev 01". Is this the WG511 and, if so, how do I get it to be detected as a network device?
chili555
February 22nd, 2011, 01:46 PM
"Network Controller: Intersil Corporation ISL 3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] rev 01". Is this the WG511 and, if so, how do I get it to be detected as a network device?Yes, it is. Usually, these devices simply need firmware. When you have a wired internet connection, please do:
sudo apt-get install linux-firmware-nonfreeAfter it installs, detach the wired ethernet and reboot. You should have working wireless. Post back if you need further guidance.
bratman91
February 22nd, 2011, 02:40 PM
Yes, it is. Usually, these devices simply need firmware. When you have a wired internet connection, please do:
sudo apt-get install linux-firmware-nonfreeAfter it installs, detach the wired ethernet and reboot. You should have working wireless. Post back if you need further guidance.
Brilliant - works a treat. Very many thanks
jtraceypgh
March 10th, 2011, 09:36 PM
I found this thread several weeks ago when working with Ubuntu 10.10 on my wife's Dell and it worked great to get the Netgear card working. Unfortunately, it is NOT working for my IBM Thinkpad g40!:confused:
Any suggestions??
Thanks!
chili555
March 10th, 2011, 09:42 PM
Please post:
rfkill list all
dmesg | grep p54
lspci -nnThanks.
jtraceypgh
March 11th, 2011, 05:44 AM
rfkill list all yielded no results
sudo dmesg | grep p54
[ 30.160598] p54pci 0000:03:00.0: enabling device (0000 -> 0002)
[ 30.160618] p54pci 0000:03:00.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
[ 30.160636] p54pci 0000:03:00.0: setting latency timer to 64
[ 30.219546] phy0: p54 detected a LM86 firmware
[ 30.219552] p54: rx_mtu reduced from 3240 to 2376
[ 31.453022] p54pci 0000:03:00.0: PCI INT A disabled
[ 31.453036] p54pci: probe of 0000:03:00.0 failed with error -110
lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3580] (rev 01)
00:00.1 System peripheral [0880]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3584] (rev 01)
00:00.3 System peripheral [0880]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3585] (rev 01)
00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 01)
00:02.1 Display controller [0380]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 01)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 01)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 81)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge [8086:24cc] (rev 01)
00:1f.1 IDE interface [0101]: Intel Corporation 82801DBM (ICH4-M) IDE Controller [8086:24ca] (rev 01)
00:1f.3 SMBus [0c05]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller [8086:24c3] (rev 01)
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 01)
00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller [8086:24c6] (rev 01)
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5901 100Base-TX [14e4:170d] (rev 01)
02:01.0 CardBus bridge [0607]: Texas Instruments PCI1410 PC card Cardbus Controller [104c:ac50] (rev 02)
03:00.0 Network controller [0280]: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] [1260:3890] (rev 01)
chili555
March 11th, 2011, 02:03 PM
This may offer some guidance: http://ubuntuforums.org/showthread.php?t=1459068
Do you believe you have a Version 1 card? Let's try the fix outlined in the link. Remove the card. Obtain a wired ethernet connection. Now open a terminal and do:
cd /lib/firmware
sudo mv isl3886pci isl3886pci.old
wget http://daemonizer.de/prism54/prism54-fw/fw-softmac/2.12.0.0.arm
sudo mv 2.12.0.0.arm isl3886pciNote any errors and post them here before you proceed.
Detach the cable. Now do:
sudo rmmod -f p54pciReinsert the device. Does it work now? If not, let's see what messages come up:
dmesg | grep p54
jtraceypgh
March 11th, 2011, 03:11 PM
Before I follow the steps you outline - which I probably won't get to until at LEAST later tonight, the card is clearly marked v3.0. Further, it worked fine previously in this laptop (Ubuntu installed inside Win XP) as well as my wife's old Dell, after a firmware update I described above. I'm currently working on an install of Ubuntu on a spare hard drive I swap with my XP drive when I have time to experiment...and it's THERE that I'm having the problem.
I said all that to say, I want to ensure the steps you outline won't cause any complications for a v3.0 card. Of course I'm aware any changes can be reversed, even if it requires reinstall. Just thought I'd ask...
Thanks again for your help!
chili555
March 11th, 2011, 03:15 PM
If you have a Version 3 card and these instructions are for a Version 1 card, then I'd recommend you NOT undertake them. Back to Google...
I should have a better answer a bit later today.
jtraceypgh
March 11th, 2011, 03:53 PM
Thanks again...
chili555
March 11th, 2011, 08:20 PM
the card is clearly marked v3.0. Could you please double-check: http://forum1.netgear.com/showthread.php?t=12727
http://kb.netgear.com/app/products/family/a_id/1270
jtraceypgh
March 16th, 2011, 06:01 PM
Thanks, Chili. That clears that up! I'll insert the Ubuntu drive, give your previous instructions a shot and report back. On vacation for a couple weeks and will have time to "play"... ;)
chili555
March 16th, 2011, 06:11 PM
Thanks, Chili. That clears that up! I'll insert the Ubuntu drive, give your previous instructions a shot and report back. On vacation for a couple weeks and will have time to "play"... ;)Post back if you get stuck or hit a snag. Enjoy the vacation.
jtraceypgh
March 16th, 2011, 06:53 PM
Got this when executed:
wget http://daemonizer.de/prism54/prism54-fw/fw-softmac/2.12.0.0.arm
--2011-03-16 13:49:07-- http://daemonizer.de/prism54/prism54-fw/fw-softmac/2.12.0.0.arm
Resolving daemonizer.de... 178.77.99.65, 2001:4dd0:fc1c::1
Connecting to daemonizer.de|178.77.99.65|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 30076 (29K) [application/octet-stream]
2.12.0.0.arm: Permission denied
Cannot write to `2.12.0.0.arm' (Permission denied).
chili555
March 16th, 2011, 11:11 PM
sudo mv 2.12.0.0.arm isl3886pciWas it at this step where you got 'permission denied?' Are you sure you preceded the command with sudo? You might try:
cd /lib/firmware
sudo su
mv 2.12.0.0.arm isl3886pci
exit
jtraceypgh
March 16th, 2011, 11:22 PM
never got there. Got that error after issuing: wget http://daemonizer.de/prism54/prism54-fw/fw-softmac/2.12.0.0.arm
chili555
March 16th, 2011, 11:24 PM
Ah, I see now. An ordinary user can't write to /lib/firmware. Oops, silly Chili!
sudo su
cd /lib/firmware
mv isl3886pci isl3886pci.old
wget http://daemonizer.de/prism54/prism54-fw/fw-softmac/2.12.0.0.arm
mv 2.12.0.0.arm isl3886pci
exit
jtraceypgh
March 16th, 2011, 11:27 PM
Tried three more times...same outcome
jtraceypgh
March 16th, 2011, 11:29 PM
If I'm following you, you're downloading a file that will then be moved and renamed, correct? Could you just e-mail it to me?
chili555
March 16th, 2011, 11:30 PM
Tried three more times...same outcomeI edited my post; please check.
jtraceypgh
March 16th, 2011, 11:37 PM
so, now what?
jtraceypgh
March 16th, 2011, 11:44 PM
My turn for silly...missed your addition of "su" Ran fine.
Completed the process as instructed and now wireless!!
You da man, Chili! Thanks!!
chili555
March 17th, 2011, 12:04 AM
and now wireless!!Awesome! You have helped some searchers, too.
Are you ready to use Thread Tools at the top and mark the thread Solved?
jtraceypgh
March 17th, 2011, 12:10 AM
Awesome! You have helped some searchers, too.
Are you ready to use Thread Tools at the top and mark the thread Solved?
Would love to, but it's not an option, perhaps because I didn't start it??
Thanks again!
chili555
March 17th, 2011, 12:17 AM
because I didn't start it??Yep, you're right. I'll do the best we can:
SOLVED.
Register208
May 9th, 2011, 07:48 PM
Hi,
I installed the non free package and try the solution explained upper.
But with no luck. The NetGear WG511 (V1) scan the networks and find mine but i can't get a connection.
Dmesg | grep p54
[ 18.313380] p54pci 0000:03:00.0: enabling device (0000 -> 0002)
[ 18.313402] p54pci 0000:03:00.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
[ 18.313421] p54pci 0000:03:00.0: setting latency timer to 64
[ 18.564879] ieee80211 phy0: p54 detected a LM86 firmware
[ 18.564888] p54: rx_mtu reduced from 3240 to 2376
[ 19.638687] Registered led device: p54-phy0::assoc
[ 19.638884] Registered led device: p54-phy0::tx
[ 19.639037] Registered led device: p54-phy0::rx
[ 19.639183] Registered led device: p54-phy0::radio
[ 19.639199] p54pci 0000:03:00.0: is registered as 'p
Dmesg after trying to connect to the ssid
[ 51.474468] wlan0: direct probe to e2:94:fd:52:cb:f4 (try 1/3)
[ 51.672049] wlan0: direct probe to e2:94:fd:52:cb:f4 (try 2/3)
[ 51.872243] wlan0: direct probe to e2:94:fd:52:cb:f4 (try 3/3)
[ 52.072242] wlan0: direct probe to e2:94:fd:52:cb:f4 timed out
Regards,
R.
http://flickr.com/r208
chili555
May 9th, 2011, 07:52 PM
Hi,
I installed the non free package and try the solution explained upper.
But with no luck. The NetGear WG511 (V1) scan the networks and find mine but i can't get a connection.
Dmesg | grep p54
[ 18.313380] p54pci 0000:03:00.0: enabling device (0000 -> 0002)
[ 18.313402] p54pci 0000:03:00.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
[ 18.313421] p54pci 0000:03:00.0: setting latency timer to 64
[ 18.564879] ieee80211 phy0: p54 detected a LM86 firmware
[ 18.564888] p54: rx_mtu reduced from 3240 to 2376
[ 19.638687] Registered led device: p54-phy0::assoc
[ 19.638884] Registered led device: p54-phy0::tx
[ 19.639037] Registered led device: p54-phy0::rx
[ 19.639183] Registered led device: p54-phy0::radio
[ 19.639199] p54pci 0000:03:00.0: is registered as 'p
Dmesg after trying to connect to the ssid
[ 51.474468] wlan0: direct probe to e2:94:fd:52:cb:f4 (try 1/3)
[ 51.672049] wlan0: direct probe to e2:94:fd:52:cb:f4 (try 2/3)
[ 51.872243] wlan0: direct probe to e2:94:fd:52:cb:f4 (try 3/3)
[ 52.072242] wlan0: direct probe to e2:94:fd:52:cb:f4 timed out
Regards,
R.
http://flickr.com/r208When you click the Network Manager icon, do you see your network? When you click it and try to connect, are you asked for the encryption key; i.e. WEP, WPA, etc.? Does it try to connect?
Register208
May 10th, 2011, 12:41 PM
Thanks for the reply.
yes it ask for the password but after a long time about a minute.
I enter it and it re asks for it after the same time.
chili555
May 10th, 2011, 01:37 PM
Is your network set to WPA or WPA2 or the dreaded and tricky mixed WPA and WPA2 mode?
Register208
May 10th, 2011, 03:33 PM
It's WPA (TKIP + AES)
And the chanel is 5, how can i see that it had chosen the right channel?
Powered by vBulletin® Version 4.2.2 Copyright © 2024 vBulletin Solutions, Inc. All rights reserved.