[Bug 2066345] Re: Lenovo T14 Gen3 AMD laptop lid suspend freezes system

2024-05-22 Thread Mario Limonciello
This should be a duplicate of 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2064595
The fix is 
https://github.com/torvalds/linux/commit/ca299b4512d4b4f516732a48ce9aa19d91f4473e

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066345

Title:
  Lenovo T14 Gen3 AMD laptop lid suspend freezes system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2066345/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065838] Re: System crash on resume from sleep

2024-05-22 Thread Mario Limonciello
Do you have secure boot enabled?  if so, turn it off and hopefully the
kernel you built should be bootadble.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065838

Title:
  System crash on resume from sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065838/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063002] Re: Add support for DCN 3.5

2024-05-21 Thread Mario Limonciello
As the firmware is on it's own stable and by the time this hardware is
in market that kernel fix should be picked up adding verification done
tag.

** Tags added: verification-done-noble

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063002

Title:
  Add support for DCN 3.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2063002/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063002] Re: Add support for DCN 3.5

2024-05-21 Thread Mario Limonciello
Internal team tested this SRU against current generic and OEM kernel and
it fails on both because they're missing the fix for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2066233.

After adding in that fix it works.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063002

Title:
  Add support for DCN 3.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2063002/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065839] Re: UBSAN: array-index-out-of-bounds

2024-05-21 Thread Mario Limonciello
** Changed in: linux (Ubuntu)
   Status: New => Invalid

** No longer affects: linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065839

Title:
  UBSAN: array-index-out-of-bounds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2065839/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065838] Re: System crash on resume from sleep

2024-05-20 Thread Mario Limonciello
Save the below as a patch file and then apply using "patch -p1 < FILE".
Build your kernel and see if it has helped.

diff --git a/drivers/acpi/acpica/exregion.c b/drivers/acpi/acpica/exregion.c
index 8907b8bf4267..ca060ec6936e 100644
--- a/drivers/acpi/acpica/exregion.c
+++ b/drivers/acpi/acpica/exregion.c
@@ -44,7 +44,6 @@ acpi_ex_system_memory_space_handler(u32 function,
struct acpi_mem_mapping *mm = mem_info->cur_mm;
u32 length;
acpi_size map_length;
-   acpi_size page_boundary_map_length;
 #ifdef ACPI_MISALIGNMENT_NOT_SUPPORTED
u32 remainder;
 #endif
@@ -138,25 +137,8 @@ acpi_ex_system_memory_space_handler(u32 function,
map_length = (acpi_size)
((mem_info->address + mem_info->length) - address);
 
-   /*
-* If mapping the entire remaining portion of the region will 
cross
-* a page boundary, just map up to the page boundary, do not 
cross.
-* On some systems, crossing a page boundary while mapping 
regions
-* can cause warnings if the pages have different attributes
-* due to resource management.
-*
-* This has the added benefit of constraining a single mapping 
to
-* one page, which is similar to the original code that used a 
4k
-* maximum window.
-*/
-   page_boundary_map_length = (acpi_size)
-   (ACPI_ROUND_UP(address, ACPI_DEFAULT_PAGE_SIZE) - address);
-   if (page_boundary_map_length == 0) {
-   page_boundary_map_length = ACPI_DEFAULT_PAGE_SIZE;
-   }
-
-   if (map_length > page_boundary_map_length) {
-   map_length = page_boundary_map_length;
+   if (map_length > ACPI_DEFAULT_PAGE_SIZE) {
+   map_length = ACPI_DEFAULT_PAGE_SIZE;
}
 
/* Create a new mapping starting at the address given */
-- 
2.34.1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065838

Title:
  System crash on resume from sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065838/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065838] Re: System crash on resume from sleep

2024-05-19 Thread Mario Limonciello
Yes since you didn't clone using git you can't use git revert.

Once you can successfully build and test that kernel I'll post you a
revert patch' with explanation how to use it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065838

Title:
  System crash on resume from sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065838/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065838] Re: System crash on resume from sleep

2024-05-19 Thread Mario Limonciello
Yeah I know they're different symptoms but the reason for that revert might 
have a similar root cause.
I'm saying this because I've got a different system that fails to boot up that 
reverting that helps.

In terms of specific instructions, I'd start with this:

https://itsfoss.com/compile-linux-kernel/

Once you can get that compiling on your own I can help you with a
applying a revert patch to see if it helps.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065838

Title:
  System crash on resume from sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065838/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065838] Re: System crash on resume from sleep

2024-05-18 Thread Mario Limonciello
As a random guess; could this be the same as
https://bugzilla.kernel.org/show_bug.cgi?id=218849?

Try reverting d410ee5109a1 ("ACPICA: avoid "Info: mapping multiple BARs.
Your kernel is fine."")


** Bug watch added: Linux Kernel Bug Tracker #218849
   https://bugzilla.kernel.org/show_bug.cgi?id=218849

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065838

Title:
  System crash on resume from sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065838/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065948] Re: fwupdmgr enable/disable-remote auto-complete is buggy

2024-05-17 Thread Mario Limonciello
Fixed upstream.
https://github.com/fwupd/fwupd/pull/7264

** Changed in: fwupd (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065948

Title:
  fwupdmgr enable/disable-remote auto-complete is buggy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2065948/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065874] Re: Can't update firmware on TPM-backed FDE systems

2024-05-16 Thread Mario Limonciello
This is the original bug for deb fwupd: 
https://github.com/canonical/ubuntu-desktop-installer/issues/2371
This is the original bug for snap fwupd: 
https://github.com/fwupd/fwupd/issues/6264

The problem is that fwupd (both deb and snap) don't understand the
layout that TPM FDE uses.

As mentioned in https://github.com/canonical/ubuntu-desktop-
installer/issues/2371#issue-1940392263 about the deb problem:

> fwupd is not aware of this layout.
In order for a firmware update to work, fwupd expects to be able to create a 
new NVRAM boot entry using shim to chainload fwupdx64.efi.

As mentioned in
https://github.com/fwupd/fwupd/issues/6264#issuecomment-1764898120 about
the snap problem:

> My take on this issue is that it's because the Ubuntu 23.10 FDE mounts
stuff in a weird location. The ESP is at /run/mnt which isn't something
that the fwupd snap interface understands. It fully expects it to be in
/boot/efi.


** Also affects: ubuntu-desktop-provision
   Importance: Undecided
   Status: New

** Changed in: fwupd (Ubuntu)
   Status: New => Triaged

** Bug watch added: github.com/canonical/ubuntu-desktop-installer/issues #2371
   https://github.com/canonical/ubuntu-desktop-installer/issues/2371

** Bug watch added: github.com/fwupd/fwupd/issues #6264
   https://github.com/fwupd/fwupd/issues/6264

** Also affects: snapd
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065874

Title:
  Can't update firmware on TPM-backed FDE systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2065874/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942616] Re: Settings Power says high hardware temperature

2024-05-12 Thread Mario Limonciello
It's saying the same thing the GUI does.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942616

Title:
  Settings Power says high hardware temperature

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1942616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942616] Re: Settings Power says high hardware temperature

2024-05-12 Thread Mario Limonciello
How about the command line tool (powerprofilesctl)?  Can you switch
using that?  If it really is a pure GCC bug then you can file it here:
https://launchpad.net/ubuntu/+source/gnome-control-center for Ubuntu and
here: https://gitlab.gnome.org/GNOME/gnome-control-center for upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942616

Title:
  Settings Power says high hardware temperature

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1942616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942616] Re: Settings Power says high hardware temperature

2024-05-12 Thread Mario Limonciello
You can file it here:

https://bugzilla.kernel.org/

Mention your reproduction using a mainline kernel and add your logs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942616

Title:
  Settings Power says high hardware temperature

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1942616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942616] Re: Settings Power says high hardware temperature

2024-05-11 Thread Mario Limonciello
This sure sounds like an intel-pstate bug.  If you can reproduce it with
the latest mainline kernel you should file a bug with the intel-pstate
maintainers.

You can find some kernel binaries for mainline kernel here:
https://kernel.ubuntu.com/mainline/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942616

Title:
  Settings Power says high hardware temperature

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1942616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063002] Re: Add support for DCN 3.5

2024-05-06 Thread Mario Limonciello
This is certainly a false negative.  This firmware only affects DCN 3.5
which isn't available for arm64 or armhf.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063002

Title:
  Add support for DCN 3.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2063002/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update

2024-05-06 Thread Mario Limonciello
I just tested on a Phoenix based laptop and tested video playback on
OEM-6.5 (1022) with VP9 content in mpv and things look good to me.

** Tags added: verification-done-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058830

