Re: Scanning etc with Airport Driver
On Wed, 10 Jan 2007 11:52:34 +1100 Dean Hamstead [EMAIL PROTECTED] wrote: Hi, whats the status with scanning in the airport/orinoco driver? has anything been finalized and committed to the kernel? I use the debian kernel 2.6.18-3 here on a Pismo with Airport card and scanning worked out of the box (iwlist scanning). Also kismet worked with the orinoco driver. It instantly found my Airport station but also detected a steadily increasing number of phantom networks with invalid data (floating hardware address and no information about the used channel). I think this are non-WLAN devices using the 2.4GHz band and wrongly detected by airport/orinoco-driver/kismet. Has anyone seen a similar phenomenon? Best Regards Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Scanning etc with Airport Driver
i was actually looking for iwlist ethX ap but scanning seems to do what i want hmm, *looks at man page* i see ap is depreciated. good work me ;) thanks matthias Dean Matthias Grimm wrote: On Wed, 10 Jan 2007 11:52:34 +1100 Dean Hamstead [EMAIL PROTECTED] wrote: Hi, whats the status with scanning in the airport/orinoco driver? has anything been finalized and committed to the kernel? I use the debian kernel 2.6.18-3 here on a Pismo with Airport card and scanning worked out of the box (iwlist scanning). Also kismet worked with the orinoco driver. It instantly found my Airport station but also detected a steadily increasing number of phantom networks with invalid data (floating hardware address and no information about the used channel). I think this are non-WLAN devices using the 2.4GHz band and wrongly detected by airport/orinoco-driver/kismet. Has anyone seen a similar phenomenon? Best Regards Matthias -- WWW: http://deanpatrick.tk LAN: http://www.fragfest.com.au EMAIL: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Scanning etc with Airport Driver
Hi All, whats the status with scanning in the airport/orinoco driver? has anything been finalized and committed to the kernel? Dean -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
mixed version of airport driver
Hello I compiled Ben's kernel (rsynced on the 18th of Dec) with the airport, orinoco and hermes as modules. Further I apt-got the wireless-tools (testing). Now, using iwconfig eth1, I got the following message: Warning: Driver for device eth1 has been compiled with version 14 of Wireless Extension, while this program is using version 15. Some things may be broken... eth1 IEEE 802.11-DS ESSID: Nickname:HERMES I Mode:Managed Frequency:2.422GHz Access Point: 00:00:00:00:00:00 Bit Rate:11Mb/s Tx-Power=15 dBm Sensitivity:1/3 Retry limit:4 RTS thr:off Fragment thr:off Encryption key:off Power Management:off How can I install the right driver version? BTW: As an accesspoint I use a Netgear MR314. Merry Christmas!! Roland Wegmann [EMAIL PROTECTED]
Re: mixed version of airport driver
On Tue, Dec 24, 2002 at 01:40:55PM +0100, Roland Wegmann wrote: I compiled Ben's kernel (rsynced on the 18th of Dec) with the airport, orinoco and hermes as modules. Further I apt-got the wireless-tools (testing). Now, using iwconfig eth1, I got the following message: Warning: Driver for device eth1 has been compiled with version 14 of Wireless Extension, while this program is using version 15. Some things may be broken... [...] I recompiled wireless-tools ... I did ... apt-get source wireless-tools edit the Makefile: There is a variable,FORCE_TO_USE_VERSION = 15 or similar. I changed it to use 14 and typed: debuild I installed the package with dpkg -i and put it on hold. It works for me Regards Jan
Re: mixed version of airport driver
On Tue, Dec 24, 2002 at 01:40:55PM +0100, Roland Wegmann wrote: I compiled Ben's kernel (rsynced on the 18th of Dec) with the airport, orinoco and hermes as modules. Further I apt-got the wireless-tools (testing). Now, using iwconfig eth1, I got the following message: Warning: Driver for device eth1 has been compiled with version 14 of Wireless Extension, while this program is using version 15. Some things may be broken... [...] I recompiled wireless-tools ... I did ... apt-get source wireless-tools edit the Makefile: There is a variable,FORCE_TO_USE_VERSION = 15 or similar. I changed it to use 14 and typed: debuild I installed the package with dpkg -i and put it on hold. It works for me Regards Jan The only things I ever compiled are kernels. So I have no expierence in compiling 'normal' packages. Can I treat the source of wireless-tools like the source of modules (means create a directory in /usr/src/ named wireless-tools) or can I compile them anywhere in the file tree? What does 'put it on hold' mean? Thanks Jan for helping me so far Roland Wegmann [EMAIL PROTECTED]
Re: airport driver
On Sun, Mar 04, 2001 at 04:33:25PM -0800, Alan DuBoff wrote: I have woody installed on a PowerBook (most recent G3 before new titaniam G4, the 2000 model, the Firewire model, Pismo, etc...call it what you like), which has an airport card in it that I would really like to use. I'm using a 2.2.18 kernel, and it is linked into /usr/src/linux. I grabbed the airport driver from www.penguinppc.org/~benh but can't get it to compile. Do I need to incorporate that directory into my kernel tree and be in: /usr/src/linux/modules/pcmcia-cs/wireless Or what is the magic trick to get the airport to compile? I've got most things worked out and the PowerBook rocks, and the last few things I'll resort to this list for help. HELP!g hmm well I had problems getting my airport driver from ben's site to compile when I got my airport card for my same model pismo, however I was using it with 2.4.*, anyway I posted a quick hack of a patch to linuxppc-dev list that would allow trhe thing to compile and be used, so I have been using that hapily since. You may want to have a look back in that mailing list's archive and use the patch or not, the two changes were pretty obvious. The change from using dev-name = s; to strncpy (dev-name, s, strlen (whatever)) is a 2.4 ism, the other thing was just something stopping it from building, anyway good luck. See You Steve -- [EMAIL PROTECTED] http://wibble.net/~sjh/ Look Up In The Sky Is it a bird? No Is it a plane? No Is it a small blue banana? YES
Re: airport driver
Steven Hanley wrote: hmm well I had problems getting my airport driver from ben's site to compile when I got my airport card for my same model pismo, however I was using it with 2.4.*, anyway I posted a quick hack of a patch to linuxppc-dev list that would allow trhe thing to compile and be used, so I have been using that hapily since. You may want to have a look back in that mailing list's archive and use the patch or not, the two changes were pretty obvious. The problems I was getting were with redefinitions, and I tried pathing in /usr/src/linux/include as some stuff was called with linux/xxx.h which were located in /usr/src/linux/include/linux, but that didn't help and gave other redefinition errors. I'm using a 2.2.18 kernel, and even though I would like to upgrade to the 2.4.x kernel, I want to continue to try and get e2compr going (the kernel patch worked for 2.2.18 with one minor mod which I have sent a message to the maintainers), but the patch to the e2fsprogs didn't compile after it was patched. Anyway, I use this to compile a compressed image that I can flash over the net, and would like to be able to do that if possible. The change from using dev-name = s; to strncpy (dev-name, s, strlen (whatever)) is a 2.4 ism, the other thing was just something stopping it from building, anyway good luck. Thanks for the info Steve, I'll dig around the linuxppc-dev list and see if I can find your patch. -- Alan DuBoff Software Orchestration, Inc.
airport driver
I have woody installed on a PowerBook (most recent G3 before new titaniam G4, the 2000 model, the Firewire model, Pismo, etc...call it what you like), which has an airport card in it that I would really like to use. I'm using a 2.2.18 kernel, and it is linked into /usr/src/linux. I grabbed the airport driver from www.penguinppc.org/~benh but can't get it to compile. Do I need to incorporate that directory into my kernel tree and be in: /usr/src/linux/modules/pcmcia-cs/wireless Or what is the magic trick to get the airport to compile? I've got most things worked out and the PowerBook rocks, and the last few things I'll resort to this list for help. HELP!g -- Alan DuBoff Software Orchestration, Inc.
airport driver
Hi, I've got some problem's with airport on a powerbook G3 (pismo) with an Apple airport-card plugged inside. -=-=-=-=-=-=-=-=-=- kernel-side -=-=-=-=-=-=-=-=-=- I'm running kernel 2.2.18pre17-ben1 (rsync'ed from ppc.samba.org::linux-pmac-benh) , freshly compiled after ennablig Wireless LAN (non-hamradio) yoko:~ uname -a Linux yoko 2.2.18pre17-ben1 #1 Tue Nov 28 13:57:41 CET 2000 ppc unknown -=-=-=-=-=-=-=-=-=- airport-driver side -=-=-=-=-=-=-=-=-=- I also donwloaded the airport driver from here: URL:http://ppclinux.apple.com/~benh/airport_0.9.3.tar.gz compiled the module, changed the owner of airport.o to root and finaly dropped airport.o on /lib/modules/2.2.18pre17-ben1/net/ -=-=-=-=-=-=-=-=-=- BUT, cause there's a but -=-=-=-=-=-=-=-=-=- insmod airport gives me an error about loops_per_sec, here is the output yoko:~ sudo insmod airport Using /lib/modules/2.2.18pre17-ben1/net/airport.o /lib/modules/2.2.18pre17-ben1/net/airport.o: unresolved symbol loops_per_sec what I'm doing wrong thank's in advance Eric -- MA QUESTION EST LA SUIVANTE: quelqu'un aurait-il un login et mot de passe a me preter en attendant que j'obtienne les miens Lundi. -+- FM in GNU : avis aux cyber crédules -+-
Re: airport driver
On Tue, 28 Nov 2000, Eric Deveaud wrote: Hi, I've got some problem's with airport on a powerbook G3 (pismo) with an Apple airport-card plugged inside. -=-=-=-=-=-=-=-=-=- kernel-side -=-=-=-=-=-=-=-=-=- I'm running kernel 2.2.18pre17-ben1 (rsync'ed from ppc.samba.org::linux-pmac-benh) , freshly compiled after ennablig sory about the confusion, I rsync from penguinppc.org::linux-pmac-benh Eric -- Selon les logs, il y a des pertes de porteuses, mais surtout des requêtes de déconnexion qui viennent de votre machine. Il faut se rappeler que windows 95 est un systeme bio-dégradable. -+- Support technique HOL in: Guide du Cabaliste Usenet - CQFD ! -+-
