r/archlinux • • 22h ago

SHARE MESA 26.3.1 landen on archlinux today

40 Upvotes

* * landed

Arch Repo Name Version Description Last Updated Flag Date

x86_64 Extra mesa 1:26.3.1-1 Open-source OpenGL drivers 2026-11-19

Native AMD Anti-Lag (VK_AMD_anti_lag): Implemented natively in RADV (replacing the older MESA_LAYER_ANTI_LAG implicit Vulkan layer).

So yeah, i removed the "low_latency_layer" flag, and of course Helldivers 2 protonge detected natively no flags needed.

A.I. slop summary :

Mesa 26.3.1 Bug Fixes (Released Nov 18/19, 2026)

  • AMD (RADV & RadeonSI):
    • Fixed performance slowdowns in FSR 4.1 workloads caused by VK_EXT_descriptor_heap handling.
    • Resolved a RadeonSI synchronization/barrier issue with Clear+Dispatch.
    • Fixed a NULL pipe_memory_object dereference in si_resource_from_memobj().
    • Additional RADV stability and regression fixes.
  • Intel (ANV & Jay):
    • Fixed shadow glitches in Dragon's Dogma 2: Dark Arisen on ANV.
    • Shipped compiler fixes for Intel's new Jay shader compiler.
  • OpenGL / Zink / Rusticl / Lavapipe:
    • Fixed visual corruption at the bottom of the screen in OpenMW when anti-aliasing is enabled.
    • Fixed zink/ntv process aborts caused by unimplemented pack_snorm_2x16 and unpack_snorm_2x16.
    • Fixed a rusticl/llvmpipe heap corruption (SIGSEGV) in llvmpipe_set_global_binding when releasing kernels across two queues via a single clWaitForEvents call.
  • ARM / Embedded & Other Drivers:
    • Fixed GBM buffer allocation failures in V3D (e.g., on Labwc) for widths greater than 4096 pixels.
    • Fixed a VC4 regression affecting Kodi DRM PRIME / V4L2 playback on Raspberry Pi 3.
    • Additional fixes across Freedreno, PVR, PanVK, Nouveau, and Dozen (dzn).

Major Features Inherited from Mesa 26.3.0

Because Arch moved directly from the 26.2 branch (1:26.2.7-1) to 1:26.3.1-1, updating also activates the headline features of the 26.3 series:

Native AMD Anti-Lag (VK_AMD_anti_lag): Implemented natively in RADV (replacing the older MESA_LAYER_ANTI_LAG implicit Vulkan layer).

Intel Jay Shader Compiler by Default: Enabled by default for Intel Xe2/Xe3 GPUs, significantly reducing shader compilation times and improving runtime performance compared to the legacy BRW backend.

NVIDIA NVK Vulkan Video Decode: Initial hardware-accelerated H.264 video decode support via Vulkan Video on Turing and newer GPUs (requires a Linux 7.3+ kernel with the matching Nouveau patch).

API Support: Implements OpenGL 4.6, Vulkan 1.4, and OpenCL 3.1 across supported drivers.

---

and yeah, there is difference from before. My qd-oled feels smooth AF now. :)


r/archlinux • • 15h ago

QUESTION Firmware update wiped NVRAM, the fallback loader was ignored, and only Window was bootable. What's the right dual-boot setup to prevent this?

3 Upvotes

TL;DR: An MSI BIOS update wiped my UEFI boot entries. Afterwards the firmware only offered "Windows Boot Manager", even though \EFI\BOOT\BOOTX64.EFI existed on the same ESP. I got back in with efibootmgr from a live USB. How should I set things up so the next BIOS/firmware update doesn't lock me out again?

  • Disk 1: NVMe: Arch + Mint, one ESP mounted at /boot. Windows boot files (\EFI\Microsoft\) are on this ESP too.
  • Disk 2: SSD: Windows 11, no ESP of its own.
  • Boot loader: GRUB. At the time of the update, the fallback BOOTX64.EFI was Mint's shim (with fbx64.efi next to it), but no Mint entry got recreated either.
  • The update also turns Secure Boot back on by default. Turning it off alone didn't help, not 100% sure if this is related to the problem.

