Re: feedback on attempting to build network-manager from Subversion
Dan Williams wrote: On Tue, 2007-03-13 at 20:48 -0400, Mark Stosberg wrote: I tried to build NetworkManager from SVN tonight, to see if the latest version fixed this bug already: http://bugzilla.gnome.org/show_bug.cgi?id=418065 From this ChangeLog entry, it appears that might be fixed: ## * src/nm-device-802-11-wireless.c: Fix wireless device scanning scheduler. The new algorithm is to start from SCAN_INTERVAL_MIN (currently defined as 0) and add a SCAN_INTERVAL_STEP (currently 20 seconds) with each successful scan until SCAN_INTERVAL_MAX (currently 120 seconds) is reached. Do not scan while the device is down, activating, or activated (in case of A/B/G cards).Remove some old dead ifdef'ed out code that used to configure wireless devices, it's all done through supplicant now. ## Likely not. The old 0.6.5 code followed approximately the same algorithm. I suspect driver issues; if the driver is dropping association during a scan, then the driver needs to get fixed. An easy way to test this is to set up a plain wpa_supplicant association, and then do successive 'iwlist eth0 scan' events every 5 or 7 seconds and see if wpa_supplicant gets a disconnect event from the driver. Ok. In my case I think I'm using the madwifi driver, and can try madwifi-ng and see if it works any better. However, the fact that the problem doesn't come up using the standard Ubuntu/Gnome networking tools points back to a NetworkManager issue. Thanks for the response! Mark ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: feedback on attempting to build network-manager from Subversion
On Wed, 2007-03-14 at 09:50 -0400, Mark Stosberg wrote: Dan Williams wrote: On Tue, 2007-03-13 at 20:48 -0400, Mark Stosberg wrote: I tried to build NetworkManager from SVN tonight, to see if the latest version fixed this bug already: http://bugzilla.gnome.org/show_bug.cgi?id=418065 From this ChangeLog entry, it appears that might be fixed: ## * src/nm-device-802-11-wireless.c: Fix wireless device scanning scheduler. The new algorithm is to start from SCAN_INTERVAL_MIN (currently defined as 0) and add a SCAN_INTERVAL_STEP (currently 20 seconds) with each successful scan until SCAN_INTERVAL_MAX (currently 120 seconds) is reached. Do not scan while the device is down, activating, or activated (in case of A/B/G cards).Remove some old dead ifdef'ed out code that used to configure wireless devices, it's all done through supplicant now. ## Likely not. The old 0.6.5 code followed approximately the same algorithm. I suspect driver issues; if the driver is dropping association during a scan, then the driver needs to get fixed. An easy way to test this is to set up a plain wpa_supplicant association, and then do successive 'iwlist eth0 scan' events every 5 or 7 seconds and see if wpa_supplicant gets a disconnect event from the driver. Ok. In my case I think I'm using the madwifi driver, and can try madwifi-ng and see if it works any better. You should not be using 'madwifi' at all. It's quite old, and has been succeeded by madwifi-ng. However, the fact that the problem doesn't come up using the standard Ubuntu/Gnome networking tools points back to a NetworkManager issue. Only as a side-effect. You can likely get the same effect if you periodicially run scans from the command-line without NetworkManager running. It happens that NetworkManager exercises different paths in the driver that static command-line tools do not exercise, but that should work all the same. If they do not, it's a driver bug. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: feedback on attempting to build network-manager from Subversion
Dan Williams wrote: You should not be using 'madwifi' at all. It's quite old, and has been succeeded by madwifi-ng. I got a different impression from reading the NetworkManager page on recommended hardware which states: Old 'madwifi' driver supports unencrypted, WEP, WPA, and WPA2. Newer 'madwifi-ng' driver should also work for all network types, but has recently been quite unstable. I read that to say madwifi supports everything I need and is more stable, and therefore, preferred. Has this part of the page become out of date? http://live.gnome.org/NetworkManagerHardware However, the fact that the problem doesn't come up using the standard Ubuntu/Gnome networking tools points back to a NetworkManager issue. Only as a side-effect. You can likely get the same effect if you periodicially run scans from the command-line without NetworkManager running. It happens that NetworkManager exercises different paths in the driver that static command-line tools do not exercise, but that should work all the same. If they do not, it's a driver bug. Thanks for the clarification. Mark ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: feedback on attempting to build network-manager from Subversion
On Wed, 2007-03-14 at 14:38 -0400, Mark Stosberg wrote: Dan Williams wrote: You should not be using 'madwifi' at all. It's quite old, and has been succeeded by madwifi-ng. I got a different impression from reading the NetworkManager page on recommended hardware which states: Old 'madwifi' driver supports unencrypted, WEP, WPA, and WPA2. Newer 'madwifi-ng' driver should also work for all network types, but has recently been quite unstable. I read that to say madwifi supports everything I need and is more stable, and therefore, preferred. Has this part of the page become out of date? http://live.gnome.org/NetworkManagerHardware Yes; madwifi-ng is now preferred though it may still have issues. They seem to do their own thing. Dan However, the fact that the problem doesn't come up using the standard Ubuntu/Gnome networking tools points back to a NetworkManager issue. Only as a side-effect. You can likely get the same effect if you periodicially run scans from the command-line without NetworkManager running. It happens that NetworkManager exercises different paths in the driver that static command-line tools do not exercise, but that should work all the same. If they do not, it's a driver bug. Thanks for the clarification. Mark ___ 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
Re: feedback on attempting to build network-manager from Subversion
Mark Stosberg wrote: I tried to build NetworkManager from SVN tonight, to see if the latest version fixed this bug already: http://bugzilla.gnome.org/show_bug.cgi?id=418065 From this ChangeLog entry, it appears that might be fixed: ## * src/nm-device-802-11-wireless.c: Fix wireless device scanning scheduler.The new algorithm is to start from SCAN_INTERVAL_MIN (currently defined as 0) and add a SCAN_INTERVAL_STEP (currently 20 seconds) with each successful scanuntil SCAN_INTERVAL_MAX (currently 120 seconds) is reached. Do not scan whilethe device is down, activating, or activated (in case of A/B/G cards).Remove some old dead ifdef'ed out code that used to configure wireless devices, it's all done through supplicant now. ## However, I ran into some barriers trying to install the latest version. First, the website refers to CVS, when the latest code is in Subversion now: http://www.gnome.org/projects/NetworkManager/developers/ For me, the experience on Ubuntu when more like this instead: sudo apt-get install subversion gnome-common checkinstall svn checkout http://svn.gnome.org/svn/NetworkManager/trunk NetworkManager ( Checkinstall would have been useful for creating a package of the CVS version, but I didn't actually get that far ). It seems gnome-common isn't all that a vanilla system needs to compile this. I also get these failures from the autogen script on Ubuntu Edgy: checking for glib-gettext = 2.2.0... testing glib-gettextize... not found. ***Error***: You must have glib-gettext = 2.2.0 installed to build NetworkManager. Download the appropriate package for from your distribution or get the source tarball at ftp://ftp.gtk.org/pub/gtk/v2.2/glib-2.2.0.tar.gz Checking for forbidden M4 macros... ***Error***: some autoconf macros required to build NetworkManager were not found in your aclocal path, or some forbidden macros were found. Perhaps you need to adjust your ACLOCAL_FLAGS? # If someone knows the extra steps missing, it would be nice to update the website to reflect them. I got a little further on this by installing some additional packages mentioned here: http://www.ubuntuforums.org/showthread.php?t=125150 However, this ultimately failed on Ubuntu Edgy, too. The reason is that dbus-glib is not new enough on Edgy: # Requested 'dbus-glib-1 = 0.72' but version of dbus-glib is 0.71 # I tried manually installing the 0.73 version of that package from Feisty, but it in turn had other dependencies: dpkg: dependency problems prevent configuration of libdbus-glib-1-2: libdbus-glib-1-2 depends on libc6 (= 2.5-0ubuntu1); however: Version of libc6 on system is 2.4-1ubuntu12.3. libdbus-glib-1-2 depends on libdbus-1-3 (= 0.94); however: Version of libdbus-1-3 on system is 0.93-0ubuntu3.1. libdbus-glib-1-2 depends on libglib2.0-0 (= 2.12.9); however: Version of libglib2.0-0 on system is 2.12.4-0ubuntu1. # And at that point I gave up again, since I'm comfortable with upgrading much of my system to Feisty at this point. Mark ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: feedback on attempting to build network-manager from Subversion
On Tue, 2007-03-13 at 21:25 -0400, Mark Stosberg wrote: Mark Stosberg wrote: I tried to build NetworkManager from SVN tonight, to see if the latest version fixed this bug already: http://bugzilla.gnome.org/show_bug.cgi?id=418065 From this ChangeLog entry, it appears that might be fixed: ## * src/nm-device-802-11-wireless.c: Fix wireless device scanning scheduler. The new algorithm is to start from SCAN_INTERVAL_MIN (currently defined as 0)and add a SCAN_INTERVAL_STEP (currently 20 seconds) with each successful scan until SCAN_INTERVAL_MAX (currently 120 seconds) is reached. Do not scan while the device is down, activating, or activated (in case of A/B/G cards).Remove some old dead ifdef'ed out code that used to configure wireless devices, it's all done through supplicant now. ## However, I ran into some barriers trying to install the latest version. First, the website refers to CVS, when the latest code is in Subversion now: http://www.gnome.org/projects/NetworkManager/developers/ For me, the experience on Ubuntu when more like this instead: sudo apt-get install subversion gnome-common checkinstall svn checkout http://svn.gnome.org/svn/NetworkManager/trunk NetworkManager ( Checkinstall would have been useful for creating a package of the CVS version, but I didn't actually get that far ). It seems gnome-common isn't all that a vanilla system needs to compile this. I also get these failures from the autogen script on Ubuntu Edgy: checking for glib-gettext = 2.2.0... testing glib-gettextize... not found. ***Error***: You must have glib-gettext = 2.2.0 installed to build NetworkManager. Download the appropriate package for from your distribution or get the source tarball at ftp://ftp.gtk.org/pub/gtk/v2.2/glib-2.2.0.tar.gz Checking for forbidden M4 macros... ***Error***: some autoconf macros required to build NetworkManager were not found in your aclocal path, or some forbidden macros were found. Perhaps you need to adjust your ACLOCAL_FLAGS? # If someone knows the extra steps missing, it would be nice to update the website to reflect them. I got a little further on this by installing some additional packages mentioned here: http://www.ubuntuforums.org/showthread.php?t=125150 However, this ultimately failed on Ubuntu Edgy, too. The reason is that dbus-glib is not new enough on Edgy: # Requested 'dbus-glib-1 = 0.72' but version of dbus-glib is 0.71 # I tried manually installing the 0.73 version of that package from Feisty, but it in turn had other dependencies: dpkg: dependency problems prevent configuration of libdbus-glib-1-2: libdbus-glib-1-2 depends on libc6 (= 2.5-0ubuntu1); however: Version of libc6 on system is 2.4-1ubuntu12.3. libdbus-glib-1-2 depends on libdbus-1-3 (= 0.94); however: Version of libdbus-1-3 on system is 0.93-0ubuntu3.1. libdbus-glib-1-2 depends on libglib2.0-0 (= 2.12.9); however: Version of libglib2.0-0 on system is 2.12.4-0ubuntu1. # And at that point I gave up again, since I'm comfortable with upgrading much of my system to Feisty at this point. Yeah, SVN trunk is a bit rocky at this point, though it should more or less work. Tambet is working on rewriting large parts of the applet to use the new D-Bus API too, and there are probably rough edges in most places. Next up is the config D-Bus API, followed by multiple active device support and then we're pretty much done for 0.7. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: feedback on attempting to build network-manager from Subversion
On Tue, 2007-03-13 at 20:48 -0400, Mark Stosberg wrote: I tried to build NetworkManager from SVN tonight, to see if the latest version fixed this bug already: http://bugzilla.gnome.org/show_bug.cgi?id=418065 From this ChangeLog entry, it appears that might be fixed: ## * src/nm-device-802-11-wireless.c: Fix wireless device scanning scheduler.The new algorithm is to start from SCAN_INTERVAL_MIN (currently defined as 0) and add a SCAN_INTERVAL_STEP (currently 20 seconds) with each successful scanuntil SCAN_INTERVAL_MAX (currently 120 seconds) is reached. Do not scan whilethe device is down, activating, or activated (in case of A/B/G cards).Remove some old dead ifdef'ed out code that used to configure wireless devices, it's all done through supplicant now. ## Likely not. The old 0.6.5 code followed approximately the same algorithm. I suspect driver issues; if the driver is dropping association during a scan, then the driver needs to get fixed. An easy way to test this is to set up a plain wpa_supplicant association, and then do successive 'iwlist eth0 scan' events every 5 or 7 seconds and see if wpa_supplicant gets a disconnect event from the driver. Dan However, I ran into some barriers trying to install the latest version. First, the website refers to CVS, when the latest code is in Subversion now: http://www.gnome.org/projects/NetworkManager/developers/ For me, the experience on Ubuntu when more like this instead: sudo apt-get install subversion gnome-common checkinstall svn checkout http://svn.gnome.org/svn/NetworkManager/trunk NetworkManager ( Checkinstall would have been useful for creating a package of the CVS version, but I didn't actually get that far ). It seems gnome-common isn't all that a vanilla system needs to compile this. I also get these failures from the autogen script on Ubuntu Edgy: checking for glib-gettext = 2.2.0... testing glib-gettextize... not found. ***Error***: You must have glib-gettext = 2.2.0 installed to build NetworkManager. Download the appropriate package for from your distribution or get the source tarball at ftp://ftp.gtk.org/pub/gtk/v2.2/glib-2.2.0.tar.gz Checking for forbidden M4 macros... ***Error***: some autoconf macros required to build NetworkManager were not found in your aclocal path, or some forbidden macros were found. Perhaps you need to adjust your ACLOCAL_FLAGS? # If someone knows the extra steps missing, it would be nice to update the website to reflect them. ( And of course, I'm still curious to find a solution the frequent disconnect/reconnect bug!) Mark ___ 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
