Diederik de Haas writes:
> Then I'm inclined to think this *is* a separate issue, which is
> due to the upgrade to -19, but that you happen to have an AMD
> GPU is 'not' relevant.
>
> I realize it's not what you want, but may result in an useful
> extra data point if you (for this test) switch
Diederik de Haas writes:
> Then I'm inclined to think this *is* a separate issue, which is
> due to the upgrade to -19, but that you happen to have an AMD
> GPU is 'not' relevant.
> I realize it's not what you want, but may result in an useful
> extra data point if you (for this test) switch
On Sunday, 23 October 2022 15:15:36 CEST inasprecali wrote:
> It does not boot at all, I'm unable to SSH into it. It's not
> merely that the display does not work.
Then I'm inclined to think this *is* a separate issue, which is due to the
upgrade to -19, but that you happen to have an AMD GPU
On Sun, 23 Oct 2022 13:40:26 +0200 Diederik de Haas
wrote:
> Does it really not boot? Or does the screen not work properly?
>
> The cases in this bug report all boot AFAIK, it's just that the
screen does
> not work properly, but people were able to SSH into the machine.
> If your system
On zondag 23 oktober 2022 12:02:52 CEST inasprecali wrote:
> After updating to the latest version (5.10.149-2), my system
> running an AMD GPU and CPU still does not boot. I am unable to
> retrieve any logs from the systemd journal.
Does it really not boot? Or does the screen not work properly?
After updating to the latest version (5.10.149-2), my system
running an AMD GPU and CPU still does not boot. I am unable to
retrieve any logs from the systemd journal.
CPU: AMD FX-8350
GPU: AMD R9 270X (Southern Islands Family)
Kernel command line parameters:
Dear maintainer,
I can confirm this bug too. Processor is an AMD Ryzen 5 5600G with
Radeon Graphics. It doesn't boot (at least not in ~10min) and displays
only the mentioned "flip_done timed out" messages.
5.10.0-18-amd64 works normally.
Best regards,
Andreas
Can confirm this issue with a AMD Ryzen 3 2200G Processor with Vega 8
Graphics on a AsRock DeskMini A300.
I can confirm this same exact problem on a machine of mine.
CPU: AMD FX-8350
GPU: AMD R9 270X (Southern Islands Family)
5.10.0-19 fails to boot, while 5.10.0-18 does.
Best regards.
--
inasprecali
Failed to boot kernel 5.10.0-19 with:
CPU: AMD Ryzen 7 3800X (16) (no integrated graphics)
GPU: AMD ATI Radeon Vega Frontier Edition
No issues with kernel 5.10.0-18.
---
Ian
I can confirm too
AMD® Ryzen 7 4700u with radeon graphics × 8
AMD® Renoir
Same thing here with an AMD Ryzen 5 PRO 3400G system.
Also gnome-shell have been complaining about "Failed to set CRTC gamma:
drmModeCrtcSetGamma on CRTC 62 failed: Permission denied" for some time. I
don't know what is CRTC 62, but clearly it is related.
Dear Maintainer,
i can confirm the problem.
All of our notebooks with integrated AMD graphics (CPU: AMD Ryzen 7 PRO
4750U with Radeon Graphics) are affected and don't boot anymore.
During boot the following error-messages appear:
[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
Package: linux-image-amd64
Version: 5.10.149-1
Severity: important
X-Debbugs-Cc: autop...@protonmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I upgraded to the latest security kernel on Stable
14 matches
Mail list logo
