Intel Wireless AC 7260 WiFi: no data transfer on Linux with Dlink AP (iwlwifi, iwlmvm)

Bug #1497825 reported by André Heynatz
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I have a problem with a Wireless connection over a Dlink router using an Intel 7260 rev bb chip (802.11ac speed), or rev 0x144 according to iwlwifi. Another access point has worked well, but this one is not working. If I enable an access point on my Android 4.4.2 device Motorola Moto E (Qualcomm Snapdragon 200), it is working, but it is a mobile connection with limited volume.
On the same PC I have a Windows 7 SP1 64 Bit installation, and am using the full featured Intel driver Wireless_18.11.0_s64.exe. On Windows, I have absolutely no problem with the WiFi connection over Dlink router. Excellent signal strength, and 72 MBit/s speed (WPA2-PSK, AES, 802.11n).
I am using Linux Mint 17.2 which is based on Ubuntu 14.04.2 LTS and uses a 3.16 kernel. I have installed the Linux firmware update and iwlwifi 7260 firmware 14 additionally to test out some newer kernels from ppa. No kernel works, but here is the table of my experiments, referring to https://wireless.wiki.kernel.org/en/users/Drivers/iwlwifi and 'modinfo iwlwifi':

Kernel Documented FW FW used (modinfo) FW used (iwlwifi)
3.16 9 9
4.0.9 12 10
4.1.7 13 12
4.2.0 14 12 25.30.14.0 op_mode iwlmvm
4.3.0rc1 14 12

On Linux, the signal strength is much lower than on Windows, about 50%. And I get no data transfer, DNS resolution already fails. The connection seems to be established.
I hope that the functionality of the Windows driver can be transferred to Linux, because it works so well. But it is quite new, from August 2015.
I have seen new uploads for linux-firmware, until firmware 16. Is there a kernel or driver to test it? I could compile it and give a feedback.

I have used the WiFi connection in Germany with an AVM 7490 router successfully, and am now in Ecuador. All tests have been done in Ecuador. Setting the regulatory domain to the correct value with "sudo iw reg set EC" leads to repeated disconnects, so I assume "US" is working better, it is automatically set according to dmesg dump.

Here is a filtered dmesg dump of the 4.2.0 kernel test:

[ 5.868916] iwlwifi 0000:06:00.0: Direct firmware load for iwlwifi-7260-15.ucode failed with error -2
[ 5.879942] iwlwifi 0000:06:00.0: loaded firmware version 25.30.14.0 op_mode iwlmvm
[ 5.911923] iwlwifi 0000:06:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144
[ 5.911976] iwlwifi 0000:06:00.0: L1 Disabled - LTR Disabled
[ 5.912202] iwlwifi 0000:06:00.0: L1 Disabled - LTR Disabled
[ 5.934333] cfg80211: World regulatory domain updated:
[ 5.934336] cfg80211: DFS Master region: unset
[ 5.934337] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 5.934339] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 5.934341] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 5.934342] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 5.934343] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 5.934345] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 6.141534] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 6.493114] iwlwifi 0000:06:00.0: L1 Disabled - LTR Disabled
[ 6.493365] iwlwifi 0000:06:00.0: L1 Disabled - LTR Disabled
[ 6.699109] iwlwifi 0000:06:00.0: L1 Disabled - LTR Disabled
[ 6.699355] iwlwifi 0000:06:00.0: L1 Disabled - LTR Disabled
[ 6.711736] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 10.159730] wlan0: authenticate with c0:a0:bb:13:a9:fa
[ 10.164836] wlan0: send auth to c0:a0:bb:13:a9:fa (try 1/3)
[ 10.166982] wlan0: authenticated
[ 10.169284] wlan0: associate with c0:a0:bb:13:a9:fa (try 1/3)
[ 10.176401] wlan0: RX AssocResp from c0:a0:bb:13:a9:fa (capab=0xc11 status=0 aid=4)
[ 10.177185] wlan0: associated
[ 10.177207] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 10.178740] cfg80211: Regulatory domain changed to country: US
[ 10.178743] cfg80211: DFS Master region: unset
[ 10.178744] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 10.178745] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm), (N/A)
[ 10.178747] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm), (N/A)
[ 10.178747] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (0 s)
[ 10.178748] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (0 s)
[ 10.178749] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (0 s)
[ 10.178750] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm), (N/A)
[ 10.178751] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)

