Netgear WG511 and Puppy4 (solved)
Netgear WG511 and Puppy4 (solved)
prism54 module is loaded, but the card isn't even powered.
cartctl shows no cards in either PCMCIA slot.
cartctl shows no cards in either PCMCIA slot.
Last edited by ieee488 on Sat 02 Aug 2008, 14:10, edited 2 times in total.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Try resetting the Cardbus interface, as explained here -
http://www.murga-linux.com/puppy/viewto ... 1707#31707
http://www.murga-linux.com/puppy/viewto ... 1707#31707
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
There are 3 forum members all with prism54 problems in Puppy4 at the same time. Spooky!
First I would reload the prism54 module, just in case it loaded incorrectly during boot up.
Now run this command to see if the prism54 module has successfully created a network interface
If you already have a LAN interface, the wifi interface is likely to be "eth1". If you see eth1, the problem may simply be that the interface needs to be brought up before running the Network Wizard, so do this -
But if you don't see a wifi interface listed, run dmesg to check to see how the prism54 module loaded. Look especially for messages relating to firmware.
Also check to see if the prism54 firmware is in place in /lib/firmware
These are the 3 firmware files that should be there -
isl3877
isl3880 (symlink)
isl3890
First I would reload the prism54 module, just in case it loaded incorrectly during boot up.
Code: Select all
rmmod prism54
modprobe prism54
Code: Select all
ifconfig -a
Code: Select all
ifconfig eth1 up
Also check to see if the prism54 firmware is in place in /lib/firmware
These are the 3 firmware files that should be there -
isl3877
isl3880 (symlink)
isl3890
I was able to get the card working by using ndiswrapper.
Yay!
Why prism54 module will not work -->
per http://linux-wless.passys.nl/language/l ... nglish.php, it appears that there are 2 versions of the WG511 v1 cards not to be confused with the fact that there are WG511 v2 cards as well. These WG511 v1 cards actually only say WG511 and the antenna plastic is white not black. Anyhow, the two versions of the WG511 v1 cards are those made in China and those made in Taiwan. Apparently, those made in China will not work with prism54 module. The relevant section in the linked webpage to read is PrismGT chipset.
Yay!
Why prism54 module will not work -->
per http://linux-wless.passys.nl/language/l ... nglish.php, it appears that there are 2 versions of the WG511 v1 cards not to be confused with the fact that there are WG511 v2 cards as well. These WG511 v1 cards actually only say WG511 and the antenna plastic is white not black. Anyhow, the two versions of the WG511 v1 cards are those made in China and those made in Taiwan. Apparently, those made in China will not work with prism54 module. The relevant section in the linked webpage to read is PrismGT chipset.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Yes, there are different variants of the same model number with different chipsets. This is a common situation.
You have the Marvell-based version of the WG511 v1.
Clearly you attempted to load this module, yourself.
I caution everyone not to assume what driver will work, unless you know the exact variant of your wifi device, or the exact pci id.
I see that forum member Unicav is in a similar situation, and it's likewise unclear whether prism54 is correct in his case.
Hopefully the information I explained above is still relevant to forum member mpierrat25's SMC2835W.
You have the Marvell-based version of the WG511 v1.
Your original post does not explain why the prism54 module was loaded, but we now know that Puppy would not have loaded this module automatically ... because the pci id would not match.ieee488 wrote:prism54 module is loaded, but the card isn't even powered.
Clearly you attempted to load this module, yourself.
I caution everyone not to assume what driver will work, unless you know the exact variant of your wifi device, or the exact pci id.
I see that forum member Unicav is in a similar situation, and it's likewise unclear whether prism54 is correct in his case.
Hopefully the information I explained above is still relevant to forum member mpierrat25's SMC2835W.
No, my card does not have Marvell chipset.
According to http://daemonizer.de/prism54/wg511/, I have WG511 v3 (3rd one down from the top) except mine is made in China.
Puppy recognized it and loaded prism54. I wasn't the one to do it. But because it was a "softmac" limited firmware in the card itself versus "fullmac", it does not work with prism54.
I hope this helps those with the WG511 card.
According to http://daemonizer.de/prism54/wg511/, I have WG511 v3 (3rd one down from the top) except mine is made in China.
Puppy recognized it and loaded prism54. I wasn't the one to do it. But because it was a "softmac" limited firmware in the card itself versus "fullmac", it does not work with prism54.
I hope this helps those with the WG511 card.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
I am trying to get a WG511 version 3 (China) working on eth1. I have pointed ndiswrapper to the Windows Netgear driver (netwg511.inf) but the network wizard shows prism54 associated with eth1, probably because Puppy tried it first.
How can I unload prism54 and stop it loading on boot?
How can I unload prism54 and stop it loading on boot?
Last edited by Terryphi on Fri 01 Aug 2008, 06:40, edited 1 time in total.
Here is a bit more info in case it is relevant. I have got a WG111 working on wlan0 and its driver is also linked with ndiswrapper.
iwconfig produces this response:
ifconfig eth1 up produces this response:
Code: Select all
ndiswrapper -l
netwg111 : driver installed
netwg511 : driver installed
device (1260:3890) present (alternate driver : prism54)
Code: Select all
iwconfig
eth1 NOT READY!
Code: Select all
ifconfig eth1 up
ifconfig : SIOCSIFFLAGS : Timer expired
Thanks for the pointers, ieeee488.
I have found the thread on how to blacklist a module here:
http://www.murga-linux.com/puppy/viewto ... 35&t=31883
I will also look at your other suggestions when I have time. I have the WG111 working OK but I don't like being defeated by the WG511!
I have found the thread on how to blacklist a module here:
http://www.murga-linux.com/puppy/viewto ... 35&t=31883
I will also look at your other suggestions when I have time. I have the WG111 working OK but I don't like being defeated by the WG511!
I did this:
Open /etc/modprobe.conf and enter:
alias prism54 off
save and reboot.
The WG511 then flashes its lights at bootup and the network connection icon appears on the desktop. However, my browser connects only briefly to a web page and then the connection becomes inactive. The network connection freezes, but still identifies itself as having a signal and being connected. When I do dmesg it appears that there is a problem with process ntos-wq/0. After a lot of code I see:
A Google search suggests that this a widespread problem reported in other distros including Ubuntu.
https://bugs.launchpad.net/ubuntu/+sour ... bug/136814
There has been discussion whether this is a ndiswrapper bug or a Linux kernel bug. Either way this is unlikely to work until the bug is fixed in a later version.
I have gone back to using the WG111 for now as it works perfectly. However, I would like to get the WG511 working because it is WPA capable and the WG111 is not.
Open /etc/modprobe.conf and enter:
alias prism54 off
save and reboot.
The WG511 then flashes its lights at bootup and the network connection icon appears on the desktop. However, my browser connects only briefly to a web page and then the connection becomes inactive. The network connection freezes, but still identifies itself as having a signal and being connected. When I do dmesg it appears that there is a problem with process ntos-wq/0. After a lot of code I see:
Code: Select all
note: ntos_wq/0[3323] exited with preempt_count 3
https://bugs.launchpad.net/ubuntu/+sour ... bug/136814
There has been discussion whether this is a ndiswrapper bug or a Linux kernel bug. Either way this is unlikely to work until the bug is fixed in a later version.
I have gone back to using the WG111 for now as it works perfectly. However, I would like to get the WG511 working because it is WPA capable and the WG111 is not.
Last edited by Terryphi on Sun 03 Aug 2008, 17:12, edited 2 times in total.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
There is now a better way to tell Puppy to use one module instead of another; by modifying /etc/rc.d/MODULESCONFIGTerryphi wrote:I have found the thread on how to blacklist a module here:
http://www.murga-linux.com/puppy/viewto ... 35&t=31883
http://puppylinux.com/blog/?page=10
But I wouldn't bother struggling with ndiswrapper, your best bet is the new p54pci module in Puppy 4.1alpha5
http://distro.ibiblio.org/pub/linux/dis ... 4.1alpha5/
Puppy 4.1alpha5 with p54pci is no better.( I used the IDE kernel version as I thought that was probably best for my system.)tempestuous wrote: But I wouldn't bother struggling with ndiswrapper, your best bet is the new p54pci module in Puppy 4.1alpha5
http://distro.ibiblio.org/pub/linux/dis ... 4.1alpha5/
I'll stick with the WG111 which does work very well with ndiswrapper.