Dapper 5, wireless RT61 problem

I meant 'iwconfig ra0 essid some_essid' obviously :)

I tried flight 6 and this is still hapening

i have same problem.

Haven't tried using iwconfig, but my card wont get any ipadress when using the standard network applet. It seems to "work" otherwise, since it's flashing the LEDs and the network applet reports traffic, but no IP adress...

This is the output from ifconfig (if it helps):
ra0 Link encap:Ethernet HWaddr 00:13:46:78:B3:9D
          inet6 addr: fe80::213:46ff:fe78:b39d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:6543 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1374 errors:0 dropped:0 overruns:0 carrier:0
          collisions:154 txqueuelen:1000
          RX bytes:482510 (471.2 KiB) TX bytes:240 (240.0 b)
          Interrupt:10

Keep up the great work!!!

Forgot to mention that I too use Flight 6.

Could someone please update this bug with whether or not it's still occurring in Dapper Final or, if possible, Edgy Beta?

Thanks

I seem to be experiencing this problem on Dapper final.
I have a D-link DWL-G510 Revision C1 wireless desktop adapter.

iwconfig uses all of CPU and top shows it is 100% sys.

Trying to do anything with the process (attach gdb, killing it, strace) doesn't work. The gdb/kill/strace just sits there doing nothing.

The odd thing is that I can get the connection to work. It seems that if I do:
====
paulm@ubuntu:~ $ sudo ifconfig ra0 up
paulm@ubuntu:~ $ sudo ifconfig ra0 down
paulm@ubuntu:~ $ sudo ifup ra0
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/ra0/00:15:e9:32:4d:6b
Sending on LPF/ra0/00:15:e9:32:4d:6b
Sending on Socket/fallback
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 192.168.0.1
DHCPREQUEST on ra0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.102 -- renewal in 280604 seconds.
paulm@ubuntu:~ $
====

If I try it without doing the ifconfig up/down beforehand then it just hangs
====
paulm@ubuntu:~ $ sudo ifup ra0
Password:
====
and that's it.

I have no idea why this would make a difference but am happy to investigate further if given a bit of direction. I have had this card for at least 6 months and after failing to get it to work on Breezy this is the first time I have tried to get it going on Dapper.

The workaround isn't much use because I need the connection to start up automatically and adding

auto ra0

to /etc/network/interfaces just causes the server to hang with iwconfig at 100% cpu on start up and seems to block a lot of other stuff starting properly (X for example complains that it failed to load the NVidia kernel module) and the server startup process eventualy stops dead when trying to start the Firestarter firewall.

There seem's to be plenty of people experiencing this problem to confirm it. Does edgy happen to work correctly?

If possible, please test it with the latest feisty herd. Now's the time to get this fixed.

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.