Description of problem: Could be systemd, could be dracut, could be the kbd tools, I suppose it even could be legacy crud from grub. On boot, at some point, all of the whitespace on the screen, and some of the text, is changed to garbage characters. This happens before the DRM driver is loaded, and before the plymouth theme starts (both of these clear the display). Happens with & without nomodeset. Version-Release number of selected component (if applicable): systemd-188-3.fc18.x86_64 dracut-023-39.git20120910.fc18.x86_64 How reproducible: 100% Steps to Reproduce: 1. boot
Created attachment 615581 [details] screenshot Here's a screencap from a video of the boot - the change in color halfway through the screen is an artifact of taking a still frame of the video.
Spotted the Keytable warning but it went away either when I installed the latest kernel from koji and or when I ran grub2-mkconfig to regenerate grub menu. You can install ( or reinstall ) the latest kernel from koji and regenerate the grub menu to see if it fixes this issue.
Did you see the corruption as well, or just the keytable warning? Regenerated grub2 config, it didn't appear to change the behavior with respect to the font(?) corruption. Happens both with F17 kernel and current F18 kernel.
I only saw the keytable warning no font corruption
uhum not the FONT warning or the corruption
systemd doesn't actually interface with the kernel when loading keymaps/fonts. This is done via loadfont from kbd. The garbage problem is somewhere between kbd and the kernel. Reassigning.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.