You are not logged in.
Pages: 1
Hi all,
When Waldorf has finished booting, about half of the available wireless networks in NM (including mine) are greyed out. Not a problem I have had at all with stable.
Anyone any ideas?
Thanks.
Offline
^ If you want a quick fix, please post a link to this thread, in the Stable support section - xaos52 will surely be able to help you and others with similar problems.
Offline
I had the same problem with my old thinkpad.
lspci | grep net -i
02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
02:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (MOB) Ethernet Controller (rev 81)I was able to connect by manually entering my wireless details in "Edit Connections..." -> "Wireless" -> "Add"
It works just fine although it shows no signal strengh.
Offline
Thanks for that, I can create a new connection but still won't connect - will continue the fight.
Offline
You can try starting nm-applet with sudo:
Alt-f3 -> gksudo -> nm-applet
Offline
I have a Dell Latitude D810 that has the same problem. Wireless connections are all detected (nm-applet), strength is good but they are all greyed out The first time I could work around by manualy add the network but on restart, that does not appear to help any more.
Offline
I guess it is because the new version of network-manager that comes with Waldorf stores its 'user connections' in a different way than the previous version in Statler.
Solution should be to start nm-applet with sudo, remove existing connections and recreate them.
You can choose between saving as a 'user' connection or a 'system' connection by ticking the 'allow for all users' box.
You should have to do this only once. Thereafter you can use the normal - without sudo - invocation of nm-applet.
bootinfoscript - emacs primer - I ♥ #!
Offline
Thanks xaos, I'll try this out.
Offline
I guess it is because the new version of network-manager that comes with Waldorf stores its 'user connections' in a different way than the previous version in Statler.
Solution should be to start nm-applet with sudo, remove existing connections and recreate them.
You can choose between saving as a 'user' connection or a 'system' connection by ticking the 'allow for all users' box.You should have to do this only once. Thereafter you can use the normal - without sudo - invocation of nm-applet.
Tried the above, ran sudo nm-applet in a terminal. Got a second nm-applet that looked and behaved exactly the same as the first. Also a whole string of messages like this:
"(nm-applet:2043): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:632:20: Unknown pseudo-class 'backdrop' " the numbers changed but message stayed the same.
Offline
My bad. I do not use network-manager and it seems my memory is flakey. Try this:
Stop the running nm-applet with
pkill nm-appletNow run
sudo nm-connection-editorDelete the old connections.
Stop nm-connection-editor
Start nm-applet as your normal user:
nm-applet &PS: If that does not work, Try again, but create the new connection while in nm-connection-editor.
Last edited by xaos52 (2012-05-08 08:11:24)
bootinfoscript - emacs primer - I ♥ #!
Offline
Pages: 1
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.