Title:
  vp9 hw decode broken on modern AMD apus, needs amdgpu update

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2058830/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064815] Re: Always black screen on first reboot after fresh install 24.04, Intel and AMD GPU

2024-05-05 Thread Mario Limonciello
*** This bug is a duplicate of bug 2063143 ***
https://bugs.launchpad.net/bugs/2063143

** This bug has been marked a duplicate of bug 2063143
   Frequent boot to black display

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064815

Title:
  Always black screen on first reboot after fresh install 24.04, Intel
  and AMD GPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064815/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063877] Re: Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU with "quiet splash" (Grub)

2024-05-05 Thread Mario Limonciello
*** This bug is a duplicate of bug 2063143 ***
https://bugs.launchpad.net/bugs/2063143

** This bug is no longer a duplicate of bug 2064815
   Always black screen on first reboot after fresh install 24.04, Intel and AMD 
GPU
** This bug has been marked a duplicate of bug 2063143
   Frequent boot to black display

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063877

Title:
  Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU with
  "quiet splash" (Grub)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2063877/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063143] Re: Frequent boot to black display

2024-05-05 Thread Mario Limonciello
The issue here is the same one that happened in gdm last year where the
startup would race with the load of DRM graphics drivers.

GDM fixed it by essentially running the equivalent of 'udevadm settle'.
The same kind of fix needs to be ported to sddm or systemd needs to be
modified to not emit CanGraphical until DRM graphics drivers are fully
loaded.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063143

Title:
  Frequent boot to black display

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/2063143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2008958] Re: please backport 0.21 to jammy

2024-05-04 Thread Mario Limonciello
Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2008958

Title:
  please backport 0.21 to jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2008958/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2008958] Re: please backport 0.21 to jammy

2024-05-03 Thread Mario Limonciello
Thanks for testing!  By chance do either of those have batteries?  Could
you test with AC unplugged too?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2008958

Title:
  please backport 0.21 to jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2008958/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2008958] Re: please backport 0.21 to jammy

2024-04-28 Thread Mario Limonciello
I've tested the jammy upload against two AMD Phoenix laptops and
everything is working as I would expect.

However; I don't think it's appropriate to add the verification-done-
jammy tag until we have some information from people on Intel machines
to ensure we didn't cause any unintended side effects.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2008958

Title:
  please backport 0.21 to jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2008958/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064023] Re: Installer should detect small ESP in a dual boot

2024-04-28 Thread Mario Limonciello
And so it's clear how this size is determined by fwupd it's based on the
size of the payload the system will be using (IE the SPI size):

https://github.com/fwupd/fwupd/blob/9713cead62e79da26d4c5637dd9682b21a9f0b21/plugins/uefi-
capsule/fu-uefi-device.c#L635

The size is doubled because often the firmware updater will make a
backup of the SPI to the ESP or will extract the payload while updating.

I think a reasonable default would be to ensure that there is 128MB of
free space available to cover up to a 64Mb SPI part and a backup.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064023

Title:
  Installer should detect small ESP in a dual boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2064023/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064023] [NEW] Installer should detect small ESP in a dual boot

2024-04-28 Thread Mario Limonciello
Public bug reported:

If someone sets up Windows before Ubuntu, Windows will create an EFI
system partition that gets reused by Ubuntu.

This is generally fine, but a major problem is that the EFI system
partition is also where firmware updates are staged during a BIOS
update.

If the ESP is too small, then the update won't be able to run.  The
command line fwupdmgr tool will show this type of message:

/boot/efi does not have sufficient space, required 93.2 MB, got 66.8 MB

This is a situation that should be handled at install time.  If the ESP
is too small to support updates later it should be resized or a new one
created for Ubuntu to use.

** Affects: subiquity
 Importance: Undecided
 Status: New

** Affects: fwupd (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Also affects: fwupd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: fwupd (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064023

Title:
  Installer should detect small ESP in a dual boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2064023/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059215] Re: HDMI Display Not detected: AMD Ryzen 5 7530U/LENOVO IdeaPad Flex 5 14ABR8

2024-04-27 Thread Mario Limonciello
** Changed in: linux-firmware (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059215

Title:
  HDMI Display Not detected: AMD Ryzen 5 7530U/LENOVO IdeaPad Flex 5
  14ABR8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2059215/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063143] Re: Frequent boot to black display

2024-04-24 Thread Mario Limonciello
For the plymouth part I think the suggestion above "plymouth.use-
simpledrm" makes sense.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063143

Title:
  Frequent boot to black display

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1869655] Re: Boot animations start too late to be useful

2024-04-24 Thread Mario Limonciello
> No longer in progress. You can get to 100% fixed by adding kernel
parameter 'plymouth.use-simpledrm' but I'm not totally sure that's
something everyone will want.

The main reasons that can be problematic are rotation right?  I wonder
if the right way to go about it is a heuristic within plymouth to decide
whether it can/should output.  For example if there are no rotation
sensors on the machine, or by looking at the orientation on them?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869655

Title:
  Boot animations start too late to be useful

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/1869655/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063002] Re: Add support for DCN 3.5

2024-04-23 Thread Mario Limonciello
** Description changed:

- Products with DCN 3.5 need linux-firmware to be added for noble.
- Matching kernel support is already in kernel 6.8.
+ [Impact]
+ Products with DCN 3.5 need linux-firmware to be added for noble.  Matching 
kernel support is already in kernel 6.8.
  
+ Without this firmware amdgpu won't bind.
+ 
+ [Test Plan]
+ Boot system and ensure accelerated graphics works.
+ 
+ [Where problems could occur]
+ This firmware is only loaded on hardware with DCN 3.5, VPE 6.1, VCN 4.0.5, 
SDMA 6.1.0, GC 11.5.0, or PSP 14.0.0.
+ 
+ [Other info]
+ Here are commit IDs:
  6bfdacdd amdgpu: add DMCUB 3.5 firmware
  cb59bf73 amdgpu: add VPE 6.1.0 firmware
  3ca35ef5 amdgpu: add VCN 4.0.5 firmware
  9a3a6c61 amdgpu: add UMSCH 4.0.0 firmware
  62cc1372 amdgpu: add SDMA 6.1.0 firmware
  b455dd24 amdgpu: add PSP 14.0.0  firmware
  30c1adcb amdgpu: add GC 11.5.0 firmware

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063002

Title:
  Add support for DCN 3.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2063002/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063002] [NEW] Add support for DCN 3.5

2024-04-20 Thread Mario Limonciello
Public bug reported:

Products with DCN 3.5 need linux-firmware to be added for noble.
Matching kernel support is already in kernel 6.8.

6bfdacdd amdgpu: add DMCUB 3.5 firmware
cb59bf73 amdgpu: add VPE 6.1.0 firmware
3ca35ef5 amdgpu: add VCN 4.0.5 firmware
9a3a6c61 amdgpu: add UMSCH 4.0.0 firmware
62cc1372 amdgpu: add SDMA 6.1.0 firmware
b455dd24 amdgpu: add PSP 14.0.0  firmware
30c1adcb amdgpu: add GC 11.5.0 firmware

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-firmware (Ubuntu Noble)
 Importance: Undecided
 Status: New


** Tags: originate-from-2063001

** Also affects: linux-firmware (Ubuntu Noble)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063002

Title:
  Add support for DCN 3.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2063002/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062412] Re: No input through internal microphone (Ryzen 6000)

2024-04-20 Thread Mario Limonciello
There is a second commit with a similar problem and really the one I
should have linked; this one is much more severe.

Here is that fix:

https://github.com/torvalds/linux/commit/37bee1855d0e3b6dbeb8de71895f6f68cad137be

It also came into 6.8.3.

3e52444ed190 ("ASoC: amd: yc: Revert "add new YC platform variant (0x63)
support"")

Maybe you can try some of the mainline PPA builds to confirm they picked up the 
fix.
https://kernel.ubuntu.com/mainline/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062412

Title:
  No input through internal microphone (Ryzen 6000)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062412] Re: No input through internal microphone (Ryzen 6000)

2024-04-20 Thread Mario Limonciello
The problem is that the "Pink Sardine" (Phoenix) laptops were being
applied to the "Yellow Carp" (Rembrandt) driver.  This is improper
behavior and will cause other problems even if it fixed the immediate
microphone issue.

The Phoenix Lenovo laptops are supposed to have something in the ACPI
tables that makes sure they bind properly to the Pink Sardine driver,
shouldn't need quirks.

You *might* be able to workaround the issue until Ubuntu issues a fix by
blacklisting snd_pci_acp6x.  A Phoenix laptop should be loading
snd_pci_ps.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062412

Title:
  No input through internal microphone (Ryzen 6000)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062412] Re: No input through internal microphone (Ryzen 6000)

2024-04-19 Thread Mario Limonciello
This is the upstream solution:

