-
Notifications
You must be signed in to change notification settings - Fork 412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No testing BIOS update available for Framework 13 #7060
Comments
You're missing all the "interesting" output from |
Woops, should be there now. |
OK, one more thing. Can you please run |
And can you please attach |
Here you go, my good sir. |
Hmm, looks like no components in the silo to me. This seems pretty bad @hughsie.
|
Seems to be tied specifically to zstd.. |
Someone on the Framework forums had a similar issue and reportedly got it working again by clean up the var folder and disabling and enabling all remotes. I may try that, but I'm also willing to further assist with tracking down this possible bug, if there's anything I can do. |
Seems to be something funky about decoding the file:
The last chunk of decoded data seems to be |
It's specifically with libxmlb's decompression. Running |
I've got an idea; one sec. |
Regression from hughsie/libxmlb@20eeebd perhaps? |
This partially reverts 20eeebd, but instead moves the success check to after we update bytes_read and bytes_written. Fixes fwupd/fwupd#7060
I think so; hughsie/libxmlb#170 is probably the right fix and seems to work with everything I have to throw at it. |
If that works I can do a new libxmlb tarball on Thursday. |
Yeah that works for me. |
This partially reverts 20eeebd, but instead moves the success check to after we update bytes_read and bytes_written. Fixes fwupd/fwupd#7060
hmm, updated to libxmlb-0.3.18 and my fwupdmgr still shows: |
|
Have you restarted the service since upgrading and refreshed metadata since then? |
And also what version of |
Yes to both Qs above. Rebuilt fwupd against new libxlmb too(on Gentoo) |
Okay, please open another issue and attach daemon logs with From the client run the refresh cycle and let's see what it shows. Please also attach build logs for fwupd. |
|
oh, new issue. OK will do |
Yes please
Not the client; the daemon. like modify |
Affects FC40 as well (0.3.18 has not been pushed to testing).
|
From an upstream perspective it's finished. I suggest advocating for that change in the matching RH bugzilla. |
It's been in testing for a while: https://bodhi.fedoraproject.org/updates/FEDORA-2024-a960990153 |
This still doesn't seem to work for me. I installed the RPM from the link above, and fwupdmgr still doesn't seem to recognize the update. I have lvfs-testing enabled. I made sure to restart after installing the libxmlb update.
|
Try manually deleting the cache in |
I deleted it, but still not seeing any changes with respect to the behavior. I have an empty |
And then restart the service |
That was it. Should've followed the linked issue a little better. Thanks for your support once again 😄. fwupd/lvfs are truly life changing pieces of software. |
It's in updates-testing not updates ; yes my bad I thought I had enabled
testing on this machine.
…On Wed, 17 Apr 2024 at 09:02, Tristan Partin ***@***.***> wrote:
That was it. Should've followed the linked issue a little better. Thanks
for your support once again 😄. fwupd/lvfs are truly life changing pieces
of software.
—
Reply to this email directly, view it on GitHub
<#7060 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACF5L2472JESAZLKLKSTALY5WGV3AVCNFSM6AAAAABF65FI4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJZHEYTOMRYG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Describe the bug
On my Framework 13 AMD running Fedora 39 with BIOS 3.03, the 3.05 beta BIOS is not available.
lvfs-testing
is enabled. The laptop is plugged into AC.Output of
sudo fwupdtool update -vv
:fwupdtool.log
Steps to Reproduce
fwupdmgr enable-remote lvfs-testing
fwupdmgr refresh --force
fwupdmgr get-updates
fwupdmgr update
Expected behavior
3.05 beta BIOS showing up as an update.
fwupd version information
fwupdmgr get-devices --show-all-devices
Framework Laptop 13 (AMD Ryzen 7040Series)
│
├─AMD Ryzen 5 7640U w/ Radeon 760M Graphics:
│ │ Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ │ Current version: 0x0a704103
│ │ Vendor: Advanced Micro Devices, Inc.
│ │ GUIDs: 2a1df9de-fe02-59c8-8af1-32c8bb011f94 ← CPUID\PRO_0&FAM_19&MOD_74
│ │ 5a4bca32-6547-584f-bb36-920d9adede25 ← CPUID\PRO_0&FAM_19&MOD_74&STP_1
│ │ Device Flags: • Internal device
│ │
│ ├─Graphics Processing Unit (GPU):
│ │ │ Device ID: 83eba1fa14bdefee1f6b4bcf06069b298e1c338f
│ │ │ Summary: AMD AMD_PHOENIX_GENERIC
│ │ │ Current version: 022.012.000.024.000001
│ │ │ Vendor: Advanced Micro Devices, Inc. [AMD/ATI] (PCI:0x1002)
│ │ │ GUID: 6c23af4f-d6cd-5ffc-a502-0b85e472e7cb ← AMD\113-PHXGENERIC-001
│ │ │ Device Flags: • Internal device
│ │ │
│ │ └─NE135FBM-N41:
│ │ Device ID: aec1a869eb0df71b7cea6b3ac71d39b830faf164
│ │ GUID: ace3bb34-1bbb-5a5f-9694-73c4cede9692 ← DRM\VEN_BOE&DEV_0BCA
│ │ Device Flags: • Internal device
│ │
│ ├─Secure Processor:
│ │ Device ID: c54ab0237d7a8db8c717b68e0be78e4374a2a079
│ │ Current version: 00.2d.00.74
│ │ Bootloader Version:00.2d.00.74
│ │ Vendor: Advanced Micro Devices, Inc. (PCI:0x1022)
│ │ GUIDs: 9eb6a793-7f97-5fb5-b49c-139d2ce3ee46 ← PCI\VEN_1022&DEV_15C7
│ │ 2e4eb727-a7c8-5eba-80cd-553b8d796d80 ← PCI\VEN_1022&DEV_15C7&SUBSYS_F1110006
│ │ Device Flags: • Internal device
│ │
│ ├─System Management Unit (SMU):
│ │ Device ID: db0330716216c629bb2c07256e5d018f499eb6ce
│ │ Summary: Microcontroller used within CPU/APU program 0
│ │ Current version: 76.70.0
│ │ Vendor: Advanced Micro Devices, Inc.
│ │ GUID: 3ac3159e-6eef-5f6b-bc8d-67686b238747 ← /sys/devices/platform/AMDI0009:00
│ │ Device Flags: • Internal device
│ │
│ └─TPM:
│ Device ID: c6a80ac3a22083423992a3cb15018989f37834d6
│ Summary: TPM 2.0 Device
│ Current version: 6.3.1.610
│ Vendor: Microsoft (TPM:MSFT)
│ GUIDs: 2a65d4b6-60a0-5e8c-acfa-d86cc3cbe4c3 ← TPM\VEN_MSFT&DEV_0001
│ 31a7bb1b-f5e1-53ff-b0e5-8692a21caed6 ← TPM\VEN_MSFT&MOD_Pluton.TPM.A
│ 5bea8d58-c840-513e-a5ad-0184cbaa9821 ← TPM\VEN_MSFT&DEV_0001&VER_2.0
│ e02519c6-9139-5de8-89d4-9dca2f5c3b66 ← TPM\VEN_MSFT&MOD_Pluton.TPM.A&VER_2.0
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device can recover flash failures
│ • Full disk encryption secrets may be invalidated when updating
│ • Signed Payload
│
├─Fingerprint Sensor:
│ Device ID: 23ec719b6aabc2d2dac5176c232f0da7a21881b0
│ Summary: Match-On-Chip fingerprint sensor
│ Current version: 01000334
│ Vendor: Goodix (USB:0x27C6)
│ Install Duration: 10 seconds
│ Serial Number: UID097F42EB_XXXX_MOC_B0
│ GUID: 1e8c8470-a49c-571a-82fd-19c9fa32b8c3 ← USB\VID_27C6&PID_609C
│ Device Flags: • Updatable
│ • Device stages updates
│ • Device can recover flash failures
│ • Signed Payload
│
├─GPIO controller:
│ Device ID: f685512aa07369c9e77742acef941d779d31e766
│ GUID: 37b440a9-2473-5087-a39b-db84f32a8ed8 ← GPIO\ID_AMDI0030:00
│
├─System Firmware:
│ │ Device ID: 1e4fa9cea0b89e613370cf9657ffa0b6d3f37fec
│ │ Summary: UEFI System Resource Table device (Updated via caspule-on-disk)
│ │ Current version: 771
│ │ Minimum Version: 1
│ │ Vendor: Framework (DMI:INSYDE Corp.)
│ │ Update State: Success
│ │ GUID: b5f7dcc1-568c-50f8-a4dd-e39d1f93fda1
│ │ Device Flags: • Internal device
│ │ • Updatable
│ │ • System requires external power source
│ │ • Needs a reboot after installation
│ │ • Cryptographic hash verification is available
│ │ • Device is usable for the duration of the update
│ │ Device Requests: • Message
│ │
│ └─UEFI dbx:
│ Device ID: 362301da643102b9f38477387e2193e57abaa590
│ Summary: UEFI revocation database
│ Current version: 371
│ Minimum Version: 371
│ Vendor: UEFI:Linux Foundation
│ Install Duration: 1 second
│ GUIDs: f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
│ 115f7cac-f705-5d34-9a47-37177c3e8514 ← UEFI\CRT_B38FAD316F525F27B27A21B486456C3E4279748BF16893827BF16FE659C0F75E&ARCH_X64
│ Device Flags: • Internal device
│ • Updatable
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Only version upgrades are allowed
│ • Signed Payload
│
├─UEFI Platform Key:
│ Device ID: 6924110cde4fa051bfdc600a60620dc7aa9d3c6a
│ Summary: frame.work-LaptopAMDPK
│ GUID: c701846d-5461-5c19-a7ae-2d89b2f44c14 ← UEFI\CRT_D610D8205624E644D9435383826B2DBF7298859C
│
└─WD BLACK SN770 1TB:
Device ID: 03281da317dccd2b18de2bd1cc70a782df40ed7e
Summary: NVM Express solid state drive
Current version: 731100WD
Vendor: Sandisk Corp (NVME:0x15B7)
Serial Number: 2334H2403142
GUIDs: 1524d43d-ed91-5130-8cb6-8b8478508bae ← NVME\VEN_15B7&DEV_5017
87cfda90-ce08-52c3-9bb5-0e0718b7e57e ← NVME\VEN_15B7&DEV_5017&SUBSYS_15B75017
914bfa00-b683-532c-8c3c-71a59e7ae800 ← WD_BLACK SN770 1TB
Device Flags: • Internal device
• Updatable
• System requires external power source
• Needs a reboot after installation
• Device is usable for the duration of the update
efibootmgr -v
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0005,0001,2001,2002,2003
Boot0001* Fedora HD(1,GPT,6975d142-18c0-4bf5-9dfa-dba4622a2aab,0x800,0x12c000)/\EFI\fedora\shim.efiRC
dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 c0 12 00 00 00 00 00 42 d1 75 69 c0 18 f5 4b 9d fa db a4 62 2a 2a ab 02 02 / 04 04 2e 00 5c 00 45 00 46 00 49 00 5c 00 66 00 65 00 64 00 6f 00 72 00 61 00 5c 00 73 00 68 00 69 00 6d 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
data: 52 43
Boot0002* EFI PXE 0 for IPv4 (0C-37-96-6A-73-67) PciRoot(0x0)/Pci(0x8,0x3)/Pci(0x0,0x4)/USB(1,0)/MAC(0c37966a7367,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)RC
dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 03 08 / 01 01 06 00 04 00 / 03 05 06 00 01 00 / 03 0b 25 00 0c 37 96 6a 73 67 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 03 0c 1b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
data: 52 43
Boot0003* Windows Boot Manager HD(2,GPT,26bedf9f-4b32-435d-98fb-4e9e25ce2800,0xa00800,0x82000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000048000100000010000000040000007fff0400
dp: 04 01 2a 00 02 00 00 00 00 08 a0 00 00 00 00 00 00 20 08 00 00 00 00 00 9f df be 26 32 4b 5d 43 98 fb 4e 9e 25 ce 28 00 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 48 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0004* Windows Boot Manager HD(2,GPT,26bedf9f-4b32-435d-98fb-4e9e25ce2800,0xa00800,0x82000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000048000100000010000000040000007fff0400
dp: 04 01 2a 00 02 00 00 00 00 08 a0 00 00 00 00 00 00 20 08 00 00 00 00 00 9f df be 26 32 4b 5d 43 98 fb 4e 9e 25 ce 28 00 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 48 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0005* Fedora HD(1,GPT,6975d142-18c0-4bf5-9dfa-dba4622a2aab,0x800,0x12c000)/\EFI\fedora\shimx64.efi
dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 c0 12 00 00 00 00 00 42 d1 75 69 c0 18 f5 4b 9d fa db a4 62 2a 2a ab 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 66 00 65 00 64 00 6f 00 72 00 61 00 5c 00 73 00 68 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot2001* EFI USB Device RC
dp: 7f ff 04 00
data: 52 43
Boot2002* EFI DVD/CDROM RC
dp: 7f ff 04 00
data: 52 43
Boot2003* EFI Network RC
dp: 7f ff 04 00
data: 52 43
Above command returns empty.
Additional questions
The text was updated successfully, but these errors were encountered: