Public bug reported:
Description:
- my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of
booting, after grub)
- does not even show the enter cryptsetup passphrase
- affected kernels:
# apt list --installed |grep linux-signed
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64
[installed]
linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70
amd64 [installed]
linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now
5.0.0.15.71 amd64 [installed]
- the setup is not new, has been working perfectly before (about 7 days
since my last restart?)
System:
- HW: ASUS Zenbook 14 UX433FN
- Ubuntu 18.04, runing latest HWE, fully updated
- grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),
Suspected/possible cause?:
- recent intel-microcode package update
- recent kernel package updates
Steps taken:
- tried to remove "splash quiet" from grub/kernel cmd line (also tried adding
nosplash, noplymouth)
- completely removed nvidia drivers (apt purge *nvidia*)
- completely purged and reinstalled grub (grup-pc)
- completely purged and reinstalled all kernels (headers, modules, image, ..)
- toggle BIOS "fastboot" (now using OFF)
- toggle UEFI SecureBoot (now using ON)
- remove plymoyth (apt remove *plymouth* , but the workaround is working with
plymouth installed)
Workaround:
- so far, I'm only able to boot with non-Ubuntu kernel!
(linux-image-liquorix-amd64)
- which needs "splash" option ON
I am not sure how to get you more debug info, as this setup has been
working before, and it's a very eary boot-process bug, so I can't even
access dmesg etc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-hwe-edge (Ubuntu)
Importance: Undecided
Status: New
** Tags: cryptsetup kernel-bug plymouth splash
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-hwe-edge (Ubuntu)
Importance: Undecided
Status: New
--
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/1829620
Title:
cryptsetup stuck at loading initramfs
Status in linux package in Ubuntu:
New
Status in linux-hwe package in Ubuntu:
New
Status in linux-hwe-edge package in Ubuntu:
New
Bug description:
Description:
- my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of
booting, after grub)
- does not even show the enter cryptsetup passphrase
- affected kernels:
# apt list --installed |grep linux-signed
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64
[installed]
linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now
4.18.0.20.70 amd64 [installed]
linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now
5.0.0.15.71 amd64 [installed]
- the setup is not new, has been working perfectly before (about 7
days since my last restart?)
System:
- HW: ASUS Zenbook 14 UX433FN
- Ubuntu 18.04, runing latest HWE, fully updated
- grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),
Suspected/possible cause?:
- recent intel-microcode package update
- recent kernel package updates
Steps taken:
- tried to remove "splash quiet" from grub/kernel cmd line (also tried adding
nosplash, noplymouth)
- completely removed nvidia drivers (apt purge *nvidia*)
- completely purged and reinstalled grub (grup-pc)
- completely purged and reinstalled all kernels (headers, modules, image, ..)
- toggle BIOS "fastboot" (now using OFF)
- toggle UEFI SecureBoot (now using ON)
- remove plymoyth (apt remove *plymouth* , but the workaround is working with
plymouth installed)
Workaround:
- so far, I'm only able to boot with non-Ubuntu kernel!
(linux-image-liquorix-amd64)
- which needs "splash" option ON
I am not sure how to get you more debug info, as this setup has been
working before, and it's a very eary boot-process bug, so I can't even
access dmesg etc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