https://github.com/torvalds/linux/commit/861b3415e4dee06cc00cd1754808a7827b9105bf

Here is the commit from 6.8.3:

b44a34f581b0 ("ASoC: amd: yc: Revert "Fix non-functional mic on Lenovo
21J2"")

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062412

Title:
  No input through internal microphone (Ryzen 6000)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2008699] Re: fwupd-refresh.service always fails after hibernate

2024-04-16 Thread Mario Limonciello
I've uploaded a 1.9.16 fwupd and 0.3.18 libxmlb (build-dependency for
fwpud 1.9.16) to the archive for an SRU team member to review.  It
should fall under
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages

I've got build logs and a diff of the uploads posted at this PPA as well:
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages

** Changed in: fwupd (Ubuntu Kinetic)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2008699

Title:
  fwupd-refresh.service always fails after hibernate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2008699/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2028548] Re: fwupd too old to get and install releases for UEFI dbx

2024-04-16 Thread Mario Limonciello
I've uploaded a 1.9.16 fwupd and 0.3.18 libxmlb (build-dependency for
fwpud 1.9.16) to the archive for an SRU team member to review.  It
should fall under
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages

I've got build logs and a diff of the uploads posted at this PPA as well:
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2028548

Title:
  fwupd too old to get and install releases for UEFI dbx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2028548/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056548] Re: fwupd metadata bug due to outdated version in Ubuntu 22.04 repositories

2024-04-16 Thread Mario Limonciello
I've uploaded a 1.9.16 fwupd and 0.3.18 libxmlb (build-dependency for
fwpud 1.9.16) to the archive for an SRU team member to review.  It
should fall under
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages

I've got build logs and a diff of the uploads posted at this PPA as well:
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages

FYI - this does NOT cover focal.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056548

Title:
  fwupd metadata bug due to outdated version in Ubuntu 22.04
  repositories

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2056548/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1979963] Re: Upgrade fwupd to 1.8.3 in jammy to support HP Thunderbolt Dock G4

2024-04-16 Thread Mario Limonciello
I've uploaded a 1.9.16 fwupd and 0.3.18 libxmlb (build-dependency for
fwpud 1.9.16) to the archive for an SRU team member to review.  It
should fall under
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages

I've got build logs and a diff of the uploads posted at this PPA as well:
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1979963

Title:
  Upgrade fwupd to 1.8.3 in jammy to support HP Thunderbolt Dock G4

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1979963/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060197] Re: [FFe] [HWE] fwupd-efi 1.6 and gnu-efi 3.0.18

2024-04-15 Thread Mario Limonciello
I suggest redoing the diff to fwupd-efi 1.6.  It "basically" is the same
as 1.5 but drops all the debian patches that were upstreamed.

** Summary changed:

- [FFe] [HWE] fwupd-efi 1.5 and gnu-efi 3.0.18
+ [FFe] [HWE] fwupd-efi 1.6 and gnu-efi 3.0.18

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060197

Title:
  [FFe] [HWE] fwupd-efi 1.6 and gnu-efi 3.0.18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd-efi/+bug/2060197/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061708] Re: Yubikey stopped working after noble upgrade

2024-04-15 Thread Mario Limonciello
According to the upstream bug, this appears to be a new intended
behavior with newer gnupg2:

https://dev.gnupg.org/T6871

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061708

Title:
  Yubikey stopped working after noble upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061708] Re: Yubikey stopped working after noble upgrade

2024-04-15 Thread Mario Limonciello
I managed to get it working as a user by manually starting pcscd.service
and with the following to force scdaemon to use it.

# cat ~/.gnupg/scdaemon.conf 
card-timeout 5
disable-ccid

To me this seems to be a regression in behavior from 2.2.27-3ubuntu2.1
to 2.4.4-2ubuntu17.

** Bug watch added: 
gitlab.archlinux.org/archlinux/packaging/packages/gnupg/-/issues #4
   https://gitlab.archlinux.org/archlinux/packaging/packages/gnupg/-/issues/4

** Also affects: archlinux-lp via
   https://gitlab.archlinux.org/archlinux/packaging/packages/gnupg/-/issues/4
   Importance: Unknown
   Status: Unknown

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061708

Title:
  Yubikey stopped working after noble upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061708] [NEW] Yubikey stopped working after noble upgrade

2024-04-15 Thread Mario Limonciello
Public bug reported:

In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
since upgrading to Noble I get the following trying to access it.

$ gpg --card-status
gpg: selecting card failed: No such device 
gpg: OpenPGP card not available: No such device

If I run this as root it works:

$ sudo gpg --card-status
Reader ...: 1050:0407:X:0
Application ID ...: D27600012401000609082616
Application type .: OpenPGP
Version ..: 2.1
Manufacturer .: Yubico
Serial number : 
Name of cardholder: [not set]
Language prefs ...: [not set]
Salutation ...: 
URL of public key : [not set]
Login data ...: [not set]
Signature PIN : not forced
Key attributes ...: rsa4096 rsa4096 rsa2048
Max. PIN lengths .: 127 127 127
PIN retry counter : 10 0 10
Signature counter : 1172
UIF setting ..: Sign=off Decrypt=off Auth=off
Signature key : 
  created : 
Encryption key: 
  created : 
Authentication key: [none]
General key info..: [none]

If I manually run pcscd.service then it stops working both as root and a
user.

$ sudo pkill -9 scdaemon
$ sudo systemctl start pcscd.service
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
$ sudo gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device

It might be worth mentioning I'm accessing the machine over SSH, so I
also did experiment with a polkit rule like this:

polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_card" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_pcsc" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});

Added into /etc/polkit-1/rules.d/99-pcscd.rules and then reloading
polkit.service in case this was a polkit issue, but this didn't do
anything.


Versions in noble:
pcscd: 2.0.3-1build1
libpcslite1: 2.0.3-1build1
gnupg: 2.4.4-2ubuntu17
scdaemon: 2.4.4-2ubuntu17

** Affects: archlinux-lp
 Importance: Unknown
 Status: Unknown

** Affects: gnupg2 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: gnupg (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: gnupg (Ubuntu) => gnupg2 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061708

Title:
  Yubikey stopped working after noble upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1899036] Re: failed to build silo: failed to compile /usr/share/fwupd/quirks.d/tpm.quirk

2024-04-11 Thread Mario Limonciello
** Changed in: libxmlb (Ubuntu)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899036

Title:
  failed to build silo: failed to compile
  /usr/share/fwupd/quirks.d/tpm.quirk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1899036/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2039926] Re: Error UBSAN: array-index-out-of-bounds amdgpu (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)

2024-04-09 Thread Mario Limonciello
Variable sized arrays have fallen out of fashion.

There are various patches like that which fix this issue every time it
crops up.

If you can still reproduce on the latest 6.9-rc kernels you should
report a bug upstream to get the remaining cases fixed. Or if you feel
comfortable you can write a patch for any remaining cases you hit. As
you can see it's a trivial fix.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039926

Title:
  Error UBSAN: array-index-out-of-bounds amdgpu
  (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039926/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2039926] Re: Error UBSAN: array-index-out-of-bounds amdgpu (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)

2024-04-09 Thread Mario Limonciello
https://patchwork.freedesktop.org/patch/588305/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039926

Title:
  Error UBSAN: array-index-out-of-bounds amdgpu
  (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039926/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2008958] Re: please backport 0.21 to jammy

2024-04-09 Thread Mario Limonciello
** Description changed:

  [ Impact ]
  
  power-profiles-daemon has the ability to make drastic improvements to
  the power consumption of machines.  This increases the likelihood of
  them passing energy certifications such as Energy Star.
  
  On AMD laptops the following improvements are made:
  * Tune the platform cTDP using the ACPI platform profile drivers.
  * Tune the CPU using the amd-pstate EPP driver (kernel 6.5 or newer)
  * Tune the backlight using AMD ABM (kernel 6.8 or newer)
  * Tune the EPP dynamically based on AC vs battery
  On Intel laptops the following improvements are made:
  * Tune the CPU using the intel-pstate EPP/EPB driver
  * Tune the EPP dynamically based on AC vs battery
  
  As Ubuntu 22.04 has kernel 6.5 and will later get kernel 6.8, many of
  the improvements specifically for AMD laptops can apply.
  
  [ Test Plan ]
  
  Check for visual "performance issues" on battery using a web browser.
  Verify correct EPP targets are selected (balance_power on battery 
balance_performance on AC).
  Verify that changing to power-saver and performance profiles work properly.
