You don’t need a USB drive, you can use the ESP or any other FAT32 partition as well.
Hi Tom,
By default in a new installation, the touchscreen only works on top screen and if I touch the bottom one it gets redirected to the top. When I run set-tablet-mapping both screens seem to react independently, but it’s like the position of the X it’s ok, but the cursor Y gets farther from the stylus as I approach to the middle. The feeling is that I have a resolution of 2880x3600 with both screens, but the touch area of both screens altogether is 2880x1800, as it was a single screen. Here’s a video showing the issue that illustrates it better than my explanation. Notice that when I go up, when I reach the top border of the bottom screen It has reached the top of the top screen.
[https://youtube.com/shorts/BDVE2hEbS8E]
I have tried different resolutions and parameters as well but the result is exactly the same. Anyways in my case I have the ui set to 200%, so ui.scale=2 and by the script comment ```
y offset = height of resolution / ui_scale I think y_offset must be 1800/2=900.
Regarding sound issues I think it’s weird, but 100% of the times I’ve tried, sound works fine when I boot into linux with the PC completely turned off. If I’m on windows and I reboot to linux, almost all the times I’m having no sound issues. I don’t think it makes sense, but I’ve tried a lot of times with the same result.
Sure, you can download the update from asus website and then you can enter the uefi setup (esc during boot). There’s an option to upgrade using a pendrive or similar.
Having the same sound disconnecting issue here with Fedora 40. Not the crackling one. Only fix seems to reboot the laptop.
Usually use a Bluetooth headphone, it connects and transmits audio every time. Sometimes I have microdisconnections (not really a disconnection, but the audio skips a few fractions of a second), but those are not common.
Hi LGiusti84,
If I boot fedora with the computer previously turned off I’m having almost no issues right now. I’ve seen in my case that if I’m in Windows and reboot to fedora the audio issues are highly likely to occur. Do you have windows installed or only linux? are you in last bios 306?
To minimize audio issues I’ve installed Pavucontrol, as some apps like Unity that use an old Fmod to control audio, gets directed to HDMI instead of speaker, so I correct this manually.
1 Like
@xevicb hey I see you are using gnome. Not sure it lets you map touch inputs to outputs manually.
However if touchscreen functionality is very important to you consider using KDE as it has been reported to allow you to manually correct it, further up in this thread.
I use swaywm and can do it manually with kanshi:
profile Duo {
output eDP-1 scale 2 position 0,0 adaptive_sync on
output eDP-2 scale 2 position 0,900 adaptive_sync on
exec busctl --user set-property rs.wl-gammarelay /outputs/eDP_1 rs.wl.gammarelay Temperature q 3850
exec busctl --user set-property rs.wl-gammarelay /outputs/eDP_2 rs.wl.gammarelay Temperature q 3350
exec swaymsg input "1267:16986:ELAN9009:00_04F3:425B" map_to_output eDP-1
exec swaymsg input "1267:16987:ELAN9008:00_04F3:425A" map_to_output eDP-2
exec swaymsg input "1267:16986:ELAN9009:00_04F3:425B_Stylus" map_to_output eDP-1
exec swaymsg input "1267:16987:ELAN9008:00_04F3:425A_Stylus" map_to_output eDP-2
}
1 Like
Tom, thanks for your great support,
I’m not sure what to do, the truth is that I selected Fedora 40 with GNOME 46 because according to the description of Alesya’s scripts, the mapping of touch screens only worked with this system.
Now I have returned to the functionality that had the touch screens out of the box, that is, the inputs from the bottom screen are transferred to the top one consistently in terms of position. I wonder, despite the limitations of GNOME, if it would be possible to reverse the functionality, that is, if I touch the top screen the actions go to the bottom one. In fact, I don’t need the touch functionality on both screens, I only use the bottom one for drawing and sculpting with Blender.
Or I don’t know if it would be possible even if it is with a slightly hacky script to add an offset to the Y coordinate of 1800 pixels.
These commands fix the input mapping of the touchscreen for me, mostly. You might have to adjust the ID (04F3:4259…) to match your system, which you can find by running xinput.
Occasionally it maps the wrong screen to the wrong touchscreen… I think there needs to be some logic involved as eDP-1 and eDP-2 seem to change sometimes.
Thought this might help with the previous query, but not sure.
xinput --map-to-output $(xinput list | grep 04F3:4259 | grep --invert-match Touchpad | grep “pointer” | awk ‘{for(i=1;i<=NF;i++) if ($i ~ /id=[0-9]+/) print substr($i, 4)}’) eDP-1
xinput --map-to-output $(xinput list | grep 04F3:42EC | grep --invert-match Touchpad | grep “pointer” | awk ‘{for(i=1;i<=NF;i++) if ($i ~ /id=[0-9]+/) print substr($i, 4)}’) eDP-2
1 Like
Hi Mathieu,
I think it’s not working for me, as I run the commands it throws this warning, though it doen’t seem to have any effect on touchscreen behavior.
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
Currently in wacom gnome settings I have set it all screens to automatic, so the bottom screen outputs to the top. If I list devices with xinput throws this list, but I can’t identify there 04F3:425A and 425B in my case.
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ xwayland-pointer:16 id=6 [slave pointer (2)]
⎜ ↳ xwayland-relative-pointer:16 id=7 [slave pointer (2)]
⎜ ↳ xwayland-pointer-gestures:16 id=8 [slave pointer (2)]
⎜ ↳ xwayland-touch:16 id=10 [slave pointer (2)]
⎜ ↳ xwayland-tablet stylus:16 id=11 [slave pointer (2)]
⎜ ↳ xwayland-tablet eraser:16 id=12 [slave pointer (2)]
⎜ ↳ xwayland-tablet cursor:16 id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ xwayland-keyboard:16 id=9 [slave keyboard (3)]
Thanks for your help, i’m still a newbie in linux world though slowly I’m getting used to it and I love it. Can’t wait to ditch windows if I could fix some rough edges!
Has anyone noticed any extra-buggy display behaviour on Plasma 6.1? It seems to be turning the lower display on constantly, even when I turn it off in the system settings. I’m not running any fancy scripts or anything.
Yesterday I did a nix flake update which pushed my linux kernel up from 6.9.8 to 6.9.12, and have found that the onboard audio speaker & mic on the UX8406MA is no longer functioning.
$ dmesg | grep sof-audio
[ 23.571162] sof-audio-pci-intel-mtl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[ 23.572505] sof-audio-pci-intel-mtl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[ 23.572520] sof-audio-pci-intel-mtl 0000:00:1f.3: enabling device (0000 -> 0002)
[ 23.572683] sof-audio-pci-intel-mtl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[ 23.572752] sof-audio-pci-intel-mtl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 23.579528] sof-audio-pci-intel-mtl 0000:00:1f.3: use msi interrupt mode
[ 23.615509] sof-audio-pci-intel-mtl 0000:00:1f.3: hda codecs found, mask 5
[ 23.615514] sof-audio-pci-intel-mtl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
[ 23.615519] sof-audio-pci-intel-mtl 0000:00:1f.3: DMICs detected in NHLT tables: 2
[ 23.620894] sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware paths/files for ipc type 1:
[ 23.620898] sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware file: intel/sof-ipc4/mtl/sof-mtl.ri
[ 23.620899] sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware lib path: intel/sof-ipc4-lib/mtl
[ 23.620900] sof-audio-pci-intel-mtl 0000:00:1f.3: Topology file: intel/sof-ace-tplg/sof-hda-generic-2ch.tplg
[ 23.622962] sof-audio-pci-intel-mtl 0000:00:1f.3: Loaded firmware library: ADSPFW, version: 2.9.0.1
[ 23.734142] sof-audio-pci-intel-mtl 0000:00:1f.3: Booted firmware version: 2.9.0.1
[ 23.744461] sof-audio-pci-intel-mtl 0000:00:1f.3: Topology: ABI 3:29:0 Kernel ABI 3:23:0
[ 23.744691] sof-audio-pci-intel-mtl 0000:00:1f.3: error: source host-copier.3.playback\xff\xff not found
[ 23.746281] sof-audio-pci-intel-mtl 0000:00:1f.3: error: tplg component load failed -22
[ 23.746717] sof-audio-pci-intel-mtl 0000:00:1f.3: error: failed to load DSP topology -22
[ 23.747309] sof-audio-pci-intel-mtl 0000:00:1f.3: ASoC: error at snd_soc_component_probe on 0000:00:1f.3: -22
Just a warning to everyone at this point. I don’t know for sure that it is caused by the 6.9.12 kernel, but that’s the first standout difference during the upgrade.
EDIT: The issue appears to be the same as Audio system not working after an system upgrade on my thinkpad x1yoga gen5 · Issue #330685 · NixOS/nixpkgs · GitHub, and can be addressed by pulling up the kernel to 6.10 or by backporting some patches (Audio system not working after an system upgrade on my thinkpad x1yoga gen5 · Issue #330685 · NixOS/nixpkgs · GitHub). Having bumped my kernel up to 6.10 (boot.kernelPackages = pkgs.linuxPackages_6_10;), internal audio is working again.
Great news, as of 6.10.5 the blank bottom display issue seems to be resolved
1 Like
Hi @greasecake, thanks for the update.
On fedora 40 this kernel seems extremely broken. When I’m able to log in, the bottom screen freezes randomly and system becomes really unresponsive (seconds, even minutes to react) and on other occasions simply crashes completely.
Is someone else not facing this on NixOS or fedora?
If there is any way I can help with fixing let me know and I’ll see what I can help with.
PS: I have @alesya-h scripts on my system (by the way, great work and thanks for them!!!).
I took a look at them before using them so I really doubt this issues are related to those, but had disabled them anyway and rebooted my system, issue is still there. I also encounter this problems even before login in most occasions (before they would run).
1 Like
I was able to disable rfkill in wayland KDE with the help of the following:
Build from source went without a hitch.
and here is my keyd config file:
[ids]
*
[main]
wlan = esc
i basically remapped the wlan to esc so that when keyboard is removed/attached it does not disable the wifi
1 Like
Yeah I also tried to upgrade and encountered the same issues on arch gnome, I rolled back to the 6.8, the computer is again responsive but the bottom screen does not work, as if something else is causing the issue other than the kernel.
Between 6.10.3 and 6.10.5 there seems to be a functional regression in the i915 driver on the Zenbook Duo. For me the experience was worse than “freezes randomly”; the display never left the console mode to become graphically functional at all. Upgrading not recommended at this time.
I’ll see if I can pull together enough information to file an additional i915 bug report.
Aug 21 13:17:01 zenbook-nixos kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:134:pipe B] flip_done timed out
Aug 21 13:17:01 zenbook-nixos kernel: ------------[ cut here ]------------
Aug 21 13:17:01 zenbook-nixos kernel: i915 0000:00:02.0: drm_WARN_ON(!(val & ((u32)(((((1UL))) << (31)) + ((int)(sizeof(struct { int:(-!!((sizeof(int) == sizeof(*(8 ? ((void *)((long)(31) * 0l)) : (int *)8))) && ((31) < 0 || (31) > 31))); })))))))
Aug 21 13:17:01 zenbook-nixos kernel: WARNING: CPU: 10 PID: 2277 at drivers/gpu/drm/i915/display/intel_psr.c:2035 intel_psr_exit+0x324/0x500 [i915]
Aug 21 13:17:01 zenbook-nixos kernel: Modules linked in: uhid cmac algif_hash algif_skcipher af_alg af_packet bnep snd_ctl_led snd_soc_skl_hda_dsp snd_soc_hdac_hdmi snd_sof_probes snd_soc_intel_hda_dsp_common hid_sensor_custom_intel_hinge hid_sensor_accel_3d hid_sensor_als hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common industrialio hid_sensor_custom hid_sensor_hub nls_iso8859_1 nls_cp437 snd_hda_codec_hdmi intel_ishtp_hid vfat fat snd_hda_codec_realtek snd_hda_codec_generic snd_hda_scodec_component snd_soc_dmic snd_sof_pci_intel_mtl snd_sof_intel_hda_generic xt_conntrack soundwire_intel nf_conntrack soundwire_cadence snd_sof_intel_hda_common nf_defrag_ipv6 nf_defrag_ipv4 snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp ip6t_rpfilter ipt_rpfilter snd_sof iwlmvm snd_sof_utils snd_hda_ext_core snd_soc_acpi_intel_match xt_pkttype soundwire_generic_allocation snd_soc_acpi xt_LOG soundwire_bus nf_log_syslog xt_tcpudp nft_compat snd_soc_core mac80211 nf_tables snd_compress
Aug 21 13:17:01 zenbook-nixos kernel: sch_fq_codel ac97_bus intel_uncore_frequency snd_pcm_dmaengine intel_uncore_frequency_common snd_hda_intel snd_intel_dspcfg x86_pkg_temp_thermal snd_intel_sdw_acpi intel_powerclamp uvcvideo snd_hda_codec snd_hda_scodec_cs35l41_spi cmdlinepart regmap_spi r8153_ecm videobuf2_vmalloc coretemp uvc spi_pxa2xx_platform snd_hda_scodec_cs35l41_i2c crc32_pclmul dw_dmac btusb videobuf2_memops snd_hda_scodec_cs35l41 cdc_ether 8250_dw snd_hda_core spi_nor iTCO_wdt ptp dw_dmac_core videobuf2_v4l2 btrtl usbnet uinput snd_hda_cs_dsp_ctls intel_pmc_bxt polyval_clmulni pps_core polyval_generic xe mei_gsc_proxy mtd watchdog intel_rapl_msr libarc4 iwlwifi snd_hwdep btintel gf128mul snd_soc_cs_amp_lib videodev ghash_clmulni_intel processor_thermal_device_pci cs_dsp r8152 snd_pcm processor_thermal_device drm_gpuvm btbcm loop intel_ish_ipc snd_soc_cs35l41_lib processor_thermal_wt_hint asus_nb_wmi btmtk drm_exec rapl processor_thermal_rfim videobuf2_common snd_timer hid_asus intel_cstate mii ucsi_acpi cfg80211 bluetooth
Aug 21 13:17:01 zenbook-nixos kernel: intel_uncore intel_ishtp libphy mc asus_wmi wmi_bmof processor_thermal_rapl platform_profile typec_ucsi tun intel_lpss_pci i2c_i801 mei_me gpu_sched intel_rapl_common snd intel_lpss igen6_edac idma64 processor_thermal_wt_req typec tap drm_suballoc_helper i2c_mux spi_intel_pci mousedev mei processor_thermal_power_floor spi_intel crc16 i2c_smbus intel_vpu soundcore 8250_pci virt_dma rfkill drm_ttm_helper joydev edac_core hid_multitouch thermal roles processor_thermal_mbox fan serial_multi_instantiate ac i2c_hid_acpi uas macvlan battery i2c_hid int3403_thermal tiny_power_button tpm_crb int340x_thermal_zone intel_pmc_core bridge tpm_tis intel_vsec tpm_tis_core intel_hid int3400_thermal pmt_telemetry acpi_tad pmt_class pinctrl_meteorlake soc_button_array acpi_thermal_rel acpi_pad sparse_keymap stp button evdev llc mac_hid serio_raw kvm_intel kvm fuse efi_pstore configfs nfnetlink zram efivarfs dmi_sysfs ip_tables x_tables autofs4 dm_crypt cbc encrypted_keys trusted asn1_encoder tee tpm rng_core libaescfb
Aug 21 13:17:01 zenbook-nixos kernel: ecdh_generic ecc sd_mod usb_storage scsi_mod scsi_common hid_generic usbhid hid nvme nvme_core nvme_auth t10_pi crc64_rocksoft crc64 crc_t10dif crct10dif_generic input_leds led_class thunderbolt xhci_pci atkbd xhci_pci_renesas crct10dif_pclmul libps2 crct10dif_common vivaldi_fmap sha512_ssse3 sha256_ssse3 xhci_hcd sha1_ssse3 aesni_intel crypto_simd cryptd rtc_cmos vmd i8042 serio dm_mod dax btrfs blake2b_generic libcrc32c crc32c_generic crc32c_intel xor raid6_pq i915 i2c_algo_bit drm_buddy video wmi backlight ttm intel_gtt drm_display_helper firmware_class cec
Aug 21 13:17:01 zenbook-nixos kernel: CPU: 10 PID: 2277 Comm: X Not tainted 6.10.5 #1-NixOS
Aug 21 13:17:01 zenbook-nixos kernel: Hardware name: ASUSTeK COMPUTER INC. ASUS Zenbook Duo UX8406MA_UX8406MA/UX8406MA, BIOS UX8406MA.306 05/03/2024
Aug 21 13:17:01 zenbook-nixos kernel: RIP: 0010:intel_psr_exit+0x324/0x500 [i915]
Aug 21 13:17:01 zenbook-nixos kernel: Code: 8b 6f 50 48 85 ed 75 03 48 8b 2f e8 d6 ae 21 dd 48 c7 c1 20 94 8a c0 48 89 ea 48 c7 c7 ce be 8c c0 48 89 c6 e8 5d 9a a1 dc 90 <0f> 0b 90 90 e9 55 fe ff ff 48 8d bf 48 0d 00 00 e8 c7 2d a4 dc 48
Aug 21 13:17:01 zenbook-nixos kernel: RSP: 0018:ffffa5538b62fdc0 EFLAGS: 00010286
Aug 21 13:17:01 zenbook-nixos kernel: RAX: 0000000000000000 RBX: ffff9882c93fa188 RCX: 0000000000000027
Aug 21 13:17:01 zenbook-nixos kernel: RDX: ffff98862ff21848 RSI: 0000000000000001 RDI: ffff98862ff21840
Aug 21 13:17:01 zenbook-nixos kernel: RBP: ffff9882c2fcfad0 R08: ffffffff9ec5a120 R09: 000000009f61adea
Aug 21 13:17:01 zenbook-nixos kernel: R10: ffffffffffffffff R11: ffffffff9ed3a168 R12: ffff9882c5ca0000
Aug 21 13:17:01 zenbook-nixos kernel: R13: 0000000000061800 R14: ffff9882c5ca0000 R15: ffff9882c5ca0618
Aug 21 13:17:01 zenbook-nixos kernel: FS: 00007fb123dfa9c0(0000) GS:ffff98862ff00000(0000) knlGS:0000000000000000
Aug 21 13:17:01 zenbook-nixos kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 21 13:17:01 zenbook-nixos kernel: CR2: 00007fa9ec006f40 CR3: 000000012f2ea006 CR4: 0000000000f70ef0
Aug 21 13:17:01 zenbook-nixos kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 21 13:17:01 zenbook-nixos kernel: DR3: 0000000000000000 DR6: 00000000ffff07f0 DR7: 0000000000000400
Aug 21 13:17:01 zenbook-nixos kernel: PKRU: 55555554
Aug 21 13:17:01 zenbook-nixos kernel: Call Trace:
Aug 21 13:17:01 zenbook-nixos kernel: <TASK>
Aug 21 13:17:01 zenbook-nixos kernel: ? __warn+0x80/0x120
Aug 21 13:17:01 zenbook-nixos kernel: ? intel_psr_exit+0x324/0x500 [i915]
Aug 21 13:17:01 zenbook-nixos kernel: ? report_bug+0x164/0x190
Aug 21 13:17:01 zenbook-nixos kernel: ? handle_bug+0x3d/0x80
Aug 21 13:17:01 zenbook-nixos kernel: ? exc_invalid_op+0x17/0x70
Aug 21 13:17:01 zenbook-nixos kernel: ? asm_exc_invalid_op+0x1a/0x20
Aug 21 13:17:01 zenbook-nixos kernel: ? intel_psr_exit+0x324/0x500 [i915]
Aug 21 13:17:01 zenbook-nixos kernel: intel_psr_invalidate+0x24b/0x2c0 [i915]
Aug 21 13:17:01 zenbook-nixos kernel: __intel_fb_invalidate+0x36/0xd0 [i915]
Aug 21 13:17:01 zenbook-nixos kernel: intel_fbdev_client_restore+0x5c/0x80 [i915]
Aug 21 13:17:01 zenbook-nixos kernel: drm_client_dev_restore+0x69/0xc0
Aug 21 13:17:01 zenbook-nixos kernel: drm_release_noglobal+0x4f/0x70
Aug 21 13:17:01 zenbook-nixos kernel: __fput+0xee/0x2c0
Aug 21 13:17:01 zenbook-nixos kernel: __x64_sys_close+0x3c/0x80
Aug 21 13:17:01 zenbook-nixos kernel: do_syscall_64+0xb7/0x200
Aug 21 13:17:01 zenbook-nixos kernel: entry_SYSCALL_64_after_hwframe+0x77/0x7f
Aug 21 13:17:01 zenbook-nixos kernel: RIP: 0033:0x7fb1240d1194
Aug 21 13:17:01 zenbook-nixos kernel: Code: 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 80 3d b5 de 0e 00 00 74 13 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 44 c3 0f 1f 00 48 83 ec 18 89 7c 24 0c e8 73
Aug 21 13:17:01 zenbook-nixos kernel: RSP: 002b:00007ffc3d278c08 EFLAGS: 00000202 ORIG_RAX: 0000000000000003
Aug 21 13:17:01 zenbook-nixos kernel: RAX: ffffffffffffffda RBX: 0000000007419dd0 RCX: 00007fb1240d1194
Aug 21 13:17:01 zenbook-nixos kernel: RDX: 000000000742a489 RSI: 0000000007419f10 RDI: 000000000000000c
Aug 21 13:17:01 zenbook-nixos kernel: RBP: 0000000007419f20 R08: 0000000000000002 R09: 0000000000000001
Aug 21 13:17:01 zenbook-nixos kernel: R10: 0000000000000007 R11: 0000000000000202 R12: 0000000007419e10
Aug 21 13:17:01 zenbook-nixos kernel: R13: 0000000000000000 R14: 000000000000000c R15: 000000000742d560
Aug 21 13:17:01 zenbook-nixos kernel: </TASK>
Aug 21 13:17:01 zenbook-nixos kernel: ---[ end trace 0000000000000000 ]---
Aug 21 13:17:11 zenbook-nixos kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Aug 21 13:17:11 zenbook-nixos kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:134:pipe B] commit wait timed out
Aug 21 13:17:22 zenbook-nixos kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Aug 21 13:17:22 zenbook-nixos kernel: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:250:eDP-2] commit wait timed out
Aug 21 13:17:32 zenbook-nixos kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Aug 21 13:17:32 zenbook-nixos kernel: i915 0000:00:02.0: [drm] *ERROR* [PLANE:84:plane 1B] commit wait timed out
Aug 21 13:17:42 zenbook-nixos kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:134:pipe B] flip_done timed out
3 Likes
same here. 6.10.4 works for me, but 6.10.5 does not
@ultramarine 6.8.12 works fine on my system. Even after switching back and forth with 6.10.5 and having the system as up to date as possible (other than the kernel).
Edit: sorry I wanted to respond to ultramarine, but ended up doing it on my own message 
I’ve been trying to narrow down the 6.10.5 issue and have found that, at least on my machine, on NixOS, it’s not a kernel issue. I was able to reproduce the same issue on 6.10.3 when I had other recent NixOS updates. So, after bisecting those recent nixpkgs upgrades, I’ve been able to identify that the error I posted above (flip_done timed out & etc) is caused by an upgrade to linux-firmware from 20240709->20240811 (linux-firmware: 20240709 -> 20240811 · NixOS/nixpkgs@be2751d · GitHub).
After this firmware package upgrade is excluded, I’m currently running 6.10.5 with no stability issues.
For NixOS users, you can exclude this upgrade by branching nixos-24.05 into your own nixpkgs, reverting be2751daf952676b1a6ab43b3e62d6d1f5cfc7a4, and using that branch as a package channel or flake. However, you’ll then have to keep that branch up-to-date with changes from nixos-24.05 with periodic merges.
I intend to try to report this issue upstream somewhere in the next few days.
edit: This seems promising for the issue being identified upstream already: Revert "i915: Update MTL DMC v2.22" (!276) · Merge requests · kernel-firmware / Linux Firmware · GitLab. Introduced in 20240811 which matches my bisect, related to this display hardware, and now reverted.
4 Likes
I can confirm that rolling back linux-firmware to 202407 solved the freezing issues, with latest kernel 6.10.6 on arch. Maybe @LGiusti84 your linux-firmware package is tied to the kernel update on fedora?
1 Like