Announcement

Collapse
No announcement yet.

Can't use wifi

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Can't use wifi

    Hi, just installed this.

    I cannot connect to WiFi as i get the message below.

    Other issues i found on my blog: http://nayarweb.com/blog/2015/kubunt...1-wifi-no-use/

    I am on a Dell Inspiron 5547
    Attached Files

    #2
    I have to manually enable my wifi adapter on each boot via keyboard. I don't use it much so haven't really investigated.

    What do $ ifconfig and $ iwconfig say?

    Post which card you have and someone may recognize it.

    Comment


      #3
      Well, i can find the SSIDs in the network manager. It just can't connect to it.
      Attached Files

      Comment


        #4
        Maybe $ tail -f /var/log/syslog as you try to connect will provide some clues.

        Comment


          #5
          Originally posted by ronw View Post
          Maybe $ tail -f /var/log/syslog as you try to connect will provide some clues.
          Can't make much sense from below.

          Code:
          Mar  2 21:40:40 nayar-area51 wpa_supplicant[1109]: wlan0: CTRL-EVENT-SCAN-STARTED 
          Mar  2 21:40:40 nayar-area51 NetworkManager[934]: <info> (wlan0): supplicant interface state: disconnected -> scanning
          Mar  2 21:40:42 nayar-area51 NetworkManager[934]: <warn> Activation (wlan0/wireless): association took too long, failing activation.
          Mar  2 21:40:42 nayar-area51 NetworkManager[934]: <info> (wlan0): device state change: config -> failed (reason 'ssid-not-found') [50 120 53]
          Mar  2 21:40:42 nayar-area51 NetworkManager[934]: <warn> Activation (wlan0) failed for connection ':P'
          Mar  2 21:40:42 nayar-area51 NetworkManager[934]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
          Mar  2 21:40:42 nayar-area51 NetworkManager[934]: <info> (wlan0): deactivating device (reason 'none') [0]
          Mar  2 21:40:42 nayar-area51 wpa_supplicant[1109]: wlan0: Reject scan trigger since one is already pending
          Mar  2 21:40:42 nayar-area51 NetworkManager[934]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
          Mar  2 21:40:45 nayar-area51 wpa_supplicant[1109]: wlan0: CTRL-EVENT-SCAN-STARTED

          Comment


            #6
            Code:
            lspci
            will show what wireless card you have ,,,,,,,,,,,,,I'm thinking Broadcom .

            if you go to system settings>Driver manager dose it offer you an updated driver .

            VINNY
            i7 4core HT 8MB L3 2.9GHz
            16GB RAM
            Nvidia GTX 860M 4GB RAM 1152 cuda cores

            Comment


              #7
              $ lspci
              ...
              03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev 01)
              03:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
              04:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
              $ tail -f /var/log/syslog
              Mar 5 08:13:20 Hydrant-II wpa_supplicant[1030]: wlan0: CTRL-EVENT-SCAN-STARTED
              Mar 5 08:13:20 Hydrant-II NetworkManager[939]: <info> (wlan0): supplicant interface sta
              te: disconnected -> scanning
              Mar 5 08:13:22 Hydrant-II NetworkManager[939]: <warn> Activation (wlan0/wireless): asso
              ciation took too long, failing activation.
              Mar 5 08:13:22 Hydrant-II NetworkManager[939]: <info> (wlan0): device state change: con
              fig -> failed (reason 'ssid-not-found') [50 120 53]
              Mar 5 08:13:22 Hydrant-II NetworkManager[939]: <warn> Activation (wlan0) failed for con
              nection 'Hydrant 1'
              Mar 5 08:13:22 Hydrant-II NetworkManager[939]: <warn> Couldn't disconnect supplicant in
              terface: This interface is not connected.
              Mar 5 08:13:22 Hydrant-II NetworkManager[939]: <info> (wlan0): device state change: fai
              led -> disconnected (reason 'none') [120 30 0]
              Mar 5 08:13:22 Hydrant-II NetworkManager[939]: <info> (wlan0): deactivating device (rea
              son 'none') [0]
              Mar 5 08:13:22 Hydrant-II wpa_supplicant[1030]: wlan0: Reject scan trigger since one is
              already pending
              Mar 5 08:13:22 Hydrant-II NetworkManager[939]: <warn> Couldn't disconnect supplicant in
              terface: This interface is not connected.
              Mar 5 08:13:25 Hydrant-II wpa_supplicant[1030]: wlan0: CTRL-EVENT-SCAN-STARTED



              Wired network works fine, symptoms otherwise as above. Same issue on Live CD and once installed on HDD and updated.

              Comment


                #8
                OK, once more with the system log:

                Mar 5 08:20:22 Hydrant-II NetworkManager[939]: <info> kernel firmware directory '/lib/f
                irmware' changed
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) starting conne
                ction 'Hydrant 1'
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) Stage 1 of 5 (
                Device Prepare) scheduled...
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) Stage 1 of 5 (
                Device Prepare) started...
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> (wlan0): device state change: dis
                connected -> prepare (reason 'none') [30 40 0]
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) Stage 2 of 5 (
                Device Configure) scheduled...
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) Stage 1 of 5 (
                Device Prepare) complete.
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) Stage 2 of 5 (
                Device Configure) starting...
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> (wlan0): device state change: pre
                pare -> config (reason 'none') [40 50 0]
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0/wireless): acce
                ss point 'Hydrant 1' has security, but secrets are required.
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> (wlan0): device state change: con
                fig -> need-auth (reason 'none') [50 60 0]
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) Stage 2 of 5 (
                Device Configure) complete.
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) Stage 1 of 5 (
                Device Prepare) scheduled...
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <warn> Couldn't disconnect supplicant in
                terface: This interface is not connected.
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) Stage 1 of 5 (
                Device Prepare) started...
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> (wlan0): device state change: nee
                d-auth -> prepare (reason 'none') [60 40 0]
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) Stage 2 of 5 (
                Device Configure) scheduled...
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) Stage 1 of 5 (
                Device Prepare) complete.
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) Stage 2 of 5 (
                Device Configure) starting...
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> (wlan0): device state change: pre
                pare -> config (reason 'none') [40 50 0]
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0/wireless): conn
                ection 'Hydrant 1' has security, and secrets exist. No new secrets needed.
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Config: added 'ssid' value 'Hydra
                nt'
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Config: added 'scan_ssid' value '
                1'
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Config: added 'key_mgmt' value 'W
                PA-PSK'
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Config: added 'auth_alg' value 'O
                PEN'
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Config: added 'psk' value '<omitt
                ed>'
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Activation (wlan0) Stage 2 of 5 (
                Device Configure) complete.
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <warn> Couldn't disconnect supplicant in
                terface: This interface is not connected.
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> Config: set interface ap_scan to
                1
                Mar 5 08:20:09 Hydrant-II wpa_supplicant[1030]: message repeated 8 times: [ wlan0: CTRL
                -EVENT-SCAN-STARTED ]
                Mar 5 08:21:03 Hydrant-II wpa_supplicant[1030]: wlan0: SME: Trying to authenticate with
                90:9f:33:31:fb:6c (SSID='Hydrant' freq=2412 MHz)
                Mar 5 08:21:03 Hydrant-II kernel: [ 3054.937881] wlan0: authenticate with 90:9f:33:31:f
                b:6c
                Mar 5 08:21:03 Hydrant-II kernel: [ 3054.938807] wlan0: send auth to 90:9f:33:31:fb:6c
                (try 1/3)
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> (wlan0): supplicant interface sta
                te: scanning -> authenticating
                Mar 5 08:21:03 Hydrant-II kernel: [ 3055.011855] wlan0: send auth to 90:9f:33:31:fb:6c
                (try 2/3)
                Mar 5 08:21:03 Hydrant-II kernel: [ 3055.084014] wlan0: send auth to 90:9f:33:31:fb:6c
                (try 3/3)
                Mar 5 08:21:03 Hydrant-II kernel: [ 3055.151097] wlan0: authentication with 90:9f:33:31
                :fb:6c timed out
                Mar 5 08:21:03 Hydrant-II wpa_supplicant[1030]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id
                =0 ssid="Hydrant" auth_failures=1 duration=10
                Mar 5 08:21:03 Hydrant-II NetworkManager[939]: <info> (wlan0): supplicant interface sta
                te: authenticating -> disconnected
                Mar 5 08:21:13 Hydrant-II wpa_supplicant[1030]: wlan0: CTRL-EVENT-SCAN-STARTED
                Mar 5 08:21:13 Hydrant-II NetworkManager[939]: <info> (wlan0): supplicant interface sta
                te: disconnected -> scanning
                Mar 5 08:21:17 Hydrant-II wpa_supplicant[1030]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 s
                sid="Hydrant"
                Mar 5 08:21:17 Hydrant-II wpa_supplicant[1030]: wlan0: SME: Trying to authenticate with
                90:9f:33:31:fb:6c (SSID='Hydrant' freq=2412 MHz)
                Mar 5 08:21:17 Hydrant-II kernel: [ 3068.963312] wlan0: authenticate with 90:9f:33:31:f
                b:6c
                Mar 5 08:21:17 Hydrant-II kernel: [ 3068.965205] wlan0: send auth to 90:9f:33:31:fb:6c
                (try 1/3)
                Mar 5 08:21:17 Hydrant-II NetworkManager[939]: <info> (wlan0): supplicant interface sta
                te: scanning -> authenticating
                Mar 5 08:21:17 Hydrant-II kernel: [ 3069.038508] wlan0: send auth to 90:9f:33:31:fb:6c
                (try 2/3)
                Mar 5 08:21:17 Hydrant-II kernel: [ 3069.104054] wlan0: send auth to 90:9f:33:31:fb:6c
                (try 3/3)
                Mar 5 08:21:17 Hydrant-II kernel: [ 3069.166052] wlan0: authentication with 90:9f:33:31
                :fb:6c timed out
                Mar 5 08:21:17 Hydrant-II wpa_supplicant[1030]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id
                =0 ssid="Hydrant" auth_failures=2 duration=20
                Mar 5 08:21:17 Hydrant-II NetworkManager[939]: <info> (wlan0): supplicant interface sta
                te: authenticating -> disconnected
                Mar 5 08:21:27 Hydrant-II wpa_supplicant[1030]: wlan0: CTRL-EVENT-SCAN-STARTED
                Mar 5 08:21:27 Hydrant-II NetworkManager[939]: <info> (wlan0): supplicant interface sta
                te: disconnected -> scanning
                Mar 5 08:21:28 Hydrant-II NetworkManager[939]: <warn> Activation (wlan0/wireless): asso
                ciation took too long, failing activation.
                Mar 5 08:21:28 Hydrant-II NetworkManager[939]: <info> (wlan0): device state change: con
                fig -> failed (reason 'ssid-not-found') [50 120 53]
                Mar 5 08:21:28 Hydrant-II NetworkManager[939]: <warn> Activation (wlan0) failed for con
                nection 'Hydrant 1'
                Mar 5 08:21:28 Hydrant-II NetworkManager[939]: <info> (wlan0): device state change: fai
                led -> disconnected (reason 'none') [120 30 0]
                Mar 5 08:21:28 Hydrant-II NetworkManager[939]: <info> (wlan0): deactivating device (rea
                son 'none') [0]
                Mar 5 08:21:28 Hydrant-II NetworkManager[939]: <warn> Couldn't disconnect supplicant in
                terface: This interface is not connected.
                Mar 5 08:21:28 Hydrant-II wpa_supplicant[1030]: wlan0: Reject scan trigger since one is
                already pending
                Mar 5 08:21:31 Hydrant-II wpa_supplicant[1030]: wlan0: CTRL-EVENT-SCAN-STARTED


                Driver Manager, btw, contains only "Using Processor micromode firmware for Intel CPUs from intel-microcode"

                Comment


                  #9
                  An obvious question, but, did you try clicking on either of the Available connections??
                  Using Kubuntu Linux since March 23, 2007
                  "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                  Comment


                    #10
                    Yes.

                    click network manager tray icon ---> click Connect on anything under Available Connections ---> (enter information or wallet password if needed) ---> wait ---> fails with the two error messages shown above. The selected SSID only gets to "Configuring Interface"

                    Comment


                      #11
                      Have you actually configured the wifi connection??
                      Using Kubuntu Linux since March 23, 2007
                      "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                      Comment


                        #12
                        Settings were autodetected and look fine, password is correct. Identical issue trying to connect to a completely unsecured open network. Was also unable to connect during installation from Live CD (worked fine with 14.10 and 14.04.02 Live CDs earlier same day).

                        At the risk of being equally obvious, I'm leaning toward assuming it's a bug.

                        Comment


                          #13
                          Is there a hardware switch and/or keyboard switch for turning on/off the wireless? And lastly, have you checked to see if a proprietary driver is available? System Settings > Driver Manager
                          Using Kubuntu Linux since March 23, 2007
                          "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                          Comment


                            #14
                            Activating the one (unrelated) proprietary driver had no effect.

                            There is no hardware switch for the wifi. There's a keyboard switch for airplane mode, but it has no effect. Going into and out of airplane mode in network manager clears then refreshes the list of SSIDs, but does not fix the problem.

                            WiFi worked under the 14.04.02 and 14.10 Live CDs, and it can see the SSIDs under the 15.04 beta, so I conclude that it is on. For every SSID it lists the detected form of security, a plausible signal strength, "never used", plus the MAC address of wlan0. I might have expected to see the access point's MAC address there instead, but I don't recall seeing any MAC address there in previous releases so I'm not sure what to expect.
                            Last edited by dpeets; Mar 04, 2015, 07:00 PM.

                            Comment


                              #15
                              When you click on the wrench in Networkmanager (upper right corner), highlight the wireless SSID connection name and click Edit, is All users may connect to this network checked? In the Wireless Security tab, what Security is being used? Is Password filled in?
                              Using Kubuntu Linux since March 23, 2007
                              "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                              Comment

                              Working...
                              X