airo-linux-general Mailing List for Linux 802.11 Aironet driver (Page 4)
Status: Inactive
Brought to you by:
breed
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(12) |
Feb
|
Mar
(4) |
Apr
(3) |
May
(1) |
Jun
(4) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2003 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
(2) |
May
(2) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(3) |
Oct
(1) |
Nov
(1) |
Dec
|
2004 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2006 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(9) |
Jun
(7) |
Jul
|
Aug
(7) |
Sep
|
Oct
(3) |
Nov
|
Dec
(13) |
2007 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Cory S. <co...@st...> - 2002-01-11 15:52:53
|
I'm having some trouble compiling my kernel after patching it with CVS code. I've tried this with a 2.4.7 and 2.4.17 kernel. If my kernel source is in /usr/src/linux and my CVS patches are in /usr/src/airo-linux, I cd to /usr/src/ and type "patch -p0 < airo-linux/kernel/patches/2.4.3.patch" and get the following errors: patching file linux/drivers/net/Config.in Hunk #1 FAILED at 254. 1 out of 1 hunk FAILED -- saving rejects to file linux/drivers/net/Config.in.rej patching file linux/drivers/net/Makefile Hunk #1 succeeded at 94 (offset 5 lines). patching file linux/drivers/net/pcmcia/Config.in Hunk #1 succeeded at 31 (offset 1 line). Hunk #2 FAILED at 40. 1 out of 2 hunks FAILED -- saving rejects to file linux/drivers/net/pcmcia/Config.in.rej patching file linux/drivers/net/pcmcia/Makefile patching file linux/Documentation/Configure.help Hunk #1 succeeded at 8650 with fuzz 1 (offset 1340 lines). After looking at linux/drivers/net/Config.in.rej it appears that ~ ling 290 something is where it wants to put the code. I don't think it's necessary anyway, because Config.in sources drivers/net/wireless/Config.in which has a spot for CONFIG_AIRO. I have no idea what linux/drivers/net/pcmcia/Config.in.rej wants to do. I can't match the rej stuff to anything in that Config file. I decided to not worry about it, because I'm not running on a laptop, and therefore not using pcmcia. Next, I move linux/drivers/net/wireless/airo.c and airo_cs.c to airo-old.c and airo_cs-old.c respectively. I copy airo-linux/kernel/airo.c airo.h and airo_cs.c to linux/drivers/net/wireless. I run "make menuconfig", configure the kernel, and then successfully run "make dep". When I run "make bzImage" I get the following errors: gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i586 -DEXPORT_SYMTAB -c auto_irq.c rm -f net.o ld -m elf_i386 -r -o net.o tulip/tulip.o airo.o Space.o setup.o net_init.o loopback.o ppp_generic.o slhc.o ppp_async.o ppp_synctty.o ppp_deflate.o bsd_comp.o auto_irq.o ld: cannot open airo.o: No such file or directory make[3]: *** [net.o] Error 1 make[3]: Leaving directory `/usr/src/linux/drivers/net' make[2]: *** [first_rule] Error 2 make[2]: Leaving directory `/usr/src/linux/drivers/net' make[1]: *** [_subdir_net] Error 2 make[1]: Leaving directory `/usr/src/linux/drivers' make: *** [_dir_drivers] Error 2 Any help would be greatly appreciated. Thanks, Cory |
From: Cory S. <co...@st...> - 2002-01-03 02:32:34
|
This is a newbie question. Any preferences or recomendations on how to pass parameters to airo.c? I'm running it statically compiled into the kernel (no modules). I was planning on adding an ether= parameter to the boot loader, but all the documentation that I can find on the ether kernel parameter doesn't indicate that it takes any parameters besides address, irq, and name. Wold you recomend ehco-ing data into the appropriate field in the /proc directory? Thanks, Cory |
From: Ian C. <id...@en...> - 2002-01-01 01:36:18
|
I'm doing some ad hoc networking with the Aironet 350 cards (firmware 4.25.23) on Linux 2.4 (with airo-Linux driver). Sometimes one or more of the nodes link quality goes to 176 and I can't get them to return to the ad hoc network. The only way I've found is to restart pcmcia and then set all the nodes to a new essid. Also, I've experimented with moving nodes in and out of range of each other, often I see the same behavior. They work, then move out of range, then move into range and they don't reconnect (the link quality stays at 176 forever). Has anyone had similar experiences? Does anyone know the reason (or a solution) to this problem? Thanks, Ian Chakeres |
From: Cory S. <co...@st...> - 2001-12-28 21:26:24
|
Thanks, that got it to compile. Cory -------- Original Message -------- Subject: Re: [Airo-linux-general] compiling for a Cisco 350 Date: Fri, 28 Dec 2001 09:33:35 -0800 (PST) From: Benjamin Reed <br...@ya...> To: co...@st..., air...@li... CC: co...@st... Yes, that is a problem we corrected in CVS, but evidently we haven't sent it to the kernel guys. The problem is that __devinitdata is on the wrong side of the =. It should be: static struct pci_device_id card_ids[] __devinitdata = { ben --- Cory Steers wrote: > Hello. I'm new to the list. I have a Cisco 350 PCI > card and an > external directional antenna comming in the mail, as > a package I'm > purchasing for high speed internet access. Don't > have the card yet, but > I thought I'd get started on updating my kernel. > I've tried a 2.4.7 and > 2.4.17 kernel, and can't get the airo driver > compiled statically into > the kernel. I can get it compiled as a module, but > I'm not confident > that it will work just because it compiled. This is > a desktop machine, > but do I need pcmcia compiled into the kernel to > make this work? I'm > just relying on the code that came with the kernels, > should I patch the > kernel with some other code? > > > Here's a snippit of the config file: > > # > # Wireless LAN (non-hamradio) > # > CONFIG_NET_RADIO=y > # CONFIG_STRIP is not set > # CONFIG_WAVELAN is not set > # CONFIG_ARLAN is not set > # CONFIG_AIRONET4500 is not set > # CONFIG_AIRONET4500_NONCS is not set > # CONFIG_AIRONET4500_PROC is not set > CONFIG_AIRO=y > # CONFIG_HERMES is not set > # CONFIG_PLX_HERMES is not set > CONFIG_NET_WIRELESS=y > > ... and here's the error messages I got: > > make -C wireless > make[3]: Entering directory > `/usr/src/linux-2.4.17/drivers/net/wireless' > make all_targets > make[4]: Entering directory > `/usr/src/linux-2.4.17/drivers/net/wireless' > gcc -D__KERNEL__ -I/usr/src/linux-2.4.17/include > -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 > -fomit-frame-pointer > -fno-strict-aliasing -fno-common -pipe > -mpreferred-stack-boundary=2 > -march=i586 -DEXPORT_SYMTAB -c airo.c > airo.c:50: parse error before `__attribute__' > airo.c:3228: warning: `airo_pci_remove' defined but > not used > make[4]: *** [airo.o] Error 1 > make[4]: Leaving directory > `/usr/src/linux-2.4.17/drivers/net/wireless' > make[3]: *** [first_rule] Error 2 > make[3]: Leaving directory > `/usr/src/linux-2.4.17/drivers/net/wireless' > make[2]: *** [_subdir_wireless] Error 2 > make[2]: Leaving directory > `/usr/src/linux-2.4.17/drivers/net' > make[1]: *** [_subdir_net] Error 2 > make[1]: Leaving directory > `/usr/src/linux-2.4.17/drivers' > make: *** [_dir_drivers] Error 2 > > Any help would be greatly appreciated. > > Thanks, > Cory > > > _______________________________________________ > Airo-linux-general mailing list > Air...@li... > https://lists.sourceforge.net/lists/listinfo/airo-linux-general __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com |
From: Benjamin R. <br...@ya...> - 2001-12-28 17:33:36
|
Yes, that is a problem we corrected in CVS, but evidently we haven't sent it to the kernel guys. The problem is that __devinitdata is on the wrong side of the =. It should be: static struct pci_device_id card_ids[] __devinitdata = { ben --- Cory Steers <co...@st...> wrote: > Hello. I'm new to the list. I have a Cisco 350 PCI > card and an > external directional antenna comming in the mail, as > a package I'm > purchasing for high speed internet access. Don't > have the card yet, but > I thought I'd get started on updating my kernel. > I've tried a 2.4.7 and > 2.4.17 kernel, and can't get the airo driver > compiled statically into > the kernel. I can get it compiled as a module, but > I'm not confident > that it will work just because it compiled. This is > a desktop machine, > but do I need pcmcia compiled into the kernel to > make this work? I'm > just relying on the code that came with the kernels, > should I patch the > kernel with some other code? > > > Here's a snippit of the config file: > > # > # Wireless LAN (non-hamradio) > # > CONFIG_NET_RADIO=y > # CONFIG_STRIP is not set > # CONFIG_WAVELAN is not set > # CONFIG_ARLAN is not set > # CONFIG_AIRONET4500 is not set > # CONFIG_AIRONET4500_NONCS is not set > # CONFIG_AIRONET4500_PROC is not set > CONFIG_AIRO=y > # CONFIG_HERMES is not set > # CONFIG_PLX_HERMES is not set > CONFIG_NET_WIRELESS=y > > ... and here's the error messages I got: > > make -C wireless > make[3]: Entering directory > `/usr/src/linux-2.4.17/drivers/net/wireless' > make all_targets > make[4]: Entering directory > `/usr/src/linux-2.4.17/drivers/net/wireless' > gcc -D__KERNEL__ -I/usr/src/linux-2.4.17/include > -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 > -fomit-frame-pointer > -fno-strict-aliasing -fno-common -pipe > -mpreferred-stack-boundary=2 > -march=i586 -DEXPORT_SYMTAB -c airo.c > airo.c:50: parse error before `__attribute__' > airo.c:3228: warning: `airo_pci_remove' defined but > not used > make[4]: *** [airo.o] Error 1 > make[4]: Leaving directory > `/usr/src/linux-2.4.17/drivers/net/wireless' > make[3]: *** [first_rule] Error 2 > make[3]: Leaving directory > `/usr/src/linux-2.4.17/drivers/net/wireless' > make[2]: *** [_subdir_wireless] Error 2 > make[2]: Leaving directory > `/usr/src/linux-2.4.17/drivers/net' > make[1]: *** [_subdir_net] Error 2 > make[1]: Leaving directory > `/usr/src/linux-2.4.17/drivers' > make: *** [_dir_drivers] Error 2 > > Any help would be greatly appreciated. > > Thanks, > Cory > > > _______________________________________________ > Airo-linux-general mailing list > Air...@li... > https://lists.sourceforge.net/lists/listinfo/airo-linux-general __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com |
From: Cory S. <co...@st...> - 2001-12-28 14:50:37
|
Hello. I'm new to the list. I have a Cisco 350 PCI card and an external directional antenna comming in the mail, as a package I'm purchasing for high speed internet access. Don't have the card yet, but I thought I'd get started on updating my kernel. I've tried a 2.4.7 and 2.4.17 kernel, and can't get the airo driver compiled statically into the kernel. I can get it compiled as a module, but I'm not confident that it will work just because it compiled. This is a desktop machine, but do I need pcmcia compiled into the kernel to make this work? I'm just relying on the code that came with the kernels, should I patch the kernel with some other code? Here's a snippit of the config file: # # Wireless LAN (non-hamradio) # CONFIG_NET_RADIO=y # CONFIG_STRIP is not set # CONFIG_WAVELAN is not set # CONFIG_ARLAN is not set # CONFIG_AIRONET4500 is not set # CONFIG_AIRONET4500_NONCS is not set # CONFIG_AIRONET4500_PROC is not set CONFIG_AIRO=y # CONFIG_HERMES is not set # CONFIG_PLX_HERMES is not set CONFIG_NET_WIRELESS=y ... and here's the error messages I got: make -C wireless make[3]: Entering directory `/usr/src/linux-2.4.17/drivers/net/wireless' make all_targets make[4]: Entering directory `/usr/src/linux-2.4.17/drivers/net/wireless' gcc -D__KERNEL__ -I/usr/src/linux-2.4.17/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i586 -DEXPORT_SYMTAB -c airo.c airo.c:50: parse error before `__attribute__' airo.c:3228: warning: `airo_pci_remove' defined but not used make[4]: *** [airo.o] Error 1 make[4]: Leaving directory `/usr/src/linux-2.4.17/drivers/net/wireless' make[3]: *** [first_rule] Error 2 make[3]: Leaving directory `/usr/src/linux-2.4.17/drivers/net/wireless' make[2]: *** [_subdir_wireless] Error 2 make[2]: Leaving directory `/usr/src/linux-2.4.17/drivers/net' make[1]: *** [_subdir_net] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.17/drivers' make: *** [_dir_drivers] Error 2 Any help would be greatly appreciated. Thanks, Cory |
From: Ian C. <id...@en...> - 2001-11-28 00:50:38
|
I'm working on an ad hoc networking protocol called AODV. In this protocol I need to know when a packet fails to send and the ip address of the destination of the packet. Is this information is available? It looks like issuecommand() might return this information in the Resp. Would it? Would I need to set any special flags? It looks like TXCTL_TXEX is already set. How can I access this information (the data that failed to send) and in what method do you think I should do it? Thanks, Ian Chakeres |
From: Jim C. <ji...@pi...> - 2001-11-19 22:56:38
|
I'm trying to determine if there is a Linux driver for the "Dell TrueMobile 1150" internal wireless network device on the Inspiron 4100 or 8100. On Dell's support site a screen shot for setting it up under Windows showed an Aironet logo. But Cisco's web site disclaims all knowledge of the brand name "TrueMobile 1150" (or anything else 1150). So, does anyone on the list know, will the Aironet driver(s) work, or do you know anything about this equipment that might help me decide if I can use it? Thanks very much in advance. Dell's response to a query was, ``It's a DELL network solution!'' Big help. If Dell (or any other vendor) really wants to sell to the Linux community, they should clearly identify the chipsets for the onboard stuff; otherwise too many people will take advantage of their 30-day return policy. I'm currently using Proxim Symphony on a Dell Inspiron 3800, and I want to upgrade both the laptop and the wireless. When I bought it I had the same lack of information about Dell's wireless cards, which again I believed to be Aironet (802.11), but I declined the special pricing from Dell because I couldn't discover what I was getting. With an internal device, the decision is much more critical. -- jimc |