Thread: [Ndiswrapper-general] iwlist fails with latest CVS
Status: Beta
Brought to you by:
pgiri
From: Diwaker G. <dg...@cs...> - 2003-12-23 17:13:33
|
With the latest CVS, iwlist scan fails. The following message appears in dmesg: eth1: get statitics failed with c0010017 iwlist itself returns saying "operation not permitted" |
From: Cyril J. <cyr...@bl...> - 2003-12-23 21:55:57
|
I get the same result. Was working with release 0.3. iwlist version 25 kernel 2.4.23 RedHat 9 Intel PRO/Wireless 7100 Cyril Diwaker Gupta wrote: > With the latest CVS, iwlist scan fails. The following message appears > in dmesg: > > eth1: get statitics failed with c0010017 > > iwlist itself returns saying "operation not permitted" > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general > |
From: Giridhar P. <gi...@lm...> - 2003-12-24 00:20:25
|
I updated new code. You should get statistics again. Wait till cvs catches up. It also suggests that your driver doesn't support certain functionality. You may want to try another driver? -- Giri |
From: Cyril J. <cyr...@bl...> - 2003-12-24 15:01:42
|
I get latest CVS. Now iwlist give me my AP :) But I get this warning : "Warning : Driver for device eth1 has been compiled with version 16 of Wireless Extension, while this program is using version 15. Some things may be broken...". I'll find a rpm with Wireless-tools compiled with Wireless Extension v16 latter. When I look into kernel logs, I still get "eth1: get statistics failed with c0010017" :( Iwlist reports me a Signal level of -35 dBm and a Noise level of -256 dBm. Ifconfig reports a Signal level of -53 dBm and a Noise level of -256 dBm. Could this be correct ? Try with an other Windows driver but get the same :( Should Link Quality reports something ? Mine is always at 0/0 :( I like the Gnome Wireless Link Monitor ;) Thanks for your work Cyril Giridhar Pemmasani wrote: >I updated new code. You should get statistics again. Wait till cvs >catches up. > >It also suggests that your driver doesn't support certain >functionality. You may want to try another driver? > > > |
From: Giridhar P. <gi...@lm...> - 2003-12-24 16:22:19
|
Fixed. Wait for cvs to catch up and update. The quality that is reported right now is not really a good indicator; it is just a heuristic, as there is no one-to-one correspondence between what wireless-tools in linux want and what NDIS driver reports. So don't rely on the quality much. Signal level should be correct, though. Noise is not computed at all. Other numbers are vague indicators. -- Giri |
From: Cyril J. <cyr...@bl...> - 2003-12-25 00:12:40
|
I update to Wireless-tools using Wireless Extension v16 (a Mandrake rpm). I didn't get the warning anymore and iwconfig seems to report me "better" values for "Signal level" (210/254 and not -35 dBm like before) and for "Noise level" (0/154) but I still get "Link Quality" to 0 (0/100 exactly) and still the same kernel message "eth1: get statistics failed with c0010017" :( I try with 3 differents Windows drivers but no changes... Nobody with the same problem using Intel PRO/Wireless ? Has someone "Link Quality" working ? Thanks |
From: Giridhar P. <gi...@lm...> - 2003-12-25 04:01:56
|
The return value c0010017 means it is an invalid NDIS function call. So it seems in your case either the driver or the card doesn't support this feature. What card is it? As I said before, there is no correspondence between what NDIS driver reports and what wirelss-tools want. Sometimes conversion is possible, sometimes not. I have now added procfs interface to the cvs. With this, you can get much of the information in /proc/<interface>/stats and wep files. This interface will certainly change over time, so don't rely on it yet. It should be easy to understand what the fields mean. If it is not clear, well, you have the code :-). I will add writing support (to set the wep/ssid etc. it should be as simple as writing to a field in these files) when time permits. Using the procfs interface you can see exactly what your NDIS driver reports. -- Giri |
From: Diwaker G. <dg...@cs...> - 2003-12-24 15:21:16
|
Okay, few updates (regarding the Centrino problems thread): o I went back and tried again with 2.6.0-test11 and the latest CVS. The results are identical (i.e. sending still crashes the wireless interface) o It seems though that the problem has something to do with my router. I have a 2Wire router right now. I tried with a Belkin router from a friend, and sending works just fine. What I don't understand is how sending was working fine earlier (2.6.0-test11 and a pre 3.0 CVS). In any case, are there any suggestions on how to solve router specific issues? Diwaker Giridhar Pemmasani wrote: > Also, try to narrow it down; e.g., you say it was working with test11 > and probably 0.3 release? Then try them again and confirm it > works. Then upgrade the cvs (you can get cvs for a specific date - use > date spec option to cvs). If you point where the problems start, I can > take a look. > -- Diwaker Gupta Graduate Student, Computer Sc. and Engg. University of California, San Diego <http://www.cse.ucsd.edu/users/dgupta> |
From: Cyril J. <cyr...@bl...> - 2003-12-25 10:18:57
|
The Makefile hasn't been updated to use proc.c. /proc/eth1/stats returns me only 0 value. I have a Intel PRO/Wireless 2100 mini-PCI in my HP/Compaq NX7000 running with RedHat 9 and kernel 2.4.23. Everythings seems to run well except the "Link Quality" stats :( I know other people use ndiswrapper with Intel PRO/Wireless. Nobody has "eth1: get statistics failed with c0010017" ? Thanks and Merry Christmas Cyril Giridhar Pemmasani wrote: >The return value c0010017 means it is an invalid NDIS function >call. So it seems in your case either the driver or the card doesn't >support this feature. What card is it? > >As I said before, there is no correspondence between what NDIS driver >reports and what wirelss-tools want. Sometimes conversion is possible, >sometimes not. > >I have now added procfs interface to the cvs. With this, you can get >much of the information in /proc/<interface>/stats and wep files. This >interface will certainly change over time, so don't rely on it yet. It >should be easy to understand what the fields mean. If it is not clear, >well, you have the code :-). I will add writing support (to set the >wep/ssid etc. it should be as simple as writing to a field in these >files) when time permits. > >Using the procfs interface you can see exactly what your NDIS driver >reports. > > > |
From: Tomas S. <sz...@pi...> - 2003-12-25 17:09:05
|
On Dec-25 2003, Thu, 11:18 +0100 Cyril Jaquier <cyr...@bl...> wrote: > The Makefile hasn't been updated to use proc.c. > > /proc/eth1/stats returns me only 0 value. I have a Intel PRO/Wireless > 2100 mini-PCI in my HP/Compaq NX7000 running with RedHat 9 and kernel > 2.4.23. Everythings seems to run well except the "Link Quality" stats :( > > I know other people use ndiswrapper with Intel PRO/Wireless. Nobody has > "eth1: get statistics failed with c0010017" ? Well, I also get this kind of syslog spammage, but the card seems to work. - ndiswrapper cvs as of 2003-12-25 18:00 CET - linux 2.6.0 - slackware-current -- Tomas Szepe <sz...@pi...> |
From: Stefan <ste...@gm...> - 2003-12-25 20:39:56
|
Hello, > > /proc/eth1/stats returns me only 0 value. I have a Intel PRO/Wireless > > 2100 mini-PCI in my HP/Compaq NX7000 running with RedHat 9 and kernel > > 2.4.23. Everythings seems to run well except the "Link Quality" stats :( > > > > I know other people use ndiswrapper with Intel PRO/Wireless. Nobody has > > "eth1: get statistics failed with c0010017" ? I think the centrino driver uses some proprietary interface for the link quality. That's what the Linuxant guys say, the link quality does not work, with driverloader too. Maybe this is in the dll files or has something to do with the proset utiliy. That's also the reason for the "eth1: get statistics failed with c0010017" error I gues. /Stefan |
From: Giridhar P. <gi...@lm...> - 2003-12-25 20:55:30
|
Hi Stefan, Thanks for the info. Can one of you send me the link to the driver (for which stats don't work)? -- Giri |
From: Tomas S. <sz...@pi...> - 2003-12-25 21:03:48
|
On Dec-25 2003, Thu, 15:54 -0500 Giridhar Pemmasani <gi...@lm...> wrote: > Can one of you send me the link to the driver (for which stats don't > work)? ftp://ftp.support.acer-euro.com/notebook/TravelMate_80x/driver/winxp/intel2100b.zip -- Tomas Szepe <sz...@pi...> |
From: Tomas S. <sz...@pi...> - 2003-12-25 17:37:28
|
On Dec-24 2003, Wed, 23:00 -0500 Giridhar Pemmasani <gi...@lm...> wrote: > I have now added procfs interface to the cvs. With this, you can get > much of the information in /proc/<interface>/stats and wep files. Giridhar, I believe ndiswrapper's proc pathname should follow the convention paved by other in-kernel net drivers, that is the module should place these per-interface statistics in /proc/driver/ndiswrapper/<interface> Let's not make /proc even messier than it already is today. -- Tomas Szepe <sz...@pi...> |
From: Giridhar P. <gi...@lm...> - 2003-12-25 19:49:23
|
No, I think it should be in /proc/net/ndiswrapper/<interface>. Anyway, I haven't decided on it yet; that is why it is left in /proc as of now. I am doing a few other things, so I put it in the todo list. Will do this later. -- Giri |
From: Cyril J. <cyr...@bl...> - 2004-01-04 13:36:49
|
Can we expect to have this working in the futur ? Is there any other=20 possibility to compute link quality ? Has someone try to ask Intel about=20 this ? Ndiswrapper works fine and if we could get some link quality statistics=20 it would be perfect !!! Cyril Stefan D=F6singer wrote: >Hello, > > =20 > >>>/proc/eth1/stats returns me only 0 value. I have a Intel PRO/Wireless >>>2100 mini-PCI in my HP/Compaq NX7000 running with RedHat 9 and kernel >>>2.4.23. Everythings seems to run well except the "Link Quality" stats = :( >>> >>>I know other people use ndiswrapper with Intel PRO/Wireless. Nobody ha= s >>>"eth1: get statistics failed with c0010017" ? >>> =20 >>> >I think the centrino driver uses some proprietary interface for the link= =20 >quality. That's what the Linuxant guys say, the link quality does not wo= rk, =20 >with driverloader too. Maybe this is in the dll files or has something t= o do=20 >with the proset utiliy. That's also the reason for the "eth1: get statis= tics=20 >failed with c0010017" error I gues. > >/Stefan > > > >------------------------------------------------------- >This SF.net email is sponsored by: IBM Linux Tutorials. >Become an expert in LINUX or just sharpen your skills. Sign up for IBM'= s >Free Linux Tutorials. Learn everything from the bash shell to sys admin= . >Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick >_______________________________________________ >Ndiswrapper-general mailing list >Ndi...@li... >https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general > > =20 > |
From: Giridhar P. <gi...@lm...> - 2004-01-04 18:04:37
|
On Sun, 04 Jan 2004 14:36:32 +0100, Cyril Jaquier <cyr...@bl...> said: Cyril> Can we expect to have this working in the futur ? Is there Cyril> any other possibility to compute link quality ? Has someone Cyril> try to ask Intel about this ? Cyril> Ndiswrapper works fine and if we could get some link Cyril> quality statistics it would be perfect !!! I doubt it is possible to add quality information, as NDIS doesn't have functions for it. That is why each card manufacturer will supply another executable that shows link quality; windows itself doesn't do it. However, it is possible that the current implementation can be improved a bit to use a better heuristic. Note that the link quality reported by ndiswrapper is not compatible with that from other drivers. -- Giri |