- 
- The below significant bugfixes are implemented, which would enable more
- power & energy efficient modes on our supported laptops, as well as
- enable for the kernel default to change.
  
  [ Where problems could occur ]
  
  There is a very thorough integration test suite distributed with power-
  profiles-daemon.  This covers combinations of kernels and hardware that
  are seen in Ubuntu.
  
  It is reported upstream that some "old" Intel systems don't handle
  balance_power effectively and can cause skipped frames.  This should be
  looked for explicitly when testing.
  
  It is possible that some users would prefer the increased performance
  instead of efficiency that will be available on a laptop in battery
  mode.  They will need to manually change to performance mode to get that
  performance.
  
  [ Other info ]
  
  Frame.work has been suggesting to their AMD laptop users to use a
  backported release on this PPA
  https://launchpad.net/~superm1/+archive/ubuntu/ppd since Framework 13
  AMD and Framework 16 AMD launched.  There have been no reports of bugs
  on the release on this PPA.
  
  Full upstream changelog is below.
  
  0.21
  
  Since this release power-profiles-daemon is battery-state aware and some 
drivers
  use a more power efficient state when using the balanced profile on battery.
  In particular both the AMD and Intel P-State drivers will use the
  balance_power EPP profile, while for Intel one we also set the energy
  performance bias to 8 (instead of 6).
  
  This release also contains various fixes for the powerprofilesctl command line
  tool when using the launch or version commands.
  The tool is now better documented as we generate a manual page for it (if
  python3-argparse is installed) and bash completions. We're even generating the
  ZSH completions, but the install path must be provided.
  
  The daemon command line interface has been improved for debugging, so use
  --help-debug for further information.
  
  The systemd service lockdown settings have been restricted even more.
  
  Various code optimizations.
  
  0.20
  
  
  This release adds support for multiple power-profiles-daemon drivers to
  load simultaneously.  This notably allows both CPU based control with
  amd-pstate or intel-pstate as well as ACPI platform profile based control.
  
  This release also adds support for the amdgpu panel power savings which uses
  dedicated hardware in systems with integrated Radeon graphics to decrease 
panel
  power consumption when the system is on battery.
  
  0.13
  
  
  This release adds support for the AMD P-State driver that's been added to the
  6.3 Linux kernel. This release also fixes mismatched profiles on some HP
  laptops and some miscellaneous bug fixes.
  
  0.12
  
  
  This release adds support for the Intel "Energy Performance Bias" feature, 
which
  can be used on hardware that doesn't have a platform_profile or doesn't 
support
  HWP. It will also be used to eke out a bit more performance, or power, on 
systems
  which already supported HWP.
  
  More information is available in the README.
  
  0.11.1
  --
  
  This release stops power-profiles-daemon from modifying the cpufreq driver 
when
  driver when the user/administrator has chosen to disable the Intel P-State 
scaling
  governor (eg. forcing a passive operation mode).
  
  More information is available in the README.
  
  0.11
  
  
  This release fixes problems on Intel machines when the CPUs didn't support 
turbo at
  all, or the performance scaling governor was built as default in the kernel.
  
  It also adds better end-user documentation, fixes in the command-line tool to 
not
  cause bug report tools to popup on not-uncommon errors, and a bug fix for 
running
  on some systems with controllable charge speeds.

-- 
You received this bug notification because you are 

[Bug 2008958] Re: please backport 0.21 to jammy

2024-04-09 Thread Mario Limonciello
I've updated the description to the SRU template.  I do feel that this
meets the "other safe cases" section.


** Description changed:

+ [ Impact ]
+ 
+ power-profiles-daemon has the ability to make drastic improvements to
+ the power consumption of machines.  This increases the likelihood of
+ them passing energy certifications such as Energy Star.
+ 
+ On AMD laptops the following improvements are made:
+ * Tune the platform cTDP using the ACPI platform profile drivers.
+ * Tune the CPU using the amd-pstate EPP driver (kernel 6.5 or newer)
+ * Tune the backlight using AMD ABM (kernel 6.8 or newer)
+ * Tune the EPP dynamically based on AC vs battery
+ On Intel laptops the following improvements are made:
+ * Tune the CPU using the intel-pstate EPP/EPB driver
+ * Tune the EPP dynamically based on AC vs battery
+ 
+ As Ubuntu 22.04 has kernel 6.5 and will later get kernel 6.8, many of
+ the improvements specifically for AMD laptops can apply.
+ 
+ [ Test Plan ]
+ 
+ Check for visual "performance issues" on battery using a web browser.
+ Verify correct EPP targets are selected (balance_power on battery 
balance_performance on AC).
+ Verify that changing to power-saver and performance profiles work properly.
+ 
  The below significant bugfixes are implemented, which would enable more
  power & energy efficient modes on our supported laptops, as well as
  enable for the kernel default to change.
+ 
+ [ Where problems could occur ]
+ 
+ There is a very thorough integration test suite distributed with power-
+ profiles-daemon.  This covers combinations of kernels and hardware that
+ are seen in Ubuntu.
+ 
+ It is reported upstream that some Intel systems don't handle
+ balance_power effectively and can cause skipped frames.  This should be
+ looked for explicitly when testing.
+ 
+ It is possible that some users would prefer the increased performance
+ instead of efficiency that will be available on a laptop in battery
+ mode.  They will need to manually change to performance mode to get that
+ performance.
+ 
+ [ Other info ]
+ 
+ Frame.work has been suggesting to their AMD laptop users to use a
+ backported release on this PPA
+ https://launchpad.net/~superm1/+archive/ubuntu/ppd since Framework 13
+ AMD and Framework 16 AMD launched.  There have been no reports of bugs
+ on the release on this PPA.
+ 
+ Full upstream changelog is below.
  
  0.21
  
  Since this release power-profiles-daemon is battery-state aware and some 
drivers
  use a more power efficient state when using the balanced profile on battery.
  In particular both the AMD and Intel P-State drivers will use the
  balance_power EPP profile, while for Intel one we also set the energy
  performance bias to 8 (instead of 6).
  
  This release also contains various fixes for the powerprofilesctl command line
  tool when using the launch or version commands.
  The tool is now better documented as we generate a manual page for it (if
  python3-argparse is installed) and bash completions. We're even generating the
  ZSH completions, but the install path must be provided.
  
  The daemon command line interface has been improved for debugging, so use
  --help-debug for further information.
  
  The systemd service lockdown settings have been restricted even more.
  
  Various code optimizations.
- 
  
  0.20
  
  
  This release adds support for multiple power-profiles-daemon drivers to
  load simultaneously.  This notably allows both CPU based control with
  amd-pstate or intel-pstate as well as ACPI platform profile based control.
  
  This release also adds support for the amdgpu panel power savings which uses
  dedicated hardware in systems with integrated Radeon graphics to decrease 
panel
  power consumption when the system is on battery.
  
  0.13
  
  
  This release adds support for the AMD P-State driver that's been added to the
  6.3 Linux kernel. This release also fixes mismatched profiles on some HP
  laptops and some miscellaneous bug fixes.
  
  0.12
  
  
  This release adds support for the Intel "Energy Performance Bias" feature, 
which
  can be used on hardware that doesn't have a platform_profile or doesn't 
support
  HWP. It will also be used to eke out a bit more performance, or power, on 
systems
  which already supported HWP.
  
  More information is available in the README.
  
  0.11.1
  --
  
  This release stops power-profiles-daemon from modifying the cpufreq driver 
when
  driver when the user/administrator has chosen to disable the Intel P-State 
scaling
  governor (eg. forcing a passive operation mode).
  
  More information is available in the README.
  
  0.11
  
  
  This release fixes problems on Intel machines when the CPUs didn't support 
turbo at
  all, or the performance scaling governor was built as default in the kernel.
  
  It also adds better end-user documentation, fixes in the command-line tool to 
not
  cause bug report tools to popup on not-uncommon errors, and a bug fix for 
running

[Bug 1942616] Re: Settings Power says high hardware temperature

2024-04-09 Thread Mario Limonciello
That's great to hear!

I'll close this issue then since we have the newer version in Noble and a 
wishlist bug to backport it to Jammy:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2008958

If anyone else encounters this again, please ensure you're on 0.21 and if you 
are please capture these at the time of the failure:
/sys/devices/system/cpu/intel_pstate/no_turbo
/sys/devices/system/cpu/intel_pstate/turbo_pct

** Changed in: power-profiles-daemon (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942616

Title:
  Settings Power says high hardware temperature

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1942616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060197] Re: [FFe] [HWE] fwupd-efi 1.5 and gnu-efi 3.0.18

2024-04-09 Thread Mario Limonciello
As this is going to be staged on the PPA and copied; how about staging
it "now" rather than waiting for the release manager?

This will allow at least testing it with secure boot turned off (using
the unsigned binary).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060197

