You are not logged in.
Hi, fellow archians.
I'm currently having problems getting my NetGear WNA1000M with the RTL8188CUS chipset to work. The wired connection works fine with the same router. What I've done so far:
lsusb:
Bus 001 Device 002: ID 0846:9041 NetGear, Inc. WNA1000M 802.11bgn [Realtek RTL8188CUS]
I assumed the RTL8188CUS chipset went under the same module as rtl8192cu, and the dmesg for that returns:
dmesg | grep rtl8192cu:
[ 6.139617] rtl8192cu: rtl8192cu: Chip version 0x10
[ 6.223612] rtl8192cu: MAC address: c4:3d:c7:78:99:cf
[ 6.223615] rtl8192cu: Board Type 0
[ 6.223623] Loading firmware rtlwifi/rtl8192cufw.bin
[ 6.223913] usbcore: registered new interface driver rtl8192cu
[ 8.648609] rtl8192cu: MAC auto ON okay!
[ 8.681239] rtl8192cu: Tx queue select: 0x05
To my understanding, this should at least be in order. Then comes the setting up of the actual wireless:
ip link set wlan0 up
iwlist wlan0 scan:
wlan0 Scan completed :
Cell 01 - Address: F0:7D:68:D8:CF:F0
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=68/70 Signal level=-42 dBm
Encryption key:off
ESSID:"dlink"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=00000000488d71cd
Extra: Last beacon: 733ms ago
IE: Unknown: 0005646C696E6B
IE: Unknown: 010882848B962430486C
IE: Unknown: 030101
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: Unknown: 32040C121860
IE: Unknown: 2D1A7C181BFFFF000000000000000000000000000000000000000000
IE: Unknown: 3D1601080000000000000000000000000000000000000000
IE: Unknown: DD790050F204104A000110104400010210570001011041000100103B00010310470010E21A7DA5745BFAB287588D3405AC91001021000842726F6164636F6D1023000842726F6164636F6D1024000631323334353610420004313233341054000800060050F20400011011000844534C3237343042100800020088
IE: Unknown: DD090010180200F4010000
IE: Unknown: DD1E00904C337C181BFFFF000000000000000000000000000000000000000000
IE: Unknown: DD1A00904C3401080000000000000000000000000000000000000000
iwconfig wlan0 essid "dlink"
iwconfig wlan0 channel 1
iwconfig wlan0:
wlan0 IEEE 802.11bgn ESSID:"dlink"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr=2347 B Fragment thr:off
Power Management:off
dhcpcd wlan0:
dhcpcd[948]: version 5.5.6 starting
dhcpcd[948]: wlan0: using hwaddr c4:3d:c7:78:99:cf
dhcpcd[948]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
dhcpcd[948]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
dhcpcd[948]: wlan0: waiting for carrier
dhcpcd[948]: timed out
dhcpcd[948]: allowing 8 seconds for IPv4LL timeout
dhcpcd[948]: timed out
There's no difference if I choose to use dhclient. Wicd gets stuck on "obtaining ip address", so I assume there's something other wonky going on.
Any help/diagnose is appreciated!
Offline
check dmesg
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
check dmesg
Ah, this is the output of dmesg: http://pastebin.com/1mMuuqSB
However, it turns out that if I leave the computer off for a while, it's able to connect to the wireless network. However; if I reboot the computer, it's unable to do so. It refuses to give me an association point, if that's the case.
For what it matters; the router recognizes it's existence.
BSSID Associated Authorized SSID
C4:... No No dlink
I'm honestly at loss.
Last edited by tsoet (2012-05-30 16:22:18)
Offline
Hi.
I've had some association problems with this adapter also. Although I can't claim to know exactly what happens, it seems like the device gets into a certain "state" where you must remove the power (unplugging or shutdown) to use the adapter again. I use netcfg to bring up my connection automatically at boot, but if a situation occurs where I must disconnect, I have to replug the usb device in order to reconnect to the network with netcfg - or shutdown and power back on.
I would suggest just unplugging the device for a couple of seconds and plugging it back in - then trying again. I hope this helps - not sure if this is your exact problem, but I think it's caused by the same underlying issue with this hardware or driver.
Offline
Hi, I'm having similar problems with the rtl8192ce module (i.e. the connection time out at the authentication stage) (bugtracker)
A solution for me was to disable the power saving features as explained in this post: https://bbs.archlinux.org/viewtopic.php … 3#p1107433
Can you check if a similar hack works for you?
Offline
Hi, I'm having similar problems with the rtl8192ce module (i.e. the connection time out at the authentication stage) (bugtracker)
A solution for me was to disable the power saving features as explained in this post: https://bbs.archlinux.org/viewtopic.php … 3#p1107433
Can you check if a similar hack works for you?
It looks like the ips and fwlps options don't exist for the rtl8192cu module. I have noticed that if I just unload and reload the module, it gets around my problem, but it would be nice to find an equivalent hack for this module, if that is indeed the issue. modinfo didn't give me much in the way of specifying a equivalent options.
Offline