Your message dated Thu, 20 Feb 2025 12:29:59 +0100 (CET)
with message-id <20250220112959.bcf9dbe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #942513,
regarding linux 5.2.0-0.bpo.3-amd64: amdgpu doesn't find firmware
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
942513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Severity: normal
Dear Maintainer,
On buster with linux image 5.2.0-0.bpo.3-amd64 at boot time I have this error
message :
"*ERROR* amdgpu requires firmware installed"
[ 1.317558] [drm] amdgpu kernel modesetting enabled.
[ 1.317812] [drm:amdgpu_pci_probe [amdgpu]] *ERROR* amdgpu requires firmware
installed
But firmware is actually installed both in
# ls /usr/lib/firmware/amdgpu/ | wc
--> 289 lines
and in
# lsinitramfs /boot/initrd.img-5.2.0-0.bpo.3-amd64 | grep firmware | grep
amdgpu | wc
--> 289 lines
$ dpkg -l :
ii firmware-amd-graphics 20190717-2~bpo10+1 all
-- System Information:
Debian Release: 10.1
APT prefers stable-updates
APT policy: (991, 'stable-updates'), (991, 'stable'), (95, 'testing'), (90,
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.2.0-0.bpo.3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
