nm-applet breakage/fixage
Hi all, A quick note to introduce myself. I'm Michael Croes, I'm a Gentoo and Ubuntu user and currently working on a Gentoo ebuild overlay with some bleeding edge stuff. Besides doing this for others, there's some stuff I want to work for myself too, like NetworkManager. I succesfully compiled NetworkManager revision 2467 and wrote an ebuild that works fine right now. Next problem was network-manager-applet. Now it seems there have been quite some changes in NetworkManager which caused some breakage in network-manager-applet, so it certainly won't compile with minor changes atm. I'd be very happy to (at least try to) fix the current network-manager-applet, but it would be nice if there's some description about the changes in NetworkManager to do so. Is there some place where this is documented in more detail than is done in the svn comments? Or is there someone that can explain the changes to me on irc/mail/msn or anything? Greetings, Michael ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet breakage/fixage
On Wed, 2007-03-14 at 11:46 +0100, Michael Croes wrote: I succesfully compiled NetworkManager revision 2467 and wrote an ebuild that works fine right now. Next problem was network-manager-applet. Now it seems there have been quite some changes in NetworkManager which caused some breakage in network-manager-applet, so it certainly won't compile with minor changes atm. I'd be very happy to (at least try to) fix the current network-manager-applet, but it would be nice if there's some description about the changes in NetworkManager to do so. Is there some place where this is documented in more detail than is done in the svn comments? Or is there someone that can explain the changes to me on irc/mail/msn or anything? You should use the NETWORKMANAGER_0_6_0_RELEASE branch for bleeding edge. The SVN trunk has new DBUS API and doesn't currently work at all with nm-applet. If you want to help out with the development, see NetworkManager/libnm-glib/*.[ch] and replace the DBUS code in nm-applet with libnm-glib code. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: network-manager-applet release
Am Montag, den 12.03.2007, 19:34 -0700 schrieb Elijah Newren: it'd be great to have a tarball release. In fact, nm-applet can't be included in the GNOME release without having a tarball release to include. I'm very tempted to just request that nm-applet be re-proposed for inclusion in 2.20, but maybe if we get a tarball quickly... whouah, still no release? this makes me pretty pissed. this is exactly the maintainer behaviour that would let me vote for no if nm-applet would be proposed again for inclusion into gnome: Module owners should show they can hit release deadlines - oh yeah. andre -- mailto:[EMAIL PROTECTED] | failed! http://www.iomc.de/ | http://blogs.gnome.org/portal/aklapper ---BeginMessage--- On Fri, 2007-03-02 at 22:38 +0100, Vincent Untz wrote: (cc'ing the NM list) Le vendredi 02 mars 2007, à 21:54, Jaap Haitsma a écrit : Something I noticed. The latest release of network manager (applet) is 0.6.4 which is already something like 9 months. AFAIK there has not been a release since. Is there going to be a release for 2.18? Hi, I (and possibly Andre) have pinged NetworkManager people about this. It's definitely important to have a release for 2.18.0. (It would have been great to have a release for the RC too...) Yeah; I'll get an applet 0.6.5 release done this week. Dan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list---End Message--- signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
talk about going around robinhood's barn...
... or maybe hunting heffalumps. but apparenty the only way i can perhaps get what i take to be a simple question about networkmanager answered is to 'post a message to all the list members' and hope somebody either knows the answer or at least can aim me at whoever the unspecified-anywhere-i-could-spot purveyors of this program the apparent web site of which [http://www.gnome.org/projects/NetworkManager/] seems to have been composed by an old-line ibm salesman, since all it does is tell you how great it's going to be. [unless, of course, i'm supposed to plink the red hat inc. link since they're the copyright holders, even tho i always thought there were only copyleft's in this world.] answer by direct netmail, as we called it when we were inventing it, please, since as should be obvious i'm not on the mailing list and have no desire to be on it. [don't ask why; i might answer ... at far more length than you'll want to see.] so, here's what i want to know: how, if at all, can i get networkmanager to offer me a choice between both the built-in wifi widget in my new lenovo 3000 n100 [which i think of as VistaSystem 1 because, like playstations, if you work incredibly hard you can get at the computer you know is in there rather than just do the things it wants you to do -- as in play playstation games on playstations and use vista on vistastations -- provided you're willing to run the super grub disc to clean up after incredible obscenities that vista commits upon the mbr if you happen to need to use the now dual-booted vista that comes with the thing ... and which will wipe out your linux along with everything else on the hard drive if you have to reinstall the bloody vista], which isn't the ipw3945 i'd been misled to believe it was going to be, but some broadcom thing that's apparently not going to be usable on linux yet [i speak after a week or more of trying to get it to work ... and, of course, failing], and the airlink usb thing i picked up for 12bux at fry's in case i could never get what i thought at the time was the ipw3945 to work, but it was supposed to on linux, especially ubuntu 6.10, which i happened to choose for reasons i've already forgotten but i think had something to do wit the ipw3945 was supposed to work with it. ok, that's a rather involved sentence. and it doesn't quite make the real point, which is that there's the built-in wifi on eth1 that doesn't work and this usb wifi on eth2 that should work, but all network manager seems to do is notice eth1, so how can i make it notice both [and then select the latter] -- or can't i make it notice both and i'll have to wait for ubuntu 7.04 which is supposed to support the built-in [i think]? and PLEASE don't tell me to switch to your favorite 'distro' instead. i just invested another several hours doing a clean reinstall of 6.10 in hopes of clearing away all the messes i'd made trying to get all three of the wifi widgets to work and then either get the usb one to work or wait until 'feisty' comes out officially because there's enough about the current ubuntu that i do like that i don't intend to abandon it ... this time; i've abandoned any number of 'distros' over the last few years, and i think i'm finally willing to stay with it. so if i have to use bloody vista to get at the 'net from my living room when i want to get at the net from my living room for 6 weeks or so, so be it. for that matter, don't ask me exactly which broadcom and zydas chips are involved either. i know that neither might be workable [except for the fact that somehow i did get one of them -- i think the usb one -- to work, once, it's just that it wouldn't work the next time and i couldn't recreate what i'd done to accidentally make it work after that], but all i want to know is how i can i get netmanager to let me see/choose between eth1 and eth2. and yes, i have wasted far too much time looking for anything remotely resembling documentation on networkmanager. all i found was a probably outdated 'faq' which was no help and which didn't indicate how to communicate with whoever wrote it ... unless the plinkable last revised by item that led to a logically blank page was meant to be the way to communicate, in which case it's broken. thanks, and cheers, map [whose shoulder problems caused him to break down some time ago and create a 'signature' file to apologize for the lack of his formerly customary e-volubility -- and who's been employing shiftless typing for a long time now to spare his wristsnfingers, in case you didn't know ... and who's further broken down and done http://www.lafn.org/~ba213/mapstuff.html , rather grudgingly] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: talk about going around robinhood's barn...
On 3/14/07, Mike Padlipsky [EMAIL PROTECTED] wrote: ... or maybe hunting heffalumps. but apparenty the only way i can perhaps get what i take to be a simple question about networkmanager answered is to 'post a message to all the list members' and hope somebody either knows the answer or at least can aim me at whoever the unspecified-anywhere-i-could-spot purveyors of this program the apparent web site of which [http://www.gnome.org/projects/NetworkManager/] seems to have been composed by an old-line ibm salesman, since all it does is tell you how great it's going to be. [unless, of course, i'm supposed to plink the red hat inc. link since they're the copyright holders, even tho i always thought there were only copyleft's in this world.] answer by direct netmail, as we called it when we were inventing it, please, since as should be obvious i'm not on the mailing list and have no desire to be on it. [don't ask why; i might answer ... at far more length than you'll want to see.] so, here's what i want to know: how, if at all, can i get networkmanager to offer me a choice between both the built-in wifi widget in my new lenovo 3000 n100 [which i think of as VistaSystem 1 because, like playstations, if you work incredibly hard you can get at the computer you know is in there rather than just do the things it wants you to do -- as in play playstation games on playstations and use vista on vistastations -- provided you're willing to run the super grub disc to clean up after incredible obscenities that vista commits upon the mbr if you happen to need to use the now dual-booted vista that comes with the thing ... and which will wipe out your linux along with everything else on the hard drive if you have to reinstall the bloody vista], which isn't the ipw3945 i'd been misled to believe it was going to be, but some broadcom thing that's apparently not going to be usable on linux yet [i speak after a week or more of trying to get it to work ... and, of course, failing], and the airlink usb thing i picked up for 12bux at fry's in case i could never get what i thought at the time was the ipw3945 to work, but it was supposed to on linux, especially ubuntu 6.10, which i happened to choose for reasons i've already forgotten but i think had something to do wit the ipw3945 was supposed to work with it. ok, that's a rather involved sentence. and it doesn't quite make the real point, which is that there's the built-in wifi on eth1 that doesn't work and this usb wifi on eth2 that should work, but all network manager seems to do is notice eth1, so how can i make it notice both [and then select the latter] -- or can't i make it notice both and i'll have to wait for ubuntu 7.04 which is supposed to support the built-in [i think]? and PLEASE don't tell me to switch to your favorite 'distro' instead. i just invested another several hours doing a clean reinstall of 6.10 in hopes of clearing away all the messes i'd made trying to get all three of the wifi widgets to work and then either get the usb one to work or wait until 'feisty' comes out officially because there's enough about the current ubuntu that i do like that i don't intend to abandon it ... this time; i've abandoned any number of 'distros' over the last few years, and i think i'm finally willing to stay with it. so if i have to use bloody vista to get at the 'net from my living room when i want to get at the net from my living room for 6 weeks or so, so be it. for that matter, don't ask me exactly which broadcom and zydas chips are involved either. i know that neither might be workable [except for the fact that somehow i did get one of them -- i think the usb one -- to work, once, it's just that it wouldn't work the next time and i couldn't recreate what i'd done to accidentally make it work after that], but all i want to know is how i can i get netmanager to let me see/choose between eth1 and eth2. and yes, i have wasted far too much time looking for anything remotely resembling documentation on networkmanager. all i found was a probably outdated 'faq' which was no help and which didn't indicate how to communicate with whoever wrote it ... unless the plinkable last revised by item that led to a logically blank page was meant to be the way to communicate, in which case it's broken. thanks, and cheers, map Ok in that long email I was not able to determine exactly what issue you are having so let me try and break it down. You have two wireless cards: 1) Broadcom Mini-PCI 2) Some USB device Network Manager sees the MiniPCI device but not the USB device? Can you post your /etc/network/interfaces (commenting out any keys) and post the type of chipset in the usb device? Please make sure you include the list on the reply so others can see the same information. Thanks ___ NetworkManager-list mailing list NetworkManager-list@gnome.org
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
Cannot Install from SVN
I checked this out on March 14th at about 7:45 eastern time. I tried running autogen.sh to create the configuration files needed to install. I got the following output. [EMAIL PROTECTED]:/home/mdshann/nmSVN/NETWORKMANAGER_0_6_0_RELEASE# ./autogen.sh /usr/bin/gnome-autogen.sh checking for autoconf = 2.53... testing autoconf2.50... not found. testing autoconf... found 2.60 checking for automake = 1.7... testing automake-1.7... not found. testing automake-1.8... not found. testing automake-1.9... found 1.9.6 checking for libtool = 1.5... testing libtoolize... found 1.5.22 checking for glib-gettext = 2.2.0... testing glib-gettextize... found 2.12.4 checking for intltool = 0.30... testing intltoolize... found 0.35.0 checking for pkg-config = 0.14.0... testing pkg-config... found 0.20 Checking for required M4 macros... Checking for forbidden M4 macros... **Warning**: I am going to run `configure' with no arguments. If you wish to pass any to it, please specify them on the `./autogen.sh' command line. Processing ./vpn-daemons/pptp/configure.in Running libtoolize... You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'. Running glib-gettextize... Ignore non-fatal messages. Copying file mkinstalldirs Copying file po/Makefile.in.in Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /usr/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/. Running intltoolize... Running aclocal-1.9... acinclude.m4:12: warning: underquoted definition of AS_AC_EXPAND run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending-aclocal Running autoconf... Running autoheader... Running automake-1.9... cp: cannot stat `COPYING': No such file or directory cp: cannot stat `INSTALL': No such file or directory configure.in: installing `./install-sh' configure.in: installing `./missing' auth-dialog/Makefile.am: installing `./compile' auth-dialog/Makefile.am: installing `./depcomp' cmp: COPYING: No such file or directory cp: cannot stat `COPYING.autogen_bak': No such file or directory cmp: INSTALL: No such file or directory cp: cannot stat `INSTALL.autogen_bak': No such file or directory Processing ./vpn-daemons/openvpn/configure.in Running libtoolize... You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'. Running glib-gettextize... Ignore non-fatal messages. Copying file mkinstalldirs Copying file po/Makefile.in.in Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /usr/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/. Running intltoolize... Running aclocal-1.9... acinclude.m4:12: warning: underquoted definition of AS_AC_EXPAND run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending-aclocal Running autoconf... Running autoheader... Running automake-1.9... cp: cannot stat `COPYING': No such file or directory cp: cannot stat `INSTALL': No such file or directory configure.in: installing `./install-sh' configure.in: installing `./missing' auth-dialog/Makefile.am: installing `./compile' auth-dialog/Makefile.am: installing `./depcomp' cmp: COPYING: No such file or directory cp: cannot stat `COPYING.autogen_bak': No such file or directory cmp: INSTALL: No such file or directory cp: cannot stat `INSTALL.autogen_bak': No such file or directory Processing ./vpn-daemons/vpnc/configure.in Running libtoolize... You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'. Running glib-gettextize... Ignore non-fatal messages. Copying file mkinstalldirs Copying file po/Makefile.in.in Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /usr/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/. Running intltoolize... Running aclocal-1.9... acinclude.m4:12: warning: underquoted definition of AS_AC_EXPAND run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending-aclocal Running autoconf... Running autoheader... Running automake-1.9... cp: cannot stat `COPYING': No such file or directory cp: cannot stat `INSTALL': No such file or directory configure.in: installing `./install-sh' configure.in: installing `./missing' auth-dialog/Makefile.am: installing `./compile' auth-dialog/Makefile.am: installing `./depcomp' cmp: COPYING: No such file or directory cp:
Re: talk about going around robinhood's barn...
At 05:31 AM 3/14/2007, Darren Albers wrote: Ok in that long email I was not able to determine exactly what issue you are having so let me try and break it down. You have two wireless cards: 1) Broadcom Mini-PCI 2) Some USB device Network Manager sees the MiniPCI device but not the USB device? Can you post your /etc/network/interfaces (commenting out any keys) and post the type of chipset in the usb device? Please make sure you include the list on the reply so others can see the same information. Thanks Sorry about the length. I find writing cathartic. By way of apology, I'll even use the shift key this time and use html to make the most important points stand out since even this isn't as short as you might like it to. (And I'll use my alternate .sig, which might help explain the over-writing tendencies.) However, my current .../interfaces is irrelevant. I did a clean reinstall to clear away the tangles I'd gotten myself into, and haven't even reinstalled NetManager yet because I'm trying to find out if it'll be worth my while to do so. I am sure I had nothing but lo active during several of the NetManager attempts, though, and it still only seemed to be noticing eth1 (and presumably eth0) but not eth2. And while I'm willing to fire up the notebook to get the exact chip info if it turns out that that might be relevant, all I really want to know is Can NetManager in principle deal with two WiFi devices in the same machine? If so, what's the trick to make it do so? (For example, should the USB device only be inserted after NetManager's had its first shot at things?) Sure, if might be the case that the answer to the first question is Yes, but only if it knows about both; and the answer to the second is No trick at all if it does know about both, it'll just show them to you, so tell me exactly what you've got. But if that's the case, I think I already know it doesn't know about both -- and that the one it thinks it knows about has changed subtly on its way into the Lenovo 3000 N100 under Vista, since it also didn't work before I plugged the USB device in -- and I'll just wait for Feisty. (Well, unless there turns out to be some source[s] I couldn't find for getting the appropriate driver[s] so NetManager would know about both. Or even just about the built-in.) Please believe me, I'm not trying to be difficult, I'm just trying to conserve what little energy I have left after 3+ weeks of not being able to get Edgy to do wireless on that stupid machine I wish I hadn't been tempted to buy because it seemed I was getting a lot of good iron for the money. thanks, and cheers, map Michael A. Padlipsky 8011 Stewart Ave. Los Angeles, CA 90045 310-670-4288 http://www.lafn.org/~ba213/mapstuff.html __ Mr. Padlipsky is the author of The Elements of Networking Style and Other Essays and Animadversions on the Art of Intercomputer Networking, the world's only known Constructively Snotty computer science book (©1985, reprinted ©2000). ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Cannot Install from SVN
Matthew Shannon wrote: I don't understand how wireless tools could not be installed since I use wireless already. I am trying to get LEAP functionality from NetworkManager SVN. I noticed that there was a configure file so I tried it as well, but got basically the same error, since autogen.sh calls configure at the end anyways. Any suggestions? Thanks! Also, anyone who has gotten leap working, what wireless cards are you using, and what drivers (ndiswrapper or a kernel module)? I unfortunately cannot help you in what package you need - but when compiling, you will need -dev packages, which most binary distros do not install by default. My guess is, you are missing the wireless-tools-dev package (just a while guess based on typical naming fashions) -- Steev ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: talk about going around robinhood's barn...
snipping everything as its fairly pointless (no offense) The reason that we ask about the chipsets, and your interfaces file, is that each distro handles wireless differently, this includes the way they install and use NetworkManager. Gentoo does patch a little bit to the backend (should probably check that in some time soonish) - however, Ubuntu will *IGNORE* any devices that are *configured* in /etc/network/interfaces so - whether or not they are active, if they are located in the file, simply comment them out. We can't tell you if $RANDOM_USB_STICK works because we need to know chipsets - some drivers are known to be buggy and may require workarounds that we do not include in NetworkManager, does it work with wpa_supplicant - does it continue to work with wpa_supplicant if you issue a scan every 5-10 seconds... Things like this. Yes, networkmanager can handle multiple wireless cards in a machine, and even multiple wireless *and* a wired interface - although wired will take precedence. You can only have 1 wired or wireless interface active at a time however. As long as hal can see the interface, and it's driver is exporting the information that NetworkManager needs, then there should be no issues with using the card - UNLESS - it is *configured* in your /etc/network/interfaces file. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Cannot Install from SVN
On 3/14/07, Steev Klimaszewski [EMAIL PROTECTED] wrote: Matthew Shannon wrote: I don't understand how wireless tools could not be installed since I use wireless already. I am trying to get LEAP functionality from NetworkManager SVN. I noticed that there was a configure file so I tried it as well, but got basically the same error, since autogen.sh calls configure at the end anyways. Any suggestions? Thanks! Also, anyone who has gotten leap working, what wireless cards are you using, and what drivers (ndiswrapper or a kernel module)? I unfortunately cannot help you in what package you need - but when compiling, you will need -dev packages, which most binary distros do not install by default. My guess is, you are missing the wireless-tools-dev package (just a while guess based on typical naming fashions) -- Steev ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list To back up what Steev mention in the Debian (And it's variants) world you need libiw-dev. Thanks! Darren ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: talk about going around robinhood's barn...
At 04:47 PM 3/14/2007, Steev Klimaszewski wrote: We can't tell you if $RANDOM_USB_STICK works because we need to know chipsets ok, once you put it that way of course, that does give rise to the question of how i know what the chipset is. and that's NOT being cute. lsusb says 1215 ZyDAS. so does ifconfig. but iwconfig says zd1211. best 2 out of 3? [well, sure, that one was a bit cute. but being new to linux/ubuntu, even if i was designing and implementing operating systems 4 years before linus torvalds was born, how am i supposed to know which method you think is definitive? when i was futzing around w/ fwcutter before the cleaning of the slate reinstall i'd managed to convince myself it was the 1215 after far too much googing around, but that might've been the wrong guess ... except for the 'fact' that somewhere or another somebody had said the 1211 'works out of the box' and whatever i've got didn't.] and while we're at it, lspci says the built-in's a broadcom 4311 (rev01), iwconfig says it's a 4311, and ... brace yourself ... ifconfig doesn't say anything at all about eth1, tho it does about eth0 and eth2. you see why i'm frustrated? and why i was hoping i wouldn't have to tell you what chip[s] was/were involved? never mind, i'm not really asking for sympathy, or 'understanding', just asking for help. and i'm already grateful to have been told unequivocally that networkmanager should be able to deal with the 2-wirelesswidgets case ... even if it took longer than i'd hoped to hear that. cheers, map [whose shoulder problems caused him to break down some time ago and create a 'signature' file to apologize for the lack of his formerly customary e-volubility -- and who's been employing shiftless typing for a long time now to spare his wristsnfingers, in case you didn't know ... and who's further broken down and done http://www.lafn.org/~ba213/mapstuff.html , rather grudgingly] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: talk about going around robinhood's barn...
On 3/14/07, Mike Padlipsky [EMAIL PROTECTED] wrote: At 04:47 PM 3/14/2007, Steev Klimaszewski wrote: We can't tell you if $RANDOM_USB_STICK works because we need to know chipsets ok, once you put it that way of course, that does give rise to the question of how i know what the chipset is. and that's NOT being cute. lsusb says 1215 ZyDAS. so does ifconfig. but iwconfig says zd1211. best 2 out of 3? [well, sure, that one was a bit cute. but being new to linux/ubuntu, even if i was designing and implementing operating systems 4 years before linus torvalds was born, how am i supposed to know which method you think is definitive? when i was futzing around w/ fwcutter before the cleaning of the slate reinstall i'd managed to convince myself it was the 1215 after far too much googing around, but that might've been the wrong guess ... except for the 'fact' that somewhere or another somebody had said the 1211 'works out of the box' and whatever i've got didn't.] and while we're at it, lspci says the built-in's a broadcom 4311 (rev01), iwconfig says it's a 4311, and ... brace yourself ... ifconfig doesn't say anything at all about eth1, tho it does about eth0 and eth2. you see why i'm frustrated? and why i was hoping i wouldn't have to tell you what chip[s] was/were involved? I think we all wish that were the case but with many wireless vendors being unable/unwilling to support Linux you will find that the drivers are a mixed bag. There is current a standard for Wireless devices call the Wireless Extension (WEXT) and Network-Manager requires that to interface with the cards so it doesn't have to support all the various ways the cards expose themselves. Looking at the Zydas page it looks like it should support WEXT so I am not sure why it doesn't show up. Can you post the output of iwconfig and lshal -l? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: talk about going around robinhood's barn...
On 3/14/07, Darren Albers [EMAIL PROTECTED] wrote: snip I think we all wish that were the case but with many wireless vendors being unable/unwilling to support Linux you will find that the drivers are a mixed bag. There is current a standard for Wireless devices call the Wireless Extension (WEXT) and Network-Manager requires that to interface with the cards so it doesn't have to support all the various ways the cards expose themselves. Looking at the Zydas page it looks like it should support WEXT so I am not sure why it doesn't show up. Can you post the output of iwconfig and lshal -l? Ok I recant what I said, the version in Edgy doesn't seem to support WEXT. The version in Feisty does however but there is a howto on the Ubuntu Forums that gives instructions for installing the newer driver on Edgy: http://www.ubuntuforums.org/showthread.php?t=288753 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
