LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   Rt2500 pci not working in Fedora 12 (https://www.linuxquestions.org/questions/linux-wireless-networking-41/rt2500-pci-not-working-in-fedora-12-a-802354/)

Rasmus 04-16-2010 04:37 AM

Rt2500 pci not working in Fedora 12
 
Code:

iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0    IEEE 802.11bg  ESSID:"******" 
          Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: CE:58:86:B2:A2:26 
          Tx-Power=20 dBm 
          Retry  long 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

Code:

02:01.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
The two points in the networkmanager in gnome turns green, but no connection...

It works on debian and ubuntu

nimnull22 04-16-2010 09:24 PM

Tell please, you can not connect to AP or you can not go to internet?

Rasmus 04-17-2010 02:55 AM

Quote:

Originally Posted by nimnull22 (Post 3938138)
Tell please, you can not connect to AP or you can not go to internet?

AP?

If I use the cable I can reach internet, but I need also wireless to be able to work in another part of the house.

I also tried it with wicd, but got a other problem with that
Code:

libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Could not initalize pynotify
Has notifications support False
Loading...
Connecting to daemon...
Can't connect to the daemon, trying to start it automatically...
Wicd daemon is shutting down!

** (wicd-client.py:1954): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

** (wicd-client.py:1954): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

** (wicd-client.py:1954): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
Done loading.


Rasmus 04-17-2010 05:57 AM

solved by installing wicd 1.6.2 from source


All times are GMT -5. The time now is 10:51 AM.