Welcome to MilkyWay@home

Posts by Sebastian*

21) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65221)
Posted 20 Sep 2016 by Sebastian*
Post:
The Computer with the R9 390X isn't even initializing the Project. It does not download the .exe -file or any other files. I copied them in manually, with an app_config file. I got the message, that the app_config file contains no known executables.

There must be something wrong at the initial detection, when Boinc sends, or the server requests infos about the hardware.

Any idea how i can monitor that traffic, to give you some hints?
22) Message boards : News : GPU Issues Mega Thread (Message 65220)
Posted 20 Sep 2016 by Sebastian*
Post:
You can try the 341.96 driver. Which was displayed when i searched for the 9000 series and window 10. it is from 16th of August this year.
23) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65218)
Posted 20 Sep 2016 by Sebastian*
Post:
Hello Jake, i tried the new version on my R9 390X with the latest driver. It is requesting Tasks, but getting none. Removed an added the Project again with no success. No error Message so far. Could the error be, that the newer cards support OpenCL 2.0 instead of 1.2? And the software is only checking for 1.2 and is ignoring newer versions?

There is no driver version reported, when i check my computers in Boinc for this computer. All other from HD 4xxx cards to R9 280X cards report a driver version.

Computer ID: 704045

If you can check on the server side, why i don't get any workunits.

Edit: I added a more detailed request at the end of this message.

9/20/2016 11:51:58 PM | | Starting BOINC client version 7.6.22 for windows_x86_64
9/20/2016 11:51:58 PM | | log flags: file_xfer, sched_ops, task
9/20/2016 11:51:58 PM | | Libraries: libcurl/7.45.0 OpenSSL/1.0.2d zlib/1.2.8
9/20/2016 11:51:58 PM | | Data directory: C:\ProgramData\Boinc
9/20/2016 11:51:58 PM | | Running under account Sebastian
9/20/2016 11:51:58 PM | | OpenCL: AMD/ATI GPU 0: Hawaii (driver version 2117.13 (VM), device version OpenCL 2.0 AMD-APP (2117.13), 8192MB, 8192MB available, 3802 GFLOPS peak)
9/20/2016 11:51:58 PM | | OpenCL CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 5.2.0.10094, device version OpenCL 1.2 (Build 10094))
9/20/2016 11:51:58 PM | | OpenCL CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 2117.13 (sse2,avx), device version OpenCL 1.2 AMD-APP (2117.13))
9/20/2016 11:51:58 PM | | Host name: Hydra
9/20/2016 11:51:58 PM | | Processor: 4 GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz [Family 6 Model 60 Stepping 3]
9/20/2016 11:51:58 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 vmx tm2 pbe fsgsbase bmi1 smep bmi2
9/20/2016 11:51:58 PM | | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.10586.00)
9/20/2016 11:51:58 PM | | Memory: 15.93 GB physical, 18.31 GB virtual
9/20/2016 11:51:58 PM | | Disk: 118.69 GB total, 93.32 GB free
9/20/2016 11:51:58 PM | | Local time is UTC +2 hours
9/20/2016 11:51:58 PM | | Config: GUI RPCs allowed from:
9/20/2016 11:51:58 PM | | 192.168.000.50
9/20/2016 11:51:58 PM | | 192.168.000.62
9/20/2016 11:51:58 PM | | Config: simulate 4 CPUs
9/20/2016 11:51:58 PM | | Config: report completed tasks immediately
9/20/2016 11:51:58 PM | PrimeGrid | URL http://www.primegrid.com/; Computer ID 514902; resource share 100
9/20/2016 11:51:58 PM | | General prefs: from http://milkyway.cs.rpi.edu/milkyway/ (last modified 15-Jun-2016 13:12:51)
9/20/2016 11:51:58 PM | | Host location: none
9/20/2016 11:51:58 PM | | General prefs: using your defaults
9/20/2016 11:51:58 PM | | Reading preferences override file
9/20/2016 11:51:58 PM | | Preferences:
9/20/2016 11:51:58 PM | | max memory usage when active: 8156.68MB
9/20/2016 11:51:58 PM | | max memory usage when idle: 14682.03MB
9/20/2016 11:51:58 PM | | max disk usage: 92.39GB
9/20/2016 11:51:58 PM | | suspend work if non-BOINC CPU load exceeds 50%
9/20/2016 11:51:58 PM | | (to change preferences, visit a project web site or select Preferences in the Manager)
9/20/2016 11:52:08 PM | | Fetching configuration file from http://milkyway.cs.rpi.edu/milkyway/get_project_config.php
9/20/2016 11:52:25 PM | Milkyway@Home | Master file download succeeded
9/20/2016 11:52:30 PM | Milkyway@Home | Sending scheduler request: Project initialization.
9/20/2016 11:52:30 PM | Milkyway@Home | Requesting new tasks for CPU and AMD/ATI GPU
9/20/2016 11:52:33 PM | Milkyway@Home | Scheduler request completed: got 0 new tasks
9/20/2016 11:52:33 PM | Milkyway@Home | No tasks sent
9/20/2016 11:52:33 PM | Milkyway@Home | Tasks for CPU are available, but your preferences are set to not accept them
9/20/2016 11:53:38 PM | Milkyway@Home | Sending scheduler request: To fetch work.
9/20/2016 11:53:38 PM | Milkyway@Home | Requesting new tasks for AMD/ATI GPU
9/20/2016 11:53:43 PM | Milkyway@Home | Scheduler request completed: got 0 new tasks
9/20/2016 11:54:52 PM | Milkyway@Home | update requested by user
9/20/2016 11:54:53 PM | Milkyway@Home | Sending scheduler request: Requested by user.
9/20/2016 11:54:53 PM | Milkyway@Home | Requesting new tasks for AMD/ATI GPU
9/20/2016 11:54:55 PM | Milkyway@Home | Scheduler request completed: got 0 new tasks


