View Issue Details

IDProjectCategoryView StatusLast Update
0008288Kali LinuxGeneral Bugpublic2023-12-07 10:34
Reporterkimocoder Assigned To 
Status closedResolutionopen 
Product Versionkali-dev 
Summary0008288: OpenCL issues

We now include pocl2 (libpocl2) in standard images, this is a bad solution.
Intel for Intel, Nvidia for Nvidia and AMD for AMD. If we run the portable O
POCL2 on top if these computing libraries, which we do today, user experience related to computing tools will have an
issue with decreased hash rate. We dont want this.

We cannot do Intel + POCL2 and so, they will be registrated and system 1 and 2 in computing tools
like hashcat. Register as 2, devided. This will decrease computing hashed significant.

Intel ICD for Intel, Nvidia ICD for Intel, AMD for AMD and POCL2 for NetHunter or ARM64 systems is what we want.


has duplicate 0008297 closedarnaudr OpenCL issues 




2023-05-06 01:44

reporter   ~0017883

Reproduced running latest weekly builds.



2023-05-08 16:25

manager   ~0017896

I'm not entirely sure what we should do here. According to chick3nman..

From: chick3nman

that's... hmm
i think its correct sorta but not fully
while it does highlight a real issue with POCL and Intel's OpenCL driver conflicting, im not sure i understand the alternative
because, as far as i know, there isn't one
Intel's runtime is proprietary (AMD doesnt have their own, you use intel's) and POCL is open source
when POCL works, it works fairly well and i don't expect significant performance loss
but if you were to not ship POCL, i don't know if you could ship Intel's due to the license
I'm pretty sure shipping POCL is the only way to ship a decently working runtime


2023-05-08 16:27

manager   ~0017897

Maybe we could demote whatever depends on pocl2, to having it be a Recommends, so that users can remove it, in favor of installing their own Intel implementation?



2023-05-08 16:29

reporter   ~0017898

Me too, I've been thinking about this one several times.
Possibly ship none in x86_64 builds, but for NetHunter this will be a positive action again.



2023-05-08 16:30

reporter   ~0017899

Possibly, I'll let other decide this �



2023-05-09 03:25

manager   ~0017901

This might actually be a moot point; we actually get hashcat from debian, and it's quite likely that is what is pulling it in for you. opencl packages should be providing opencl-icd, which would allow them to replace the pocl2 package without things breaking. Regardless, perhaps if you raise the issue there?

It also seems a bit odd that hashcat would default to the cpu if the gpu is installed; are you sure that the intel packages are installing correctly? I don't have the hardware here so I can't tell.



2023-12-07 10:34

administrator   ~0018680

This report has been filed against an old version of Kali. We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux (

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup?
For more information, please read:

Issue History

Date Modified Username Field Change
2023-05-06 01:43 kimocoder New Issue
2023-05-06 01:44 kimocoder Note Added: 0017883
2023-05-06 09:02 xpister Issue cloned: 0008290
2023-05-08 16:25 steev Note Added: 0017896
2023-05-08 16:27 steev Note Added: 0017897
2023-05-08 16:29 kimocoder Note Added: 0017898
2023-05-08 16:30 kimocoder Note Added: 0017899
2023-05-09 03:22 steev Summary OpenCL issues [important] => OpenCL issues
2023-05-09 03:25 steev Note Added: 0017901
2023-05-09 16:04 sidhupb13 Issue cloned: 0008297
2023-05-10 01:14 arnaudr Relationship added has duplicate 0008297
2023-12-07 10:34 g0tmi1k Note Added: 0018680
2023-12-07 10:34 g0tmi1k Status new => closed