Boot stuck in UEFI after enrolling keys for drivers

Bug #1925055 reported by Gluttton
6
This bug affects 1 person
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/controlC0: gluttton 1602 F.... pulseaudio
CasperMD5CheckResult: unknown
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=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-16-generic N/A
 linux-backports-modules-5.11.0-16-generic N/A
 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.asset.tag: ���������������
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40688 WIN
dmi.chassis.asset.tag: ���������������
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Yoga Slim 7 14IIL05
dmi.ec.firmware.release: 1.29
dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
dmi.product.family: Yoga Slim 7 14IIL05
dmi.product.name: 82A1
dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
dmi.product.version: Yoga Slim 7 14IIL05
dmi.sys.vendor: LENOVO

Revision history for this message
Gluttton (gluttton) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

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/FindRightPackage. 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.]

tags: added: bot-comment
Gluttton (gluttton)
affects: ubuntu → plymouth (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Do you need to change VT or is pressing Esc to dismiss the plymouth screen enough? Could you try if starting without splash (https://wiki.ubuntu.com/Plymouth#Toggling_to_Traditional_Text-based_Boot) workaround the issue?

Changed in plymouth (Ubuntu):
status: New → Incomplete
Revision history for this message
Gluttton (gluttton) wrote :

Hello Sebastien,

> Do you need to change VT or is pressing Esc to dismiss the plymouth screen enough?
Yes, change VT is necessary, pressing Esc (or Fn+Esc) doesn't help. Moreover after pressing Esc trick with Alt+Fn+F2 Alt+Fn+F1 doesn't work too and I need to reboot. I checked it before and after disabling "splash".

> Could you try if starting without splash (https://wiki.ubuntu.com/Plymouth#Toggling_to_Traditional_Text-based_Boot) workaround the issue?
I removed "splash" from /etc/default/grub and regenerated grub.cfg via sudo update-grub (according to the link). During the next boot I can see a difference (I see dmesg output in the display). Unfortunately, it doesn't help to solve the issue.

One difference: with disabled splash instead of black screen WITH blinking underlying cursor I see only a completely black screen WITHOUT any cursor.

I can't say for sure, but it seems that the issue happens not during plymouth, but during switch between plymouth and login screen.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks, it seems the issue is happening without plymouth then so it's probably the wrong component. I'm unsure what's the right place but I'm going to reassign to systemd which is probably closer from being right

affects: plymouth (Ubuntu) → systemd (Ubuntu)
Changed in systemd (Ubuntu):
status: Incomplete → New
Revision history for this message
Dan Streetman (ddstreet) wrote :

> But after I install some drivers (NVidia

you appear to have 2 separate graphics cards:
[ 4.893710] nvidia 0000:30:00.0: enabling device (0006 -> 0007)
[ 6.034799] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device

my guess would be you're having problems with the kernel choosing the correct graphics device to use, and/or some problem with the driver not correctly updating the screen.

I also noticed this:
[ 5.535665] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7
however you said disabling secure boot doesn't help, so that's probably not related.

Have you tried uninstalling the nvidia driver package to see if that is what's causing the problem?

> Return to the original console by Alt+Fn+F1

Just a note, since you're booting with vt.handoff=7 the active VT should be 7, i.e. Ctrl+Alt+F7

You might also want to try booting with all the possibly relevant params removed, i.e. remove 'quiet splash vt.handoff=7'

You could also try adding 'nomodeset' to the kernel boot params to see if that helps.

In any case, this certainly looks like a kernel issue, not systemd.

Changed in systemd (Ubuntu):
status: New → Invalid
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1925055

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: hirsute
Revision history for this message
Gluttton (gluttton) wrote :

Hello Dan,

Thank you very much for your comments!

I played with graphics card settings and found out that when I use only Intel graphics everything works well and I can boot without stuck.

I performed the following steps.
1. Originally I used NVidia graphics via NVidia driver.
2. First I switched on Nouveau driver and it didn't help.
3. Then I switched again on NVidia recommended driver (nvidia-driver-460) and it didn't help.
4. Eventually I switched on Intel graphics via nvidia-settings (prime selection) and it helped.

Thanks!

tags: added: apport-collected wayland-session
description: updated
Revision history for this message
Gluttton (gluttton) wrote : AlsaInfo.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : CRDA.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : IwConfig.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : Lspci.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : Lspci-vt.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : Lsusb.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : Lsusb-t.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : Lsusb-v.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : PaInfo.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : ProcEnviron.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : ProcModules.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : PulseList.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : RfKill.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : UdevDb.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : WifiSyslog.txt

apport information

Revision history for this message
Gluttton (gluttton) wrote : acpidump.txt

apport information

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.