I purchased a dlink wireless usb adapter DWL-g122 for my SUSE 10.0 box. My first attempt was to just plug it in and see what happened. SUSE recognized the new hardware and configured it with YaST. About the only thing I had to do was enter the ESSID for my network. It loaded the rt2570 module. The lnk and act leds on the adapter were on/blinking and I had an ip address assigned to rausb0. I could ping my Netgear router and access the configuration page. But I couldn't connect to the internet and KWiFiManager said I had zero signal strength. The router is 4 ft from the adapter.

Second Try: I installed ndiswrapper and used the windows driver from the dlink cd. I now had wlan0 in YaST with the ndiswrapper module, also configured with my ESSID. There were no leds lit on the adapter, except an occasional blink on the act led. Iwconfig showed the ESSID as being off/any instead of the correct id I had previously. Even after using the command: iwconfig wlan0 essid "name" it still said off/any. I couldn't get an ip address for wlan0 but KWiFiManager said the signal strength was 100%.

Now, I've uninstalled the ndiswrapper module and reconfigured rausb0 with the rt2570 module. The result is the same, but at least I have an ip address and the leds are on. And I can still connect to my router. But I have zero signal.

I did notice one difference between eth0 and rausb0 from the ifconfig command. eth0 has a line listing the interrupt and rausb0 doesn't.

eth0
Link encap:Ethernet HWaddr 00:01:6C:C1:30:AF
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::201:6cff:fec1:30af/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:79 errors:0 dropped:0 overruns:0 frame:0
TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13596 (13.2 Kb) TX bytes:8438 (8.2 Kb)
Interrupt:3 Base address:0x8000

rausb0
Link encap:Ethernet HWaddr 00:13:46:E8:22:4D
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::213:46ff:fee8:224d/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:130543 (127.4 Kb) TX bytes:25512 (24.9 Kb)

eth0 connection works fine. Any ideas?

Go back to the non-ndis option.

Make sure that the interface is routed properly

paste the output from Cheers
-Rob

yeah, i agree. no point in using ndis if a native solution is avalable.

I prefer to use the rt2570 from SUSE, but had the same problem as pilotgi.

See post 5:
http://www.linuxquestions.org/questi...d.php?t=404799

ndis saved me for the moment.

Keep us updated

Results of route:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 rausb0
link-local * 255.255.0.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0

ifconfig still shows the same as above in my first post for rausb0. The lnk led is steady greeen on the adapter. I'll try Fire!'s suggestion with ndis later this evening.

for the moment disable any onboard lan. any change?

If you mean stopping eth0 with 'rcnetwork stop eth0' then, no this doesn't help with the wireless.

Good news (for the moment)
I performed a auto update of the SUSE kernel to 2.6.13-15.8-default
And I expected that my USB network card to fail after reboot...

After reboot ndis was corrupt like I predicted, but unexpected
my Belkin USB (F5D7050) started to come alive! rt2570.ko must be improved.
I went to yast to configure the rausb0.

Yes next, I unloaded the windows drivers from ndis, removed the ndis program
itself and the configuration for wlan0.

For the last hour I am 100% linux. The upcoming days I try to use the
connection as much as possible to see how it performs.

I've been using SuSE since 5.0 and I love it. I love Linux just as much, and with the exception of VMWare and 'doze XP for development and testing, I'm all *nix.

That being said, I have a laptop from Linux Certified (yes, made just fox Linux) and have had nothing but problems with wireless networking. The support for it, at least in the out-of-the-box configuration of SuSE which I have (just installed with YAST, made no changes to wireless networking), it's a PITA.

Linux and wireless networking (at least under SuSE) still have quite a ways to go to get the level that Windows, Mac, etc. have reached. I find that KWiFiManager rarely detects networks properly, lacks the interface of Windows or the proprietary Atheros programs, and KNetAttach lacks most any functionality which I assumed it would have (automatic switchover between WLAN/LAN, and the ability to remember a variety of LAN profiles for us laptop users).