Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21

[atactic]

When starting the PC, the splash screen freezes with the motherboard logo displayed.
As my disk is encrypted the decryption field does not appear below the logo.

By typing [ALT] + [CTRL] + [DEL] then the splash screen appears again followed by a start-up menu with the following line:
*Ubuntu
 Advanced options for Ubuntu

By selecting 'Advanced options for Ubuntu' the following submenu appears:
*Ubuntu, with Linux5.19.0-15-generic
 Ubuntu, with Linux5.19.0-15-generic (recovery mode)

Selecting the second option, then the system starts loading with the initial lines of code:
Loading Linux 5.19.0-15-generic ...
Loading initial ramdisk ...

When code has finished loading, the last line at the bottom of the screen is for unlocking the disk:
Begin: Mounting root fie system ... Begin Running /script/local-top ... Please unlock disk nvme0n1p3_crypt:

Then i type in the code and hit [return] and more code is loading, until a recovery menu with purple background appears, with the title:
Recovery Menu (filesystem state: read-only).

I select the first menu item:
resume Resume normal boot
and hit [return].

The menu changes to the notification:
You are now going to exit the recovery mode bla bla bla
with the [OK] button below it.

I hit the [OK] button and then the login screen finally appears.

I will post a video of the complete boot sequence later on as I need to install a softaware to edit the video.

It is noteworthy that on my previous Ubuntu 22.04 install the same issue with the frozen splash screen occurred when my system was updated with Kernel 5.15.5, but then I did not try out to execute the [ALT] + [CTRL] + [DEL] command.

Therefore the bug is probably affecting all kernels from 5.15.5 upwards.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-15-generic 5.19.0-15.15
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset wl nvidia
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 25 08:30:29 2022
InstallationDate: Installed on 2022-09-24 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920)
MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-15-generic N/A
 linux-backports-modules-5.19.0-15-generic N/A
 linux-firmware 20220923.gitf09bebf3-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F10
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97X-UD5H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Z97X-UD5H
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[atactic (atactic)]

Video details the boot and start up sequence with actions between stages.

[atactic (atactic)]

Meanwhile kernel has been updated to 5.19.0.18.18, but this has not changed the boot and start up issue.

[atactic (atactic)]

Kernel has been updated to version 5.19.0.21.21 and now during boot the system hangs with a white blinking cursor after hitting the [OK] button following the resume Resume normal boot option (see above explanations about boot sequence).

I had to hard reboot the system and select instead from the 'Advanced options for Ubuntu' the
'Ubuntu, with Linux5.19.0-19-generic (recovery mode)' to be able to start the system again.

Would be thankful to the forum if this bug could be addressed as issues are getting worse and worse, fearing that with the next kernel update that would remove the kernel 5.19.0.19.19 the system may not be starting at all any more due to the just described issue.

[Brian Murray (brian-murray)]

Could you try booting with a daily live image, available at https://cdimage.ubuntu.com/ubuntu/daily-live/current/, and see if the issue exists with it? Thanks in advance.

[atactic (atactic)]

Absolutely.

[atactic (atactic)]

So the issue is that I am only able to boot via CTRL + ALT + DEL from the splash screen with Gigabyte motherboard logo and from there via recovery mode only.
With Kernel 5.19.0-15 up to 5.19.0-19 after recovery mode a 'Resume normal boot' screen appears and from there a normal boot occurs.

[atactic (atactic)]

Which was already the issue reported in the present Bug.
But since Kernel 5.19.0-21 was installed yesterday, then even selecting recovery mode does not work at all any longer. After the 'Resume normal boot' screen by hitting OK, the next screen is a white blinking cursor.
Typing CTRL + ALT + DEL stops processes and gnome and turns the PC down.

[atactic (atactic)]

In fact if wait long enough (about 40 sec) after selecting Recovery Mode with Kernel 5.19.0-21 the system start-up resumes but in recovery mode with a low res, single-screen display.?field.comment=In fact if waiting long enough (about 40 sec) after selecting Recovery Mode with Kernel 5.19.0-21 the system start-up resumes but in recovery mode with a low res, single-screen display.

