You are not logged in.
I've been successfully using knetworkmanager for a couple of weeks. However, I once needed to connect to a wireless network that used WEP key. Unfortunately it was too difficult for knetworkmanager, it just did not want to connect to it, so I disabled it and used iwconfig. Everything worked fine but after a couple of days I returned to my old network (which used WPA encryption). Unfortuanetly the option "Enable wireless" in knetworkmanager became grayed-out, I just couldn't click it.
Here are some outputs from the console:
$ iwconfig
wlan0 IEEE 802.11bg Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no$ ifconfig
wlan0 Link encap:Ethernet HWaddr 00:15:AF:2D:8E:D7
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)$ lspci
...
01:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)$ iwlist scan
wlan0 Scan completed :
Cell 01 - Address: 00:27:19:...
/some more information about three available networks/
.../etc/rc.conf:
DAEMONS=(syslog-ng network netfs crond alsa dbus hal crond knetworkmanager kdm)It seems that there's nothing wrong with my card, I can connect to the wireless network that uses WEP cryptography. But the "Enable wireless" button remains grayed-out. I tried killing knetworkmanager and restarting it, but it didn't help.
Last edited by Jajo (2010-07-06 17:17:13)
Offline
even i have same problem....
Offline
Kind of a copout solution. But I have had nothing but problems with networkmanager in the past. I found WICD and love it. What I found works even better is the ncurses interface. The GUI can be a little slow. I just add this to my menu list...
terminator -e wicd-curses
or
xterm -e wicd-curses
Basically it is a front-end for all the stranded tools like ifconfig, dhcpcd, iwconfig, iwlist, and stuff that is way it works so well.
Last edited by hunterthomson (2010-07-11 10:32:03)
OpenBSD-current Thinkpad X230, i7-3520M, 16GB CL9 Kingston, Samsung 830 256GB
Contributor: linux-grsec
Offline
Same thing happened on one of my laptops... couldn't hit the soft key on the laptop to enable wifi which I think was the problem.
Offline
Owe ya, always check that hardware switch... Reminds me of the Kill Switch on my motorcycle giving me a scare ![]()
OpenBSD-current Thinkpad X230, i7-3520M, 16GB CL9 Kingston, Samsung 830 256GB
Contributor: linux-grsec
Offline
Kind of a copout solution. But I have had nothing but problems with networkmanager in the past. I found WICD and love it. What I found works even better is the ncurses interface. The GUI can be a little slow. I just add this to my menu list...
terminator -e wicd-curses
or
xterm -e wicd-cursesBasically it is a front-end for all the stranded tools like ifconfig, dhcpcd, iwconfig, iwlist, and stuff that is way it works so well.
It's terrific
. Although the "GUI" is quite... minimalistic
, it works perfectly. Unfortunately knetworkmanager still doesn't work, I have no idea what's going on. The hardware switch is on.
Offline
Right on, I'm glad you like it. Ya, it is minimalistic but that is why it works. It will save you from a bunch of problems in the future too because, Networkmanager causes problems with some pentesing tools and wireless drivers as well.
Also, lets say xorg will not start. You can use wicd-curses and still connect to WPA2 WiFi easy as pie.
Last edited by hunterthomson (2010-07-19 05:45:58)
OpenBSD-current Thinkpad X230, i7-3520M, 16GB CL9 Kingston, Samsung 830 256GB
Contributor: linux-grsec
Offline
try this:
/etc/rc.d/networkmanager stop
rm /var/lib/NetworkManager/NetworkManager.state
/etc/rc.d/networkmanager startyou can also try editing the networkmanager.state file.
Offline