-
Notifications
You must be signed in to change notification settings - Fork 0
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
Weird charging bugs/bahaviour with FW16 #28
Comments
tacsist
changed the title
Wierd charging bugs/bahaviour with FW16
Weird charging bugs/bahaviour with FW16
Dec 22, 2024
Just noticed that the dock and the charger are not the same for bug A (3.25 vs 3.75). Here are extended logs for the dock.
|
With the dock, the framework-systems seems to be confused with current V, idk if it's a tool bug or actual ec bug.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Device Information
System Model or SKU
Please select one of the following
BIOS VERSION
3.05
DIY Edition information
Memory: FW 2x16gb
Storage: Samsung 970 EVO Plus
Port/Peripheral information
Affects all charge capable ports with usb-c expansions (if I remember correctly, i tested with direct connection as well)
Standalone Operation
Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?
Describe the bug
In reality this could be 2 separate issues that interact with each other.
Bug A: HP dock does not provide full 100W PD supply, instead it is set to 20V, 3.25A (as reported by linux) and never switches up to 5A.
Bug B: 140W charger makes linux confused. Sensors report 0V 5A while the battery charging seems to work at full power. Running games in this state results in worse performance than 100W chargers, with dgpu clocks constantly jump between power states (mid to high?) and makes FPS jump as well.
Where it becomes weird is with the charger from bug B. Bug A I had for a long time and at some point chucked it off to HP sucking ass (it had other bugs not related). When I would connect a 2nd cable to 140w charger with nothing on the other end, the bug B would stop and instead turns into bug A.
I do posses other 100w bricks that behave correctly and do not experience this. As I remember testing, bug A happens on my thinkpad e4 running fedora with the HP dock as well. I have not tested bug B with it. The cables do not seem to matter (i have not tested many, but I did some, most cables are USB4 spec)
Steps To Reproduce
Expected behavior
Get expected PD power (20V 5A or 28V 5A). Have no silly stuff happen with dGPU performance.
Operating System (please complete the following information):
Linux 6.12.6-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 19 Dec 2024 21:29:01 +0000 x86_64 GNU/Linux
Logs
Bug A with HP dock (not full output):
Bug A with 140w charger:
Bug B with 140w charger:
Additional context
I have decided to finally stop sitting on my, at this point hardboiled, eggs and document my problems here and not just share my ramblings with @DHowett (thank you for listening <3). I do not think the dGPU could be a cause, i think it also gets confused by 0V reported. I do get the classical usci_acpi errors. I'll try to test further, but I could be AWOL. Maybe Howett can fill in some blind spots.
The text was updated successfully, but these errors were encountered: