[Kernel-packages] [Bug 1214852] Re: encrypted drive can't boot

2013-08-23 Thread Martin Stut
I could not install the test kernel from http://people.canonical.com/~henrix/lp1215155/ - Software Center complains wrong architecture amd64. I am in fact running i386, to be able to boot a small netbook from the external hard drive. The kernel in proposed (aptitude got me 3.8.0-30.44) works

[Kernel-packages] [Bug 1214852] Re: encrypted drive can't boot

2013-08-23 Thread Joseph Salisbury
** Changed in: linux (Ubuntu) Status: Incomplete = Fix Committed -- 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/1214852 Title: encrypted drive can't boot Status in “linux”

[Kernel-packages] [Bug 1214852] Re: encrypted drive can't boot

2013-08-22 Thread Joseph Salisbury
Also, the 3.8.0-30.43 kernel is now available in the -proposed repository. Would it be possible for you to test this latest kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Kernel-packages] [Bug 1214852] Re: encrypted drive can't boot

2013-08-22 Thread Joseph Salisbury
This may be a duplicate of bug #1215155. Before testing the kernels in comments #3 and #4, can you test the kernel that was built for bug 1215155? You can download the test kernel here: http://people.canonical.com/~henrix/lp1215155/ Thanks. -- You received this bug notification because you

[Kernel-packages] [Bug 1214852] Re: encrypted drive can't boot

2013-08-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- 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/1214852 Title: encrypted drive can't boot Status in “linux” package

[Kernel-packages] [Bug 1214852] Re: encrypted drive can't boot

2013-08-22 Thread Joseph Salisbury
I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue. Can you test the following kernels and post back? We are looking for the first kernel