Ha, un petit retour d'utilisation à mon niveau très personnel de mon laptop #Framework13.
J'avais lu pas mal de mauvais retours sur la qualité de leurs firmwares, et du faible nombre de mises à jour.
Et bien peut-être que les choses ont évoluées. C'est vrai, j'ai bien eu des problèmes de mon côté avec leurs firmwares.
Mais je me dois aussi d'être honnête : je n'ai jamais eu un laptop avec des mises à jour aussi régulières, et qui changent vraiment les choses.
I'm a laptop weirdo and that's why I like my new Framework 13
https://blog.matthewbrunelle.com/im-a-laptop-weirdo-and-thats-why-i-like-my-new-framework-13/
#HackerNews #laptopweirdo #Framework13 #techenthusiast #innovation #laptoplove
That’s a bit of a weird one. The latest kernel 6.17.8 update for @fedora 43 is breaking the keyboard input during boot on my @frameworkcomputer 13. I can’t enter the encryption password to continue booting.
Rolling back fixes it (thank god for atomic distros)
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?
[solved] Framework 13 keeps freezing after upgrade to Fedora 43: flip_done timed out
Edit: Thanks to @save_the_humans@leminal.space for pointing to this guide by @stdevel@chaos.social—I haven’t had further freezes since following the steps in it:
It is sufficient to add the boot parameter amdgpu.dcdebugmask=0x10 in the GRUB configuration (/etc/default/grub):
Parleur
Hacker News
Jazzynupe
Didier Malenfant
Joel Wirāmu, Pauling
Ian Forrester | @cubicgarden
Tommi 🤯
cabbage...
GRUB_CMDLINE_LINUX="... amdgpu.dcdebugmask=0x10"
...
Afterwards the GRUB configuration must be updated and the computer must be rebooted:
# grub2-mkconfig -o /boot/grub2/grub.cfg
# reboot
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
Sean Bala