Comment 29 for bug 2031198

Revision history for this message
Bruce Goodwin (bgoodwin) wrote (last edit ): Re: Boots to black after upgrade to 22.04, Cannot use other TTY interfaces either (ctrl+alt+f2, etc)

Pretty sure it's booting to the VT with the login screen because the login screen is at least receiving keyboard input without switching VTs. (I can log in using the "pretend there's a login screen there, even though it is not displayed" workaround from comment #5) but i did the experiment anyway to be sure. Never assume anything, right?

So I just tried switching around between VTs on boot (while the login was invisible on VT1). Here are the results:

With 'nvidia-drm.modeset=1' : Booted to a black screen with no backlight. I tried VTs 2-12, going back to VT1 in-between. backlight was off on all VTs. I sshed in and plymouthd was blocked on nvidia_modeset so apparently i didn't even get as far as the login screen.

With 'nvidia-drm.modeset=0' : Booted to a black screen with the backlight on. I tried VTs 2-12, going back to VT1 in-between. On VTs 2-12 I can see the tail end of the kernel log, but it is not a usable terminal. There's no login prompt and nothing shows up on typing. Each time I went back to VT1 there was just blackness (backlight stayed on).

Regarding `nvidia-drm.modeset`; I'm happy to switch to 'nvidia-drm.modeset=1` for individual experiments. However, 'nvidia-drm.modeset=0', is the only way I've found so far to get to a working logged-in x session (this gets me no login screen displayed but I can log in and the logged-in x session displays fine). If I use 'nvidia-drm.modeset=1' (or don't specify `nvidia-drm.modeset` at all) I get the soft lockups blocked on `nvidia_modeset` either on plymouthd or the logged-in x session.