Bug 702187 - Can't connect my computer to internet with wi-fi integrated card
Summary: Can't connect my computer to internet with wi-fi integrated card
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 19
Hardware: i686
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-05 01:34 UTC by Gianluca
Modified: 2015-02-17 13:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 13:44:19 UTC
Type: ---


Attachments (Terms of Use)
Fedora 14 messages file (91.57 KB, application/octet-stream)
2011-05-06 13:31 UTC, Gianluca
no flags Details
Fedora 14 wpa supplicant (738 bytes, application/octet-stream)
2011-05-06 13:32 UTC, Gianluca
no flags Details
Fedora 15BETA messages file (160.03 KB, application/octet-stream)
2011-05-06 13:33 UTC, Gianluca
no flags Details
Fedora 15BETA wpa supplicant file (2.08 KB, application/octet-stream)
2011-05-06 13:34 UTC, Gianluca
no flags Details

Description Gianluca 2011-05-05 01:34:47 UTC
Description of problem:When using Fedora 14 & 15BETA I cannot connect to the internet my computer using wi-fi connection in the Network Manager standard tool. I have this integrated wi-fi card: Intel 82566DC-2 Gigabit Network Connection


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:I cannot connect my computer to the internet using wi-fi on the Network Manager Fedora desktop i686 integrated tool


Expected results:after install new Fedora 15 and future versions the internet connection must work smoothly and quickly without problems


Additional info:in previous Fedora versions everything worked out for the best. On terminal with the command # lsusb the result is: "Bus 001 Device 002: ID 15a9:0004 Gemtek WUBR177G".
I have an assembled HP PC

Comment 1 Jirka Klimes 2011-05-05 08:41:04 UTC
Please attach following info:
1. nm-tool output
2. /var/log/messages file
3. (ifconfig wlan0 up)
   iwlist wlan0 scan
4. do you see any errors in dmesg?
5. rpm -q kernel
6. rpm -q rt73usb-firmware

Comment 2 Gianluca 2011-05-05 11:31:28 UTC
1. $ nm-tool output

NetworkManager Tool

State: disconnected

- Device: eth0 -----------------------------------------------------------------
  Type:              Wired
  Driver:            e1000e
  State:             unavailable
  Default:           no
  HW Address:        00:1D:60:C1:14:91

  Capabilities:
    Carrier Detect:  yes

  Wired Properties
    Carrier:         off


- Device: wlan0 ----------------------------------------------------------------
  Type:              802.11 WiFi
  Driver:            rt73usb
  State:             disconnected
  Default:           no
  HW Address:        00:16:44:1F:56:0C

  Capabilities:

  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points 
    tele2_00238EE52E6A: Infra, 00:23:8E:E5:2E:6A, Freq 2437 MHz, Rate 54 Mb/s, Strength 20 WPA
    USR9111:         Infra, 00:14:C1:2E:5C:9B, Freq 2437 MHz, Rate 54 Mb/s, Strength 77 WPA WPA2

2. /var/log/messages file  -  I don't know

3. ifconfig wlan0 up


wlan0     Link encap:Ethernet  HWaddr 00:16:44:1F:56:0C  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

$ iwlist wlan0 scanning

wlan0     Scan completed :
          Cell 01 - Address: 00:14:C1:2E:5C:9B
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=54/70  Signal level=-56 dBm  
                    Encryption key:on
                    ESSID:"USR9111"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000002bea0994f0a
                    Extra: Last beacon: 9475ms ago
                    IE: Unknown: 000755535239313131
                    IE: Unknown: 010582848B962C
                    IE: Unknown: 030106
                    IE: Unknown: 2A0100
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                       Preauthentication Supported
                    IE: Unknown: 32080C1218243048606C
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00

4. I don't see errors in dmesg. At one point I saw this:
[   61.729217] ADDRCONF(NETDEV_UP): wlan0: link is not ready

5. rpm -q kernel   
[liveuser@localhost ~]$ rpm -q kernel
kernel-2.6.35.6-45.fc14.i686

6. rpm -q rt73usb-firmware-

[liveuser@localhost ~]$ rpm -q rt73usb-firmware-
rt73usb-firmware-1.8-7.fc13.noarch

