Fedora 40 on the Framework Laptop 13

Leonard · April 26, 2024, 2:32pm

Just did the upgrade on my AMD Framework. So far no issues!

Gulfam_Rana_Amd · April 26, 2024, 3:10pm

Been gaming for like a week and fan is always spinning

With this upgrade my fan no longer spins even in performance mode and just gets burning hot instead

Is this the same for other people or am I trippin

Gulfam_Rana_Amd · April 26, 2024, 7:24pm

Fixed this by reinstalling the multimedia codecs posted in the original post

But just to clarify, I never did install those steam codecs with 39, but I need them to spin the fan for 40.

Could be useful for others so I will leave this here instead of delete my post

Firestorm980 · April 26, 2024, 9:23pm

Upgraded from 39 OK. I had the audio issue listed in this thread and the same fixed worked just fine. I was happy to see my HW acceleration and other things survived. Note, I did have TLP going and noticed that PPD was on again after upgrading. If you plan on using TLP, make sure you mask or remove PPD.

Edit: 12th Gen Intel i5, BTW.

Greg_Stedman · April 28, 2024, 5:09pm

Fedora 40 on 12th Gen Framework 13 i7 here. Everything was OK until a couple of days ago when the Framework fan started really blasting all the time the laptop is on, regardless of what I am doing. It isn’t anything to do with processes as far as I can tell from watching System Monitor, the temperature doesn’t seem to be going nuts, it’s just spinning the fan like mad now. Didn’t do that with Fedora 39 or with Fedora 40 until very recently, so something has changed. Any thoughts?

nadb · April 28, 2024, 5:54pm

Are you using Power Profiles Daemon? If so is it defaulting to performance?

Greg_Stedman · April 28, 2024, 8:00pm

I have tried Power Saver, Balanced and Performance power modes and I didn’t notice any difference.

However, I just installed today’s operating system updates and since then the fan has stopped going crazy. Maybe too early to be sure, but it feels like something in those latest updates has corrected whatever the problem was. I’ll report back tomorrow.

Greg_Stedman · April 29, 2024, 8:28pm

Yes, since the updates yesterday the hyperactive fan problem is no longer a problem. Strange, but good news.

dimitris · April 30, 2024, 1:39am

Does dnf history list / dnf history info <transaction> provide any clues as to which update(s) might have been involved?

kholdstare · April 30, 2024, 8:44am

I’m getting GPU freezes and hard locks again in F40, vanilla kernel and fully updated - on the plus side no idle freezes, but anything that touches VAAPI or uses hwaccel (Zoom calls especially) can reliably hard-lock the system and the graphics can’t recover.

This ffmpeg command can pretty reliably take down the system in the same way that Firefox or Zoom will occasionally:

ffmpeg -vaapi_device /dev/dri/renderD128 -i sample.mp4 -vf 'format=nv12,hwupload' -c:v hevc_vaapi -rc_mode CQP -q 30 sample_amd.mp4

Crash dmesg:

Apr 30 16:38:12 kronk kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=408367, emitted seq=408369
Apr 30 16:38:12 kronk kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process kwin_wayland pid 2122 thread kwin_wayla:cs0 pid 2193
Apr 30 16:38:12 kronk kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset begin!
Apr 30 16:38:17 kronk kernel: amdgpu 0000:c1:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x0000001A SMN_C2PMSG_82:0x00000000
Apr 30 16:38:17 kronk kernel: amdgpu 0000:c1:00.0: amdgpu: Failed to disable gfxoff!
Apr 30 16:38:20 kronk kernel: ------------[ cut here ]------------
Apr 30 16:38:20 kronk kernel: WARNING: CPU: 11 PID: 5155 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn314/dcn314_smu.c:159 dcn314_smu_send_msg_with_param+0x108/0x1b0 [amdgpu]
Apr 30 16:38:20 kronk kernel: Modules linked in: uvcvideo uvc videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev uinput rfcomm snd_seq_dummy snd_hrtimer uhid nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables qrtr bnep sunrpc binfmt_misc intel_rapl_msr intel_rapl_common edac_mce_amd kvm_amd vfat fat kvm irqbypass snd_sof_amd_acp63 snd_sof_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir mt7921e snd_sof_amd_acp snd_hda_codec_realtek mt7921_common snd_sof_pci snd_sof_xtensa_dsp snd_hda_codec_generic mt792x_lib snd_hda_codec_hdmi snd_sof mt76_connac_lib mt76 snd_hda_intel snd_sof_utils snd_soc_core snd_intel_dspcfg snd_usb_audio snd_intel_sdw_acpi snd_compress ac97_bus snd_hda_codec mac80211 snd_pcm_dmaengine snd_usbmidi_lib snd_pci_ps snd_ump snd_rpl_pci_acp6x snd_rawmidi snd_acp_pci snd_hda_core btusb snd_acp_legacy_common
Apr 30 16:38:20 kronk kernel:  mc btrtl snd_hwdep snd_pci_acp6x btintel snd_seq hid_sensor_als btbcm btmtk cros_ec_lpcs hid_sensor_trigger cros_ec snd_seq_device hid_sensor_iio_common industrialio_triggered_buffer libarc4 bluetooth snd_pcm kfifo_buf snd_pci_acp5x industrialio pcspkr wmi_bmof rapl snd_timer snd_rn_pci_acp3x thunderbolt cfg80211 snd_acp_config i2c_piix4 snd k10temp snd_soc_acpi soundcore snd_pci_acp3x rfkill amd_pmf amdtee amd_sfh tee platform_profile amd_pmc joydev loop nfnetlink zram hid_logitech_hidpp hid_logitech_dj dm_crypt amdgpu amdxcp i2c_algo_bit drm_ttm_helper ttm drm_exec crct10dif_pclmul gpu_sched crc32_pclmul crc32c_intel nvme drm_suballoc_helper polyval_clmulni drm_buddy polyval_generic nvme_core drm_display_helper r8152 video ghash_clmulni_intel ucsi_acpi mii hid_multitouch hid_sensor_hub sha512_ssse3 sha256_ssse3 sha1_ssse3 typec_ucsi ccp cec sp5100_tco typec nvme_auth wmi i2c_hid_acpi i2c_hid serio_raw ip6_tables ip_tables fuse i2c_dev
Apr 30 16:38:20 kronk kernel: CPU: 11 PID: 5155 Comm: kworker/u32:39 Not tainted 6.8.7-300.fc40.x86_64 #1
Apr 30 16:38:20 kronk kernel: Hardware name: Framework Laptop 13 (AMD Ryzen 7040Series)/FRANMDCP07, BIOS 03.05 03/29/2024
Apr 30 16:38:20 kronk kernel: Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched]
Apr 30 16:38:20 kronk kernel: RIP: 0010:dcn314_smu_send_msg_with_param+0x108/0x1b0 [amdgpu]
Apr 30 16:38:20 kronk kernel: Code: be 93 62 01 00 5d 41 5c 41 5d e9 d3 d5 ef ff 44 89 ea 48 c7 c6 58 f1 1e c1 48 c7 c7 d0 1f d5 c0 e8 5d 3c dc c1 e9 48 ff ff ff <0f> 0b 48 8b 3b b9 80 84 1e 00 44 89 e2 89 ee e8 74 74 f0 ff eb b5
Apr 30 16:38:20 kronk kernel: RSP: 0018:ffffaa664b0cf8d8 EFLAGS: 00010246
Apr 30 16:38:20 kronk kernel: RAX: 0000007522472724 RBX: ffff9b4b814ea000 RCX: 000000000000000b
Apr 30 16:38:20 kronk kernel: RDX: 000000000000877b RSI: 00000000000080ab RDI: 0000007522469fa9
Apr 30 16:38:20 kronk kernel: RBP: 000000000000000d R08: 0000000000000001 R09: 0000000000000000
Apr 30 16:38:20 kronk kernel: R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
Apr 30 16:38:20 kronk kernel: R13: 0000000000000000 R14: ffff9b4b814d78d8 R15: 0000000000000001
Apr 30 16:38:20 kronk kernel: FS:  0000000000000000(0000) GS:ffff9b5a600c0000(0000) knlGS:0000000000000000
Apr 30 16:38:20 kronk kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 30 16:38:20 kronk kernel: CR2: 00007fe705d74000 CR3: 0000000bc5422000 CR4: 0000000000f50ef0
Apr 30 16:38:20 kronk kernel: PKRU: 55555554
Apr 30 16:38:20 kronk kernel: Call Trace:
Apr 30 16:38:20 kronk kernel:  <TASK>
Apr 30 16:38:20 kronk kernel:  ? dcn314_smu_send_msg_with_param+0x108/0x1b0 [amdgpu]
Apr 30 16:38:20 kronk kernel:  ? __warn+0x81/0x130
Apr 30 16:38:20 kronk kernel:  ? dcn314_smu_send_msg_with_param+0x108/0x1b0 [amdgpu]
Apr 30 16:38:20 kronk kernel:  ? report_bug+0x16f/0x1a0
Apr 30 16:38:20 kronk kernel:  ? handle_bug+0x3c/0x80
Apr 30 16:38:20 kronk kernel:  ? exc_invalid_op+0x17/0x70
Apr 30 16:38:20 kronk kernel:  ? asm_exc_invalid_op+0x1a/0x20
Apr 30 16:38:20 kronk kernel:  ? dcn314_smu_send_msg_with_param+0x108/0x1b0 [amdgpu]
Apr 30 16:38:20 kronk kernel:  ? dcn314_smu_send_msg_with_param+0xae/0x1b0 [amdgpu]
Apr 30 16:38:20 kronk kernel:  link_set_dpms_off+0xf8/0x730 [amdgpu]
Apr 30 16:38:20 kronk kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 30 16:38:20 kronk kernel:  ? optc31_set_drr+0x128/0x1d0 [amdgpu]
Apr 30 16:38:20 kronk kernel:  dcn31_reset_hw_ctx_wrap+0x20f/0x410 [amdgpu]
Apr 30 16:38:20 kronk kernel:  dce110_apply_ctx_to_hw+0x48/0x280 [amdgpu]
Apr 30 16:38:20 kronk kernel:  dc_commit_state_no_check+0x59e/0xe00 [amdgpu]
Apr 30 16:38:20 kronk kernel:  dc_commit_streams+0x249/0x3b0 [amdgpu]
Apr 30 16:38:20 kronk kernel:  dm_suspend+0x1dd/0x1f0 [amdgpu]
Apr 30 16:38:20 kronk kernel:  amdgpu_device_ip_suspend_phase1+0x6c/0xe0 [amdgpu]
Apr 30 16:38:20 kronk kernel:  amdgpu_device_ip_suspend+0x29/0x70 [amdgpu]
Apr 30 16:38:20 kronk kernel:  amdgpu_device_pre_asic_reset+0xd0/0x2a0 [amdgpu]
Apr 30 16:38:20 kronk kernel:  amdgpu_device_gpu_recover+0x449/0xca0 [amdgpu]
Apr 30 16:38:20 kronk kernel:  amdgpu_job_timedout+0x187/0x270 [amdgpu]
Apr 30 16:38:20 kronk kernel:  drm_sched_job_timedout+0x73/0x100 [gpu_sched]
Apr 30 16:38:20 kronk kernel:  process_one_work+0x16d/0x330
Apr 30 16:38:20 kronk kernel:  worker_thread+0x273/0x3c0
Apr 30 16:38:20 kronk kernel:  ? __pfx_worker_thread+0x10/0x10
Apr 30 16:38:20 kronk kernel:  kthread+0xe5/0x120
Apr 30 16:38:20 kronk kernel:  ? __pfx_kthread+0x10/0x10
Apr 30 16:38:20 kronk kernel:  ret_from_fork+0x31/0x50
Apr 30 16:38:20 kronk kernel:  ? __pfx_kthread+0x10/0x10
Apr 30 16:38:20 kronk kernel:  ret_from_fork_asm+0x1b/0x30
Apr 30 16:38:20 kronk kernel:  </TASK>
Apr 30 16:38:20 kronk kernel: ---[ end trace 0000000000000000 ]---
Apr 30 16:38:25 kronk kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 30 16:38:25 kronk kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 30 16:38:25 kronk kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 30 16:38:25 kronk kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 30 16:38:25 kronk kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 30 16:38:25 kronk kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 30 16:38:25 kronk kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 30 16:38:25 kronk kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 30 16:38:25 kronk kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 30 16:38:25 kronk kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 30 16:38:25 kronk kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 30 16:38:25 kronk kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 30 16:38:25 kronk kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 30 16:38:25 kronk kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 30 16:38:25 kronk kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 30 16:38:25 kronk kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 30 16:38:26 kronk kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Apr 30 16:38:26 kronk kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Apr 30 16:38:26 kronk kernel: amdgpu 0000:c1:00.0: amdgpu: MODE2 reset
Apr 30 16:38:30 kronk kernel: amdgpu 0000:c1:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x0000001A SMN_C2PMSG_82:0x00000000
Apr 30 16:38:30 kronk kernel: amdgpu 0000:c1:00.0: amdgpu: Mode2 reset failed!
Apr 30 16:38:30 kronk kernel: amdgpu 0000:c1:00.0: amdgpu: ASIC reset failed with error, -62 for drm dev, 0000:c1:00.0
Apr 30 16:38:30 kronk kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset(2) failed
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset end with ret = -62
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm] Skip scheduling IBs!
Apr 30 16:38:30 kronk kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -62
Apr 30 16:38:41 kronk kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=4406, emitted seq=4408
Apr 30 16:38:41 kronk kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
Apr 30 16:38:41 kronk kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset begin!
Apr 30 16:38:41 kronk kernel: amdgpu 0000:c1:00.0: amdgpu: Failed to disallow df cstate

