You are not logged in.
@jtgd that was covered by the first link blablo posted in post #5
Updates have broken my system
This information would be worth to figure in the Arch news RSS feed.
All arch users which use nvidia-340xx driver are affected.
Offline
Have a look in the wiki: Downgrading packages
Look which old packages are in pacman cache:
$ ls /var/cache/pacman/pkg | grep xorg-server
gives something like:
xorg-server-1.19.3-1-x86_64.pkg.tar.xz
xorg-server-1.19.3-2-x86_64.pkg.tar.xz
xorg-server-1.19.3-3-x86_64.pkg.tar.xz
xorg-server-1.19.4-1-x86_64.pkg.tar.xz
xorg-server-1.19.5-1-x86_64.pkg.tar.xz
xorg-server-1.19.6+13+gd0d1a694f-1-x86_64.pkg.tar.xz
xorg-server-1.19.6+13+gd0d1a694f-2-x86_64.pkg.tar.xz
xorg-server-1.19.6-2-x86_64.pkg.tar.xz
xorg-server-1.20.0-2-x86_64.pkg.tar.xz
xorg-server-common-1.19.3-1-x86_64.pkg.tar.xz
xorg-server-common-1.19.3-2-x86_64.pkg.tar.xz
xorg-server-common-1.19.3-3-x86_64.pkg.tar.xz
xorg-server-common-1.19.4-1-x86_64.pkg.tar.xz
xorg-server-common-1.19.5-1-x86_64.pkg.tar.xz
xorg-server-common-1.19.6+13+gd0d1a694f-1-x86_64.pkg.tar.xz
xorg-server-common-1.19.6+13+gd0d1a694f-2-x86_64.pkg.tar.xz
xorg-server-common-1.19.6-2-x86_64.pkg.tar.xz
xorg-server-common-1.20.0-2-x86_64.pkg.tar.xz
xorg-server-utils-7.6-4-any.pkg.tar.xz
xorg-server-xephyr-1.19.3-1-x86_64.pkg.tar.xz
xorg-server-xephyr-1.19.3-2-x86_64.pkg.tar.xz
xorg-server-xephyr-1.19.3-3-x86_64.pkg.tar.xz
xorg-server-xephyr-1.19.4-1-x86_64.pkg.tar.xz
xorg-server-xephyr-1.19.5-1-x86_64.pkg.tar.xz
xorg-server-xephyr-1.19.6+13+gd0d1a694f-1-x86_64.pkg.tar.xz
xorg-server-xephyr-1.19.6+13+gd0d1a694f-2-x86_64.pkg.tar.xz
xorg-server-xephyr-1.19.6-2-x86_64.pkg.tar.xz
xorg-server-xephyr-1.20.0-2-x86_64.pkg.tar.xz... and downgrade using pacman, e.g.:
# pacman -U/var/cache/pacman/pkg/<Name of old xorg-server or xorg-server-common package>-x86_64.pkg.tar.xz
Also add xorg-server and xorg-server-common to IgnorePkg in /etc/pacman.conf with -
IgnorePkg = xorg-server xorg-server-common
so that they are skipped next time you do a system upgrade.
Offline
Hi,
I encountered the same problem with nvidia-340xx driver, but adding option "IgnoreABI" as @sayonalion suggested did not solve the problem. I had to downgrade xorg-server to 1.19.
Regards
Thank-you for this suggestion.
I spent entirely too long trying to fix this after misdiagnosing the issue as being related to my attempt to install a new graphics card.
Offline
Fixed now, but these nvidia/xorg issues are a real pain.
The boot hangs because the graphical login manager (gdm in my case) can't start. Then, the simplest fix involves booting up a USB install drive and chrooting to remove the login manager service from starting. Hopefully that's the last of 'em for a while.
6.5.3.arch1-1(x86_64) w/Gnome 44.4
Arch on: ASUS Pro-PRIME x470, AMD 5800X3D, AMD 6800XT, 32GB, | Intel NUC 7i5RYK | ASUS ux303ua | Surface Laptop
Offline
Hi,
Downgrade of xorg worked great for my 340xx - thanks also to the moderator who marked my post as a duplicate, which lead me to this.
Is there any alert system for when this issue is resolved (if ever) in xorg?
Best,
Offline
jal it should be fixed in testing for 340xx but it will be there a while because it coincided with linux 4.17 also being in testing.
You could rebuild nvidia-340xx 340.107 and nvidia-340xx-utils 340.107 locally for 4.16.
Offline
Sorry for necrobumping but the introduction of Xorg server 1.21.1.1 has revived that problem for all users on Nvidia legacy drivers again (version 340 and 390 of the proprietary Nvidia driver). I just found this thread on that occasion.
This time, it is ABI version 25.2 which is not supported by the Nvidia driver, and I am afraid that this time, Nvidia will no longer update the legacy drivers.
Fortunately, the workaround disabling the ABI check as provided in post #4 by Sayonalion works this time as well.
In /etc/X11/xorg.conf.d/20-server_flags.conf you will have to amend like below:
Section "ServerFlags"
Option "IgnoreABI" "1"
EndSection
Offline
This really isn't the same situation anymore, and nvidia will eventually fix 390xx, they've stated it is supported and receives compat fixes until the end of 2022.
Closing this old topic.
Last edited by V1del (2021-11-15 11:58:56)
Offline