Bug 439236 - rt2x00 does not establish wireless connection.
Summary: rt2x00 does not establish wireless connection.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-27 17:12 UTC by Daniel Senderowicz
Modified: 2008-07-29 03:13 UTC (History)
1 user (show)

Fixed In Version: 2.6.25.10-47.fc8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-28 17:56:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
outputs of different commands. (82.24 KB, application/octet-stream)
2008-05-01 19:58 UTC, Daniel Senderowicz
no flags Details

Description Daniel Senderowicz 2008-03-27 17:12:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)

Description of problem:
I have a PCI wireless card RaLink RT2600 802.1. With kernels newer than 2.6.23.15-137 it does not connect at all. It connects OK with that kernel. However, even with 2.6.23.15-137 it won't use the static address of the machine properly setup, it will always go the DHCP to get an IP number.

Version-Release number of selected component (if applicable):
subsequent to kernel-2.6.23.15-137

How reproducible:
Always


Steps to Reproduce:
1. After reboot, just check connection with the Network Manager and it says something like "Wireless Network Disconnected"
2.
3.

Actual Results:
No wireless connection.

Expected Results:
It should have established a connection to the present wireless network.

Additional info:

Comment 1 John W. Linville 2008-03-28 13:26:37 UTC
What is the latest kernel you have tried?

Comment 2 Daniel Senderowicz 2008-03-28 16:29:34 UTC
The latest I've tried was 2.6.24.3-50.

Comment 3 John W. Linville 2008-04-08 19:49:52 UTC
Please try 2.6.24.4-69.fc8 -- many rt2x00 users have reported success with it:

   http://koji.fedoraproject.org/koji/buildinfo?buildID=44648

Does that help?

Comment 4 Daniel Senderowicz 2008-04-21 21:51:51 UTC
No, it's still deaf and mute. The worst part is that when I installed that
kernel, it erased the one that was working, so I have to figure out how to get
it back.

Comment 5 John W. Linville 2008-04-22 17:12:35 UTC
Please attach the contents of /var/log/messages after a failed connection.  
Also attach the output of running 'iwconfig' and 'lspci -n'...thanks!

Comment 6 Daniel Senderowicz 2008-05-01 19:58:50 UTC
Created attachment 304342 [details]
outputs of different commands.

Comment 7 John W. Linville 2008-07-08 20:06:59 UTC
Do you continue to experience problems with current kernels?

Comment 8 Daniel Senderowicz 2008-07-08 21:58:28 UTC
The latest kernel I downloaded was 2.6.25.9-40 and is still deaf and mute. The
one that works is the old 2.6.23.15-137 . As a reminder, even with the latter,
the IP is not what I set, it always goes to auto (dhcp). Thanks,

Dan

Comment 9 Daniel Senderowicz 2008-07-19 21:23:46 UTC
Last night I updated the system, that included 2.6.25.10-47.fc8. Now it is able
to talk and hear through the wireless card. However the other problem still
remains. It assigns a random IP number, ala DHCP, although I have the LAN
configured as a fixed IP number. Or there is something else that keeps the
system from using the IP I gave it?

Cheers,

Daniel

Comment 10 John W. Linville 2008-07-28 17:56:35 UTC
It sounds like either you are enabling NetworkManager or have not properly
configured the network in system-config-network.  In either case, this does not
sound like a kernel issue any longer.  I'm going to close this one -- you should
open a new bug if system-config-network is not working properly...thanks!

Comment 11 Daniel Senderowicz 2008-07-29 03:13:46 UTC
Hi John,

Yes, that was the problem. I just stopped Network Manager and it gives the right
IP. Thanks for all your help.

Cheers,

Daniel


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