All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 220130] New: Display not working when connected via displayport (purple screen)
Date: Thu, 15 May 2025 23:06:37 +0000	[thread overview]
Message-ID: <bug-220130-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 220130
           Summary: Display not working when connected via displayport
                    (purple screen)
           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: kontoepicowe@tutanota.com
        Regression: No

Created attachment 308130
  --> https://bugzilla.kernel.org/attachment.cgi?id=308130&action=edit
the purple screen

The photograph of how it looks is in the attachment. I have a GTX 970 connected
via DisplayPort. When launching any LiveISO in normal mode, I get this screen.
HDMI works, although stuttery. The GPU is completely fine, as I game on it on
daily basis. In some distros (tried Linux Mint) starting with nomodeset makes
the display working. On Arch-based distros I get stuck at "Reached target
graphical interface" in the TTY.

-- 
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:[~2025-05-15 23:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 23:06 bugzilla-daemon [this message]
2025-05-16 11:22 ` [Bug 220130] Display not working when connected via displayport (purple screen) bugzilla-daemon
2025-05-18 22:14 ` bugzilla-daemon
2025-11-06  8:22 ` bugzilla-daemon
2025-11-06  8:22 ` bugzilla-daemon

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-220130-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.