And here a filtered syslog of the 4.2.0 kernel test:

kernel: [ 5.950999] Bluetooth: Core ver 2.20
kernel: [ 5.951011] NET: Registered protocol family 31
kernel: [ 5.951012] Bluetooth: HCI device and connection manager initialized
kernel: [ 5.951015] Bluetooth: HCI socket layer initialized
kernel: [ 5.951018] Bluetooth: L2CAP socket layer initialized
kernel: [ 5.951022] Bluetooth: SCO socket layer initialized
kernel: [ 5.972903] Intel(R) Wireless WiFi driver for Linux
kernel: [ 5.972906] Copyright(c) 2003- 2015 Intel Corporation
kernel: [ 5.981224] iwlwifi 0000:06:00.0: Direct firmware load for iwlwifi-7260-15.ucode failed with error -2
kernel: [ 5.981390] AVX2 version of gcm_enc/dec engaged.
kernel: [ 5.981391] AES CTR mode by8 optimization enabled
kernel: [ 5.986901] iwlwifi 0000:06:00.0: loaded firmware version 25.30.14.0 op_mode iwlmvm
kernel: [ 6.006817] iwlwifi 0000:06:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144
kernel: [ 6.006869] iwlwifi 0000:06:00.0: L1 Disabled - LTR Disabled
kernel: [ 6.007094] iwlwifi 0000:06:00.0: L1 Disabled - LTR Disabled
kernel: [ 6.057082] intel_rapl: Found RAPL domain package
kernel: [ 6.057085] intel_rapl: Found RAPL domain core
kernel: [ 6.057087] intel_rapl: Found RAPL domain uncore
kernel: [ 6.057089] intel_rapl: Found RAPL domain dram
kernel: [ 6.073295] cfg80211: World regulatory domain updated:
kernel: [ 6.073305] cfg80211: DFS Master region: unset
kernel: [ 6.073306] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
kernel: [ 6.073308] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
kernel: [ 6.073310] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
kernel: [ 6.073311] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
kernel: [ 6.073313] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
kernel: [ 6.073314] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
kernel: [ 6.094413] init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE
kernel: [ 6.244175] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
kernel: [ 6.268966] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
kernel: [ 6.268968] Bluetooth: BNEP filters: protocol multicast
kernel: [ 6.268972] Bluetooth: BNEP socket layer initialized
kernel: [ 6.298862] Bluetooth: RFCOMM TTY layer initialized
kernel: [ 6.298867] Bluetooth: RFCOMM socket layer initialized
kernel: [ 6.298871] Bluetooth: RFCOMM ver 1.11
avahi-daemon[1395]: Network interface enumeration completed.
avahi-daemon[1395]: Registering HINFO record with values 'X86_64'/'LINUX'.
NetworkManager[1381]: <info> monitoring kernel firmware directory '/lib/firmware'.
NetworkManager[1381]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:06:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
NetworkManager[1381]: <info> WiFi enabled by radio killswitch; enabled by state file
NetworkManager[1381]: <info> WWAN enabled by radio killswitch; enabled by state file
NetworkManager[1381]: <info> WiMAX enabled by radio killswitch; enabled by state file
NetworkManager[1381]: <info> Networking is enabled by state file
NetworkManager[1381]: <warn> failed to allocate link cache: (-12) Object not found
NetworkManager[1381]: <info> (eth0): carrier is OFF
NetworkManager[1381]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
NetworkManager[1381]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
NetworkManager[1381]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
NetworkManager[1381]: <info> (eth0): bringing up device.
ntpdate[1749]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
ntpdate[1749]: no servers can be used, exiting
NetworkManager[1381]: <info> (eth0): preparing device.
NetworkManager[1381]: <info> (eth0): deactivating device (reason 'managed') [2]
NetworkManager[1381]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:1c.2/0000:05:00.2/net/eth0
kernel: [ 6.680688] r8169 0000:05:00.2 eth0: link down
kernel: [ 6.680722] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
NetworkManager[1381]: <info> (wlan0): using nl80211 for WiFi device control
NetworkManager[1381]: <info> (wlan0): driver supports Access Point (AP) mode
NetworkManager[1381]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 3)
NetworkManager[1381]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
NetworkManager[1381]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
NetworkManager[1381]: <info> (wlan0): bringing up device.
kernel: [ 6.682888] iwlwifi 0000:06:00.0: L1 Disabled - LTR Disabled
kernel: [ 6.683113] iwlwifi 0000:06:00.0: L1 Disabled - LTR Disabled
kernel: [ 6.902341] iwlwifi 0000:06:00.0: L1 Disabled - LTR Disabled
kernel: [ 6.902590] iwlwifi 0000:06:00.0: L1 Disabled - LTR Disabled
NetworkManager[1381]: <info> (wlan0): preparing device.
NetworkManager[1381]: <info> (wlan0): deactivating device (reason 'managed') [2]
dbus[1211]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper)
NetworkManager[1381]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
NetworkManager[1381]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
NetworkManager[1381]: <info> urfkill disappeared from the bus
kernel: [ 6.915412] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
NetworkManager[1381]: <info> ModemManager available in the bus
dbus[1211]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
NetworkManager[1381]: <info> wpa_supplicant started
wpa_supplicant[2331]: Successfully initialized wpa_supplicant
acpid: starting up with netlink and the input layer
acpid: 9 rules loaded
acpid: waiting for events: event logging is off
NetworkManager[1381]: <info> (wlan0) supports 5 scan SSIDs
NetworkManager[1381]: <warn> Trying to remove a non-existant call id.
NetworkManager[1381]: <info> (wlan0): supplicant interface state: starting -> ready
NetworkManager[1381]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
NetworkManager[1381]: <info> (wlan0): supplicant interface state: ready -> disconnected
NetworkManager[1381]: <info> (wlan0) supports 5 scan SSIDs
wpa_supplicant[2352]: wlan0: Reject scan trigger since one is already pending
wpa_supplicant[2352]: wlan0: CTRL-EVENT-SCAN-STARTED
kernel: [ 7.970104] Bluetooth: hci0 command 0x0c03 tx timeout
ModemManager[1279]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.2/0000:05:00.2': not supported by any plugin
ModemManager[1279]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.3/0000:06:00.0': not supported by any plugin
NetworkManager[1381]: <info> Auto-activating connection 'Auto dlink-ap'.
NetworkManager[1381]: <info> Activation (wlan0) starting connection 'Auto dlink-ap'
NetworkManager[1381]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[1381]: <info> NetworkManager state is now CONNECTING
NetworkManager[1381]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[1381]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[1381]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[1381]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[1381]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[1381]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[1381]: <info> Activation (wlan0/wireless): connection 'Auto dlink-ap' has security, and secrets exist. No new secrets needed.
NetworkManager[1381]: <info> Config: added 'ssid' value 'dlink-ap'
NetworkManager[1381]: <info> Config: added 'scan_ssid' value '1'
NetworkManager[1381]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
NetworkManager[1381]: <info> Config: added 'psk' value '<omitted>'
NetworkManager[1381]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[1381]: <info> Config: set interface ap_scan to 1
NetworkManager[1381]: <info> (wlan0): supplicant interface state: disconnected -> inactive
wpa_supplicant[2352]: wlan0: SME: Trying to authenticate with c0:a0:bb:14:aa:32 (SSID='dlink-ap' freq=2412 MHz)
kernel: [ 10.356555] wlan0: authenticate with c0:a0:bb:14:aa:32
wpa_supplicant[2352]: wlan0: Trying to associate with c0:a0:bb:14:aa:32 (SSID='dlink-ap' freq=2412 MHz)
NetworkManager[1381]: <info> (wlan0): supplicant interface state: inactive -> associating
kernel: [ 10.359375] wlan0: send auth to c0:a0:bb:14:aa:32 (try 1/3)
kernel: [ 10.361139] wlan0: authenticated
kernel: [ 10.362657] wlan0: associate with c0:a0:bb:14:aa:32 (try 1/3)
wpa_supplicant[2352]: wlan0: Associated with c0:a0:bb:14:aa:32
kernel: [ 10.366885] wlan0: RX AssocResp from c0:a0:bb:14:aa:32 (capab=0xc11 status=0 aid=4)
kernel: [ 10.368950] wlan0: associated
kernel: [ 10.368974] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
kernel: [ 10.370544] cfg80211: Regulatory domain changed to country: US
kernel: [ 10.370547] cfg80211: DFS Master region: unset
kernel: [ 10.370548] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
kernel: [ 10.370549] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm), (N/A)
kernel: [ 10.370551] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm), (N/A)
kernel: [ 10.370552] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (0 s)
kernel: [ 10.370553] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (0 s)
kernel: [ 10.370554] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (0 s)
kernel: [ 10.370555] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm), (N/A)
kernel: [ 10.370556] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
NetworkManager[1381]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
wpa_supplicant[2352]: wlan0: WPA: Key negotiation completed with c0:a0:bb:14:aa:32 [PTK=CCMP GTK=TKIP]
wpa_supplicant[2352]: wlan0: CTRL-EVENT-CONNECTED - Connection to c0:a0:bb:14:aa:32 completed [id=0 id_str=]
NetworkManager[1381]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
NetworkManager[1381]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'dlink-ap'.
NetworkManager[1381]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
NetworkManager[1381]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
NetworkManager[1381]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
NetworkManager[1381]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
NetworkManager[1381]: <info> dhclient started with pid 2481
NetworkManager[1381]: <info> Activation (wlan0) Beginning IP6 addrconf.
NetworkManager[1381]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
dhclient: Internet Systems Consortium DHCP Client 4.2.4
NetworkManager[1381]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
dhclient: Listening on LPF/wlan0/48:51:b7:18:45:34
dhclient: Sending on LPF/wlan0/48:51:b7:18:45:34
dhclient: Sending on Socket/fallback
dhclient: DHCPREQUEST of 192.168.0.112 on wlan0 to 255.255.255.255 port 67 (xid=0x243b622e)
kernel: [ 10.989573] init: plymouth-stop pre-start process (2484) terminated with status 1
avahi-daemon[1395]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::4a51:b7ff:fe15:78b3.
avahi-daemon[1395]: New relevant interface wlan0.IPv6 for mDNS.
avahi-daemon[1395]: Registering new address record for fe80::4a51:b7ff:fe15:78b3 on wlan0.*.
dhclient: DHCPREQUEST of 192.168.0.112 on wlan0 to 255.255.255.255 port 67 (xid=0x243b622e)
dhclient: DHCPACK of 192.168.0.112 from 192.168.0.1
dhclient: bound to 192.168.0.112 -- renewal in 230966 seconds.
NetworkManager[1381]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
NetworkManager[1381]: <info> address 192.168.0.112
NetworkManager[1381]: <info> prefix 24 (255.255.255.0)
NetworkManager[1381]: <info> gateway 192.168.0.1
NetworkManager[1381]: <info> nameserver '192.168.0.1'
NetworkManager[1381]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
NetworkManager[1381]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
avahi-daemon[1395]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.112.
avahi-daemon[1395]: New relevant interface wlan0.IPv4 for mDNS.
avahi-daemon[1395]: Registering new address record for 192.168.0.112 on wlan0.IPv4.
NetworkManager[1381]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
NetworkManager[1381]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
NetworkManager[1381]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
NetworkManager[1381]: <info> NetworkManager state is now CONNECTED_GLOBAL
NetworkManager[1381]: <info> Policy set 'Auto dlink-ap' (wlan0) as default for IPv4 routing and DNS.
NetworkManager[1381]: <info> DNS: starting dnsmasq...
NetworkManager[1381]: <warn> dnsmasq not available on the bus, can't update servers.
NetworkManager[1381]: <error> [1442802760.34388] [nm-dns-dnsmasq.c:396] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
NetworkManager[1381]: <warn> DNS: plugin dnsmasq update failed
NetworkManager[1381]: <info> Writing DNS information to /sbin/resolvconf
dnsmasq[3009]: started, version 2.68 cache disabled
dnsmasq[3009]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth
dnsmasq[3009]: DBus support enabled: connected to system bus
dnsmasq[3009]: warning: no upstream servers configured
kernel: [ 15.967945] Bluetooth: hci0 sending initial HCI reset command failed (-110)
NetworkManager[1381]: <info> Activation (wlan0) successful, device activated.
dbus[1211]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
NetworkManager[1381]: <info> WiFi hardware radio set enabled
NetworkManager[1381]: <warn> dnsmasq appeared on DBus: :1.39
NetworkManager[1381]: <info> Writing DNS information to /sbin/resolvconf
dnsmasq[3009]: setting upstream servers from DBus
dnsmasq[3009]: using nameserver 192.168.0.1#53
NetworkManager[1381]: <info> (wlan0): IP6 addrconf timed out or failed.
NetworkManager[1381]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
wpa_supplicant[2352]: wlan0: CTRL-EVENT-SCAN-STARTED
NetworkManager[1381]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
NetworkManager[1381]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
ntpdate[3151]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
ntpdate[3151]: no servers can be used, exiting
---
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ah 2756 F.... pulseaudio
 /dev/snd/controlC0: ah 2756 F.... pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-12-27 (269 days ago)
