Half shocked to find the #framework13 USB-C to HDMI expansion card worked on a Mac book, saving the day in a #mozfest2025 session.
https://frame.work/pl/en/products/hdmi-expansion-card-3rd-gen
I thought it would work but never tried it before. The power of open hardware, people take note!

The HDMI (3rd Gen) Expansion Card has been reoptimized to reduce system power consumption, improving battery life. Supports HDMI 2.0b for resolutions up to 4k 60Hz, along with audio output. You can use multiple simultaneously to handle additional monitors, up to the number your processor supports.
I am experiencing very short battery life on my #Framework13 since I updated to #Fedora43. Anyone else? Tips?
[issue identified] Framework 13 keeps freezing after upgrade to Fedora 43: flip_done timed out
Edit: I’m fairly certain @exupulosion@sh.itjust.works got it right when linking it to this unresolved issue.
The title pretty much sums it up. The freezes can happen while I am not doing anything, and while no additional software is running. I don’t really know where to start with this one.
Here’s journalctl -b -1 -e from the latest crash, as I found online that this could be useful:
okt. 29 16:28:29 framework systemd[2793]: Starting systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories...
okt. 29 16:28:29 framework systemd[2793]: Finished systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories.
okt. 29 16:32:02 framework systemd[2793]: Starting flatpak-portal.service - flatpak portal...
okt. 29 16:32:02 framework systemd[2793]: Started flatpak-portal.service - flatpak portal.
okt. 29 16:32:02 framework systemd[2793]: Started app-flatpak-org.gnome.Geary-307090962.scope.
okt. 29 16:32:03 framework xdg-desktop-portal[6482]: (xdg-desktop-portal-validate-icon:2): GLib-WARNING **: 15:32:03.036: getpwuid_r(): failed due to unknown user id (1000)
okt. 29 16:32:03 framework xdg-desktop-portal[6482]: (xdg-desktop-portal-validate-icon:2): GLib-WARNING **: 15:32:03.036: Could not find home directory: $HOME is not set, and user database could not be read.
okt. 29 16:32:03 framework xdg-desktop-portal[6482]: (xdg-desktop-portal-validate-icon:2): GLib-WARNING **: 15:32:03.037: Could not find home directory: $HOME is not set, and user database could not be read.
okt. 29 16:32:03 framework kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
okt. 29 16:32:03 framework kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
okt. 29 16:32:03 framework kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
okt. 29 16:32:13 framework kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* [CRTC:80:crtc-0] flip_done timed out
okt. 29 16:33:16 framework systemd[1]: flatpak-system-helper.service: Deactivated successfully.
okt. 29 16:33:16 framework audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=flatpak-system-helper comm="systemd" exe="/usr/lib/systemd/systemd" hostnam>
journalctl -b -2 -e, just 11 minutes earlier:
okt. 29 16:22:21 framework NetworkManager[1132]: <info> [1761751341.1716] device (wlp1s0): supplicant interface state: disconnected -> interface_disabled
okt. 29 16:22:21 framework NetworkManager[1132]: <info> [1761751341.1721] device (wlp1s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
okt. 29 16:22:21 framework systemd[2911]: Starting systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories...
okt. 29 16:22:21 framework chronyd[938]: Source 172.232.132.19 offline
okt. 29 16:22:21 framework chronyd[938]: Source 194.58.202.148 offline
okt. 29 16:22:21 framework chronyd[938]: Source 172.232.157.27 offline
okt. 29 16:22:21 framework chronyd[938]: Can't synchronise: no selectable sources (4 unreachable sources)
okt. 29 16:22:21 framework chronyd[938]: Source 192.36.143.134 offline
okt. 29 16:22:21 framework NetworkManager[1132]: <info> [1761751341.1984] device (wlp1s0): set-hw-addr: reset MAC address to F4:4E:B4:15:7E:51 (unmanage)
okt. 29 16:22:21 framework systemd[2911]: Finished systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories.
okt. 29 16:22:21 framework wpa_supplicant[1272]: p2p-dev-wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
okt. 29 16:22:21 framework wpa_supplicant[1272]: p2p-dev-wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
okt. 29 16:22:21 framework wpa_supplicant[1272]: nl80211: deinit ifname=p2p-dev-wlp1s0 disabled_11b_rates=0
okt. 29 16:22:21 framework wpa_supplicant[1272]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
okt. 29 16:22:21 framework wpa_supplicant[1272]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
okt. 29 16:22:21 framework wpa_supplicant[1272]: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
okt. 29 16:22:25 framework systemd-logind[956]: Power key pressed short.
okt. 29 16:22:25 framework kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* [CRTC:80:crtc-0] flip_done timed out
okt. 29 16:22:25 framework systemd-logind[956]: Delay lock is active (UID 1000/redacted, PID 3200/gnome-shell) but inhibitor timeout is reached.
okt. 29 16:22:25 framework systemd[1]: Reached target sleep.target - Sleep.
okt. 29 16:22:25 framework systemd[1]: Starting systemd-suspend.service - System Suspend...
okt. 29 16:22:25 framework systemd[1]: user@1000.service: Unit now frozen-by-parent.
okt. 29 16:22:25 framework systemd[1]: session-2.scope: Unit now frozen-by-parent.
okt. 29 16:22:25 framework systemd[1]: user-1000.slice: Unit now frozen-by-parent.
okt. 29 16:22:25 framework systemd[1]: user.slice: Unit now frozen.
okt. 29 16:22:25 framework systemd-sleep[7487]: Successfully froze unit 'user.slice'.
okt. 29 16:22:25 framework systemd-sleep[7487]: Performing sleep operation 'suspend'...
okt. 29 16:22:25 framework kernel: PM: suspend entry (s2idle)
Any help would be greatly appreciated!
The laptop is rather new, but with the AMD Ryzen™ 5 7640U w/ Radeon™ 760M Graphics × 12 processor from the previous generation.
So I have come to my first #Linux rite of passage - I delved too deep into the terminal and messed something up. The culprit was trying to mount the drive for @mailbox_org (using instructions way over my head) to @fedora on my @frameworkcomputer.
I'll try to fix it tomorrow but I feel strangely proud to have broken something I MIGHT be able fix later....
#technology #fedora #computer #laptop #framework #framworklaptop #framework13 #tech
Eh, another discharged laptop battery. I charged my #framework13 to 100% when I woke up at 6:00. At 8 I took it with me and at 9:00 I tried to use it to prototype some software. The system was fully discharged.
I booted the older kernel but apparently something in Fedora 43 still breaks suspend.
At this rate I'm pondering another reinstall to something else. If all current kernels are broken I may go back to something like 24.04 LTS or even Windows 11.
It's the little things that break :/
Caution to anyone using Core Ultra 1 #framework13. With #fedora43 the system no longer suspends. Discharged, overheated laptop from the bag each time.
Kernel warning in journal:
spd5118 18-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
Si vous possédez un #framework, je rappel que votre secure boot n'est plus une protection suffisante depuis Juin dernier.
La vulnérabilité Hydroph0bia, n'est toujours pas corrigée.
Vous devez donc être TRÈS vigilent⋅e, surtout si vous êtes une personne "à risques".
Le risque majeur étant les travaux de Joanna Rutkowska sur la virtualisation et le risque d'infection persistante niveau processeur (ring 0 ou "moins").
https://community.frame.work/t/vulnerable-to-hydroph0bia-secure-boot-bypass-cve-2025-4275/70432

Are Framework BIOS versions vulnerable to the “Hydroph0bia” (CVE-2025-4275) secure boot bypass? Links: Researcher blog post CVE entry Insyde Security Advisory SA-2025002. The Insyde advisory gives a list of H2O BIOS kernel versions with the fix, but I’m not sure how these correlate to Framework BIOS releases. EDIT: Fixed the spelling of H2O, thanks @junaraga for the heads-up.
@FreeBSDFoundation those of us with #AMD @frameworkcomputer laptops are failing on wifi. The Ethernet card does work. The MediaTek cards are what get included in #Framework13
Support the MediaTek Wireless cards · Issue #66 · FreeBSDFoundation/proj-laptop
https://github.com/FreeBSDFoundation/proj-laptop/issues/66
> User Story As a user, I want to use the MediaTek wireless card included in my Framework laptop so that I don't have to purchase a separate USB wireless adaptor.
#MediaTek #FreeBSD #BSDAdvice #BSDHelp #WiFi #WiFi7