Red Hat Bugzilla – Bug 238632
rt2500pci wireless card see as an ethernet card
Last modified: 2007-12-21 13:11:27 EST
Description of problem:
my rt2500pci wireless card is viewed as an ethernet card in test4 live cd so i
can't use it to associate.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
what is the output of:
Maybe a firmware is missing to put that card operational?
This device works fine without any firmware. It works fine with networkmanager.
My problem is as my system is a desktop i don't want to use networkmanager and i
want to configure the network definitely using system-config-network. I will
post the output of iwconfig when i'll be back at home
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
Warning: Driver for device wlan0 has been compiled with version 22
of Wireless Extension, while this program supports up to version 20.
Some things may be broken...
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Retry min limit:7 RTS thr:off Fragment thr=2346 B
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
But only eth0 and wmaster0 are seen in system-config-network
this problem seems to be solved using livecd RC2 (ie kernel 2.6.21-1.3194.fc7)
Now the wireless card is viewed in system-config-network and i achieve to put it
up but the network don't work. When i ping router : host unreachable.
If i use network manager the network work like a charm
I've seen similar issues with the rt2500pci driver. My network
has a Linksys access point & uses a 128 bit WEP key. The network
does not reliably start up using ifup. (I haven't been using
NetworkManager on that workstation.) When it does come up, the
data rate is very low (~30 kib/s). Even when the interface is
up, and appears to be working from the workstation's desktop,
remote access is intermittent. HTTP and SSH connections ofter
only succeed for a short period (minutes to hours) after the
connection is raised, and then later timeout. Outbound connections
often still work, and previously opened SSH connections from the
outside often stay up. I haven't seen any correlations in this
behavior with dmesg output. (Unfortunately, I'm not at the
workstation right now and SSH is not connecting. I can provide
further diagnostic information later if requested.)
For me this is solved. Could we close the bug ?