InstallationMedia: Linux Mint 17.1 "Rebecca" - Release amd64 20141126
MachineType: Notebook P15SM-A/SM1-A
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic root=UUID=12f37da9-2e20-4fc0-b02b-3f1c4b171e7f ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-38-generic N/A
 linux-backports-modules-3.16.0-38-generic N/A
 linux-firmware 1.127.15
Tags: rafaela
Uname: Linux 3.16.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/14/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: P15SM-A/SM1-A
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/14/2014:svnNotebook:pnP15SM-A/SM1-A:pvrNotApplicable:rvnNotebook:rnP15SM-A/SM1-A:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: P15SM-A/SM1-A
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

Revision history for this message
Seth Forshee (sforshee) wrote :

Switching this to affect linux instead of linux-firmware since right now we're not sure that it's a firmware problem.

Please run 'apport-collect 1497825' to attach hardware information and logs to this bug, preferably after you've been experiencing wireless problems. This will only work when you're running an official Ubuntu kernel.

The 4.2 kernel should support firmware versions up to -15, so please go ahead and give this a try as well and let us know whether or not it makes a difference.

Thanks!

affects: linux-firmware (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
André Heynatz (ombatar) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected rafaela
description: updated
Revision history for this message
André Heynatz (ombatar) wrote : BootDmesg.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : CRDA.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : CurrentDmesg.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : IwConfig.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : Lspci.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : Lsusb.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : ProcEnviron.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : ProcInterrupts.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : ProcModules.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : PulseList.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : RfKill.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : UdevDb.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : UdevLog.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote : WifiSyslog.txt

apport information

Revision history for this message
André Heynatz (ombatar) wrote :

I am offline with the dlink connection, and apport-collect requires the system to be online. I tried to separate the collection process from the reporting process like this:

apport-cli --save bug-1497825-crashfile linux
apport-cli -u 1497825 -c bug-1497825-crashfile

But apport-cli -u does not permit a crashfile to be used. And the crashfile is rather small. So I used

apport-collect 1497825

with my *working connection over my Android 4.4.2 phone*. I have seen that the report created by apport-collect is much larger (1.2 MB).

If you tell me how can I send a proper apport-collect report with an offline system, I will do it.

Revision history for this message
Seth Forshee (sforshee) wrote :

The logs include some associations with the dlink AP, so I think we're good for now. Did you get a chance to test 4.2 with the -15 firmware?

Revision history for this message
André Heynatz (ombatar) wrote :

Unfortunately, -15 firmware does not work either.

Revision history for this message
André Heynatz (ombatar) wrote :

The notebook is a Schenker P504 (based on Clevo P157SM-A). I did a BIOS update in December 2014, and because it is an old chassis from 2012, I have not cared for more BIOS updates since then.

What I did this evening, was another BIOS update, and surprisingly, now I am online with the Linux system.

BIOS Update for Schenker P504 (based on Clevo P157SM-A):

EC 1.03.07 -> 1.05.01 (ECFlash.bat)
ME 9.1.0.1120 -> 9.1.30.1008
BIOS 1.03.08 -> 1.05.01a (flashme.bat, calls FLASH.BAT automatically after updating ME)

I have tested this BIOS/ME/EC version with kernel 4.2.0, 3.16.7, and 3.13.11: success with all kernels.

The Windows 7 64 Bit driver has had disconnects (old BIOS version, left side). I have updated it with Wireless_18.20.0_ s64.exe.

I assume the Windows driver is more tolerant to BIOS faults.

Revision history for this message
André Heynatz (ombatar) wrote :

syslog for kernel 4.2.0
ntpdate is successful in last try

Revision history for this message
André Heynatz (ombatar) wrote :

syslog for kernel 3.16.7
ntpdate is successful in last try

Revision history for this message
André Heynatz (ombatar) wrote :

syslog for kernel 3.13.11
ntpdate is successful in last try

Revision history for this message
André Heynatz (ombatar) wrote :

After a while, I got disconnected. Stopping and starting the WiFi connection has not helped. The signal strength still is quite a bit lower on Linux (64% with 4.2.0/-15) than on Windows (100% with 18.20.0_s64).

Revision history for this message
André Heynatz (ombatar) wrote :

This time I could not transfer data again, even with a lot of patience (4.2.0/-15). The signal strength was 57-60%. The Windows driver on the same system reaches over the same AP 100% and the connection is very good. So I was very lucky yesterday.

Seth Forshee (sforshee)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Seth Forshee (sforshee) wrote :

I don't see any clues in the logs as to what the problem might be.

As for the regulatory domain, the transmit power limit in the 2.4 GHz range is higher for the US rule than for EC's, so that might help explain the difference there. It looks like the router must be broadcasting its location as being in the US.

I have a script you can try to collect more detailed information at http://people.canonical.com/~sforshee/wifi-debug. To use it:

 1. Download the file.
 2. Run 'sudo bash wifi-debug -t' (it may prompt you to install extra packages).
 3. Connect to the wireless network and verify you're experiencing connection problems.
 4. Press Ctrl-C to terminate the script, and it will generate a wifi-debug-files.tar.gz file in the current directory.

wifi-debug-files.tar.gz might contain private information about your wireless network, so I recommend you don't attach it to the bug. You can email me the file or use some other mechanism if you wish. I'd also like your permission to share this information with engineers at Intel.

Thanks!

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
André Heynatz (ombatar) wrote :

The model of the router is a Dlink DIR 610N+. A TV cable provider has installed it, so I cannot view the configuration and tell more about it.

Revision history for this message
Seth Forshee (sforshee) wrote :

andrehe: Based on your comments over email that you haven't been having problems recently, I'm going to mark this bug as fixed. If the problems return feel free to reopen this bug.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.