Hello, On Fri, Mar 28, 2025 at 10:20:56AM +0100, @ wrote:On 28/03/2025 01:02, Ben Hutchings wrote:In bug discussions, please always reply-all, don't just reply to the sender. I have another question below. On Thu, 2025-03-27 at 19:58 +0100, @ wrote:On 27/03/2025 01:42, Ben Hutchings wrote:Control: tag -1 moreinfo On Mon, 24 Mar 2025 21:44:25 +0100 Joe<shannyodo@yahoo.fr> wrote: [...]I can't provide kernel log with the reportbug program due to howsudoer is set, I usually use pkexec or su . I there another way to transmit the logs if that's useful ?Let me know if you need more informations.Please send the kernel log as an attachment. Also send the kernel log from the working kernel version.Here's the dmesg outputs for 6.12.19 & 6.12.17 . I have no idea what's wrong, good luck and thank you.There's an obvious difference in the logs, which is that we have a lot of messages from the amdgpu driver on 6.12.17 and *none* on 6.12.19.$ grep -r amdgpu /etc/modprobe.* /etc/modprobe.d/blacklist-amdgpu.conf:blacklist amdgpuYou're not the first having such a blacklist entry. Do you have an idea what created it? We tried to pinpoint how this file was created in previous bug reports (e.g. #1094767), but didn't manage to identify the component. Do you have any non-Debian packages on your system that might be responsible?
This might have come from tinkering with AI gen and ROCM from AMD's repo.
The packages were uninstalled, and the source disabled long before the issue came up though.
I'm fairly sure the initramfs was regened by apt while I did that
and possibly in other updates down the line, but I can't think of
anything else that would affect GPU driver selection.
I hope this is helpful.
-- Joe