Hussain_Arif · April 30, 2024, 10:18am

Does wireplumber crash frequently for anyone else? It restarts itself but when it crashes during meetings, Linux disables my mic and I have to rejoin the meeting to speak again.
Same for Bluez

Michael_Wu · April 30, 2024, 5:54pm

I’ve also gotten that yesterday and today during playing a YouTube video in Firefox. Previously fine on F39.

AMD 7840U
6.8.7-300.fc40.x86_64

I’m wondering if the recently published mesa-dri-drivers 24.0.6-2.fc40 fixes the issue, but I haven’t updated yet since there’s a dependency conflict from the mesa-freeworld drivers from RPM Fusion being currently behind.

Or if mesa-freeworld 24.0.6 fixes the issue, which is currently in testing.

I might install/test it manually if it isn’t released soon — it also causes my screen (Sway) to irrecoverably freeze, though oddly I can still move my mouse cursor around. Audio still continues playing, and I can switch to another virtual terminal.

Logs below:

kernel: gmc_v11_0_process_interrupt: 49 callbacks suppressed
kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32787, for process code pid 88433 thread code:cs0 pid 88456)
kernel: amdgpu 0000:c1:00.0: amdgpu:   in page starting at address 0x0000f0f13df0f000 from client 10
kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00401430
kernel: amdgpu 0000:c1:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
kernel: amdgpu 0000:c1:00.0: amdgpu:          MORE_FAULTS: 0x0
kernel: amdgpu 0000:c1:00.0: amdgpu:          WALKER_ERROR: 0x0
kernel: amdgpu 0000:c1:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
kernel: amdgpu 0000:c1:00.0: amdgpu:          MAPPING_ERROR: 0x0
kernel: amdgpu 0000:c1:00.0: amdgpu:          RW: 0x0
code[88433]: amdgpu: amdgpu_cs_query_fence_status failed.
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
code[88433]: amdgpu: amdgpu_cs_query_fence_status failed.

