| Summary: | Cannot connect to Wi-Fi network | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Matt C <mattwigway> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | dcbw, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, matthias |
| 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: | 2012-07-11 17:49:48 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
When this happens, run "dmesg" in a terminal and see if you get any messages from the ipw2200 driver about "failed to send command: already sending command" or something like that. If so, it's a duplicate of bug 802106 and bug 738508. Fedora 15 has reached it's end of life as of June 26, 2012. As a result, we will not be fixing any remaining bugs found in Fedora 15. In the event that you have upgraded to a newer release and the bug you reported is still present, please reopen the bug and set the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. Thank you for taking the time to file a report. We hope newer versions of Fedora suit your needs. |
Description of problem: I have a Toshiba Tecra M2 with an ipw2200 wireless chipset (Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)). When I try to connect to a wireless network (I've tried both WEP and open networks), it continually asks for the key on a secured network, and simply never connects to an unsecured network. The first green orb in the NetworkManager applet lights, but the second never does. dmesg reports: ipw2200: Failed to send SCAN_ABORT: Command timed out. ADDRCONF(NETDEV_UP): eth1: link is not ready. ipw2200: Failed to send CARD_DISABLE: Command timed out. eth1 IEEE 802.11bg ESSID:"BlueHole" Mode:Managed Frequency:2.442 GHz Access Point: 00:09:5B:46:17:B6 Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ifconfig: eth1 Link encap:Ethernet HWaddr 00:0E:35:E8:9E:7F UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:240 (240.0 b) Interrupt:11 Base address:0xc000 Memory:fceff000-fcefffff As you can see, it has initiated network handshaking (it's found the network and moved to the correct channel), but it hasn't been assigned an IP address, &c. I do see an accurate list of available networks in the menu. I had the same problem on F14, and fixed it by downgrading to version 3.0 of the firmware (from the shipped 3.1), but that didn't solve the problem on F15. Version-Release number of selected component (if applicable): 3.1-5 How reproducible: Every time. Steps to Reproduce: 1. Select a network from the dropdown menu. 2. Enter the key (if applicable). 3. Note that it never finishes connecting. Actual results: No connection; possible continued prompting for key (if connecting to a secured network). Expected results: A network connection. Additional info: