Re: iwconfig and interesting problem
But When i use this key in network-manager's interface i can connect to the internet. On Thu, 2010-08-05 at 16:53 -0500, Dan Williams wrote: On Thu, 2010-08-05 at 09:19 +0430, Mohsen Pahlevanzadeh wrote: Dear all When i use by hand iwconfig , i get following error: debian:/home/mohsen# iwconfig wlan0 essid mohsen key s:googooli Your key is wrong here; you're attempting to use a WEP ASCII key, and those *must* be either 5 or 13 characters long. Yours is 8 and thus is not a valid WEP ASCII key. Dan Error for wireless request Set Encode (8B2A) : SET failed on device wlan0 ; Invalid argument. debian:/home/mohsen# But i have a question: How networkmanager can connect to access poin? if possible tell me that i can try and connect.because networkmanagers's parameter that it involved can help me. Yours, Mohsen ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
BCM4312/b43 acts weird with NetworkManager and F13
Hi, I'm running Fedora 13 with NetworkManager-0.8.1-1 and a 2.6.34 kernel from koji. My system has a BCM4312 wifi chip which I'm using with the b43 module and the proprietary firmware from Broadcom. NetworkManager is acting a bit weird with wifi. Every time I reboot the laptop, the wireless connection is disabled, meaning I have to right click on the nm-applet icon and choose Enable wireless. Based on /var/log/messages the firmware is loaded to the device at this point like this: NetworkManager[968]: info (wlan0): bringing up device. kernel: b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready dbus-daemon: [system] Rejected send message, 1 matched rules; type=method_return, sender=:1.1 (uid=0 pid=968 comm=NetworkManager) interface=(unset) member=(unset) error name=(unset) requested_reply=0 destination=:1.56 (uid=500 pid=1563 comm=nm-applet)) NetworkManager[968]: info (wlan0): supplicant interface state: starting - ready NetworkManager[968]: info (wlan0): device state change: 2 - 3 (reason 42) NetworkManager[968]: info Activation (wlan0) starting connection 'Auto network name here' etc. etc. With my previous laptop, which had an Intel wifi chip, the wireless network was always automatically enabled when I booted up the computer. I know the b43 drivers are still under development, but does anyone have an idea what could be going wrong? The dbus error does look a bit scary to me. -- Ville-Pekka Vainio ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: howto ignore rfkill switch
On 08/06/2010 12:51 AM, Dana Goyette wrote: My Samsung laptop's rfkill switch, on the other hand, is entirely software. If I unload the samsung-laptop module with the wifi card set to kill, the wifi card can at least receive. I'm not sure about sending, since r8192pci mostly fails. The staging drivers for the 8192 know nothing about the rfkill subsystem, thus this point is moot. Larry ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Modem gone after suspend/resume
Hello, a 3G modem is no longer recognized by modem-manager when the system resumes. It seems the USB identification changes upon resume, from usb6/6-1 to usb6/6-2. This might be caused by udev rules? I've collected some logs here on Launchpad: dmesg after resume: http://launchpadlibrarian.net/53157289/dmesg find in the sys directory after resume: http://launchpadlibrarian.net/53157295/find debug output for modemmanager: http://launchpadlibrarian.net/53157338/mm.log Any chance to get modem-manager/networkmanager to rescan the device tree to find the modem again? Torsten ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Modem gone after suspend/resume
On Friday 06 of August 2010 18:30:48 Torsten Spindler wrote: Hello, a 3G modem is no longer recognized by modem-manager when the system resumes. It seems the USB identification changes upon resume, from usb6/6-1 to usb6/6-2. This might be caused by udev rules? Nope, it did not change. Device usb6/6-2 existed also before suspend: [2.444051] usb 6-2: new full speed USB device using uhci_hcd and address 3 [2.636033] usb 6-2: configuration #1 chosen from 1 choice There is not enough information to know what it is, but I guess it is (built-in?) smart card reader, based on [ 4251.276912] usb 6-2: usbfs: process 1360 (pcscd) did not claim interface 0 before use Compare lsusb -v output before and after resume. As for your modem - it seems to have dropped off after resume: [ 4251.624038] usb 6-1: new full speed USB device using uhci_hcd and address 4 [ 4251.744422] usb 6-1: device descriptor read/64, error -71 [ 4251.968059] usb 6-1: device descriptor read/64, error -71 [ 4252.184088] usb 6-1: new full speed USB device using uhci_hcd and address 5 [ 4252.304068] usb 6-1: device descriptor read/64, error -71 [ 4252.528099] usb 6-1: device descriptor read/64, error -71 [ 4252.744095] usb 6-1: new full speed USB device using uhci_hcd and address 6 [ 4253.160115] usb 6-1: device not accepting address 6, error -71 [ 4253.272083] usb 6-1: new full speed USB device using uhci_hcd and address 7 [ 4253.688067] usb 6-1: device not accepting address 7, error -71 [ 4253.688104] hub 6-0:1.0: unable to enumerate USB device on port 1 I would start with checking that device alone (without any application) can survive suspend/resume cycle. Stop NM/MM to make sure nothing attempts to attach to device; plug in modem; verify that it is available using lsusb; now suspend/resume and check whether modem is still available. If not - this is kernel problem and NM cannot do anything about it. I've collected some logs here on Launchpad: dmesg after resume: http://launchpadlibrarian.net/53157289/dmesg find in the sys directory after resume: http://launchpadlibrarian.net/53157295/find debug output for modemmanager: http://launchpadlibrarian.net/53157338/mm.log Any chance to get modem-manager/networkmanager to rescan the device tree to find the modem again? Torsten ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list signature.asc Description: This is a digitally signed message part. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NEWS entries / Announcement mails
Hi everybody,
I know you're all busy coding and enhancing NM, which is a good thing per se.
Yet I would like to ask if anybody could once in a while spend some
time extending the NEWS file or create a Announcement mail when a new version
gets out?
I have, for a start, a rather hard time defining why an update from 0.8.0 to
0.8.1 should be a good thing to do (other than upstream released a new
version). For our packaging policy it is mandatory to outline the most
important changes between package versions.
I would appreciate if this could be considered (and maybe cought up for the
0.8.1 release of the various modules, NM, NM-{openvpn,pptp,vpnc} and the
gnome applet).
Thank you very much for your help!
Dominique
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: howto ignore rfkill switch
On 08/06/2010 07:10 AM, Larry Finger wrote: On 08/06/2010 12:51 AM, Dana Goyette wrote: My Samsung laptop's rfkill switch, on the other hand, is entirely software. If I unload the samsung-laptop module with the wifi card set to kill, the wifi card can at least receive. I'm not sure about sending, since r8192pci mostly fails. The staging drivers for the 8192 know nothing about the rfkill subsystem, thus this point is moot. Larry What I mean is that the 8192 driver fails in various ways even when not rfkilled -- but that's an entirely different issue. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NEWS entries / Announcement mails
On Fri, Aug 6, 2010 at 11:52, Dominique Leuenberger dominique.leuenber...@tmf-group.com wrote: Hi everybody, I know you're all busy coding and enhancing NM, which is a good thing per se. Yet I would like to ask if anybody could once in a while spend some time extending the NEWS file or create a Announcement mail when a new version gets out? Like this? http://blogs.gnome.org/dcbw/2010/08/02/determination-that-is-incorruptible/ ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NEWS entries / Announcement mails
On 08/06/2010 at 6:44 PM, Daenyth Blank daen...@gmail.com wrote: On Fri, Aug 6, 2010 at 11:52, Dominique Leuenberger dominique.leuenber...@tmf-group.com wrote: Hi everybody, I know you're all busy coding and enhancing NM, which is a good thing per se. Yet I would like to ask if anybody could once in a while spend some time extending the NEWS file or create a Announcement mail when a new version gets out? Like this? http://blogs.gnome.org/dcbw/2010/08/02/determination-that-is-incorruptible/ Thanks, exactly something like this :) Is there something similar to this for - NetworkManager-openvpn - NetworkManager-pptp - gnome-network-applet - NetworkManager-vpnc - ModemManager ? As those certainly did get some love to on the road to 0.8.1, but it's at best related to what NM itself received. Dominique ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NEWS entries / Announcement mails
On Fri, Aug 6, 2010 at 12:56, Dominique Leuenberger dominique.leuenber...@tmf-group.com wrote: On 08/06/2010 at 6:44 PM, Daenyth Blank daen...@gmail.com wrote: On Fri, Aug 6, 2010 at 11:52, Dominique Leuenberger dominique.leuenber...@tmf-group.com wrote: Hi everybody, I know you're all busy coding and enhancing NM, which is a good thing per se. Yet I would like to ask if anybody could once in a while spend some time extending the NEWS file or create a Announcement mail when a new version gets out? Like this? http://blogs.gnome.org/dcbw/2010/08/02/determination-that-is-incorruptible/ Thanks, exactly something like this :) Is there something similar to this for - NetworkManager-openvpn - NetworkManager-pptp - gnome-network-applet - NetworkManager-vpnc - ModemManager ? As those certainly did get some love to on the road to 0.8.1, but it's at best related to what NM itself received. Dominique That I don't know about. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
2010/8/6 Ville-Pekka Vainio vpiva...@cs.helsinki.fi Hi, I'm running Fedora 13 with NetworkManager-0.8.1-1 and a 2.6.34 kernel from koji. My system has a BCM4312 wifi chip which I'm using with the b43 module and the proprietary firmware from Broadcom. In Ubuntu, the native b43 module is broken, as the device is always disabled. We have to block it and use the bcmwl-kernel-source, which installs a wl driver that works. Maybe this works for you, too? NetworkManager is acting a bit weird with wifi. Every time I reboot the laptop, the wireless connection is disabled, meaning I have to right click on the nm-applet icon and choose Enable wireless. Based on /var/log/messages the firmware is loaded to the device at this point like this: NetworkManager[968]: info (wlan0): bringing up device. kernel: b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready dbus-daemon: [system] Rejected send message, 1 matched rules; type=method_return, sender=:1.1 (uid=0 pid=968 comm=NetworkManager) interface=(unset) member=(unset) error name=(unset) requested_reply=0 destination=:1.56 (uid=500 pid=1563 comm=nm-applet)) NetworkManager[968]: info (wlan0): supplicant interface state: starting - ready NetworkManager[968]: info (wlan0): device state change: 2 - 3 (reason 42) NetworkManager[968]: info Activation (wlan0) starting connection 'Auto network name here' etc. etc. With my previous laptop, which had an Intel wifi chip, the wireless network was always automatically enabled when I booted up the computer. I know the b43 drivers are still under development, but does anyone have an idea what could be going wrong? The dbus error does look a bit scary to me. -- Ville-Pekka Vainio ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Is Network Manager in 11.3 different from 11.2?
For many years I've used scpm to reconfigure my laptop by changing the nfs fstab file depending on what environment I was in. This year I understand scpm is no longer available in 11.3, and I've been told to use network manager. In 11.2, network manager, despite it's name couldn't manage networks, just connections. Has network manager changed so I can easily alter my nfs setup as I move my laptop from connection to connection? -- Robert Smits CEP525G Nanaimo, Duncan District Labour Council Box 822 Nanaimo, V9R 5N2 Ph 250-760-0547 Fax 250-760-0548 Email lab...@telus.net ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
Em 6 de agosto de 2010 15:43, Ville-Pekka Vainio vpiva...@cs.helsinki.fiescreveu: On Fri, 6 Aug 2010 15:32:27 -0300, José Queiroz wrote: In Ubuntu, the native b43 module is broken, as the device is always disabled. We have to block it and use the bcmwl-kernel-source, which installs a wl driver that works. Maybe this works for you, too? Thanks for the suggestion, but I'd rather not use closed source drivers as long as the open source ones work, at least to some degree. -- Ville-Pekka Vainio Won't you even give it a try? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