Comment 3 Jirka Klimes 2011-05-06 06:58:53 UTC
Thanks for the data.
I had thought that you could have a problem with firmware, but according to the logs, the firmware is present and NetworkManager can see WiFi networks: tele2_00238EE52E6A and USR9111.

So we really need /var/log/messages file to see what NetworkManager is doing. You have to navigate to /var/log directory (using a terminal or some file manager) and attach 'messages' file to this report. You have to be root because the file is protected.
/var/log/wpa_supplicant.log would also be valuable.

Can you tell us what (desktop) environment and tools do you use to activate your wireless connection?

Comment 4 Gianluca 2011-05-06 13:31:54 UTC
Created attachment 497350 [details]
Fedora 14 messages file

Comment 5 Gianluca 2011-05-06 13:32:52 UTC
Created attachment 497351 [details]
Fedora 14 wpa supplicant

Comment 6 Gianluca 2011-05-06 13:33:31 UTC
Created attachment 497353 [details]
Fedora 15BETA messages file

Comment 7 Gianluca 2011-05-06 13:34:09 UTC
Created attachment 497354 [details]
Fedora 15BETA wpa supplicant file

Comment 8 Gianluca 2011-05-06 13:35:12 UTC
Hi, yes I can see WiFi networks, my router is USR9111 (US.Robotics router 802.11g with WPA2-PSK password) yesterday I've tried also without WPA password but the problem still exist the same way.
I'm trying to test the problem both in Fedora 14 live CD Desktop and Fedora 15 Beta live CD desktop, I can use only Wi-fi connection in my house, no cable and no other methods that's why my problem is urgent. 
Here are the systems specs:


FEDORA 14  Kernel Linux 2.6.35.6-45.fc14.i686
GNOME 2.32.0
Applet NetworkManager 0.8.1

FEDORA 15BETA  Kernel Linux 2.6.38.2-9.fc15.i686
GNOME 2.91.93
NetworkManager found in the CD

I've attached both Fedora14 and Fedora15BETA messages files and both wpa_supplicant.log files

The last test in Fedora 14 = no connection as always
The last test in Fedora15BETA = first time I've tried: no connection; then I've tried again and (for the FIRST and LAST time) it worked and connected well, I don't know why. Then I saved the messages files I'm sending, I hope you can see that.

Comment 9 Jirka Klimes 2011-05-09 08:42:10 UTC
The WiFi card successfully associates with the router. But, what appears to be a problem is obtaining IP address. It looks like you don't run DHCP server on your router or it's misconfigured. Please check that.
In case you don't want to use DHCP, you have to edit 'Auto USR9111' connection to use static IP address. You can do that through nm-connection-editor, where you change method from 'Automatic (DHCP)' to 'Manual' and set a IP (on 'IPv4 Settings' tab).

Comment 10 Gianluca 2011-05-09 10:54:29 UTC
Hi, this seem very strange because in Windows7 with the same router settings all works! And in past Fedora's versions all was right!
I've checked my router's settings and status, I use non-static IP and DHCP is configurated the right way.

Comment 11 Jirka Klimes 2011-05-09 13:35:29 UTC
It seems there is an issue with rt73usb driver.

Please try reload the driver with nohwcrypt option:
# rmmod rt73usb
# modprobe rt73usb nohwcrypt=1

Links:
http://comments.gmane.org/gmane.linux.kernel.wireless.general/62651
http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2011-May/003749.html
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/777784

Comment 12 Gianluca 2011-05-10 00:53:53 UTC
Hello, I've tried to reload the driver with your terminal lines but nothing happened, only 2sec loading when press enter on the second line but wi-fi didn't connect again.

Comment 13 Gianluca 2011-05-22 23:40:51 UTC
Hello, I've tried to reload the driver with nohwcrypt option:
# rmmod rt73usb
# modprobe rt73usb nohwcrypt=1

but again wi-fi connection doesn't seems to work! Is there another solution?
Maybe in the next Fedora 15 release all will work the right way?

Comment 14 Fedora End Of Life 2013-04-03 14:22:25 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 15 Fedora End Of Life 2015-01-09 16:39:20 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 16 Fedora End Of Life 2015-02-17 13:44:19 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.