9/21/2016 12:22:39 AM | Milkyway@Home | [work_fetch] set_request() for AMD/ATI GPU: ninst 1 nused_total 0.00 nidle_now 1.00 fetch share 1.00 req_inst 1.00 req_secs 1728000.00
9/21/2016 12:22:39 AM | Milkyway@Home | [work_fetch] request: CPU (0.00 sec, 0.00 inst) AMD/ATI GPU (1728000.00 sec, 1.00 inst)
9/21/2016 12:22:42 AM | Milkyway@Home | [work_fetch] backing off AMD/ATI GPU 302 sec
9/21/2016 12:22:42 AM | | [work_fetch] Request work fetch: RPC complete
9/21/2016 12:22:47 AM | | [work_fetch] ------- start work fetch state -------
9/21/2016 12:22:47 AM | | [work_fetch] target work buffer: 864000.00 + 864000.00 sec
9/21/2016 12:22:47 AM | | [work_fetch] --- project states ---
9/21/2016 12:22:47 AM | Milkyway@Home | [work_fetch] REC 0.000 prio 0.000 can't request work: scheduler RPC backoff (55.98 sec)
9/21/2016 12:22:47 AM | PrimeGrid | [work_fetch] REC 1230.459 prio 0.000 can't request work: "no new tasks" requested via Manager
9/21/2016 12:22:47 AM | | [work_fetch] --- state for CPU ---
9/21/2016 12:22:47 AM | | [work_fetch] shortfall 6912000.00 nidle 4.00 saturated 0.00 busy 0.00
9/21/2016 12:22:47 AM | Milkyway@Home | [work_fetch] share 0.000 blocked by project preferences
9/21/2016 12:22:47 AM | PrimeGrid | [work_fetch] share 0.000
9/21/2016 12:22:47 AM | | [work_fetch] --- state for AMD/ATI GPU ---
9/21/2016 12:22:47 AM | | [work_fetch] shortfall 1728000.00 nidle 1.00 saturated 0.00 busy 0.00
9/21/2016 12:22:47 AM | Milkyway@Home | [work_fetch] share 0.000 project is backed off (resource backoff: 296.59, inc 600.00)
9/21/2016 12:22:47 AM | PrimeGrid | [work_fetch] share 0.000
9/21/2016 12:22:47 AM | | [work_fetch] ------- end work fetch state -------
9/21/2016 12:22:47 AM | | [work_fetch] No project chosen for work fetch
24) Message boards : News : GPU Issues Mega Thread (Message 65216)
Posted 20 Sep 2016 by Sebastian*
Post:
Peter, from what i can see, your 9500GS (which is a 9500GT) should be able to run Einstein. It has compute capability 1.1 which should do it. For Milkyway you need 2.0 i think, which the 2xx Series had.
25) Message boards : News : GPU Issues Mega Thread (Message 65214)
Posted 20 Sep 2016 by Sebastian*
Post:
Hey BQL_FFM, what do you mean by "i buy it!"