Title:
  [FFe] [HWE] fwupd-efi 1.5 and gnu-efi 3.0.18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd-efi/+bug/2060197/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056445] Re: external monitors flash white with every interrupt

2024-04-09 Thread Mario Limonciello
It was confirmed by many people this is fixed in the upgraded Framework
BIOS 3.05.

** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056445

Title:
  external monitors flash white with every interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056445/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056803] Re: amdgpu: hotplugging display sometimes fails

2024-04-09 Thread Mario Limonciello
*** This bug is a duplicate of bug 2056445 ***
https://bugs.launchpad.net/bugs/2056445

** This bug has been marked a duplicate of bug 2056445
   external monitors flash white with every interrupt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056803

Title:
  amdgpu: hotplugging display sometimes fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056803/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1979215] Re: gnu-efi: ld.bfd: warning: /usr/lib64/crt0-efi-x86_64.o: missing .note.GNU-stack section implies executable stack

2024-04-06 Thread Mario Limonciello
I checked the source and this is there for 3.0.15 or later:

$ git checkout upstream/3.0.15
$ grep .note.GNU-stack gnuefi/crt0-efi-x86_64.S -R
.section .note.GNU-stack,"",%progbits


** Changed in: gnu-efi (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1979215

Title:
  gnu-efi: ld.bfd: warning: /usr/lib64/crt0-efi-x86_64.o: missing
  .note.GNU-stack section implies executable stack

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnu-efi/+bug/1979215/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060143] Re: FFe: Move fwupd to zstd instead of xz

2024-04-06 Thread Mario Limonciello
** Attachment added: "reinstalling from authenticated remote"
   
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+attachment/5761732/+files/Screenshot%20from%202024-04-05%2010-51-50.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060143

Title:
  FFe: Move fwupd to zstd instead of xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060143] Re: FFe: Move fwupd to zstd instead of xz

2024-04-06 Thread Mario Limonciello
So I tried the same in the (apt version) of gnome-firmware.  No problems
reinstalling firmware there.


** Attachment added: "gnome-firmware reinstasll"
   
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+attachment/5761733/+files/Screenshot%20from%202024-04-05%2010-55-18.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060143

Title:
  FFe: Move fwupd to zstd instead of xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060143] Re: FFe: Move fwupd to zstd instead of xz

2024-04-06 Thread Mario Limonciello
Here is the testing from the PPA.  I installed fwupd-tests and then ran
below.

$ fwupdmgr --version 
compile   com.hughsie.libxmlb   0.3.17
compile   com.hughsie.libjcat   0.2.0
compile   org.freedesktop.fwupd 1.9.16
runtime   org.freedesktop.fwupd-efi 1.4
compile   org.freedesktop.gusb  0.4.8
runtime   com.hughsie.libjcat   0.2.0
runtime   org.freedesktop.gusb  0.4.8
runtime   org.freedesktop.fwupd 1.9.16

$ sudo fwupdtool enable-test-devices 
Loading… [** ]
Successfully enabled test devices
$ sudo systemctl restart fwupd

$ fwupdmgr get-updates 
Firmware metadata has not been updated for 30 days and may not be up to date.
Update now? (Requires internet connection) [y|N]: y
Updating lvfs
Downloading… [** ]
Successfully downloaded new metadata: 3 local devices supported
Devices with no available firmware updates: 
 • WD PC SN740 SDDPNQD-256G
Devices with the latest available firmware version:
 • Fingerprint Sensor
 • System Firmware
Framework Laptop 13 (AMD Ryzen 7040Series)
│
└─Integrated Webcam™:
  │   Device ID:  08d460be0f1f9f128413f816022a6439e0078018
  │   Summary:Fake webcam
  │   Current version:1.2.2
  │   Minimum Version:1.2.0
  │   Bootloader Version: 0.1.2
  │   Vendor: ACME Corp. (USB:0x046D)
  │   GUID:   b585990a-003e-5270-89d5-3705a17f9a43
  │   Device Flags:   • Updatable
  │   • System requires external power source
  │   • Supported on remote server
  │   • Cryptographic hash verification is available
  │   • Unsigned Payload
  │   Device Requests:• Message
  │ 
  └─FakeDevice Device Update:
New version:  1.2.4
Remote ID:lvfs
Release ID:   81488
Summary:  Firmware for the ACME Corp Integrated Webcam
License:  GPL-2.0+
Size: 10 bytes
Created:  2024-01-21
Urgency:  Medium
Tested by Google:
  Tested: 2024-03-09
  Distribution:   chromeos 124
  Old version:1.2.2
  Version[fwupd]: 1.9.13
Source:   
https://github.com/fwupd/fwupd/tree/main/data/installed-tests
Vendor:   LVFS
Release Flags:• Trusted metadata
  • Is upgrade
Description:  
Fixes another bug with the flux capacitor to prevent time going 
backwards.
Checksum: 
a92d4f433e925ea8e4a10d25dfa58e64ba1e68d07ee963605a2ccbaa2e3185aa


$ fwupdmgr update
Devices with no available firmware updates: 
 • WD PC SN740 SDDPNQD-256G
Devices with the latest available firmware version:
 • Fingerprint Sensor
╔══╗
║ Upgrade Integrated Webcam™ from 1.2.2 to 1.2.4?  ║
╠══╣
║ Fixes another bug with the flux capacitor to prevent time going backwards.   ║
║  ║
║ Integrated Webcam™ and all connected devices may not be usable while ║
║ updating.║
╚══╝
Perform operation? [Y|n]: y
Waiting… [***]
Successfully installed firmware
 • System Firmware

$ fwupdmgr reinstall 
0.  Cancel
1.  23ec719b6aabc2d2dac5176c232f0da7a21881b0 (Fingerprint Sensor)
2.  08d460be0f1f9f128413f816022a6439e0078018 (Integrated Webcam™)
3.  1e4fa9cea0b89e613370cf9657ffa0b6d3f37fec (System Firmware)
Choose device [0-3]: 1
╔══╗
║ Reinstall Fingerprint Sensor to 01000334?║
╠══╣
║ Fix physical MITM vulnerability that was found from blackwinghq - a touch║
║ of pwn part 1.   ║
║  ║
║ Fingerprint Sensor and all connected devices may not be usable while ║
║ updating.║
╚══╝
Perform operation? [Y|n]: y
Waiting… [***] Less than 
one minute remaining…
Successfully installed firmware
Successfully uploaded 1 report


** Bug watch added: github.com/canonical/firmware-updater/issues #264
   https://github.com/canonical/firmware-updater/issues/264


[Bug 2056445] Re: external monitors flash white with every interrupt

2024-04-06 Thread Mario Limonciello
I have a suspicion the root cause of the white screen could be fixed in
BIOS 3.05.

https://community.frame.work/t/framework-
laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle-beta/48276

Can you still reproduce it with no workarounds, 6.8.0-20 and the BIOS
upgrade?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056445

Title:
  external monitors flash white with every interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056445/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver

2024-04-06 Thread Mario Limonciello
Probably nvidia.ko is missing a call to
drm_aperture_remove_conflicting_pci_framebuffers()

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
  Phantom 46" monitor (simpledrm) shown in Settings after installing the
  Nvidia driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060143] Re: FFe: Move fwupd to zstd instead of xz

2024-04-06 Thread Mario Limonciello
Actually Jeremy copied it over from Debian already, closing bug.

** Changed in: fwupd (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060143

Title:
  FFe: Move fwupd to zstd instead of xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060143] Re: FFe: Move fwupd to zstd instead of xz

2024-04-06 Thread Mario Limonciello
Here is the diff:

https://launchpadlibrarian.net/723307725/fwupd_1.9.15-2_1.9.16-1~noble1.diff.gz

** Description changed:

  Fwupd 1.9.16 has added support to get metadata from LVFS using ZSTD
  format instead of of XZ format.
  
  In light of CVE-2024-3094 and Ubuntu 24.04 being an LTS I wanted to
  discuss considering an upgrade to fwupd 1.9.16 to make fwupd not use xz
  by default.
+ 
+ Also; there are a number of bug fixes in this release that I believe are
+ worth pulling in before Ubuntu 24.04 releases.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060143

Title:
  FFe: Move fwupd to zstd instead of xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060143] Re: FFe: Move fwupd to zstd instead of xz

2024-04-06 Thread Mario Limonciello
I also attempted to do testing with firmware-updater snap.  This is the
version I tested with:

installed:  0+git.90251bb(121) 11MB -

I had no problems enumerating devices.

I however did run into two problems:
1) I couldn't reinstall the test firmware.  This is not a new bug and was 
present previously, it's been reported back in February to the firmware-updater 
project.
https://github.com/canonical/firmware-updater/issues/264

