There isn’t a kernel bug per se. For the Kernel to break this functionality by accident and not catch said failure seems like a deliberate change.
That said, there is an upstream report and open issue with the Intel NEO drivers not being detected in the 6.8 kernel.
It’s unknown if this is an Intel problem or indeed a kernel problem.
We are monitoring the progress to see what happens.
There are options but most of those options are unacceptable for users.
If we’re understanding what’s happening correctly.
- Intel is / has migrated from OpenCL tone mapping to VAAPI tonemapping
- In their migration, they did not include any of the CPUs from JasperLake → KabyLake.
- If this is correct unstanding and their intent,
– Only TigerLake and above QSV machines will be supported by them.
– JasperLake, KabyLake, ApolloLake, and especially GeminiLake are all dropped.
As you can see, there is a considerable lack of information as to both current status, short term and long term plans.
We’re trying to learn as quickly as possible.