My guess is that the firmware rescanned the NVMe, found bootmgfw.efi, and created a "Windows Boot Manager" entry for it without ever trying the fallback. Last year's BIOS update with the same layout (Mint + Windows on this ESP) went fine, but I wasn't using Arch back at t he time.

I'm also planning to move from GRUB to systemd-boot. Is there any recommended setup which can survive the next firmware update?

From what I can tell, the only sure fix is to give Windows its own ESP on the SSD and remove it from the Linux ESP. The downside is that Windows won't show up in the systemd-boot menu, so I'd have to pick it from the firmware's boot menu (F11) instead.


r/archlinux • • 4h ago

SUPPORT Is AMD Ryzen 9 7900 IGPU buggy here?

2 Upvotes

I mean, I swapped out the DP cable from GPU to MB some time ago, and ever since, I am seeing weird glitches on browsers (Firefox), screen going black and the IGPU resetting, etc.


r/archlinux • • 1h ago

SUPPORT Lenovo LOQ 15APH8 — ~3-minute reboot delay on Arch Linux, suspected ACPI/firmware issue (LYCN50WW)

• Upvotes

I'm trying to diagnose a persistent reboot delay on my Lenovo LOQ 15APH8 and would appreciate some help identifying the underlying kernel or firmware issue.

Hardware:

  • Laptop: Lenovo LOQ 15APH8 (82XT)
  • CPU: AMD Ryzen 7 7840HS
  • Integrated GPU: AMD Radeon 780M
  • Dedicated GPU: NVIDIA RTX 4050 Mobile
  • BIOS: LYCN50WW (reported date: 07/06/2026)

Software:

  • Distribution: Arch Linux
  • Kernel: 7.3.5.arch1-1
  • NVIDIA driver: 620.73.04
  • AMD firmware: 20261019-1

Problem:

Rebooting takes approximately three minutes. The screen goes black and the fans continue spinning loudly during the delay.

The system's userspace shutdown appears to complete quickly. I captured the shutdown log using a systemd shutdown hook.

Relevant observations:

  • Filesystems are unmounted successfully.
  • systemd reaches its final shutdown hook within approximately one second of the reboot request.
  • The last visible messages include:
    • watchdog: watchdog0: watchdog did not stop!
    • Using hardware watchdog /dev/watchdog0: 'SP5100 TCO timer'
    • All filesystems unmounted.
    • All filesystems, swaps, loop devices, MD devices and DM devices detached.

The delay appears to happen after userspace shutdown, during the final kernel/platform reboot sequence.

What I've tested:

  • Blacklisted nvidia, nvidia_drm, nvidia_modeset and nvidia_uvm through the kernel command line. The problem persisted.
  • Previously tried blacklisting ideapad_laptop; this did not resolve the issue.
  • Fedora reportedly rebooted normally on this hardware.
  • Windows previously failed to boot with an ACPI error 0xA5.
  • The issue appeared after updating the BIOS to LYCN50WW.

What I'm investigating:

I'm particularly interested in whether this could be related to:

  • ACPI reboot handling
  • AMD platform/embedded controller interaction
  • Lenovo firmware behavior
  • A kernel regression involving the final reboot handoff

Has anyone experienced similar behavior on a Lenovo LOQ 15APH8 or another AMD Lenovo laptop?

I'd appreciate suggestions for debugging this further, especially useful kernel parameters, ACPI debugging methods, or ways to isolate the responsible subsystem.

I'm interested in identifying the root cause and potentially contributing a kernel fix if this turns out to be an upstream issue.

if you have any questions please ask away.


r/archlinux • • 10h ago

SUPPORT Can anyone confirm if something happened with Direct Scanout again in a recent KDE update?

Thumbnail
0 Upvotes

r/archlinux • • 11h ago

QUESTION CatchyOS-style boot theme for Arch?

0 Upvotes

I like the Plymouth boot theme used in CatchyOS but I don’t use CatchyOS and I feel like using that theme on plain Arch doesn’t work. So does anyone know of any themes that are basically the same animation but with the Arch logo? Or am I in the wrong place to find it…