[Kernel-packages] [Bug 1024491] Re: Centrino Advanced-N 6205 wifi doesn't resume (hard blocked)

2013-12-07 Thread Matt Zimmerman
It's been two weeks since I upgraded my BIOS to 1.39, and the problem has not recurred. If it happens again I will reopen. Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1024491] Re: Centrino Advanced-N 6205 wifi doesn't resume (hard blocked)

2013-11-18 Thread Christopher M. Penalver
Matt Zimmerman, as per http://download.lenovo.com/express/ddfm.html an update is available for your BIOS (1.38). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything? If not, could you please both specify what happened, and provide the output of

[Kernel-packages] [Bug 1024491] Re: Centrino Advanced-N 6205 wifi doesn't resume (hard blocked)

2013-11-18 Thread Matt Zimmerman
Indeed, there have been a lot of updates. I will update the BIOS and report back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1024491 Title: Centrino Advanced-N 6205 wifi doesn't

[Kernel-packages] [Bug 1024491] Re: Centrino Advanced-N 6205 wifi doesn't resume (hard blocked)

2013-07-23 Thread Matt Zimmerman
The system in question uses encrypted home with ecryptfs. I'll collect the info you requested the next time it happens. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1024491

[Kernel-packages] [Bug 1024491] Re: Centrino Advanced-N 6205 wifi doesn't resume (hard blocked)

2013-07-21 Thread Matt Zimmerman
This is still the original one. Interestingly though, I now also have a different laptop at work which has the same wifi chip but is an entirely different model of laptop (ThinkPad X1 Carbon). It does not seem to exhibit this problem. So I suspect it has to do with the RF kill switch or the