** Tags added: originate-from-2106922
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106923
Title:
Fix divide by zero errors in DML2
To manage notifications about this bug go to:
https://bugs.launc
Public bug reported:
Several HP platforms have a design change that eDP is connected to DP1 instead
of DP0.
Because of this amdgpu needs a quirk to know to find eDP on DP1.
https://github.com/torvalds/linux/commit/139e99d58e373bd11f085766e681d21d34d0b097
https://github.com/torvalds/linux/commit/
Public bug reported:
Random crashes have been reported on GPUs that use DML2 (Ryzen AI APUs
and Radeon 9000 dGPU). The crashes are root caused to corruption in
registers used for floating point code.
They are caused by a lack of FP context protection around that code.
They are fixed by these 3 co
It should be there. Maybe the issue is in the initramfs building then.
Didn't 25.04 move to dracut? Perhaps there is a bug with it.
** Also affects: dracut (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: dracut (Ubuntu Noble)
--
You received this bug notification beca
I just upgraded a Framework laptop from Ubuntu 24.04 to Ubuntu 24.10 and
then to Ubuntu 25.04. I did
# sudo apt install dracut
# sudo dracut --force
# sudo reboot
Then I checked the next boot (while booted into 6.14.0-13) and
everything seems fine to me. xdna driver loaded just fine.
I'm going
> So it works for me now after a manual rebuild. I don't know how to
debug this further, or if it's even worth trying to do so
I do think it's worth understanding this. If it's related to the
eventual dracut move it's just 'kicking the can down the road' and
something that needs to be figured out
So the files are there but you're still seeing errors?
Try to `rmmod amdxdna` and `modprobe amdxdna`.
If that works I suspect that what's going on is it got loaded into the
initramfs but was missing firmware in the initramfs.
Maybe this commit is missing in your kernel.
https://github.com/torva
Can you please bring your bug report upstream here?
https://github.com/fwupd/fwupd/issues
We will need to do some more triage on what version you have, daemon
logs etc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
This doesn't look like a fwupd packaging problem, but rather a dpkg
problem.
/usr/bin/dpkg-maintscript-helper: 609: setup_colors: not found
dpkg: aviso: o subprocesso do pacote antigo fwupd, script pre-removal retornou
erro do status de saída 127
dpkg: em vez disso a tentar script do novo pacote
I can't control the release from unapproved queue, this is the job of an
archive administrator. I uploaded to the queue on 3/25.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104109
Title:
[SRU] Ca
** Package changed: fwupd (Ubuntu) => 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/2105899
Title:
Fans spinning after sleep mode (s2idle) - Dell Precision
To manage notifications ab
*** This bug is a duplicate of bug 2056548 ***
https://bugs.launchpad.net/bugs/2056548
** This bug has been marked a duplicate of bug 2056548
fwupd metadata bug due to outdated version in Ubuntu 22.04 repositories
--
You received this bug notification because you are a member of Ubuntu
Bu
** Changed in: linux-oem-6.11 (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/2100748
Title:
Disable Human Presence Detection on AMD SFH
To manage notifications
*** This bug is a duplicate of bug 2056548 ***
https://bugs.launchpad.net/bugs/2056548
** Package changed: fwupdate (Ubuntu) => fwupd (Ubuntu)
** This bug has been marked a duplicate of bug 2056548
fwupd metadata bug due to outdated version in Ubuntu 22.04 repositories
--
You received th
To me it sounds like an infra issue or an ISP issue not a fwupd issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104858
Title:
fwupd-refresh.service failing as at March 27 2025 on Ubuntu 22.04
I've uploaded 1.9.29 to noble and oracular unapproved queue.
Here is PPA you can use for now as well for early testing (exact same upload).
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages
For 2.0.7 I've uploaded it to unstable, and it will need to be synced to
plucky.
--
You recei
Got it; thanks for clarifying. After we get 2.0.7 in Plucky we can do
the SRU for 1.9.29 for older releases then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104109
Title:
[SRU] Can't update Del
** Changed in: fwupd (Ubuntu Plucky)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104109
Title:
[SRU] Can't update Dell Dock RMM firmware
To manage notifications
AFAICT the fix is not in 1.9.29. We need to wait for 1.9.30.
** Also affects: fwupd (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: fwupd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: fwupd (Ubuntu Oracular)
Importance: Undecided
This was reported upstream too.
https://github.com/fwupd/fwupd/issues/8522
It will be fixed for the 2.0.7 release coming up soon.
** Bug watch added: github.com/fwupd/fwupd/issues #8522
https://github.com/fwupd/fwupd/issues/8522
--
You received this bug notification because you are a member
I don't see any problems here with what fwupd is doing. After you
reboot is the device not up to date?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2102703
Title:
UEFI dbx update does not apply
T
Can you please provide more details? We need ideally the output of:
# sudo fwupdtool update -v 2>&1
** Changed in: fwupd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
This should be a bug in the firmware updater snap.
** 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/2099749
Title:
reboot popup shows two op
I don't draw that same conclusion as you. I feel you have two separate
issues that can cause severe problems.
If accessing the DPCD sysfs file provided by nouveau crashes in a way
that is enough to taint it there is certainly a nouveau bug (the
original one you filed here).
For this particular b
> Unfortunately, I can't replicate this as I have no idea how to easily
trigger a GPU reset
On AMD systems You can use debugfs file you can do it with. For example
on my system:
# cat /sys/kernel/debug/dri/0/amdgpu_gpu_recover
--
You received this bug notification because you are a member of Ub
Plucky already rebased to new enough linux-firmware, so only need task
for noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098979
Title:
[SRU] Add amdnpu firmware
To manage notifications abou
Public bug reported:
OEM-6.14 and mainline 6.14 kernel include AMD XDNA NPU kernel module.
Without matching NPU firmware the kernel will show an error about
failing to load on many platforms. This firmware should be SRU'ed into
Noble linux-firmware package to prevent this problem.
https://git.ke
** 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/2098668
Title:
nouveau crashes when fwupd requests DPCD reads on drm_dp_auxN
To manage noti
> According to the answer of this question, "fwupd scans for all dpaux
devices and probes them". Hence there might be no plugin that I could
disable to bypass this bug.
That's correct.
> Unfortunately, no. The ASUS TUF Gaming laptop may need it to run the
display. I suspect that because long ago
Can you please experiment with modprobe.blacklist=nouveau?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098668
Title:
fwupd daemon hangs for a while during TPM access
To manage notifications abou
> 2. Once it is up and running, starting the firmware-updater.firmware-notifier
> service produced this message:
> 15:55:12.499 FuPluginLinuxLockdown failed to ensure attribute fix flags:
> missing executable grubby in PATH
This message is to be expected; Ubuntu doesn't use grubby.
> 1. For som
From your log this looks like a nouveau kernel problem to me that is
tickled by fwupd using the DPCD reading interface.
If you don't use that GPU you can try modprobe.blacklist=nouveau or you
can try another kernel like OEM 6.11 or HWE 6.11.
** Package changed: fwupd (Ubuntu) => linux (Ubuntu)
-
2025-02-16T00:08:02.549345+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU
kernel: [ cut here ]
2025-02-16T00:08:02.549359+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU
kernel: WARNING: CPU: 13 PID: 1192141 at
drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c:192
r535_gsp_c
Also plucky is marked Fix Released because matching change is in fwupd
2.0.5 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097728
Title:
fwupd daemon not able to open device successfully
Here are some packages on the PPA for early testing until it's in
proposed.
https://launchpad.net/~superm1/+archive/ubuntu/uefi
I've uploaded to unapproved queue.
** Changed in: fwupd (Ubuntu)
Status: New => In Progress
** Also affects: fwupd (Ubuntu Noble)
Importance: Undecided
So could this release to updates now then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083020
Title:
Backport packages for 24.04.2 HWE stack
To manage notifications about this bug go to:
https:/
I've adjusted the upstream bug to re-open and make the situation
clearer.
--
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 noti
That's actually not going to help here - that's specifically with uefi-
dbx, not uefi-capsule. There needs to be more work explicitly for snapd
FDE compat with uefi-capsule.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
> I clearly dont have time to play with (1) and rebuilding/maintaining a
kernel in the hope of a non reproduction ; especially since I dont have
clear STR so it means making this my daily driver.
I'm not suggesting you to keep using/maintaining such a kernel, it's a
debugging data point to prove w
From the trace this is triggered from a userspace IOCTL to remove a
framebuffer. This causes drm core to process atomic_remove_fb() as
work, and this will use the drm driver to do atomic modesets.
One of the things that happens for this is going to be recalculating MST
DSC configs (if appropriate
As I gather there is already an upstream bug report, but no one has
worked on fixing it. I think we should mark this triaged in Ubuntu, and
if/when it's fixed upstream bring in the appropriate stable version to
Ubuntu (per the SRU exception policy for fwupd).
** Changed in: fwupd (Ubuntu)
To me it looks like the crash is in glib.
** Information type changed from Private to Public
** Package changed: fwupd (Ubuntu) => glib2.0 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20938
Although your stack probably does a better job on all the pieces you can
control than UEFI + secure boot, the root of trust doesn't come back to
hardware and that's what BootGuard is about.
I don't feel there is any work in Ubuntu for this at this time, but it's
worth iterating on the conversation
Crag has been working upstream on getting code ready for 1.9.27, and
it's been released today.
I've uploaded it to unapproved for noble and oracular. Please work with
SRU team on rest of SRU process.
I've also staged it on a PPA if you want to test before it's in -proposed.
https://launchpad.net
Crag has been working upstream on getting code ready for 1.9.27, and
it's been released today.
I've uploaded it to unapproved for noble and oracular. Please work with
SRU team on rest of SRU process.
I've also staged it on a PPA if you want to test before it's in -proposed.
https://launchpad.net
** 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/2083801
Title:
Support update logic changed for mediatek scalar
To manage notifica
** Changed in: fwupd (Ubuntu Plucky)
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/2085433
Title:
Support Dell K2 dock firmware update
To manage notifications
The plan is still 1.9.27 for SRU. 2.0 series has ABI bump and will be in
unstable release only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085433
Title:
Support Dell K2 dock firmware update
To
Can you tell me how many times you unplugged and plugged power adapter
during that log?
I see that hardware left s0i3 state 4 times over the one suspend cycle:
> 2024-11-19 21:47:42,898 INFO: ○ Hardware sleep cycle count: 4
I'm wondering if it's 1:1 mapping that it woke up and went back to
hardw
> sorry, I don't understand question. How do I change power adapter
state over the suspend sequence?
I'm meaning do either of these scenarios (specifically) trigger it:
1) You start your suspend sequence with it unplugged and then plug in and then
resume and the issue happens.
2) You start your
Did you happen to change the power adapter state over the suspend
sequence when this reproduced? There may be a problem with the firmware
handling of that event.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Your bad log seems to be showing the following problems.
Nov 10 22:38:42 Silencio kernel: [drm:drm_atomic_helper_wait_for_flip_done
[drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out
Nov 10 22:41:17 Silencio kernel: [drm:drm_crtc_commit_wait [drm]] *ERROR*
flip_done timed out
Nov 10
I suggest starting out with a mainline kernel build for 6.12-rc7.
* If you can reproduce the issue still there then you should check if
it's on the AMD bug tracker
(https://gitlab.freedesktop.org/drm/amd/-/issues). If it's not you
should raise an issue there.
* If you can't reproduce it on 6.12-
** No longer affects: amd
** Project changed: xf86-video-amd => linux
** Also affects: linux (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/2085388
I'm going to close this issue in Ubuntu, if you still feel documentation
needs to be changed then please raise it upstream with more specific
proposals. Pull requests would be most appreciated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Furthermore maintaining documentation in a man page is a lot of work -
it very easily gets outdated.
Instead a lot of the documentation is online and generated
automatically.
https://fwupd.github.io/
** Changed in: fwupd (Ubuntu)
Status: New => Opinion
--
You received this bug notificat
> Now the problem is I can't reproduce this so far. gnome-shell/xwayland
randomly exits at some point without any explanation (you can see it
just starts broken pipe at 12:31:54, no crash before, I need to find the
cause for that and report another bug :(
Maybe this:
https://gitlab.gnome.org/GNOM
*** This bug is a duplicate of bug 2083801 ***
https://bugs.launchpad.net/bugs/2083801
Yes then it's duplicate of
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2083801. Will mark
accordingly. Update the SRU text on that bug if necessary.
** This bug has been marked a duplicate of bug
Maybe this is actually duplicate of
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2083801
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085436
Title:
Support Mediatek MT9700 scalar IC firmwa
This bug will batch together with
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2085433 (that is
1.9.27 will fix both).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083801
Title:
Support up
OK, once that's tagged upstream, I will get this in plucky first.
** Also affects: fwupd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: fwupd (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: fwupd (Ubuntu Plucky)
Importance: Undecided
Is it different than
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2076151?
What specific fwupd version needed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085436
Title:
Support Mediatek
Can you please advise specific version needed? 1.9.26 or 1.9.27?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085433
Title:
Support Dell K2 dock firmware update
To manage notifications about thi
> Attaching the Journal, the initial crash can be seen at 12:31:54, lots
going on there, but nothing root-causing this.
[ 3300.659129] WARNING: CPU: 1 PID: 65823 at
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315
dal_gpio_service_open+0x1b6/0x270 [amdgpu]
This is the assertion yo
Did you rebuild your initramfs after blacklist? Or maybe it's
"dell_laptop"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084971
Title:
Unable to change power modes from balanced
To manage notifi
It still appears loaded. Or something else is providing the platform
profile.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084971
Title:
Unable to change power modes from balanced
To manage notif
** Changed in: fwupd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079907
Title:
All fwupdmgr commands failing, fwupd segfault appears in dmesg
To man
Oh this is a Dell system? I thought it was a Thinkpad sorry.
Can you please try to blacklist dell-laptop and restart your system?
Does it still reproduce?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
This appears to be a kernel driver or platform firmware bug. If it's new
to this kernel upgrade then it's more likely a kernel bug.
You should report it against the Thinkpad ACPI driver upstream.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: power-pro
(From the log you can see that you switched modes but then the kernel
changed it right back)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084971
Title:
Unable to change power modes from balanced
Can you please add -vv to the ExecStart command in the systemd unit and
then restart the daemon?
Share the journal output for the unit after reproducing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Here is the fixed firmware binary upstream.
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/ath12k/WCN7850/hw2.0?id=34d181d737527d903ebb363de6b2e3b1dcd42683
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Are you sure it's kernel? Or that's just a first guess? This could
easily be the systemd bugs.
https://github.com/systemd/systemd/issues/33626
https://github.com/systemd/systemd/issues/33462
You could try SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false to see if it
helps.
** Bug watch added: github.c
** Changed in: linux (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/2083538
Title:
amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence
fall
Do you have glib installed from somewhere outside of Ubuntu
repositories? Or any other dependencies?
** Changed in: fwupd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Is this different work than
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2076151? I guess
so; it should probably match the work that went into upstream 1.9.25
release.
https://github.com/fwupd/fwupd/commit/d8d5082255cad0a82cb332fa158ec8bbd93583ed
❯ git describe --contains d8d5082255cad0a
> but the GPU restarts are failing and the driver apparently deadlocks
or something (quite a bunch of mutex backtraces).
Yes; poor clean up/recovery should be tracked as a separate bug report
at https://gitlab.freedesktop.org/drm/amd/-/issues
--
You received this bug notification because you are
Possibly the same issue as fixed in mesa 24.1
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11138
Please uprev mesa in the snap and see if it helps.
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11138
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11138
--
You receiv
Can you check that? Was this maybe when the snap refreshed silently in
background? Or try a version without snap so you could use the host
mesa?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083538
T
This is most likely a mesa issue. Have you upgraded mesa recently to
match when it showed up?
** Also affects: mesa (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.lau
Actually the second is in 6.11 already.
> git describe --contains bf5641eccf71bcd13a849930e190563c3a19815d
v6.11-rc2~2^2~4
This is just an ask for 6.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
I see the same message on 0x60. Please pull in the this commit too.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bf5641eccf71bcd13a849930e190563c3a19815d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
> I don't know why i use dkms
When you installed the packaged version of ROCm you can use arguments to
decide whether or not to build the DKMS package. I don't expect you
really need it with this kernel version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I am tending to agree with Juerg, this is not Ubuntu's bug. They picked
up a stable update that fixed a problem, but it just so happens this
DKMS doesn't compile anymore.
I think the DKMS package will need to be re-spun due to this change.
I suggest reporting it here: https://gitlab.freedesktop.o
This definitely isn't an Ubuntu kernel bug, I will reject it as such.
You can file an issue here:
https://gitlab.freedesktop.org/drm/amd/-/issues if you have problems
stemming from that script.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notificati
> That's an unsupported DKMS, not a kernel problem. Is there any reason
why you don't use the kernel's amdgpu driver?
The DKMS driver takes an upstream snapshot of amdgpu for use with older
kernel versions. As I notice that in the above error log the DKMS
driver is from "6.8.5-2009582.24.04" you
Thanks for checking. I believe what's going on is that it resets the
topology, but the policy to re-authorize it doesn't happen because bolt
is missing until the rootfs is loaded. So initramfs needs a hook to
include bolt.
--
You received this bug notification because you are a member of Ubuntu
Fwupd only reports the security of the firmware that it can measure.
It's not a fwupd bug if there is a problem.
** 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.
Thanks for confirming it. You can also try to add thunderbolt to
/etc/initramfs-tools/modules to see if that's enough to fix the issue
instead of the kernel command line workaround.
I suspect it's not though, and that a hook will be needed to add:
* /lib/udev/rules/90-bolt.rules
* bolt.service
*
Try adding thunderbolt.host_reset=0 to your kernel command line.
Suspect it's the changes that came in
https://launchpad.net/ubuntu/+source/linux/6.8.0-38.38:
- thunderbolt: Introduce tb_port_reset()
- thunderbolt: Introduce tb_path_deactivate_hop()
- thunderbolt: Make tb_switch_reset(
This appears to be a different problem even if it leads to same symptom.
Please open a separate issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064595
Title:
AMD Rembrandt & AMD Rembrandt-R: S
> But building a new kernel and switching to it without deeper
experience and a fallback would be too hard for me.
No need to build a new kernel. There are binaries in the link that was
posted above. You can grab some of those to try. Just note that you
need to turn off secure boot if you have i
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077411
Title:
[Ubuntu 24.04] Somtimes unable to exit 'fwupd' install excution via
That regression isn't real. Looks like an infra problem.
0s autopkgtest [15:16:00]: starting date and time: 2024-08-23 15:16:00+
0s autopkgtest [15:16:00]: git checkout: fd3bed09 nova: allow more retries
for quota issues
0s autopkgtest [15:16:00]: host
juju-7f2275-prod-proposed-migratio
Verified that ESP is still being identified properly on my test systems.
❯ sudo fwupdtool esp-list
Loading… [ ]15:24:50.821
FuHistoryLoading…
[** ]
Selected volume: /org/freedesk
KC - Yes, I've already uploaded it to unapproved queue. It's waiting
for SRU team member review (see comment #8).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076151
Title:
[SRU] Support new hard
Perhaps a dumb question - but why even bother to put any of the GPU
binaries in the initramfs? There should be a good enough display from
the pre-boot framebuffer that none of them should be needed with
simpledrm.
Punt i915.ko, xe.ko, amdgpu.ko, nvidia.ko out of the initramfs and let
them get loa
As this is really a development effort not a bug I've also filed it at
https://github.com/canonical/ubuntu-desktop-provision/issues/800.
** Bug watch added: github.com/canonical/ubuntu-desktop-provision/issues #800
https://github.com/canonical/ubuntu-desktop-provision/issues/800
--
You receiv
** Description changed:
- Please see offical fwupd bug report ticket and the maintainer fixed it and
commited it already
+ [Impact]
+ Please see offical fwupd bug report ticket and the maintainer fixed it and
commited it already
* https://github.com/fwupd/fwupd/issues/7593
And following
** Changed in: fwupd (Ubuntu Oracular)
Status: Fix Committed => 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/2076151
Title:
[SRU] Support new hardware system in mediatek_scalar
1 - 100 of 6894 matches
Mail list logo