2) I couldn't install firmware from a remote requiring authentication.  This is 
not a new bug and was present previously, it's been reported last week to the 
firmware-updater project.
https://github.com/canonical/firmware-updater/issues/274

** Attachment added: "reinstalling from firmware-updater"
   
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+attachment/5761731/+files/Screenshot%20from%202024-04-05%2010-51-33.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060143

Title:
  FFe: Move fwupd to zstd instead of xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060143] Re: FFe: Move fwupd to zstd instead of xz

2024-04-05 Thread Mario Limonciello
Here is the changelog for fwupd 1.9.16:

This release adds the following features:

Prefer zstd over xz for metadata
Relicense a few remaining plugin files to LGPL-2.1+

This release fixes the following bugs:

Correctly record UEFI success if adding ESRT nodes
Defer the DP Aux MST scanning on hotplug to workaround a kernel bug
Do not do the post-update version check if the device needs-reboot
Fix a fastboot warning when loading device
Fix a possible warning in fwupdmgr when excluding releases
Fix a qsi-dock warning when writing chunks
Ignore attribute-changed to work around a regression in macOS
Ignore ZFS zvols when finding the default ESP
Mark Pluton TPMs as part of the main CPU
Put the fwupd-efi verbose debugging in the journal
Recognize zfsbootmenu in ESP detection heuristic

This release adds support for the following hardware:

Acer T34 and U33 docks
Qualcomm Series 5 Gen 1 and Gen 2 and Series 3 Gen 1 and Gen 2 devices
Several Puya SPI chips
VIA VL822 C0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060143

Title:
  FFe: Move fwupd to zstd instead of xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060143] Re: FFe: Move fwupd to zstd instead of xz

2024-04-04 Thread Mario Limonciello
** No longer affects: libxmlb (Ubuntu)

** Description changed:

- Fwupd 1.9.16 and libxmlb 0.3.16 have added support to get metadata from
- LVFS using ZSTD format instead of of XZ format.
+ Fwupd 1.9.16 has added support to get metadata from LVFS using ZSTD
+ format instead of of XZ format.
  
  In light of CVE-2024-3094 and Ubuntu 24.04 being an LTS I wanted to
- discuss considering an upgrade to libxmlb 0.3.16 and fwupd 1.9.16 to
- make fwupd not use xz by default.
+ discuss considering an upgrade to fwupd 1.9.16 to make fwupd not use xz
+ by default.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060143

Title:
  FFe: Move fwupd to zstd instead of xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942616] Re: Settings Power says high hardware temperature

2024-04-04 Thread Mario Limonciello
Anyone still affected by this, can I please ask you to check the 0.21
release?  It's been uploaded to Noble.  I've also got it backported on a
PPA that can be used on Jammy or Mantic:

https://launchpad.net/~superm1/+archive/ubuntu/ppd

After upgrading if you're seeing this message still, can you please
gather the value of "/sys/devices/system/cpu/intel_pstate/no_turbo" at
the same time as the problem?

If that is set then this isn't the "fault" of power-profiles-daemon but
rather the hardware, kernel, or other software.

However the "reason" string emitted by power-profiles-daemon might need
some improvements.

** Changed in: power-profiles-daemon (Ubuntu)
   Status: Confirmed => Incomplete

** Bug watch added: Debian Bug tracker #1063757
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063757

** Also affects: power-profiles-daemon (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063757
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942616

Title:
  Settings Power says high hardware temperature

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1942616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2008958] Re: please backport 0.21 to jammy

2024-04-03 Thread Mario Limonciello
** Summary changed:

- please backport 0.20 to jammy
+ please backport 0.21 to jammy

** Description changed:

  The below significant bugfixes are implemented, which would enable more
  power & energy efficient modes on our supported laptops, as well as
  enable for the kernel default to change.
+ 
+ 0.21
+ 
+ Since this release power-profiles-daemon is battery-state aware and some 
drivers
+ use a more power efficient state when using the balanced profile on battery.
+ In particular both the AMD and Intel P-State drivers will use the
+ balance_power EPP profile, while for Intel one we also set the energy
+ performance bias to 8 (instead of 6).
+ 
+ This release also contains various fixes for the powerprofilesctl command line
+ tool when using the launch or version commands.
+ The tool is now better documented as we generate a manual page for it (if
+ python3-argparse is installed) and bash completions. We're even generating the
+ ZSH completions, but the install path must be provided.
+ 
+ The daemon command line interface has been improved for debugging, so use
+ --help-debug for further information.
+ 
+ The systemd service lockdown settings have been restricted even more.
+ 
+ Various code optimizations.
+ 
  
  0.20
  
  
  This release adds support for multiple power-profiles-daemon drivers to
  load simultaneously.  This notably allows both CPU based control with
  amd-pstate or intel-pstate as well as ACPI platform profile based control.
  
  This release also adds support for the amdgpu panel power savings which uses
  dedicated hardware in systems with integrated Radeon graphics to decrease 
panel
  power consumption when the system is on battery.
  
  0.13
  
  
  This release adds support for the AMD P-State driver that's been added to the
  6.3 Linux kernel. This release also fixes mismatched profiles on some HP
  laptops and some miscellaneous bug fixes.
  
  0.12
  
  
  This release adds support for the Intel "Energy Performance Bias" feature, 
which
  can be used on hardware that doesn't have a platform_profile or doesn't 
support
  HWP. It will also be used to eke out a bit more performance, or power, on 
systems
  which already supported HWP.
  
  More information is available in the README.
  
  0.11.1
  --
  
  This release stops power-profiles-daemon from modifying the cpufreq driver 
when
  driver when the user/administrator has chosen to disable the Intel P-State 
scaling
  governor (eg. forcing a passive operation mode).
  
  More information is available in the README.
  
  0.11
  
  
  This release fixes problems on Intel machines when the CPUs didn't support 
turbo at
  all, or the performance scaling governor was built as default in the kernel.
  
  It also adds better end-user documentation, fixes in the command-line tool to 
not
  cause bug report tools to popup on not-uncommon errors, and a bug fix for 
running
  on some systems with controllable charge speeds.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2008958

Title:
  please backport 0.21 to jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2008958/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939138] Re: Fwupd missing uefi plugin for riscv64

2024-04-03 Thread Mario Limonciello
> I expect we'll be syncing fwupd-efi 1.5 from Debian in the next few
days which adds riscv64 support

It also means syncing gnu-efi 3.0.18.  Is that OK at this stage?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939138

Title:
  Fwupd missing uefi plugin for riscv64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1939138/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060143] Re: FFe: Move fwupd to zstd instead of xz

2024-04-03 Thread Mario Limonciello
** Changed in: fwupd (Ubuntu)
 Assignee: (unassigned) => Mario Limonciello (superm1)

** Changed in: libxmlb (Ubuntu)
 Assignee: (unassigned) => Mario Limonciello (superm1)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060143

Title:
  FFe: Move fwupd to zstd instead of xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060143] Re: FFe: Move fwupd to zstd instead of xz

2024-04-03 Thread Mario Limonciello
libxmlb changelog:

Version 0.3.16
~~
Released: 2024-04-03

New Features:
 - Add the lzma and zstd support to the pkgconfig file (Richard Hughes)

Bugfixes:
 - Make the LZMA support optional (Richard Hughes)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060143

Title:
  FFe: Move fwupd to zstd instead of xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060143] [NEW] FFe: Move fwupd to zstd instead of xz

2024-04-03 Thread Mario Limonciello
Public bug reported:

Fwupd 1.9.16 and libxmlb 0.3.16 have added support to get metadata from
LVFS using ZSTD format instead of of XZ format.

In light of CVE-2024-3094 and Ubuntu 24.04 being an LTS I wanted to
discuss considering an upgrade to libxmlb 0.3.16 and fwupd 1.9.16 to
make fwupd not use xz by default.

** Affects: fwupd (Ubuntu)
 Importance: Undecided
 Assignee: Mario Limonciello (superm1)
 Status: Confirmed

** Affects: libxmlb (Ubuntu)
 Importance: Undecided
 Assignee: Mario Limonciello (superm1)
 Status: Confirmed

** Also affects: libxmlb (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060143

Title:
  FFe: Move fwupd to zstd instead of xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060143] Re: FFe: Move fwupd to zstd instead of xz

2024-04-03 Thread Mario Limonciello
Packages staged for testing here:
https://launchpad.net/~superm1/+archive/ubuntu/lp2060143

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060143

Title:
  FFe: Move fwupd to zstd instead of xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2060143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059807] Re: Power management settings on Ryzen 7 5800H are missing

2024-03-29 Thread Mario Limonciello
This is because amd-pstate is in active mode but nothing is tuning EPP
most likely.

Try to upgrade to this version of power profiles daemon:

https://launchpad.net/~superm1/+archive/ubuntu/ppd

