Bug#1111095: continued...

From	Uwe Kleine-König <ukleinek@debian.org>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#1111095: continued...
Date	2026-08-18 14:00 +0200
Message-ID	<NtqE1-bG6M-3@gated-at.bofh.it> (permalink)
References	<LjJjj-7BbQ-5@gated-at.bofh.it> <NtqE1-bG6M-5@gated-at.bofh.it> <LjJjj-7BbQ-5@gated-at.bofh.it> <NtqE1-bG6M-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Sun, Aug 09, 2026 at 04:21:15PM +0200, Topaze Topaze wrote:
> Just for information, in case anyone runs into this bug. I'm currently
> using kernel 6.12.101+deb13-amd64 and dmesg was still reporting error
> messages. But an AI agent suggested that I reload AMD’s non-free firmware
> and add this file:
> 
> /etc/modprobe.d/amdgpu.conf with the following content:
> options amdgpu cik_support=1
> options radeon cik_support=0

I guess that upstream should consider using amdgpu for your hardware
then, too.

Can you please try a more recent kernel, the one from testing or
backports will do.

Assuming the situation is the same there (i.e. radeon defaults to bind
to that hardware but amdgpu being better), can you please report that
upstream to amd-gfx@lists.freedesktop.org? Please keep the bug on Cc:
for that.

Thanks
Uwe

Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread

Thread

Bug#1111095: continued... Uwe Kleine-König <ukleinek@debian.org> - 2026-08-18 14:00 +0200

csiph-web