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

    Atheros ath0: device timeout errors

    Scheduled Pinned Locked Moved Wireless
    4 Posts 3 Posters 1.8k Views
    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.
    • D
      diyguy
      last edited by

      Hi all
      I have installed pfsense 2.2.6-RELEASE on a PC Engines APU2C4 board, with a Compex WLE200NX WiFi mini-PCIe adapter.

      The WLE200NX is detected as ath0 but the card doesn't seem to transmit any SSID I configure, and I'm getting regular 'ath0: device timeout' errors - maybe one every minute or so, but it does successfully pick up my home Wifi SSID using the pfSense UI Status/WiFi/Rescan.

      Some information that might be useful below.

      From what I've read it looks like the Atheros AR9280 chipset is supported but I don't really know where to go from here.  Any help or advice very much appreciated.

      Thanks,

      
      enabling HT modes
      ath0: [HT] 1 stream STBC receive enabled
      ath0: [HT] 1 stream STBC transmit enabled
      ath0: [HT] 2 RX streams; 2 TX streams
      ath0: AR9280 mac 128.2 RF5133 phy 13.0
      ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0
      wlan0: changing name to 'ath0_wlan0'
      ath0_wlan0: promiscuous mode enabled
      ath0: device timeout
      ath0: device timeout
      ath0: device timeout
      

      Also, athstats gives me this output.  Not sure if the ioctl errors at the beginning are normal or not

      
      [2.2.6-RELEASE][admin@pfSense.localdomain]/var/log: athstats
      athstats: ioctl: ath0: Invalid argument
      athstats: ioctl: ath0: Invalid argument
      1108         data frames received
      2740         data frames transmit
      1M           current transmit rate
      28           watchdog timeouts
      9            tx stopped 'cuz no xmit buffer
      2729         tx frames with no ack marked
      69           rx failed 'cuz of bad CRC
      17           periodic calibrations
      -0/+0        TDMA slot adjust (usecs, smoothed)
      2            rssi of last ack
      57           avg recv rssi
      -96          rx noise floor
      11           tx frames through raw api
      1044         raw tx failed 'cuz interface/hw down
      5            Half-GI frames received
      78           CRC errors for non-last A-MPDU subframes
      15           CRC errors for last subframe in an A-MPDU
      Antenna profile:
      [0] tx     2508 rx        0
      [1] tx        0 rx     1108
      
      
      JonathanLeeJ 1 Reply Last reply Reply Quote 0
      • JonathanLeeJ
        JonathanLee @diyguy
        last edited by JonathanLee

        @diyguy

        Did you ever get this going?? I just noticed your post it is a bit old but hey I wanted to reply and see if you got it going.

        https://docs.netgate.com/pfsense/en/latest/wireless/configuration-ap.html

        I got mine to work well with Wifi 802.11AN with it set to -40 ht. 802.11ng was really bad for my connection.

        Make sure to upvote

        provelsP 1 Reply Last reply Reply Quote 0
        • provelsP
          provels @JonathanLee
          last edited by provels

          @JonathanLee FWIW, that user had a many versions back install. I use a 200 just fine.
          Also, FWIW,I have read 40ht isn't recommended for 2.4ng.

          Peder

          MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
          BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

          JonathanLeeJ 1 Reply Last reply Reply Quote 0
          • JonathanLeeJ
            JonathanLee @provels
            last edited by JonathanLee

            @provels 802.11NG 20ht was really bad for me. It only works well with 802.11NA on -40ht with a 5dbi antenna set. The 8dbi was like a laser or point to point. The 5dbi is like an oval shape for coverage.

            Make sure to upvote

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.