1c74ca7a1a9a ("drm/fb-helper: call vga_remove_vgacon automatically.")
bp at alien8.de
Fri Aug 9 09:43:05 UTC 2019
On Fri, Aug 09, 2019 at 10:54:41AM +0200, Gerd Hoffmann wrote:
> A bit later:
> [ 8.198138] radeon 0000:00:01.0: Direct firmware load for radeon/PALM_pfp.bin failed with error -2
> [ 8.198351] r600_cp: Failed to load firmware "radeon/PALM_pfp.bin"
> [ 8.198512] [drm:evergreen_init [radeon]] *ERROR* Failed to load firmware!
> [ 8.198590] radeon 0000:00:01.0: Fatal error during GPU init
> So the radeon drm driver tries to load and fails due to missing firmware,
> thats why you have a non-working display.
> So your options are:
> (a) install linux-firmware, so the radeon driver can initialize, or
> (b) boot your kernel with "nomodeset" command line option. The radeon
> driver will not initialize then, and also not disable conflicting
> display drivers (vgacon or fbcon @ vesafb/efifb).
Damn firmware! I should've seen that message. ;-\
Yeah, did a) and that worked. Thanks!
> Possibly it also makes sense to have the radeon driver try load the firmware
> (from disk) rather early in the initialization process, before calling
> drm_fb_helper_remove_conflicting_pci_framebuffers, so firmware not being
> installed doesn't kill the display.
That would've helped and saved a lot of time.
Good mailing practices for 400: avoid top-posting and trim the reply.
More information about the dri-devel