Announcement

Collapse
No announcement yet.

Wifi keeps disconnecting

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    [Internet] Wifi keeps disconnecting

    Hi,

    I just installed Kubuntu and the wifi keeps disconnecting. Then Mozilla says "Hum, we"re having trouble finding that site". Or sometimes it says this and if I click on the wifi icon on the bottom bar I see zero bits going up and zero bits coming down. The fix here is to manually disconnect and reconnect. Then the problem starts again...

    Even while I was playing a game on the computer, I kept being pestered by messages from the wifi.

    I saw on another post that I had to show the output of : sudo lshw -C net :

    Code:
    *-network                 
     description: Ethernet interface
     product: NetLink BCM57780 Gigabit Ethernet PCIe
     vendor: Broadcom Limited
     physical id: 0
     bus info: pci@0000:01:00.0
     logical name: enp1s0
     version: 01
     serial: dc:0e:a1:b3:63:8a
     size: 10Mbit/s
     capacity: 1Gbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.137 duplex=half firmware=sb latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:27 memory:b3400000-b340ffff
*-network
     description: Wireless interface
     product: AR9287 Wireless Network Adapter (PCI-Express)
     vendor: Qualcomm Atheros
     physical id: 0
     bus info: pci@0000:02:00.0
     logical name: wlp2s0
     version: 01
     serial: 9c:b7:0d:e5:a1:67
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
     configuration: broadcast=yes driver=ath9k driverversion=4.10.0-42-generic firmware=N/A ip=192.168.0.100 latency=0 link=no multicast=yes wireless=IEEE 802.11
     resources: irq:17 memory:b2400000-b240ffff
    And the syslog file (shortened because it's too long) :
    Code:
    Dec 28 07:35:05 kub rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="589" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Dec 28 07:35:23 kub anacron[3341]: Job `cron.daily' terminated
Dec 28 07:35:23 kub anacron[3341]: Normal exit (1 job run)
Dec 28 07:38:52 kub dhclient[2692]: DHCPREQUEST of 192.168.0.100 on wlp2s0 to 192.168.0.1 port 67 (xid=0x54a35aff)
Dec 28 07:38:52 kub dhclient[2692]: DHCPACK of 192.168.0.100 from 192.168.0.1
Dec 28 07:38:52 kub NetworkManager[856]: <info>  [1514443132.5186] dhcp4 (wlp2s0):   address 192.168.0.100
Dec 28 07:38:52 kub NetworkManager[856]: <info>  [1514443132.5187] dhcp4 (wlp2s0):   plen 24 (255.255.255.0)
Dec 28 07:38:52 kub NetworkManager[856]: <info>  [1514443132.5187] dhcp4 (wlp2s0):   gateway 192.168.0.1
Dec 28 07:38:52 kub NetworkManager[856]: <info>  [1514443132.5187] dhcp4 (wlp2s0):   server identifier 192.168.0.1
Dec 28 07:38:52 kub NetworkManager[856]: <info>  [1514443132.5188] dhcp4 (wlp2s0):   lease time 7200
Dec 28 07:38:52 kub NetworkManager[856]: <info>  [1514443132.5188] dhcp4 (wlp2s0):   nameserver '192.168.0.1'
Dec 28 07:38:52 kub NetworkManager[856]: <info>  [1514443132.5188] dhcp4 (wlp2s0): state changed bound -> bound
Dec 28 07:38:52 kub dbus[630]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Dec 28 07:38:52 kub systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 28 07:38:52 kub dbus[630]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 28 07:38:52 kub systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 28 07:38:52 kub nm-dispatcher: req:1 'dhcp4-change' [wlp2s0]: new request (1 scripts)
Dec 28 07:38:52 kub nm-dispatcher: req:1 'dhcp4-change' [wlp2s0]: start running ordered scripts...
Dec 28 07:38:52 kub dhclient[2692]: bound to 192.168.0.100 -- renewal in 3095 seconds.
Dec 28 08:17:01 kub CRON[3518]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 28 08:30:27 kub dhclient[2692]: DHCPREQUEST of 192.168.0.100 on wlp2s0 to 192.168.0.1 port 67 (xid=0x54a35aff)
Dec 28 08:30:27 kub dhclient[2692]: DHCPACK of 192.168.0.100 from 192.168.0.1
Dec 28 08:30:27 kub NetworkManager[856]: <info>  [1514446227.9227] dhcp4 (wlp2s0):   address 192.168.0.100
Dec 28 08:30:27 kub NetworkManager[856]: <info>  [1514446227.9228] dhcp4 (wlp2s0):   plen 24 (255.255.255.0)
Dec 28 08:30:27 kub NetworkManager[856]: <info>  [1514446227.9229] dhcp4 (wlp2s0):   gateway 192.168.0.1
Dec 28 08:30:27 kub NetworkManager[856]: <info>  [1514446227.9229] dhcp4 (wlp2s0):   server identifier 192.168.0.1
Dec 28 08:30:27 kub NetworkManager[856]: <info>  [1514446227.9230] dhcp4 (wlp2s0):   lease time 7200
Dec 28 08:30:27 kub NetworkManager[856]: <info>  [1514446227.9230] dhcp4 (wlp2s0):   nameserver '192.168.0.1'
Dec 28 08:30:27 kub NetworkManager[856]: <info>  [1514446227.9230] dhcp4 (wlp2s0): state changed bound -> bound
Dec 28 08:30:27 kub dbus[630]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Dec 28 08:30:27 kub systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 28 08:30:27 kub dbus[630]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 28 08:30:27 kub systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 28 08:30:27 kub nm-dispatcher: req:1 'dhcp4-change' [wlp2s0]: new request (1 scripts)
Dec 28 08:30:27 kub nm-dispatcher: req:1 'dhcp4-change' [wlp2s0]: start running ordered scripts...
Dec 28 08:30:28 kub dhclient[2692]: bound to 192.168.0.100 -- renewal in 2968 seconds.
Dec 28 09:17:01 kub CRON[3556]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 28 09:19:56 kub dhclient[2692]: DHCPREQUEST of 192.168.0.100 on wlp2s0 to 192.168.0.1 port 67 (xid=0x54a35aff)
Dec 28 09:19:56 kub dhclient[2692]: DHCPACK of 192.168.0.100 from 192.168.0.1
Dec 28 09:19:56 kub NetworkManager[856]: <info>  [1514449196.2078] dhcp4 (wlp2s0):   address 192.168.0.100
Dec 28 09:19:56 kub NetworkManager[856]: <info>  [1514449196.2078] dhcp4 (wlp2s0):   plen 24 (255.255.255.0)
Dec 28 09:19:56 kub NetworkManager[856]: <info>  [1514449196.2079] dhcp4 (wlp2s0):   gateway 192.168.0.1
Dec 28 09:19:56 kub NetworkManager[856]: <info>  [1514449196.2079] dhcp4 (wlp2s0):   server identifier 192.168.0.1
Dec 28 09:19:56 kub NetworkManager[856]: <info>  [1514449196.2079] dhcp4 (wlp2s0):   lease time 7200
Dec 28 09:19:56 kub NetworkManager[856]: <info>  [1514449196.2080] dhcp4 (wlp2s0):   nameserver '192.168.0.1'
Dec 28 09:19:56 kub NetworkManager[856]: <info>  [1514449196.2080] dhcp4 (wlp2s0): state changed bound -> bound
Dec 28 09:19:56 kub dbus[630]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Dec 28 09:19:56 kub systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 28 09:19:56 kub dbus[630]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 28 09:19:56 kub systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 28 09:19:56 kub nm-dispatcher: req:1 'dhcp4-change' [wlp2s0]: new request (1 scripts)
Dec 28 09:19:56 kub nm-dispatcher: req:1 'dhcp4-change' [wlp2s0]: start running ordered scripts...
Dec 28 09:19:56 kub dhclient[2692]: bound to 192.168.0.100 -- renewal in 3318 seconds.
Dec 28 09:38:20 kub dbus[630]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Dec 28 09:38:20 kub org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
Dec 28 09:38:20 kub org.kde.powerdevil.backlighthelper: message repeated 2 times: [ QDBusArgument: read from a write-only object]
Dec 28 09:38:20 kub dbus[630]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Dec 28 09:39:03 kub wpa_supplicant[973]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=c4:6e:1f:86:e7:f0 reason=4 locally_generated=1
Dec 28 09:39:03 kub NetworkManager[856]: <warn>  [1514450343.6639] sup-iface[0x8ca3e00,wlp2s0]: connection disconnected (reason -4)
Dec 28 09:39:03 kub wpa_supplicant[973]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 28 09:39:03 kub NetworkManager[856]: <info>  [1514450343.6691] device (wlp2s0): supplicant interface state: completed -> disconnected
Dec 28 09:39:03 kub NetworkManager[856]: <info>  [1514450343.7731] device (wlp2s0): supplicant interface state: disconnected -> scanning
Dec 28 09:39:04 kub kernel: [62637.395226] wlp2s0: authenticate with c4:6e:1f:86:e7:f0
Dec 28 09:39:04 kub wpa_supplicant[973]: wlp2s0: SME: Trying to authenticate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 09:39:04 kub NetworkManager[856]: <info>  [1514450344.7344] device (wlp2s0): supplicant interface state: scanning -> authenticating
Dec 28 09:39:04 kub kernel: [62637.419480] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 09:39:04 kub wpa_supplicant[973]: wlp2s0: Trying to associate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 09:39:04 kub kernel: [62637.422222] wlp2s0: authenticated
Dec 28 09:39:04 kub kernel: [62637.426118] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 09:39:04 kub NetworkManager[856]: <info>  [1514450344.7427] device (wlp2s0): supplicant interface state: authenticating -> associating
Dec 28 09:39:04 kub wpa_supplicant[973]: wlp2s0: Associated with c4:6e:1f:86:e7:f0
Dec 28 09:39:04 kub wpa_supplicant[973]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to c4:6e:1f:86:e7:f0 completed [id=0 id_str=]
Dec 28 09:39:04 kub kernel: [62637.538608] wlp2s0: RX AssocResp from c4:6e:1f:86:e7:f0 (capab=0x421 status=0 aid=2)
Dec 28 09:39:04 kub kernel: [62637.538773] wlp2s0: associated
Dec 28 09:39:04 kub NetworkManager[856]: <info>  [1514450344.8595] device (wlp2s0): supplicant interface state: associating -> completed
Dec 28 09:41:04 kub wpa_supplicant[973]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=c4:6e:1f:86:e7:f0 reason=4 locally_generated=1
Dec 28 09:41:04 kub NetworkManager[856]: <warn>  [1514450464.6837] sup-iface[0x8ca3e00,wlp2s0]: connection disconnected (reason -4)
Dec 28 09:41:04 kub NetworkManager[856]: <info>  [1514450464.6874] device (wlp2s0): supplicant interface state: completed -> disconnected
Dec 28 09:41:04 kub wpa_supplicant[973]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 28 09:41:04 kub NetworkManager[856]: <info>  [1514450464.7913] device (wlp2s0): supplicant interface state: disconnected -> scanning
Dec 28 09:41:05 kub kernel: [62758.420162] wlp2s0: authenticate with c4:6e:1f:86:e7:f0
Dec 28 09:41:05 kub wpa_supplicant[973]: wlp2s0: SME: Trying to authenticate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 09:41:05 kub kernel: [62758.445033] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 09:41:05 kub NetworkManager[856]: <info>  [1514450465.7506] device (wlp2s0): supplicant interface state: scanning -> authenticating
Dec 28 09:41:06 kub wpa_supplicant[973]: wlp2s0: Trying to associate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 09:41:06 kub kernel: [62758.742169] wlp2s0: authenticated
Dec 28 09:41:06 kub kernel: [62758.743377] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 09:41:06 kub NetworkManager[856]: <info>  [1514450466.0534] device (wlp2s0): supplicant interface state: authenticating -> associating
Dec 28 09:41:06 kub kernel: [62759.291441] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 2/3)
Dec 28 09:41:06 kub kernel: [62759.474504] wlp2s0: RX AssocResp from c4:6e:1f:86:e7:f0 (capab=0x421 status=0 aid=2)
Dec 28 09:41:06 kub kernel: [62759.474673] wlp2s0: associated
Dec 28 09:41:06 kub wpa_supplicant[973]: wlp2s0: Associated with c4:6e:1f:86:e7:f0
Dec 28 09:41:06 kub wpa_supplicant[973]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to c4:6e:1f:86:e7:f0 completed [id=0 id_str=]
Dec 28 09:41:06 kub NetworkManager[856]: <info>  [1514450466.7862] device (wlp2s0): supplicant interface state: associating -> completed
Dec 28 09:41:37 kub dbus[630]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Dec 28 09:41:37 kub org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
Dec 28 09:41:37 kub org.kde.powerdevil.backlighthelper: message repeated 2 times: [ QDBusArgument: read from a write-only object]
Dec 28 09:41:37 kub dbus[630]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Dec 28 09:42:52 kub dbus[630]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Dec 28 09:42:52 kub org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
Dec 28 09:42:52 kub org.kde.powerdevil.backlighthelper: message repeated 2 times: [ QDBusArgument: read from a write-only object]
Dec 28 09:42:52 kub dbus[630]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Dec 28 09:44:07 kub dbus[630]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Dec 28 09:44:07 kub org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
Dec 28 09:44:07 kub org.kde.powerdevil.backlighthelper: message repeated 2 times: [ QDBusArgument: read from a write-only object]
Dec 28 09:44:07 kub dbus[630]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Dec 28 10:15:15 kub dhclient[2692]: DHCPREQUEST of 192.168.0.100 on wlp2s0 to 192.168.0.1 port 67 (xid=0x54a35aff)
Dec 28 10:15:15 kub dhclient[2692]: DHCPACK of 192.168.0.100 from 192.168.0.1
Dec 28 10:15:15 kub NetworkManager[856]: <info>  [1514452515.0599] dhcp4 (wlp2s0):   address 192.168.0.100
Dec 28 10:15:15 kub NetworkManager[856]: <info>  [1514452515.0600] dhcp4 (wlp2s0):   plen 24 (255.255.255.0)
Dec 28 10:15:15 kub NetworkManager[856]: <info>  [1514452515.0600] dhcp4 (wlp2s0):   gateway 192.168.0.1
Dec 28 10:15:15 kub NetworkManager[856]: <info>  [1514452515.0601] dhcp4 (wlp2s0):   server identifier 192.168.0.1
Dec 28 10:15:15 kub NetworkManager[856]: <info>  [1514452515.0601] dhcp4 (wlp2s0):   lease time 7200
Dec 28 10:15:15 kub NetworkManager[856]: <info>  [1514452515.0602] dhcp4 (wlp2s0):   nameserver '192.168.0.1'
Dec 28 10:15:15 kub NetworkManager[856]: <info>  [1514452515.0602] dhcp4 (wlp2s0): state changed bound -> bound
Dec 28 10:15:15 kub dbus[630]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Dec 28 10:15:15 kub systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 28 10:15:15 kub dbus[630]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 28 10:15:15 kub systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 28 10:15:15 kub nm-dispatcher: req:1 'dhcp4-change' [wlp2s0]: new request (1 scripts)
Dec 28 10:15:15 kub nm-dispatcher: req:1 'dhcp4-change' [wlp2s0]: start running ordered scripts...
Dec 28 10:15:15 kub dhclient[2692]: bound to 192.168.0.100 -- renewal in 3098 seconds.
Dec 28 10:17:01 kub CRON[3797]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 28 10:55:13 kub dbus[630]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Dec 28 10:55:13 kub org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
Dec 28 10:55:13 kub org.kde.powerdevil.backlighthelper: message repeated 2 times: [ QDBusArgument: read from a write-only object]
Dec 28 10:55:13 kub dbus[630]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Dec 28 10:55:33 kub wpa_supplicant[973]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=c4:6e:1f:86:e7:f0 reason=4 locally_generated=1
Dec 28 10:55:33 kub NetworkManager[856]: <warn>  [1514454933.1011] sup-iface[0x8ca3e00,wlp2s0]: connection disconnected (reason -4)
Dec 28 10:55:33 kub wpa_supplicant[973]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 28 10:55:33 kub NetworkManager[856]: <info>  [1514454933.1033] device (wlp2s0): supplicant interface state: completed -> disconnected
Dec 28 10:55:33 kub NetworkManager[856]: <info>  [1514454933.2070] device (wlp2s0): supplicant interface state: disconnected -> scanning
Dec 28 10:55:34 kub kernel: [67227.144711] wlp2s0: authenticate with c4:6e:1f:86:e7:f0
Dec 28 10:55:34 kub wpa_supplicant[973]: wlp2s0: SME: Trying to authenticate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 10:55:34 kub NetworkManager[856]: <info>  [1514454934.1704] device (wlp2s0): supplicant interface state: scanning -> authenticating
Dec 28 10:55:34 kub kernel: [67227.168539] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 10:55:34 kub wpa_supplicant[973]: wlp2s0: Trying to associate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 10:55:34 kub kernel: [67227.234036] wlp2s0: authenticated
Dec 28 10:55:34 kub kernel: [67227.235546] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 10:55:34 kub NetworkManager[856]: <info>  [1514454934.2412] device (wlp2s0): supplicant interface state: authenticating -> associating
Dec 28 10:55:34 kub kernel: [67227.375556] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 2/3)
Dec 28 10:55:34 kub kernel: [67227.419917] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 3/3)
Dec 28 10:55:34 kub kernel: [67227.475508] wlp2s0: association with c4:6e:1f:86:e7:f0 timed out
Dec 28 10:55:34 kub NetworkManager[856]: <info>  [1514454934.5073] device (wlp2s0): supplicant interface state: associating -> disconnected
Dec 28 10:55:35 kub NetworkManager[856]: <info>  [1514454935.0146] device (wlp2s0): supplicant interface state: disconnected -> scanning
Dec 28 10:55:35 kub kernel: [67228.952499] wlp2s0: authenticate with c4:6e:1f:86:e7:f0
Dec 28 10:55:35 kub wpa_supplicant[973]: wlp2s0: SME: Trying to authenticate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 10:55:35 kub NetworkManager[856]: <info>  [1514454935.9781] device (wlp2s0): supplicant interface state: scanning -> authenticating
Dec 28 10:55:35 kub wpa_supplicant[973]: wlp2s0: Trying to associate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 10:55:35 kub kernel: [67228.976295] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 10:55:35 kub kernel: [67228.978524] wlp2s0: authenticated
Dec 28 10:55:35 kub kernel: [67228.979758] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 10:55:35 kub NetworkManager[856]: <info>  [1514454935.9853] device (wlp2s0): supplicant interface state: authenticating -> associating
Dec 28 10:55:36 kub kernel: [67229.183692] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 2/3)
Dec 28 10:55:36 kub kernel: [67229.287707] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 3/3)
Dec 28 10:55:36 kub kernel: [67229.443712] wlp2s0: association with c4:6e:1f:86:e7:f0 timed out
Dec 28 10:55:36 kub NetworkManager[856]: <info>  [1514454936.4751] device (wlp2s0): supplicant interface state: associating -> disconnected
Dec 28 10:55:37 kub NetworkManager[856]: <info>  [1514454937.4832] device (wlp2s0): supplicant interface state: disconnected -> scanning
Dec 28 10:55:38 kub wpa_supplicant[973]: wlp2s0: SME: Trying to authenticate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 10:55:38 kub kernel: [67231.418509] wlp2s0: authenticate with c4:6e:1f:86:e7:f0
Dec 28 10:55:38 kub NetworkManager[856]: <info>  [1514454938.4428] device (wlp2s0): supplicant interface state: scanning -> authenticating
Dec 28 10:55:38 kub kernel: [67231.441184] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 10:55:38 kub wpa_supplicant[973]: wlp2s0: Trying to associate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 10:55:38 kub kernel: [67231.631878] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 2/3)
Dec 28 10:55:38 kub kernel: [67231.634377] wlp2s0: authenticated
Dec 28 10:55:38 kub kernel: [67231.636123] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 10:55:38 kub NetworkManager[856]: <info>  [1514454938.6413] device (wlp2s0): supplicant interface state: authenticating -> associating
Dec 28 10:55:38 kub kernel: [67231.738324] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 2/3)
Dec 28 10:55:38 kub kernel: [67231.891889] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 3/3)
Dec 28 10:55:38 kub kernel: [67231.899134] wlp2s0: RX AssocResp from c4:6e:1f:86:e7:f0 (capab=0x421 status=0 aid=2)
Dec 28 10:55:38 kub kernel: [67231.899305] wlp2s0: associated
Dec 28 10:55:38 kub wpa_supplicant[973]: wlp2s0: Associated with c4:6e:1f:86:e7:f0
Dec 28 10:55:38 kub wpa_supplicant[973]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to c4:6e:1f:86:e7:f0 completed [id=0 id_str=]
Dec 28 10:55:38 kub NetworkManager[856]: <info>  [1514454938.9062] device (wlp2s0): supplicant interface state: associating -> completed
Dec 28 10:55:42 kub wpa_supplicant[973]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=c4:6e:1f:86:e7:f0 reason=4 locally_generated=1
Dec 28 10:55:42 kub NetworkManager[856]: <warn>  [1514454942.6506] sup-iface[0x8ca3e00,wlp2s0]: connection disconnected (reason -4)
Dec 28 10:55:42 kub NetworkManager[856]: <info>  [1514454942.6553] device (wlp2s0): supplicant interface state: completed -> disconnected
Dec 28 10:55:42 kub wpa_supplicant[973]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 28 10:55:42 kub NetworkManager[856]: <info>  [1514454942.7589] device (wlp2s0): supplicant interface state: disconnected -> scanning
Dec 28 10:55:43 kub kernel: [67236.694940] wlp2s0: authenticate with c4:6e:1f:86:e7:f0
Dec 28 10:55:43 kub wpa_supplicant[973]: wlp2s0: SME: Trying to authenticate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 10:55:43 kub NetworkManager[856]: <info>  [1514454943.7195] device (wlp2s0): supplicant interface state: scanning -> authenticating
Dec 28 10:55:43 kub kernel: [67236.718387] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 10:55:44 kub kernel: [67237.580275] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 2/3)
Dec 28 10:55:44 kub kernel: [67237.748314] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 3/3)
Dec 28 10:55:45 kub kernel: [67238.604310] wlp2s0: authentication with c4:6e:1f:86:e7:f0 timed out
Dec 28 10:55:45 kub NetworkManager[856]: <info>  [1514454945.6349] device (wlp2s0): supplicant interface state: authenticating -> disconnected
Dec 28 10:55:46 kub NetworkManager[856]: <info>  [1514454946.1423] device (wlp2s0): supplicant interface state: disconnected -> scanning
Dec 28 10:55:47 kub kernel: [67240.081229] wlp2s0: authenticate with c4:6e:1f:86:e7:f0
Dec 28 10:55:47 kub wpa_supplicant[973]: wlp2s0: SME: Trying to authenticate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 10:55:47 kub kernel: [67240.103990] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 10:55:47 kub NetworkManager[856]: <info>  [1514454947.1049] device (wlp2s0): supplicant interface state: scanning -> authenticating
Dec 28 10:55:47 kub kernel: [67240.232473] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 2/3)
Dec 28 10:55:47 kub kernel: [67240.284518] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 3/3)
Dec 28 10:55:47 kub kernel: [67240.333652] wlp2s0: authentication with c4:6e:1f:86:e7:f0 timed out
Dec 28 10:55:47 kub NetworkManager[856]: <info>  [1514454947.3632] device (wlp2s0): supplicant interface state: authenticating -> disconnected
Dec 28 10:55:47 kub org.kde.kuiserver[1092]: kuiserver: adding job contact for address:  ":1.22"  objectPath:  "/DataEngine/applicationjobs/JobView_1"
Dec 28 10:55:47 kub org.kde.kuiserver[1092]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_1"
Dec 28 10:55:47 kub org.kde.kuiserver[1092]: kuiserver: removing jobview from list, it finished
Dec 28 10:55:48 kub NetworkManager[856]: <info>  [1514454948.3711] device (wlp2s0): supplicant interface state: disconnected -> scanning
Dec 28 10:55:49 kub kernel: [67242.329349] wlp2s0: authenticate with c4:6e:1f:86:e7:f0
Dec 28 10:55:49 kub wpa_supplicant[973]: wlp2s0: SME: Trying to authenticate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 10:55:49 kub NetworkManager[856]: <info>  [1514454949.3467] device (wlp2s0): supplicant interface state: scanning -> authenticating
Dec 28 10:55:49 kub kernel: [67242.345882] wlp2s0: send auth to c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 10:55:49 kub wpa_supplicant[973]: wlp2s0: Trying to associate with c4:6e:1f:86:e7:f0 (SSID='kubnet' freq=2417 MHz)
Dec 28 10:55:49 kub kernel: [67242.350660] wlp2s0: authenticated
Dec 28 10:55:49 kub kernel: [67242.352659] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 1/3)
Dec 28 10:55:49 kub NetworkManager[856]: <info>  [1514454949.3564] device (wlp2s0): supplicant interface state: authenticating -> associating
Dec 28 10:55:49 kub kernel: [67242.456612] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 2/3)
Dec 28 10:55:50 kub kernel: [67243.596717] wlp2s0: associate with c4:6e:1f:86:e7:f0 (try 3/3)
Dec 28 10:55:50 kub kernel: [67243.904732] wlp2s0: association with c4:6e:1f:86:e7:f0 timed out
Dec 28 10:55:50 kub wpa_supplicant[973]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="kubnet" auth_failures=1 duration=10 reason=CONN_FAILED
Dec 28 10:55:50 kub NetworkManager[856]: <info>  [1514454950.9353] device (wlp2s0): supplicant interface state: associating -> disconnected
Dec 28 10:55:55 kub NetworkManager[856]: <info>  [1514454955.9479] device (wlp2s0): supplicant interface state: disconnected -> scanning
Dec 28 10:55:57 kub NetworkManager[856]: <warn>  [1514454957.5854] device (wlp2s0): link timed out.
Dec 28 10:55:57 kub NetworkManager[856]: <info>  [1514454957.5855] device (wlp2s0): state change: activated -> failed (reason 'supplicant-timeout') [100 120 11]
Dec 28 10:55:57 kub NetworkManager[856]: <info>  [1514454957.5859] manager: NetworkManager state is now CONNECTED_LOCAL
Dec 28 10:55:57 kub NetworkManager[856]: <info>  [1514454957.5861] manager: NetworkManager state is now DISCONNECTED
Dec 28 10:55:57 kub whoopsie[1000]: [10:55:57] offline
    Last edited by oshunluvr; Dec 28, 2017, 08:39 AM.
    Tags: None
    • Top
    • Bottom
    #2
    Please, when posing a lengthy copy from a source like in this post, use the CODE tags so the text in enclosed in a scroll box. This makes the post much more readable because it puts your text in a scroll-able box. As it was - many folks will just move onto the next post because it's just too hard to scroll through page after page of often unhelpful text. You'll get more replies from a well formatted post.

    To use the tags, click the CODE (hash or pound sign icon) tag in the formatting bar and the tags will appear like this [TAG][/TAG], then paste your text inside the tag boxes. Alternately, highlight text after pasting and then click the tag icon.

    I edited it for you this time. Good luck with your issue.

    Please Read Me
    • Top
    • Bottom

    Comment

      #3
      I have an Atheros AR9462 that was behaving identically to what yours is doing.

      I created the following file:
      /etc.modprobe.d/ath9k.conf

      and put the following lines in it:
      options ath9k blink=0
      options ath9k nohwcrypt=1
      options ath9k btcoex=1
      options ath9k bt_ant_diversity=1
      options ath9k ps_enable=0
      options ath9k use_chnctx=1
      Those settings may need to be tweaked to help your case, but they stopped the disconnecting. What replaced that behavior was the speed dropping from 54Mbps to 1Mpbs with no apparent activity. I'd disconnect and reconnect the wireless to get it active again.

      My laptop is an Acer V3-771G. I was using a Cisco Linksys E2500 wifi router with DD-WRT's firmware burned in, but I could never get it into a working 5GHz mode, so the best I could get was the 2GHz band at 54Mbps. (802.11g) It wan't a dual band router. So, I decided to get an dual band type router with DD-WRT already burned in. I chose the Buffalo N600
      https://www.amazon.com/Buffalo-AirSt.../dp/B0096239G0

      WHAT A DIFFERENCE a good wifi makes. I can simultaneously have GreyGeek2 and GreyGeek5 as AP's and my wifti to laptop speed on GreyGeek5 has gone as high as 300Mbps+. I am on a 100Mbps symmetric fiber optic cable, so my speed improvement is significant. My download speed has been limited only by the internet webserver supplying the files. My wifi connection never slows to 1Mbps or stops working.

      IOW, it turned out that the Atheros wifi chip in this laptop was good all along. The bottleneck was the wifi router and its reliability. It may be your bottleneck too.

      PS: In the N-Band setting an iPhone6 wouldn't connect to the wifi. With the Buffalo it can connect to either band. I always use the 5GHz band.
      Last edited by GreyGeek; Dec 28, 2017, 04:05 PM.
      "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
      – John F. Kennedy, February 26, 1962.
      • Top
      • Bottom

      Comment

        #4
        Originally posted by GreyGeek View Post
        I created the following file:
        /etc.modprobe.d/ath9k.conf
        Is that a typo GreyGeek?

        Shouldn't it be:
        /etc/modprobe.d/ath9k.conf

        Don't want to confuse the newbie any more than necessary.
        Last edited by Rod J; Dec 28, 2017, 07:44 PM.
        Desktop PC: Intel Core-i5-4670 3.40Ghz, 16Gb Crucial ram, Asus H97-Plus MB, 128Gb Crucial SSD + 2Tb Seagate Barracuda 7200.14 HDD running Kubuntu 18.04 LTS and Kubuntu 14.04 LTS (on SSD).
        Laptop: HP EliteBook 8460p Core-i5-2540M, 4Gb ram, Transcend 120Gb SSD, currently running Deepin 15.8 and Manjaro KDE 18.
        • Top
        • Bottom

        Comment

          #5
          Try this

          Find the file

          /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

          Open it as root and edit the option

          wifi.powersave = 3

          And change the 3 to 2

          Sent from my ONEPLUS A5010 using Tapatalk
          • Top
          • Bottom

          Comment

            #6
            Originally posted by Rod J View Post
            Is that a typo GreyGeek?

            Shouldn't it be:
            /etc/modprobe.d/ath9k.conf

            Don't want to confuse the newbie any more than necessary.
            yup. *blushes*
            "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
            – John F. Kennedy, February 26, 1962.
            • Top
            • Bottom

            Comment

              #7
              Thank you all. I'll try to find out how to use code tags next time.
              Sorry GreyGeek, I couldn't tweak your file. I have no idea what any of that means.
              I changed the default-wifi-powersave-on.conf file. Setting wifi.powersave to 2 seems to function. At least for now.
              What if I set it to 1? Or to 0? Wouldn"t it be even better? I don't need to save power, I'm on mains.

              For the next newbie, the command to know here is "sudo nano <filename>". You can edit any text file with it.
              • Top
              • Bottom

              Comment

                #8
                3 is enable. 2 is disable.
                • Top
                • Bottom

                Comment

                  #9
                  Later.

                  Hum, no. It started playing up again. Should I reboot after making the change?
                  • Top
                  • Bottom

                  Comment

                    #10
                    Originally posted by mr_raider View Post
                    3 is enable. 2 is disable.
                    Strange. Why not 0 and 1?
                    • Top
                    • Bottom

                    Comment

                      #11
                      Originally posted by Marianne View Post
                      Should I reboot after making the change?
                      Yes. Not all configuration changes are dynamic, and require either a logout or reboot to take effect. If your problem persists after logging out/rebooting, further digging is required.
                      Using Kubuntu Linux since March 23, 2007
                      "It is a capital mistake to theorize before one has data." - Sherlock Holmes​
                      • Top
                      • Bottom

                      Comment

                      Previous template Next
                      Working...
                      X