Yeah, I did that. The thing that says “grub cmd Linux default” or whatever? That’s exactly what I did. I added exactly what I typed, with spaces, and it left me with the picture I sent.
Did it complete when you ran the grub update? The only thing you can do is remove it and update grub again and reboot.
I ran the grub update command and everything. I made sure to do that before rebooting. But now when I boot into the system, it gets stuck on systemd.
And that’s the problem. I’d remove it, but I can’t even get into my system to fix it. I don’t think I can open it in TTY mode either.
Have you tried? alt + f1 f2 or whatever? Log in as root.
Just tried that. It didn’t really do anything. It’s still stuck on the same thing
I wondering if I made a typo when I edited the grub file…
Well you can always arch-chroot into it then and change the grub file.
Trying this, and it doesn’t let me mount the file system because it’s encrypted. It says that “crypto_LUKS” is an unknown filesystem type
Ok, update:
Apparently, optimus manager is the problem. It has a couple of bugs that caused it to not start correctly, but upon further research, I was able to fix it by editing some config files. The only problem is that I can’t use wayland at the moment because optimus manager doesn’t work well with that. So, I didn’t have to blacklist anything. It was just a wayland and optimus issue.
Now that I have said this, I would like to clarify something for the record: at no point during the process of fixing this problem did I spend four hours breaking and, subsequently, reinstalling my entire system. That did not happen, and anything that suggests otherwise is wrong.
Also, @ricklinux and @manuel, thank you for your help and patience, and I’m so sorry for wasting your time.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.