From: Borislav Petkov <bp@alien8.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: 1c74ca7a1a9a ("drm/fb-helper: call vga_remove_vgacon automatically.")
Date: Fri, 9 Aug 2019 11:43:05 +0200 [thread overview]
Message-ID: <20190809094305.GE2152@zn.tnic> (raw)
In-Reply-To: <20190809085441.vwg2psrndjo2366q@sirius.home.kraxel.org>
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.
Thanks again!
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-08-09 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190808174542.GN20745@zn.tnic>
[not found] ` <20190809072133.2xlafq4qxitgky6l@sirius.home.kraxel.org>
[not found] ` <20190809074700.GD2152@zn.tnic>
2019-08-09 8:54 ` 1c74ca7a1a9a ("drm/fb-helper: call vga_remove_vgacon automatically.") Gerd Hoffmann
2019-08-09 9:43 ` Borislav Petkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190809094305.GE2152@zn.tnic \
--to=bp@alien8.de \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox