Zero issues so far, and I was running the beta for a week before now too.
Edit: AMD Ryzen™ 7 7840U other hardware YMMV
1 Like
@Destroya why was the tag for my hardware type removed ?
You created your thread under the wrong category, I fixed it for you.
Category ? Do you mean tag ? Surly a tag for the hardware type is right ?
We do not have the device tags under Linux subcategory.
This might be helpful : Framework Community Forums 101
Might be worth allowing them, rather than lumping Intel and AMD all together in a lump, when the experience could wildly vary ?
Without them you can’t filter for FW13, Linux, AMD for instance, can you ?
if you have any suggestions, you can share them here : Framework Community Forums - Feedback and Updates Thread
Currently, we do not have product tags under the Linux subcategory, we divide issues by the distro tags instead. Due to number of distros, it would be very challenging for folks to choose both the product tag and the distro tag.
While it’s not possible to filter issues using the tags, we actually have a template in the linux subcategories, when you create a new thread under linux subcategory, you choose the linux distro tag and you fill out the template and share additional information in your post body (such as release version, kernel, bios version and the model (AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™) since you created your thread under the wrong category (Framework Laptop 13 main category instead of Linux) you missed this template)
Hope this helps! If you have additional suggestions and feedback about categories, subcategories, tags etc, please share them in the feedback thread I shared above.
Dang, now I’m having hangs (audio keeps playing, but graphics are locked up).
This looks sus in the the jounatlctl output ?
Apr 18 13:29:09 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:10 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:10 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:10 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:10 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:11 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:11 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:11 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:11 frame rtkit-daemon[2096]: Supervising 9 threads of 6 processes of 1 users.
Apr 18 13:29:11 frame rtkit-daemon[2096]: Supervising 9 threads of 6 processes of 1 users.
Apr 18 13:29:11 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:12 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:12 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:12 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:13 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:13 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:13 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 18 13:29:13 frame kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
-- Boot 6783b95aacd24bc8ac76470c50b4b8fe --
I’ll try the 6.14.2 kernel (via mainline) and report back, as 25.04 only ships 6.14.0 which is very early.
I have the same issue and tried 6.14.2 but my system keeps freezing, I was about to check any new mesa versions to test.
Is there an easy way to test difference versions of mesa (like, as easy mainline makes testing kernels) ?
Same here 
on FW13 7640U
This looks similar to 7840U/780M: `*ERROR* [CRTC:83:crtc-1] flip_done timed out`, leads to frozen display and need to hard reboot (#4141) · Issues · drm / amd · GitLab, happens with recent stable kernels too apparently.
Hmm, maybe ? I’m using whatever(*) linux-firmware / mesa 25.04 ships, and the 6.14.2 kernel (from mainline). I have BIOS 0.0.3.7 (one of the ones that were kinda-sorta pulled a few days after release).
I’m not getting any lock up issues. I don’t use an external monitor or dock.
(*) 20250317.git1d4c88ee-0ubuntu1 & 25.0.3-1ubuntu2
Started getting lock ups last few days. Possibility it’s only happening after YouTube usage in FireFox…
And looks like the canonical way to install a more recent Mesa, doesn’t support 25.04 : kisak-mesa fresh : kisak
kernel 6.14.4 is now available from mainline so I’m going to try that, in the mean time, anyone else know another way to get a recent Mesa onto 25.04 ?
I am running Ubuntu 24.04, but have been using mainline kernels up to 6.14.4.
I have not seen the DMCUB issue. So I would probably suspect mesa more than the kernel as the cause.
I guess the other difference might be the firmware blob.
I had exactly the same issue! The system would slow down and get unusable, mostly after watching YouTube in firefox. (I’m on 24.04/standard kernel.)
For me adding amdgpu.dcdebugmask=0x10 as boot parameter in grub fixed that completely.
1 Like
I do not have any extra params :
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.14.4-061404-generic root=/dev/mapper/vgkubuntu-root ro resume=/dev/mapper/vgkubuntu-swap_1
$
With 6.14.4, but stock Mesa things do seem much more stable on Ubuntu 25.04
Has this worked for anyone else? Also getting these hangs after suspend or Youtube in Firefox (and occasionally on games)