ehsanj · May 1, 2024, 5:47pm

Do you have the mesa-*-freeworld packages from rpmfusion installed by any chance? I was experiencing similar freezes until I swapped them for the bundled versions:

sudo dnf swap mesa-va-drivers-freeworld mesa-va-drivers
sudo dnf swap mesa-vdpau-drivers-freeworld mesa-vdpau-drivers

Note that you may have to specify the --allowerasing option for the commands above to succeed. If you choose to try this out, be sure to reboot your machine after the package swap.

I have not had this issue since I removed the freeworld hardware codecs (been ~2 weeks).

Jbk0 · May 1, 2024, 7:16pm

adding to this: just logging out and back in or running this command (just restarting audio services for the logged in user) works too:

systemctl --user restart pipewire.service pipewire-pulse.service wireplumber.service

kholdstare · May 1, 2024, 10:38pm

That’s a damned shame - yeah I’ve been using those since it’s nice to have the accel – I’ll swap 'em out and see if I can trigger it, cheers.

Matt_Hartley · May 2, 2024, 5:23pm

Just a reminder, if you feel you have come across a potential bug, please file a bug report with the Fedora team in addition to mentioning it here. Thanks!

Michael_Wu · May 3, 2024, 6:33am

@kholdstare @ehsanj FYI I haven’t had any freezes since while remaining on the freeworld-24.0.5 drivers (the non-freeworld packages have been on 24.0.6 for a while), so it might’ve been fixed from some other update. Nonetheless,

