[SOLVED] Help – Wicd stopped working suddenly

Forum Forums General Software [SOLVED] Help – Wicd stopped working suddenly

Tagged: ,

  • This topic has 3 replies, 2 voices, and was last updated Apr 10-6:34 am by caprea.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #20351
    Member
    Klaas Vaak

      I was surfing the web, when suddenly pages would not load anymore. Wicd cannot spot any networks anymore, pressing the Refresh button does not do anything. I am on antiX 17.2
      Here are the hardware details:

       inxi -Fxz
      System:
        Host: Yoga300 Kernel: 4.19.25-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc 
        v: 6.3.0 Desktop: IceWM 1.4.2 
        Distro: antiX-17.2_x64-full Helen Keller 4 October 2018 
        base: Debian GNU/Linux 9 (stretch) 
      Machine:
        Type: Laptop System: LENOVO product: 80M0 v: Lenovo YOGA 300-11IBY serial: <filter> 
        Mobo: LENOVO model: Mini v: SDK0J33995WIN serial: <filter> UEFI: LENOVO v: C0CN25WW 
        date: 04/21/2015 
      Battery:
        ID-1: BAT1 charge: 6.3 Wh condition: 26.3/30.0 Wh (88%) model: SMP L14M2P22 
        status: Discharging 
      CPU:
        Topology: Dual Core model: Intel Celeron N2840 bits: 64 type: MCP arch: Silvermont 
        rev: 8 L2 cache: 1024 KiB 
        flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8663 
        Speed: 500 MHz min/max: 500/2582 MHz Core speeds (MHz): 1: 500 2: 500 
      Graphics:
        Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
        vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
        Display: server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa 
        resolution: 1366x768~60Hz 
        OpenGL: renderer: Mesa DRI Intel Bay Trail v: 3.3 Mesa 13.0.6 direct render: Yes 
      Audio:
        Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio 
        vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
        Sound Server: ALSA v: k4.19.25-antix.1-amd64-smp 
      Network:
        Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo 
        driver: r8169 v: kernel port: 1000 bus ID: 01:00.0 
        IF: eth0 state: down mac: <filter> 
        Device-2: Intel Wireless 3160 driver: iwlwifi v: kernel port: 1000 bus ID: 02:00.0 
        IF: wlan0 state: down mac: <filter> 
      Drives:
        Local Storage: total: 29.12 GiB used: 4.14 GiB (14.2%) 
        ID-1: /dev/mmcblk0 model: BGND3R size: 29.12 GiB 
      Partition:
        ID-1: / size: 7.81 GiB used: 4.14 GiB (53.0%) fs: ext4 dev: /dev/mmcblk0p2 
        ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/mmcblk0p3 
      Sensors:
        System Temperatures: cpu: 28.0 C mobo: N/A 
        Fan Speeds (RPM): N/A 
      Info:
        Processes: 169 Uptime: 1h 34m Memory: 1.83 GiB used: 225.4 MiB (12.0%) 
        Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.29
      • This topic was modified 4 years ago by Klaas Vaak.
      #20356
      Moderator
      caprea
        Helpful
        Up
        0
        ::

        The first thing that comes to mind is you pressed accidentally a hotkey for wlan.
        Does
        sudo rfkill unblock all
        help ?

        Hmm, I saw your thread on mx-forum about the start on bootscreen being stopped.Maybe your keyboard has a life of its own and presses one or more keys.

        #20358
        Member
        Klaas Vaak
          Helpful
          Up
          0
          ::

          The first thing that comes to mind is you pressed accidentally a hotkey for wlan.
          Does
          sudo rfkill unblock all
          help ?

          Caprea, you really are a star!! And that is not meant like a sycophantic remark, it is meant. Whenever you reply your advice is always useful. So yes, this worked. There is no wlan hotkey, but I (actually my wife, it’s her laptop) must have pressed a key that did this.

          Hmm, I saw your thread on mx-forum about the start on bootscreen being stopped.Maybe your keyboard has a life of its own and presses one or more keys.

          The bootscreen issue is not a major one, just an annoyance. If it is not solvable I/she will live with it.

          Regarding the keyboard, I started a thread about it being blocked after a de-suspension, you advised me to update the kernel to 4.19 or 4.20. The latest listed was 4.19.something, which I installed 2 days ago. It is a bit early yet to make a definitive statement, but so far so good. In any case I have not experienced any untoward effects yet. I will follow that issue up in the other thread.

          Anyway, thanks again for this simple, effective solution, you made my wife very happy. Thanks.

          • This reply was modified 4 years ago by Klaas Vaak.
          • This reply was modified 4 years ago by Klaas Vaak.
          #20362
          Moderator
          caprea
            Helpful
            Up
            0
            ::

            Thanks for the kind words, blushing, just like to help, and I like antiX.

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