[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)"

All of lore.kernel.org
 help / color / mirror / Atom feed

From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.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 16:33:39 +0000	[thread overview]
Message-ID: <bug-215652-2300-VhE0WckDtD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215652-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215652

--- Comment #5 from Erhard F. (erhard_f@mailbox.org) ---
Ok, changed my config to include the firmware via
CONFIG_EXTRA_FIRMWARE="radeon/R520_cp.bin"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"

With CONFIG_DRM_RADEON=y the machine boots now as expected with no radeon error
messages.

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 may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

next prev parent reply	other threads:[~2022-03-03 16:33 UTC|newest]

Thread overview: 21+ 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 [this message]
2022-03-03 17:49 ` bugzilla-daemon
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
  -- strict thread matches above, loose matches on Subject: below --
2022-03-02 23:04 [Bug 215652] New: " 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
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-2300-VhE0WckDtD@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.