For AMD/ATI: updated all apps to match the v8.24 stock release, with safety patch for RX 5700-series 'NAVI' GPUs. You must also upgrade to the Adrenalin 2020 Edition 20.1.2 Optional driver or later.

I never did. I'm still running 20.1.1, which in its release notes states: "Fixed result overflows that can be experienced with Radeon RX 5700 series when using SETI@Home"

I never did. I'm still running 20.1.1, which in its release notes states: "Fixed result overflows that can be experienced with Radeon RX 5700 series when using SETI@Home"

At your own risk. I was following Keith's message 2028458.

And if that's the worst bug in the installer, I'm off to bed. See you in the (UK) morning.

The Adrenaline 20.1.2 Optional drivers were what the AMD Support site listed were current as of my post and offered automatically on the download page. Think they are up to 20.1.4 now.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I am testing the new version of Lunatics for a week now. No problems with 20.1.1 and up (so far). Looks very good on my side.

The Adrenaline 20.1.2 Optional drivers were what the AMD Support site listed were current as of my post and offered automatically on the download page. Think they are up to 20.1.4 now.

I think the original 20.1.1 were described here as Beta drivers, and might have been harder for users to find.

Hello Richard!

The Adrenalin 2020 Edition 20.1.1, 20.1.2, 20.1.3 and the 20.1.4 Optional are all beta (with the Seti@home fix) drivers.

The last non-beta driver is Adrenalin 2020 Edition 19.12.2 Recommended (without the Seti@home fix).

So you need to have a beta driver installed to get Seti@home working.

OK, thanks. I don't own an AMD card so I'm not a habitual visitor to their website. If they fixed the original problem in .1, I wonder what else they fixed in .2, .3, and .4?

The Adrenaline 20.1.2 Optional drivers were what the AMD Support site listed were current as of my post and offered automatically on the download page. Think they are up to 20.1.4 now.

It's not about which version they show as (optional) current, it's about which version had the fix and states that in its release notes. 20.1.2 does not say that the fix for Seti@Home was in that version, it may be incorporated but it's not the version with the fix. So we don't have to scare everyone out there that they're using the wrong driver version (20.1.1) when they aren't.

You must also upgrade

@Richard. The release notes state per version what they fixed:
20.1.1
20.1.2
20.1.3
20.1.4

20.1.2.:

Support For

- Dragon Ball Zâ„¢: Kakarot
- Vulkan®1.2
Product is conformant with the Vulkan® 1.2 Specification. Vulkan and the Vulkan logo are registered trademarks of the Khronos Group Inc.

Fixed Issues

- Some UE4 based titles such as KovaaK 2.0: The Metaâ„¢, Tetris Effectâ„¢ and Snooker 19â„¢ may fail to launch with Adrenalin 2020 edition software.
- Some single display Radeon RX 5700 series graphics product system configurations may experience intermittent reboots when the system is left idle on desktop.

Source: https://www.amd.com/en/support/kb/release-notes/rn-rad-win-20-1-2

20.1.3.:

Support For

- Radeon RX 5600 XT

Fixed Issues

- An intermittent black screen or loss of display may occur when performing parallel actions such as web browsing, gaming or watching video.
- A limited number of games such as Niohâ„¢, Dragon Quest Builders 2â„¢, WWEâ„¢2K20, Dead or Alive 6â„¢ and Atelier Ryzaâ„¢ may crash or fail to launch.
- Wolfensteinâ„¢ 2: The New Colossus is not detected in Radeon Software games manager.
- Text overflow in some UI boxes or toast messages may be experienced in some language localizations.
- Fan Tuning may change back to the default state when switching between available GPUs.
- Copy text options are not available in the display specs table for Radeon Software.
- An intermittent black screen or loss of display may occur when the system is left idle at desktop.
- Factory Reset install may keep previously configured Radeon Software game profiles. This can cause mismatch between global graphics settings and per profile settings.

Source: https://www.amd.com/en/support/kb/release-notes/rn-rad-win-20-1-3

20.1.4.:

Support For

- Warcraft III: Reforgedâ„¢
- With high presets on the Radeon™ RX 5700 XT, achieve up to 11% better performance playing Warcraft® III: Reforged™ with Radeon™ Software Adrenalin 2020 edition 20.1.4 than with Radeon™ Software Adrenalin 2020 Edition 20.1.3.RS-331
Journey to the Savage Planetâ„¢

Fixed Issues

- Red Dead Redemption 2™ may experience square or blocky textures on some terrain during gameplay when using Vulkan® API.
- Some Vulkan® API games may experience a crash or application hang when performing a task switch while Radeon Image Sharpening is enabled.
- Text overflow is observed in toast messages for some languages.
- Radeon ReLive may fail to switch recording to desktop when Radeon Software is open.
- Grand Theft Autoâ„¢ 5 may experience a system hang or black screen at launch, when opening Radeon Overlay while in game, or after performing a task switch while in game.
- Audio may intermittently be missing from Radeon ReLive recordings near the end of recorded clips.
- Integer Scaling option is not showing up or available on some Windows®7 system configurations.


[url]https://www.amd.com/en/support/kb/release-notes/rn-rad-win-20-1-4[/url

