Boot stuck in UEFI after enrolling keys for drivers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hello,
I faced the following problem.
After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description.
Normal behavior:
1. Press the power button on Laptop.
2. Enter to Grub menu, select Ubuntu and continue.
3. See boot logo.
4. Successfully boot in Ubuntu.
Bad behavior:
1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox).
2. Enter a password for Secure boot during installation.
3. Shut down the system.
4. Press the power button on Laptop.
5. Enter to Grub menu, select Ubuntu and continue.
6. See boot logo.
7. System stuck, only black screen and blinking white underscore cursor.
After some time I realized that to continue boot after step 7 I need the following.
8. Change console by Alt+Fn+F2.
9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately).
10. Successfully boot in Ubuntu.
Issue occurrence: 100%.
Removing drivers (apt-get purge virtualbox) doesn't help.
Disabling of secure boot in BIOS doesn't help.
Expected behavior: To be able to boot successfully.
Actual result: Stuck on boot.
Environment:
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ uname -a
Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Please find dmesg attached.
Any help is appreciated!
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2021-03-06 (46 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: LENOVO 82A1
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.197
Tags: hirsute wayland-session
Uname: Linux 5.11.0-16-generic x86_64
UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2021
dmi.bios.release: 1.31
dmi.bios.vendor: LENOVO
dmi.bios.version: DHCN31WW
dmi.board.
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40688 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.ec.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: Yoga Slim 7 14IIL05
dmi.product.name: 82A1
dmi.product.sku: LENOVO_
dmi.product.
dmi.sys.vendor: LENOVO
affects: | ubuntu → plymouth (Ubuntu) |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1925055/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]