Arch Linux

chipbuster

Member

Registered: 2012-02-22

Posts: 12

RT3062-based wireless cannot assign requested address

EDIT: Found this thread which suggests that a new dhcpcd might be causing the error. Removed IPv6 from dhcp and downgraded to 5.2.9-1 via ARM--still no change.

Hey all. I've been trying to get my wireless connection stable for a while now, and it's simply not working out. I have an EDIMAX-7722In, which uses the Ralink RT3062 chipset. I initially started using the rt2800pci driver and family, after hearing that it was supported in kernel 3.2, though I never got that confirmed and I'm not sure where to look to find out. I'm using NetworkManager and KDE, controlling it through the networkmanager widget, since I'm still figuring out how to use ip/iwconfig.

When I have the rt2800pci driver loaded and I attempt to connect to an insecure network, it will start to connect, get stuck on "setting network address," and fail after a time. It usually takes 4 or 5 tries to connect to an unsecured network like this, with a lot of failures along the way. I have not noticed any tendency for the connection to be dropped once its connected, though I haven't used it very much. errors.log shows a repitition of this line for each failed connection:

Mar 16 18:53:14 localhost dhcpcd[1728]: wlan0: sendmsg: Cannot assign requested address
Mar 16 18:53:44 localhost dhcpcd[1728]: timed out

I've tried looking into dhcpd.conf, but there's nothing there that would seem to help my case out.

I tried connecting via CLI per the Wiki, but it seems to fail quite miserably. I can scan for networks, but it refused to associate with any of them when I enter "sudo iwconfig wlan0 [essid]." iwconfig wlan0 returns with "ESSID:off/any" and "Access Point: Not-Associated." dhcpcd, of course, can't get ip addresses because it's not connected.

