from the graphic-drivers-are-logo-emblazoned-golf-clubs dept.
AMD Ceases Graphics Driver Development for 32-bit Operating Systems
With the recent October releases of Adrenalin Edition, AMD has finally discontinued support for 32-bit operating systems. The latest 32-bit packages can still be manually downloaded through older driver release notes, of which Adrenalin Edition 18.9.3 is the last release with 32-bit drivers.
The change doesn't come as a surprise. Earlier this year, NVIDIA ceased driver development for 32-bit OSes, and early last year AMD dropped graphics driver support for 32-bit Windows 8.1. Pre-GCN hardware was moved to legacy status back in 2015. Ultimately, the idea is to concentrate development and engineering resources, particularly if those resources are limited. Over the past few years, AMD has put in a renewed effort in graphics driver development, retiring Catalyst for "Radeon Software" and embarking on major annual updates, both for gaming and professional products. In that sense, prolonging 32-bit support diffuses focus for very specific edge cases for little benefit, and that goes for both NVIDIA and AMD.
Previously: Nvidia to Stop Writing Drivers for 32-Bit Systems (Eventually)
Nvidia Ends Mainstream Support for Fermi GPUs and 32-Bit Operating Systems
Related Stories
Nvidia to cease producing new drivers for 32-bit systems
While most people have probably made the switch by now, yet another reason to drop 32-bit operating systems and move to 64-bits is coming. Version 390 of Nvidia's graphics drivers, likely to arrive in January, will be the last to contain support for 32-bit versions of Windows (7, 8/8.1, and 10), Linux, and FreeBSD.
There will be another year of security updates for 32-bit drivers, but all new features, performance enhancements, and support for new hardware will require the use of a 64-bit operating system and 64-bit drivers.
This week, NVIDIA has announced that they are ending mainstream graphics driver support for Fermi-based GeForce GPUs. Effective as of this month (i.e. immediately), all Fermi products are being moved to legacy support status, meaning they will no longer receive Game Ready driver enhancements, performance optimizations, and bugfixes. Instead, they will only receive critical bugfixes through the end of the legacy support phase in January 2019.
While the announcement mentions 'Fermi series GeForce GPUs,' the actual support plan specifies that mainstream driver support is limited to Kepler, Maxwell, and Pascal GPUs. So presumably all Fermi products are affected.
In the same vein, also effective this month is NVIDIA dropping mainstream driver support for 32-bit operating systems, as announced in December 2017. Like Fermi, 32-bit operating systems will still receive critical security updates through January 2019. This update also encompasses GeForce Experience, which will no longer receive software updates for Windows 32-bit operating systems.
Previously:
Nvidia to Stop Writing Drivers for 32-Bit Systems (Eventually)
AMD's Latest Radeon Drivers Finally Bring Official Support to Ryzen Mobile
When Ryzen Mobile launched in October of 2017, most probably did not envision the poor state its drivers would be in for over a year. AMD never released an official driver for its Raven Ridge-based mobile APUs, so users had to rely on OEMs like HP that only released a single driver in November.
But at CES 2019, AMD promised to fix the situation with official support for Ryzen Mobile through its Adrenaline drivers. Those are the same drivers that already supported AMD's desktop APUs based on the same Raven Ridge architecture used for Ryzen Mobile. Today, AMD finally delivered on that promise with its newest 19.2.3 drivers.
According to AMD's release notes, the new driver offers an average of 10% more performance in gaming compared to the October Ryzen Mobile driver, and in eSports titles specifically, an average of 17% more performance. Of the games tested, most of them showed double-digit performance gains, especially Counter Strike: Global Offensive and Player Unknown's Battlegrounds. These kinds of gains could easily turn an unplayable experience into one that is playable, and such extreme gains are seen because this driver is a year and a half newer than the launch revision.
Also at Engadget.
Related: AMD Finally Pushing Out Open-Source Vulkan Driver
AMD Ceases Graphics Driver Development for 32-Bit Operating Systems
(Score: 1, Insightful) by Anonymous Coward on Tuesday October 30 2018, @02:10AM (8 children)
This is just further proof that professional programmers are actually dumbasses who don't employ even the most basic abstractions.
(Score: 2, Disagree) by Runaway1956 on Tuesday October 30 2018, @02:35AM (5 children)
Are you seriously trying to put the latest and greatest video card into a 32 bit computer? Come on dude - there is "backward compatibility", but FFS, you simply cannot make use of a GTX 1080 in a TRS-80.
As for 32 bit operating systems on 64 bit capable systems - you've already foregone using the CPU's built in capabilities. Do you really think you can put that GTX 1080 to it's best use by constraining how it communicates with the CPU?
Need an auto analogy? You can't take the turbo charger out of an F1 formula car, and pop it into a 1963 Ford Falcon. It's unsupported, it won't work, and you will have wasted a lot of money. Doesn't matter how much you want a turbocharged Falcon, it isn't going to work. You probably CAN hire an engineer to build a turbocharger specifically designed to enhance that old six-cylinder engine - but it's going to cost you.
In the case of these graphic drivers, AMD is simply announcing that they won't bear the cost of supporting old, obsolete equipment any longer.
Alternative für Deutschland
(Score: 1, Informative) by Anonymous Coward on Tuesday October 30 2018, @03:00AM (2 children)
AMD is saying they are dropping support for a product that has hitherto been supported on 32-bit machines.
(Score: 4, Insightful) by c0lo on Tuesday October 30 2018, @04:36AM (1 child)
Does it mean that the currently available drivers will cease to exist, will be no longer available to download or otherwise the installed drivers will become unusable?
To my mind it mean no more and no less than: "no new versions or bug updates for the 32 bits versions in the future".
https://www.youtube.com/@ProfSteveKeen https://soylentnews.org/~MichaelDavidCrawford
(Score: 0) by Anonymous Coward on Tuesday October 30 2018, @03:41PM
SIGH
(Score: 2) by FatPhil on Tuesday October 30 2018, @10:14AM
Don't get me wrong, as someone who's been 64-bit since the 90s (DEC Alpha fanboi at your service), I can't say I'm sorry to see the 32-bit world fall off the desktop.
Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves
(Score: 1) by shrewdsheep on Tuesday October 30 2018, @11:10AM
Why so far fetched?
'nuff said
(Score: 0) by Anonymous Coward on Tuesday October 30 2018, @12:04PM
Unless written direectly in ASSEM and code per CPU model, there is NO, repeat NO, reason to need one over the other,, they code is equal.
This is purely a money grab. DESTORY the old so they buy a new. ANYONE who is believes other wise is foul who deserve the cash being SUCKED from their pockets.
WRITTEN on a 16yr old machine and surrounded by 7 other equally old, if it not older machines... ALL RUNNING the LATEST 2018 software. Planned obsolescence my eye!.
(Score: 2) by tibman on Wednesday October 31 2018, @03:01AM
Don't insult people when you have no idea what you're talking about. Compilers turn non-cpu specific code into a cpu specific executable. Programmers write in a generic language that is abstracted away from hardware targets. You can compile the same C program for 8bit Atmel microcontrollers, or 32bit ARM cpus, or 64bit x86-64.
A company probably won't run that hardware, legacy OS, and test all the executables when it affects like 0.1% of the customer base. 64bit x86 CPUs have been available for ~15 years. Linux support was there for a long time. Windows went grudgingly but it's there now. If you're using 10 year old hardware, then you should really be glad they supported it for so long. Surely that old hardware has damn good drivers by now?
SN won't survive on lurkers alone. Write comments.
(Score: 2) by bzipitidoo on Tuesday October 30 2018, @03:07AM (1 child)
I have a Radeon HD 5450 (the lowest and cheapest of the 5000 series) in a 64bit computer. AMD announced some 5 years ago that they would not be updating the drivers for the 5000 series any more, and so there was no point downloading and updating to their latest drivers.
But, as is typical, they didn't handle the sunset too well. Instead of making sure the sunset operations work correctly, they allowed their Windows driver update software to get into an endless loop. It upgrades, then next boot downgrades, then the boot after that upgrades again. Or, you can tell it not to upgrade, but somehow you can't tell it not to nag you about upgrades, so you have to tell it not to upgrade every time you boot.
I suppose it's understandable that fixing such issues is low on their list of priorities. And maybe the harassment will help nudge the end user into upgrading. That's commercial software for you :p.
(Score: 0) by Anonymous Coward on Tuesday October 30 2018, @03:12AM
That's the problem with proprietary software; it ain't your property.
(Score: 2) by RamiK on Tuesday October 30 2018, @08:49AM (4 children)
Latest x86 is 390.87 legacy (2018.8.27) while the latest x86_64 is 410.57 stable (2018.10.25): https://www.nvidia.com/object/unix.html [nvidia.com]
Pretty sure all the 32bit proprietary games and CAD software require the 32bit drivers so they won't be supported on new nVidia graphics cards now. That includes wine of course...
compiling...
(Score: 0) by Anonymous Coward on Wednesday October 31 2018, @01:14AM (1 child)
They certainly do not require 32-bit drivers. 32-bit libraries probably, but that is handled elsewhere and there are entire distros now that drop x86 support.
For example Arch has https://www.archlinux.org/packages/multilib/x86_64/lib32-nvidia-utils/ [archlinux.org] which provides 32-bit libraries to legacy applications on amd64 distribution in the latest version 410.x.
(Score: 0) by Anonymous Coward on Wednesday October 31 2018, @03:27AM
OP (probably?) referring to the issues you can google with "wine nvidia 396 32bit". It seems some install scripts (binary blobs so not exactly scripts) were definitely broken as well as wine in some distros. Some of it got fixed. Some old stuff will never be fixed. Since most distros skip the short lived branches (beta) and most users avoid the unstable distros, it will take over a year before everyone switches over and notices the issues.
e.g. early in the release cycle Steam was being "smart" and trying to install "missing" packages under debian/ubuntu using the wrong package names. In Mint this might still be an issue.
Already people are installing the old driver, deploying their proprietary crap, and then upgrading the driver thus avoiding the issue. In newer hardware this won't be an option so it will come biting users in the ass later on.
(Score: 0) by Anonymous Coward on Thursday November 01 2018, @12:47AM (1 child)
Only the kernel module is limited to amd64. The amd64 driver contains both ia32 and amd64 OpenGL libraries.
(Score: 2) by RamiK on Thursday November 01 2018, @09:24AM
While saying "all" was wrong, as the other reply to the other reply mentioned, it's buggy in the real world and will take months for distros users to test out and some stuff will never work unless someone actively hacks the install blobs and removes false dependencies and the likes.
compiling...
(Score: 2) by SomeGuy on Tuesday October 30 2018, @09:10AM (3 children)
Just a reminder that 32-bit Windows 10 is still out there. When people were tricked in to upgrading from Windows 7 to 10 they automatically got the same bit-nes as they were already running, and Windows 7-32 bit was the most common for several years after it came out. Granted, most people who are running it probably don't even know what they have and are not likely to buy one of these fancy shmancy gaming video cards.
I haven't heard of any change in its support status from Microsoft. Although these days I simply expect when I turn on a computer it will tell me "Michael Dell needs to buy a new yacht, go give him some more money".
I remember a day when one could fit a fun game in 4k bytes of memory.
(Score: 2) by Pino P on Tuesday October 30 2018, @02:49PM
Such as the NES version of Martin Korth's Magic Floor [problemkaputt.de]. But its presentation is fairly basic, and the Game Boy port is quite a bit bigger than that, maybe about 10K so far.
(Score: 2) by Freeman on Tuesday October 30 2018, @04:03PM (1 child)
I would argue that a 4k or 10k game had enough technical limitations that it reduced the fun quality of the game. Not that it wasn't a great game for the system it was created on, just that it could have been much more fun with a little bit more resources. Games like X-COM, Master of Magic, and Ultima VII still are a joy to play (each taking up 10 to 50 MB), if you can get them to work on your computer. Generally, DOSBox is an acceptable quality for X-COM and Master of Magic, while Exult has been great for running Ultima VII on modern computers. The Exult team even backported the magic keyring from the Silver Seed and a couple of other "quality of life" enhancements.
Joshua 1:9 "Be strong and of a good courage; be not afraid, neither be thou dismayed: for the Lord thy God is with thee"
(Score: 2) by takyon on Tuesday October 30 2018, @09:51PM
I agree. There's nothing technically stopping a 100 gigabyte game from being fun, since you can fit all the code you want in there before moving on to the evul graphics (cue the angry gameplay vs. graphics anon). But a 4 KB/KiB game is going to be limited by the file size. It could be fun, and it might do a lot within its limits, but it won't represent the full range of what could be possible with more code.
[SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]