[ATrpms-users] RE: ipw2200 and monitor mode

[Johnny Choque]

Hello,

I think that the ipw2200 atrpm was build with older wireless tools version,
maybe v26, and I think for monitor mode it's needed the latest stable
version of Wireless Tools, version 27.

Johnny

> -----Mensaje original-----
> De: Axel Thimm [mailto:Axel.Thimm at atrpms.net] 
> Enviado el: miércoles, 08 de junio de 2005 21:25
> Para: Johnny Choque
> CC: atrpms-users at atrpms.net
> Asunto: Re: ipw2200 and monitor mode
> 
> On Wed, Jun 08, 2005 at 02:13:11PM +0200, Johnny Choque wrote:
> >  
> > 
> > > De: Axel Thimm [mailto:Axel.Thimm at atrpms.net] Enviado el: 
> martes, 07 
> > > de junio de 2005 22:38
> > > Para: Johnny Choque
> > > CC: atrpms-users at atrpms.net
> > > Asunto: Re: ipw2200 and monitor mode
> > > 
> > > Hi,
> > > 
> > > On Tue, Jun 07, 2005 at 05:40:05PM +0200, Johnny Choque wrote:
> > > > Hi all,
> > > > 
> > > > I was testing the last version of atrpm's ipw2200 packages
> > > and I have
> > > > found that it does not work with monitor mode. I have used the 
> > > > following rpm
> > > > packages:
> > > > 
> > > > ipw2200-1.0.4-28.rhfc3.at.i386.rpm
> > > > ipw2200-kmdl-2.6.11-1.27_FC3-1.0.4-28.rhfc3.at.i686.rpm
> > > > ipw2200-firmware-2.3-6.at.noarch.rpm
> > > > 
> > > > When run "iwconfig eth1 mode monitor" I get the following
> > > error message:
> > > > 
> > > > Error for wireless request "Set Mode" (8B06):
> > > >      Set failed on device eth1; invalid argument
> > > > 
> > > > But the ipw2200 driver loaded for the eth1 interface is working 
> > > > without any problem.
> > > > 
> > > > For testing, I have uninstalled the atrpm packages, then I have 
> > > > installed the ipw2200 source package from 
> > > > http://ipw2200.sourceforge.net/ and now the "iwconfig eth1
> > > mode monitor" command is working correctly.
> > > > 
> > > > Do you know what the problem is?
> > > 
> > > First thing that comes to mind is module loading order. 
> Try rmmoding 
> > > ipw2200 and ieee80211* and check the output of
> > > 
> > > modprobe -nv ipw2200
> > > 
> > > Perhaps on first run of ATrpms old modules were still in place?
> > > ATrpms' rpms don't rmmod the old modules, they only 
> install the new 
> > > ones and make sure modprobe should pick them up (if 
> modprobe checks 
> > > /updates/ before other folders).
> > > 
> > > Other than that nothing comes to mind. The buildlogs are clean.
> > 
> > Hi Axel,
> > 
> > Thanks for your quick answer. I have bad news. I had the 
> opportunity 
> > to make a new install of Fedora in other laptop and the end 
> the problem is the same.
> > After install and upgrade Fedora Core 3, I cleaned all 
> files related 
> > with ipw2200 driver using "unload" and "remove-old" scripts from 
> > ipw2200-1.0.4.tgz source package. I verified that other ipw2200 
> > packages are not installed using "rpm -qa | grep ipw" 
> command. Then, I installed Atrpms'
> > rpms without any problems. When run "modprobe -nv ipw2200" 
> I get the 
> > following message:
> > 
> > insmod
> > 
> /lib/modules/2.6.11-1.27_FC3/updates/drivers/net/wireless/ipw/ieee8021
> > 1_cryp
> > t.ko
> > insmod
> > 
> /lib/modules/2.6.11-1.27_FC3/updates/drivers/net/wireless/ipw/ieee8021
> > 1.ko
> > insmod
> > 
> /lib/modules/2.6.11-1.27_FC3/updates/drivers/net/wireless/ipw/ipw2200.
> > ko
> > 
> > The ipw2200 driver is working very well, the only 
> functionality does 
> > not work is the monitor mode because I get the same error message.
> > 
> > Any ideas?
> 
> It's only guesswork, but perhaps the moditor mode is only 
> built in presence of some user-land header files? ATrpms' 
> packages are built in clean-room chroots, and all 
> requirements have to be written into
> BuildRequires: statements. So, perhaps something is missing.
> --
> Axel.Thimm at ATrpms.net
>