Re: Error with Atheros chipset.

From: Sam Leffler (sam_at_errno.com)
Date: 07/31/03

  • Next message: John: "-current panic: ffs_valloc: dup alloc" 
    Date: Wed, 30 Jul 2003 15:17:49 -0700
To: Marcin Jessa <freebsd@yazzy.org>, freebsd-small@freebsd.org, freebsd-current@freebsd.org

    [Not sure about cross-posting but I'll leave it for now.]

    > I've recompiled -CURRENT with support for atheros cards.
    > I have two cards, one PCI(desktop) and one PCMCIA(laptop). Both are
    > Proxim 11a/b/g combo cards with AR5212 chips. The cards are recognized
    > fine.
    > pciconf -l -vv shows:
    >
    > ath0@pci2:4:0: class=0x020000 card=0x0a6014b7 chip=0x0013168c rev=0x01
    > hdr=0x00 vendor = 'Atheros Communications Inc.'
    > class = network
    > subclass = ethernet
    >
    > dmesg shows:
    > ath0: <Atheros 5212> mem 0x40000000-0x4000ffff irq 5 at device 4.0 on pci2
    > ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
    > ath0: 802.11 address: 00:20:a6:4c:ef:62
    >
    > I've tried every possible example combo from man ath(4), i.e:
    >
    > ifconfig ath0 inet 192.168.0.1 netmask 0xffffff00 ssid my_net mode 11a
    > mediaopt adhoc
    >
    > to create adhoc network.
    >
    > The problems start when I try to configure them with ifconfig.
    >
    > Every attempt result in following errors and lack of communication
    > between them: ar5212AniGetCurrentState: Out of space in ANI table for
    > channel 5785/0x140! ar5212AniGetCurrentState: Out of space in ANI table
    > for channel 5805/0x140! ar5212AniGetCurrentState: Out of space in ANI
    > table for channel 5825/0x140! ar5212AniGetCurrentState: Out of space in
    > ANI table for channel 5785/0x140! ar5212AniGetCurrentState: Out of space
    > in ANI table for channel 5805/0x140!
    >
    > etc etc.
    >
    > Any idea how to fix that and how to make the cards work? A simple ping
    > would make my day :)

    You're stuck for now. This is a bug in the HAL that I've got fixed but is
    taking forever to verify correctness. With luck I'll have new stuff
    committed this week (but that's what I thought last week...).

    Sorry, it was my bad :(

            Sam

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: John: "-current panic: ffs_valloc: dup alloc"