I hate to say this, but I'm stumped. The various outputs you just posted show the card is correctly configured, it is associated with an access point, it has a valid IP and gateway, it just doesn't work.

The only things I can think of are:
1) If you haven't already, turn on the SSID broadcast of your AP. For some reason this makes a difference with some cards.
2) Try some different Windows drivers if you can find them (this is likely a longshot though).
3) Give linuxant a try. Linuxant is conceptually similar to ndiswrapper (i.e. it uses a Windows driver in Linux) but it sometimes works when ndiswrapper fails. It isn't free (I think the fee is $20) but they do have a free test period to try it out and see if it works.

Hum, another extreme thing to try, is to install mandriva 2005 or 2006 free (not the so-called one version) on a spare partition.

Alternatively if you still have time, other long shots, try latest ndiswrapper,
or update the kernel (re-install ndis after)
or even try suse 10.1

I think so as well, as these are working on my PC

Ok,

I think this might have to do with ndiswrapper. if I install version 16 I do not even get a card configuration in iwconfig...

I will try to install another distro, but I am also considering replacing the card... can anyone advice me a usb wireless card (I prefer usb but it can also be pci) that will work without any pain in linux suse and in preference with the 64 bits version?

BTW I got an email from linksys asking if the problem was solves. here you have my reply:

Date: Mon, 5 Jun 2006 23:56:54 -0700

Subject: WUSB54GS - Drivers [Incident: 060528-003632]

We have not heard from you concerning your request for support in the 120 hours since we sent you a response. Consequently, we have changed the status of your question to SOLVED.

To update this question by email, please reply to this message. Because your reply will be automatically processed, you MUST enter your reply in the space below. Text entered into any other part of this message will be discarded.

[===> Please enter your reply below this line <===]

The problem is not solved, you were just incapable to help solving it and, therefore, your costumer support was just useless.

I am selling the Linksys card and buying one from another brand.

[===> Please enter your reply above this line <===]

If you're thinking about replacing the card, I would do some homework in the LQ Hardware Compatibility List. There are lots of reports there on cards that work and cards that don't. My experience hanging around in this forum suggests that USB wireless cards are siginificantly more problematic that PCI or PCMCIA cards. I would also look for one that has native linux drivers. Intel is actually well supported, but there are certainly others.

And I love your reply to Linksys! If those clowns would support Linux, it would certainly be very helpful. I guess I find it highly ironic that they use Linux in their routers, yet refuse to support it for their other products.

This is good nagging to linksys!
I am going to install suse 10.1 on the laptop (curiosity)
and just for the sake of it try my WUSB54GS there.
Do try mandriva then
I may try a later release of ndisw, if I got the time

Maybe you found a kernel/ndiswrapper incompatibility of some kind

Linksys reply again stupid...

To which I replied excatly the same as in my previous email Aparently they have an automatic reply to the emails so I set up a automatic reply also )) Delete their rubish and keep sending always the same email...

Emanuel_UK, please let me know if it worked for you.

Cheers and guys thank you very much for all the help and support...

PA

______________________________________________________________
Dear Linksys Valued Customer,


Thank you for contacting Linksys Customer Support.

Thank you very much for taking time in giving us such valuable feedback. Rest assured that we shall continue to exert our best efforts to improve our products and services to meet your needs.

For more information on our products, please visit http://www.linksys.com/kb

Please feel free to send us an E-mail at support@linksys.com for any questions or suggestions that you may want us to know.

Thank you and have a nice day.


Regards,

I tried on suse 10.1 yesterday at home, no luck so far.
ndiswrapper 1.14 and 1.16 I tried.

I get a "bad cable error", then a bit of USB messages the device is named and identified correctly, but the device does not lit (does not start). Sorry no log at hand, but I know it does display this info in a different format
iManufacturer 1 Broadcom
iProduct 2 Linksys Wireless-G USB Network Adapter with
SpeedBooster
iSerial 3 8057


I feel mandriva does some magic with usb scripts that other distro handle
differently

I do not even get this
I possibly miss some USB / hotplug (I am running autofs) thingy.
I did a "stock install"
I really never licked suse, I must say 10.1 found it worse than previous versions.
Did not like beagle, htdig, very slow install, etc. My opinion anyway.

