[Solved] 17.1 Cannot Connect Wireless – System Crashes

Forum › Forums › New users › New Users and General Questions › [Solved] 17.1 Cannot Connect Wireless – System Crashes

  • This topic has 2 replies, 2 voices, and was last updated Aug 18-7:00 am by rej.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • August 17, 2018 at 1:24 pm #11827
    Member
    rej

      When the Wicd is opened – icons vibrate rapidly in the system tray and the entire system freezes up – wait and wait – must power off.

      Ceni appears to have configured it in Terminal – still no wireless.

      Fresh install antiX17.1 – tried two different laptops. Different hard drives. Tried a new kernel. Rebooted many many times – same result.

      Fresh installed several times [and updated] got Wicd to connect a couple of times, however, crashes on reboot.

      /etc/default/wicd START_DAEMON=yes

      Never had this without being able to resolve before.

      Installed antix 17.1 pre-configured snapshots do not run into this issue.

      Is there a fix for this?

      I have inxi -F if needed from both PCs.

      Thank you.

      • This topic was modified 4 years, 8 months ago by rej.
      August 17, 2018 at 4:37 pm #11828
      Forum Admin
      rokytnji
        Helpful
        Up
        0
        ::

        Yes Please.

        I have inxi -F if needed from both PCs.

        Howdy and Welcome. Have you md5sum checked your AntiX iso ?

        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

        August 18, 2018 at 7:00 am #11831
        Member
        rej
          Helpful
          Up
          0
          ::

          Thanks rokytnji-

          Found the answer. After much trial and error, made a 4th partition, installed 17.1, ran update & dist-upgrade and, changed kernel to 4.17.4, again, and had the usual behavior, yet in this instance, it eventually settled down after some time, unfroze and was able to hook up a stable wifi connection. So appears to be the kernel after all. Could not get it to connect the first time with the 4.17.4 kernel (updated GRUB, made sure it was running) – had to have omitted something important or maybe did not wait long enough for it to settle and unfreeze.

          Tried it fresh on another partition to verify and had the same success.

          Error popup:

          “Could not connect to wicd’s D-Bus interface.
          Check the wicd log for error messages.” [nothing in the wicd.log]

          Then it goes into scanning mode [CPU @ 26%] with vibrating icons, and another error message pops up:

          The wicd daemon has shut down. The full UI will not function properly until it is restarted.

          Then never ending scanning mode, desktop freezes. Must power off.

          Thanks again. Your assistance is always appreciated.

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