And could you unhide your PC here in milkyway? I would be intrested in how fast the GTX 1060 runs through the Milkyway@home workunits.

Peter Hucker, you can leave your Intel integrated GPUs on Einstein. The Intel GPUS don't have double precision, so they can't run Milkyway. I am a little bit confused by you Nvidia GPU, i can only find a 9500M GS or a 9600GS. If it is a 9600GS it should be able to run at least Einstein@home.
26) Message boards : News : GPU Issues Mega Thread (Message 65180)
Posted 19 Sep 2016 by Sebastian*
Post:
Peter Hucker, yes, that is the message i mean. But your Nvidia card has no double precision capability, so it can't run Milkyway@home.

Colonywest, i guess it is the Nvidia driver, since it gave me the most trouble on linux. But i don't have much experience there. Maybe some permissions are missing to fully utilize the Nvidia driver. If you find a solution, please tell me. I never got the latest version of Boinc working properly on a Linux system. And the Nvidia driver always made things worse for me.
27) Message boards : News : GPU Issues Mega Thread (Message 65171)
Posted 19 Sep 2016 by Sebastian*
Post:
Jake Weiss is working on the GPU detection issues. Currently no newer cards than the R9 280X or 7970 are detected by Milkyway@home. Nvidia cards seem to work well, as older AMD/ATI cards do.
28) Message boards : News : GPU Issues Mega Thread (Message 65159)
Posted 17 Sep 2016 by Sebastian*
Post:
Milkyway has a problem with GPU detection for newer cards than the R9 280X (HD 7970) You should get the same message i did, because Milkyway thinks you have another GPU.

The good news is, that Jake is working on a solution to that problem.
29) Message boards : News : GPU Issues Mega Thread (Message 65156)
Posted 16 Sep 2016 by Sebastian*
Post:
Thank you for the information Jake.

I don't know how far you are with your bughunting on the gpu detection stuff. I just tried to connect a R9 390X to Milkyway and got:

9/16/2016 11:54:20 PM | Milkyway@Home | Message from server: ATI GPU R600 (R38xx) does not support OpenCL

However the GPU was detected correctly by Boinc, exept for the shown Gigaflops. They were around 3000 instead of nearly 6000. But i don't give too much about it, since the R9 280X GPUs are detected with the double Gigaflops they really have.

zioriga, you said now your GTX 1080 is working correctly, but i haven't seen any valid workunits on your account. You have some units running, but not uploaded yet. Would like to see, if it runs correctly.
30) Message boards : News : GPU Issues Mega Thread (Message 65141)
Posted 14 Sep 2016 by Sebastian*
Post:
Hi Joseph.

I have to agree to Keith Myers, but there is a problem with your HD 4xxx series cards and Windows 10. There are, and will never be, drivers from AMD for your HD 4xxx series cards for Windows 10. Check yourself on the AMD driver page.

I brought online a computer with 3 HD 4850s. I run Windows 7 with the latest driver for the HD 4xxx series cards. (Catalyst 13.9) It seems to run quiet well from what i can see.

Windows 8.1 is the lastest OS AMD supports drivers for. If you considering changing your OS.

Or you could search for just the OpenCL SDK from AMD. But i am not sure if it still exists (it is integrated into the driver now), or if it will give the Microsoft drivers OpenCL support. I would give it a try before you remove your OS.
31) Message boards : News : GPU Issues Mega Thread (Message 65127)
Posted 10 Sep 2016 by Sebastian*
Post:
Thanks for the info Jake :)

apohawk i can confirm the HD 6950 running well with the latest driver for it and with the current Milkyway workunits.
32) Message boards : News : GPU Issues Mega Thread (Message 65109)
Posted 6 Sep 2016 by Sebastian*
Post:
Hello mancausoft,

i think you are running OpenCL on your Nvidia GPU (GTX 750M Device 0) but all seem to error out. I have no experience with Darwin as an operating system, but i think it could be a driver issue, or some permissions are missing so Boinc is not allowed to use all the files it needs.

Your device 1 (second device) is you Intel GPU integrated in you CPU. But this one does not have a double precision compute capability.
Look for: "Device doesn't support double precision" in your last post.
33) Message boards : News : GPU Issues Mega Thread (Message 65101)
Posted 3 Sep 2016 by Sebastian*
Post:
Hello Tim,

Yes, you are right the Numbers are wrong. The numbers of my AMD cards are there where they should be.

