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
On 5/9/2024 16:50, Pratap Nirujogi wrote:
Add the isp driver in amdgpu to support ISP device on the APUs that
supports ISP IP block. ISP hw block is used for camera front-end, pre
and post processing operations.
Signed-off-by: Pratap Nirujogi
Reviewed-by: Mario Limonciello
---
Changes made
On 5/9/2024 14:35, Pratap Nirujogi wrote:
Enable ISP for ISP V4.1.0 and V4.1.1 in amdgpu_discovery.
Signed-off-by: Pratap Nirujogi
Reviewed-by: Mario Limonciello
---
drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c | 22 +++
1 file changed, 22 insertions(+)
diff --git
On 5/9/2024 14:35, Pratap Nirujogi wrote:
ISP hw block is supported in some of the AMD GPU versions, add support
to discover ISP IP in amdgpu_discovery.
Signed-off-by: Pratap Nirujogi
Reviewed-by: Mario Limonciello
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 +
drivers/gpu/drm
On 5/9/2024 14:35, Pratap Nirujogi wrote:
Add the isp driver in amdgpu to support ISP device on the APUs that
supports ISP IP block. ISP hw block is used for camera front-end, pre
and post processing operations.
Signed-off-by: Pratap Nirujogi
Change-Id:
On 5/9/2024 07:43, Linux regression tracking (Thorsten Leemhuis) wrote:
On 18.04.24 21:43, Harry Wentland wrote:
On 2024-03-07 01:29, Wayne Lin wrote:
[Why]
Commit:
- commit 5aa1dfcdf0a4 ("drm/mst: Refactor the flow for payload
allocation/removement")
accidently overwrite the commit
- commit
On 5/9/2024 07:43, Linux regression tracking (Thorsten Leemhuis) wrote:
On 18.04.24 21:43, Harry Wentland wrote:
On 2024-03-07 01:29, Wayne Lin wrote:
[Why]
Commit:
- commit 5aa1dfcdf0a4 ("drm/mst: Refactor the flow for payload
allocation/removement")
accidently overwrite the commit
- commit
On 5/9/2024 07:43, Linux regression tracking (Thorsten Leemhuis) wrote:
On 18.04.24 21:43, Harry Wentland wrote:
On 2024-03-07 01:29, Wayne Lin wrote:
[Why]
Commit:
- commit 5aa1dfcdf0a4 ("drm/mst: Refactor the flow for payload
allocation/removement")
accidently overwrite the commit
- commit
OLED panels don't support the ABM, they shouldn't offer the
panel_power_savings attribute to the user. Check whether aux BL
control support was enabled to decide whether to offer it.
Reported-by: Gergo Koteles
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3359
Signed-off-by: Mario
On 5/8/2024 09:50, Pratap Nirujogi wrote:
Add the isp driver in amdgpu to support ISP device on the APUs that
supports ISP IP block. ISP hw block is used for camera front-end, pre
and post processing operations.
Signed-off-by: Pratap Nirujogi
---
drivers/gpu/drm/amd/amdgpu/Makefile |
The pixel_clock_mhz property is populated in amdgpu_dm when Freesync is setup,
but it is not used anywhere in amdgpu_dm. Remove the dead code.
Cc: chiahsuan.ch...@amd.com
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 3 ---
drivers/gpu/drm/amd/display
orary Disable MST DP Colorspace
Property").
Reported-and-tested-by: Tyler Schneider
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3353
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/d
orary Disable MST DP Colorspace
Property").
Reported-and-tested-by: Tyler Schneider
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3353
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/d
ses: https://gitlab.freedesktop.org/drm/amd/-/issues/3353
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
b/drivers/gpu/drm/amd/display
ses: https://gitlab.freedesktop.org/drm/amd/-/issues/3353
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
b/drivers/gpu/drm/amd/display
/drm/amd/-/issues/3353
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/drm_mode_object.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_mode_object.c
b/drivers/gpu/drm/drm_mode_object.c
index 0e8355063eee..b077547a2db4 100644
--- a/drivers/gpu/drm
/drm/amd/-/issues/3353
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/drm_mode_object.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_mode_object.c
b/drivers/gpu/drm/drm_mode_object.c
index 0e8355063eee..b077547a2db4 100644
--- a/drivers/gpu/drm
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
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.
*** 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.
*** 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
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
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
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:
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
On 5/3/2024 07:05, fililip wrote:
This patch allows setting a low power cap if |ignore_min_pcap| is set to 1.
Signed-off-by: fililip
Rather than an attachment you should send the patch inline. That would
mean that your commit message and SoB should be at the top of the patch
itself.
If
org/drm/amd/-/issues/3351
Signed-off-by: Mario Limonciello
---
I tested this on SMU 13.0.4 for ~85 cycles with this script, BIOS 1.1.0.2a and
didn't observe any hangs.
```
#!/bin/sh
echo test_resume > /sys/power/disk
i=1
while [ : ]; do
echo "Starting cycle $i"
echo disk > /sys
-foundations-team, but admittedly I have not
conferred closely with other members.
I would invite discussion on any opposing views from other members.
On Sun, Feb 18, 2024 at 12:11:48AM -0600, Mario Limonciello wrote:
Considering all of that, I wanted to discuss with the release team to
modify
t was just introduced that regressed VRR disable it for now
so that problem can be properly root caused.
Cc: Tom Chung
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3344
Fixes: 5950efe25ee0 ("drm/amd/display: Enable Panel Replay for static screen
use case")
Signed-off-b
On 4/29/2024 08:38, Alex Deucher wrote:
This reverts commit 31729e8c21ecfd671458e02b6511eb68c2225113.
This causes problems with reboots/shutdowns for some users.
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3351
Signed-off-by: Alex Deucher
Cc: Tim Huang
It would be unfortunate
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
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
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
** 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
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2059215
Title:
HDMI Display Not detected: AMD Ryzen 5
On 4/13/2024 03:51, Gergo Koteles wrote:
Hi>
ABM will reduce the backlight and compensate by adjusting brightness and
contrast of the image. It has 5 levels: 0, 1, 2, 3, 4. 0 means off. 4 means
maximum backlight reduction. IMO, 1 and 2 look okay. 3 and 4 can be quite
impactful, both to
On 4/13/2024 03:51, Gergo Koteles wrote:
Hi>
ABM will reduce the backlight and compensate by adjusting brightness and
contrast of the image. It has 5 levels: 0, 1, 2, 3, 4. 0 means off. 4 means
maximum backlight reduction. IMO, 1 and 2 look okay. 3 and 4 can be quite
impactful, both to
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
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
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 Kubuntu
Bugs, which is subscribed to sddm in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
To
> 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
> 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
** 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
** 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
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
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
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
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
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
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
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
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
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:
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:
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:
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:
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
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
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
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:
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:
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 Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/2061708
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
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:
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
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
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
** 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
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
https://patchwork.freedesktop.org/patch/588305/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039926
Title:
Error UBSAN: array-index-out-of-bounds amdgpu
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
+
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
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
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
** 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:
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
+
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
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
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
*** 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 Kernel
Packages, which is
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.
*** 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
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
** 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
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
--
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
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
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
Could you please also capture the value in
/sys/devices/system/cpu/intel_pstate/turbo_pct when you reproduced the
issue?
In that case can you please modify the daemon's systemd unit to run
the daemon with -vv in the ExecStart command then share the unit's
journal output from a boot this occurs to better understand it?
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
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:
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
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060268
Title:
Phantom 46" monitor (simpledrm)
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
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
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
** 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.
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
** 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.
Can this still reproduce using power-profiles-daemon 0.21-1? It's
available in unstable.
If so, can you please check the value of
"/sys/devices/system/cpu/intel_pstate/no_turbo" at the time of the
problem?
If the kernel doesn't advertise turbo support then
power-profiles-daemon can't do
101 - 200 of 13557 matches
Mail list logo