Ubuntu fails to boot (Nvidia hybrid)

[Bashing-om]

xashyar; Me thinks

"recovery" does employ nomodeset to boot.

Possible that you are not following my advise to boot from grub's boot menu.

Boot to the grub menu
and with the latest kernel (default) selected; press the e key for edit mode.
In this next screen is the boot sequence - arrow down to the line that starts with linux
substitute systemd.unit=multi-user.target for quiet splash
key combo ctl+x to continue to boot

do you now boot to a TTY ?

maybe Yes

[xashyar]

Bashing-om; Ooops!

Sorry I described it badly.

This is exactly what happens.

1. In the grub menu I edit the first option (Ubuntu):
https://ibb.co/mJtzFWt


2. And, as usual this is what happens when I press Ctrl + X:
https://ibb.co/myhGbmB

(But If I pick one of the 'recovery mode' kernels, place 'systemd.unit=multi-user.target' and then press ctrl+x to continue I do get a TTY, to start a graphical.target and the rest)

My digression (°–°)ﾉ

[Bashing-om]

xashyar - Hey !

A Image *is* worth a thousand words ---
crashkernel ??
rebooting now and rechecking my memory what the linux line should be !

-I shall return-

[Bashing-om]

xashyar - OK

No idea of the why or wherfore a crashkernel parameter is extent!
All that required ls vmlinuz<version> and the root=UUIDXXXX ro
that boots to the display manger's login screen.
Now we want to boot to a TTY instead so we insert the systemd.unit=multi-user.target parameter.
so:
On the linux line remove all after the root=UUID=<217ed9a7-e11a-4e32-8c05-992e8c8932b6> ro
and next insert that boot parameter systemd.unit=multi-user.target after "ro".
key combo ctl+X

-Now do you boot to a TTY ?

-Maybe-

[xashyar]

Bashing-om; excuse my delayed response.

I removed the crashkernel parameter altogether, and grub's now looking like this:
https://ibb.co/SVgMKVr

But unfortunately I still get the boot-freeze scenario, after hitting ctrl+x:
https://ibb.co/GTWth0J


Also, I think this bug is very similar:
https://bugs.launchpad.net/ubuntu/+s...5/+bug/2031198

[Bashing-om]

xashyar - Sorry

Now above my skills set.
Unable to boot to a TTY and I can not explain why

Looks as Daniel van Vugt (vanvugt) - very talented developer - from the bug report; seems to indicate there is no real fix here.

ouch!

[xashyar]

Bashing-om; It is kind of sad,

Yess Daniel also chimed in on my bug report https://bugs.launchpad.net/ubuntu/+bug/2071680 and marked it as inconclusive.

The truth of it is, I used to run Ubuntu on this machine for a long time, pre-2022, and now in 2024. My hunch was that something has changed in this period and therefore we can trace it, hopefully.


I have a few options left now, 1) Try a non-GNOME Ubuntu flavor (perhaps Kubuntu?), however I'm not sure if it's a DE problem. 2) Downgrading the BIOS/UEFI firmware, not sure a good idea, but I can try 3) Trying Debian, since it's a more conservative release, 4) Wait for a new Nvidia-driver release

And eventually if all fails, I might have to bite the actual bullet and go back to windows, it's real hard to deal with Ubuntu in recovery mode.

Best