Seems to be fixed again in 5.11.0-34
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936583
Title:
Fix resume failure on Tongfang GMxZGxx Barebone
To manage notifications about this bug go to:
Offtoppic, but just for reference: Checked the Clevo NS50MU on windows:
There 4k@60Hz is also only possible with YCbCr420 so it's no linux
specific problem, but propably some strange hardware limitation.
So this device defenetly needs this patch and there is no other fix
where 4k@60Hz would run
Ok, turns out it only works on some Intel based laptops. But for them
this is still an improvement so I vote for this patch to be keept, as it
has no downsides for other devices.
e.g. The Clevo NS50MU Barebone with an i7-1165G7 only outputs 4k@30Hz without
this patch, but 4k@60Hz with YCbCr420
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934489
Title:
Make Intel GPUs choose YCbCr420 encoding
Something seems to have broken automatic selection of ycbcr420 (Also in
mainline linux releases).
I need more time to figure out what exactly is causing this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The issue was fixed in focal hwe 5.11.0-26 kernel in proposed, but props
up in hwe 5.11.0-27 again because hwe-27 is directly based on hwe-25 and
not on -26
Very unusual pattern in the kernel log:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=Ubuntu-hwe-5.11-5.11.0-27.29_20.04.1
Yes, this patch alone fixed the problem.
I tested 5.11.0-26 today, which has this patch included and it works now
^^.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936583
Title:
Fix resume
Public bug reported:
The Tongfang PH4TUX1 barebone has occasional display flickering with a
3k eDP display on 5.11 ubuntu kernel, but not on 5.8 ubuntu kernel.
Setting i915.enable_psr=0 as a boot parameter fixes the issue, so my
guess is that this patch missing on 5.11 is causing the regression:
I messed up: The patch is already in 5.11, what I somehow missed when
checking for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936583
Title:
Fix resume failure on Tongfang GMxZGxx Barebone
Public bug reported:
SRU Justification:
Impact:
The Tongfang GMxZGxx Barebone and propably also other new AMD based laptops
fail to resume after suspend, and reboot instead with the 5.11 or earlier
kernel.
Fix:
There is a quirk in newer linux kernel that can easily applied to 5.11 also.
Patchset ported, tested, and sent to kernel-team mailing list
** Description changed:
SRU Justification:
Impact:
On some setups, while the monitor and the GPU support display modes with
pixel clocks of up to 600MHz, the connector might not. This prevents RGB
encoding for 4k60Hz, but
The bug still exists on 5.11.
The Patchset just got merged after the 5.13 mainline release, so in
mainline it will be in 5.14 onwards.
** Description changed:
SRU Justification:
Impact:
On some setups, while the monitor and the GPU support display modes with
pixel clocks of up to
Public bug reported:
SRU Justification:
Impact:
On some setups, while the monitor and the GPU support display modes with pixel
clocks of up to 600MHz, the connector might not. This prevents RGB encoding for
4k60Hz, but YCbCr420 encoding might still be possible. However, which color
mode is
I'm currently resolving the minor merge conflict with ubuntu-5.8 kernel
and then test it
** Description changed:
SRU Justification:
Impact:
On some setups, while the monitor and the GPU support display modes with
pixel clocks of up to 600MHz, the connector might not. This prevents RGB
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
Title:
Make AMD gpus choose YCbCr420 encoding automatically
Testing done:
The proposed kernels are fixing the bug.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
Title:
Make AMD gpus choose YCbCr420 encoding automatically
Tested and works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922759
Title:
SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
To manage notifications about this bug go to:
tl:dr;
- No issue with linux-image-5.8.0-51.57
- Test devices did not work because we accidentially did not install
linux-modules-extra-5.8.0-51-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok I think I found out what happened: When we tested 5.8-51 on the NUC
and the Clevo NH55RZQ we forgot to also update linux-modules-extra (We
just installed the linux-image package).
When we tested the Clevo NL50RU we installed/updated the HWE meta
package which also updated the modules extra
Tested the clevo NL50RU and it works without issues with both 50 and 51.
Also ubuntu 5.11 kernel works on both nuc10 and clevo NH55RZQ.
I have no other device at hand that usses the ALC269_FIXUP_DMIC quirk and the
NUC10 quirk is exclusive for that device.
Both quirks are pretty straight forward
NUC 10 also tested, also doesn't work
Since the clevo and the nuc are completly different platforms with
different quirks i suspect it's not the quirk causing the issue between
50 and 51.
I'm currently installing ubuntu on a different clevo that should already
be working, and let you know my
ubuntu 5.11 kernel will also be tested tomorrow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922759
Title:
SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
To manage notifications about this bug
My colleague tested the Clevo NH55RZQ
However the 5.8.0-51.57 kernel is borked for some reason: Audio setting
is only showing a Dummy device, which is worse then unpatched kernel.
However the mainline 5.12 kernel which uses the exact same quirk works
just fine:
links to wring repo but same in groovy repo:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
groovy.git/tree/sound/pci/hda/patch_realtek.c?h=master-
prep=0f3c49138f90cb367c96f94d68cdbf530869f971#n8155
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
Loking in the code of 5.8.0-51.57 the fixes are there:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
focal.git/tree/sound/pci/hda/patch_realtek.c?h=hwe-5.8=37a31d9d4344b1438a49f8afaabdac3c834364a7#n8155
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
** Description changed:
- On some setups, while the monitor and the gpu support display modes with
- pixel clocks of up to 600MHz, the link encoder might not. This prevents
- YCbCr444 and RGB encoding for 4k60Hz, but YCbCr420 encoding might still be
- possible. However, which color mode is used
Oh I'm sorry I missed that.
I only checked the git for focal hwe-kernel because I thought: hwe-
kernel = kernel of the next release.
I was apperently misstaken on that ^^.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484810/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484815/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484813/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484814/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484812/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484811/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484809/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484808/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484807/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484806/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484805/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484804/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484803/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484802/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484801/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484800/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484798/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922754
Title:
Make
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1922754/+attachment/5484799/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected focal
** Description changed:
On some setups, while the monitor and the gpu support display modes with
pixel clocks of up to 600MHz, the link encoder might not. This prevents
YCbCr444 and RGB encoding for 4k60Hz, but YCbCr420 encoding
I don't have the two devices at hand atm, but the patches should be
pretty streigt forward so the system log might not be required?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added:
"13046370c4d143b629adc1a51659a8a6497fbbe6..73e7161eab5dee98114987239ec9c87fe8034ddb.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+attachment/5484796/+files/13046370c4d143b629adc1a51659a8a6497fbbe6..73e7161eab5dee98114987239ec9c87fe8034ddb.patch
--
You
Public bug reported:
The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin
setup and enable microphones to work correctly when using via the audio
jacks.
Patches that are fixing these problems have already been accepted to
current Linux stable releases:
** Description changed:
On some setups, while the monitor and the gpu support display modes with
pixel clocks of up to 600MHz, the link encoder might not. This prevents
YCbCr444 and RGB encoding for 4k60Hz, but YCbCr420 encoding might still be
possible. However, which color mode is used
Public bug reported:
On some setups, while the monitor and the gpu support display modes with
pixel clocks of up to 600MHz, the link encoder might not. This prevents
YCbCr444 and RGB encoding for 4k60Hz, but YCbCr420 encoding might still be
possible. However, which color mode is used is decided
52 matches
Mail list logo
