ipw2200

Message

yim · #1 Post by **yim** » Sun 18 Jan 2009, 01:15

has anyone ever had the ipw2200 wireless to work out of the box running the network wizard, sons Thinkpad R52 has this. I got it running once with ndiswrapper but can't remember the configuration or the exact driver. His XP install has 3 folders with lan drivers. When I did have this working it worked well but can't figure out why the linux driver that comes with puppy doesn't work. I've tried all versions from pup2.14 to current the ipw2200 that is detected on boot has never worked.

If anyone has had luck please post what you did if anything special in settings. trying to connect to wpa, and have changed setting to open and to wpa2 to no avail. Have a pcmcia card EDIMAX that works perfectly on all settings with the supplied rt61 driver.

Any help would be greatly appreciated.

wireless with ipw2200 does work with xp

thanks yim

yim · #2 Post by **yim** » Tue 20 Jan 2009, 13:05

canezilla · #3 Post by **canezilla** » Tue 20 Jan 2009, 21:52

Hi yim,

I am back using puppy again because I just fixed a laptop that was being tossed out. It is an old Dell Inspiron 8200. I bought the cheapest mini-PCI card and that turns out to have been the Intel IPW2200 BG I believe.

First, I loaded Debian from a generic install CD. It knew it was there but I spent all day trying to compile the kernel and make things work... but no luck.

Second, I went to my collection of trusty puppy distro CDs I have collected throughout the years. I grabbed my latest Lighthouse Puppy 3.01g. Booted and loaded the network configure app. And to my surprise, it was ready to work!! etho=LAN, eth1=Intel ipw2200.... Are you kidding?? I thought??!! Configured, saved, then USE THIS PROFILE and I was done fighting my intel wifi card. I am writing now using puppy and my wifi.

So, In summary, I hope I can save you time by suggesting that you download Lighthouse Puppy 3.01g. It just works. Good luck to you. And THANKS to those involved in Puppy and, in particular, Lighthouse Puppy!!

Brian

canezilla · #4 Post by **canezilla** » Tue 20 Jan 2009, 21:54

Also, I did not use ndiswrapper. I didn't have to. It worked without that step.......

yim · #5 Post by **yim** » Wed 21 Jan 2009, 06:41

canezilla:

thanks for the info, I have that cd here somewhere, will let my son try it see what he thinks
I really appreciate the info

yim

tempestuous · #6 Post by **tempestuous** » Sat 24 Jan 2009, 03:24

The IPW2200 wifi device is quite old, and the Linux ipw2200 driver has been reported working in Puppy versions as far back as v1.04 in 2005.
Since it's not a new device, there are few reports on the forum about it, but HairyWill reports recent success here
http://www.murga-linux.com/puppy/viewto ... 935#267935

canezilla wrote:Also, I did not use ndiswrapper. I didn't have to.

Of course not. Puppy has an extensive collection of native drivers. ndiswrapper is rarely necessary, and should always be the last resort option.

HairyWill · #7 Post by **HairyWill** » Sat 24 Jan 2009, 06:36

tempestuous wrote:HairyWill reports recent success here
http://www.murga-linux.com/puppy/viewto ... 935#267935

My old thinkpad used ipw2200 as well and worked great with wep. I will try and crank up the security on my AP some time and see if I can still get it to work.

kirk · #8 Post by **kirk** » Mon 26 Jan 2009, 05:15

My current laptop that I've had for the past 3 years or so uses the ipw2200. Never had a problem. Sometimes the device ids for some devices overlap and the wrong kernel module gets loaded. Are you sure it's an ipw2200?

yim · #9 Post by **yim** » Mon 26 Jan 2009, 13:30

most definitely, yes

I have noticed that the ipw2200 that is detected is showing as eth1

and also I kept tinkering and did get this to work with 3.01 but not in the later puppies

memeyou · #10 Post by **memeyou** » Tue 27 Jan 2009, 08:07

ipw2200 has worked on my r51 for quiet some time now - a lot longer than iwl has anyway - one reason i chose puppy was for the 2.6.25+ kernel for it's better iwl driver.

but sometimes the autoloading modules change order and udev or whatever screws all the names up - sometimes a module has an option to fix this but ipw2200 doesn't - so, i blacklisted ipw2200 and manually load my drivers so my rc.firewall etc. don't get messed up on startup. you can blacklist and manually load drivers without even using the terminal! puppy ftw.

brymway · #11 Post by **brymway** » Fri 30 Jan 2009, 18:41

ipw2200 works great here. Loads as eth1, no problem

yim · #12 Post by **yim** » Sat 31 Jan 2009, 01:16

brymway

just out of curiosity, does the wi-fi indicator light come on with a working setup, (if you have one, that is).

Reason for asking is that the only time it worked for me the indicator light came on. If no light no connection

yim

brymway · #13 Post by **brymway** » Sat 31 Jan 2009, 18:22

The ipw2200 is on a no name laptop that has three lights on the front of the case, one for power, one for battery and one for wireless. Then on the left side of the computer I have a slider switch that manually turns the wireless on/off. When I turn that on, the wireless modem is activated and the light comes on.

muggins · #14 Post by **muggins** » Sat 28 Mar 2009, 02:14

@yim,

I've just acquired an r52, and noticed that under windows the wireless LED is active upon boot, but not with puppy. Because where I am there's not much wireless around to test it, I just tried it at a netcafe, with wireless access, & yes, when I connect to wireless the LED becomes active.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

ipw2200

ipw2200