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
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
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.
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
** 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
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
+++
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.
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:
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
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
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
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:
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
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
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
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
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
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
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
> 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
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
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
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
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039926
Title:
Error UBSAN: array-index-out-of-bounds amdgpu
** 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 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
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
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
** 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.
> 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.
** 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.
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
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
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
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.
> 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
> 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
*** 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
> 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
> 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
** 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.
** 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:
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
*** 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
*** 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
*** 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 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
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
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:
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
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
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
*** 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
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
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.
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,
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
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
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
** 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
** 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
*** 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
@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
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
** 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
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
1 - 100 of 6904 matches
Mail list logo