Wasn't that commit reverted because it caused other regressions?
IE c4849f88164b13dd141885e28210f599741b304b
I would suggest to check that latest linux-firmware for this platform
still has the issue instead.
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1987670
Title:
Add support for AMD PMF
Status in linux package in
Public bug reported:
Some upcoming platforms support for AMD-PMF.
This will enable ACPI platform profiles and some automatic transitions.
The first 11 patches are queued up for 6.1 and also available in an immutable
branch.
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
As dependency bug 1969091 was covered by v5.15.33 this is really just
two patches, and the more important one is 5.15.y already. The other
one is just messaging: f316ba0a8814f4c91e80a435da3421baf0ddd24c.
# git describe --contains 9e53c25f326604c838d528b430b8e603944b9e28
v5.15.46~190
It's landed
Checked on correct system
$ cat /proc/cpuinfo | grep "model\|family" | head -n 2
cpu family : 23
model : 160
$ dpkg -l | grep linux-firmware
ii linux-firmware
20220329.git681281e4-0ubuntu3.5 all Firmware for Linux kernel
drivers
Ran a few
The kernel patch solution for #1968155 I don't believe will cover "HL-
DT-ST BDDVDRW GGC-H20L".
If you're comfortable building your own kernel to test it you can try to
add a new entry for your drive to replicate the solution for #1968155
(https://lore.kernel.org/linux-
Here is the fix that has been queued up:
https://lore.kernel.org/linux-
ide/20220926183718.480950-1-niklas.cas...@wdc.com/
--
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/1968155
Title:
b60e31bf18a70 ("thunderbolt: Add DP OUT resource when DP tunnel is
discovered")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1983143
Title:
AMD Rembrandt: DP tunneling fails
FYI - one of those commits has reverted in 6.1 due to regressions.
See this commit:
5632e2beaf9d5 ("Revert "PCI: Distribute available resources for root buses,
too"")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in
** Changed in: linux (Ubuntu Focal)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1950062
Title:
Unable to access CPU i2c interfaces
Here is the kernel bug report.
https://bugzilla.kernel.org/show_bug.cgi?id=216460
** Bug watch added: Linux Kernel Bug Tracker #216460
https://bugzilla.kernel.org/show_bug.cgi?id=216460
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=216460
Importance: Unknown
Status: Unknown
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification
** Tags added: verification-done-jammy
--
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/1987670
Title:
Add support for AMD PMF
Status in HWE Next:
New
Status in linux package in
> For linux-firmware, adding the following to debian/remove-
firmware.list creates a deb file without AMD-SEV files:
Presumably amd64-microcode will also need some handholding with
Conflicts/Replaces to make sure that it works on upgrade as it will
probably upgrade before linux-firmware does,
AFAICT it should be in Ubuntu-5.15.0-47.50.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1950062
Title:
Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
Status
Yeah there are positive test results in bug 1978067.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1983143
Title:
AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.17 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Focal)
Status: New => Invalid
** Tags added: stella
** Tags added: originate-from-1980851
**
Great thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1981922
Title:
Upgrade yellow carp DMCUB firmware to fix suspend failure
Status in HWE Next:
New
Status in
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1998106
Title:
Fix AMD-PState driver for Genoa
Would it be possible to bump up to 5.15.83 this cycle instead? Wanting
to see
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y=249011f4c3b8a636f019c9740d5c4356d11031be
land.
--
You received this bug notification because you are a member of Kernel
Packages,
** Bug watch added: Linux Kernel Bug Tracker #216816
https://bugzilla.kernel.org/show_bug.cgi?id=216816
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=216816
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Did you ever end up testing your own patch for that other drive?
--
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/1970136
Title:
Optical drive no longer usable after upgrading to kernel
As an FYI, Kalle is also sending this fix to 6.1-rc with a CC to stable.
So this will eventually drop off the Ubuntu kernels as SAUCE.
https://patchwork.kernel.org/project/linux-
wireless/patch/20221102114803.13485-1-kv...@kernel.org/
--
You received this bug notification because you are a
Just for reference in a quick Google search on my profile for "Adaptec
AHA-284x" my top hit was an OS/2 driver..
--
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/2009759
Title:
Change
It's ancient EISA card, does anything modern still use EISA?
--
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/2009759
Title:
Change default of CONFIG_EISA_VLB_PRIMING
Status in linux
I tested this on a Z13 with following combo:
$ dpkg -l | grep linux-firmware
ii linux-firmware
20220329.git681281e4-0ubuntu3.11all Firmware for Linux kernel
drivers
$ uname -a
Linux Z13-Gen-1 6.1.0-1008-oem #8-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar
** Description changed:
[Impact]
To whom it may concern:
I was experiencing frequent wake-ups from s0i3x on a HP Pro 435 G9
convertible [1] using the Qualcomm FastConnect 6900 Soc [2]. The issue
is related to FW revision
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9
Public bug reported:
Currently the Ubuntu kernels ship with CONFIG_EISA_VLB_PRIMING=y. This
doesn't match the upstream default (n) and this is the help text:
Activate this option if your system contains a Vesa Local
Bus (VLB) card that identify itself as an EISA card (such
Tested kinetic kernel 5.19.0-38.39 and focal kernel 5.15.0-69.76 and
both pass.
** Tags added: verification-done-focal verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/2009759
Title:
Change default of CONFIG_EISA_VLB_PRIMING
Status in
Dev kernel and OEM 6.1 maybe?
--
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/2009759
Title:
Change default of CONFIG_EISA_VLB_PRIMING
Status in linux package in Ubuntu:
Confirmed
OK, here's the patch being submitted upstream that should help this if
it's S/G caused:
https://patchwork.freedesktop.org/patch/532323/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2015297
Title:
Update GPU F/W for DCN 3.1.4 products to fix S0i3 issue
Status in HWE
> Just to give another data point, I've been running 5.19 from hwe-edge
(instead of hwe) for some time but I realized this suspend issue after
updating hwe-edge from 5.19.0.28.29~22.04.6 to 5.19.0.32.33~22.04.9.
I had a try with the latest 5.19 HWE kernel on a Lenovo Z13 I have on
hand (with a
I do think a double check against 6.3-rc4 would be worthwhile with no
parameters set.
The upstream issue is a bit confusing because it has both PSR and S/G
issues conflated.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1
Public bug reported:
[ Impact ]
The current GPU firmware in place for DCN 3.1.4 based products fails to resume
from s2idle on newer BIOSes.
The following GPU F/W stack is confirmed to fix the problem and works
both with the older BIOSes and newer BIOSes:
9ee24ce0 amdgpu: Update SDMA 6.0.1
There are potentially two bugs at play here. One with scatter/gather
and one for PSR. They both manifest really similarly, so let's try with
both disabled.
There is a parameter that is introduced in 6.3 for amdgpu.sg_display.
Can you please explicitly set that to "0" along with the PSR disable
** No longer affects: linux (Ubuntu)
** Changed in: linux-firmware (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1523565
Title:
If it's trending to be caused by PSR (which it sounds like it is), try to
revert this patch:
https://github.com/torvalds/linux/commit/751281c55579f0cb0e56c9797d4663f689909681
> Short, massive flickering while running with parameters
"amdgpu.dcdebugmask=0x10 amdgpu.sg_display=0",
Have a try with
I verified a system that uses this IP version could boot with this
package and OEM 6.1 1008 package.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Just a little extra context for this.
Some systems this manifests as described because they don't use _BTP for
notifying when battery has crossed a critical threshold but instead
notify the OS of every battery level change.
Systems that use _BTP still will have the issue manifest with other ACPI
** Also affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Lunar)
Importance: Undecided
Status: New
--
You received
> Anyway, I still don't get why upgrading the wifi-cards firmware to a
> more recent version fixes the problem.
> Would you mind to elaborate on this a bit more?
When the system is in the hardware sleep state it can be woken up from
either a GPIO or a GPE. Any of those ACPI events I mentioned
The commit is in linux-firmware upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=c7a57ef688f7d99d8338a5d8edddc8836ff0e6de
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
Ah, in that case I would say it shouldn't be a cherry pick. Just pick
the file.
IE We don't need the whole commit for either, just
amdgpu/yellow_carp_dmcub.bin (For RMB) and amdgpu/dcn_3_1_4_dmcub.bin
(for PHX).
--
You received this bug notification because you are a member of Kernel
Packages,
I've verified the PHX jammy update (which jumped up to 0x8001b00) with a
non-problematic panel doesn't cause any additional regressions with
display or suspend on both 6.4-rc1 or with 6.1-OEM 1015.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux-oem-6.1 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Kinetic)
Status: New => Invalid
--
You received this bug notification because you are a member of
60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release
31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release
introduced a regression on 11.0.1/11.0.4, which is why specifically
requested (https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/2024427/comments/16) below
** Tags removed: verification-failed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2024427
Title:
potential S3 issue for amdgpu
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2024774
Title:
AMD Rembrandt / Phoenix PSR-SU related freezes
Status in Linux Firmware:
Confirmed on a Phoenix laptop no longer see the fallback path with 6.1
1016-OEM kernel. marking verified.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Under stress testing it was reported that the system will sometimes fail
to wake from S3.
This firmware version has been run heavily under Q/A on various 6.1.y
kernel and those issues don't occur after taking this runtime firmware
update.
--
You received this bug notification because you are a
> Not entirely sure if this is the exact logging you are looking for,
but this is the result from my testing.
Thanks for having a try.
> ➜ ~ sudo python Downloads/psr.py
> DRI device 0 DMCUB F/W version: 0x043c
> ○ PSR 2 with Y coordinates (eDP 1.4a) [3]
> ○ Sink OUI: Parade
> ○ resv_40f: 01
** Changed in: linux-firmware (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2015297
Title:
Update GPU F/W for DCN 3.1.4
Just to clarify Renjith tested on a Phoenix machine.
Based on Renjith's test result though, this is a fail and an extra change is
needed.
It turns out that this linux-firmware commit should come too:
1c513ec7 ("amdgpu: Update GC 11.0.1 and 11.0.4")
This is because of kernel commit
That's good news. Just today there was a new patch posted that might
help the remaining PSR issue. Can you please apply this on top of
6.4-rc5?
https://patchwork.freedesktop.org/patch/541535/
--
You received this bug notification because you are a member of Kernel
Packages, which is
OK let's look for results with that patch when you have time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2009952
Title:
[amdgpu][psr] Screen flickering/ tearing on
> - I still have an error message in dmesg:
In this issue you actually discovered two independent bugs.
The first was the regression, the second was the UBSAN issue.
* The first fix is what you tested.
* The second fix wasn't picked up yet.
This is the commit that is now landed upstream for the
OEM-6.1 1018 picks up this patch which was accidentally introduced even
though reverted upstream.
- drm/amd/display: edp do not add non-edid timings
This breaks mirror mode. It's already reverted in 6.5 and being
reverted in 6.1.42.
Can you please revert in OEM 6.1 1018 as well?
--
You
Something that I notice in both logs:
/etc/udev/rules.d/70-amdgpu.rules:1 Invalid operator for GROUP.
Where did this file come from and what's in it?
Also; is it possible you're just missing the matching linux-
modules-6.2.0-25-generic/linux-modules-6.2.0-26-generic?
--
You received this bug
Public bug reported:
[ Impact ]
When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU).
After a non-deterministic amount of time the system may hang with a message
like this in the logs:
"[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed
out]"
For reference, current version of linux-firmware
(20220329.git681281e4-0ubuntu3.14) contains following versions:
Rembrandt: 0x422
Phoenix: 0x8000e00
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
I include tasks for Jammy because 6.2-HWE kernel will backport soon and
expose this issue in Jammy.
** Also affects: linux-firmware (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also
Upstream linux-firmware has a tag that includes these firmware
(20230625) so perhaps mantic task can be closed by syncing to that tag.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
mantic has linux-firmware 20230629.gitee91452d-0ubuntu1, closing that
task.
** Changed in: linux-firmware (Ubuntu Mantic)
Status: New => Fix Released
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux (Ubuntu Lunar)
Status: New => Triaged
**
Thanks, I see mantic has migrated as well, closing the mantic task.
** Changed in: linux-firmware (Ubuntu Mantic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
> Tainted: G
In the two upstream bugs it was noted that there was an amdgpu dkms
package in place. I believe that's where this issue likely was. Commit
63a9ab264a8c came in 6.3-rc1 and the commit it fixes was also in 6.3-rc1
(b1a9557a7d00).
So at least one of the issues is probably invalid in
** Also affects: linux-oem-6.1 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.1 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a
** Changed in: linux-oem-6.1 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2011403
Title:
Jammy update: v6.1.1 upstream stable
OK here are the fixes for this identified upstream:
Mantic (6.3+):
* UBSAN issue fixed by
https://gitlab.freedesktop.org/agd5f/linux/-/commit/3a5fb036af0a18436209fbb16e331edd26a07b3d
Kinetic (5.19):
* UBSAN issue fixed by
Public bug reported:
[ Impact ]
* Selecting certain resolutions causes hangs when an AMD GPU is
connected to a display that supports FreeSync
[ Test Plan ]
* Verify display with freesync doesn't hang anymore
[ Where problems could occur ]
* AMD GPU could stop displaying
[ Other Info ]
Here is the request to take it back to stable:
https://lore.kernel.org/stable/20230515150426.2197413-1-alexander.deuc...@amd.com/T/#u
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.1 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux (Ubuntu Kinetic)
Status: Invalid => Incomplete
--
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/2018470
Title:
Linux 5.19 amdgpu: NULL pointer on GCN2 and
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1994068
Title:
Kinetic update: v5.19.9 upstream stable release
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1994076
Title:
Kinetic update: v5.19.14 upstream stable release
This issue has been fixed in later kernels and s2idle is supported now.
Suggest to use LTS 5.15 or LTS 6.1 kernels.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Zesty)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xserver-xorg-video-amdgpu (Ubuntu Xenial)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Xenial)
5.4.243:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=d60f15682a5ce51e8119c1b9ff522494554e33b5
5.15.112:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y=0788273bd0a6bbfb3c65ec77b52ebee504713925
6.1.29:
This commit from 6.4-rc1 fixes the S/G mode issue.
https://github.com/torvalds/linux/commit/08da182175db4c7f80850354849d95f2670e8cd9
It's CC to stable.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
Internal team at AMD has tested an OEM RMB that doesn't need the DP swap
change to check for any potential regression. They tested using OEM
6.5-1014 kernel. This testing well.
Anson will confirm results on the system needing DP swap after he's back
from holiday.
--
You received this bug
Internal team at AMD has tested across a number of different OEM PHX
systems using OEM 6.5-1014 kernel. This is testing well.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
The two missing commits are specified in comment #4.
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1180974eb33ac67903269b71f35a489a2b77e5e9
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/6b91b2ef6f4173099c1434e5d7c552e51814e26e
** Tags added: verification-failed-jammy
I examined the packages and I notice the MT7921 firmware (Which
confusingly goes by MT7961) is updated but "not" the MT7922 firmware.
Based on the above comments and below finding it seems that the MT7921
hardware is fixed with the update but not the MT7922 (which also
confusingly uses the
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: Triaged => Won't Fix
--
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/2036737
Title:
Enable dynamic boost control in ccp kernel
Do you perhaps have the older version in /lib/firmware/updates?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix
Did you put any other files in /lib/firmware? Maybe the output of
$tree /lib/firmware
Would explain what is going on.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Is this happening possibly when there is a resolution change for the
eDP? If so, can you please try the latest linux-6.5.y kernel:
https://kernel.ubuntu.com/mainline/v6.5.13/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
OK thanks for clarifying. Can you please still try latest 6.5.13 and
6.6.6 and see if it happens in either of those?
--
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/2039570
Title:
The patches for this issue are in the original bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042867
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2046504
Title:
*** This bug is a duplicate of bug 2047389 ***
https://bugs.launchpad.net/bugs/2047389
** This bug has been marked a duplicate of bug 2047389
Fix AMDGPU crash on 6.5 kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This is the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573
Here is a commit that fixes the issue by changing default pre-emption
policy since the kernel can't know about your mesa version.
Here's the fix commit ID to backport to fix this issue.
https://github.com/torvalds/linux/commit/d6a57588666301acd9d42d3b00d74240964f07f6
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It's a pretty complicated backport to 6.1. there is a directory rename,
missing quirks that this builds on.
Considering 6.1 OEM will transition to 6.5 OEM eventually it might be
better to only target to 6.5 OEM.
They patches were nominated to 6.6.y already, but 6.5.y is EOL upstream
so it's up
Boot a bad kernel, reboot the system, boot a good kernel.
>From the good kernel:
journalctl -k -b0 > good_kernel.txt
journalctl -k -b-1 > bad_kernel.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Since the PPA failed would you be able to manually build 6.5.13 to see
if it's fixed there?
--
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/2039570
Title:
[amdgpu] Fullscreen in any
** Description changed:
- Some OEM platforms swap DP connections on the Rembrandt-R, which causes
- improper eDP behavior. AMD experimented with reproducing at CRB level to
- come out with a solution
+ [Impact]
+ Some OEM platforms swap DP connections on the Rembrandt-R, which causes
improper
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
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/2036737
Title:
Enable dynamic boost control in ccp kernel driver
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Noble)
Is this going to happen for noble? It should just be kernel config
changes at this point.
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
401 - 500 of 575 matches
Mail list logo