[Steve Langasek (vorlon)]

When this hangs, what happens if you hit 'Esc'?

[atactic (atactic)]

It actually does nothing.
Cursor continues blinking.

[atactic (atactic)]

Still confronted with the same system boot issue.
Is there any way to spot the origin of the issue from the submitted system reports here above?

[atactic (atactic)]

Hello community, is that not a bug of concern for Kinetic?

[atactic (atactic)]

Dear launchpad community,
Sorry to bump this, but it is a serious bug with Kinetic kernels.
My system is nothing extraordinary and therefore other users probably are encountering the same and staying away from Kinetic for that reason.
Anyone of you could become the solver for this issue?

[Bernard Stafford (bernard010)]

@Brian_Murray
Tested daily build you suggested.
Everything works and boots fine.
Installed then updated, rebooted 3 times.
Ubuntu 22.10 Kinetic
Kernel 5.19.0-23-generic
Python 3.10.7
I did notice it updated to a different kernel version -23.

[atactic (atactic)]

@Brian_Murray @bernard010 thank you for the effort.
Have tried now to reboot with Kernel 5.19.0-23 but same frozen mainboard screen and as well PC starts up only in recovery mode.
Therefore I am still stuck with Kernel Kernel 5.19.0-19 that still freezes at boot but can be made to start with CTRL + ALT + DEL, and starting in recovery mode, then continuing with normal boot as described in the bug description above (have you watched the short video?).
At it occurs at the very beginning of the boot sequence could it be a material compatibility issue? or a problem with the NVidia graphic driver?

[Steve Langasek (vorlon)]

Especially if you see a behavior difference with recovery mode, an Nvidia driver problem is very likely. We had some significant known issues with the Nvidia drivers right around the time of the 22.10 release. Have you made sure you have all of these packages up to date?

[atactic (atactic)]

@vorlon
of course, I care to maintain the system with the latest system, software and driver updates.

[atactic (atactic)]

Previously expressed fear confirmed:

"Would be thankful to the forum if this bug could be addressed as issues are getting worse and worse, fearing that with the next kernel update that would remove the kernel 5.19.0.19.19 the system may not be starting at all any more due to the just described issue."

Updates were done today and after that, despite selecting kernel 5.19.0.19.19 at boot time the system only boots in recovery mode / low res.

But now I changed the graphic driver from NVidia legacy to Nouveau Display Driver and after the initial Low Res splash screen with Motherboard logo only, then the normal high res splash screen with both logo and decrypt field appears. From there the system then boots normally.

The issue is then clearly a compatibility issue with the NVidia legacy driver.
Session started on Wayland.

[atactic (atactic)]

I am now writing this message from a different machine, a Dell XPS 15 7590 with a NVidia CPU and NVidia legacy drivers and that is booting normally and working perfectly fine on Ubuntu 22.10 with Kernel 5.19.0-28 running.

So obviously the issue I am encountering with the desktop machine is clearly hardware related. Since one of the features of Kinetic is to have compatibility with legacy NVidia driver on Wayland, should I continue to follow up on this issue here or should I instead raise the issue with NVidia?

[Stanislav Sidorenko (ssidorenko)]

I'm using Intel Nuc (NUC10i7FNH). Yesterday I got very similar issue on boot after updating to linux-image-5.19.0-28-generic.
linux-image-5.19.0-26-generic boots fine.

NUC10i7FNH does not have any Nvidia chip, just Intel.

[Alberto Milone (albertomilone)]

Hi atatic,

Please try the following from Recovery mode:

1) sudo apt-get --purge remove '*nvidia*'

2) sudo apt install linux-modules-nvidia-525-generic nvidia-driver-525

[atactic (atactic)]

@albertomilone

Just back home and testing this on my desktop.
Solution works.
Boot and Start-up process is now normal.
Thank you.

[Ubfan (ubfan1)]

