Thanks Fabian, There seem to be a number of different ways of installing the ipw2200 firmware and as I've said already I've tried puttting the .fw files into the firmware directory - why doesn't this work? What is actually the best/recommended way of installing the firmware in CentOS 5 please? - not too complicated please as I'm a linux enthusiast but not a great expert!
Andy
Original Message: ----------------- From: Fabian Arrotin fabian.arrotin@arrfab.net Date: Mon, 06 Aug 2007 12:57:28 +0200 To: centos@centos.org Subject: Re: [CentOS] ipw220 wireless firmware for CentOS 5
On Mon, 2007-08-06 at 05:33 -0400, andy.allen@virgin.net wrote:
OK, I've downloaded and unzipped the firmware files in ipw2200-fw-3.0.tgz - so I have 4 files: ipw2200-bss.fw, ipw2200-ibss.fw, ipw2200-sniffer.fw and LICENSE.ipw2200-fw, all of which I've placed in the /lib/firmware directory. Unfortunately, the instructions in README.ipw2200 and INSTALL are not clear as to what to do next. I'm using CentOS 5 on my (Dell) laptop so setting-up wireless networking
should
be reasonably straightforward - shouldn't it? Any help much appreciated - I'm a real linux fan, but it grieves me to say that, in this case, "wireless works much better in Windows XP!"
Use the ipw2200-firmware rpm from the RPMForge repo (see http://wiki.centos.org/Repositories) .... Then you'll be able to use/configure the ipw2200 device . You can use for example NetworkManager to automatically configure your network if you have a laptop ...
On Tue, 2007-08-07 at 07:20 -0400, andy.allen@virgin.net wrote:
Thanks Fabian, There seem to be a number of different ways of installing the ipw2200 firmware and as I've said already I've tried puttting the .fw files into the firmware directory - why doesn't this work? What is actually the best/recommended way of installing the firmware in CentOS 5 please? - not too complicated please as I'm a linux enthusiast but not a great expert!
I have successfully used both the RPMforge and ATrpms packages for IPW2200 on my laptop. If you are using packages from either repo already, sticking with that one is probably the best bet. If using both or neither, depends on whether you want to go with Axel's (ATrpms) kmdl approach (may have to wait for him to build new packages after a new kernel arrives) or with Dag's (RPMforge) dkms approach (rebuilds kernel modules on-the-fly - requires development environment to be present).
Either is likely to be less complicated than trying to use the tarball, and both have the advantage of having the package manager handle updates to new firmware or drivers.
Phil
-
andy.allen＠virgin.net -
Phil Schaffner