Then you can change the power setting using the Gnome or kde GUI for it
or by using powerprofilesctl.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059807

Title:
  Power management settings on Ryzen 7 5800H are missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059807/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056445] Re: external monitors flash white with every interrupt

2024-03-29 Thread Mario Limonciello
> I'll also report back once I am able to test the new kernel.

I had a try and I was able to install it today on Noble by pulling the
deb packages for linux-image-unsigned-6.8.0-20-generic, linux-
modules-6.8.0-20-generic, linux-modules-extra-6.8.0-20-generic from
Launchpad manually.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056445

Title:
  external monitors flash white with every interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056445/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056445] Re: external monitors flash white with every interrupt

2024-03-29 Thread Mario Limonciello
> this system has a single DIMM which was provided by framework:
DDR5-5600 - 32GB (1 x 32GB)

My system is 8GB, single stick, same speed 5600 MT/s, same company
(A-DATA).

> Restarting firefox temporarily resolves the issue. This behavior
started to happen after I switched to X11.

You're the first I've ever heard of this.  Hopefully it's not present in
Wayland.  There is very little testing or development that happens in
X11.

> After setting UMA_Game_Optimized, I can confirm that (after 30 minutes
of usage), the system appears far more stable.

That's good to hear the workarounds improve things for you too.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056445

Title:
  external monitors flash white with every interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056445/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2051410] Re: AMD-GPU, decrease video resolution leads to black screen

2024-03-28 Thread Mario Limonciello
*** This bug is a duplicate of bug 2046504 ***
https://bugs.launchpad.net/bugs/2046504

** This bug has been marked a duplicate of bug 2046504
   AMD GPU display is blank when set lower resolution than native mode on eDP

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051410

Title:
  AMD-GPU, decrease video resolution leads to black screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2051410/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056445] Re: external monitors flash white with every interrupt

2024-03-26 Thread Mario Limonciello
> Am I missing something to get the proposed
kernel?

I guess the same reason it's not migrating is the reason you can't
install it? Maybe some kernel team members can comment.

> It sounds like GTT access is what causes this issue, and that using the
bios option won't guarantee that it will never happen. Is that correct?

If you look at your journal from when this issue occurs you'll see an
IOMMU page fault. This is the IOMMU reporting that there was an
attempted access at memory that is out of the region that the GPU is
allowed to access. This can happen when there is a userspace driver bug
(IE mesa) or a misconfigured driver (IE amdgpu) or a faulty firmware (IE
the BIOS).

There have been cases of a white screen caused by an incorrect memory
addressing mask on systems with 64GB, but that's been fixed a long time
now.

It is definitely an attempt at accessing outside of VRAM but I have a
suspicion the address attempting to be addressed is ALSO outside of GTT.

> Interesting. If there's any extra info (or testing) I can provide to help
with debugging/fixing this issue, please let me know.

If you can add your details for your "specific" FW13 AMD to the upstream bug 
maybe others who are affected can help with building the pattern.
I mean the memory vendor, speed of memory, amount, channel configuration.

What you do to trigger it, etc.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056445

Title:
  external monitors flash white with every interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056445/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056445] Re: external monitors flash white with every interrupt

2024-03-26 Thread Mario Limonciello
> Should this fix the flickering issue? I'm happy to test it out.

It will fix a colored flickering; but not the white screen (if that is
what you're observing).  It also fixes issues with suspend/resume that
were present in earlier 6.8-rc kernels but fixed by the final version.

> I'm curious about the implications of the two workarounds presented. I
see that UMA_Game_Optimized will reserve some system ram for the GPU,
which I don't have any issues with if there is some benefit. Will this
use scatter/gather and therefore perform better as a result?

If you use the BIOS option yes it will carve out more memory for VRAM
use.  S/G is still used, but GTT memory is less likely to be accessed
when you have more VRAM.  If you turn off S/G then GTT will NEVER be
used.

The potential negative implication for the BIOS option is more RAM being used 
for GPU that can't be for anything else.
The potential negative implications of turning off S/G in the driver are that 
the driver may run out of memory in some situations that require a lot of VRAM 
such as multiple 4k monitor docking.


FWIW - I have a FW13 AMD and I've never seen this white screen problem myself. 
I don't know if it is tied to RAM vendor, RAM size, or a BIOS issue.  My 
educated guess is it's actually a BIOS issue and it might be properly fixed 
when FW upgrades to the next BIOS.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056445

Title:
  external monitors flash white with every interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056445/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058604] Re: Framework 16 disable touchpad when typing doesn't work

2024-03-26 Thread Mario Limonciello
** Changed in: libinput (Ubuntu)
 Assignee: (unassigned) => Mario Limonciello (superm1)

** Changed in: libinput (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058604

Title:
  Framework 16 disable touchpad when typing doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2058604/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update

2024-03-25 Thread Mario Limonciello
** Also affects: linux-firmware (Ubuntu Noble)
   Importance: Undecided
 Assignee: Jose Ogando Justo (joseogando)
   Status: New

** Also affects: linux-firmware (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-firmware (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Changed in: linux-firmware (Ubuntu Noble)
   Status: New => Fix Released

** Changed in: linux-firmware (Ubuntu Mantic)
 Assignee: (unassigned) => Jose Ogando Justo (joseogando)

** Changed in: linux-firmware (Ubuntu Jammy)
 Assignee: (unassigned) => Jose Ogando Justo (joseogando)

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #8044
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/8044

** Also affects: linux-firmware via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/8044
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058830

Title:
  vp9 hw decode broken on modern AMD apus, needs amdgpu update

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2058830/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2057424] Re: No variable refresh rate (VRR) on the Framework 16

2024-03-22 Thread Mario Limonciello
FWIW it's in drm-fixes now.

https://cgit.freedesktop.org/drm/drm/commit/?id=2f14c0c8cae8e9e3b603a3f91909baba66540027

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057424

Title:
  No variable refresh rate (VRR) on the Framework 16

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2057424/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054489] Re: Crash on blank screen

2024-03-22 Thread Mario Limonciello
*** This bug is a duplicate of bug 2056445 ***
https://bugs.launchpad.net/bugs/2056445

** This bug has been marked a duplicate of bug 2056445
   external monitors flash white with every interrupt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054489

Title:
  Crash on blank screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054489/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2053040] Re: GPU Crash When Waking from Suspend

2024-03-22 Thread Mario Limonciello
*** This bug is a duplicate of bug 2056445 ***
https://bugs.launchpad.net/bugs/2056445

** This bug has been marked a duplicate of bug 2056445
   external monitors flash white with every interrupt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2053040

Title:
  GPU Crash When Waking from Suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053040/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2052467] Re: Unplugging External Monitor Causes GPU Crash

2024-03-22 Thread Mario Limonciello
*** This bug is a duplicate of bug 2056445 ***
https://bugs.launchpad.net/bugs/2056445

** This bug has been marked a duplicate of bug 2056445
   external monitors flash white with every interrupt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052467

Title:
  Unplugging External Monitor Causes GPU Crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052467/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056445] Re: external monitors flash white with every interrupt

2024-03-21 Thread Mario Limonciello
I suggest updating to 6.8.0-20 though, this 6.8.0-11 has an old 6.8-RC
snapshot and there are other bugs that got fixed later on in the
6.8-RC's.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056445

Title:
  external monitors flash white with every interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056445/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056445] Re: external monitors flash white with every interrupt

2024-03-21 Thread Mario Limonciello
For some unknown reason this only seems to be reported on some people's
Framework 13 AMD laptops.

FYI - there are two workarounds for those currently encountering this
issue.

* On the kernel command line: amdgpu.sg_display=0
* Change the BIOS settings from Auto to UMA_Game_Optimized.


** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #3187
   https://gitlab.freedesktop.org/drm/amd/-/issues/3187

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/amd/-/issues/3187
   Importance: Unknown
   Status: Unknown

** Changed in: linux (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056445

Title:
  external monitors flash white with every interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056445/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058604] [NEW] Framework 16 disable touchpad when typing doesn't work

2024-03-20 Thread Mario Limonciello
Public bug reported:

Due to the "input deck" the Framework 16 has a "USB" internal keyboard.
This throws off heuristics for detection of keyboards to turn off when
you select disable touchpad when typing.

This is fixed in upstream libinput with the following change:
https://gitlab.freedesktop.org/libinput/libinput/-/commit/566857bd98131009699c9ab6efc7af37afd43fd0

As that's not yet part of a release yet and it's a trivial change, could
it be cherry picked for Ubuntu to give a better experience to Framework
16 users?

** Affects: libinput (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058604

Title:
  Framework 16 disable touchpad when typing doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2058604/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970069] Re: Annoying boot messages interfering with splash screen

