Comment # 7 on bug 1050256 from Dave Plater

i+ | xf86-video-amdgpu  | package | 1.3.0-1.1                  | x86_64 | oss   
i+ | xf86-video-amdgpu  | package | 1.3.0-1.1                  | x86_64 | Main
Repository (OSS)
i+ | xf86-video-fbdev   | package | 0.4.4-9.4                  | x86_64 | oss   
i+ | xf86-video-fbdev   | package | 0.4.4-9.4                  | x86_64 | Main
Repository (OSS)
i+ | xf86-video-intel   | package | 2.99.917.770_gcb6ba2da-1.3 | x86_64 | oss   
i+ | xf86-video-intel   | package | 2.99.917.770_gcb6ba2da-1.3 | x86_64 | Main
Repository (OSS)
i+ | xf86-video-nouveau | package | 1.0.15-1.3                 | x86_64 | oss   
i+ | xf86-video-nouveau | package | 1.0.15-1.3                 | x86_64 | Main
Repository (OSS)
i+ | xf86-video-vesa    | package | 2.3.4-9.4                  | x86_64 | oss   
i+ | xf86-video-vesa    | package | 2.3.4-9.4                  | x86_64 | Main
Repository (OSS)
I just rebooted with drm-kmp-default reinstalled but after deleting nomodeset I
set runlevel 3 and tailed journalctl on tty2 and init 5 on tty1 and I haven't
had a hang in plasma5 yet.
I've confirmed that "fbcon: inteldrmfb (fb0) is primary device" is in the
journal, it only occurs when I boot without nomodeset and drm-kmp-default is
installed. Ill try a reboot straight into runlevel 5