| Summary: | Unable to associate with my access point | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | galewis |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | dcbw, jklimes |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-09 16:15:54 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Most probably driver issue. What driver do you use? $ lsmod | grep rt I think, the Belkin USB adapter F6D4050 v2 (050d:935b) is supported by in-kernel rt28xx drivers (rt2800usb): http://www.wikidevi.com/wiki/Belkin_F6D4050_v2 $ modinfo rt2800usb | grep v050Dp935B So, try removing any rtXXXX drivers and 'modprobe rt2800usb' PS: There are also binary drivers from Ralink available from rpmfusion (rt2870 and rt3070), which may work. However they don't list support for your dongle. See e.g: https://bbs.archlinux.org/viewtopic.php?pid=800110 Hi Jirka, Thx for the response. However, I already had the rt2800usb driver on my system and it doesn't recognize the dongle. After a lot of surfing and reading I found the rt2870sta driver and that allowed me to at least see the dongle in the list of devices. However, regardless of which driver I load (modprobe rt28xxx) I cannot associate. With the rt2870sta driver I can at least see the light blinking so it looks like it is doing something. However, as you can see from the above details it times out. Also, I loaded and done "modinfo <driver> | grep v050Dp935B" and they both result in no output. Does this mean that the dongle is not supported. I noticed that for the rt2870sta driver v050Dp815C is listed twice, is this a mistake and should it be v050Dp935B? BTW, the instrucitons I followed to get the dongle recognized in the first place is the one you've listed above at bbs.archlinux.org. Thx (In reply to comment #2) > Hi Jirka, > > Also, I loaded and done "modinfo <driver> | grep v050Dp935B" and they both > result in no output. Does this mean that the dongle is not supported. > What kernel version do you use? With the latest F15 one, your USB dongle *is* listed in rt2800usb driver and should probably work. $ rpm -q kernel kernel-2.6.40.6-0.fc15.x86_64 $ modinfo rt2800usb filename: /lib/modules/2.6.40.6-0.fc15.x86_64/kernel/drivers/net/wireless/rt2x00/rt2800usb.ko license: GPL firmware: rt2870.bin description: Ralink RT2800 USB Wireless LAN driver. version: 2.3.0 author: http://rt2x00.serialmonkey.com srcversion: 7523926672C5248A4D4BF63 ... alias: usb:v050Dp825Ad*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp1003d*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp935Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp935Ad*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp825Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp815Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp805Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp8053d*dc*dsc*dp*ic*isc*ip* ... Here upstream commit that added 050d:935b to the kernel: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8d4ca61a10feea9583dc62ec1514722e99bdcd3d BTW, you can do modinfo even without loading the driver. > I noticed > that for the rt2870sta driver v050Dp815C is listed twice, is this a mistake > and should it be v050Dp935B? Yeah, looks like a typo. I don't know what the other ID should be. Contact author of rpmfusion's rt2870 package. Hi Jirka, I'll responed to your questions when I get home this evening. However, one thing to add is that I'm on the i686 (32 bit) kernel not x86_64 (64 bit). I don't know if that makes any difference in terms of support (I hope not). Because I definitely did not see the dongle listed when I did the modproble. Hi Jirka, Thx, for all the help. You mentioned that the dongle was supported in newer releases of the kernel so I just gave up and reinstalled but f16 instead. After the install it found the dongle on the first attempt and in fact I am updating this from the machine that couldn't get the network previously. Thx, Garfield... I'm glad it works for you now. closing the bug. |
Description of problem: It took me a few days to get to the point where I was able to finally get the OS to recognize my Belkin USB adapter (F6D4050 v2). Now I've spent most of today trying to get my computer to associate with the AP. Ive downloaded and installed the latest version of NetworkManager, however, it still refuses to associate because it reports that the association is taking too long. I've been browsing the web and have found a few issues that seem similar, however, they have been reported to have been fixed in earlier versions of the OS. Could someone please tell me what is wrong? Also, just to add, we have 4 laptops (3 Windows, 1 Fedora 15), 3 game console, 5 hand held game console and a Blue-ray player that all link to the same AP wirelessly so I know the AP is configured properly and is in working order. So this is not an issue with the AP or it's setting. Also, if I take the same USB device and plug it into my Windows laptop it operates perfectly fine. Version-Release number of selected component (if applicable): [root@bishop ~]$ rpm -qa | grep NetworkManager NetworkManager-openconnect-0.8.999-1.fc15.i686 NetworkManager-glib-0.9.1.90-3.git20110927.fc15.i686 NetworkManager-pptp-0.8.999-1.fc15.i686 NetworkManager-gnome-0.9.1.90-3.git20110927.fc15.i686 NetworkManager-openvpn-0.8.999-1.fc15.i686 NetworkManager-gtk-0.9.1.90-3.git20110927.fc15.i686 evolution-NetworkManager-3.0.1-1.fc15.i686 NetworkManager-0.9.1.90-3.git20110927.fc15.i686 NetworkManager-vpnc-0.8.999-2.fc15.i686 How reproducible: As I mentioned above I have not been able to get this to work. Steps to Reproduce: 1. Use NetworkManager to connect to my AP 2. 3. Actual results: /var/log/wpa_supplicant.log: Trying to associate with SSID 'FREEBIRD' Trying to associate with SSID 'FREEBIRD' Trying to associate with SSID 'FREEBIRD' /var/log/messages: Nov 6 01:37:07 bishop NetworkManager[693]: <info> Activation (ra0) starting connection 'Wireless connection 1' Nov 6 01:37:07 bishop NetworkManager[693]: <info> (ra0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Nov 6 01:37:07 bishop NetworkManager[693]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled... Nov 6 01:37:07 bishop NetworkManager[693]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) started... Nov 6 01:37:07 bishop NetworkManager[693]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) scheduled... Nov 6 01:37:07 bishop NetworkManager[693]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) complete. Nov 6 01:37:07 bishop NetworkManager[693]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) starting... Nov 6 01:37:07 bishop NetworkManager[693]: <info> (ra0): device state change: prepare -> config (reason 'none') [40 50 0] Nov 6 01:37:07 bishop NetworkManager[693]: <info> Activation (ra0/wireless): connection 'Wireless connection 1' has security, and secrets exist. No new secrets needed. Nov 6 01:37:07 bishop NetworkManager[693]: <info> Config: added 'ssid' value 'FREEBIRD' Nov 6 01:37:07 bishop NetworkManager[693]: <info> Config: added 'scan_ssid' value '1' Nov 6 01:37:07 bishop NetworkManager[693]: <info> Config: added 'key_mgmt' value 'NONE' Nov 6 01:37:07 bishop NetworkManager[693]: <info> Config: added 'auth_alg' value 'OPEN' Nov 6 01:37:07 bishop NetworkManager[693]: <info> Config: added 'wep_key0' value '<omitted>' Nov 6 01:37:07 bishop NetworkManager[693]: <info> Config: added 'wep_tx_keyidx' value '0' Nov 6 01:37:07 bishop NetworkManager[693]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) complete. Nov 6 01:37:07 bishop NetworkManager[693]: <info> Config: set interface ap_scan to 2 Nov 6 01:37:07 bishop lldpad[883]: vdp_ifup:ra0 vdp data already exists ! Nov 6 01:37:07 bishop kernel: [ 3510.337395] IOCTL::unknown IOCTL's cmd = 0x000089f0 Nov 6 01:37:07 bishop kernel: [ 3510.337661] IOCTL::unknown IOCTL's cmd = 0x00008994 Nov 6 01:37:07 bishop NetworkManager[693]: <info> (ra0): supplicant interface state: inactive -> associating Nov 6 01:37:21 bishop kernel: [ 3524.286760] IOCTL::unknown IOCTL's cmd = 0x000089f0 Nov 6 01:37:21 bishop lldpad[883]: vdp_ifup:ra0 vdp data already exists ! Nov 6 01:37:21 bishop kernel: [ 3524.288385] IOCTL::unknown IOCTL's cmd = 0x00008994 Nov 6 01:37:32 bishop NetworkManager[693]: <warn> Activation (ra0/wireless): association took too long. Nov 6 01:37:32 bishop NetworkManager[693]: <info> (ra0): device state change: config -> need-auth (reason 'none') [50 60 0] Nov 6 01:37:32 bishop NetworkManager[693]: <warn> Activation (ra0/wireless): asking for new secrets Nov 6 01:37:32 bishop kernel: [ 3536.028843] IOCTL::unknown IOCTL's cmd = 0x000089f0 Nov 6 01:37:32 bishop kernel: [ 3536.029208] IOCTL::unknown IOCTL's cmd = 0x00008994 Nov 6 01:37:32 bishop lldpad[883]: vdp_ifup:ra0 vdp data already exists ! Nov 6 01:37:32 bishop NetworkManager[693]: <info> (ra0): supplicant interface state: associating -> disconnected Nov 6 01:37:32 bishop NetworkManager[693]: <warn> Couldn't disconnect supplicant interface: This interface is not connected. Nov 6 01:37:46 bishop lldpad[883]: vdp_ifup:ra0 vdp data already exists ! Nov 6 01:37:46 bishop kernel: [ 3549.310224] IOCTL::unknown IOCTL's cmd = 0x000089f0 Nov 6 01:37:46 bishop kernel: [ 3549.310481] IOCTL::unknown IOCTL's cmd = 0x00008994 Nov 6 01:38:37 bishop NetworkManager[693]: <warn> No agents were available for this request. Nov 6 01:38:37 bishop NetworkManager[693]: <info> (ra0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7] Nov 6 01:38:37 bishop NetworkManager[693]: <warn> Activation (ra0) failed for access point (FREEBIRD) Nov 6 01:38:37 bishop NetworkManager[693]: <info> Marking connection 'Wireless connection 1' invalid. Nov 6 01:38:37 bishop NetworkManager[693]: <warn> Activation (ra0) failed. Nov 6 01:38:37 bishop NetworkManager[693]: <info> (ra0): device state change: failed -> disconnected (reason 'none') [120 30 0] Nov 6 01:38:37 bishop NetworkManager[693]: <info> (ra0): deactivating device (reason 'none') [0] Nov 6 01:38:37 bishop avahi-daemon[686]: Withdrawing address record for fe80::9644:52ff:fe44:702e on ra0. Nov 6 01:38:37 bishop NetworkManager[693]: <warn> (ra0): failed to change interface MAC address Nov 6 01:38:37 bishop NetworkManager[693]: <warn> (ra0): failed to reset MAC address to 00:00:00:00:00:00 Nov 6 01:38:37 bishop kernel: [ 3600.535537] # Nov 6 01:38:37 bishop kernel: [ 3600.659082] # Nov 6 01:38:37 bishop kernel: [ 3600.963434] -->RTUSBVenderReset Nov 6 01:38:37 bishop kernel: [ 3600.963558] <--RTUSBVenderReset Nov 6 01:38:38 bishop kernel: [ 3601.518174] CfgSetCountryRegion():CountryRegion in eeprom was programmed Nov 6 01:38:38 bishop kernel: [ 3601.518194] CfgSetCountryRegion():CountryRegion in eeprom was programmed Nov 6 01:38:38 bishop kernel: [ 3601.518606] Key1Str is Invalid key length(0) or Type(0) Nov 6 01:38:38 bishop kernel: [ 3601.518640] Key2Str is Invalid key length(0) or Type(0) Nov 6 01:38:38 bishop kernel: [ 3601.518673] Key3Str is Invalid key length(0) or Type(0) Nov 6 01:38:38 bishop kernel: [ 3601.518707] Key4Str is Invalid key length(0) or Type(0) Nov 6 01:38:38 bishop kernel: [ 3601.520937] 1. Phy Mode = 5 Nov 6 01:38:38 bishop kernel: [ 3601.520944] 2. Phy Mode = 5 Nov 6 01:38:38 bishop kernel: [ 3601.554147] ERROR!!! E2PROM: WRONG VERSION 0xff, should be 1 Nov 6 01:38:38 bishop kernel: [ 3601.558122] phy mode> Error! The chip does not support 5G band 1! Nov 6 01:38:38 bishop kernel: [ 3601.558357] RTMPSetPhyMode: channel is out of range, use first channel=1 Nov 6 01:38:38 bishop kernel: [ 3601.576815] 3. Phy Mode = 9 Nov 6 01:38:38 bishop kernel: [ 3601.594101] MCS Set = ff 00 00 00 01 Nov 6 01:38:38 bishop kernel: [ 3601.604922] <==== rt28xx_init, Status=0 Nov 6 01:38:38 bishop kernel: [ 3601.624845] 0x1300 = 00064300 Nov 6 01:38:38 bishop kernel: [ 3601.629881] IOCTL::unknown IOCTL's cmd = 0x000089f0 Nov 6 01:38:38 bishop lldpad[883]: evb_ifdown:port ra0 remove failed Nov 6 01:38:38 bishop kernel: [ 3601.632245] IOCTL::unknown IOCTL's cmd = 0x00008994 Nov 6 01:38:38 bishop lldpad[883]: vdp_ifdown:ra0 vdp data remove failed Nov 6 01:38:38 bishop kernel: [ 3601.649603] IOCTL::unknown IOCTL's cmd = 0x000089f0 Nov 6 01:38:38 bishop kernel: [ 3601.661195] IOCTL::unknown IOCTL's cmd = 0x00008994 Nov 6 01:38:40 bishop avahi-daemon[686]: Registering new address record for fe80::9644:52ff:fe44:702e on ra0.*. Nov 6 01:38:42 bishop kernel: [ 3606.112224] # Nov 6 01:38:49 bishop kernel: [ 3612.752456] # Nov 6 01:38:52 bishop kernel: [ 3615.374575] IOCTL::unknown IOCTL's cmd = 0x000089f0 Nov 6 01:38:52 bishop kernel: [ 3615.374964] IOCTL::unknown IOCTL's cmd = 0x00008994 Nov 6 01:38:52 bishop lldpad[883]: vdp_ifup:ra0 vdp data already exists ! Expected results: Obviously I expect this to work!!!!! :-) Additional info: ifconfig output: [root@bishop ~]$ ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:132 errors:0 dropped:0 overruns:0 frame:0 TX packets:132 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9320 (9.1 KiB) TX bytes:9320 (9.1 KiB) p5p1 Link encap:Ethernet HWaddr 00:80:C6:F2:A0:40 inet6 addr: fe80::280:c6ff:fef2:a040/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:128 dropped:0 overruns:0 carrier:128 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:21 Base address:0xc000 ra0 Link encap:Ethernet HWaddr 94:44:52:44:70:2E inet6 addr: fe80::9644:52ff:fe44:702e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10474 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:834536 (814.9 KiB) iwconfig output: [root@bishop log]# iwconfig lo no wireless extensions. p5p1 no wireless extensions. ra0 Ralink STA ESSID:"11n-AP" Nickname:"RT2870STA" Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated Bit Rate:1 Mb/s RTS thr:off Fragment thr:off Encryption key:off Link Quality=70/100 Signal level:0 dBm Noise level:0 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0