Guys, just to let you know that I am posting this from my Linux machine... yes it is true, after so much hard work I managed to get the card working... Ok I know you all are curious to know the solution... ...

I installed Mandriva

Suse sucks, Mandriva ROCKS!!!

Thanks a lot for all the help!

PA

eagleeyes, I am so happy, truely.
A new mandriva addict, null point for suse on this issue...
What can I ask for? I know of ubuntu thread whith big struggle as well.
If I even spend more time with suse and make it work I will let you know

eagleeyes, be sure to visit easyurpmi http://easyurpmi.zarb.org/
(or http://www.linuxfordummies.org/addmedia/)
to set your repositories. Do add a plf repository
Look at the tar.gz sticky in Mandy forum

Congrats!


Now if we only knew what Suse was doing wrong here.......

Have you got any idea of to tackle that? I mean usb srcipts in suse?
Or maybe kernel version issue?

Even the syslog in 10.1 is a pain. I had to edit syslog-ng to log evthg
there was not a "normal" syslog anymore

I got mandy 2005 & 2006 working: these 2 do not handle hotplugging in the same way at all.

I got a slightly similar problem while trying to use ndiswrapper (v1.6) with slackware 10.2. After a *lot* of headscratching, trying to recompile kernels, having the keyboard lock up after a "modprobe ndiswapper", reading about 4K/8K thingies and posts outside of here which reconed ndiswrapper was awful, I tried the following (note: I *do* have ndiswrapper working with Mandrake 2005 LE, but I couldn't get it going with slackware 10.2).

After doing a fresh install of slackware 10.2, I used the kernel that comes with slackware 10.2 (not the 2.4 kernel, but the 2.6.13 one as I needed the newer 2.6 kernel). There are 2 slackware CDs, this is on the second one. Everything in the directory on the cd that holds the kernel source, etc. needs to be installed.

After compiling ndiswrapper and installing it (make, make install) I then created a /etc/resolv.conf file.

After doing this and running ndiswrapper -i [driver name] where [driver name] is,for me net111v2.inf (and remembering that I got ndiswrapper to work in mandrake, but not slackware, still trying!) I decided to pinch the little script I wrote to start ndiswrapper and see what it would do. It *almost* worked, I just needed to add on lines such as "ifconfg wlan0 up" for slackware as mandrake seemed to do these automatically. This is the script I came up with;

#!/bin/sh
echo 1
sleep 3
rmmod ndiswrapper

echo 2
sleep 3
modprobe ndiswrapper

echo 3
sleep 3
iwconfig wlan0 essid ~my essid~
echo 4
sleep 3
iwconfig wlan0 key open ~my wireless encryption key~

echo 5
sleep 3
ifconfig wlan0 192.168.0.78

echo 6
ifconfig wlan0 up
sleep 3

echo 7
route add default gateway 192.168.0.10
sleep 3

ifconfig wlan0 192.168.0.78
ifconfig wlan0 up

echo
ping 192.168.0.10

--

I saved this as a script file (for want of an original name, I just called it "go"), did a chmod 0777 go on it, and ran it with ./go .

This seemed to work as well, I could ping my router and google!

NB, I was using the original driver cd which came with my netgear WG111V2 usb stick, I used the win2000 drivers (and not the xp ones).

Hope this helps someone .

SP

Thanks for your tips on this card. I've got a couple of comments:

I think starting with 1.6, ndiswrapper requires a version of gcc that Slackware 10.2 doesn't support yet. The next version should, but anyone using Slackware 10.2 or earlier should stick with ndiswrapper 1.5 or earlier. Acutally, I'm surprised you got it to compile at all.
The stock Slackware kernels don't have the 4K stack problem, but ndiswrapper thinks they do. The directive for the 4K/8K stack setting is not set in the .config file that comes with Slackware, and ndiswrapper assumes this means that 4K stacks are used. In fact, this means they aren't used.

I hope you mean you edited the resolv.conf file. A full install of Slackware should have created this. If it didn't, something went very wrong.