mesa-va-drivers-freeworld-24.0.6-1.fc40.x86_64
mesa-vdpau-drivers-freeworld-24.0.6-1.fc40.x86_64

have landed in rpmfusion-free-updates and I just updated. Will report back if I experience again but so far it’s been stable on my end.

Also, oddly dnf wasn’t refreshing/pulling the latest rpmfusion-free-updates updates, so I did a combination of uninstalling/reinstalling as well as

sudo dnf install --enablerepo=rpmfusion-free-updates  mesa-va-drivers-freeworld

without proceeding.

It then picked up the 24.0.6 version for both mesa-va-drivers-freeworld and mesa-vdpau-drivers-freeworld, and I was able to install them normally without the --enablerepo=rpmfusion-free-updates option.

Edit: 05-05-2024
Welp I’ve played plenty of YouTube videos over Firefox with no issues, but I just got the same crash mousing over a video on Amazon. Seems it may not have been fixed with the 24.0.6 freeworld drivers. I can’t repro with the above ffmpeg command. Updated to Firefox 125.0.3-1.fc40, TBD, may file an issue.

Benjamin_Eunice · May 4, 2024, 11:52am

Hey! I just had the same issue and I tried MrThees’ fix but it didn’t work for me. In my case, I had to execute the command recommended on this Fedora thread. Worked like a charm.

vhx · May 6, 2024, 5:56pm

i’ve been having hard freezes on a few distro’s i’ve played with over the last 6 weeks. kubuntu, KDE neon, and F40 kde. seems less of a problem on F40.

when the issue occurs, its almost always at resume-from-sleep (laptop is 99% in suspend,rather than shutdown).
however today i had it using superslicer appimage with simply resizing to half screen. had it crash and get (iirc) a GPU recovery popup. close and re-opened superslicer and the problem hasnt occured.

i’ve also seen the brightness work fine at reboot but after a few suspends, brightness keys do not work anymore. i’m assuming this is related to the same issue, even if there seems to be no related crash or hint it’s broken itself.

i’ll bug it with fedora if i can get more info on it…

kholdstare · May 6, 2024, 11:52pm

I’ve been getting some of the random hard-freezes as well, but no kernel panic or logs at all so it’s impossible to debug.
The displays go dark and any audio that was playing (from a game, video or music) continues playing, but the laptop is completely unresponsive and needs to be force-powered off and I can’t find any reliable way to recreate it.
Note that in all these instances I’m using it through a TB4 dock so I’m not using the touchpad or builtin keyboad.