When the bug resurfaced, was it still specific to the newer kernels?
** Summary changed:
- Unable to see second monitor
+ Unable to see second monitor in 5.15.0-52 (but 5.15.0-50 works)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Tags added: i915
** Summary changed:
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993532
Title:
Unable to see second monitor
Status in linux package in Ubuntu:
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
...but unlike last time it works when I plug HDMI directly in.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993532
Title:
Unable to see second monitor
Status in linux package in Ubun
This has resurfaced again:
$ grep connect /sys/class/drm/*/status
/sys/class/drm/card0-DP-1/status:disconnected
/sys/class/drm/card0-DP-2/status:disconnected
/sys/class/drm/card0-eDP-1/status:connected
/sys/class/drm/card0-HDMI-A-1/status:disconnected
/sys/class/drm/card0-HDMI-A-2/status:disconnec
$ uname -a
Linux tangaroa 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux
$ grep connect /sys/class/drm/*/status
/sys/class/drm/card0-DP-1/status:connected
/sys/class/drm/card0-DP-2/status:disconnected
/sys/class/drm/card0-eDP-1/status:connected
/sys/cl
oh, this is interesting. I booted with the HDMI directly connected into
-52, and it worked.
$ grep connect /sys/class/drm/*/status
/sys/class/drm/card0-DP-1/status:disconnected
/sys/class/drm/card0-DP-2/status:disconnected
/sys/class/drm/card0-eDP-1/status:connected
/sys/class/drm/card0-HDMI-A-1/s
Ah, the displaylink stuff is perhaps a red herring. Some of our office
configurations use that so I have the drivers installed to work with it,
however it's not in use in this case. Note that the monitor detection
also fails when plugged directly into the laptop's HDMI port.
These are the connecte
Thanks for the bug report.
I am slightly concerned the attached kernel log mentions "evdi" which is
used for USB-connected displays (via DisplayLink chips inside dongles).
So long as you have USB-C ports, evdi/DisplayLink should not be
necessary. So I suggest either:
(a) Get some native USB-C t
9 matches
Mail list logo
