Ok, so now I changed the systemd config to give it 30 minutes to start
and while I was at it I added "-vv" to the Exec line (it is in the same
file) just out of curiosity whether it would work despite my scepticism.
It does so here is the log. And now it makes me think that tpm isn't
going to be th
Ok, here is the complete section of log file with fwupd messing around
with nouveau. I suspect the bug is in nouveau. Requests from userspace
shall not cause kernel to crash.
** Attachment added: "Complete (and huge) log with fwupd messing with nouveau"
https://bugs.launchpad.net/ubuntu/+sourc
> 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?
Unfortunately, no. The ASUS TUF Gaming laptop may need it to run the
display. I suspect that because long ago the nvidia hardware got reset
and the system could not recover from that cleanly. The result was a
computer with dead screen bu
Ok, now the thing got running and I got the plugin list but I have no
idea which plugin to disable. I tried amd_gpu and nvme but no luck.
What can I glean from the logs is that the "drm_dp_aux_dev" is the
troublemaker here but I have no freaking idea what plugin uses that.
After some DuckDuckGoing
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
Well it appears I caught something:
2025-02-17T18:52:07.826887+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU
fwupd[55170]: 17:52:07.824 FuBackendfailed to open device
/sys/devices/virtual/drm_dp_aux_dev/drm_dp_aux0: DPCD read failed: failed to
read 14: Connection timed out
2025-02-
Well, getting the name of the TPM module turns out to be harder than I
expected. The documentation says "Allow blocking specific plugins by
name. Use fwupdmgr get-plugins to get the list of plugins." But running
that command tries to start fwupd via systemd which has no hope of
working so I need to
Mario Limonciello (superm1): Great, we are making some progress now.
Unfortunately I have to wait again because that stupid fwupd is stuck in
that stupid wait (again). Hopefully after I learn about this
DisablePlugins key, it will unstuck itself.
--
You received this bug notification because you
Ok, I have more info now.
1. Adding `-vv` to the Exec line in fwupd.service and posting the new
log will probably not help. The problem is that fwupd takes 20 minutes
to start.
2. There is something rotten in what fwupd is doing. During the 20
minute startup pause the syslog is replete with the D
10 matches
Mail list logo
