On 05-Jun-10 22:11:48, Jenny Hopkins wrote:
On 5 June 2010 22:40, Ted Harding Ted.Harding@manchester.ac.uk wrote:
On 05-Jun-10 21:31:07, Jenny Hopkins wrote:
On 5 June 2010 22:20, Jenny Hopkins hopkins.jenny@gmail.com wrote:
Hi all,
I bought a wireless network card RT2561/RT61 rev B 802.11g last week for my amd64 debian squeeze machine. _I plugged the card in, installed firmware-ralink (via wired connection), modprobed for rt61pci, and sat back watching the shiny new connection and gloating at the easiest install of hardware I have ever had.
I duly moved the pc to a room with no wired capability, and network manager (running under gnome) detected and connected me to the wap netgear with a not bad signal.
A few hours later, the connection suddenly went down. _All efforts to ifupdown wlan0 or stop and start network manager failed to connect again, with dmesg reporting "wlan0: deauthenticating from <blah> by local choice (reason=3)". _Only a reboot seemed to sort it, and then only for a short while. Oh yes - I also got some ridiculous ping times for the gateway, even though the signal was fairly strong, which reduced to a sensible amount when I succeeded finally in quashing the wired interface eth0.
I've come back after a week away, however, and it won't connect at all. _syslog reports "rt61pci _firmware: requesting rt2561.bin" , modinfo rt61pci shows a bunch of useful stuff that assures me it is all loaded. _It can't be a firmware issue, surely, as it worked at first? I just keep being told "ADDRCONF(NETDEV_UP): wlan0: link is not ready"
Neither giving wlan0 a fixed IP in interfaces, or telling it to request an address from a dhcp server makes any difference. _(The request for an address isn't even getting as far as the dhcp server).
I'm stumped - any suggestions where to look for clues? _I did read it could be a clash between udev and network manager, I also have no idea whether invoking iwconfig and iwlist scan makes any difference. _I'm sure I've tried every combination possible by now.
Thanks, sorry if this isn't very clear, I've been going in circles for so long I think I've forgotten where I began.
Ah yes, should also have said what kernel I'm running: _2.6.32-3-amd64.
Thanks,
Jenny
Hi Jen, (shooting in the dark somewhat): what happens if you move the machine back into the same room as the wireless router and start again? Does it stay OK so long as it's in the same room?
Thanks Ted:
It did actually work fine at first in the room without router/wired connection, for a good few hours. Thanks for the hint though. I'll have to move it back to that room if I don't solve the problem ( which would be a shame as I've set up a cosy office here) and use the wired interface. The first thing I'll do is check the wireless if I do have to do that but since it did work down here I can't see that would be the issue.
Jen
You can get intermittent connectivity in locations more remote from the router. Local events (beyond your control) can interfere with the wireless connection -- e.g. if your neighbour's dog settles down next to the dividing wall within a few feet of your computer, or perhaps if you get interference from a neighbour's wireless router. Or, simply, just your own nearby presence (under certain conditions, me walking into my kitchen can switch the radio therein into "mush" mode).
Radio is funny stuuf! Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@manchester.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 05-Jun-10 Time: 23:39:19 ------------------------------ XFMail ------------------------------