2024-03-13 Thread Mario Limonciello
Can you double check the framebuffer FB related conf options in your
kconfig against those in Fedora?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970069] Re: Annoying boot messages interfering with splash screen

2024-03-13 Thread Mario Limonciello
The backend is a framebuffer driver. For example efifb which uses the
framebuffer set up by GOP in pre-boot.

If there are framebuffer drivers in tinydrm then maybe they matter for
those architectures.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2057424] Re: No variable refresh rate (VRR) on the Framework 16

2024-03-12 Thread Mario Limonciello
V2 addressed comments and was reviewed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057424

Title:
  No variable refresh rate (VRR) on the Framework 16

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2057424/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056498] Re: Kernel crash in amd gpu driver

2024-03-09 Thread Mario Limonciello
*** This bug is a duplicate of bug 2039926 ***
https://bugs.launchpad.net/bugs/2039926

** This bug has been marked a duplicate of bug 2039926
   Error UBSAN: array-index-out-of-bounds amdgpu 
(drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056498

Title:
  Kernel crash in amd gpu driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2056498/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056548] Re: fwupd metadata bug due to outdated version in Ubuntu 22.04 repositories

2024-03-08 Thread Mario Limonciello
JFYI, Noble already has 1.9.14, this request is for Jammy.  There are a
bunch of other Jammy specific bugs that would be fixed by such a SRU.

https://bugs.launchpad.net/ubuntu/jammy/+source/fwupd

The SRU process (https://wiki.ubuntu.com/StableReleaseUpdate) has an
exception for fwupd (https://wiki.ubuntu.com/firmware-updates) that
/should/ allow migrating from 1.7.x to 1.9.x.


** Also affects: fwupd (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: fwupd (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: fwupd (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056548

Title:
  fwupd metadata bug due to outdated version in Ubuntu 22.04
  repositories

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2056548/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970069] Re: Annoying boot messages interfering with splash screen

2024-03-07 Thread Mario Limonciello
Even if FRAMEBUFFER=Y wasn't added, I think that a change to stop adding
all those other drm drivers makes a lot of sense. No use doubling the
initrd size for the LUKS case.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970069] Re: Annoying boot messages interfering with splash screen

2024-03-06 Thread Mario Limonciello
AFAICT; these initramfs-tools package changes would cover it:

* hooks/framebuffer can be totally removed.  
* scripts/init-top/framebuffer should probably stay
* conf/initramfs.conf needs FRAMEBUFFER=y added to it

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970069] Re: Annoying boot messages interfering with splash screen

2024-03-06 Thread Mario Limonciello
Plymouth only gets added to the initrd when LUKS is enabled or you mark
another reason for needing the framebuffer.

So the suggestion I have from comment #49 is to mark needing the
framebuffer by default, and then stop including any DRM modules because
simpledrm is built into the kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939138] Re: Fwupd missing uefi plugin for riscv64

2024-02-26 Thread Mario Limonciello
Fwupd 1.9.14 is built with uefi capsules plugin for this architecture.

** Changed in: fwupd (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939138

Title:
  Fwupd missing uefi plugin for riscv64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1939138/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2047374] Re: TPM PCR0 recontruction fails on Pluton fTPM

2023-12-27 Thread Mario Limonciello
The way this works is that the tpm event log is used to attempt to
reconstruct pcr0. If it doesn't match the value in the tpm pcr0 then
there is a bug or malware.

The same report was brought into fwupd upstream.
Various artifacts were captured and the conclusion is this is a BIOS bug.

It should be reported to the board vendor to be fixed.

https://github.com/fwupd/fwupd/issues/6574

** Bug watch added: github.com/fwupd/fwupd/issues #6574
   https://github.com/fwupd/fwupd/issues/6574

** Changed in: fwupd (Ubuntu)
   Status: New => Opinion

** Also affects: fwupd via
   https://github.com/fwupd/fwupd/issues/6574
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2047374

Title:
  TPM PCR0 recontruction fails on Pluton fTPM

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/2047374/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956509] Re: Support AMD P-State cpufreq control mechanism

2022-05-31 Thread Mario Limonciello
** Changed in: linux-oem-5.17 (Ubuntu)
   Status: Fix Committed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956509

Title:
  Support AMD P-State cpufreq control mechanism

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1956509/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962349] Re: Bolt doesn't work with native USB4 hosts

2022-05-31 Thread Mario Limonciello
** Changed in: linux-oem-5.17 (Ubuntu)
   Status: Fix Committed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962349

Title:
  Bolt doesn't work with native USB4 hosts

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1962349/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971700] Re: [jammy] 5.17.0-1004-oem breaks resume from sleep

2022-05-31 Thread Mario Limonciello
*** This bug is a duplicate of bug 1971597 ***
https://bugs.launchpad.net/bugs/1971597

This should be fixed in 5.17.0-1005.5 and newer.  It's actually a
duplicate of bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971597

** This bug has been marked a duplicate of bug 1971597
   amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971700

Title:
  [jammy] 5.17.0-1004-oem breaks resume from sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971700/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server

2022-05-24 Thread Mario Limonciello
@KH:

Thanks for sharing that!  I agree with you.  I've sent this up to explicitly 
document the new behavior.
https://lore.kernel.org/linux-ide/20220524170508.563-4-mario.limoncie...@amd.com/T/#u

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576

Title:
  SATA device hot plug regression on AMD EPYC (Asus) server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server

2022-05-23 Thread Mario Limonciello
0-> ATA_LPM_UNKNOWN,
1-> ATA_LPM_MAX_POWER,
2-> ATA_LPM_MED_POWER,
3-> ATA_LPM_MED_POWER_WITH_DIPM, /* Med power + DIPM as win IRST does */
4-> ATA_LPM_MIN_POWER_WITH_PARTIAL, /* Min Power + partial and slumber */
5-> ATA_LPM_MIN_POWER, /* Min power + no partial (slumber only) */

I hypothesize what is happening is based on your configuration that
Ubuntu configuration has CONFIG_SATA_MOBILE_LPM_POLICY as "3", and so on
your system it sets MED_POWER_WITH_DIPM if you don't override it.

Here is what that means:

med_power_with_dipm: Identical to the existing medium_power
setting except that it enables dipm (device initiated power
management) on top, which makes it match the Windows IRST (Intel
Rapid Storage Technology) driver settings. This setting is also
close to min_power, except that:

a) It does not use host-initiated slumber mode, but it does
   allow device-initiated slumber
b) It does not enable low power device sleep mode (DevSlp).


I think I found the problem.  When policy is set this way the code will look 
and see whether any links are enabled and power the port off if not.  When the 
port is powered off, it doesn't get powered back on.

case ATA_LPM_MED_POWER_WITH_DIPM:
case ATA_LPM_MIN_POWER_WITH_PARTIAL:
case ATA_LPM_MIN_POWER:
if (ata_link_nr_enabled(link) > 0)
/* no restrictions on LPM transitions */
scontrol &= ~(0x7 << 8);
else {
/* empty port, power off */
scontrol &= ~0xf;
scontrol |= (0x1 << 2);
}
break;

So no hotplug event should come through while in this state *because* the 
controller gets powered off.  
I think you can probably change the link power management file at runtime to 
wake the port back up.

Here's my ideas:
1) Revert the commit.  This will fix hotplug on Epyc, but raise power 
consumption on all the client stuff with nothing plugged in by default.  It 
could have some negative impacts to anything that passed energy certifications 
previously.

2) Live with and document the new behavior (to enable hotplug support
you need to set policy accordingly using this sysfs file etc).

3) Try to special case Epyc vs Client to only apply this mobile policy
on client parts.  This gets a bit ugly as the controllers are the same,
it's just a policy decision that is different for these.  We would need
some scalable criteria or at least a hint to know that the controller is
part of a datacenter CPU.

4) Revert the commit in stable and only let the new behavior exist in
newer kernels.

In upstream kernel we wanted to drop this mobile vs not mobile
designation, so doing #2 for this situation and coming up with a way to
do #3 upstream is my preference to solve this.

Any thoughts/suggestions?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576

Title:
  SATA device hot plug regression on AMD EPYC (Asus) server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's

2022-05-19 Thread Mario Limonciello
** Changed in: linux-oem-5.17 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950062

Title:
  Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server

2022-05-18 Thread Mario Limonciello
On any failing kernel, can you try to add "ahci.mobile_lpm_policy=0" to
the kernel command line and confirm if that fixes things?

If it does, could you also compare "ahci.mobile_lpm_policy=1" and
"ahci.mobile_lpm_policy=2"?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576

Title:
  SATA device hot plug regression on AMD EPYC (Asus) server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   5   6   7   8   9   10   >