** Changed in: mutter
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default, until "max
** Changed in: gnome-control-center
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default,
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: hwe-next
Status: New => Fix Released
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Changed in: xorg-server
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default,
This should also fix the problem for some people in Wayland sessions:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1834
It is in mutter release 40.1 and future release 3.38.5.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I just solved my 30bit problem with an Displayport to HDMI adapter[1].
Now the screens operate at 4k 60Hz 24bits in Linux and no more screen
corruption.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I came across this bug because of my problem which I described in
https://askubuntu.com/questions/1314639/weird-graphics-artifacts-
monitor-off-with-ubuntu-20-04-and-nvidia-rtx-5000/1343876#1343876
In my case the Dell monitors tell, they can support 30bit.
I came to the conclusion, that the
Sounds like a plan, if it works. Just patch the kernel to choose a more
sane default.
** Changed in: mutter (Ubuntu)
Status: New => Invalid
** Changed in: mutter (Ubuntu)
Status: Invalid => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop
apparently fixed by the series ending at
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=181567aa9f0d297804f1ea5d3ff4ba4518e05f2c
included in 5.10-rc1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by
** Changed in: oem-priority
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default, until
Full URL:
https://github.com/vsyrjala/linux/tree/dp_downstream_ports_6
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by
Intel GFX dev has a branch that works:
git://github.com/vsyrjala/linux.git dp_downstream_ports_6
Will backport the branch once it hits upstream.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I mean only EDID version 1.4 and later advertises depth, so use that but
default to 8 bpc:
Set bpc to 8.
if ((EDID >= 1.4) && (a depth is advertised in byte 20 bits 6-4)) then
Set bpc to the depth advertised in the EDID.
endif
So for this bug it would stay with bpc=8, because the EDID is only
Hello Denial,
Do you mean if the monitor EDID < 1.4, set max bpc to 8 in kernel directly?
Do I understand it correctly?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
Silly question:
Why not just default to 8 bpc and then only increase it to maximum
10/12/14/16 bpc if byte 20, bits 6-4 say that deep colour is supported
by the monitor?
https://en.wikipedia.org/wiki/Extended_Display_Identification_Data#Structure,_version_1.4
--
You received this bug
... because the EDID this bug is about (comment #23) is version 1.3. So
it would get the default 8 bpc.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on
** Also affects: hwe-next
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by
reply to #39,
yes it's a trade off that we don't either want user get darkscreen when
then randomly plug display port for case like #38 or user get lower bpc on
their working display port.
So far, there seems no solid way to make sure both requirement.
--
You received this bug
Upstream is also working on the same kind of issue:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1391
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on
according to #40 and conversation on mattermost with Kai-Heng.
HWE is planning to add quirk for the faulty dongles so that the dark screen
during boot time[1] can be fixed.
[1] https://gitlab.freedesktop.org/drm/intel/-/issues/1890
--
You received this bug notification because you are a
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1391
https://gitlab.gnome.org/GNOME/mutter/-/issues/1391
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1391
Importance: Unknown
Status: Unknown
--
You received this bug notification because
This is a kernel bug so not sure if it's wise to fix it from
userspace...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by
My concern is that you might be taking functionality (deep/wide colour)
away from people for whom it works.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal
I afraid we can not just trust (EDID_version >= 1.4 &&
EDID_supports_10bit). Because this issue caused by any problematic
component in the middle of pipeline. To ensure the compatibility, better
to just defautly set bpc=8.
Think of one scenario, a speaker get his Ubuntu machine onto stage, plug
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1066
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066
Importance: Unknown
Status: Unknown
--
You received this
** Project changed: xorg-server => gnome-control-center
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default, until
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1108
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108
** Also affects: xorg-server via
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108
Importance: Unknown
Status: Unknown
I guess my only request is that:
if (EDID_version > 1.4 && EDID_supports_10bit) then
don't restrict "max bpc"
endif
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
I guess my only request is that:
if (EDID_version >= 1.4 && EDID_supports_10bit) then
don't restrict "max bpc"
endif
** Also affects: linux via
https://gitlab.freedesktop.org/drm/intel/-/issues/1890
Importance: Unknown
Status: Unknown
--
You received this bug notification
Thanks for understanding.
There's an upstream bug discussing this similar issue, we can follow their
effort there.
https://gitlab.freedesktop.org/drm/intel/-/issues/1890
** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #1890
https://gitlab.freedesktop.org/drm/intel/-/issues/1890
No problem. It's not up to me anyway...
Long term, to get the GUI work done you will need to request
enhancements in both of these projects:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues
https://gitlab.gnome.org/GNOME/mutter/-/issues
Short term, to get the default changed you
I think different from #32.
To adding a GUI configure bpc is a long-term plan.
Before that,the default behavior should be designed to get the best user
experience.
As we all know, there're lot of hardware components on the pipline of display
path(e.g. socket, converter, dongle, cable, monitor)
** Changed in: oem-priority
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default,
** Tags added: originate-from-1887915
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc"
is
Realistically I do not expect this bug to be fixed. Because we don't
want to lower the default from 10bpc when the rest of us are trying to
enable 10bpc in more cases, and adding a GUI to make it configurable is
a multi-month effort because multiple projects would be involved there.
But if you
** Tags added: oem-priority originate-from-1886778 somerville
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default,
** Summary changed:
- Some external 4K monitor is not working properly
+ No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is
lowered to 8
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
38 matches
Mail list logo