Comment 23 for bug 1100386

Although this is fundamentally a kernel issue, the current kernel infrastructure would really only be able to abort anyone use the 'being replaced' framebuffer when we switch from efifb to a DRM framebuffer. This change will likely be extensive and slow to get through upstream. Also plymouth will have to be modified to handle being aborted and reconnect to the replacement transparently. In the short term we can avoid this issue the same way we avoided it for vesafb by demoting the driver to a secondary display. This means we only use efifb at all if no DRM driver appears. Neatly avoiding the issue.

As we have now (early saucy) moved udev over to systemd sources I have proposed this against both udev and systemd. udev for raring and systemd for saucy. I will attach patches once they are tested.