I was running a 4870 and had all the same issues Ageless had. Then, about 3-4 weeks ago, I found a killer deal on a 5870 and have since upgraded. I didn't even bother to put the 4870 in tandem with the 5870. Next on the agenda is a new motherboard, RAM (possibly CPU, waiting on Piledriver) and another 5870. The point is, I can't see ever going back to the 4xxx series.
Like Ageless said, maybe it's altogether simpler to deprecate support for 4xxx ?
As I wrote earlier, the computations for the BRP app have to be rearranged/resized to fit the hardware of the 4xxx series cards (you'll see some messages indicting this in the log output). Either this resizing process has a bug or it's causing a loss in precision. So there is still some hope that this can be made to work. Something the devs have to look into after the holiday season.
As I wrote earlier, the computations for the BRP app have to be rearranged/resized to fit the hardware of the 4xxx series cards (you'll see some messages indicting this in the log output). Either this resizing process has a bug or it's causing a loss in precision. So there is still some hope that this can be made to work. Something the devs have to look into after the holiday season.
HB
Thank you for your answer.
I must have missed the earliar post.
I have ordered a Sapphire Radeon HD6850 with 2GB of GDDR5, it'll arrive tomorrow. We'll see what that one can do around here, although I'll probably be breaking it in exclusively by playing more Skyrim 4GB.
I am using 7.0.7 because it's needed for the VBoxwrapper test project.
My other two OpenCL tasks went a lot quicker, 4,800 and 5,600 seconds.
But then this one didn't validate against the CUDA32. Unknown at this time if this is because of me or him.
I am using 7.0.7 because it's needed for the VBoxwrapper test project.
My other two OpenCL tasks went a lot quicker, 4,800 and 5,600 seconds.
But then this one didn't validate against the CUDA32. Unknown at this time if this is because of me or him.
Oh, ok.
What will the purpose be of Vboxwrapper?
Will VirtualBox be replaced at T4T?
T4T already runs a Virtual Box wrapper application, but even though they are a Beta project they do not want to go test all the adjustments and bug fixes that the BOINC developers added to the Vboxwrapper app (which begs the question why they run as a beta project then, but heck ;-)), to Virtual Box (in coop with Oracle devs) and to the BOINC client. Hence the CERNVM/Vboxwrapper Test Project set up and administrated by the BOINC developers, where we test all that.
There's no validator running over there, so there's no credits even though we do real work through the hypervisor. The project will be deleted when we're done testing.
Eventually, when we're done testing the crap out of all that, hopefully T4T will take over the vboxwrapper app and run it at their project.
I was running a 4870 and had
)
I was running a 4870 and had all the same issues Ageless had. Then, about 3-4 weeks ago, I found a killer deal on a 5870 and have since upgraded. I didn't even bother to put the 4870 in tandem with the 5870. Next on the agenda is a new motherboard, RAM (possibly CPU, waiting on Piledriver) and another 5870. The point is, I can't see ever going back to the 4xxx series.
Like Ageless said, maybe it's altogether simpler to deprecate support for 4xxx ?
Hmm... 4850 doesn't work with
)
Hmm... 4850 doesn't work with albert.
But I successfully run 4850 with PEOM@Home OpenCl app and it uses boinc 7.x.x as well.
I wonder what the difference might be?
As I wrote earlier, the
)
As I wrote earlier, the computations for the BRP app have to be rearranged/resized to fit the hardware of the 4xxx series cards (you'll see some messages indicting this in the log output). Either this resizing process has a bug or it's causing a loss in precision. So there is still some hope that this can be made to work. Something the devs have to look into after the holiday season.
HB
RE: As I wrote earlier, the
)
Thank you for your answer.
I must have missed the earliar post.
I have ordered a Sapphire
)
I have ordered a Sapphire Radeon HD6850 with 2GB of GDDR5, it'll arrive tomorrow. We'll see what that one can do around here, although I'll probably be breaking it in exclusively by playing more Skyrim 4GB.
My Radeon HD6850 just
)
My Radeon HD6850 just finished its first task, it got validated against a CUDA32. How refreshing.
RE: My Radeon HD6850 just
)
6850 is a nice card.
I'll just have to wait until the program supports 48xx cards.
Is Boinc version 7.07 scheduling any better then 7.03?
I am using 7.0.7 because it's
)
I am using 7.0.7 because it's needed for the VBoxwrapper test project.
My other two OpenCL tasks went a lot quicker, 4,800 and 5,600 seconds.
But then this one didn't validate against the CUDA32. Unknown at this time if this is because of me or him.
RE: I am using 7.0.7
)
Oh, ok.
What will the purpose be of Vboxwrapper?
Will VirtualBox be replaced at T4T?
T4T already runs a Virtual
)
T4T already runs a Virtual Box wrapper application, but even though they are a Beta project they do not want to go test all the adjustments and bug fixes that the BOINC developers added to the Vboxwrapper app (which begs the question why they run as a beta project then, but heck ;-)), to Virtual Box (in coop with Oracle devs) and to the BOINC client. Hence the CERNVM/Vboxwrapper Test Project set up and administrated by the BOINC developers, where we test all that.
There's no validator running over there, so there's no credits even though we do real work through the hypervisor. The project will be deleted when we're done testing.
Eventually, when we're done testing the crap out of all that, hopefully T4T will take over the vboxwrapper app and run it at their project.