The proper fix seems to be to add 'copy_modules_dir kernel/ubuntu/i915'
to /usr/share/initramfs-tools/hooks/framebuffer, then run 'update-
initramfs -k all -u'. Could you try that and boot stock -31 kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which
(for the record, Skylake and Braswell are affected too, they all use
i915_bpo backport module which isn't included in the vivid initramfs)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Timo's suggestion in comment 54 resolves the issue with default ubuntu
kernel:
linux-image-3.19.0-30-generic 3.19.0-30.34
linux-image-extra-3.19.0-30-generic 3.19.0-30.34
I applied the following change:
--- /usr/share/initramfs-tools/hooks/framebuffer.orig 2015-10-20
** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu)
** Changed in: initramfs-tools (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I can confirm that Timo's solution actually works!
--
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/1500751
Title:
Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
Status in
I can also confirm that 3.19.0-31.36~RevertsV2 works, it resolves the
issue on a Dell XPS13 2015.
I noticed that the issue isn't resolved if I only install the linux-
image package, it is only when I also install linux-image-
extra-3.19.0-31-generic_3.19.0-31.36~RevertsV2 the issue is resolved. I
I can confirm that 3.19.0-31-generic #36~RevertsV2 works without any of
the issues.
@rolfinator (seb2): Yes I have the same issues with the 3.19.0-30 kernel
stated in the initial post (plus some random system freezes, except the
workaround "boot -> wait for dm-crypt passphrase, which can't be
I created a V2 test kernel since reverting only 0ed67cf and 53dfa1d
still exhibits the bug. The V2 test kernel has the following four
commits reverted:
86ad82b UBUNTU: SAUCE: i915_bpo: drm/i915: Split atomic wm update to pre and
post variants
059c4a4 UBUNTU: SAUCE: Migrate Broadwell to
V2 works for me. Confirmed V1 exhibits the bug.
--
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/1500751
Title:
Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
Status in cryptsetup
I can also confirm 3.19.0-31-generic V2 works without any dmesg bloat.
--
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/1500751
Title:
Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
The kernel from comment #46 didn't resolves the bug. The issue remains
and even the reboot-workaround don't do the trick. When I disable splash
then I can enter the passphrase, but afterwards the boot hangs with the
kernel-log repeatedly stating
[drm:gen8_irq_handler [i915_bpo]] *ERROR* The
@Morten Clausen (morten-c):
Same here. But just a question:
Did you have the same issues with the initial kernel I stated in the bug report
here?
Ever since I updated to 3.19.0-30, the boot as well as shutdown messages are
full of
[16925.079865] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The
I built the next test kernel, up to the following commit:
90dcba7eec2702302f06308e5140458cf840fa3b
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1500751
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
The bisect reported 0ed67cf18 as the first bad commit. However, this
also requires that I revert commit 53dfa1d. I built a Vivid test kernel
with a revert of these commits. Can folks affected by this bug see if
this test kernel resolves this bug and/or if it introduces any new
issues?
The test
Works for me on:
Linux calcium 3.19.0-29-generic #31~lp1500751Commit90dcba7ee SMP Fri Oct
9 14:19:00 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I can confirm comment #44.
Running 3.19.0-29-generic #31~lp1500751Commit90dcba7ee works fine for me
on Thinkpad T450s.
--
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/1500751
Title:
Any news about this at all, or any idea when the fix is going to be
pushed in the repository ? It's very frustrating that we can't input the
password on all our machines, or we have to use workarounds ..
--
You received this bug notification because you are a member of Kernel
Packages, which is
I have had the same problems on my machine.
For me kernel 3.19.8-031908ckt7-generic works and fixes the issue (as
proposed by Guy Taylor).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have just marked my issue as a duplicate of this
(https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1504763).
A summary of my findings:
* Using kernel 3.19.0.28 works with graphical plymouth
* Using kernel 3.19.0.31 does not work with graphical plymouth
* Using kernel 3.19.0.31 does work
I've tested linux-image-3.19.0-29-generic version
3.19.0-29.31~lp1500751Commit0ed67cf1 and it has the bug too.
--
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/1500751
Title:
Cryptsetup
Just to let you know I'm still on Ubuntu Kernel version: 3.19.0-30-generic and
I'm experiencing this issue. However removing quiet splash from grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
allows me to boot to this Kernel version. The text version of the splash screen
asking for password is
Yes Peter. Please take a look at
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/comments/5
--
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/1500751
Title:
Cryptsetup
Tested linux-image-3.19.0-29-generic version
3.19.0-29.31~lp1500751Commita036f6b1 and it still has the bug.
--
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/1500751
Title:
Cryptsetup
I built the next test kernel, up to the following commit:
0ed67cf18a94983cea82a011df3c4f9f8314796b
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1500751
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
Same issue with the kernel aforementioned (3.19.0-30-generic) on Ubuntu
GNOME 15.04.
Oddly booting with that kernel in recovery mode gets the keyboard to
work (tried to fix dpkg from there but it can't download package,
although it seemed there was one package missing).
Blindly entering the
Tested linux-image-3.19.0-29-generic version
3.19.0-29.31~lp1500751Commit884feaefc and it also/still has the bug.
BTW, the latest release kernel, version 3.19.0-30.34, which showed up
with regular updates on my laptop today, also has the bug.
--
You received this bug notification because you
I built the next test kernel, up to the following commit:
a036f6b179825b14ea0f8cd2e6333f8689930c6e
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1500751
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
I am able to enter my passphrase (asterisks appear, boot continues on
"enter") on 3.19.0-29-generic #31~lp1500751Commit4b630e4e on my Dell
Latitude E7250.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I built the next test kernel, up to the following commit:
884feaefcd5a4b2a8ef10436f74077cef1330f6b
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1500751
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
This might not be a problem with the kernel, rather with grub. I assume
it's grub setting up the splash screen GUI, not the kernel.
Just a thought.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I built the next test kernel, up to the following commit:
4b630e4e471c138161ab053471d97b0cdd367a31
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1500751
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
** Description changed:
I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
- After upgrading the boot time is longer (what is negligible) but the more
sever error is, that I cannot enter my passphrase when I see the crypt dialog.
+ After upgrading the boot time is
The Acer Aspire E5-571-53S1 (E 15) is also affected.
--
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/1500751
Title:
Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
Status in
With 3.19.0-30, I am able to enter the passphrase if and only if I
remove "splash" from the kernel command line arguments when booting.
3.19.0-28 works normally.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm confirming rp's experenence in comment 19: The bisected linux-
image-3.19.0-29-generic version 3.19.0-29.31~lp1500751Commit2286f1ed
still contains the bug, using that kernel I cannot enter the
passsphrase.
Joseph, thank's for the deb:s of bisect builds! Let's try another one.
:)
BTW, as
I built the next test kernel, up to the following commit:
50031c9d633345cd2d5353fcd1ef954a0766026c
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1500751
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
Tested version 3.19.0-29.31~lp1500751Commit50031c9d and it also/still
has the bug.
This time it was slightly different compared to how I recall it from the
original case. I still cannot enter text in the cryptsetup area, but rather
than emitting the password at the upper left corner of the same
You can add one more XPS 13 to the list of affected systems. I'm about
to EOD but can also test additional kernels starting on Monday. All my
system info attached to duplicate LP Bug #1502171.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@Fredrik Jonson (fredrik-jonson):
Yes, in the original bug I reported, there was no input possible at all
--
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/1500751
Title:
Cryptsetup
@Fredrik Jonson (fredrik-jonson), @Sean Sosik-Hamor (sciri) :
In the original bad kernel, 3.19.0-30.33, if I typed many characters
(maybe 30) and some carriage returns. the text did show up as described
by @Fredrik Jonson (fredrik-jonson)
--
You received this bug notification because you are a
I started a kernel bisect between Ubuntu-3.19.0-28 and Ubuntu-3.19.0-30.
The kernel bisect will require testing of about 7 test kernels.
I built the first test kernel, up to the following commit:
2286f1ed6dab9794a72e7f246eafef7cfe637147
The test kernel can be downloaded from:
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
same thing, - no text accepted in the crypto-passphrase field with your
provided 3.19.0-29.31.
but i have to admit that i dont feel confident with my judgement.
perhaps somebody else should report as well just to be sure...
anyway - thanks.
--
You received this bug notification
Same Problem to me.
tried enabling vivid-proposed - but vivid-proposed does not offer a kernel
newer than 3.19.0-30.33
perhaps i missed something here...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug and bug 1501205 may be duplicates.
It sounds like this could be related to a SAUCE patch. 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
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-ckt5-vivid/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-ckt6-vivid/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-ckt7-vivid/
-> None of these kernels have the bug. Tested on Dell XPS 13
--
You received this bug
Same here on HP 820 G2. None of the kernels seem to have the issue.
If you follow my suggested solution from post #5, you won't have a graphical
interface, but a text console to enter the key.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Bug 1501497 is a duplicate of this one.
--
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/1500751
Title:
Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
Status in cryptsetup package
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided => Medium
--
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/1500751
Title:
Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
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/1500751
Title:
Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
Status in
With respect to my last comment, i meant kernel version 3.19.0-28 works.
--
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/1500751
Title:
Cryptsetup Keyboard not working on Xubuntu
You are probably right, Steve. Thanks for moving (however I tried to
find the right project/audience in the first place)
--
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/1500751
Title:
I have the same problem, too, on a Dell XPS 13 laptop. I had to go back
to the previous kerb version.
--
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/1500751
Title:
Cryptsetup Keyboard
I'd like to perform a bisect to figure out which commit introduced this
regression. It would be very helpful to know the last good kernel and
the first bad kernel.
Can you test the following kernels and report back? We are looking for
the earliest kernel version that doesn't have this bug:
If this problem is reproducible with the new kernel but not the old,
then this is evidently a kernel bug. Reassigning.
** Project changed: plymouth => linux (Ubuntu)
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
56 matches
Mail list logo
