ERROR: clGetDeviceInfo() -30

[Volt]

Hello.
Backtrack Linux 5, ATI Radeon HD 5450, the newest versions of ochHashcat-lite and driver.

root@bt:/pentest/passwords/oclHashcat-lite-0.10# oclHashcat-lite32.bin -b
oclHashcat-lite v0.10 by atom starting...

Password lengths range: 1 - 55
Watchdog: Temperature abort trigger disabled
Watchdog: Temperature retain trigger disabled
ERROR: clGetDeviceInfo() -30

oclHashcat-plus works fine, does anyone know, where is a problem?

[makakiewicz]

(08-10-2012 08:13 AM)Volt Wrote:  Hello.
Backtrack Linux 5, ATI Radeon HD 5450, the newest versions of ochHashcat-lite and driver.

root@bt:/pentest/passwords/oclHashcat-lite-0.10# oclHashcat-lite32.bin -b
oclHashcat-lite v0.10 by atom starting...

Password lengths range: 1 - 55
Watchdog: Temperature abort trigger disabled
Watchdog: Temperature retain trigger disabled
ERROR: clGetDeviceInfo() -30

oclHashcat-plus works fine, does anyone know, where is a problem?

I have the same problem on my Gentoo Linux 32bit with ati-drivers-12.8 installed.
I think the problem is 32bit specific since -30 is CL_INVALID_VALUE error code and the documentation of

Code:

cl_int clGetDeviceInfo(cl_device_id device,
                       cl_device_info param_name,
                       size_t param_value_size,
                       void *param_value,
                       size_t *param_value_size_ret)

says that CL_INVALID_VALUE is returned

Quote:if param_name is not one of the supported values or if size in bytes specified by param_value_size is less than size of return type as shown in the table above and param_value is not a NULL value.

So it's probably param_value_size or param_value_size_ret structure size mismatch originating from differences in size_t size accross 32bit/64bit platforms.

[atom]

Thanks for the hint, but oclHashcat uses size_t.

Here is a quote from the headers:

void hc_clGetDeviceInfo (cl_device_id device, cl_device_info param_name, size_t param_value_size, void *param_value, size_t *param_value_size_ret);

So I would say he is using an old driver version which did not use size_t?