Posts by Ageless

1) Message boards : Number crunching : Windows 10 - Yea or Nay? (Message 1970287)
Posted 4 hours ago by Profile Ageless
Post:
https://lifehacker.com/windows-10-collects-activity-data-even-when-tracking-is-1831054394 has a blocking workaround for the problem, while the rest waits for Microsoft to fix it (whenever).
2) Message boards : Number crunching : Incorrect timing in the "Not sending work - last request too recent:" logic. (Message 1970113)
Posted 1 day ago by Profile Ageless
Post:
You get that effect as well when you have a very low Store at least N days of work and a high Store up to an additional N days of work, as the first is the low water mark and when BOINC sends one task back, it immediately tries to up the cache again by at least one task to make the low water mark.
3) Message boards : Number crunching : Please help: BOINC not seeing 2nd GPU Windows 10 (Message 1970110)
Posted 1 day ago by Profile Ageless
Post:
When changing GPUs always uninstall & clean out the old drivers. Use something like Display Driver Uninstaller for that, from Windows Safe Mode.
Then boot to normal mode and install the new drivers. Even when the system doesn't ask for it, reboot at the end of the installation. You ought to be able to install the same drivers for both GPUs, if both are AMD and GCN GPUs.

I found it: C:\ProgramData\BOINC\projects\setiathome.berkeley.edu
That's not where the cc_config.xml file should go.

cc_config.xml is a BOINC configuration file, not a Seti file. So it should go into the BOINC Data directory, C:\ProgramData\BOINC
Make sure first there isn't already such a file there, and that it doesn't already contain a line for <use_all_gpus>, because if you add your own line at the top of the file, and there's another at the bottom with an opposite switch, the last line is used. If a line is present, change its value from 0 to 1 and save the file.

But to be able to use the <use_all_gpus> switch, BOINC should first detect both GPUs, which it isn't yet doing. When in doubt, post the first 30 or so lines of your BOINC messages (CTRL+SHIFT+E).
4) Questions and Answers : Unix/Linux : Your app_info.xml file doesn't have a usable version of SETI@home v8. xubuntu1804 (Message 1970031)
Posted 1 day ago by Profile Ageless
Post:
Either remove the app_info.xml file and then reset the project, or post the contents of your app_info.xml file.
5) Message boards : Number crunching : Error while computing on Android (Message 1970005)
Posted 2 days ago by Profile Ageless
Post:
Read https://setiathome.berkeley.edu/forum_thread.php?id=82842 on that.

To answer your question, it's a Seti@Home problem in combination with your 32bit CPUs AND Android 8. Until new science applications are released, this won't be fixable by you. Your only option is to either replace the devices with newer versions, to go back to an older Android version (force a downgrade) or to cease using these devices.
6) Questions and Answers : Getting started : Bulgarian language? (Message 1969837)
Posted 3 days ago by Profile Ageless
Post:
See https://boinc.berkeley.edu/trac/wiki/TranslateIntro for what is needed.
7) Message boards : Number crunching : Windows 10 - Yea or Nay? (Message 1969824)
Posted 3 days ago by Profile Ageless
Post:
Latest news, read all about it!
https://www.howtogeek.com/fyi/windows-10-sends-your-activity-history-to-microsoft-even-if-you-tell-it-not-to/

Windows 10 collects an “Activity History” of applications you launch on your PC and sends it to Microsoft. Even if you disable or clear this, Microsoft’s Privacy Dashboard still shows an “Activity History” of applications you’ve launched on your PCs.
8) Message boards : Number crunching : Windows 10 - Yea or Nay? (Message 1969296)
Posted 6 days ago by Profile Ageless
Post:
https://www.techradar.com/news/microsoft-halts-yet-another-windows-10-update-after-blue-screen-of-death-errors

Microsoft’s Windows 10 update woes are continuing, with the company having to halt the recent Windows 10 November 2018 cumulative update (KB4467682) after reports it was causing PCs to crash and display the infamous ‘Blue Screen of Death’.

At first, the errors appeared to only affect the Surface Book 2, Microsoft’s own hardware, which lead to the company halting the update for those devices.

However, Microsoft has now revealed that the problem is more widespread, and it has now pulled the update from all devices.

