Re: Problems with an0 and ISA Aironet Card..
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: [EMAIL PROTECTED] | Center for Telecommunications Research Home: [EMAIL PROTECTED] | 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with an0 and ISA Aironet Card..
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). > - What sort of machine are you using? (Show us the *whole* dmesg output. > Timing may also be an issue, in which case I need to know the CPU speed.) CPU: Pentium III/Xeon (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 201261056 (196544K bytes) avail memory = 192323584 (187816K bytes) Preloaded elf kernel "kernel" at 0xc02b4000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: mem 0xe600-0xe6ff,0xe400-0xe4ff irq 11 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 10 pci0: unknown card (vendor=0x1319, dev=0x0801) at 8.0 irq 11 pci0: unknown card (vendor=0x1319, dev=0x0802) at 8.1 rl0: port 0xec00-0xecff mem 0xe700-0xe7ff irq 9 at device 9.0 on pci0 rl0: Ethernet address: 00:c0:df:25:f1:5c miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isa0: unexpected tag 14 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata-isa0: already registered as ata0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic1: not probed (disabled) sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ppi0: on ppbus0 an0: reset failed unknown0: at port 0x100-0x13f irq 5 on isa0 ad0: ATA-4 disk at ata0 as master ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata0 as slave acd0: 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked I've only got one card in the machine now. Only one 'unexpected tag' line now.. > Tell us what kernel config line you use when using the card in non-PnP > mode. Note that the switches on the card must all be in the correct > position in order to enable PnP mode: consult your user's manual for > the proper settings. I believe they all need to be in the off position, > however I don't have the manual here at home with me so I could be > mistaken. (I do remember they all have to be set the same way.) for non-PnP mode, they are set as per the manual. Config line for the above was: device an0 at isa? port 0x100 irq 5 same result whether I'm using PnP or not. (above output is from PnP). > Not really. My one and only ISA card works fine, or at least it did when > I did my tests right before I imported the driver. It would help if you > could actually look at the card when the kernel boots to see if the LEDs > flash at all. If the reset is screwing up, then you should see the LEDs > flicker when it tries to access the board. If it's failing to access the > board at all, the LEDs won't change at all. The RED LED statys on during boot, until the kernel tries to init the card - then the RED LED goes out, and thats it. > Try commenting out the code in an_reset() (i.e. make it an empty > function that does nothing) and see if it works then. If it *still* > doesn't work, then there's something else wrong. Tried this - doesn't even list the card in the output except for then unknown line. > Try to run the > following program as root: > This will print out the command and status registers for the card > at iobase 0x100. If the card has been properly activated, you should > see for the COMMAND and PARAM0 registers initially, then the > program will try to write 0x1234 to the PARAM0 register and read it > back. If it reads back 0x1234, then the card is configured right > and the reset is screwing up. If on the other hand the program prints > for all of the register contents, then the card is not really > configured properly for address 0x100. pcpaul# ./testa COM
Re: Problems with an0 and ISA Aironet Card..
Of all the gin joints in all the towns in all the world, Paul Reece had to
walk into mine and say:
> Having a few problems trying to get an ISA Aironet 4800 card working under
> FreeBSD 4.0-CURRENT. I did try with 3.4-RELEASE first with the
> appropriate drivers, but had even less luck.
> What I'm seeing at boot:
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.)
- What sort of machine are you using? (Show us the *whole* dmesg output.
Timing may also be an issue, in which case I need to know the CPU speed.)
> first suspect lines:
>
> isa0: unexpected tag 14
> isa0: unexpected tag 14
I'm not sure if this is related.
> then:
>
> an0: reset failed
> unknown0: at port 0x100-0x13f irq 5 on isa0
> an0: reset failed
> unknown1: at port 0x140-0x17f irq 10 on isa0
>
>
> (machine has 2 cards in it). When trying with NON PNP mode, the cards
> also have the same problem.
Tell us what kernel config line you use when using the card in non-PnP
mode. Note that the switches on the card must all be in the correct
position in order to enable PnP mode: consult your user's manual for
the proper settings. I believe they all need to be in the off position,
however I don't have the manual here at home with me so I could be
mistaken. (I do remember they all have to be set the same way.)
> PCI cards work fine, just not the ISA
> equivalents..
>
> Anyone have any clues/hints/tips etc?
Not really. My one and only ISA card works fine, or at least it did when
I did my tests right before I imported the driver. It would help if you
could actually look at the card when the kernel boots to see if the LEDs
flash at all. If the reset is screwing up, then you should see the LEDs
flicker when it tries to access the board. If it's failing to access the
board at all, the LEDs won't change at all.
Try commenting out the code in an_reset() (i.e. make it an empty
function that does nothing) and see if it works then. If it *still*
doesn't work, then there's something else wrong. Try to run the
following program as root:
#include
#include
#include
#include
#define IOADDR 0x100 /* change to 0x140 for other card */
main()
{
int f;
f = open("/dev/io", O_RDWR);
printf("COMMAND: %x\n", inw(IOADDR));
printf("PARAM0: %x\n", inw(IOADDR + 0x2));
outw(IOADDR + 0x2, 0x1234);
printf("PARAM0: 0x\n", inw(IOADDR + 0x2));
exit(0);
}
This will print out the command and status registers for the card
at iobase 0x100. If the card has been properly activated, you should
see for the COMMAND and PARAM0 registers initially, then the
program will try to write 0x1234 to the PARAM0 register and read it
back. If it reads back 0x1234, then the card is configured right
and the reset is screwing up. If on the other hand the program prints
for all of the register contents, then the card is not really
configured properly for address 0x100.
>
> Cheers.
>
>
> Regards,
> Paul.
>
> (replies to me direct please - not on list)
I'm doing both. Deal with it.
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] | 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Problems with an0 and ISA Aironet Card..
Having a few problems trying to get an ISA Aironet 4800 card working under FreeBSD 4.0-CURRENT. I did try with 3.4-RELEASE first with the appropriate drivers, but had even less luck. What I'm seeing at boot: first suspect lines: isa0: unexpected tag 14 isa0: unexpected tag 14 then: an0: reset failed unknown0: at port 0x100-0x13f irq 5 on isa0 an0: reset failed unknown1: at port 0x140-0x17f irq 10 on isa0 (machine has 2 cards in it). When trying with NON PNP mode, the cards also have the same problem. PCI cards work fine, just not the ISA equivalents.. Anyone have any clues/hints/tips etc? Cheers. Regards, Paul. (replies to me direct please - not on list) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
