I’m experiencing an issue with my Asahi Fedora Remix KDE installation on a MacBook Pro M1 Pro (2021). After disabling the graphical target through systemd, I’ve been unable to log in. Every time I try to enter my login credentials in the (tty1), it keeps saying “login incorrect.” I’m 90% sure my login and password are correct.
Here’s what I’ve tried so far:
Attempted to boot into single-user mode and recovery mode by setting bootargs in U-Boot:
-setenv bootargs single
-setenv bootargs graphical.target
-setenv bootargs rescue
None of these commands seemed to work. The system still boots into tty1, and I’m unable to make any progress.
Root access is not an option for me as I can’t log in at all.
I’m new to Linux and don’t have much experience troubleshooting issues like this. Any guidance or suggestions would be greatly appreciated. How can I regain access to my system or at least troubleshoot the login issue?
I’ve already tried accessing the root account, but I can’t log in as root either. It results in the same ‘login incorrect’ issue. Are there any alternative ways to reset the password or troubleshoot this without root access?
The root account on Fedora is disabled by default, so you won’t be able to login into it. Also, on Asahi we use only u-boot to create the EFI environment for grub, so you can’t change the kernel cmdline from it, you need to do it from grub.
If you need to reset the password for your user, easiest is probably to enter the grub menu and edit the kernel cmdline to pass init=/bin/bash. Then boot the system and reset the password with something like:
# mount -o remount,rw /
# passwd username_to_reset
# touch /.autorelabel
# mount -o remount,ro /
# reboot
Replace username_to_reset with your actual username. This will, in order, make the filesystem writeable, reset the password, signal SELinux it will need to do a relabel on the next boot, remout read-only and reboot the system. The next boot will seems to hang for a few minutes while SELinux does its thing – leave it alone and it will eventually reboot by itself, and you should then be able to login with your new password.
It’s possible that you don’t have your PATH set at that point. Try using /usr/bin/passwd instead. That will tell your shell just where to find the program.