Problem also with an old nvidia card.
Downgrade mesa from 25.2.1-1 to 25.1.7-1 solved it (see my previous message). But it is only a workaround. I hope that the future release of mesa with fix that regression.
with 2025-08-29 update, everything works fine, but with this one, my waydroid is completely broken.
Current:
when I start my waydroid session, it enters the desktop, and since my waydroid has an android update not installed. it will pop up such a update notification with a sound.
With this update, when the notification does not show but I hear the sound, and then my PC completely freeze. the mouse and keyboard won’t work any more, I have to press the power button to shut down and boot again.
since there is update about ROCm, I’m using:
CPU: AMD Ryzen 7 8840U w/ Radeon 780M Graphics (16) @ 3.301GHz
GPU: AMD ATI c4:00.0 HawkPoint1
not sure if relevant.
tried to remove pkg vulkan-intel and lib32-vulkan-intel, waydroid issue remains and new issue comes: I cannot shutdown my PC correctly, screen freezes at the shutdown screen (the same with the boot splash manjaro screen), I have to long press the power button…
@strawhat you claim that the previous update was fine, so check your /var/log/pacman.log what got updated and try to revert to the previous version. The mesa update was already included in the last update …
The vulkan packages are not the cause of the problem. They are installed on my computer and work well after mesa and lib32-mesa downgrade?
I just restored my system with timeshift to 2025-08-29 update (before 2025-08-30). ![]()
everything works now.
I first tried with kernel 6.12 no improvement
Downgraded mesa and lib32-mesa, still same issues both with kernel 6.6 and 6.12
I have had the error at booting after install-grub; grub-secure mode.
Could someone help me to fix this issue?
Upgrade system and reboot, and run install-grub and reboot again.
Then during rebooting system, I had following error.
Go to grub-secure mode…
I saw this error at first time.
grub error
symbol 'grub_call0c' not found
sudo install-grub
Grub will be installed on: EFI Installing for x86_64-efi platform. Installation
finished. No error reported.
Update UEFI Fallback file: /boot/efi/EFI/Manjaro/
grubx64.efi Generating grub configuration file ... Found background: /usr/share/
grub/background.png Linux イメージを見つけました: /boot/vmlinuz-6.6-x86_64 Found
initrd image: /boot/intel-ucode.img /boot/initramfs-6.6-x86_64.img Found initrd
fallback image: /boot/initramfs-6.6-x86_64-fallback.img
Linux イメージを見つけました: /boot/vmlinuz-6.1-x86_64 Found initrd image: /boot/intel-ucode.img /boot/
initramfs-6.1-x86_64.img Found initrd fallback image: /boot/
initramfs-6.1-x86_64-fallback.img Linux イメージを見つけました: /boot/
vmlinuz-5.15-x86_64 Found initrd image: /boot/intel-ucode.img /boot/
initramfs-5.15-x86_64.img Found initrd fallback image: /boot/
initramfs-5.15-x86_64-fallback.img Linux イメージを見つけました: /boot/
vmlinuz-5.10-x86_64 Found initrd image: /boot/intel-ucode.img /boot/
initramfs-5.10-x86_64.img Found initrd fallback image: /boot/
initramfs-5.10-x86_64-fallback.img Linux イメージを見つけました: /boot/
vmlinuz-5.4-x86_64 Found initrd image: /boot/intel-ucode.img /boot/
initramfs-5.4-x86_64.img Found initrd fallback image: /boot/
initramfs-5.4-x86_64-fallback.img Warning: os-prober will be executed to detect
other bootable partitions. Its output will be used to detect bootable binaries on
them and create new boot entries. Found Manjaro Linux (25.0.3) on /dev/nvme0n1p2
Adding boot menu entry for UEFI Firmware Settings ... Found memtest86+ image: /
boot/memtest86+/memtest.bin
There are several tips regarding grub updates. Most likely the backup entry which is used to boot your system is not updated/synced. So try to fix bootx64.efi file as suggested.
You can check with pacman -Syu which packages are suggested for update and try one by one. Maybe just update kernels to see if there is some regression.
Don’t know what your issue is. You can try to boot a fresh 25.0.8 install media to see if it works, which includes this and last update. Else try to switch to testing branch, which has further mesa updates.
The older releases of Zetar can be found here.
Same for me. Working well now.
Created a USB with 25.0.8, boots fine.
Decided to opt for a fresh install. (previous install dated from 2019-11-19)
Did find some issues with the installer xD
Calamares in 25.0.8 crashes when entering passphrase for LUKS volume.
Switched to testing branch and updated Calamares.
Went for LUKS with ext4.
Ran into an issue with LUKS swap partition that prompted passphrase but was not shown because the load splash was blinking. (removed splash and generated passfile to auto unlock after unlocking boot partition)
And lastly update-grub threw an error that the filesystem was not btrfs. Removing the btrfs hook fixed that.
Updating this post, as this issue was somehow fixed by the new kernels and video firmware released today. That means it was either fixed by amd-ucode 20250808-2, linux-firmware-radeon 20250808-2, or linux612 6.12.44-3.
Before the fix, I was unable to get GNOME started. I would just get a black screen after passing the login prompt. I have a Ryzen 5 4500U with integrated graphics (Radeon Vega Mobile). I could access the laptop via ssh and see this in the logs:
[drm:amdgpu_job_submit [amdgpu]] *ERROR* Trying to push to a killed entity
I also saw these errors in /var/log/Xorg.0.log:
[ 56.081] (EE) AMDGPU(0): [drm] Failed to open DRM device for pci:0000:05:00.0: No such file or directory
[ 56.081] (EE) Screen 0 deleted because of no matching config section.
[ 56.081] (II) UnloadModule: "amdgpu"
[ 56.081] (EE) Device(s) detected, but none match those in the config file.
[ 56.081] (EE)
Fatal server error:
[ 56.081] (EE) no screens found(EE)
[ 56.081] (EE)
I had tried downgrading mesa, lib32-mesa, xf86-video-amdgpu, vulkan-radeon, lib32-vulkan-radeon, and tried removing vulkan-intel and lib32-vulkan-intel but that didn’t help. Before the update that fixed it, I was able to log in using lightdm instead of gdm, but I never found out what the actual problem was. Thanks to someone, somewhere, who somehow fixed it. ![]()
Hi,
tried a fresh install. Always making btrfs partitions with /boot/efi
Now the installer says boot/efi is prohibited and yet i delete that filesystem to make fresh ones in the installer.
Do i have to point out the boot partition to /boot in stead of /boot/efi ?
Anyone experiencing the same ?
I make a 1024 mb /boot/efi fat32 and with boot flag
a root (102400 MB ) on btrfs and the rest of the disk /data
Just ordinary filesystems. tested all this with the 25.07 iso’s and i could make a /boot/efi and root / and the /data filesystems so that’s fine
Anybody with a solution ?
I used the manjaro-xfce-25.0.8-minimal-250831-linux612.iso and tested the kde also.
Same message. Something wrong with the iso’s or am i doing something wrong ?
A friend of mine used fat16 for boot and then the partitions could be made.
imho fat32 is the one most used for /boot/efi so i think there’s something wrong with the iso
fat can be in 12,16 or 32 … 32 is the one mostly used.
@philm or another teammember can you please confirm ?
3 posts were split to a new topic: Akonadi and LACT daemon won’t start anymore
So far I only tested KDE Plasma ISO in a virtual machine using BTRFS filesystem. I might do some more tests. Some say that the 28.0.6 ISOs are kinda solid to install. So I really wonder why now AMDGPUs create black screens …
Hi there!
Both of my affected systems run Manjaro Cinnamon.
One issue: After updating nfs-utils (2.8.3-2 → 2.8.3-3) last Saturday, the fstab/systemd-based NFS auto-mount of shares on my Synology Diskstation NAS no longer works.
I found the following boot journal entries that I consider relevant in this context:
Sep 01 16:44:59 sunryze systemd-networkd-wait-online[2042]: Timeout occurred while waiting for network connectivity.
Sep 01 16:44:59 sunryze systemd[1]: Failed to start Wait for Network to be Configured.
Sep 01 16:45:54 sunryze systemd-coredump[2824]: Process 2612 (nemo) of user 1000 dumped core.
Stack trace of thread 2612:
...
/* Here are a bunch of stack traces from when I tried to open the mount
directories with Nemo, which crashed several times in the process. */
Sep 01 16:46:30 sunryze systemd[1]: Failed to mount /home/xy/.syno/data.
Sep 01 16:46:30 sunryze systemd[1]: Failed to start RPC Bind.
Sep 01 16:46:33 sunryze systemd[1]: Failed to mount /home/xy/.syno/usb.2.
Sep 01 16:48:00 sunryze systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
The fstab entries look like this, for example:
syno:/volume1/data /home/xy/.syno/data nfs vers=3,rw,bg,hard,user,noauto,x-systemd.automount,x-systemd.device-timeout=10 0 0
...
syno:/volumeUSB2/usbshare /home/xy/.syno/usb.2 nfs vers=3,rw,bg,hard,user,noauto,x-systemd.automount,x-systemd.device-timeout=10 0 0
Manual mounting by sudo mount -a succeeds, but it takes about 20 seconds for the 10 mounts to become available. Before the update, all mounts were already available after logging in.
Any clues anybody? THX!
Kind regards,
RJ
This release update (since the last two releases), is also freezing my System (nvidia 2080ti driver related) on LTS 6.12, switching back to LTS 6.6 fixed it again.
Did you try to downgrade mesa and lib32-mesa, then give a new try to kernel 6.12?
Those who want to downgrade to mesa 25.1.9 can use this repo on top of [extra] in /etc/pacman.conf:
[mesa-251]
SigLevel = PackageRequired
Server = https://download.manjaro.org/pkgs/mesa
If that also don’t help, maybe it is the firmware ?!? Index of /packages/l/linux-firmware-amdgpu/
A newer set of firmwares can be found here:
[linux-firmware]
SigLevel = PackageRequired
Server = https://download.manjaro.org/pkgs/linux-firmware