What is the failure mode?
Can you describe the device you are attaching, OS, failure steps to reproduce.
Sure, I posted the issue here:
I am having an issue with the dGPU locking up if I connect a display to the rear port after booting up. I run arch Linux as my main OS but also have Fedora 39 installed for further testing. The same results occur in either OS.
If I boot up with nothing connected, and then connect a display to the rear port, dmesg does show a connection like so, but the additional monitors do not work:
[ 142.939856] usb 1-2.4: new full-speed USB device number 11 using xhci_hcd
[ 143.078727] usb 1-2.4: New USB…
I have three different usb to hdmi adapters I can connect to the rear port (also the hdmi and dp expansion cards). They all act the same.
I have discovered recently that if I launch nvtop (need more testing, but probably anything that wakes it up will work), before connecting to the external port after booting up, it also works fine.
However, I noticed that it will never go back into D3cold mode again, even after rear usb is all disconnected and the dGPU is no longer in use.
Running Fedora 40 beta, and fwupdmgr doesn’t seem to see the update as available:
Determined that the current version is Version: 03.02
, and verified that the metadata on disk even has the FW16 firmware in there.
I have disabled secure boot (or I at least think I have, it was weirdly complicated finding the secure boot menu)
Fwupd version:
$ fwupdmgr --version
compile com.hughsie.libxmlb 0.3.17
compile org.freedesktop.Passim 0.1.5
compile com.hughsie.libjcat 0.2.1
compile org.freedesktop.fwupd 1.9.16
runtime org.freedesktop.fwupd-efi 1.4
compile org.freedesktop.gusb 0.4.8
runtime org.freedesktop.Passim 0.1.5
runtime org.freedesktop.gusb 0.4.8
runtime com.hughsie.libjcat 0.2.1
runtime org.kernel 6.8.4-300.fc40.x86_64
runtime org.freedesktop.fwupd 1.9.16
1 Like
I have the same issue on my Framework 13, see:
tldr: yes
$ fwupdmgr get-remotes
Framework Laptop 13 (AMD Ryzen 7040Series)
│
├─Vendor (Automatic):
│ Remote ID: vendor-directory
│ Type: directory
│ Keyring: none
│ Enabled: true
│ Priority: 1000
│ Filename: /usr/share/fwupd/remotes.d/vendor/firmware
│ Filename Source: /etc/fwupd/remotes.d/vendor-directory.conf
│
├─Linux Vendor Firmware Service (testing):
│ Remote ID: lvfs-testing
│ …
I filed a bug report for it:
opened 04:35PM - 09 Apr 24 UTC
bug
**Describe the bug**
On my Framework 13 AMD running Fedora 39 with BIOS 3.03, t… he 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](https://github.com/fwupd/fwupd/files/14921548/fwupdtool.log)
**Steps to Reproduce**
1. `fwupdmgr enable-remote lvfs-testing`
2. `fwupdmgr refresh --force`
3. `fwupdmgr get-updates`
4. `fwupdmgr update`
**Expected behavior**
3.05 beta BIOS showing up as an update.
**fwupd version information**
```fwupdmgr --version
compile com.hughsie.libxmlb 0.3.17
compile com.hughsie.libjcat 0.2.1
compile org.freedesktop.fwupd 1.9.16
runtime org.freedesktop.fwupd-efi 1.4
compile org.freedesktop.gusb 0.4.8
runtime com.hughsie.libjcat 0.2.1
runtime org.freedesktop.gusb 0.4.8
runtime org.freedesktop.fwupd 1.9.16
runtime org.kernel 6.8.4-200.fc39.x86_64```
Please note how you installed it (`apt`, `dnf`, `pacman`, source, etc):
I believe it was installed OOTB in Fedora 39. Otherwise, via dnf.
<summary>**fwupd device information**</summary>
Please provide the output of the fwupd devices recognized in your system.
```
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
```
</details>
**System UEFI configuration**
Please provide the output of the following commands:
```
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
```
```shell
efivar -l | grep fw
```
Above command returns empty.
```
sudo tree /boot
/boot
├── config-6.7.10-200.fc39.x86_64
├── config-6.7.11-200.fc39.x86_64
├── config-6.8.4-200.fc39.x86_64
├── efi
│ ├── EFI
│ │ ├── BOOT
│ │ │ ├── BOOTIA32.EFI
│ │ │ ├── BOOTX64.EFI
│ │ │ ├── fbia32.efi
│ │ │ └── fbx64.efi
│ │ └── fedora
│ │ ├── BOOTIA32.CSV
│ │ ├── BOOTX64.CSV
│ │ ├── gcdia32.efi
│ │ ├── gcdx64.efi
│ │ ├── grub.cfg
│ │ ├── grubia32.efi
│ │ ├── grubx64.efi
│ │ ├── mmia32.efi
│ │ ├── mmx64.efi
│ │ ├── shim.efi
│ │ ├── shimia32.efi
│ │ └── shimx64.efi
│ ├── mach_kernel
│ └── System
│ └── Library
│ └── CoreServices
│ └── SystemVersion.plist
├── grub2
│ ├── fonts
│ │ └── unicode.pf2
│ ├── grub.cfg
│ └── grubenv
├── initramfs-0-rescue-f430515d1e424da0aa37ee30fe09544e.img
├── initramfs-6.7.10-200.fc39.x86_64.img
├── initramfs-6.7.11-200.fc39.x86_64.img
├── initramfs-6.8.4-200.fc39.x86_64.img
├── loader
│ └── entries
│ ├── f430515d1e424da0aa37ee30fe09544e-0-rescue.conf
│ ├── f430515d1e424da0aa37ee30fe09544e-6.7.10-200.fc39.x86_64.conf
│ ├── f430515d1e424da0aa37ee30fe09544e-6.7.11-200.fc39.x86_64.conf
│ └── f430515d1e424da0aa37ee30fe09544e-6.8.4-200.fc39.x86_64.conf
├── lost+found
├── symvers-6.7.10-200.fc39.x86_64.xz -> /lib/modules/6.7.10-200.fc39.x86_64/symvers.xz
├── symvers-6.7.11-200.fc39.x86_64.xz -> /lib/modules/6.7.11-200.fc39.x86_64/symvers.xz
├── symvers-6.8.4-200.fc39.x86_64.xz -> /lib/modules/6.8.4-200.fc39.x86_64/symvers.xz
├── System.map-6.7.10-200.fc39.x86_64
├── System.map-6.7.11-200.fc39.x86_64
├── System.map-6.8.4-200.fc39.x86_64
├── vmlinuz-0-rescue-f430515d1e424da0aa37ee30fe09544e
├── vmlinuz-6.7.10-200.fc39.x86_64
├── vmlinuz-6.7.11-200.fc39.x86_64
└── vmlinuz-6.8.4-200.fc39.x86_64
```
**Additional questions**
- Operating system and version: Fedora 39
- Have you tried rebooting? Yes, multiple times
- Is this a regression? No
- Are you using an NVMe disk? Yes
- Is secure boot enabled? Yes
- Is this a Lenovo system with 'Boot Order Lock' turned on in the BIOS?
1 Like
Thanks
I managed to get it working by deleting everything in the var folder, disabling all remotes (including one called vendor-directory
), then enabled lvfs
& lvfs-testing
, did a refresh, and then suddenly it worked!
I suspect something got into a weird state, and fwupd just went stupid.
EDIT: the fwupd’s var folder. /var/lib/fwupd/
not the whole /var
folder
1 Like
I also had a similar question regarding the Graphics Driver as another posted in the AMD FW13 BIOS/Driver thread.
Is there any advantage to installing the Framework provided GPU/Adrenalin driver that’s on the 23.X major version vs the driver available from AMD on the 24.X versioning? Guaranteed compatibility, performance, something else?
Does the version included in the Framework bundle include the fix for the “Display frozen after smart MUX switching” issue reported in the 6th and 8th FW16 updates? Is that fix going to be only available in the FW version of the driver and will we have to continually look to FW for the updated versions to include the fix or is that fix going to be rolled into all new drivers available directly from AMD, and does the 24.x version available directly from them include it?
1 Like
Are all new machines shipped with latest stable BIOS? I ask, because assuming this BIOS goes to stable in the next couple of weeks, I’m in Batch 12, so curious if it’s likely I’ll be getting this or not.
5 Likes
mine (Batch 8 wave 2??) was 3.02 i immediately updated to 3.03 as i plan on installing the 2280 ssd today or tomorrow.
(running OS on the 2230)
Now batch 12 i would assume 3.03 would be final & no longer beta by then but it only took like 10 mins if that to update.
1 Like
Folks, it is immensely helpful for Linux users to include their distro and fwupdmgr --version
Editing existing posts with these details works.
Thanks
5 Likes
Nickolas_Grigoriadis:
Running Fedora 40 beta, and fwupdmgr doesn’t seem to see the update as available:
Determined that the current version is Version: 03.02
, and verified that the metadata on disk even has the FW16 firmware in there.
I have disabled secure boot (or I at least think I have, it was weirdly complicated finding the secure boot menu)
Appreciate the details. Did you do the following:
fwupdmgr enable-remote lvfs-testing
fwupdmgr refresh --force
fwupdmgr get-updates
fwupdmgr update
2 Likes
jared_kidd:
I have three different usb to hdmi adapters I can connect to the rear port (also the hdmi and dp expansion cards). They all act the same.
I have discovered recently that if I launch nvtop (need more testing, but probably anything that wakes it up will work), before connecting to the external port after booting up, it also works fine.
However, I noticed that it will never go back into D3cold mode again, even after rear usb is all disconnected and the dGPU is no longer in use.
Hi @jared_kidd ,
I’d like you to get this into a ticket as I feel like there may be additional factors. A bit warning, we do not actively test against Arch, however, I’d like to get logs from you and see if we can spot the issue, repro again with you testing a few different things.
When creating the ticket, please link to this thread and mention this is for Matt Hartley and to be sent directly to me please.
4 Likes
Kelton_Page:
I applied the beta bios v3.03 on Friday and have had no issues except today Sunday after gaming on rpcs3 for ~ 1Hr I got a random reboot. No warning or Bsod. I went into event viewer and got an error anout windows boot environment failed to load the HSP firmware (the file %hs does not exist). Then after thay error there is an error reporting that the previous shutdown (which I was gaming and everything was working fine then) was unexpected. Weird thing is the shutdown says thay it happened 4 mines befoe the actual reboot did. Then after that there js a Critical error sayibf the system has rebooted without cleanly shutting down. I hope this helps, and if any more information is needed feel free to reach out.
Hi @Kelton_Page , I’d like you to get this into a ticket as I feel like there may be additional factors.
While I am exclusively Linux support, I would like to get this ticket in front of our engineering team and will be the one connecting everyone in the ticket.
When creating the ticket, please link to this thread and mention this is for Matt Hartley and to be sent directly to me please.
2 Likes
Arazil
April 12, 2024, 3:42am
38
Has anyone encountered issues connecting with the USB-C enabled iPhone 15 Pro Max (or similar) after updating to 3.03? I am encountering an issue where the USB connection goes through an infinite connection/disconnection cycle after plugging it in via a standard USB-C to USB-C cable. This behavior occurs regardless of laptop power state (the behavior continues when the laptop is powered off). I have tried different cables and different ports but nothing resolves the issue. I sent a request in to support to have them look into the issue but it’s been a slow process of gathering data so far.
1 Like
As mentioned I managed to get it working by (as root):
Deleting everything in /var/lib/fwupd/
.
dnf update --refresh
dnf reinstall fwupd
fwupdmgr disable-remote lvfs-testing
fwupdmgr disable-remote lvfs
fwupdmgr disable-remote vendor-directory
fwupdmgr enable-remote lvfs
fwupdmgr enable-remote lvfs-testing
fwupdmgr refresh --force
fwupdmgr update
I suspect fwupd might have gotten confused as I just upgraded from F39 to F40, and I have no idea what vendor-directory
is about, but I suspect disabling that resolved things for me…
There seem to have been one or more bugs in fwupd
or rather, the libxmlb
depedency for it. See: No testing BIOS update available for Framework 13 · Issue #7060 · fwupd/fwupd · GitHub . The updated libxmlb
(3.18) is already in Fedora to fix this. There might be more issues in fwupd
though, there’s still discussion going on in a similar ticket.
Magic
April 12, 2024, 11:34am
41
Who can the userbase engage with at Microsoft to change this?
1 Like
Magic
April 12, 2024, 11:36am
42
Yes, same problem on Windows with an iPhone 15 Pro.
Complains there’s not enough power and disconnects. Then repeats the cycle.
1 Like
Magic:
Yes, same problem on Windows with an iPhone 15 Pro.
Complains there’s not enough power and disconnects. Then repeats the cycle.
There is a seperate thread about iPhones not connecting, from way back.
1 Like
Arazil
April 12, 2024, 2:48pm
44
It is still an active problem problem with the Framework 13 laptops . I could not find a corresponding Framework 16 thread before posting here. It seems like there’s something going on with the Framework USB C negotiation process.
1 Like
Thank you for the response. I had submitted a support ticket a couple days ago, but unfortunately I can’t find any ticket number or way of referencing it for you. I have just responded to the support agent’s email request for further information.
And to note on OS, I am doing any troubleshooting with Framework on Fedora 39 instead of Arch.