Details
Description
ADDITIONAL SYSTEM INFORMATION :
OS: Linux localhost.localdomain 5.15.7-200.fc35.x86_64 #1 SMP Wed Dec 8 19:00:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Java:
openjdk 17 2021-09-14
OpenJDK Runtime Environment (build 17+35-2724)
OpenJDK 64-Bit Server VM (build 17+35-2724, mixed mode, sharing)
A DESCRIPTION OF THE PROBLEM :
The ES2Pipleline is ignoring some AMD cards from the pre-qualification check at they de not report themselves with a string which is in the pre-qualifaction list.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Follow the instructions on the https://openjfx.io/openjfx-docs/#install-javafx page for running the example application but with added options for prism debug output:-
java -Dprism.verbose=true --module-path $PATH_TO_FX --add-modules javafx.controls HelloFX
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
A compatible graphics card would be detected and the ES2 hardware piple would be used.
ACTUAL -
The compatibility check fails and the application falls back to using the Prism SW pipeline.
CUSTOMER SUBMITTED WORKAROUND :
Adding the -Dprism.forceGPU=true option to the command line.
FREQUENCY : always
OS: Linux localhost.localdomain 5.15.7-200.fc35.x86_64 #1 SMP Wed Dec 8 19:00:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Java:
openjdk 17 2021-09-14
OpenJDK Runtime Environment (build 17+35-2724)
OpenJDK 64-Bit Server VM (build 17+35-2724, mixed mode, sharing)
A DESCRIPTION OF THE PROBLEM :
The ES2Pipleline is ignoring some AMD cards from the pre-qualification check at they de not report themselves with a string which is in the pre-qualifaction list.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Follow the instructions on the https://openjfx.io/openjfx-docs/#install-javafx page for running the example application but with added options for prism debug output:-
java -Dprism.verbose=true --module-path $PATH_TO_FX --add-modules javafx.controls HelloFX
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
A compatible graphics card would be detected and the ES2 hardware piple would be used.
ACTUAL -
The compatibility check fails and the application falls back to using the Prism SW pipeline.
CUSTOMER SUBMITTED WORKAROUND :
Adding the -Dprism.forceGPU=true option to the command line.
FREQUENCY : always