dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221714] New: AMDGPU: Firmware issue on Teros TE-2476G monitor causes black screen/instability with FreeSync and invalid EDID.
Date: Thu, 02 Jul 2026 21:02:21 +0000	[thread overview]
Message-ID: <bug-221714-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=221714

            Bug ID: 221714
           Summary: AMDGPU: Firmware issue on Teros TE-2476G monitor
                    causes black screen/instability with FreeSync and
                    invalid EDID.
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: MANCHOIG@gmail.com
        Regression: No

Description:
The Teros TE-2476G monitor (23.8" 144Hz) fails to properly initialize on the
amdgpu driver. The monitor firmware appears to report a null serial number
(00000000) and fails to negotiate high refresh rates (144Hz) when FreeSync is
active. This results in intermittent black screens or a fallback to 60Hz.

System Info:

    GPU: AMD Radeon RX 580

    Driver: amdgpu

    Kernel:  7.1.2-3-cachyos

    Distribution: Arch Linux / CachyOS

Steps to reproduce:

    Connect Teros TE-2476G via DisplayPort.

    Enable default FreeSync/VRR settings.

    System fails to consistently maintain 144Hz link or causes display signal
loss.

Workaround:
The issue is mitigated by disabling FreeSync via kernel parameter
(amdgpu.freesync_video=0) and forcing the monitor mode using
video=DP-1:1920x1080@144 in the bootloader command line.

Expected behavior:
The amdgpu driver should handle the monitor's invalid EDID gracefully or
provide a "quirk" to ignore the missing serial number and allow stable 144Hz
operation without requiring manual cmdline overrides.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

                 reply	other threads:[~2026-07-02 21:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-221714-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox