On my Windows Vista desktop, same results from double-clicking. However, I see no reason to disable BOINC GPU use there.
On my Windows 7 desktop, I haven't found a way yet to make the BOINC data directory visible in directory listings yet, so I could not run similar tests. Also no reason to disable BOINC GPU use there.
Either with or without BOINC in the background, but without a GPU workunit running, I get this:
By "without BOINC" I meant the client/workunits, not just BOINC Manager.
Quote:
For einsteinbinary_BRP3_1.00_graphics_windows_intelx86.exe:
A screensaver window open up and runs normally, except that all the BOINC information is either blanks or zeroes, and all the search information is zeroes.
This is the expected behavior since there's no connection to (interaction with) an active BOINC task.
Quote:
I also saw einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe and tried similar tests with it. This gives a small window, all black inside, and an error message:
This application has failed to start because cuda32_32_16.dll was not found.
Reinstalling the application may fix this.
This does't make any sense because:
1) The two binaries are the same, they just have different names. I just verified that on our server.
2) The graphics app (screensaver) doesn't need/use CUDA at all, hence it's not linked to any CUDA DLL. Are you sure you clicked on the right executable?
Quote:
Could the screensaver program have a problem telling which set of input data it should use if a BRP4 workunit has been started, but BOINC currently isn't allowed to use the GPU?
Depends, are we talking about BRP4 GPU workunit? Do you see the same screensaver problem when your affected machine runs a BRP CPU workunit?
On a related note: I strongly recommend to run any screensaver on a GPU that is used for computational purposes.
Either with or without BOINC in the background, but without a GPU workunit running, I get this:
By "without BOINC" I meant the client/workunits, not just BOINC Manager.
That's what I did.
Quote:
Quote:
I also saw einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe and tried similar tests with it. This gives a small window, all black inside, and an error message:
This application has failed to start because cuda32_32_16.dll was not found.
Reinstalling the application may fix this.
This does't make any sense because:
1) The two binaries are the same, they just have different names. I just verified that on our server.
2) The graphics app (screensaver) doesn't need/use CUDA at all, hence it's not linked to any CUDA DLL. Are you sure you clicked on the right executable?
I'm sure I clicked on the one with the 3 in the name changed to 4. If it's a bad copy of that executable, how do I tell BOINC to get another copy?
Quote:
Quote:
Could the screensaver program have a problem telling which set of input data it should use if a BRP4 workunit has been started, but BOINC currently isn't allowed to use the GPU?
Depends, are we talking about BRP4 GPU workunit? Do you see the same screensaver problem when your affected machine runs a BRP CPU workunit?
On a related note: I strongly recommend to run any screensaver on a GPU that is used for computational purposes.
HTH,
Oliver
Yes, that's a BRP4 GPU workunit. I haven't had any of the BRP3 or BRP4 CPU workunits recently.
The BOINC screensaver does not agree with you about only running the BRP4 screensaver while the GPU is used for computational purposes. Feel free to report that as a problem to the BOINC developers.
Whenever that GPU is used 100% of the time for computational purposes, I basically have the choice of either making all CPU workunits too slow to meet their deadlines (using Tthrottle64) or letting the laptop overheat enough that it will automatically go into sleep mode several times a day, which shuts off all computation until I notice and tell it to come out of sleep mode. In other words, that laptop does not have a reasonable sharing between CPU workunits and GPU workunits. I therefore disable use of the GPU much of the day so the CPU workunits can get enough CPU time, and enable use of the GPU the rest of the time so that GPU workunits can also be done.
I'm not especially interested in using that laptop for GPU workunits only, or for workunits that I know in advance will not finish by their deadlines. All the CPU workunits there now come from other BOINC projects.
Either with or without BOINC in the background, but without a GPU workunit running, I get this:
By "without BOINC" I meant the client/workunits, not just BOINC Manager.
That's what I did.
Quote:
Quote:
I also saw einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe and tried similar tests with it. This gives a small window, all black inside, and an error message:
This application has failed to start because cuda32_32_16.dll was not found.
Reinstalling the application may fix this.
This does't make any sense because:
1) The two binaries are the same, they just have different names. I just verified that on our server.
2) The graphics app (screensaver) doesn't need/use CUDA at all, hence it's not linked to any CUDA DLL. Are you sure you clicked on the right executable?
I'm sure I clicked on the one with the 3 in the name changed to 4. If it's a bad copy of that executable, how do I tell BOINC to get another copy?
Quote:
Quote:
Could the screensaver program have a problem telling which set of input data it should use if a BRP4 workunit has been started, but BOINC currently isn't allowed to use the GPU?
Depends, are we talking about BRP4 GPU workunit? Do you see the same screensaver problem when your affected machine runs a BRP CPU workunit?
On a related note: I strongly recommend to run any screensaver on a GPU that is used for computational purposes.
HTH,
Oliver
Yes, that's a BRP4 GPU workunit. I haven't had any of the BRP3 or BRP4 CPU workunits recently.
The BOINC screensaver does not agree with you about only running the BRP4 screensaver while the GPU is used for computational purposes. Feel free to report that as a problem to the BOINC developers.
Whenever that GPU is used 100% of the time for computational purposes, I basically have the choice of either making all CPU workunits too slow to meet their deadlines (using Tthrottle64) or letting the laptop overheat enough that it will automatically go into sleep mode several times a day, which shuts off all computation until I notice and tell it to come out of sleep mode. In other words, that laptop does not have a reasonable sharing between CPU workunits and GPU workunits. I therefore disable use of the GPU much of the day so the CPU workunits can get enough CPU time, and enable use of the GPU the rest of the time so that GPU workunits can also be done.
I'm not especially interested in using that laptop for GPU workunits only, or for workunits that I know in advance will not finish by their deadlines. All the CPU workunits there now come from other BOINC projects.
That sounds like you're been trying to run the BRP4 Cuda app: einsteinbinary_BRP4_1.00_windows_intelx86__BRP3cuda32.exe and not the graphics app: einsteinbinary_BRP3_1.00_graphics_windows_intelx86.exe
(I had a look in each of the download mirror's, there isn't a einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe only einsteinbinary_BRP3_1.00_graphics_windows_intelx86.exe)
You're right, I was. The touchpad on that laptop does not handle all mouse functions well, such as those needed to widen the window showing the executable names, so it was hard to look at the last part of their names.
The problem now looks like it might be fixed, but by some means other than changing the executables for the workunit and the screensaver. My guess is that some other part of the workunits was changed instead.
The BOINC screensaver does not agree with you about only running the BRP4 screensaver while the GPU is used for computational purposes. Feel free to report that as a problem to the BOINC developers.
That's why I said that I strongly recommend that. This might not be the view of the BOINC devs. For the time being it's up to the user to decide whether it makes sense to run a hardware accelerated 3D/OpenGL app on the same device that's used for GPU computing ;-)
Quote:
My guess is that some other part of the workunits was changed instead.
On my Windows Vista desktop,
)
On my Windows Vista desktop, same results from double-clicking. However, I see no reason to disable BOINC GPU use there.
On my Windows 7 desktop, I haven't found a way yet to make the BOINC data directory visible in directory listings yet, so I could not run similar tests. Also no reason to disable BOINC GPU use there.
RE: Either with or without
)
By "without BOINC" I meant the client/workunits, not just BOINC Manager.
This is the expected behavior since there's no connection to (interaction with) an active BOINC task.
This does't make any sense because:
1) The two binaries are the same, they just have different names. I just verified that on our server.
2) The graphics app (screensaver) doesn't need/use CUDA at all, hence it's not linked to any CUDA DLL. Are you sure you clicked on the right executable?
Depends, are we talking about BRP4 GPU workunit? Do you see the same screensaver problem when your affected machine runs a BRP CPU workunit?
On a related note: I strongly recommend to run any screensaver on a GPU that is used for computational purposes.
HTH,
Oliver
Einstein@Home Project
RE: RE: Either with or
)
That's what I did.
I'm sure I clicked on the one with the 3 in the name changed to 4. If it's a bad copy of that executable, how do I tell BOINC to get another copy?
Yes, that's a BRP4 GPU workunit. I haven't had any of the BRP3 or BRP4 CPU workunits recently.
The BOINC screensaver does not agree with you about only running the BRP4 screensaver while the GPU is used for computational purposes. Feel free to report that as a problem to the BOINC developers.
Whenever that GPU is used 100% of the time for computational purposes, I basically have the choice of either making all CPU workunits too slow to meet their deadlines (using Tthrottle64) or letting the laptop overheat enough that it will automatically go into sleep mode several times a day, which shuts off all computation until I notice and tell it to come out of sleep mode. In other words, that laptop does not have a reasonable sharing between CPU workunits and GPU workunits. I therefore disable use of the GPU much of the day so the CPU workunits can get enough CPU time, and enable use of the GPU the rest of the time so that GPU workunits can also be done.
I'm not especially interested in using that laptop for GPU workunits only, or for workunits that I know in advance will not finish by their deadlines. All the CPU workunits there now come from other BOINC projects.
RE: RE: RE: Either
)
That sounds like you're been trying to run the BRP4 Cuda app: einsteinbinary_BRP4_1.00_windows_intelx86__BRP3cuda32.exe and not the graphics app: einsteinbinary_BRP3_1.00_graphics_windows_intelx86.exe
(I had a look in each of the download mirror's, there isn't a einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe only einsteinbinary_BRP3_1.00_graphics_windows_intelx86.exe)
Claggy
You're right, I was. The
)
You're right, I was. The touchpad on that laptop does not handle all mouse functions well, such as those needed to widen the window showing the executable names, so it was hard to look at the last part of their names.
The problem now looks like it might be fixed, but by some means other than changing the executables for the workunit and the screensaver. My guess is that some other part of the workunits was changed instead.
RE: The BOINC screensaver
)
That's why I said that I strongly recommend that. This might not be the view of the BOINC devs. For the time being it's up to the user to decide whether it makes sense to run a hardware accelerated 3D/OpenGL app on the same device that's used for GPU computing ;-)
Not to my knowledge...
Oliver
Einstein@Home Project