In a new support post, Microsoft explains that “After installing this optional update some users have reported getting a blue or black screen with error code, “System thread exception not handled.” As a precaution, we have removed this optional update from Windows Update and Microsoft Update Catalog to protect customers.”
9) Message boards : Number crunching : Windows 10 - Yea or Nay? (Message 1969019)
Posted 7 days ago by Profile Ageless
Post:
Greetings Jord
No, no, I fell for that the last time around, ain't doing it now.

@JC4:
Have asked for and been refunded JC4, after playing it for an eye-watering hour and a half. If you're still unsure, do read this review and reconsider. As long as developers are allowed by the GP to release crap like this, they'll never learn.
10) Message boards : Number crunching : Windows 10 - Yea or Nay? (Message 1968887)
Posted 8 days ago by Profile Ageless
Post:
https://www.theinquirer.net/inquirer/news/3067659/microsofts-windows-10-debacle-has-affected-cisco-and-morphisec-endpoints

Two major Endpoint security modules, Morphisec's Protector and Cisco's AMP for Endpoints, are screwing with Windows (or perhaps more accurately, Windows is screwing with them) and so users of both have been blocked from installing the dreaded Build 1809, aka the Windows 10 October 2018 Update.

They join an ever-widening group of users who have been affected, including anyone with a small hard drive (that's what she said), anyone who uses ZIP files, anyone using HP, anyone who uses iTunes and iCloud (this one is fixed), anyone with a NAS or other network connected drive, anyone using Universal Windows apps, certain AMD chip users, users of Intel audio drivers, VPNs from F5 and some Trend Micro security software, and indeed anyone to so much as give it a funny look.
11) Questions and Answers : Windows : SETI@Home crashes windows (Message 1968797)
Posted 9 days ago by Profile Ageless
Post:
When was the last time you cleaned out the dust? Seeing how you have a laptop or notebook, that may be problematic, but try to clean the intakes and outlets anyway, with a toothbrush or other fine brush.

You can also opt for a cooling stand, a small table with one or more fans that forcibly blow cooler air into your laptop.
12) Questions and Answers : GPU applications : Reporting incorrect GPU info (Message 1968699)
Posted 9 days ago by Profile Ageless
Post:
BOINC doesn't think, it detects GPUs based on what the drivers tells it are the values for:
compute capability, software version, available memory, speed for Nvidia GPUs and double precision support, local RAM and speed for AMD GPUs.

BOINC doesn't know any GPUs. It knows it should look for a CUDA, CAL or OpenCL driver and derive the above from those. CAL is only used on old ATI GPUs (HD4000, 5000, 6000, some non-GCN 7000).

From gpu_detect.cpp:
// client-specific GPU code. Mostly GPU detection
//
// theory of operation:
// there are two ways of detecting GPUs:
// - vendor-specific libraries like CUDA and CAL,
// which detect only that vendor's GPUs
// - OpenCL, which can detect multiple types of GPUs,
// including nvidia/amd/intel as well was new types
// such as ARM integrated GPUs
//
// These libraries sometimes crash,
// and we've been unable to trap these via signal and exception handlers.
// So we do GPU detection in a separate process (boinc --detect_gpus)
// This process writes an XML file "coproc_info.xml" containing
// - lists of GPU detected via CUDA and CAL
// - lists of nvidia/amd/intel GPUs detected via OpenCL
// - a list of other GPUs detected via OpenCL
//
// When the process finishes, the client parses the info file.
// Then for each vendor it "correlates" the GPUs, which includes:
// - matching up the OpenCL and vendor-specific descriptions, if both exist
// - finding the most capable GPU, and seeing which other GPUs
// are similar to it in hardware and RAM.
// Other GPUs are not used.
// - copy these to the COPROCS structure
//
// Also, some dual-GPU laptops (e.g., Macbook Pro) don't power
// down the more powerful GPU until all applications which used
// them exit. Doing GPU detection in a second, short-lived process
// saves battery life on these laptops.
//
// GPUs can also be explicitly described in cc_config.xml

If you still feel the code does things wrong, then by all means register at Github and make it an issue, as else it won't get looked at. The volunteer BOINC developers don't read these forums.
13) Questions and Answers : GPU applications : How to use multiple GPU's (Message 1968694)
Posted 9 days ago by Profile Ageless
Post:
You manually added <use_all_gpus>1</use_all_gpus> to your cc_config.xml file, but there's already one in there. Remove the line you added, scroll down and change the 0 on the later line to 1, then save the file. All options lines should only be used once in cc_config.xml

