Mario Limonciello
Mario Limonciello
Hmm, if you need to go to the bridge firmware **first** isn't this totally expected behavior? You have to run the update twice to go normal -> bridge -> update.
I think what you're trying to do makes a lot of sense, but I also think that we need a little bit of other work in the daemon to do...
> To be clear the update package I have is working and does apply both updates in a single update step successfully. > > My only issue is with the...
Modify the systemd unit for fwupd.service to add `-vv` to the ExecStart command. Then reload the service and restart daemon. Then run your update sequence and save the journal output...
Ah I see. It did treat it as a composite two step update, but I think it's ONLY because you have both releases in a single cab file. ```c Jan...
Oh yeah! That certainly makes this clearer. @mjekdi can you please add that to both of your releases and then test the branch I pushed?
I slept on it some and I think we'll go with @hughsie's approach instead as it lets us do single CAB releases with bridges. You can test with his linked...
With the approach Richard did I think we can do it without that flag. Just try main now.
I think we need the verbose log again to see what else stands out.
> FWIW, AMD decided to finally default power profile to "3D_FULL_SCREEN" from Linux 6.13 FYI - this policy is for dGPU only.