Advertisement
Mine's an Intel PCI 2100 integrated device. Intel has a semi-official driver project at sourceforge and has made firmware available as well. Built and/or installed these and the device becomes active but I can't get the network connection active. Also, there's a secondary project
that it depends on and they don't build right separately but do when I build an older version where they were integrated.
Tried setting up an old wifi gateway we have with WEP off just to get a handle on basic connecting and using a PCMCIA wife card from my wife's laptop but no more joy.
Patience evaporating...
that it depends on and they don't build right separately but do when I build an older version where they were integrated.
Tried setting up an old wifi gateway we have with WEP off just to get a handle on basic connecting and using a PCMCIA wife card from my wife's laptop but no more joy.
Patience evaporating...
Advertisement
Advertisement
-
Re: Wifi, WEP, etc woes
Mon, September 12, 2005 - 5:19 PMI have an Intel 2200, same driver project.
My stock ubuntu kernel includes the drivers:
% find /lib/modules/2.6.10-5-k7/kernel -name \*ipw\*
/lib/modules/2.6.10-5-k7/kernel/drivers/net/wireless/ipw2100
/lib/modules/2.6.10-5-k7/kernel/drivers/net/wireless/ipw2100/ipw2100.ko
/lib/modules/2.6.10-5-k7/kernel/drivers/net/wireless/ipw2200
/lib/modules/2.6.10-5-k7/kernel/drivers/net/wireless/ipw2200/ipw2200.ko
/lib/modules/2.6.10-5-k7/kernel/drivers/usb/serial/ipw.ko
It looks like Debian distributes a kernel driver source package in their contrib repository:
packages.debian.org/testing/...00-source
installing this and building it with your kernel is probably the most reliable thing to do. But if you've grabbed your own from sourceforge and it loads fine (any dmesg errors?) we could move on to seeing if can see any networks with iwlist or iwconfig or if it registers as an interface at all with ifconfig.
The currrent issues with the ipw2100/2200 drivers are:
Ubunutu has old versions of the drivers that have issues with WPA. This is fixed in newer versions. Debian is likely tracking the newer one.
The ipw2100/2200 drivers can't set the centrino into 'promiscuous' mode, so really cool wardriving apps like Kismet don't work. This is unresolved AFAIK. -
-
Re: Wifi, WEP, etc woes
Mon, September 12, 2005 - 5:40 PMHey AJ, thanks for the response:
<<installing this and building it with your kernel is probably the most reliable thing to do. But if you've grabbed your own from sourceforge and it loads fine (any dmesg errors?) we could move on to seeing if can see any networks with iwlist or iwconfig or if it registers as an interface at all with ifconfig.>>
Since my original post, I've made some progress. I had an older wifi router that I set up with security off and I can pretty much connect to that at will now, with WEP off. Now working through what I need to do to make it work with WEP on.
One unsettling bit is that I'm winging it and basically doing what I need to connect by trial and error. There's a wireless.opts file in /etc/pcmcia which I'm thinking doesn't need to be set; the other wireless.opts file I've read about is in /etc/rc.d but my installation wasn't created with that dir.
What seems to work (and this may seem lame, using GUI tools instead of just iwconfig) is setting up the basic eth1 device in the Debian networking tool and then using the KDE wifi tool to set options, with the two matching by network SSID name. Not sure if there's a better/smarter way. Depending on settings, I have seen the eth1 wifi card come up autoatically or brought it up with ifconfig, set some options with iwconfig.
<<The currrent issues with the ipw2100/2200 drivers are:
Ubunutu has old versions of the drivers that have issues with WPA.>>
Right now, I'm just working on the WEP issue, I'll look at the better security there once I have it going for awhile.
<<The ipw2100/2200 drivers can't set the centrino into 'promiscuous' mode, so really cool wardriving apps like Kismet don't work. This is unresolved AFAIK.>>
That would be a cool thing to mess around with!
-