A full cc_config.xml file is saved to the data directory when you add an exclusive app via the menus in BOINC Manager, or when you make a change to the Event Log options menu and save that. When you next edit that file and add anything to the top, BOINC will read the file, find your added line that switches something on, then continue down to the bottom, find the line that switches it off again and that there is the problem you have.

Always check if the line you wanted isn't already in the file. They're in alphabetical order, so you can easily glance at commands starting with U.

By default BOINC uses only the best GPU it detects, any lesser GPUs are not used.
It'll do this based on what it detects in the drivers for compute capability, software version, available memory and speed.
14) Message boards : Number crunching : Windows 10 - Yea or Nay? (Message 1968687)
Posted 9 days ago by Profile Ageless
Post:
Heh, want to see something broken? Try Just Cause 4, released today. The menus alone are a nightmare, with some using a back-button to get back to the previous menu, others needing to right-click to do that, yet more others requiring you to use the arrow keys to scroll through to get to a back-button. I think I spent the full 90 euros on it for the pre-release plus DLC option. Am now wondering if I should go for s refund. ;-)
15) Questions and Answers : GPU applications : How to use multiple GPU's (Message 1968665)
Posted 10 days ago by Profile Ageless
Post:
cc_config.xml
Added <use_all_gpus>1</use_all_gpus> under options.

Did you exit & restart BOINC completely after adding this? By completely I don't just mean exit BOINC Manager and restart it because this may just restart the Manager, not the client. Command decisions, including all detection of CPU and GPU are made only at BOINC startup.

Can you also post the contents of your cc_config.xml file?
The only extension on cc_config.xml is xml? If you edited the file with Notepad, it may have added .txt to the end (and with Windows default still hiding known extensions, you may never know!)
16) Message boards : Number crunching : Private Message Inbox SPAMMED! (Message 1968324)
Posted 11 days ago by Profile Ageless
Post:
Just use the red X in the inbox, it will filter the [redacted]
I know, but by leaving him alone you can easily check if admin has done something with the information (like banish the spammer). As I understand, Eric wasn't around the past week, so that's probably why the [redacted] is still around. I'm sure he'll evaporate from my inbox eventually. :)
17) Message boards : Number crunching : Private Message Inbox SPAMMED! (Message 1968228)
Posted 12 days ago by Profile Ageless
Post:
I reported that one to Eric on Tuesday. Haven't heard back and that account is still taking up a large swat of my inbox. Lots of all CAPS.
18) Questions and Answers : GPU applications : Error in Computation for OpenCl Tasks after Updating Nvidia Drivers (Message 1967538)
Posted 15 days ago by Profile Ageless
Post:
I'd uninstall the drivers and reinstall them, this time clean. That's an option in the installer.
The error you're throwing is that you're missing a DLL file, most probably in the OpenCL driver part, which can only be fixed by reinstalling the drivers and hope that fixes it, or going back to previous - and known to be working - drivers.
19) Questions and Answers : GPU applications : GPU Missing. Waiting execution (Message 1967456)
Posted 16 days ago by Profile Ageless
Post:
Did you install drivers, or allow Windows to update the drivers?
Reasons why the GPU goes missing are:
1. Installed drivers without CUDA or OpenCL. The drivers installed by Windows don't necessarily contain these. Always install only drivers from Nvidia's website.
2. You installed BOINC as a service. Because the drivers then run in a separate account from the user, BOINC isn't able to see them, thus no GPU.

It ain't 2, as your 1050Ti is still visible. But it may be 1, where you only have CUDA installed but are missing OpenCL, and with all your GPU tasks requiring the OpenCL SoG application, that then accounts for "GPU missing".

You'll have to be more eloquent about what happened to your system.
20) Questions and Answers : GPU applications : GPU suspende user's request (Message 1967011)
Posted 18 days ago by Profile Ageless
Post:
GPU Suspended - user request happens when:
1. You've set BOINC Manager->Activity->GPU usage to "Suspend GPU".
(25/11/2018 17:56:49 | | Suspending GPU computation - user request)
2. You've set GPU Snooze to on -> right click the BOINC icon in the system tray->Snooze GPU. However, this only works for an hour, not days, weeks or months.

So go to the Activity menu in BOINC Manager and set GPU usage to "Run based on preferences". Then it will follow the preferences you set via the web site or local preferences. Only set the GPU usage to "Always" when you really want the GPU to be used always, and interfere with anything else happening on your computer.


Next 20


 
©2018 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.