[Solved] "No wireless network found" – Ext USB Hard Drive?

Forum Forums New users New Users and General Questions [Solved] "No wireless network found" – Ext USB Hard Drive?

  • This topic has 6 replies, 4 voices, and was last updated Aug 1-2:36 am by fatmac.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #11586
    Member
    rej

      Wi-Fi doesn’t connect when transferring USB connected hard drive with antiX 17.1 to other PCs.

      It cannot find Wi-Fi [or Ethernet] networks when scanned with Wicd or Ceni.

      Ceni finds the network yet will not successfully connect.

      [Preferred] Wicd – message “no wireless network found”.

      It will only recognize networks on device the snapshot was installed to the ext HD on.

      Is there a way to fix this?

      Thank you.

      • This topic was modified 4 years, 9 months ago by rej.
      #11591
      Member
      fatmac
        Helpful
        Up
        0
        ::

        In the WICD app, turn the wifi on, rescan, then set it up, I think.

        • This reply was modified 4 years, 9 months ago by fatmac.

        Linux (& BSD) since 1999

        #11595
        Member
        rej
          Helpful
          Up
          0
          ::

          Thanks fatmac –

          WICD applet in the system tray:

          Not connected

          [Menu choices:]

          -rescan: “no wireless networks found”

          -connect: “no wireless networks found”

          -connection info: “Disconnected”

          -quit
          _________________

          WICD network manager
          ——–
          network:
          “no wireless networks found”
          refresh:
          “no wireless networks found”

          ________________________

          Ceni scans, finds the correct network, asks for password, looks as though it is connecting, yet does not connect.
          ——-
          Ran Wicd in terminal:

          result – “It seems like the daemon is already running.
          If it is not, please remove /var/run/wicd/wicd.pid and try again.”

          – Removing PID, or deleting the entire file, after each, rescanned -did not change anything.
          – Removing PID, or deleting the entire file, after each, rebooted -did not change anything.

          Htop running processes shows it as running:

          2418 root 20 0 148M 15572 6264 S 0.0 0.4 0:00.22 /usr/bin/python -0 /usr/share/wicd/daemon/wicd-daemon.py –keep-connection

          ——————————————

          -Checked for correct network driver.

          -Tried installing snapshot with IceWm only to ext HD, -without Xfce in case that was a factor – no change.

          -Switched on and off hardware toggle many times

          -Compared every setting in antiX between the PC currently running it on, antiX in the PC the Snapshot was made on, and the installation on the external disk itself. – all the same.

          -Wicd does not even attempt a scan when clicked on through the Control Center or the applet in the system tray.

          -The correct ESSID-BSSID was listed on attempt to delete it in: Network-“Forget Network Settings”

          -Tried running same ext drive on several different devices – will only connect on the PC that antiX was installed to the external disk drive on.

          – Installed another network manager from stretch in Synaptic Pkg Mngr and from the terminal – installed with errors, had to purge.

          Could not find a setting “turn the wifi on” – did I overlook it?

          #11596
          Moderator
          Brian Masinick
            Helpful
            Up
            0
            ::

            I know that when you run ceni, it will ask you to use privileged mode, that is, either login as root or use sudo ceni (or su) to have the “effective ID” of the “super user”, root.

            I think that the client versions of wicd may not require the user interface to run under privileges, but I suspect that the daemon that connects the wired and wireless interface points to the network probably does require privileges. The real “experts” can confirm or refute these thoughts as needed, but that might be the “trick” you need to get things working. I hope either this helps or someone with more expertise in networking provides the 100% correct solution and diagnosis.

            Best wishes in successfully connecting to the network using antiX!

            --
            Brian Masinick

            #11597
            Forum Admin
            rokytnji
              Helpful
              Up
              0
              ::
              harry@biker:~
              $ rfkill list
              0: phy0: Wireless LAN
              	Soft blocked: no
              	Hard blocked: no
              1: hci0: Bluetooth
              	Soft blocked: no
              	Hard blocked: no
              harry@biker:~
              $ sudo ifconfig -a
              [sudo] password for harry: 
              eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
                      ether 20:1a:06:14:09:d9  txqueuelen 1000  (Ethernet)
                      RX packets 0  bytes 0 (0.0 B)
                      RX errors 0  dropped 0  overruns 0  frame 0
                      TX packets 0  bytes 0 (0.0 B)
                      TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                      device interrupt 18  
              
              lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
                      inet 127.0.0.1  netmask 255.0.0.0
                      inet6 ::1  prefixlen 128  scopeid 0x10<host>
                      loop  txqueuelen 1000  (Local Loopback)
                      RX packets 44  bytes 2802 (2.7 KiB)
                      RX errors 0  dropped 0  overruns 0  frame 0
                      TX packets 44  bytes 2802 (2.7 KiB)
                      TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
              
              wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
                      inet 192.168.254.68  netmask 255.255.255.0  broadcast 192.168.254.255
                      inet6 fe80::3e77:e6ff:fe26:f5b5  prefixlen 64  scopeid 0x20<link>
                      ether 3c:77:e6:26:f5:b5  txqueuelen 1000  (Ethernet)
                      RX packets 8045  bytes 5857942 (5.5 MiB)
                      RX errors 0  dropped 0  overruns 0  frame 0
                      TX packets 6655  bytes 768332 (750.3 KiB)
                      TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
              

              Then I would go into AntiX Control Center > Network > connect wirelessly (wicd)
              Hit the button. Open Wicd. Make sure wlan0 is in the preferences box < task bar for preferences > for wireless
              to match my ifconfig wireless readout above it.

              That is what I would try. rfkill command is just checking for switch blocking on wireless. You can hit quit on the extra wicd icon on the taskbar after all of this.

              • This reply was modified 4 years, 9 months ago by rokytnji.
              • This reply was modified 4 years, 9 months ago by rokytnji.
              • This reply was modified 4 years, 9 months ago by Brian Masinick. Reason: the

              Sometimes I drive a crooked road to get my mind straight.
              Not all who Wander are Lost.
              I'm not outa place. I'm from outer space.

              Linux Registered User # 475019
              How to Search for AntiX solutions to your problems

              #11602
              Member
              rej
                Helpful
                Up
                0
                ::

                Brian –
                Thanks for the input and getting it rolling!
                ________________________________
                rokytnji-

                Thank you-

                This worked!

                The first 25 times, I had overlooked the drop down with “Preferences”, and you provided what to do with it.

                wlan0 was not in “ifconfig -a” results – wlan1 looked similar to what you had in yours, and that connected it.

                The information you gave me is very well laid out and complete.

                After days of futile searches and failed attempts, I don’t think this fix would have come up anytime soon (if ever).

                The Ext HD is convenient to test-run, on several different devices, how a completely new modification works before replacing the original antiX version on the internal disk.

                Thanks again!

                #11618
                Member
                fatmac
                  Helpful
                  Up
                  0
                  ::

                  As an aside, I have a HP-G62 laptop wifi that no longer comes up automatically under AntiX, but it does under MX Linux, our Sister Distro. Weird. 🙂

                  Linux (& BSD) since 1999

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