Thread: [Ndiswrapper-general] iwconfig shows no wireless extension
Status: Beta
Brought to you by:
pgiri
From: Gerhard H. <g.h...@in...> - 2004-01-28 19:01:38
|
I tried both ndiswrapper 0.4 and 0.4+CVS (28.01.2004) with both supplied drivers for a Intel Pro/2100 Wireless card (on a Acer Travelmate 803LMi) The Module and driver is loaded, (showing wlan1: ndiswrapper ehernet device xx:xx:xx:xx:xx) but I cannot set any wireless options. e.g. changing the ESSID results in: iwconfig wlan1 essid MyNetwork >Error for wireless request "Set ESSID" (8B1A) : > Set failed on device wlan1 ; invalid argument I'm on a 2.4.24 kernel, iwconfig is: >Version 25 >Compatible with Wireless Extension v15 or earlier >Currently compiled wirh Wireless Extension v15. The interface is shown with ifconfig, but wireless options can not be set. Is this a know problem ? If you need more debug information (DEBUG enabled) pls drop me a note. Thanks Gerhard -- Gerhard Hintermayer mailto:g.h...@in... http://www.inode.at/g.hintermayer mobile: +43 664 1537810 |
From: Pontus F. <pon...@ta...> - 2004-01-28 19:07:16
|
On Wed, 2004-01-28 at 20:07, Gerhard Hintermayer wrote: > The interface is shown with ifconfig, but wireless options can not be set. > Is this a know problem ? If you need more debug information (DEBUG > enabled) pls drop me a note. You have probably not enabled wireless lan in you kernel (CONFIG_NET_RADIO) Pontus |
From: Gerhard H. <g.h...@in...> - 2004-01-28 21:06:46
|
Pontus Fuchs wrote: > On Wed, 2004-01-28 at 20:07, Gerhard Hintermayer wrote: > > >>The interface is shown with ifconfig, but wireless options can not be set. >>Is this a know problem ? If you need more debug information (DEBUG >>enabled) pls drop me a note. > > > You have probably not enabled wireless lan in you kernel > (CONFIG_NET_RADIO) > > Pontus > > You were right, kernel recompiled and card works, at least for a while. Then system hangs :( ,sometimes right after bringing card up, sometimes after several minutes ... Gerhard |
From: Giridhar P. <gi...@lm...> - 2004-01-28 21:23:54
|
Check if you have SMP or Hyperthreading enabled; if you have, disable it (them). Read the FAQ, too. -- Giri |
From: Gerhard H. <g.h...@in...> - 2004-01-28 21:40:03
|
Giridhar Pemmasani wrote: > Check if you have SMP or Hyperthreading enabled; if you have, disable > it (them). Read the FAQ, too. > I do not have SMP enambled. How can hyperthreading be disabled in the kernel. Select a 386 cpu ? Then I'd better not use ndiswrapper, I'd like to take advantage of my Centrino CPU ;-) Gerhard |
From: Stefan <ste...@gm...> - 2004-01-31 03:17:22
|
> I do not have SMP enambled. > How can hyperthreading be disabled in the kernel. Select a 386 cpu ? > Then I'd better not use ndiswrapper, I'd like to take advantage of my > Centrino CPU ;-) Centrino doesn't use Hyperthreading. Just Disable SMP, and select a P4 or P3 CPU. I use "pentium4" for my Centrino and it workd fine - ndiswrapper too /Stefan |
From: Tomas S. <sz...@pi...> - 2004-01-31 04:09:15
|
On Jan-29 2004, Thu, 21:24 +0000 Stefan D=F6singer <ste...@gm...> wrote: > I use "pentium4" for my Centrino=20 That's wrong, though -- you should be using p3. --=20 Tomas Szepe <sz...@pi...> |
From: Timo <ti...@ti...> - 2004-01-31 04:32:42
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Mittwoch, 28. Januar 2004 22:40 schrieb Gerhard Hintermayer: > Giridhar Pemmasani wrote: > > Check if you have SMP or Hyperthreading enabled; if you have, disable > > it (them). Read the FAQ, too. > >=20 >=20 > I do not have SMP enambled. > How can hyperthreading be disabled in the kernel. Select a 386 cpu ?=20 > Then I'd better not use ndiswrapper, I'd like to take advantage of my=20 > Centrino CPU ;-) >=20 > Gerhard if you have a Pentium M, you can't use SMP at all. (There is _no_ Centrino = CPU) Just select Pentium 4 and have SMP disabled. Timo =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQBlvXEn74FOC+06tAQLaQwf/XmuKGwVnIQfFvyW7xe2hvt7JNgmkXEhs 05MGqLhydROQyDeJI+iksLYtO5Ay+whs5gsTkpF1DT/UwbLbsVbh/DJ2uwb2wF4o HyXkHDwfiW0+dpZILT/TgGd6ZDUakffIPnpSDxLH3bLZSlulLXCLcDa45X+NN57F cJh7Tx3MwMbS1qn2F6UQbbxenZCx6PGu+rffBa/ZYqp9d3FdTNuSwpMJXT4ueZQJ qPLp3PHo03guvLBLcR2MVNgjaSWxvH8PPYCjnnx0WFnqJB7tgCIRRjoZfENVlzFi C/LRU5EoXkkXdhKKDjHk4Ly9Bx+vBBpNkKUgXLErFSNICtCMLXfvYA=3D=3D =3DRbss =2D----END PGP SIGNATURE----- |
From: Gerhard H. <g.h...@in...> - 2004-01-30 17:46:44
|
Giridhar Pemmasani wrote: > Check if you have SMP or Hyperthreading enabled; if you have, disable > it (them). Read the FAQ, too. > Good tip, If I'd read the FAQ first, that'd save me a lot of time. But thanks for all the patient advice from the list instead of RTFM posts. I disabled now hyperthreading (passed noht to kernel), SMP wasn't enabled anyhow, ACPI is in kernel and enabled (and working), but I still get regular hangs. All of the time they occur right after bringing the card up. I use 128 bit WEP (this is at home), I'll try 40 bit at work and see, if there's any diffence. Gerhard |
From: Gerhard H. <g.h...@in...> - 2004-01-29 12:33:37
|
> > Another thing: Use the driver for the Centrino chipset available from > 'supported chipsets' page, not what comes with your windows. > > -- > Giri That are the drivers I use. Now I'm at work (40 Bit WEP with broadcast of ESSID - versus 128 bit with no broadcast at home) but the system still hangs immediately, after I enable the card :-( Fiddling around with the channel setting and - voila - it works. So I'm supposed to *never ever* set the channel manually, or else the system hangs ! This should go into the FAQ: Setting the channel manually may hang your system ! Thanks again for all the hints. Gerhard |
From: Gerhard H. <g.h...@in...> - 2004-01-30 14:32:51
|
Giridhar Pemmasani wrote: >Can you try the following patch and see if you can set the channel >without getting oops? This is against the cvs code. If you are using >other versions, it should be easy to figure out what to do. > >BTW, you don't really need to set the channel; the card automatically >picks up what the AP is using. > > > >------------------------------------------------------------------------ > > > > This is getting quite strange. Taking the same ndiswrapper configuration as at work. Only the access point is different (Netgear MR814). Following things do occur: 128 bit WEP, disabled broadcast of SSID - immediate hang 64 bit WEP, disabled broadcast of SSID - immediate hang 64 bit WEP, enabled broadcast of SSID - hang after several minutes, working connection up to this point While at work (64 bit WEP, broadcast of SSID, Accesspoint ???) there were absolutely no problems ! Do you still want me to test the patch you sent me, I don't think the problem here is comparable to the problem at work. There the driver worked after removing the iwconfig frequency setting, but here I don't even use that option, and the driver still hangs the system. I will do a test with the patch you sent me tomorrow at work, but here at home that will not work. Too bad, that absolutely nothing goes into /var/log/messages, except of course the NDis* UNIMPLEMENTED messages and the wlan*: ndiswrapper ethernet device xx:xx:xx:xx:xx line :-( Gerhard |
From: Tony W. <ton...@us...> - 2004-01-30 20:09:11
|
Gerhard Hintermayer wrote: > This is getting quite strange. Taking the same ndiswrapper configuration > as at work. Only the access point is different (Netgear MR814). > Following things do occur: > 128 bit WEP, disabled broadcast of SSID - immediate hang > 64 bit WEP, disabled broadcast of SSID - immediate hang > 64 bit WEP, enabled broadcast of SSID - hang after several minutes, > working connection up to this point > > While at work (64 bit WEP, broadcast of SSID, Accesspoint ???) there > were absolutely no problems ! It might be worth checking for new firmware for your troublesome WAP. I found that my D-Link WAP didn't like Centrino chipsets (and some other Intel wireless cards) and reset itself every few seconds! After a bit of a search and some flashing, everything is fine! HTH, Tony |
From: Giridhar P. <gi...@lm...> - 2004-01-31 06:05:28
|
Can you try the new code (not the patch) that I sent (as tar.bz2 file)? That has missing functions and is known to work with Centrino chipset. Ndis drivers insist on ssid broadcast (as mentioned in FAQ). If your machine locks hard, it is quite likely the problem is due to some ndis function (instead of wrapper functions). -- Giri |