Re: Atheros abg / madwifi trouble
i agree! i just filed a bug report/enhancement request: http://bugzilla.gnome.org/show_bug.cgi?id=165933 at least for me, i find NM's constant scanning and disconnecting more than annoying, and it makes NM unusable for my (laptop's) daily needs. thanks, Sven > maybe it's possible to implement a "hidden" preference in gconf to supply > a scan interval or even prevent scanning. > i'd like to prevent nm from scanning when i'm at home 'cause i know there > is only one access point! > > bye > stefan > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Mon, 31 Jan 2005 15:45:10 -0500, Sven wrote: > On Mon, 2005-01-31 at 13:40 -0500, Dan Williams wrote: >> On Mon, 2005-01-31 at 13:31 -0500, Sven wrote: >> > my last 10c: could NM not just monitor the "Link Quality" of the >> > connection (as in /proc/net/wireless) and trigger a scan if that changes >> > dramatically? (i guess also with a timer, since if the link quality is >> > low anyway every change in LQ will be "dramatic" ...) >> >> Unfortunately, the link quality is not reported uniformly by drivers. >> Some only give you the signal level in dBm, many give you noise in dBm >> (so at least one could do a signal-to-noise ratio for some idea of >> quality), some drivers give you a quality but no maximum quality, and >> some drivers actually do the right thing. Furthermore, many drivers >> don't report the correct maximum quality/max rssi for your particular >> chipset. Its really not good to rely on anything quality related at >> this time. > > understood. i guess it's hard to find a solution that fits all... > especially with all these different cards and drivers and... > > i guess i would really really like to be able to stay connected to the > ap, i.e. be able to stop the scanning, since i'm usually in one spot for > a long time... and the constant disconnecting (even for a short time) is > really annoying. any chance to have the scanning optional? > > Sven maybe it's possible to implement a "hidden" preference in gconf to supply a scan interval or even prevent scanning. i'd like to prevent nm from scanning when i'm at home 'cause i know there is only one access point! bye stefan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Sun, 30 Jan 2005 22:52:59 -0500, Lance A. Brown wrote: > Dan Williams wrote: >> >> I've committed some updates to CVS that may fix this, but Monday at work a >> coworker has an Atheros abg card that I'll test out and see if I can come >> up with a definite fix. > > NM isn't pushing my Atheros into mode 1 (802.11a) mode anymore, and the > NIC associates with my AP properly now, but NM isn't finding out the NIC > has hardware link. It sits forever waiting. > > This is a definite improvment over getting put into 802.11a mode. I'm > glad to see progress! > > --[Lance] yes. great improvement over the version of nm released with fc3! i experience the same here. as soon as i the card associates, nm reports no hardware link and waits for another ap forever. dan, i hope you find the bug today. bye stefan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Mon, 2005-01-31 at 11:14 -0500, Dan Williams wrote: > We can't _stop_ scanning when we're successfully connected to an AP, > otherwise we'll never get an up-to-date list of access points in our > menu, but it can be far less often than we do it now. I still think > that if the normalized scan list changes, we need to bump the next scan > up earlier as well, to ensure validity of the scan list. The thing is, > if the menu lists an access point that actually is no longer there, the > user technically cannot connect to it, but its still in the menu. > _Also_ not good from a users perspective. It should be possible though to only do the scan when the applet is clicked on? At least if we're connected with "high" quality; I know there are problems with quality, but perhaps it is possible to see how sensible the returned information is, and use it if it seems reasonable. Or alternatively go the whitelist approach. 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
Re: Atheros abg / madwifi trouble
On Mon, 2005-01-31 at 13:40 -0500, Dan Williams wrote: > On Mon, 2005-01-31 at 13:31 -0500, Sven wrote: > > my last 10c: could NM not just monitor the "Link Quality" of the > > connection (as in /proc/net/wireless) and trigger a scan if that changes > > dramatically? (i guess also with a timer, since if the link quality is > > low anyway every change in LQ will be "dramatic" ...) > > Unfortunately, the link quality is not reported uniformly by drivers. > Some only give you the signal level in dBm, many give you noise in dBm > (so at least one could do a signal-to-noise ratio for some idea of > quality), some drivers give you a quality but no maximum quality, and > some drivers actually do the right thing. Furthermore, many drivers > don't report the correct maximum quality/max rssi for your particular > chipset. Its really not good to rely on anything quality related at > this time. understood. i guess it's hard to find a solution that fits all... especially with all these different cards and drivers and... i guess i would really really like to be able to stay connected to the ap, i.e. be able to stop the scanning, since i'm usually in one spot for a long time... and the constant disconnecting (even for a short time) is really annoying. any chance to have the scanning optional? Sven ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Mon, 2005-01-31 at 13:08 -0500, Sven wrote: > also, i noticed that in a network environment with many ap's with the > same essid NM only shows one entry in the wireless networks - should one > not be able to choose between the ap's if one wanted to? but that's just > a minor question on the side... Unless we're displaying the MAC address too (which we're not going to do) it doesn't really make any sense to show multiple access points in the menu. In the future, I hope to be able to pick a certain access point based on signal strength, or at least fix card drivers to be able to correctly roam to different access points in the same ESSID. Some drivers have private ioctl()s to be able to do that but AFAIK almost all cards support that capability. The problem with specifying a particular MAC address to associate with is that the card can't roam and is locked to that MAC until we change it. Which would be OK, except that scanned quality information is even worse than associated AP quality information. Some drivers (atmel, ipw2100) don't even return quality information for scanned access points, and other drivers give totally different and inconsistent quality levels for scanned access points in relation to the noise/max_quality levels they advertise (for example, the currently associated AP's quality information returned by SIOCGIWSTATS is completely different than the quality information _for that same AP_ as returned in the scan list). In short, drivers really need to be fixed. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Mon, 2005-01-31 at 13:31 -0500, Sven wrote: > my last 10c: could NM not just monitor the "Link Quality" of the > connection (as in /proc/net/wireless) and trigger a scan if that changes > dramatically? (i guess also with a timer, since if the link quality is > low anyway every change in LQ will be "dramatic" ...) Unfortunately, the link quality is not reported uniformly by drivers. Some only give you the signal level in dBm, many give you noise in dBm (so at least one could do a signal-to-noise ratio for some idea of quality), some drivers give you a quality but no maximum quality, and some drivers actually do the right thing. Furthermore, many drivers don't report the correct maximum quality/max rssi for your particular chipset. Its really not good to rely on anything quality related at this time. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
my last 10c: could NM not just monitor the "Link Quality" of the connection (as in /proc/net/wireless) and trigger a scan if that changes dramatically? (i guess also with a timer, since if the link quality is low anyway every change in LQ will be "dramatic" ...) thanks for all your efforts, i really appreciate the responses i received! Sven ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Mon, 2005-01-31 at 12:25 -0500, Dan Williams wrote: > On Mon, 2005-01-31 at 11:46 -0500, Sven wrote: > > agreed. the drivers are not perfect, but usable. i'm annoyed by the fact > > that my current madwifi driver does not display signal strengths in > > iwlist scan. however, it seems to me that the card _is_ scanning for > > changes in AP's constantly without disconnecting (ie, in wavemon i see > > changes in the AP list, but no interruptions in the connection). i > > assume that is driver specific? > > I just checked with wavemon and my Atheros a/b/g card... I also see the > list of access points changing, but the code that does that uses the > SIOCGIWAPLIST ioctl() which is deprecated and not very well supported > (only Atheros/madwifi seems to support it at all, none of the kernel > drivers do). It seems to be more of a "passive" function that just > pulls the card's current list of access points without actually > triggering a scan. I would expect this function to get removed from > Madwifi at some point. Just the fact that none of the in-kernel drivers > support SIOCGIWAPLIST means we cannot use it and that we must use > SIOCGIWSCAN. There are a number of reasons for that, first that WAPLIST > had hard limits on the attributes for each AP returned by the call, it > had an upper limit of access points returned too. > > In short, wavemon is using a deprecated API that is only supported by > the madwifi drivers and will be removed in the future AFAIK. mhhh. too bad. i played with iwlist a bit (and, after downloading the madwifi sources and building a new driver i have even link qualities now) i noticed disassociation from the AP when scanning, as you said. and iwlist ap only shows the AP's from previous scans... FWIW i also noticed though that wavemon has the same output in aplst as iwlist ap. > > I think we can address your problem by having the card scan less often > (and even less often if its an a/b/g card). that would be great! automatic scanning is great, but not if it makes the connection a pain... in the NM applet, could there be a user friendly way to restrict the card to a,b or g only? also, i noticed that in a network environment with many ap's with the same essid NM only shows one entry in the wireless networks - should one not be able to choose between the ap's if one wanted to? but that's just a minor question on the side... Sven ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Mon, 2005-01-31 at 11:46 -0500, Sven wrote: > agreed. the drivers are not perfect, but usable. i'm annoyed by the fact > that my current madwifi driver does not display signal strengths in > iwlist scan. however, it seems to me that the card _is_ scanning for > changes in AP's constantly without disconnecting (ie, in wavemon i see > changes in the AP list, but no interruptions in the connection). i > assume that is driver specific? I just checked with wavemon and my Atheros a/b/g card... I also see the list of access points changing, but the code that does that uses the SIOCGIWAPLIST ioctl() which is deprecated and not very well supported (only Atheros/madwifi seems to support it at all, none of the kernel drivers do). It seems to be more of a "passive" function that just pulls the card's current list of access points without actually triggering a scan. I would expect this function to get removed from Madwifi at some point. Just the fact that none of the in-kernel drivers support SIOCGIWAPLIST means we cannot use it and that we must use SIOCGIWSCAN. There are a number of reasons for that, first that WAPLIST had hard limits on the attributes for each AP returned by the call, it had an upper limit of access points returned too. In short, wavemon is using a deprecated API that is only supported by the madwifi drivers and will be removed in the future AFAIK. > right now, i'm more or less happy using ifplugd and connecting to secure > networks by hand. it'd be great to have a wireless solution that works > in a user friendly way, though. I think we can address your problem by having the card scan less often (and even less often if its an a/b/g card). Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Mon, 2005-01-31 at 11:14 -0500, Dan Williams wrote: > On Mon, 2005-01-31 at 10:37 -0500, Sven wrote: > > > There are really just two things to consider. We can't _never_ scan, > > > and we can't always scan. We need to find some algorithm for NM of > > > balancing the two, and make that algorithm tunable on-the-fly. We want > > > to do a few scans on startup of course, to build the initial list. And > > > perhaps we want to scan more often when the card isn't in use or when > > > its not associated, for example. > > it seems to me that if the card is connected to an AP, it should not try to > > scan that much/often unless the user wants it to. > > We can't _stop_ scanning when we're successfully connected to an AP, > otherwise we'll never get an up-to-date list of access points in our > menu, but it can be far less often than we do it now. I still think > that if the normalized scan list changes, we need to bump the next scan > up earlier as well, to ensure validity of the scan list. The thing is, > if the menu lists an access point that actually is no longer there, the > user technically cannot connect to it, but its still in the menu. > _Also_ not good from a users perspective. > > At a future point we may be able to filter out access points that are at > the edge of the card's range, but under Linux right now the drivers > simply suck too much. Its hard enough getting usable signal strength > for the _current_ access point, let alone for scanned access points. agreed. the drivers are not perfect, but usable. i'm annoyed by the fact that my current madwifi driver does not display signal strengths in iwlist scan. however, it seems to me that the card _is_ scanning for changes in AP's constantly without disconnecting (ie, in wavemon i see changes in the AP list, but no interruptions in the connection). i assume that is driver specific? right now, i'm more or less happy using ifplugd and connecting to secure networks by hand. it'd be great to have a wireless solution that works in a user friendly way, though. Sven ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Mon, 2005-01-31 at 10:37 -0500, Sven wrote: > > There are really just two things to consider. We can't _never_ scan, > > and we can't always scan. We need to find some algorithm for NM of > > balancing the two, and make that algorithm tunable on-the-fly. We want > > to do a few scans on startup of course, to build the initial list. And > > perhaps we want to scan more often when the card isn't in use or when > > its not associated, for example. > it seems to me that if the card is connected to an AP, it should not try to > scan that much/often unless the user wants it to. We can't _stop_ scanning when we're successfully connected to an AP, otherwise we'll never get an up-to-date list of access points in our menu, but it can be far less often than we do it now. I still think that if the normalized scan list changes, we need to bump the next scan up earlier as well, to ensure validity of the scan list. The thing is, if the menu lists an access point that actually is no longer there, the user technically cannot connect to it, but its still in the menu. _Also_ not good from a users perspective. At a future point we may be able to filter out access points that are at the edge of the card's range, but under Linux right now the drivers simply suck too much. Its hard enough getting usable signal strength for the _current_ access point, let alone for scanned access points. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Mon, 2005-01-31 at 10:00 -0500, Dan Williams wrote: > On Sun, 2005-01-30 at 17:11 -0500, Sven wrote: > > NetworkManager does not work well with my mini Atheros abg card. it can > > associate ok, but then roughly every minute it looses the connection and > > the card is scanning/cycling through all channels for about 10 secs or > > so. during that time iwconfig gives "FF:...:FF" as the AP. it cycles > > through the channels 3 times, and the associates with the original AP > > again. > > Sven, > > Ok, I took a look with this card. The behavior you're seeing is pretty > much expected, that's the card running its wireless scan so we can > update our list of access points. The thing you may not be aware of is > that the card supports so many frequencies that it takes a _long_ time > to scan all the channels (somewhere around 10s it seems, from this > card). Obviously, since the card isn't associated during that time, it > cannot send or receive traffic. > > Some observations: > > 1) NetworkManager starts with a 20s scan interval, and if the aggregate > list of access points does not change with each successive scan, it > backs the scan interval back to 60s. If the list changes (an AP drops > off after the 2m "last seen" check, or a new one appears), the scan > interval jumps back to 20s. > IMHO this is a lot of scanning & disconnection from the AP. I forced the card in b-mode only, and it's still scanning and disconnecting for ~4s every 60s. > 2) Since the card takes so long to scan, and since no traffic can flow > during the scan, it doesn't work very well from a user's perspective. Word! what bothers me most is the "dead time" of disassociation. > 3) I don't mind tuning the scan algorithm. I can figure out how many > channels the card supports, and if its over 14 that means its an a/b/g > card right now. I then know that it will take a while to scan, since > the time that a card must remain on a channel to sense the AP's beacon > does have a lower bound (a couple hundred ms, something like 150ms - > 200ms). Perhaps if the card is an a/b/g card, I should step the scan > interval back 20s rather than 10. whatever works... i'm just a user ;-) > 4) There are smarter ways of doing this. For example, no card will do > well with streaming video/audio when scanning. So perhaps > NetworkManager should monitor the amount of traffic on the card, and if > its above a certain level, then put off the scan. If more than 4 scans > (for example) have been deferred, then force a scan at the next > interval. This would mean far fewer interruptions. I assume the kernel > has some way of relaying traffic statistics to us. not just audio streaming. i ssh a lot, and scanning time means dead time. > There are really just two things to consider. We can't _never_ scan, > and we can't always scan. We need to find some algorithm for NM of > balancing the two, and make that algorithm tunable on-the-fly. We want > to do a few scans on startup of course, to build the initial list. And > perhaps we want to scan more often when the card isn't in use or when > its not associated, for example. it seems to me that if the card is connected to an AP, it should not try to scan that much/often unless the user wants it to. > I think I've got a few ideas on how to do this, but at the moment there > are a few other things that need to get done first... Patches would be > accepted though. If you'd like to file a bug at bugzilla.gnome.org or > bugzilla.redhat.com just to keep me reminded, that would be helpful. > Say something like "RFE: Tuneable scanning algorithm". done. thanks, Sven ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Sun, 2005-01-30 at 17:11 -0500, Sven wrote: > NetworkManager does not work well with my mini Atheros abg card. it can > associate ok, but then roughly every minute it looses the connection and > the card is scanning/cycling through all channels for about 10 secs or > so. during that time iwconfig gives "FF:...:FF" as the AP. it cycles > through the channels 3 times, and the associates with the original AP > again. Sven, Ok, I took a look with this card. The behavior you're seeing is pretty much expected, that's the card running its wireless scan so we can update our list of access points. The thing you may not be aware of is that the card supports so many frequencies that it takes a _long_ time to scan all the channels (somewhere around 10s it seems, from this card). Obviously, since the card isn't associated during that time, it cannot send or receive traffic. Some observations: 1) NetworkManager starts with a 20s scan interval, and if the aggregate list of access points does not change with each successive scan, it backs the scan interval back to 60s. If the list changes (an AP drops off after the 2m "last seen" check, or a new one appears), the scan interval jumps back to 20s. 2) Since the card takes so long to scan, and since no traffic can flow during the scan, it doesn't work very well from a user's perspective. 3) I don't mind tuning the scan algorithm. I can figure out how many channels the card supports, and if its over 14 that means its an a/b/g card right now. I then know that it will take a while to scan, since the time that a card must remain on a channel to sense the AP's beacon does have a lower bound (a couple hundred ms, something like 150ms - 200ms). Perhaps if the card is an a/b/g card, I should step the scan interval back 20s rather than 10. 4) There are smarter ways of doing this. For example, no card will do well with streaming video/audio when scanning. So perhaps NetworkManager should monitor the amount of traffic on the card, and if its above a certain level, then put off the scan. If more than 4 scans (for example) have been deferred, then force a scan at the next interval. This would mean far fewer interruptions. I assume the kernel has some way of relaying traffic statistics to us. There are really just two things to consider. We can't _never_ scan, and we can't always scan. We need to find some algorithm for NM of balancing the two, and make that algorithm tunable on-the-fly. We want to do a few scans on startup of course, to build the initial list. And perhaps we want to scan more often when the card isn't in use or when its not associated, for example. I think I've got a few ideas on how to do this, but at the moment there are a few other things that need to get done first... Patches would be accepted though. If you'd like to file a bug at bugzilla.gnome.org or bugzilla.redhat.com just to keep me reminded, that would be helpful. Say something like "RFE: Tuneable scanning algorithm". Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Sun, 30 Jan 2005 18:09:43 -0500, Dan Williams wrote: > On Sun, 30 Jan 2005, Sven wrote: >> NetworkManager does not work well with my mini Atheros abg card. it can >> associate ok, but then roughly every minute it looses the connection and >> the card is scanning/cycling through all channels for about 10 secs or >> so. during that time iwconfig gives "FF:...:FF" as the AP. it cycles >> through the channels 3 times, and the associates with the original AP >> again. > > I've committed some updates to CVS that may fix this, but Monday at work a > coworker has an Atheros abg card that I'll test out and see if I can come > up with a definite fix. > > FWIW, how far away from the AP are you? > Same problem here. I am at 1 meter from the AP. Manual configuration works just fine (without NM ). ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
Dan Williams wrote: > > I've committed some updates to CVS that may fix this, but Monday at work a > coworker has an Atheros abg card that I'll test out and see if I can come > up with a definite fix. NM isn't pushing my Atheros into mode 1 (802.11a) mode anymore, and the NIC associates with my AP properly now, but NM isn't finding out the NIC has hardware link. It sits forever waiting. This is a definite improvment over getting put into 802.11a mode. I'm glad to see progress! --[Lance] -- Celebrate The Circle http://www.celebratethecircle.org/ Carolina Spirit Quest http://www.carolinaspiritquest.org/ My LiveJournal http://www.livejournal.com/users/labrown/ GPG Fingerprint: 409B A409 A38D 92BF 15D9 6EEE 9A82 F2AC 69AC 07B9 CACert.org Assurer ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Sun, 2005-01-30 at 18:09 -0500, Dan Williams wrote: > On Sun, 30 Jan 2005, Sven wrote: > > NetworkManager does not work well with my mini Atheros abg card. it can > > associate ok, but then roughly every minute it looses the connection and > > the card is scanning/cycling through all channels for about 10 secs or > > so. during that time iwconfig gives "FF:...:FF" as the AP. it cycles > > through the channels 3 times, and the associates with the original AP > > again. > > I've committed some updates to CVS that may fix this, but Monday at work a > coworker has an Atheros abg card that I'll test out and see if I can come > up with a definite fix. > > FWIW, how far away from the AP are you? when i tried last, 5 feet from a netgear wgr614v4 in g mode. the same happened (with older versions of NM) at various distances with an ap in b mode. looking forward to a fix, Sven ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi trouble
On Sun, 30 Jan 2005, Sven wrote: > NetworkManager does not work well with my mini Atheros abg card. it can > associate ok, but then roughly every minute it looses the connection and > the card is scanning/cycling through all channels for about 10 secs or > so. during that time iwconfig gives "FF:...:FF" as the AP. it cycles > through the channels 3 times, and the associates with the original AP > again. I've committed some updates to CVS that may fix this, but Monday at work a coworker has an Atheros abg card that I'll test out and see if I can come up with a definite fix. FWIW, how far away from the AP are you? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Atheros abg / madwifi trouble
NetworkManager does not work well with my mini Atheros abg card. it can associate ok, but then roughly every minute it looses the connection and the card is scanning/cycling through all channels for about 10 secs or so. during that time iwconfig gives "FF:...:FF" as the AP. it cycles through the channels 3 times, and the associates with the original AP again. i'm using: * Fedora Core 3, kernel 2.6.10-1.753, up2date, * CVS NetworkManager from 20050130, * madwifi driver snapshot from 20050125, * wireless tools 28pre4 card details: 02:0a.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01) Subsystem: Atheros Communications, Inc. Netgate 5354MP ARIES a (108Mb turbo)/b/g MiniPCI Adapter Flags: bus master, medium devsel, latency 168, IRQ 11 Memory at 2001 (32-bit, non-prefetchable) [size=64K] Capabilities: [44] Power Management version 2 any help with this issue is greatly appreciated. unless this problem is fixed NetworkManager is pretty useless for me. thanks, Sven ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
