[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141010080507.GA29165@openwall.com>
Date: Fri, 10 Oct 2014 12:05:07 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: "Failed copy data to gpu" when using fork with descrypt-opencl
Hi Royce,
Thank you for reporting this. On further occasions, please direct such
postings to john-users rather than john-dev. This is essentially user
experience, and it's useful for other users to know that they may/should
use --fork for this purpose, and that it failed in this version for this
GPU type.
On Thu, Oct 09, 2014 at 11:58:26PM -0800, Royce Williams wrote:
> When running this version of bleeding-jumbo:
>
> commit 3d8c4ea17f918130e62108be91309883c7023541
> Merge: 379881a 53cbf8b
> Author: Dhiru Kholia <dhiru@...nwall.com>
> Date: Thu Oct 9 20:28:03 2014 +0200
>
>
> ... I'm getting the following error when I try to use fork to get more
> CPU cores participating in feeding my GPU:
Did this work for you before, on this same GPU, with older
bleeding-jumbo? Can you identify the newer version that worked?
And yes, you're right in using --fork to speedup descrypt-opencl.
In fact, once this issue is resolved, I think you'll want to use
something like --fork=4.
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
