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

    Wifi no longer working after upgrade to 2.3.1

    Scheduled Pinned Locked Moved Wireless
    6 Posts 2 Posters 2.0k 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.
    • P
      pvoigt
      last edited by

      Today I have finished a fresh full installation of pfSense 2.3.1 (amd64) on an mSATA of an apu1d4. The installation worked as expected and I could manually reinstall the needed nut package without any issues.

      Unfortunately, my wifi card stopped working, e.g. the dashboard shows the wlan interfaces are down. Indeed, I have cloned the interface to have to SSIDs "wlan" and "wlan2". This setup with exactly the same hardware is working without any trouble with pfSense 2.2.6.

      My WLAN card is a Compex WLE200NX abgn based on an Atheros AR9280 chip: http://www.pcengines.ch/wle200nx.htm

      Update: When saving any changes to the interfaces WLAN and WLAN2 I obtain following errors:

      
      ath0: ath_reset_grablock: didn't finish after 10 iterations
      ath0: ath_reset_grablock: warning, recursive reset path!
      ath0: ath_reset: concurrent reset! Danger!
      
      
      1 Reply Last reply Reply Quote 0
      • P
        pvoigt
        last edited by

        Update:
        Meanwhile I have done numerous tests with my wireless configuration. The good news: It is possible to bring up both wireless clones in a reliable way. Bad news: This usually does not happen on a regular reboot.

        I figured out that after a cold or warm reboot at least one of the wireless clones does not start correctly and shows up as "down" in the webGUI. However, it s possible to bring up such a device, if you select the device and just save the settings of this interface without making any changes. Somestimes you have to repeat this step once again but as soon as the interface is up, it is working correctly.

        After numerous reboot tests I had approximately one out of 30 attempts where both wireless clones are initialized correctly and show up as "up".

        My apu1d4 with a fresh and full installation of version 2.3.2 is online now and I am going to collect further experiences with special focus on the wirless subsystem.

        Apart from this wireless issue and a small and meanwhile fixed error with the NUT package (https://forum.pfsense.org/index.php?topic=115760.0) pfSense 2.3.2 leaves a good impression.

        Thanks for the good work.

        1 Reply Last reply Reply Quote 0
        • A
          azertypro
          last edited by

          Hello,

          I have the same bug like you

          2.3.2-RELEASE
          APU2C4
          WLE200NX

          I have set up two VAP on my pfsense on the ath0

          • WIFI ath0_wlan1

          • WIFI-GUEST ath0_wlan2

          After a reboot, my pfsense is looping

          Configuring LAGG interfaces...done.
          Configuring VLAN interfaces...done.
          Configuring QinQ interfaces...done.
          Configuring WAN interface...done.
          Configuring WIFI interface...
          ```crashhhhhhhhhh
          
          

          <118>Configuring WIFI interface...
          ath0: ath_reset_grablock: didn't finish after 10 iterations
          ath0: ath_reset_grablock: warning, recursive reset path!
          ath0: ath_chan_set: concurrent reset! Danger!

          
          After few tests, i have bypass the bug by starting the pfsense on "Safe Mode"
          
          *   Press "space" on the startup menu of pfsense to freeze the menu
          
          *   Press "o" to enter in option
          
          *   Press "m" to activate the "Safe Mode"
          
          *   Press "enter" to laucnh pfsense with your option which you select
          
          NB : if you reboot again, your pfsense will not start in safe mode by default.
          
          I don't know what is the best way to fix it :/
          1 Reply Last reply Reply Quote 0
          • P
            pvoigt
            last edited by

            Your experiences sound even worse.

            Although my card is showing the same errors and warnings I have never seen them on a regular reboot. They appear on my apu1d4 only, when saving the wireless settings in the webGUI. And luckily I have not had any crash so far.

            Is there no chance to bring up your apu2c4 in non-safe, e.g. regular mode?

            I am particularly interested in this question because I am thinking about getting an apu2 as well  :).

            1 Reply Last reply Reply Quote 0
            • P
              pvoigt
              last edited by

              Just a shot in the dark: On the PC Engines homepage I have just read the changlog of the BIOS versions and have found:

              Update 1/20/2016: fix miniPCIe IRQ assignments, wle200nx working

              Are you running the lastest BIOS version?

              1 Reply Last reply Reply Quote 0
              • A
                azertypro
                last edited by

                I have the latest 160311

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