Had the same issue, and I definitely feel the pain that you guys are experiencing. It sucks when an upstream package provider eliminates support for hardware that is still very prolific. I will say, the Arch wiki was a great help to me in restoring the graphics environment. I had the same issue where the resolution got squeezed after a reboot applied my pacman -Syu updates which I had done without checking the news or warnings. This page in particular - https://wiki.archlinux.org/title/NVIDIA - indicates that the 580xx-dkms were the drivers I would need. So in TTY I did the following steps which fixed my system perfectly without any further issues:
Cleared pacman cache Forcibly removed old nvidia drivers and associated libraries (there will be dependency complaints) While doing this, Steam complained about dependencies so I just uninstalled the steam native runtime as well Install older 580 series drivers indicated in the wiki Reboot That worked for me, but your situation may differ. On Thu, Jan 8, 2026 at 11:01 AM Russ <[email protected]> wrote: > I have a GTX 1080 or 1050 or something like that. It is easy to see if > your card has that chip. If it does, DO NOT UPDATE. I didnt realize I was > losing driver coverage until my monitors started looking like it was > trying to squeeze a 600X800 res monitor onto my 1900Xwhatever monitor. > After a bit of digging and banging my head on my desk, I figured out what > happened. I initially tried to install the backup driver that you > referenced but was unable to get it to work correction. I then tried to > get an old version of the just updated driver, but that was not trivial. > I'm sure this could be resolved given a sufficient amount of time expended > that I just didn't have, but the computer in question is used by one of my > employees, and I travel for months at at a time. I realized that if > something like this happened when I was traveling (granted, just don't > update...) she would have a bricked computer if I was not there to tinker > with it. For my application, this was my cue to change OSs for this > application. I put LMDE on this computer due to my application - not a > ding on arch, just wrong tool for the job there. > > In hindsight, if I knew what was being depreciated in the update in > advance, I would have made sure that the old version was never updated. My > advice is keep what you got and don't poke it! > > > > Russ > > > > *Confidentiality Notice: This message may contain confidential and/or > privileged information. If you are not the addressee or authorized to > receive this for the addressee, you must not use, copy, disclose, or take > any action based on this message or any information herein. If you have > received this message in error, please advise the sender immediately by > reply e-mail and delete this message.Non-Binding and Expiration Disclaimer: > Content of emails, to include any included links and attachments thereto, > sent or received shall not create a binding contract or be construed to be > conveyance or acceptance of any offer, contract or any other agreement, > whatsoever, nor shall the same be binding on any party until a written > contract is signed by all parties. In the event a bona fide, signed offer > is conveyed via email, the same shall expire, if not accepted and fully > executed by all parties, upon the latter of its explicitly stated > expiration date or, if such a date is not specified, twenty-four hours from > its initial transmission by the offeror and shall thereafter not be binding > on any party.* > > > > > *Wire Fraud Notice: Never trust wiring instructions sent via email. Cyber > criminals are hacking email accounts and sending emails with fake wiring > instructions. These emails are convincing and sophisticated. Always > independently confirm wiring instructions in person or via a telephone call > to a trusted and verified phone number. Never wire money without > double-checking that the wiring instructions are correct.Affiliated > Business Disclosure: I have an ownership interest in both Pink Realty, Inc > and Pink Realty Rentals and work closely with both companies and their > agents and employees, my real estate license and my brokerage activity is > with Pink Realty Rentals.* > > > On Thu, Jan 8, 2026 at 10:44 AM Mark E. Mallett <[email protected]> wrote: > >> Hi, >> >> There was a notice on arch-announce and on archlinux.org/news ( >> >> https://archlinux.org/news/nvidia-590-driver-drops-pascal-support-main-packages-switch-to-open-kernel-modules/ >> ) >> >> that confuses me. "With the update to driver version 590, the NVIDIA >> driver no longer supports Pascal (GTX 10xx) GPUs or older" etc. I don't >> really know if that applies to me, given the brand/model labels and all. >> (some detail about my hardware is offered at the end of this message.) >> And even if it does, the notice is (to my dull mind) unclear. It says: >> >> Updating the NVIDIA packages on systems with Pascal, Maxwell, or >> older cards will fail to load the driver, which may result in a >> broken graphical environment. >> >> That would be bad and makes me hesitent to experiment. >> >> Part of what confuses me is this: >> >> Users with GTX 10xx series and older cards must switch to the legacy >> proprietary branch to maintain support >> >> I'm using the proprietary nvidia driver already, so what does that >> statement >> mean to me? (I'm not running nouveau or other) >> >> So I have questions >> >> - the one above ("does this mean me?") >> >> - the one about already using the proprietary driver >> >> - can I simply not upgrade the nvidia driver, keep using the installed >> one? >> >> - If the system breaks, what is my recourse? >> >> - Is "Install nvidia-580xx-dkms from the AUR" (as it says) appropriate >> for me? >> >> I know this sounds like a lot of foggy nonunderstanding, and I guess >> that's >> because that's what it is. The relevant system has a very old NVIDIA >> card. I haven't seen any reactions to this, maybe I'm the only one left ;) >> >> Possibly relevant stuff from hwinfo: >> >> 22: PCI 100.0: 0300 VGA compatible controller (VGA) >> [Created at pci.395] >> Unique ID: VCu0.4tATP2A+FnB >> Parent ID: 8otl.w6ofvOouCK2 >> SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:01:00.0 >> SysFS BusID: 0000:01:00.0 >> Hardware Class: graphics card >> Model: "nVidia GM206 [GeForce GTX 960]" >> Vendor: pci 0x10de "nVidia Corporation" >> Device: pci 0x1401 "GM206 [GeForce GTX 960]" >> SubVendor: pci 0x1462 "Micro-Star International Co., Ltd. [MSI]" >> SubDevice: pci 0x3201 >> Revision: 0xa1 >> Driver: "nvidia" >> Driver Modules: "nvidia" >> Memory Range: 0xfd000000-0xfdffffff (rw,non-prefetchable) >> Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable) >> Memory Range: 0xce000000-0xcfffffff (ro,non-prefetchable) >> I/O Ports: 0xcc00-0xcc7f (rw) >> Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) >> IRQ: 27 (1392224 events) >> Module Alias: "pci:v000010DEd00001401sv00001462sd00003201bc03sc00i00" >> Driver Info #0: >> Driver Status: nouveau is not active >> Driver Activation Cmd: "modprobe nouveau" >> Driver Info #1: >> Driver Status: nvidia_drm is active >> Driver Activation Cmd: "modprobe nvidia_drm" >> Driver Info #2: >> Driver Status: nvidia is active >> Driver Activation Cmd: "modprobe nvidia" >> Config Status: cfg=new, avail=yes, need=no, active=unknown >> Attached to: #20 (PCI bridge) >> >> >> Thanks for any attention. >> >> -mm- (long time no write) >> >> >>