Note that the Nvidia packaging does not play well with phased updates. For kernel 519.0-35, the Nvidia 525-76.. driver got removed, but then phasing held back some nvidia 525-85 packages necessary to rebuild the nvidia modules -- leaving the currently running kernel without an Nvidia driver. A day later the phasing caught up, all the Nvidia packages downloaded, and the modules rebuilt successfully.

[atactic (atactic)]

@ubfan1 thank you, I have seen your comment as well on Discourse (https://discourse.ubuntu.com/t/22-04-nvidia-drivers/28072/27).
I am not sure to understand your message.
Do you mean that the 5.19.0.35 packages are working again with nVidia legacy drivers?
So should I reinstall them and how to do this and also with which nVidia driver version?

[Ubfan (ubfan1)]

Yesterday, running the 5.19.0-35 kernel and Nvidia 525.76... driver, an update held back several Nvidia 525 packages (the 525.85.05 versions). That in itself was not a problem, but the existing Nvidia modules for that kernel got deleted! Rebooting, the laptop was running off the intel GPU. The Software & Updates/Additional Drivers thought the nvidia 525 driver was selected and in use, but lsmod did not show it, and anything needing the nvidia modules like nvidia-settings or nvidia-smi could not communicate with the driver (the .ko driver files in /lib/modules/5.19.0-35-generic/kernel/nvidia-525 were missing. Booting a former kernel (with the 525.76.. driver still worked. Rather than forcing the issue (doing an explicit install of the held back nvidia packages), I just waited a day, and the phasing (which was at 70%) caught up, the sudo apt full-upgrade succeeded, the modules got rebuilt, and everything worked again. Just wait a bit and see if things correct themselves when you run the upgrade.

[Alex Sim (alextcranglesim)]

Adding a note here too (as well as the discourse page). I had this bug happen to be via phased updates, exactly as ubfan1 mentioned above.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1975650, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

[Daniel van Vugt (vanvugt)]

Comments #24-#25 seem to confirm the original issue for the OP was in fact bug 1975650. If anyone is experiencing a different or new issue then please open a new bug.

[atactic (atactic)]

@alextcranglesim
This bug is not necessarily a duplicate of the referred bug
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1975650
It just happened to also arise in some cases with Kernel updates but this is just the last instance of it happening.
The black screen with blinking cursor happened to me many times in the past when during a fresh install not installing proprietary drivers and later on installing nVidia drivers downloaded from nVidia.
You can search the internet for 'black screen', 'ubuntu', 'blinking cursor', 'nVidia'... and will find plenty of issues reported but none of the solutions ever worked for me.
The point is that I previously never knew how to handle this situation and resorted to a fresh install as I though my system was definitely broken.
This is until I realized that it is still possible to access the system with some keyboard commands as explained above in order to start up Ubuntu and to restore its proper startup behaviour by subsequently updating the driver to the proprietary tested version, which was by the way only the last step in solving the black screen issue.
The other bug report only provides the code to restore the drivers but not what to do when the system is hanging with the black screen.

[Daniel van Vugt (vanvugt)]

'black screen', 'ubuntu', 'blinking cursor', 'nVidia' do not describe a bug, but instead are common characteristics of many thousands of different bugs.

Although bug 1975650 doesn't seem to describe a black screen problem, if you find that reinstalling the driver fixed the issue (comment #25) then we should keep this as a duplicate of bug 1975650.

One possible reason for a black screen is that Nvidia systems are known to sometimes boot to the wrong VT, or even log into the wrong VT. The workaround for that is to use Ctrl+Alt+F1-FN to find the correct screen. Like in bug 1960868 and bug 1878838.

If your black screen problem persists after reinstalling the Nvidia driver, or if you would like to continue debugging that issue, then please use 'journalctl -b-1' or similar to collect a full system log from when the black screen was occurring.

[atactic (atactic)]

Bug is back with Kernel 5.19.038.39
System boots only in recovery mode with basic configuration and not even third party driver for wireless network adapter...
Needed to fall back booting on last working kernel 5.19.0.31.32.