govind, as this report is closed, it has nothing to do with your problem. If
you want your issue addressed, please file a new report via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
the problem got solved by inter changing configuration to various options
given in network edit . I change d to automatic to manual and then to local
links.. after opting to local links some local configuration appeared in
IPv4 section,, Here i changed /edited to my service provider's IP, net-mask
the problem ihave seen is in edit connection wi fi is showing IPv4
empty, even aftee editing it wifi is not connecting. though Ethernet
connects.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
This bug was fixed in the package linux - 3.19.0-20.20
---
linux (3.19.0-20.20) vivid; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1459957
* Revert SAUCE: Call i915_bpo specific functions from the hda driver
- LP: #1457369
linux (3.19.0-19.19) vivid;
** Changed in: system76
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
Intel 3160 wireless card no longer able to connect to wifi networks
Okay, after some more careful testing,
afcee962b09842d0f4191beb4a2d08251b4c7705 does indeed fix the problem.
I was having some unrelated issues when connecting to 2.4GHz N when too
far away from the access point (lots of WiFi interference here at
System76 HQ).
But the important thing is that
The proposed kernel worked for me with bluetooth on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
Intel 3160 wireless card no longer able to connect to wifi networks
To manage
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
I'm not sure what the relevant difference is, but I'm still having
trouble connecting to 2.4GHz N networks with an Intel 3160 when running
3.19.0-20-generic from proposed (when Bluetooth is turned on). In
particular, my 2.4GHz N SSID frequently isn't showing up in the list of
available access
Jason Gerard DeRose, it may be best for you to file a new report against
your hardware so whatever the delta is between your environment and
Michael Boratko (router, connecting PCI hardware, revision, etc.) is
identified, and addressed.
--
You received this bug notification because you are a
This bug was fixed in the package linux - 3.19.0-20.20
---
linux (3.19.0-20.20) vivid; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1459957
* Revert SAUCE: Call i915_bpo specific functions from the hda driver
- LP: #1457369
linux (3.19.0-19.19) vivid;
kernel 4.0.0 #1 SMP on a Gigabyte BXi7H-550. Behaviour is intermittent:
sometimes it connects fine, sometimes it won't connect but the networks
can be seen, sometimes the card is not visible to iwconfig.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
hi, I have the same issue however none of the above fixed it for me:
- kernel 4.1rc2 doesnt fix it
- booting with bluetooth of doesnt fix it either
it just says connecting and the goes back to disconnected state, exactly
as stated above.
I also have a Y50 with an Intel 3160. I also updated the
so at least I got that ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
Intel 3160 wireless card no longer able to connect to wifi networks
To manage notifications about this bug go
actually the only thing that does work is going back to kernel 3.16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
Intel 3160 wireless card no longer able to connect to wifi networks
I've the same problem and confirm that putting OFF the bluetooth and
restarting the PC the connection is OK ( even if manually I've choiced
it ).
thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@boratko - no problem, thanks for figuring out that it was related to
bluetooth being turned on!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
Intel 3160 wireless card no longer able
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
Intel 3160 wireless card no longer able to connect to wifi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Vivid)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+
Laptop: Lenovo Y70 Touch
Wireless Card: Intel Corporation Wireless 3160 (rev 93)
When running Ubuntu Gnome 14.10 (on a live USB drive) I am able to
connect to wifi
The full git ID for the commit which fixes this issue in the mainstream
kernel is:
16c426ff9e13a06d754ed7484f5e6e6d6550f968
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
Intel 3160
Mostly just confirming what @boratko already shared, plus perhaps a few
new details:
The ingredients needed to reproduce this bug on Vivid:
1) Intel 3160 WiFi card
2) Boot with bluetooth enabled (turn on in the bluetooth indicator and
reboot if needed)
3) Connect to a 2.4 GHz N router
In
** Also affects: system76
Importance: Undecided
Status: New
** Changed in: system76
Status: New = Triaged
** Changed in: system76
Assignee: (unassigned) = Jason Gerard DeRose (jderose)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: system76
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
Intel 3160 wireless card no longer able to connect to wifi networks
To
@jderose - Thanks for catching the error with my commit ID, yes that is
the commit I meant to refer to.
Also, I seem to be getting intermittent behavior still when connected to
a 5GHz wireless AC network. I haven't tested others, but even with the
bluetooth off I am getting random disconnects. I
Attaching the patch from:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=afcee962b09842d0f4191beb4a2d08251b4c7705
** Patch added: fix-1442411.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1442411/+attachment/4397772/+files/fix-1442411.patch
** Changed
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
Intel 3160 wireless card no longer able to connect to wifi networks
To manage notifications about this bug go to:
Okay, afcee962b09842d0f4191beb4a2d08251b4c7705 seems to fix this
problem:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=afcee962b09842d0f4191beb4a2d08251b4c7705
I cherry-picked it into the current ubuntu-vivid.git tree and built a
kernel, and have had no problems so
@boratko - what's the full git commit ID of the of the mainline commit
that fixes this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
Intel 3160 wireless card no longer able to
** Tags removed: needs-reverse-bisect
** Tags added: cherry-pick
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
** Description changed:
Laptop: Lenovo Y70 Touch
Wireless Card: Intel Corporation Wireless 3160 (rev 93)
When running Ubuntu Gnome 14.10 (on a live USB
I reverse bisected the upstream kernel, and determined that the fix is
in commit 16c426f. I also believe that this is (upstream) already set to
be merged into the 3.19 kernel (please let me know if that's not the
case).
Specifically, there is only one small change in this commit, which
adjusts
mexlinux, unfortunately WORKAROUNDs are not considered solutions. Also,
making folks dumpster dive through some link isn't terribly helpful
here.
Despite this, it will be most helpful if you filed a new report via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You
The solution indicated here:
http://askubuntu.com/questions/611222/cannot-connect-to-wifi-intel-corporation-wireless-3160
Makes it possible to connect to wifi, but after suspension it does not
work, restarting network services does not work. Restarting computer
does.
--
You received this bug
I am perplexed to report that, although I am able to reproduce the error
on 4.0, I am not able to reproduce it on 4.1. Furthermore, directly
after writing the above comment, I updated my Arch Linux install, and
now the wifi fails in a completely different way than described above,
so I really
Understood. It just seemed that if there was a bug in the upstream kernel
and (for instance) the Arch kernel team had found it, it would similarly be
reported back upstream, not to mention that Arch seems quite against making
upstream modifications.
In any event, I am in the process of reverse
Michael Boratko, please keep in mind that the Ubuntu kernel, Arch
kernel, and upstream/mainline kernel are all different from one another.
Despite this, the next step is to fully reverse commit bisect from
kernel 4.0-rc7 to 4.1-rc1 in order to identify the last bad commit,
followed immediately by
I understand what you're saying, however I'm confused as to why this
would work appropriately on other distributions with the newer (version
12) firmware. In particular, it works on Arch linux (mentioned above).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I think perhaps I'm using the wrong vocabulary, which is the cause of
confusion.
When I did the git bisect I tested each bisection point manually, so I
must have actually tested that commit at some point in the past
(otherwise I wouldn't have truly bisected). Checking the bisect log,
that commit
To be more specific, commit f47f46d7b09cf1d09e4b44b6cc4dd7d68a08028c
works, commit ab1304b986468e3ef698ec4e1cb1a3d4ba080811 does not.
Furthermore, checking out Ubuntu 3.19.0-13.13 and reverting commit
ab1304b986468e3ef698ec4e1cb1a3d4ba080811 (which requires making a minor
merge conflict
I thought that is exactly what git bisect does.
In any event, I manually created a new branch and compiled the kernel
one commit behind ab1304b986468e3ef698ec4e1cb1a3d4ba080811, and verified
that it does work on this commit.
--
You received this bug notification because you are a member of
Michael Boratko, if one does not confirm by testing to the results of a
git bisect, then no, it's not what a git bisect does.
However, given you tested one commit back, this contradicts your statement in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1442411/comments/22 :
The thing is,
First, I have to mention that after additional testing I found that the
ab1304b986468e3ef698ec4e1cb1a3d4ba080811 commit actually does work, but
for some unknown reason I have to turn off the wifi adapter and turn it
back on after the computer starts.
The commit after that
Michael Boratko, if this is reproducible with the latest mainline kernel
(4.0), then the issue you are reporting is an upstream one. Could you
please report this problem to the appropriate mailing list (linux-
wireless, ilw, iwlwifi maintainer, CC the regression committer and those
who signed off
Michael Boratko, it wouldn't hurt to confirm your results by testing one
commit prior to this.
** Tags added: bisect-done
** Tags removed: bisect-done
** Tags added: needs-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I figured out how to do a kernel bisection manually, and isolated the
first bad commit to this one:
ab1304b986468e3ef698ec4e1cb1a3d4ba080811 is the first bad commit
commit ab1304b986468e3ef698ec4e1cb1a3d4ba080811
Author: Marcel Holtmann mar...@holtmann.org
Date: Mon Aug 11 22:11:35 2014 +0200
The asterisk mentioned above (for kernel 3.16.0-28.38) should be
disregarded - the behavior was present for a few tests, but I have
repeatedly tested it at this point and I think it was just typical wifi
wonkyness rather than the indication of a problem. Therefore,
3.16.0-28.38 should be regarded
I cloned the git repo for the Ubuntu kernel and I built a number of test
kernels. It seems like the problem starts in 3.18.0-1.1, here are the
kernels tested:
Good
3.16.0-23.31
3.16.0-24.32
3.16.0-25.33
3.16.0-28.38 *
Bad
3.18.0-1.1
3.18.0-7.8
3.19.0-1.1
3.19.0-10.10
3.19.0-12.12
3.19.0-13.13
*
Michael Boratko, could you please boot into a Utopic kernel
https://launchpad.net/ubuntu/+source/linux/3.16.0-23.31 in your current
install and advise to the results following
https://wiki.ubuntu.com/Kernel/KernelBisection ?
** Tags added: latest-bios-2.01 regression-release
** Tags added:
apport information
** Tags added: apport-collected vivid
** Description changed:
Laptop: Lenovo Y70 Touch
Wireless Card: Intel Corporation Wireless 3160 (rev 93)
When running Ubuntu Gnome 14.10 (on a live USB drive) I am able to
connect to wifi networks without any issue. When
The above logs are from apport on Ubuntu Vivid running the 3.19 kernel
(fully updated at time of posting).
I also updated to newest version of kernel (4.0.0-04rc7-generic) as
you requested, and the problem persists as before. Do you want more
apport logs from the new kernel as well?
**
The wireless card also works in Arch Linux using this kernel:
Linux LenovoY70 3.19.3-3-ARCH #1 SMP PREEMPT Wed Apr 8 14:10:00 CEST
2015 x86_64 GNU/Linux
I've attached the wifi script output from Arch to this
** Attachment added: Wifi Script run on Arch
51 matches
Mail list logo
