From: stratus@tuta.io
To: Nouveau <nouveau@lists.freedesktop.org>
Subject: [Nouveau] Some monitors not working after 6.2 kernel due to Nouveau commit
Date: Tue, 12 Sep 2023 18:31:03 +0200 (CEST) [thread overview]
Message-ID: <Ne9DqFj--3-9@tuta.io> (raw)
Dear Nouveau developers,
I encountered this problem using Artix Linux:
https://forum.artixlinux.org/index.php/topic,5859
On 2 laptops (Dell M4400 and M4500, Nvidia graphics using Nouveau) which have a VGA port, a Maxim MX11-LCD15 TV with a VGA port stopped working, also another Panasonic TX-26LXD500 TV using VGA. These are older TV's, from the 2000's, I guess the EDID might not be entirely compliant with modern standards. A newish AEC monitor (not TV) did work with the latest kernels so not all VGA connected monitors are affected.
From searching online it seems that there are numerous reports of monitors stopping working with the 6.2 kernel in various distros.
This is the commit where the problem apparently first appears:
https://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-fixes&id=f530bc60a30bee47ff51b7fb71511fdd058b774a
commit f530bc60a30bee47ff51b7fb71511fdd058b774a (HEAD)
Author: Ben Skeggs <bskeggs@redhat.com>
Date: Wed Jun 1 20:46:33 2022 +1000
drm/nouveau/disp: move HDMI config into acquire + infoframe methods
v2:
- fix typo in sorhdmi/g84 struct initialiser (kbuild test robot)
v3:
- less convoluted flow control in nvkm_uoutp_mthd_acquire_tmds() (lyude)
v4:
- we don't support hdmi on original nv50, don't try
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Reviewed-by: Lyude Paul <lyude@redhat.com>
reply other threads:[~2023-09-29 8:42 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=Ne9DqFj--3-9@tuta.io \
--to=stratus@tuta.io \
--cc=nouveau@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.