Intel Wifi 3160 connects to AP but no internet access with 802.11n 2.4Ghz

[Jonathan Boler]

I have a Lenovo Y50-70 with Intel Wifi 3160

I can associate and authenticate with my wifi router but I have been unable to send/receive data using 802.11n 2.4Ghz on Ubuntu 14.04.2. Trying to ping the router IP address just times out.

I guessed this might be fixed in the latest version of Ubuntu so I installed the daily build of 15.10 from http://cdimage.ubuntu.com/daily-live/current/ dated June 3rd but got the same results.

I can access the internet using the 5Ghz band but the range is not as good as 2.4Ghz so I get very low speeds at the top of my house.

All my other laptops & phones can connect at 2.4Ghz at 70-150Mbit with no problems at the top of my house. I've tested with iPhones, Nexus 5, Moto X, Lenovo Thinkpads and Macbooks.

I've also tested Ubuntu 14.04.2 with Kernel 4.1 and iwlwifi firmware version 13 with the same results and I've tested this using the 15.04 live cd with the same results.

I've tried rfkill block bluetooth to turn off bluetooth.

I have attached a file with all the necessary debug info from Ubuntu 15.10 daily fresh installation.

The only output from dmesg after trying 2.4Ghz is as follows:

[ 369.179441] cfg80211: Calling CRDA to update world regulatory domain
[ 369.182145] cfg80211: World regulatory domain updated:
[ 369.182149] cfg80211: DFS Master region: unset
[ 369.182150] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 369.182153] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 369.182155] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 369.182156] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 369.182158] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 369.182159] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 380.579257] wlan1: authenticate with f8:8f:ca:41:e3:bc
[ 380.582170] wlan1: send auth to f8:8f:ca:41:e3:bc (try 1/3)
[ 380.603705] wlan1: authenticated
[ 380.604603] wlan1: associate with f8:8f:ca:41:e3:bc (try 1/3)
[ 380.644131] wlan1: RX AssocResp from f8:8f:ca:41:e3:bc (capab=0x411 status=0 aid=8)
[ 380.644699] wlan1: associated
---
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: tenpin 1402 F.... pulseaudio
 /dev/snd/controlC0: tenpin 1402 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.10
InstallationDate: Installed on 2015-07-01 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150603)
MachineType: LENOVO 20378
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=5dc092a3-4bc5-475f-b070-73857a6a9790 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-20-generic N/A
 linux-backports-modules-3.19.0-20-generic N/A
 linux-firmware 1.144
Tags: wily
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/12/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 9ECN36WW(V2.00)
dmi.board.asset.tag: 31900058WIN
dmi.board.name: Lenovo Y50-70
dmi.board.vendor: LENOVO
dmi.board.version: 31900058WIN
dmi.chassis.asset.tag: 31900058WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Y50-70
dmi.modalias: dmi:bvnLENOVO:bvr9ECN36WW(V2.00):bd01/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY50-70:
dmi.product.name: 20378
dmi.product.version: Lenovo Y50-70
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1470647

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Jonathan Boler (galatians)]

apport information

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[penalvch (penalvch)]

Jonathan Boler, as per http://support.lenovo.com/us/en/products/laptops-and-netbooks/lenovo-y-series-laptops/y50-70-notebook-lenovo an update to your computer's buggy and outdated BIOS is available (2.02). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]