Comment 32 for bug 127008

Awesome, that looks like an acceptable solution to me.

I did a bit more experimentation, and I found that after installation has completed (even before rebooting), the issue cannot be reproduced using the steps I outlined. So it is only occurring during a very specific point of time, after /target is mounted, but before installation has completed. I did a `modprobe vga16fb fbcon` to turn on the installation environment's framebuffer, but that was not sufficient, so there is something more unique about that environment than just the vga16fb. I wonder if packages are in an inconsistent state or something... (Maybe there's a mismatch between what's in memory and what's on disk?)

Anyway, since I couldn't find anything more enlightening that way, I think your patch is going to be the best way to go. I'll roll it out directly. Good work!