Hello, not much of a Linux user (situations like this are why)…but long story short, I’m trying to rehab a ROG PC from 2018.
I made a bootable USB of the current Mint distro, but booting leads to a black screen. I tried compatibility mode, but the boot process hangs on “EFI stub: Measured initrd data into PCR 9”
The PC came with an Nvidia 2080, but it’s actually a 980ti. Also there isn’t integrated graphics here. Any troubleshooting advice would be cool
Update: if I select recovery mode then ‘resume normal boot’, Mint 21 works. However, this computer will be a gift to a tech-illiterate person, so that level of input will not suffice. I installed the recommended (and correct) Nvidia driver, but the results are the same
Mint 21 works! I just got to the desktop environment…and guidance from here?
Edit: I went ahead with the installation. A clean erase and rebuild. The computer didn’t appreciate that. First restart took me to a hanging ROG logo. A second restart took me to GRUB then a black screen
Edit2: manually selecting generic, recovery mode boot option then resume normal boot gets me to the desktop. If anyone knows how I can program the boot sequence to default to generic, recovery then resume normal boot without any input, I’ll consider that a success
Ah, just saw edit2.
Are you saying that there are two options in GRUB one works and the other doesn’t?
If so, this is probably the easiest way: https://wiki.archlinux.org/title/GRUB/Tips_and_tricks#Recall_previous_entry
If it’s multiple options in a menu before you get to GRUB (i.e. there are multiple boot devices), you can edit the order with efibootmgr (https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface#efibootmgr).
This will show you the boot options. You have to run this as root (using sudo)
This will change the boot order
You can remove unwanted entries with
Make sure you use the full 4 digit number and verify that you’re deleting the right one. You can add an entry back, but it is tedious to explain.
Just to clarify, none of the options “work.” But ‘Advanced options for Linux Mint 21’ > ‘recovery mode’ gives me the option to ‘Resume normal boot’. And for whatever reason, that works when a normal boot (without extra steps) doesn’t.
You’re using GRUB: https://wiki.archlinux.org/title/GRUB
There’s a .cfg file in your EFI system partition, sometimes mounted on /boot. /boot/grub/grub.cfg has the settings for the items in that menu. If you can figure out what works about the recovery mode (it’s probably just launching with no kernel parameters), then you can edit the default one.
e: just saw your edits, you don’t need to do any of this, you can just look at your journal with ‘sudo journalctl’ from a terminal (or whatever GUI app Mint ships with)
Did the install complete and then you rebooted and it failed?
This is progress! Presumably, when your system tried to boot it would be writing information to a log that we can read. With your fancy new sysrescuecd, you can boot into a live environment and read that log.
We’ll need to use the sysrescuecd live environment to mount your hard drive and read the log.
Start sysrescuecd, startx, and open a terminal.
Make a directory
Find the device for your system’s root partition. Run
You’ll see a list of things like sda, sdb, nvme0n1. If you’re using a M.2 drive it’ll probably be nvme0n1. Under that it will list the partitions (ex. nvme0n1p1). Your system partition should be the largest one but I don’t know Mint’s default partition layout. If there are multiple we can check them all, so just choose the most likely one.
Once you’ve found the right device you can mount it to the folder you created (you’re already root, you don’t need sudo):
Now if you look in that directory (ls mint-root), you should see a bunch of directories like /bin, /dev, /sys, /usr, /var. If so, this is your system drive. If not and you see a directory named after the user your created when you installed mint, go back and choose the other partition, this is just a home partition.
Assuming you have your system partition, now you can look at the logs:
This viewer uses vim-like controls, so j to go down and k to go up. Page Up and Page Down should also work (probably mouse scrolling too if you’re in a GUI terminal).
The thing that caused the problem should be in the last few lines.