From owner-freebsd-current Thu Jan 27 15:21:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 122D815892 for ; Thu, 27 Jan 2000 15:21:08 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA26648; Thu, 27 Jan 2000 18:24:53 -0500 From: Bill Paul Message-Id: <200001272324.SAA26648@skynet.ctr.columbia.edu> Subject: Re: Problems with an0 and ISA Aironet Card.. To: paul@pulsat.com.au (Paul Reece) Date: Thu, 27 Jan 2000 18:24:52 -0500 (EST) Cc: current@freebsd.org In-Reply-To: from "Paul Reece" at Jan 20, 2000 05:35:16 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3944 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Paul Reece had to walk into mine and say: > On Thu, 20 Jan 2000, Bill Paul wrote: > > > > > Back up. You're leaving out some info. > > > > - When did you buy these cards? (The firmware rev may be an issue. > > knowing when you bought the card helps me figure out if your firmware > > is newer than mine.) > > Cards were purchased in the past 6 months. Revision of the card I'm using > at the moment is 3.13 - I upgraded the firmware to the latest. (Win DGS > under 'status' reports 3.13). You can view the firmware rev with the if_an driver (when it works) by doing ancontrol -i an0 -I. The newest PCMCIA card that I have seems to be using revision 3.10. The ISA card that I have is using 2.06. The trouble is I don't have Windows machine set up to run the firmware update utility. What I tried to do today was swap the PCMCIA module on my existing ISA card with one of the new ones with the later firmware. I did this a while back when I got our first batch of cards. However, I can't do it now. One of the problems I had with the Aironet cards initially is that they were set up so that they would operate in two modes: if you applied +5volts to the vpp1 and vpp2 pins on the PCMCIA module, it would work in PCMCIA mode such that you could get at the CIS data and configure it like any other PCMCIA card. Without the +5volts, the module would work in a special 'dumb bus' mode that would allow it to interface with the ISA and PCI bridge adapter cards that Aironet uses for their ISA and PCI cards. Basically, this allows them to make just one PCMCIA module and use it in all three kinds of cards. However the latest PCMCIA cards that we just got are different: now they always work in PCMCIA mode regardless of how vpp1 and vpp2 are set. On the one hand, this is good because it means you don't have to frob sys/pccard/pccard.c to enable the vpp voltage when the card is inserted. (My older cards will not work with FreeBSD unless I apply this tweak to the kernel.) On the other hand, this means that the newer PCMCIA cards won't work in the ISA and PCI bridge adapters. This sort of stymied my attempts to duplicate your problem here in the lab. What would be nice is if you could somehow set up a scratch box with an Aironet ISA4800 card in it that I could access remotely. I'm reasonably confident I could make it work if I could just experiment with it for a while. Unfortunately, this may not be possible depending on technical on various political constraints, especially since I need to twiddle around as root in order to examine register contents and test a new driver. > pcpaul# ./testa > COMMAND: 0 > PARAM0: ff11 > PARAM0: 0x > > (still no lights on card) > if I run it again: > > pcpaul# ./testa > COMMAND: 0 > PARAM0: 1234 > PARAM0: 0x > > (and still no lights). > > > This info help at all? Well, yes. It tells me two things. First, it tells me that I made a typo on the program that I gave you. :) Second, it shows me that the card is at the I/O address that it's supposed to be, although it appears to not be responding to the 'read SSID list' command that the if_an driver issues during the probe phase. Unfortunately, as I said earlier, I need to be able to experiment on this thing in order to figure out the problem, and I can't do that unless you can somehow arrange remote access. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message