[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220804155749.GA29583@openwall.com>
Date: Thu, 4 Aug 2022 17:57:49 +0200
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: Using OpenCL with Radeon RX 580
On Thu, Aug 04, 2022 at 10:48:07AM +0900, dskshnd@...il.com wrote:
> I did
> > if (crack_count_ret > 1)
> > return 1;
> and
> > FMT_CASE | FMT_8_BIT | FMT_DYNA_SALT | FMT_HUGE_INPUT |
> FMT_NOT_EXACT,
> .
> But nothing has changed.
That's puzzling - if you applied the changes correctly, at least the
error message should have changed slightly. I don't see how it can be
"cmp_one(1)" in there (notice the "1") with the changed code.
I understand the error message changing is a "nothing" for your actual
usage, though.
> So I will use an old NVIDIA card.
OK.
You can also try building an older revision of JtR:
git checkout bb82d0153bafc3e52a53f64c69809a563bbc47ba
or if that doesn't help, even older:
git checkout f59129c8b77032dabaf407d73f95e4394a62fe9e
These specific revisions correspond to moments just before relevant
changes to zip-opencl were made in our codebase, so using these
revisions is likely to hide the issue you're running into (but may
expose other issues, including bugs we've since fixed, unfortunately).
These are an alternative to the manual edits I had suggested (that is,
don't make any manual edits when trying these older revisions).
You'll need to:
./configure # maybe with options
make -s clean
make -sj24
after each "git checkout". You don't need the complicated approach with
two builds and OMP_FALLBACK_BINARY that you've been using (although it
does not hurt, and you can use it if you like).
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.
