From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"
Date: Thu, 03 Mar 2022 17:49:08 +0000 [thread overview]
Message-ID: <bug-215652-206035-cd18BsvQjv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215652-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215652
--- Comment #6 from Alex Deucher (alexdeucher@gmail.com) ---
(In reply to Erhard F. from comment #5)
>
> With CONFIG_DRM_RADEON=m radeon does not load and I still get "modprobe:
> ERROR: could not insert 'radeon': Unknown symbol in module, or unknown
> parameter (see dmesg)" trying to load it manually via modprobe -v radeon.
You need to make sure the firmware is in your initrd. When the kernel loads,
it loads from the initrd. There is no filesystem mounted yet when the radeon
driver is loaded so the firmwares need to be in the initrd.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching someone on the CC list of the bug.
next prev parent reply other threads:[~2022-03-03 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 23:04 [Bug 215652] New: kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)" bugzilla-daemon
2022-03-02 23:07 ` [Bug 215652] " bugzilla-daemon
2022-03-02 23:07 ` bugzilla-daemon
2022-03-03 2:38 ` bugzilla-daemon
2022-03-03 10:33 ` bugzilla-daemon
2022-03-03 16:33 ` bugzilla-daemon
2022-03-03 17:49 ` bugzilla-daemon [this message]
2022-03-03 18:21 ` bugzilla-daemon
2022-03-10 13:19 ` bugzilla-daemon
2022-03-10 14:35 ` bugzilla-daemon
2022-03-18 1:08 ` bugzilla-daemon
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=bug-215652-206035-cd18BsvQjv@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).