22.04 ISO (Nvidia) doesn't boot to live session

[SegaSystem16C]

Cannot get the live disk of Pop!_OS 22.04 LTS to boot into the live session/graphical interface on my PC.

Issue/Bug Description:

Boot from the installation media as usual. The ISO loads services and modules but ultimately hangs with a blinking cursor at [ OK ] Finished Record Runlevel Change in UTMP.
I re-downloaded the 22.04 LTS ISO, and burned a new DVD with an updated CD Burner XP, and used another brand of DVD-R. It had fewer erros when trying to start services, but stopped at the same line. The disc inside the drive wasn't spinning anymore, so I knew no data was being loaded from the DVD anymore. I left it for 30 minutes and the live session wouldn't start. The PC wasn't frozen, because Ctrl+Alt+Del ejects the disc and restarts the computer.

)

I didn't have this issue with the Pop!_OS 21.04 installation disc or my other Linux discs.

Steps to reproduce (if you know):

Insert the installation disc on the DVD drive.
Boot from the DVD drive.
Load modules and services.
Stop after the "[ OK ] Finished Record Runlevel Change in UTMP" line.
Blinking cursor.

Expected behavior:

Boot into the live session of Pop!_OS 22.04 LTS and perform installation or system refresh.

Other Notes:

Intel Pentium G4560
Nvidia GeForce GT 1030
16 GB DDR4 RAM (2x8)
1 TB Seagate Barracuda HDD (Windows 10 Pro)
240 GB Crucial Sata III SSD (Pop!_OS 21.10, with broken GNOME 42 and APT after failed upgrade to 22.04
Gigabyte H110M-S2PH Rev 1.0
Secure Boot = Disabled
UEFI BIOS = Enabled

[DayVeeBoi]

Edit: after trying to boot several previous versions, I eventually found that that version 20.04_39 will boot. I also used
sudo dd if=name-of-iso.iso of=/dev/sdb bs=1024k status="progress" rather than gui usb creators, although I am not sure if that was a factor.

I have a similar issue with Nvidia RTX and AMD R7 5800h. Sometimes it gets stuck at the same point:

At other times, it will stop here:

Other Ubuntu and Arch based live images boot fine. I'm typing this from the same machine with Ubuntu installed and hybrid graphics (seemingly) working. Previously, I had installed Pop on this system and used it for a few weeks. So when I encountered this problem I tried using older Pop ISOs, as well as the non-Nvidia specific Pop!_OS images, all had similar outcomes.

AMD® Ryzen 7 5800h with radeon graphics
16 GB DDR4 RAM (2x8)
1 TB Samsung SSD
Lenovo Legion 5
Secure Boot = Disabled
UEFI BIOS = Enabled

[leviport]

Does the latest iso (number 10) work better? #302 was added to help it on certain Nvidia systems.

[DayVeeBoi]

I get a kernel panic now when trying to boot from image number 10. I did encrypt my hard disk during installation of the earlier release (20.04_39) and the kernel panic seems to be related to that. Maybe it's expected behavior, I've never used full disk encryption before, so I have no idea.
If it will be helpful, I am willing to format the ssd and give it another try.

[renbell313]

Did anyone solve this problem?

[leviport]

I was pretty certain that #302 fixed this issue, so it could be something else you're experiencing. Does it hang at exactly the same screen?

[gsavarela]

Unfortunately it seems the patch hasn't fixed the issue as I am having the same problem while installing Pop! Os as the second OS in a dual boot setup:

Steps to reproduce:

Insert the USB drive.
Boot from the USB drive.
Load modules and services.
Stop after the "[ OK ] Finished Record Runlevel Change in UTMP" line.
Blinking cursor.

Expected behavior:

Boot into the live session of Pop!_OS 22.04 LTS and perform installation or system refresh.

Other Notes:
ISO: pop-os_22_04_amd64_nvidia_19
System Model: DELL XPS 8920
Bios Version/Date: Dell Inc. 10.0.23, 6/11/2020 (Latest)
Processor: Intel Core(TM) i5-7400 CPU @ 3.00GHz, 3000Mhz, 4 Cores(2)
Nvidia GeForce GT 730
Memory: 8 GB DDR4 RAM
1 TB Dual Boot Windows 10 Home, Pop!_OS 22.04 LTS
Windows 10 Home partition, encrypted with VeraCrypt
Secure Boot = Disabled
UEFI BIOS = Disabled

[mmstick]

@gsavarela NVIDIA dropped support for the GT 700 models, so you have to use the Intel ISO now.

[gsavarela]

Thanks, I'll give it a try, and let you know.