Red Hat Bugzilla – Bug 439236
rt2x00 does not establish wireless connection.
Last modified: 2008-07-28 23:13:46 EDT
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 126.96.36.199-137 it does not connect at all. It connects OK with that kernel. However, even with 188.8.131.52-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-184.108.40.206-137
Steps to Reproduce:
1. After reboot, just check connection with the Network Manager and it says something like "Wireless Network Disconnected"
No wireless connection.
It should have established a connection to the present wireless network.
What is the latest kernel you have tried?
The latest I've tried was 220.127.116.11-50.
Please try 18.104.22.168-69.fc8 -- many rt2x00 users have reported success with it:
Does that help?
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
Please attach the contents of /var/log/messages after a failed connection.
Also attach the output of running 'iwconfig' and 'lspci -n'...thanks!
Created attachment 304342 [details]
outputs of different commands.
Do you continue to experience problems with current kernels?
The latest kernel I downloaded was 22.214.171.124-40 and is still deaf and mute. The
one that works is the old 126.96.36.199-137 . As a reminder, even with the latter,
the IP is not what I set, it always goes to auto (dhcp). Thanks,
Last night I updated the system, that included 188.8.131.52-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?
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!
Yes, that was the problem. I just stopped Network Manager and it gives the right
IP. Thanks for all your help.