You beat me to it.
I can confirm your observation. I was set to post the draft below:
I updated my Rawhide 24-hours ago. Since then, I lost textual output. I can see the GRUB menu and the Plymouth screen. After those, no texts show up any more -- only the blinking cursor remains. I can tell that there is activity on the machine because the cursor keeps moving around (changing lines like it is printing out stuff, only I can't see any texts). Some commands execute as expected (without visuals, that is). For example, "clear" sends the cursor back to the top-left corner of the screen; but I do not see the text while typing. The phenomenon is strange.
So, I went on to download the latest rawhide ISO (Fedora-Server-dvd-x86_64-Rawhide-20210424.n.0.iso). The installation went fine (graphics and all). However, after installing, I am back to the same phenomena. This behaviour implies that one or more recent packages in rawhide repositories have bugs. Has anyone experienced this recently? Perhaps I should investigate further.
Regards Onyeibo
On Sun, 25 Apr 2021 21:38:59 +0000 (UTC) George R Goffe via test test@lists.fedoraproject.org wrote:
Hi,
I ran a system upgrade late last night and at reboot noticed a major problem with tty (possibly).
I run this system with the multi-user target active, which means I get a text based invitation to login and have to start X manually. This is NOT a new change.
Instead of seeing text "printed" on the screen, I see nothing. It's like the text is invisible. This situation happens near the time of the font change for the various boot messages. After this change, nothing appears except for a blinking "text" cursor. This happens with and without the "nomodeset" boot command line operand present. All the ttys are affected so I doubt that it's an X problem. Hitting enter acts like I entered a blank userid. I visualize logging in and then starting X. This works and I get an X session, windowmaker in my case. ALL the other ttys behave the same... no characters appear except for the cursor. I don't see anything obvious in the output of "journalctl -x -b0".
This system is at the "latest" Fedora 35 (x86_64) upgrades installed.
I'm kinda lost as to just where this problem "lives". Any/all help, hints, tips, suggestions would be greatly appreciated.
Best regards,
George... _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure