WiFi keeps dropping – please help

Forum Forums New users New Users and General Questions WiFi keeps dropping – please help

  • This topic has 8 replies, 3 voices, and was last updated Jun 24-10:34 am by Xecure.
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #62104
    Member
    discipulus

      relevant part of inxi -F :

      Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
      IF: wlan0 state: up mac: 42:9c:d6:c7:5a:4f

      iwconfig:

      wlan0 IEEE 802.11 ESSID:”Freebox-4B2D7C_EXT”
      Mode:Managed Frequency:2.412 GHz Access Point: 8C:3B:AD:2A:93:FE
      Bit Rate=65 Mb/s Tx-Power=22 dBm
      Retry short limit:7 RTS thr:off Fragment thr:off
      Power Management:off
      Link Quality=45/70 Signal level=-65 dBm
      Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
      Tx excessive retries:0 Invalid misc:4 Missed beacon:0

      Tried both connman and ceni and both seem to lose the connection in a way that I’ve not experienced before on other OSes. Not saying it ISN’T my connection for 100% but I’d be surprised if it suddenly changed and became this unstable.

      hwinfo –wlan

      10: PCI 300.0: 0282 WLAN controller
      [Created at pci.386]
      Unique ID: y9sn.Sygf2rrlQCD
      Parent ID: HnsE.gGxyAxJBuk6
      SysFS ID: /devices/pci0000:00/0000:00:1c.5/0000:03:00.0
      SysFS BusID: 0000:03:00.0
      Hardware Class: network
      Device Name: “WLAN”
      Model: “Intel Dual Band Wireless-AC 3168NGW [Stone Peak]”
      Vendor: pci 0x8086 “Intel Corporation”
      Device: pci 0x24fb “Dual Band Wireless-AC 3168NGW [Stone Peak]”
      SubVendor: pci 0x8086 “Intel Corporation”
      SubDevice: pci 0x2110
      Revision: 0x10
      Driver: “iwlwifi”
      Driver Modules: “iwlwifi”
      Device File: wlan0
      Features: WLAN
      Memory Range: 0xa4000000-0xa4001fff (rw,non-prefetchable)
      IRQ: 130 (no events)
      HW Address: 42:9c:d6:c7:5a:4f
      Permanent HW Address: e4:42:a6:f3:ad:1d
      Link detected: yes
      WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
      WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7
      WLAN encryption modes: WEP40 WEP104 TKIP CCMP
      WLAN authentication modes: open sharedkey wpa-psk wpa-eap
      Module Alias: “pci:v00008086d000024FBsv00008086sd00002110bc02sc80i00”
      Driver Info #0:
      Driver Status: iwlwifi is active
      Driver Activation Cmd: “modprobe iwlwifi”
      Driver Info #1:
      Driver Status: wl is active
      Driver Activation Cmd: “modprobe wl”
      Config Status: cfg=new, avail=yes, need=no, active=unknown
      Attached to: #16 (PCI bridge)

      • This topic was modified 1 year, 10 months ago by discipulus.
      #62109
      Member
      Xecure
        Helpful
        Up
        0
        ::

        I had just finished writing a very long post explaining how to configure connman or in its defect network manager, when I went and searched for information on your specific device [8086:2110].

        It seems that there are sometimes issues with disconnecting (see linuxmint forum).

        Support may have improved on newer kernels, but maybe some other solution works.

        In the future, with wifi issues it is better to post
        inxi -Nxxx
        as it gives the device ID easily (which then helps search for issues in https://linux-hardware.org/?id=pci:8086-24fb-8086-2110

        If the linux mint post doesn’t help, you can force rconnect after errors in cmst connman interface, to get your connection back as soon as possible (Details > your WAP > autoconnect, and in “Preferences” tab, enable Retry failed connection).

        antiX Live system enthusiast.
        General Live Boot Parameters for antiX.

        #62157
        Member
        discipulus
          Helpful
          Up
          0
          ::

          I followed the instructions on the Mint forum, installing the firmware for the wifi card. But now upon login, I get

          “Unable to create an interface to connman on the system bus. CMST will not be able to communicate with connman”

          and I have no connection until I manually run Ceni.

          Should I just remove the connman package since I’m using Ceni anyway?

          Thanks

          • This reply was modified 1 year, 10 months ago by discipulus.
          #62161
          Member
          Xecure
            Helpful
            Up
            0
            ::

            Should I just remove the connman package since I’m using Ceni anyway?

            Yes, do so.
            You could also try your luck with network manager if you also prefer an easier way to switch WAPs or for sharing your network or any other things that cannot be done with ceni.

            antiX Live system enthusiast.
            General Live Boot Parameters for antiX.

            #62165
            Member
            discipulus
              Helpful
              Up
              0
              ::

              No problems since deletion of Connman. Initially I couldn’t load pages, until I figured out that deletion of Connman had emptied resolv.conf but I repopulated that with OpenDNS nameserver addresses and Bob’s your father’s brother. 🙂

              #62200
              Member
              discipulus
                Helpful
                Up
                0
                ::

                Since first restart after deleting Connman, there is no wifi until I re-run the Ceni config subroutine
                Please tell me how I can get the system to activate wlan0 and connect to my previously chosen network, automatically
                Most things about antiX are very nice but this is a bit of a mess, tbh

                #62210
                Moderator
                christophe
                  Helpful
                  Up
                  0
                  ::

                  hello, discipulus.

                  See if this is the issue – I ran into this some time ago with ceni:

                  If “allow hot-plug” (removable devices)” is checked, I had to re-run ceni each reboot.
                  So now I set it to “auto (built-in devices)” – whether it’s a removable usb dongle or internal, built-in.
                  Now, set up as “auto” – it reconnects at each reboot automatically.

                  • This reply was modified 1 year, 10 months ago by christophe. Reason: added image
                  Attachments:

                  confirmed antiX frugaler, since 2019

                  #62235
                  Member
                  discipulus
                    Helpful
                    Up
                    0
                    ::

                    Thank you Christophe, I will see if that works 🙂

                    #62241
                    Member
                    Xecure
                      Helpful
                      Up
                      0
                      ::

                      If after setting to auto the system takes too long to boot, change /etc/network/interfaces wlan0 option from auto to manual and add to /etc/rc.local
                      ifup wlan0
                      before exit.
                      This will start the wlan0 interface a few seconds after boot.

                      antiX Live system enthusiast.
                      General Live Boot Parameters for antiX.

                    Viewing 9 posts - 1 through 9 (of 9 total)
                    • You must be logged in to reply to this topic.