| 29 Apr 2026 |
|  brett 💕 joined the room. | 21:07:34 |
| brett 💕 | :rooms
| 21:09:30 |
| brett 💕 | w | 21:10:07 |
| brett 💕 | :edit
| 21:10:12 |
| brett 💕 | is this room still used at all?
| 21:10:30 |
| brett 💕 | hi | 21:11:21 |
 sudoforge | used in what way? you can see messages from 12 days ago, and there are 218 members in the room. so i mean, yes, it's used, but if you're really asking if it's a super active room, the answer is no. | 21:38:40 |
| 30 Apr 2026 |
|  Daniel joined the room. | 23:23:17 |
| 1 May 2026 |
|  llakala set a profile picture. | 17:12:25 |
|  nyanbinary 🏳️⚧️ left the room. | 23:19:19 |
| 2 May 2026 |
|  deniel22 joined the room. | 14:14:33 |
| 3 May 2026 |
|  AJ (they/them) changed their display name from A. (they/them) to AJ (they/them). | 18:04:23 |
| 4 May 2026 |
 [0x4A6F] |
| 18:34:31 |
| [0x4A6F] | * ```
| 18:34:46 |
|  @itoncek:matrix.org left the room. | 18:36:14 |
| [0x4A6F] | * On a framework 13 AMD AI 300 Series (with expansiuon cards - top-left USB-C, bottom-left USB-A):
`xhci_hcd 0000:c3:00.0: Refused to change power state from D0 to D3hot
I switched that USB-A Expansion card into my old 11th-gen Framework 13 without these log messages.
| 18:38:59 |
| [0x4A6F] | * On a framework 13 AMD AI 300 Series (with expansion cards - far-left(1) USB-C, near-left(2) USB-A):
`xhci_hcd 0000:c3:00.0: Refused to change power state from D0 to D3hot
I switched that USB-A Expansion card into my old 11th-gen Framework 13 without these log messages.
- https://knowledgebase.frame.work/en_us/expansion-card-functionality-on-framework-laptop-13-amd-ryzen-ai-300-series-Hy5SfMRs1l
| 18:46:37 |
| [0x4A6F] | * On a framework 13 AMD AI 300 Series (with expansion cards - far-left(1) USB-C, near-left(2) USB-A):
xhci_hcd 0000:c3:00.0: Refused to change power state from D0 to D3hot
I switched that USB-A Expansion card into my old 11th-gen Framework 13 without these log messages.
- https://knowledgebase.frame.work/en_us/expansion-card-functionality-on-framework-laptop-13-amd-ryzen-ai-300-series-Hy5SfMRs1l
| 18:52:15 |
| sudoforge | i think this is a pretty well-documented issue. to explain the error message, what's happening is that the kernel is trying to put the USB controller into a low power state (D3hot) but the hardware is refusing because it's still in an active state (D0). i'm pretty sure this is a power mgmt or firmware issue that FW is aware of (and hopefully working on); perhaps we can get an update here.
a workaround for you would be to adjust your port layout. because the USB-A expansion card has higher power draw in ports 1 and 3 you pretty much want to keep it in ports 3 or 4. no idea if you'll encounter the same issue in port 4 (but presumably, you would). so... i guess at the end of the day, you can either ignore the error, or make the leap into the modern era and converge on USB-C everywhere :P
| 20:58:25 |
| 7 May 2026 |
 Daniel Schaefer (Framework) | Under what conditions does that happen? | 13:02:09 |
|  tristan957 joined the room. | 21:02:19 |
| 8 May 2026 |
 Just Some Dude | Would this be a good place to troubleshoot my framework 13 not being able to fully sleep and not being able to wake up completely from sleep without using systemctl cancel? | 02:03:37 |
| Just Some Dude | I've tried it on KDE, Gnome, and Cosmic. Happens on all 3. | 02:04:28 |
| Just Some Dude | I tried using kernelPackages_latest and the enableRedistributableFirmware options and they didnt do anything | 02:05:41 |
| sudoforge | what shows up in dmesg? | 02:09:43 |
| Just Some Dude | What would I be looking for? | 02:13:54 |
| sudoforge | error messages. | 02:27:35 |
| Just Some Dude | It looks like the only messages are from me authenticating with sudo | 02:28:59 |
| sudoforge | so, there's literally nothing going on before your systemctl cancel? | 02:29:36 |
| sudoforge | and, can you go into more detail about "not being able to fully sleep" and "not being able to wake up completely from sleep"? what are the symptoms you experience? | 02:30:16 |
