-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Device Information
System Model or SKU
Please select one of the following
- Framework Laptop 13 (11th Gen Intel® Core™)
- Framework Laptop 13 (12th Gen Intel® Core™)
- Framework Laptop 13 (13th Gen Intel® Core™)
- Framework Laptop 13 (AMD Ryzen™ 7040 Series)
- Framework Laptop 13 (Intel® Core™ Ultra Series 1)
- Framework Laptop 16 (AMD Ryzen™ 7040 Series)
BIOS VERSION
Linux:
UEFI BIOS
Version: 03.05
Release Date: 11/13/2024
EC Firmware
Build version: "lotus_v3.4.113371-ec:227507,os:7b88e1,cmsis:4aa3ff 2024-11-13 03:10:00 lotus@ip-172-26-3-226"
RO Version: "lotus_v3.4.113371-ec:227507,os:"
RW Version: "lotus_v3.4.113371-ec:227507,os:"
Current image: RO
PD Controllers
Right (01)
Main: 0.0.30 (Active)
Backup: 0.0.30
Left (23)
Main: 0.0.30 (Active)
Backup: 0.0.30
Retimers
Unknown
CSME
Unknown
DIY Edition information
Memory: Framework Provided - DDR5-5600 - 64GB (2 x 32GB)
Storage: Samsung SSD 990 PRO 4TB
Port/Peripheral information
- [ Framework - Type C ]
- [ Framework - Type C ]
- [ Framework - Type C ]
- [ Framework - Type C ]
- [ Framework - Type C ]
- [ Framework - Type C ]
Standalone Operation
Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?
- Yes
- No
Describe the bug
For a reason I have yet to be able to determine charging the battery on ports 2,4 and 5 stops functioning. Sometimes it starts working again for reasons I also don't understand. Port one always charges the laptop though with the exact same cable and charger.
Steps To Reproduce
Steps to reproduce the behavior:
- Use laptop normally.
- Plugging a cable into 2,4 and 5 will no longer charge the laptop.
- Plugging cable into 1 will always charge laptop.
Expected behavior
Able to always charge the laptop from any ports supporting power delivery (1, 2, 4, 5)
Operating System (please complete the following information):
- Linux
- Distro: Arch
- Version: Linux avasarala 6.12.9-arch1-1 # 1 SMP PREEMPT_DYNAMIC Fri, 10 Jan 2025 00:39:41 +0000 x86_64 GNU/Linux
Additional context
Called into the support once and they had me reset the EC. That fixed the problem for a short period of time but it comes back.