I tried booting with newly published iso images and Manjaro doesn’t even boot. This is a screen where everything hangs.
This screen just keeps refreshing and not progressing forward at all.
It might be my karma or this release is a bit troublesome
Hmm, maybe the kernel in the ISO is something newer than the latest LTS? Curious if booting into the ISO, manjaro-chroot -a, sudo pacman -S linux612, exit (chroot), reboot would help you out?
Currently released versions and older can be found here: Manjaro 25.0 Zetar released
Been getting amdgpu crashes in Metro Exodus EE, they point to vkd3d but they seem to be related to using up-scaling through Optiscaler perhaps the spoofing part. When I disabled it did not crash.
Kernel is 6.12.48
The output is as follows:
amdgpu 0000:28:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32801)
amdgpu 0000:28:00.0: amdgpu: in process MetroExodus.exe pid 1304818 thread vkd3d_queue pid 1305002
amdgpu 0000:28:00.0: amdgpu: in page starting at address 0x000080039509d000 from client 0x1b (UTCL2)
amdgpu 0000:28:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601030
amdgpu 0000:28:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
amdgpu 0000:28:00.0: amdgpu: MORE_FAULTS: 0x0
amdgpu 0000:28:00.0: amdgpu: WALKER_ERROR: 0x0
amdgpu 0000:28:00.0: amdgpu: PERMISSION_FAULTS: 0x3
amdgpu 0000:28:00.0: amdgpu: MAPPING_ERROR: 0x0
amdgpu 0000:28:00.0: amdgpu: RW: 0x0
I’ll switch to 6.16 to see if that changes things, I switched back back to 6.12 a week or so ago and I cannot remember having such frequent crashes with Metro Exodus EE and Optiscaler.
Update: retested on 6.16.8 and haven’t had the above crash in over 30 min, while on 6.12 is occurred within 5 min.
Based on my limited understanding from GPU Debugging — The Linux Kernel documentation… your error can be decoded as…
A shader (cliend id = TCP) generated a read (RW = 0x0) to an invalid page (PERMISSION_FAULTS = 0x3) at GPU virtual address 0x000080039509d000.
And because vmid:6 is non-zero, it points to an application (vkd3d / proton / mesa ?) issue and not kernel/firmware…
If the vmid is 0, this fault was likely caused by the kernel driver or firmware. If the vmid is non-0, it is generally a fault in a user application.
So in your example it looks like the Optiscaler was triggering the shader issue?
And it’ll be confusing (based on the non-zero vmid explanation) if the kernel/driver ends up being a solution for you.
All I know is… post June/July … amdgpu “issues” are more frequent.
Updated Thought re:Proton / dxvk
Reading posts like All Protons are way behind my customized Wine :: Steam for Linux General Discussions are starting to make me think Proton may be a “lagging” package concerning dxvk as a potential cause of issues.
Looking at GitHub - doitsujin/dxvk: Vulkan-based implementation of D3D8, 9, 10 and 11 for Linux / Wine I can see the latest release is dxvk 2.71, yet Proton 10/Experimental is using dxvk 2.62, Proton 9 is using dxvk 2.51, etc… per Changelog · ValveSoftware/Proton Wiki · GitHub
2 Likes
A post was merged into an existing topic: Update requests for packages imported from Arch Linux
9 posts were split to a new topic: Stable is a not updated at 2 months why?
Discord 1:0.0.116-1 freezes when screen-sharing. Revert to 1:0.0.115-1 fixes the issue.
The admittedly[1] bug-containing version 3.2.4 of pyparsing (extra/python-pyparsing) bundled in stable-20250926 also affects console version mitmproxyof mitmproxy (extra/mitmproxy) – so it’s not only AUR and it should count.
1 Like
Welcome to Manjaro forum @x_a
python-pyparsing 3.2.5 is available on unstable and testing branches
Thanks for the welcome.
I already knew that. My point wasn’t to ask for advise, though, but to confirm that stable indeed has an issue – factual and perhaps QA-wise.
1 Like
That’s good. Then you also know that switching branch to either Testing or Unstable is a valid workaround in the meantime, for those who might potentially be affected.
2 Likes
Issue reported 26 Sep 2025 for python-pyparsing v3.2.4 was resolved by updating to v3.2.5
New version of python-pyparsing should be released to stable branch soon