Skip to content

Unsupported OpenGL Version on Windows EC2 2019 Base Image - Used for Medical Imaging

0

Hi all, I am using g4ad.xlarge instance which comes under the GPU Accelerated Computing Instance. This instance used for medical imaging purpose. Previously it was g4dn.xlarge which is 16 GB of GPU. Now is downgraded to instance which i mentioned at the first. I have used the new instance "g4ad.xlarge" and installed the medical imaging application in it. But when I open any medical image from the application, there was an error saying "Unsupported OpenGL Version: Microsoft Corporation, GDI Generic, 1.1.0". For your kind information, even changing the instance type to "g4dn.xlarge". The same error comes. But if I use the old instance which is presently used in staging environment it works perfectly. Can anyone tell me how to get rid of that OpenGL error? I have even tried to update the graphics driver but there seems nothing to update. Or do we have any special library/binary/exe to be installed for this new instance? It would be great if anyone could help me on this scenario. Thanks!

asked 2 years ago408 views

2 Answers
2

Do ensure you install AMD driver in your g4ad instance. Refer to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/install-amd-driver.html#download-amd-driver for installation instructions.

You can install GL Extensions Viewer to verify OpenGL version.. Below screenshot is g4ad with AMD driver installed. OpenGL version is 4.6 Enter image description here

AWS
EXPERT

answered 2 years ago

0

The issue you're experiencing with the "Unsupported OpenGL Version" error on your EC2 instances (both g4ad.xlarge and g4dn.xlarge) for your medical imaging application is likely related to the GPU drivers and OpenGL support. Here are some steps you can take to address this problem:

  1. Ensure you have the correct NVIDIA drivers installed:
  • For g4dn instances (which use NVIDIA GPUs), you need to install the appropriate NVIDIA GRID drivers. These instances require GRID 13.1 or later (or GRID 12.4 or later).
  • For g4ad instances (which use AMD GPUs), make sure you have the latest AMD GPU drivers installed.
  1. Check if you're using the correct AMI:
  • If you're using a custom Windows AMI, ensure it's a standardized image created with Windows Sysprep. This is necessary for the GRID driver to work properly.
  1. Verify Windows Server version compatibility:
  • Note that GRID 17.0 and later do not support Windows Server 2019. If you're using a newer GRID driver, you may need to use a different Windows Server version.
  1. Install OpenGL libraries:
  • Ensure that you have the necessary OpenGL libraries installed on your instance. You may need to install additional software or libraries to support the required OpenGL version for your medical imaging application.
  1. Consider using a GPU instance with more powerful graphics capabilities:
  • If your application requires advanced OpenGL features, you might need to use a more powerful GPU instance type. The G5 instances, for example, offer more recent NVIDIA GPUs with better graphics performance.
  1. Check application compatibility:
  • Verify that your medical imaging application is compatible with the GPU and drivers available on the EC2 instance types you're using.

If these steps don't resolve the issue, you may need to contact AWS support for further assistance, especially if you suspect there's a problem with the instance configuration or available GPU drivers.

Remember that GPU instances work best for applications with massive parallelism, such as graphics processing and spatial computing. Ensure that your chosen instance type is appropriate for your medical imaging workload.

Sources
NVIDIA drivers for your Amazon EC2 instance - Amazon Elastic Compute Cloud
Amazon EC2 FAQs – AWS

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.