[
Date Prev
][
Date Next
] [
Thread Prev
][
Thread Next
] [
Date Index
] [
Thread Index
]
Bug#904884:
To
:
904884@bugs.debian.org
Subject
: Bug#904884:
From
: Jaoued Zahraoui <
jzahraoui@gmail.com
>
Date
: Mon, 22 Oct 2018 21:29:00 +0200
Message-id
: <
[🔎]
CAD-gMMzAEZ3KO5QMVs5=dghsLJWbVYJamtAGGgdy4qBJtad93g@mail.gmail.com
>
Reply-to
: Jaoued Zahraoui <
jzahraoui@gmail.com
>,
904884@bugs.debian.org
References
: <153284966597.11019.9087931751631493490.reportbug@kattalyser.lan>
Having the exctly same problem. I have an AMD 2400G.
I think that the 2160p@60Hz have to be in
YCbCr 4:2:0 or it will be over the max clock (300MHz)
Reply to:
debian-x@lists.debian.org
Jaoued Zahraoui (on-list)
Jaoued Zahraoui (off-list)
Prev by Date:
wayland_1.16.0-1~bpo9+1_source.changes ACCEPTED into stretch-backports
Next by Date:
Bug#911647: xserver-xorg-video-nouveau: viewing a pdf on github site through chrome corrupts chrome's nouveau context resulting in repeated "fb: trapped read at ..." errors
Previous by thread:
wayland_1.16.0-1~bpo9+1_source.changes ACCEPTED into stretch-backports
Next by thread:
Bug#911647: xserver-xorg-video-nouveau: viewing a pdf on github site through chrome corrupts chrome's nouveau context resulting in repeated "fb: trapped read at ..." errors
Index(es):
Date
Thread