02-24-2022, 10:00 PM
@pdo
@Snoopy
Thank you for reply.
Yes, requirement for Hashcat v6.2.5
Intel CPUs require this runtime:
"OpenCL Runtime for Intel Core and Intel Xeon Processors" (16.1.1 or later)
However, the same for v5.1.0, v4.2.0, v3.6.0
Intel CPUs require this runtime and/or driver:
"OpenCL Runtime for Intel Core and Intel Xeon Processors" (16.1.1 or later)
In fact, I didn't install a separate OpenCL Runtime.
Instead, I installed the latest driver for my Intel HD Graphics 2500
https://www.intel.com/content/www/us/en/...15-33.html
This driver have OpenCL support.
It seems, there is no OpenCL runtime update for my CPU/GPU.
My notebook was manufactured in 2014.
My CPU was first introduced in 2013.
https://ark.intel.com/content/www/us/en/...0-ghz.html
Probably only Jens Steube (atom) knows the real reason for this long initializing.
Initializing backend runtime for device #1. Please be patient...
@Snoopy
Thank you for reply.
Yes, requirement for Hashcat v6.2.5
Intel CPUs require this runtime:
"OpenCL Runtime for Intel Core and Intel Xeon Processors" (16.1.1 or later)
However, the same for v5.1.0, v4.2.0, v3.6.0
Intel CPUs require this runtime and/or driver:
"OpenCL Runtime for Intel Core and Intel Xeon Processors" (16.1.1 or later)
In fact, I didn't install a separate OpenCL Runtime.
Instead, I installed the latest driver for my Intel HD Graphics 2500
https://www.intel.com/content/www/us/en/...15-33.html
This driver have OpenCL support.
It seems, there is no OpenCL runtime update for my CPU/GPU.
My notebook was manufactured in 2014.
My CPU was first introduced in 2013.
https://ark.intel.com/content/www/us/en/...0-ghz.html
Probably only Jens Steube (atom) knows the real reason for this long initializing.
Initializing backend runtime for device #1. Please be patient...