I will test MW on my Titan blacks tomorrow.

Did you enable inside the driver the double precision option? If this is disabled, then the double precison number could be true. And even when you get the Titan Blacks fully utilized, then it is slower than a AMD card with one Terraflop.

Nvidia does not really care about OpenCL, they still pushing CUDA. So OpenCL is not optimized very well.
34) Message boards : News : GPU Issues Mega Thread (Message 65096)
Posted 2 Sep 2016 by Sebastian*
Post:
Hey everyone, i set up a HD 5970 (Dual 5870 on one card). I installed the newest not beta driver on it, and it runs smoothly. If you have such cards (HD 5850 or 5870) then you can use them without troubel for MW.
I will test a 69xx card soon, but i expect the same results :)

@Keith Myers

Yep, i agree to your last post. Most projects only have a few persons, even students working on it (programming, maintaining server) so that only for one GPU brand is optimized. You have to pick your cards depending on what projects you like most. A GTX Titan black has 1700 Gigaflop of double precision power, but it can barely compare to a 7970 with 1000 Gigaflop here in Milkyway. Primegrid is the other way around.

I can image that even OpenCL is hard work for the project programmers. Even if they only optimize on one manufacturer, they have to deal with different GPU architectures. And there is no help from the companies as well, since you can't earn profit on that :(
35) Message boards : News : GPU Issues Mega Thread (Message 65088)
Posted 1 Sep 2016 by Sebastian*
Post:
Thanks for all the feedback so far :)

@Keith Myers
The problem with Nvidia Cards is, that they have almost no Double Precision crunching power except for The GTX Titan or Titan Black (both Kepler).
I also had some driver issues with my Titan Blacks, when the cuda version was updated and a bug was in that version.
And i am glad that Nvidia at least supports OpenCL 1.2, so we can run them here :)

@_heinz
Your Titans can do quite well on Milkyway. If you want to run it a little, you have to set in the driver that double precision is used. And you have to use the app_config file to run 6 to 8 workunits in parallel per card to get them fully loaded.
36) Message boards : News : GPU Issues Mega Thread (Message 65083)
Posted 31 Aug 2016 by Sebastian*
Post:
Hello Jake, thanks for hunting the bugs.

For the GPU dection issu, is suggest you contact Einstein@home, they never had issues with the GPU detection in my opinion. And AMD GPUS work very well there with OpenCL.

I can test the older AMD GPUs there with the latest available driver for them (5870 or 6870 / 6970 GPUS)

I can also bring them online for Milkyway@home. For some reason, with driver newer then Catalyst 13.1, Milkyway@home aborts some tasks. (Have to check which one)

Thanks to Joseph, for reminding us about maintenance. But i have to object to the 5 years of GPU life-time. The GPU-Chips might hold that long, but the fans usually fail much erlier. And they are very hard to find

Can anyone check, how well the Nvidia detection works? I can check with my GTX 980. When anyone has a 700 series card, or even a 1000 series card, it would be nice to see some feedback :)
37) Message boards : News : No More Work From Modfit Project (Message 64887)
Posted 14 Jul 2016 by Sebastian*
Post:
Thanks Jake.

It looks better now, some of the "fixedangles" still error out.

At a closer look, the fixedangles_simBPLfixed2_3 (2_2 and 2_1) run through, the 1_1 and 1_2 error out.

I guess we have to run the 1_x versions through until they are gone?

Edit: Some of the 2_1 error out as well.
38) Message boards : News : No More Work From Modfit Project (Message 64880)
Posted 13 Jul 2016 by Sebastian*
Post:
Have to agree with Vortac, the tasks got fewer, but there are a lot of them again now.
39) Message boards : News : No More Work From Modfit Project (Message 64870)
Posted 12 Jul 2016 by Sebastian*
Post:
Thanks for the heads up Jake.

But i get new WUs for some hours now, they look like this:

de_modfit_fast_15_3s_fixedangles_simBPL_1_1468263296_787598

all WUs with "fixedangles" just error out.
40) Message boards : News : Running Modfit on MilkyWay@home (Message 64783)
Posted 30 Jun 2016 by Sebastian*
Post:
Thanks for the reply Jake :)

Good luck with the Linux binary.

I hope you find a useful documentary about the server config :)

Take your time, i can still remember the time when Milkyway@home was one of the very unstable and unreliable projects.

We have come a long way, keep up the good work :)


Previous 20 · Next 20

©2021 Astroinformatics Group