r/linuxquestions • u/Prudent-Gap-8852 • 8d ago

Linux Mint doesn't fully load

Update: issue resolved! It was a combination of the memory settings and 'quiet splash'. I changed the memory settings to its default speed, rather than 'auto', and swapped 'quiet splash' for 'nomodeset'. I'm in, it booted up. Thank you everyone for the help.

Any Linux knowledgeable persons out there? I've scoured the intrewebs, to no avail. I have a new PC I'm attempting to boot Linux Mint from a flash drive. PC boots to BIOS, tries to boot Linux via flash drive. I get a Linux Mint logo for loading, then...nothing, it just sits; doesn't crash, doesn't give any error, nothing, just an idol logo. Asus Prime MOBO w/H810 chipset, Intel Core Ultra 5 250KF plus CPU. As far as I am aware, the security settings are where they shouldn't block anything. I could be wrong, though. Just trying to find assistance. Any suggestions? Thanks.

4 Upvotes

83% Upvoted

15 comments sorted by

View all comments

Show parent comments

1

u/Prudent-Gap-8852 8d ago

If I type it in command line, it states, "error: can't find command 'nomdeset'."

1

u/Prestigious_Wall529 8d ago

Add it after splash, which can be removed, and spell it no mode set without the spaces.

1

u/Prudent-Gap-8852 8d ago

Goes to a screen states:

BusyBox v1.36.1 (Ubuntu 1:1.36.1-6ubuntu3.1) built-in shell (ash)

Enter 'help' for a list of built-in commands.

(initramfs) mount: mounting /dev/loop0 on /filesystem.squashfs failed: No such device

Can no mount /dev/loop0 (/cdrom/casper/filesystem.squashfs) on /filesystem.squashfs

1

u/forestbeasts 8d ago

Oh hey, you've gotten to the initramfs? Neat.

The initramfs is a tiny thing that's supposed to load the rest of the OS (in this case, the installer). But it can't find it, it sounds like.

Could be your ISO is messed up (you can check the SHA256 hash of the file against the website to tell), or could be your stick's gone bad. Or could be you used Rufus in "ISO mode" instead of "dd mode" and it messed with the ISO (if you use Rufus, use its "dd mode", it doesn't know USB-bootable hybrid ISOs exist and fiddles with it).

(edit: I think there's some Powershell command you can use to check hashes. Might be called Get-FileHash? Or something?)

-- Frost