You may be getting getting hit by a known bug? Under the Known Issues
New issues:
Some Nvidia cards don’t work with the current 460.80 drivers when used with Display Port and/or 4k Monitors. More about the issue at the Nvidia Developer Forum. We recommend to switch to Nouveau driver as needed. If you however need the Nvidia driver, you can get the PKGBUILDs of the 460.73.01 version and build your driver locally with makepkg or use the pre-compiled packages: nvida-utils, dkms and lib32 + precompiled .
Networking never loads, It just does fschk and then blackscreens at the point it would normally load in. I dont know if its an nvidia thing or something else. It is nvidia with my main monitor on display port.
Was able to rescue system with arch-chroot from a liveUSB with timeshift-autosnap backup
Ill be not updating my system until this nvidia thing is sorted out, or there is some way to get it functioning with an updated driver, thats a deal breaker for me.
I have an Nvidia GTX 960 with the proprietary driver and two 1080p monitors, one connected to HDMI and the other to DVI. Will I be okay applying this update?
I updated anyways and it all seems to be okay with my configuration and both my monitors seem to be working.
It was also my first stable update after installing Pipewire and it works alright.
So, no problems on my part with:
EDIT: OK seems i solved it myself … killing pamac, remove db lock, removing the locally newer pamac version and sudo update-grub did the trick for me … at least it is still working after a reboot.
Original post:
Well … i tried to update but now pamac ist stuck
Is it save to kill the task :(?
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.12-x86_64-fallback.img
==> Image generation successful
Updating Grub-Bootmenu
Generating grub configuration file …
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.12-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.12-x86_64.img
Found initrd fallback image: /boot/initramfs-5.12-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
It’s output will be used to detect bootable binaries on them and create new boot entries.
umount: /var/lib/os-prober/mount: das Ziel wird gerade benutzt.
rmdir: konnte ‘/var/lib/os-prober/mount’ nicht entfernen: Das Gerät oder die Ressource ist belegt
rmdir: konnte ‘/var/lib/os-prober/mount’ nicht entfernen: Das Gerät oder die Ressource ist belegt
After updating, my plasmashell (I think) doesn’t work. After splash screen I get black screen with no Plasma stuff, only cursor, sometimes I can open terminal over Yakuake if it starts automatically and then I can start other programs as usual, but still no task bar, workspaces desktops or anything.
I upgrade my wifi card to AX210 on my X230 Thinkpad. The card isn’t usable until I rename / remove the following file.
iwlwifi-ty-a0-gf-a0.pnvm under /usr/lib/firmware/
I am on 5.11 now and it was the same with 5.12
Well … i now killed pacman as it won’t close on its own and cancel button was disabled.
I had to delete /var/lib/pacman/db.lck now sudo pacman -Syyu results in:
Warnung: pamac-cli: Lokale Version (10.1.2-0.1) ist neuer als extra (10.0.6-2)
Warnung: pamac-common: Lokale Version (10.1.2-0.1) ist neuer als extra (10.0.6-2)
Warnung: pamac-flatpak-plugin: Lokale Version (10.1.2-0.1) ist neuer als extra (10.0.6-2)
Warnung: pamac-gtk: Lokale Version (10.1.2-0.1) ist neuer als extra (10.0.6-2)
Warnung: pamac-snap-plugin: Lokale Version (10.1.2-0.1) ist neuer als extra (10.0.6-2)
Seems i got an anhealthy pamac? I will revert to the old version.
@Manjaro team After update the reboot was necessary → my reboot stopped with black screen. I had to do 2 times (twice) Ctrl+Alt+Del in order to make reboot hapenning successfully. Should I (or could I) do something about this ?
@CalibratedCabbage My reboot issue does not look (to me) like yours. I had this quite minor issue only in one desktop, not in laptops. My now, after this (Ctrl+Alt+Del) was done, this does not happen any more in the desktop in question.
The amdgpu-bug causing a lockup after suspend still seems present in 5.12.2
Haven’t dared to check latest 5.11, as I will then lose 5.11.6, which is the last (known to me) working kernel from 5.11 without lockups after suspend (on my Ryzen 4600U-based laptop).