Device Information
System Model or SKU
Please select one of the following
BIOS VERSION
Reproduced on BIOS 03.07 and 04.03
DIY Edition information
Memory: Crucial DDR5 RAM 32GB 5600MHz SODIMM CL46 - CT32G56C46S5 x2
Storage: Crucial P3 1TB M.2 PCIe Gen3 NVMe Internal SSD - CT1000P3SSD8
Port/Peripheral information
- USB-C Expansion Card
- HDMI (3rd Gen) Expansion Card
- USB-A Expansion Card
- USB-C Expansion Card
- USB-C Expansion Card
- USB-A Expansion Card
Standalone Operation (Laptop Only)
Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?
Describe the bug
The laptop can end up in a state where USB-PD negotiation fails on all chargers, leading to the laptop not charging (i.e. charging at 0W) when on or in sleep mode. This started occurring when I updated from BIOS 3.05 to 4.03 at the end of January. I have been troubleshooting this and collecting data since then.
Steps To Reproduce
This is a complicated issue that is tough to reproduce consistently. The best way to describe it is to categorise the working of the laptop into two states: "good" and "fail". I have collected data using various chargers in both states so that the difference can be compared.
When testing, I used an Anker Prime 27,650mAh Power Bank (250W) running firmware v1.7.0, an Anker Laptop Charger (140W, 4-Port, PD 3.1) and the official Framework 180W charger. For each of the scenarios below, I tested these with the USB-C to USB-C cable that came with the Framework 180W charger, a 240W Anker 765 USB-C to USB-C Cable and the 240W USB-C to USB-C cable that comes with the Anker Laptop Charger. The USB-C cable used did not make a difference.
I additionally have a Dell WD19S USB-C Dock running Package Firmware Version 01.01.01.01 (WD19S MST version 05.07.08, Gen1 Hub version 01.23, Gen2 Hub version 01.62, WD19S Dock Ec version 01.01.00.15), which can supply 90W via USB PD 3.0.
The Anker Power Bank and Laptop Charger both have screens which display power output. For each scenario, I have provided a photo of the relevant screen, and/or a screenshot from Framework Control.
When in good state, charging works as expected.
Scenario 1: Framework 180W Charger (Good State)
Here, charging is working as expected.
Scenario 2: Dell WD19S USB-C Dock (Good State)
Here, charging is working as expected, but is slower as the dock only supplies 90W.
Scenario 3: Anker Laptop Charger (Good State)
Here, charging is working as expected.
Scenario 4: Anker Power Bank (Good State)
The Anker Power Bank has two USB-C ports: C1 and C2. They are ostensibly identical, however, I am much more likely to get power when I use C2 rather than C1. However, I have seen both supply 0W before and I have seen both supply 140W before. 0W being supplied by the power bank does not necessarily mean the laptop is in the fail state. The known issues on the BIOS page does state that one of the issues is that "Cannot negotiate charging for certain portable EPR power banks.", which is what I imagine is happening here. Sometimes, this negotiates to 2W, which is interesting behaviour.
I do note, however, that I never had any 0W issues with this power bank on BIOS 3.05.
In terms of making the fail state occur, I have not found a reliable way to do this. It seems to occur randomly, but is more likely to occur when the laptop is on less than 40%, and is more likely to happen after I attempt to use the Anker Power Bank. It does not happen every time after I use the power bank, however, and I have also seen it occur without using the power bank.
When in fail state, USB-PD negotiation fails, resulting in 0W charging when on or in sleep mode. This is also sometimes characterised by the battery state flipping rapidly between "Charging" and "Not Charging" in Windows, which is presumably the system rapidly connecting and disconnecting from the charger as it repeatedly tries and fails to negotiate charging.
Once it is in fail state, the best way to resolve it is to go into the BIOS and disconnect the battery, then wait a few minute before turning the computer back on. I believe this resets the EC. This does not always resolve it, but works the vast majority of the time.
Scenario 5: Framework 180W Charger (Fail State)
The computer is discharging here despite being plugged in.
Scenario 6: Anker Power Bank (Fail State)
The computer is discharging here despite being plugged in, and the power bank is supplying 0W. There is no difference here in terms of what is actually happening compared to when the power bank does not supply power in good state, so the photos are the same.
However, if I hibernate the laptop and then plug it in again, the power bank supplies 88W. I am not sure why this is, and why it is capping itself at 88W when it can supply up to 140W. I imagine the negotiation is simpler when the laptop is not on, which is why it is working but not perfectly.
Scenario 7: Dell WD19S USB-C Dock (Fail State)
Interestingly, when I try to use the dock while in fail state, rather than discharging, there is just enough power supplied to keep the battery charge the same. To be honest, this behaviour baffles me.
Scenario 8: Anker Laptop Charger (Fail State)
I have also seen this occur with the Anker Laptop Charger, however I do not have any photos of this. The behaviour is the same as with the Framework charger, where the laptop is discharging despite being plugged in.
Expected behaviour
USB-PD negotiation to complete successfully every time, resulting in charging at full speed every time.
Screenshots
See Above
Operating System (please complete the following information):
- OS/Distribution: Windows 11
- Version: 25H2 (OS Build 26200.7840)
Additional context
Reverting back to BIOS 03.05 stops this issue from occurring (or, at least, I have not seen it occur on 03.05)
I have seen other reports of this issue (or similar ones) on the forums:
I also believe the following GitHub issues may be related, however none of them describe this issue directly, presumably because it is so hard to reliably reproduce: #40, #75, #174
I do not believe this is a hardware issue, as charging can work fine, I did not see this issue occur on BIOS 3.05, and there are similar reports from other users. However, I have also opened a support ticket just in case.
I am happy to collect any additional data and/or do any more testing. Please let me know.
Device Information
System Model or SKU
Please select one of the following
BIOS VERSION
Reproduced on BIOS 03.07 and 04.03
DIY Edition information
Memory: Crucial DDR5 RAM 32GB 5600MHz SODIMM CL46 - CT32G56C46S5 x2
Storage: Crucial P3 1TB M.2 PCIe Gen3 NVMe Internal SSD - CT1000P3SSD8
Port/Peripheral information
Standalone Operation (Laptop Only)
Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?
Describe the bug
The laptop can end up in a state where USB-PD negotiation fails on all chargers, leading to the laptop not charging (i.e. charging at 0W) when on or in sleep mode. This started occurring when I updated from BIOS 3.05 to 4.03 at the end of January. I have been troubleshooting this and collecting data since then.
Steps To Reproduce
This is a complicated issue that is tough to reproduce consistently. The best way to describe it is to categorise the working of the laptop into two states: "good" and "fail". I have collected data using various chargers in both states so that the difference can be compared.
When testing, I used an Anker Prime 27,650mAh Power Bank (250W) running firmware v1.7.0, an Anker Laptop Charger (140W, 4-Port, PD 3.1) and the official Framework 180W charger. For each of the scenarios below, I tested these with the USB-C to USB-C cable that came with the Framework 180W charger, a 240W Anker 765 USB-C to USB-C Cable and the 240W USB-C to USB-C cable that comes with the Anker Laptop Charger. The USB-C cable used did not make a difference.
I additionally have a Dell WD19S USB-C Dock running Package Firmware Version 01.01.01.01 (WD19S MST version 05.07.08, Gen1 Hub version 01.23, Gen2 Hub version 01.62, WD19S Dock Ec version 01.01.00.15), which can supply 90W via USB PD 3.0.
The Anker Power Bank and Laptop Charger both have screens which display power output. For each scenario, I have provided a photo of the relevant screen, and/or a screenshot from Framework Control.
When in good state, charging works as expected.
Scenario 1: Framework 180W Charger (Good State)
Here, charging is working as expected.
Scenario 2: Dell WD19S USB-C Dock (Good State)
Here, charging is working as expected, but is slower as the dock only supplies 90W.
Scenario 3: Anker Laptop Charger (Good State)
Here, charging is working as expected.
Scenario 4: Anker Power Bank (Good State)
The Anker Power Bank has two USB-C ports: C1 and C2. They are ostensibly identical, however, I am much more likely to get power when I use C2 rather than C1. However, I have seen both supply 0W before and I have seen both supply 140W before. 0W being supplied by the power bank does not necessarily mean the laptop is in the fail state. The known issues on the BIOS page does state that one of the issues is that "Cannot negotiate charging for certain portable EPR power banks.", which is what I imagine is happening here. Sometimes, this negotiates to 2W, which is interesting behaviour.
I do note, however, that I never had any 0W issues with this power bank on BIOS 3.05.
In terms of making the fail state occur, I have not found a reliable way to do this. It seems to occur randomly, but is more likely to occur when the laptop is on less than 40%, and is more likely to happen after I attempt to use the Anker Power Bank. It does not happen every time after I use the power bank, however, and I have also seen it occur without using the power bank.
When in fail state, USB-PD negotiation fails, resulting in 0W charging when on or in sleep mode. This is also sometimes characterised by the battery state flipping rapidly between "Charging" and "Not Charging" in Windows, which is presumably the system rapidly connecting and disconnecting from the charger as it repeatedly tries and fails to negotiate charging.
Once it is in fail state, the best way to resolve it is to go into the BIOS and disconnect the battery, then wait a few minute before turning the computer back on. I believe this resets the EC. This does not always resolve it, but works the vast majority of the time.
Scenario 5: Framework 180W Charger (Fail State)
The computer is discharging here despite being plugged in.
Scenario 6: Anker Power Bank (Fail State)
The computer is discharging here despite being plugged in, and the power bank is supplying 0W. There is no difference here in terms of what is actually happening compared to when the power bank does not supply power in good state, so the photos are the same.
However, if I hibernate the laptop and then plug it in again, the power bank supplies 88W. I am not sure why this is, and why it is capping itself at 88W when it can supply up to 140W. I imagine the negotiation is simpler when the laptop is not on, which is why it is working but not perfectly.
Scenario 7: Dell WD19S USB-C Dock (Fail State)
Interestingly, when I try to use the dock while in fail state, rather than discharging, there is just enough power supplied to keep the battery charge the same. To be honest, this behaviour baffles me.
Scenario 8: Anker Laptop Charger (Fail State)
I have also seen this occur with the Anker Laptop Charger, however I do not have any photos of this. The behaviour is the same as with the Framework charger, where the laptop is discharging despite being plugged in.
Expected behaviour
USB-PD negotiation to complete successfully every time, resulting in charging at full speed every time.
Screenshots
See Above
Operating System (please complete the following information):
Additional context
Reverting back to BIOS 03.05 stops this issue from occurring (or, at least, I have not seen it occur on 03.05)
I have seen other reports of this issue (or similar ones) on the forums:
I also believe the following GitHub issues may be related, however none of them describe this issue directly, presumably because it is so hard to reliably reproduce: #40, #75, #174
I do not believe this is a hardware issue, as charging can work fine, I did not see this issue occur on BIOS 3.05, and there are similar reports from other users. However, I have also opened a support ticket just in case.
I am happy to collect any additional data and/or do any more testing. Please let me know.