Edit: I was to late. :-(

OK, OK. I've done a minor refresh on the build, primarily to provide a better return path from OpenCL_NV_sah to CUDA. But I've taken the opportunity to change the ATI required driver version in the documentation.

If any mirror site operator has jumped the gun and mirrored this installer before the end of testing, please update - mirroring is absolutely fine and welcome, but I'd prefer you to wait until we confirm an official release at the end of testing.

BTW, the NV return path was primarily prompted by a couple of PMs received overnight. I'd prefer it if any installer problems were reported here on the boards, so that other testers and users can be alerted quickly and can confirm any problems. I'd keep PMs for the private pre-release stuff. And having said that, it's great to see Schatten posting here - he and Jord were the only two people who responded to my call for alpha testers.

Well over 48 hours since I posted the refreshed installer. I've had precisely one PM saying it's looking OK, and no more reported quibbles. Are we good to go? I'd like to see some actual tester feedback, please - good or bad.

Well you know it's running fine, as I copied everything from the test directory in the main project directory and am running with that. On my broken BOINC. ;-)
But if you have as many testers as we have at BOINC, we're in for heavy weather.

The AMD/ATI App is fine. No Problems yet on my 5700 xt with it. I give it a "GO".

Note:

Testing since 21th of January. Before I "tested" with the old Lunatics and the new driver. That didn't went very well and some invalid tasks from this time come up from time to time. This was the time when we had the database issue and when i saw it it was too late and i canceled the remaining tasks. Dumb me.

Well over 48 hours since I posted the refreshed installer. I've had precisely one PM saying it's looking OK, and no more reported quibbles. Are we good to go? I'd like to see some actual tester feedback, please - good or bad.

. . Does that include installing it for a Windows machine running a GTX1050 ??

Stephen

? ?

Well over 48 hours since I posted the refreshed installer. I've had precisely one PM saying it's looking OK, and no more reported quibbles. Are we good to go? I'd like to see some actual tester feedback, please - good or bad.

. . Does that include installing it for a Windows machine running a GTX1050 ??

Stephen

? ?

You should be asking that in this thread Stephen. ;-)

https://setiathome.berkeley.edu/forum_thread.php?id=84694

But if you want to run the latest drivers then there is a 2nd OpenCL app there to use. ;-)

Cheers.

Well over 48 hours since I posted the refreshed installer. I've had precisely one PM saying it's looking OK, and no more reported quibbles. Are we good to go? I'd like to see some actual tester feedback, please - good or bad.

. . Does that include installing it for a Windows machine running a GTX1050 ??

Stephen

? ?

You should be asking that in this thread Stephen. ;-)

https://setiathome.berkeley.edu/forum_thread.php?id=84694

But if you want to run the latest drivers then there is a 2nd OpenCL app there to use. ;-)

Cheers.

. . Thanks but i wasn't concerned about the latest drivers issue, I am not running them. I just wanted to know if Richard was interested in feedback on installing the latest Lunatics version on a Windows/Nvidia rig ...

Stephen

Well over 48 hours since I posted the refreshed installer. I've had precisely one PM saying it's looking OK, and no more reported quibbles. Are we good to go? I'd like to see some actual tester feedback, please - good or bad.

. . Does that include installing it for a Windows machine running a GTX1050 ??

Stephen

? ?

You should be asking that in this thread Stephen. ;-)

https://setiathome.berkeley.edu/forum_thread.php?id=84694

But if you want to run the latest drivers then there is a 2nd OpenCL app there to use. ;-)

Cheers.

. . Thanks but i wasn't concerned about the latest drivers issue, I am not running them. I just wanted to know if Richard was interested in feedback on installing the latest Lunatics version on a Windows/Nvidia rig ...

Stephen

*forehead slap* :-(

OK, bad news first: it would appear that this issue is still responsible for the entire SETI@Home project's recent two-week spate of no or low work, stalled up/downloads, scheduler timeouts and general slowness. This is because to avoid the RXs from cross-validating, all overflow results whether from them or not are now set to a quorum of three rather than two. Whenever we get a "shorty storm" of "noise bomb" work units, these are all -9 overflows and will trigger the quorum = 3 and resends. The result is that millions more tasks then need to be re-sent to third computers (resulting in the puzzler of stalling up/download servers even with no work being generated) and the results table overflowing with >20M active tasks awaiting validation, so work generation is turned off leading to much angst.

The good (very) news: As of Jan. 29, the fixed AMD drivers (20.1.3) are now WHQLed/Recommended rather than Optional. This means that they may start appearing in Windows updates rather than needing manual installation. (This is one of the times I can be happy about Windows 10's pushiness with updates!) Once this happens, soon everyone will have them and this issue is very happily a thing of the past.

Please, if someone with an AMD card could verify when 20.1.3 or later is being offered as a Windows update, this would be very much appreciated. I hope that, unlike the NVidia drivers, that the Windows-provided AMD ones are more complete with OpenCL included so no manual installation is required.

Edit: Thanks Richard... the proverbial "perfect storm" of those two issues. I'll definitely mention that.

---

The other good news is that we are nearing the end of the penultimate BLC35 file. Although there are other sources of overflow tasks, that's been the most prolific in recent weeks. If you can persuade Eric to say 'thanks, but no thanks' to any more BLC35 tapes (at least for the time being), that would help, too.

The one pending install on a new system I have built and am still installing Windows Updates on, is Advanced Micro Devices, Inc. 2.2.0.124
I'll wait until after the installation to see what that translates into.

Edit: Windows Update states it downloaded and installed 2.2.0.124, but in Device Manager the Radeon RX 470 still shows as driver install date 26/08/2019, driver version 26.20.12028.2
So I don't know what it does there. I'll install BOINC and see what it finds.

Ah:
02/03/20 22:06:15 | | OpenCL: AMD/ATI GPU 0: Radeon (TM) RX 470 Graphics (driver version 2841.19, device version OpenCL 2.0 AMD-APP (2841.19), 8192MB, 8192MB available, 5161 GFLOPS peak)

Why would Windows 10 state it downloaded and installed 2.2.0.124 when it clearly hasn't?
But at least I now learned that drivers installed by Windows itself do include OpenCL.