When I try to connect to a network with 802.1x security, networkmanager never gets past asking for my password (in the widget, "configuring interface"). I did manage to get past that stage once or twice, but it just spit back an authentication failure (and I'm absolutely positive I got the credentials right).

I did manage to capture one line from networkmanager that seemed to be about authentication in the logs.

Mar 16 10:53:47 localhost NetworkManager[574]: wifi_secrets_cb: assertion `nm_device_get_state (dev) == NM_DEVICE_STATE_NEED_AUTH' failed

I tried the wireless driver provided by EDIMAX, but it didn't seem to make things much better. I compiled as I did before (I got this card working on Ubuntu 11.10 prior to installing Arch) and loaded it into the kernel while removing rt2800pci and family. I got a new interface (ra0 instead of wlan0), but networkmanager widget wouldn't let me connect: clicking on the networks had no effect. I'm not sure how to connect via ip.

So here I am, at wits end. Googling my errors wasn't much help, since they resulted mostly in similar-sounding errors coming off of completely different systems. I can't seem to find a good way to fix this,

If rt2800pci is in fact fully supported on the 3.2 kernel, I'd like to use it, since it'll save me the pain of recompiling with every kernel update, but right now I'd just like to get this card going. Here's a little more info on my computer, I'd be happy to provide anything else that may be needed, but I'm going to be away from my computer for quite some time this weekend (between 3pm and 10pm):

lspci (relevant results):

[chipbuster@lpc1 etc]$ lspci -nn
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 03)
04:06.0 Network controller [0280]: Ralink corp. RT3062 Wireless 802.11n 2T/2R [1814:3062]

lsmod|grep rt2

Module                  Size  Used by
rt2800pci               9341  0 
rt2800lib              40260  1 rt2800pci
rt2x00pci               5082  1 rt2800pci
rt2x00lib              35183  3 rt2x00pci,rt2800lib,rt2800pci
eeprom_93cx6            1376  1 rt2800pci
crc_ccitt               1363  1 rt2800lib
mac80211              228527  3 rt2x00lib,rt2x00pci,rt2800lib
cfg80211              172260  2 mac80211,rt2x00lib
rfkill                 15498  1 cfg80211

a snippet from NetworkManager

Mar 17 02:42:56 localhost NetworkManager[571]: <info> Auto-activating connection 'UCM-Guest'.
Mar 17 02:42:56 localhost NetworkManager[571]: <info> Activation (wlan0) starting connection 'UCM-Guest'
Mar 17 02:42:56 localhost NetworkManager[571]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Mar 17 02:42:56 localhost NetworkManager[571]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 17 02:42:56 localhost NetworkManager[571]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 17 02:42:56 localhost NetworkManager[571]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar 17 02:42:56 localhost NetworkManager[571]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 17 02:42:56 localhost NetworkManager[571]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 17 02:42:56 localhost NetworkManager[571]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Mar 17 02:42:56 localhost NetworkManager[571]: <info> Activation (wlan0/wireless): connection 'UCM-Guest' requires no security.  No secrets needed.
Mar 17 02:42:56 localhost NetworkManager[571]: <info> Config: added 'ssid' value 'UCM-Guest'
Mar 17 02:42:56 localhost NetworkManager[571]: <info> Config: added 'scan_ssid' value '1'
Mar 17 02:42:56 localhost NetworkManager[571]: <info> Config: added 'key_mgmt' value 'NONE'
Mar 17 02:42:56 localhost NetworkManager[571]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar 17 02:42:56 localhost NetworkManager[571]: <info> Config: set interface ap_scan to 1
Mar 17 02:42:56 localhost NetworkManager[571]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Mar 17 02:42:57 localhost NetworkManager[571]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Mar 17 02:42:57 localhost NetworkManager[571]: <info> (wlan0): supplicant interface state: authenticating -> associating
Mar 17 02:42:57 localhost NetworkManager[571]: <info> (wlan0): supplicant interface state: associating -> completed
Mar 17 02:42:57 localhost NetworkManager[571]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'UCM-Guest'.
Mar 17 02:42:57 localhost NetworkManager[571]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Mar 17 02:42:57 localhost NetworkManager[571]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Mar 17 02:42:57 localhost NetworkManager[571]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Mar 17 02:42:57 localhost NetworkManager[571]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Mar 17 02:42:57 localhost NetworkManager[571]: <info> dhcpcd started with pid 4674
Mar 17 02:42:57 localhost NetworkManager[571]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Mar 17 02:42:57 localhost dhcpcd[4674]: version 5.2.9 starting
Mar 17 02:42:57 localhost dhcpcd[4674]: wlan0: rebinding lease of 10.12.194.149
Mar 17 02:42:57 localhost NetworkManager[571]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Mar 17 02:43:07 localhost dhcpcd[4674]: wlan0: broadcasting for a lease
Mar 17 02:43:19 localhost dhcpcd[4674]: wlan0: offered 10.12.194.149 from 1.1.1.1
Mar 17 02:43:27 localhost dhcpcd[4674]: timed out
Mar 17 02:43:27 localhost NetworkManager[571]: <info> (wlan0): DHCPv4 client pid 4674 exited with status 1
Mar 17 02:43:27 localhost NetworkManager[571]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) scheduled...
Mar 17 02:43:27 localhost NetworkManager[571]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) started...
Mar 17 02:43:27 localhost NetworkManager[571]: <info> (wlan0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Mar 17 02:43:27 localhost NetworkManager[571]: <warn> Activation (wlan0) failed for access point (UCM-Guest)
Mar 17 02:43:27 localhost NetworkManager[571]: <info> Marking connection 'UCM-Guest' invalid.
Mar 17 02:43:27 localhost NetworkManager[571]: <warn> Activation (wlan0) failed.
Mar 17 02:43:27 localhost NetworkManager[571]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) complete.
Mar 17 02:43:27 localhost NetworkManager[571]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Mar 17 02:43:27 localhost NetworkManager[571]: <info> (wlan0): deactivating device (reason 'none') [0]

P.S. If anyone can suggest a Linux-friendly PCI wireless card for under $40, I'm totally game for that too Unfortunately, most of the ones I see on sale are really old or really expensive.

Last edited by chipbuster (2012-03-17 09:48:03)

ratcheer

Member

Registered: 2011-10-09

Posts: 924

Re: RT3062-based wireless cannot assign requested address

Why not just install the rt3562sta driver from Ralink? Then your existing card will work just fine. I will help you, if needed.

Tim

chipbuster

Member

Registered: 2012-02-22

Posts: 12

Re: RT3062-based wireless cannot assign requested address

Sorry for the unclarity on that. I already tried installing the rt3562, both from source and from the repos.

The repository version fails to insert with "ERROR: could not insert 'rt3562sta': Exec format error." I haven't been able to isolate the source of this.

My own version will sometimes successfully load into the kernel, but I can't access anything on NetworkManager, It's actually stopped loading just as I checked it for writing this post, so I'll see if I can figure out what's going on here...

EDIT: Okay, flushing the repository rt352sta package let it load, but now it just sits there. Following the instructions on the Wiki page results in nothing. It just give me a prompt like it connected, but iwconfig shows no ESSID. Doing it with rt2800pci gives me no problems for now, but I'll see if it stays that way.

EDIT2: Okay, now rt2800pci is have the same problem: it can't associate with the essid.

EDIT3: iwconfig can now associate to the essid, but dhcpcd shows "wlan0: Waiting for carrier" and then times out, even though I've set "iwconfig wlan0 channel auto"

Last edited by chipbuster (2012-03-17 19:31:25)

ratcheer

Member

Registered: 2011-10-09

Posts: 924

Re: RT3062-based wireless cannot assign requested address

I have no idea what is going on with all that. I can rarely get rt2800pci to do anything. On rare occasions, it says it is connected, but then it disconnects and tries to reconnect, continuously. More often, it just doesn't work at all.

I run rt3562sta version 4.1.1 that I downloaded directly from Ralink. If I already have it on my machine, I run "make clean". Then, "make", "make install", and "modprobe rt3562sta". I also blacklist rt2800pci. Before I make rt3562sta, if I have never done it before on a given system, I edit ..../src/linux/config.mk to set HAS_WPA_SUPPLICANT=y and HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y

I never could figure out how to use the one from the AUR. I can't remember what my problem was.

Good luck,
Tim

chipbuster

Member

Registered: 2012-02-22

Posts: 12

Re: RT3062-based wireless cannot assign requested address

I have the driver compiled with HAS_WPA_SUPPLICANT=y and HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y, but when I insert it (after modprobe -r rt2800pci), it doesn't connect. iwlist ra0 scan says "interface does not support scanning." None of the fixes in the wiki have worked. Currently pawing through dmesg to see if I can find anything relevant (although it mostly looks like gibberish to me).

chipbuster

Member

Registered: 2012-02-22

Posts: 12

Re: RT3062-based wireless cannot assign requested address

Unfortunately, not solved, and probably won't be. I switched out to a $20 TPLink card with an Atheros chipset, works like a breeze. I suppose my computer's not ready for the RT chips yet.