I can also confirm that an unmodified 5.10.153 from kernel.org with
debians .config file works.
On Fri, 28 Oct 2022 20:26:55 +0200 Gert wrote:
> 5.19.0-0.deb11.2-amd64 works fine at first glance.
I am also affected and i also tried this kernel and it works as you can
read here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042#160
I also filed a new drm bug here:
https://gitlab.
On Thu, 27 Oct 2022 19:12:43 + inasprecali
wrote:
> I think bug 1022806 is a recent one referring to 5.10.149-2
> specifically, which is about this same issue. I don't think there
> is a need to report yet another bug about it.
Ok, then i switch to 1022806 too. I already created a new drm bu
Am 23.10.22 um 14:27 schrieb Diederik de Haas:
On zondag 23 oktober 2022 14:10:11 CEST Andreas Wirooks wrote:
You both have kernel parameters like these. Can you explain why?
I have an AMD GPU on a machine and I have never set parameters like these.
These are parameters for Southern Islands
Am 23.10.22 um 13:43 schrieb Diederik de Haas:
You both have kernel parameters like these. Can you explain why?
I have an AMD GPU on a machine and I have never set parameters like these.
These are parameters for Southern Islands (si) and Sea Islands (cik) AMD
GPUs:
https://en.wikipedia.org/wiki
The new Debian 11/bullseye kernel 5.10.149-2 does not help on my setup.
Still a black screen and nothing is logged.
Also in rescue mode without "quiet".
My GPU is:
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81)
02:00.1 Au
Hi.
as far as i know only packages from testing are backported. And linux
latest is actually at the same version in testing/stretch and jessie
backports. So testing/stretch has exactly the same problem. The version
in SID already depends on Kernel 4.7. I don't know what blocks its
transition to tes
Thank you very much for answering to my report.
Please excuse my late answer. I did't had much time to test.
> It works on my own system with one of these chips, but only from
> soft-off (S5) and not suspend-to-disk (S4). Which are you testing?
>
> Does this work in Linux 3.2 from testing/unst
Package: linux-2.6
Version: 2.6.32-41squeeze2
Severity: normal
The title says it all. I already tried the ethtool setting from the debian
wiki. No success.
I found one solution by using the r8168 driver from realtek. With this driver
WOL works.
The r8168 driver has an other problem. Sometime
Thank you for ansering, but the free radeon driver has the same effect.
I forgot two things to to tell in my report. First, i already tried
without fglrx. Second, suspend to ram is not affected - only suspend to
disk.
Regards,
Andreas
P.S.
Sorry for sending RichText first (i hope it was filtered
Package: linux-2.6
Version: 2.6.32-32
Severity: important
Resume leads to a total crash. In the log's i found the following in messages:
[0.00] PM: Registered nosave memory: 0009f000 -
000a
[0.00] PM: Registered nosave memory: 000a -
000e
11 matches
Mail list logo
