Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Cannot get wireless atheros card to be recognized in pfSense 2.0.1

    Wireless
    2
    2
    2315
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      chriv last edited by

      I read some similar threads, including this one: http://forum.pfsense.org/index.php?topic=12807.0, but I didn't find any answers.

      Simple problem: pfSense 2.0.1 doesn't load the driver for my atheros wireless card in my Acer netbook.

      Here's some applicable output:

      #: dmesg | grep -i ath
      ath0: <atheros 2424="" 5424=""> irq 17 at device 0.0 on pci3
      ath0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
      ath0: cannot map register space
      device_attach: ath0 attach returned 6</atheros>
      
      #: pciconf -lv
      ...
      ath0@pci0:3:0:0:        class=0x020000 card=0xe00d105b chip=0x001c168c rev=0x01 hdr=0x00
          class      = network
          subclass   = ethernet
      

      Anybody have any ideas?  I haven't the foggiest clue how to recompile the kernel without the atheros driver to slip in the atheros kernel module, so that won't work for me without some pretty explicit instructions.  I don't think it would fix these errors anyway.

      1 Reply Last reply Reply Quote 0
      • W
        wallabybob last edited by

        @chriv:

        Simple problem: pfSense 2.0.1 doesn't load the driver for my atheros wireless card in my Acer netbook.

        Wrong diagnosis. The driver is already built in the kernel and it is effectively reporting the I/O subsystem is not correctly setup for the card.

        #: dmesg | grep -i ath
        ath0: <atheros 2424="" 5424=""> irq 17 at device 0.0 on pci3
        ath0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
        ath0: cannot map register space
        device_attach: ath0 attach returned 6</atheros>
        

        After a quick look through the FreeBSD source code I suspect this means something like:
        1. There isn't enough kernel address space or page table entries to map the 0x10000 (64k) bytes of PCI memory address space on the ath device into kernel memory space; or
        2. An upstream PCI bridge doesn't have enough memory address space to allow access to all its downstream devices AND this device;

        Is this card a mini PCI-Express card replacing the netbook's standard WiFi card?

        Is pfSense running in some kind of virtual environment?

        Was the card in the system at boot time?

        Have you tried a snapshot build of pfSense 2.1?

        1 Reply Last reply Reply Quote 0
        • First post
          Last post

        Products

        • Platform Overview
        • TNSR
        • pfSense Plus
        • Appliances

        Services

        • Training
        • Professional Services

        Support

        • Subscription Plans
        • Contact Support
        • Product Lifecycle
        • Documentation

        News

        • Media Coverage
        • Press
        • Events

        Resources

        • Blog
        • FAQ
        • Find a Partner
        • Resource Library
        • Security Information

        Company

        • About Us
        • Careers
        • Partners
        • Contact Us
        • Legal
        Our Mission

        We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

        Subscribe to our Newsletter

        Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

        © 2021 Rubicon Communications, LLC | Privacy Policy