I just installed fedora 44 KDE plasma on my Lenovo yoga after using the live USB stick. I’m very impressed with how it handled the tablet out of the box. So I installed it and went through the setup process after rebooting setting my username and password. Now when I try to log in it just keeps coming back to the login screen over and over again. I installed it one more time thinking that maybe I made a mistake during the setup process and the same thing is happening.
Can you switch to an alternative tty using ctrl, alt and f3 and login there? If so, take a look at the end I’d journalctl and post it here as prefirmatted text.
I tried all those combinations to no avail. Nothing but login
OK - try booting with the kernel parameters rhgb and quiet removed from the grub command list, and nomodeset added.
Try the same Ctrl-Alt-F3 combination if it boots to a black screen.
There are lots of “yoga” models. If you don’t find a solution quickly you should install the inxi package in the Live environment, then use a terminal to run inxi -Fzxx and post the output as web-discoverable pre-formatted text so we have hardware details.
The live USB worked fine. How do I open the grub list to edit?
Ok, I booted from the USB again and navigate to grub2 on the boot partion and removed rhgb and quiet from 3 lines. Added nomdeset to al 3 lines. Tried to save the file and got this
Unknown code 177
/run/initramfs/live/boot/grub2/grub.config.part
This is the grub file;
set default=“1”
if [ “$grub_platform” == “efi” ]; then
function load_video {
insmod efi_gop
insmod efi_uga
insmod video_bochs
insmod video_cirrus
insmod all_video
}
set basicgfx=“nomodeset”
else
function load_video {
insmod all_video
}
set basicgfx=“nomodeset vga=791”
fi
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
terminal_input console
terminal_output console
set timeout=10
set timeout_style=menu
search --file --set=root /boot/0x6e8f9104
menuentry “Start Fedora-KDE-Desktop-Live” --class fedora --class gnu-linux --class gnu --class os {
linux ($root)/boot/x86_64/loader/linux nomodeset root=live:CDLABEL=Fedora-KDE-Live-44 rd.live.image
initrd ($root)/boot/x86_64/loader/initrd
}
menuentry “Test this media & start Fedora-KDE-Desktop-Live” --class fedora --class gnu-linux --class gnu --class os {
linux ($root)/boot/x86_64/loader/linux nomodeset root=live:CDLABEL=Fedora-KDE-Live-44 rd.live.image rd.live.check
initrd ($root)/boot/x86_64/loader/initrd
}
submenu “Troubleshooting -->” {
menuentry “Start Fedora-KDE-Desktop-Live in basic graphics mode” --class fedora --class gnu-linux --class gnu --class os {
linux ($root)/boot/x86_64/loader/linux nomodeset root=live:CDLABEL=Fedora-KDE-Live-44 rd.live.image ${basicgfx}
initrd ($root)/boot/x86_64/loader/initrd
}
}
Nah, it’s easier than all that.
Boot from the installation on your hard-drive
When grub pops up hit e, move down to the line with rhgb and quiet on it, remove them, add nomodeset then hit F10 to boot that kernel with those parameters.
Hopefully it gets you in, albeit with a super crappy resolution.
If it does get you to the desktop, you can run journalctl -b -1 --no-hostname --no-pager which will show the journal from the previous boot (-1 means previous boot, 0 means this boot, -3 means three boots ago and so on).
With this in mind you might want to perform a failing boot so that when you do this process immediately after it, the previous boot (the -b -1 in effect) shows what happens when it fails.
Have a look at the journal output for messages towards the end of indicating errors or failures of kde, sddm and so forth - we want to see what happens when you log in, and it turfs you back to the login screen.
I’m a bit concerned that switching to a TTY doesn’t work - are you certain that Ctrl+Alt+F4 for example doesn’t throw you to a new pseudo TTY?
I’ve tried ctl+alt F1-FF12 
. The login screen doesn’t change. I’ll try your suggestion as soon as I get back
I just tried your suggestion and I still can’t login. I changed the line removing rhgb quiet and added nomodeset then pressed F10. Boots to login screen. I type my password and back to login. Tried ctl+alt+F3, nothing.
Ok, so I tried to install Aroura instead. Maybe it doesn’t have the same issue. It doesn’t. It has a completely different issue. Fails to install. Takes forever for the software to install which I don’t think any software gets installed as there is no progress bar. the pic shows the error. So now back to F44.
Fails at login. Just returns to login screen over and over. Function keys are no help, they don’t work. It amazes me that this didn’t come up in testing before release. I feel like I’m back in 1998.
Please do not open a new topic just to complain.
I am merging this with your other topic that appears to be the cause of this post.
The odd thing about your situation is that if the system is up enough to bring you back to a graphical login screen, it’s definitely up enough to present multiple pseudo TTY’s.
Your function keys - do you need to press some other key with them so that they function as F2, F3, F4 etc and not mute, volume up, volume down, brightness controls and so on.
You don’t state which Lenovo Yoga you have, but according to this you may well have a Fn Lock key which if it’s in the “wrong” mode, means you’re not actually hitting Ctrl+Alt+F3… you’re hitting Ctrl+Alt+Mute or something along those lines. Maybe this is teaching you to suck eggs… /shrug
It likely didn’t come up in testing, because no-one had whatever Yoga you have with this level of firmware and so on.
Agreed, but in addition, I would suggest to first test only in textual mode and with a
debug root shell.
To do that, edit the grub entry as said before:
- suppress
rhgbandquiet - add:
nomodeset 3 systemd.debug_shell
The 3 will ask systemd to start the multi-user.target instead of the graphical one
You should normally get a textual prompt for loging in.
systemd.debug_shell will start a root shell on tty9.
Try then to log in with your username and password. If this also fails, one will use
the root shell to debug.
Thank you for the (FN lock). After a new install I used alt+fn+f3 to login at the prompt. I’m now in but how do I start the gui? And how do i fix the graphical login?
Found the commands to start the gui. Now to fix the graphical login
Log in, on the TTY, run the command journalctl -f --no-pager --no-hostname.
It will start displaying the tail of the journal.
Pop back to the now running login greeter and enter your details.
When it throws you back to the greeter, switch back to the TTY you have running and you’ll see what occurred in the background when you logged in, and probably the error causing the fall back to the greeter.
You’ll almost certainly be user 1000, so you should see that in the logs… that’s you logging in. Stuff after that is the interesting bit.
I appreciate all the help I’ve received here. I am able to login via tty and get the gui running. As I mentioned before I really like the fact that F44 does a great job with the tablet (touch screen) side of things. Another huge + is the finger print sensor!! Also, it seems battery usage is more efficient.
The obvious con is the login is a PIA. I don’t think I have to say that this will deter adoption by users who aren’t willing to go the extra mile to figure it out. Maybe it’s just Lenovo yoga issue but considering the several other distros I have tried, Arch and Debian flavors didn’t have a problem leaves me wondering.
I am enjoying the KDE experience fedora has built. I have always liked KDE but there was always some issue that moved me back to gnome. Even other distros plasma builds aren’t this good including KDE LINUX immutable which drove me mad.
One of these days I’ll pull a boot journal and post it. Right now i just didn’t shut the system down which I never do anyway.
Thanks again
Cheers