[sagher]

Hello all experts...!

I have a question about basic Hardware info of VPS server, we got simply CPU info my putting this " 

Code: (Select All)

cat /proc/cpuinfo

but GPU info and OpenGL version not mention in this info. can anyone have working command to check GPU server info. size memory of GPU card if any?

[fChk]

Hello all experts...!

I have a question about basic Hardware info of VPS server, we got simply CPU info my putting this " 

Code: (Select All)

cat /proc/cpuinfo

but GPU info and OpenGL version not mention in this info. can anyone have working command to check GPU server info. size memory of GPU card if any?

For the OpenGL version:

Code: (Select All)

$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 20.2.4

OR, with more info:

Code: (Select All)

$ glxinfo | grep "OpenGL"
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1)
OpenGL core profile version string: 4.2 (Core Profile) Mesa 20.2.4
OpenGL core profile shading language version string: 4.20
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 20.2.4
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 20.2.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

For the GPU unit:

Code: (Select All)

$ glxinfo | grep 'OpenGL renderer string'
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1)

OR, with more verbosity:

Code: (Select All)

$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
   Vendor: Intel Open Source Technology Center (0x8086)
   Device: Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1) (0x152)
   Version: 20.2.4
   Accelerated: yes
   Video memory: 1536MB
   Unified memory: yes
   Preferred profile: core (0x1)
   Max core profile version: 4.2
   Max compat profile version: 3.0
   Max GLES1 profile version: 1.1
   Max GLES[23] profile version: 3.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1)
OpenGL core profile version string: 4.2 (Core Profile) Mesa 20.2.4
OpenGL core profile shading language version string: 4.20
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 20.2.4
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 20.2.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

If you don't have glxinfo in your system, then install the glx-utils package if you're on CentOS/Fedora systems, or the equivalent on the other distros.

Otherwise, use the standard lshw command:

Code: (Select All)

sudo lshw -numeric -C display

[sagher]

For the OpenGL version:

Code: (Select All)

$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 20.2.4

OR, with more info:

Code: (Select All)

$ glxinfo | grep "OpenGL"
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1)
OpenGL core profile version string: 4.2 (Core Profile) Mesa 20.2.4
OpenGL core profile shading language version string: 4.20
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 20.2.4
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 20.2.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

For the GPU unit:

Code: (Select All)

$ glxinfo | grep 'OpenGL renderer string'
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1)

OR, with more verbosity:

Code: (Select All)

$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
   Vendor: Intel Open Source Technology Center (0x8086)
   Device: Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1) (0x152)
   Version: 20.2.4
   Accelerated: yes
   Video memory: 1536MB
   Unified memory: yes
   Preferred profile: core (0x1)
   Max core profile version: 4.2
   Max compat profile version: 3.0
   Max GLES1 profile version: 1.1
   Max GLES[23] profile version: 3.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1)
OpenGL core profile version string: 4.2 (Core Profile) Mesa 20.2.4
OpenGL core profile shading language version string: 4.20
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 20.2.4
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 20.2.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

If you don't have glxinfo in your system, then install the glx-utils package if you're on CentOS/Fedora systems, or the equivalent on the other distros.

Otherwise, use the standard lshw command:

Code: (Select All)

sudo lshw -numeric -C display

I have Debian 9 x64, these commands giving E: unable to locate error. please guide me step by step

[fChk]

I have Debian 9 x64, these commands giving E: unable to locate error. please guide me step by step

Why I'm not surprised ? :-)

Okay!.. A couple of checks here:

1- Does glxinfo command exist on your system ?
> How do you know that? Well just run this:

Code: (Select All)

which glxinfo

If it's installed you'll have the path of its binary.

> + If answer is yes > go to 2.
 + If answer is NO! > then install the mesa-utils package (for debian-based systems):

Code: (Select All)

sudo apt-get install mesa-utils

2- I hope you're not trying this on VPS-9!.. because it doesn't have a display unless you've explicitly created one with xvfb for example. In which point I don't see the point of looking for the GPU!.

> + If answer is yes : you have to give more details on what are you trying to do.
+ If answer is no and you're doing this on a GPU-backed system with its display and all that, then go to 3.

3- If you get to point 3 and still can't figure out your problem then you're on your own!..

Good luck!

[sagher]

Why I'm not surprised ? :-)

Okay!.. A couple of checks here:

1- Does glxinfo command exist on your system ?
> How do you know that? Well just run this:

Code: (Select All)

which glxinfo

If it's installed you'll have the path of its binary.

> + If answer is yes > go to 2.
 + If answer is NO! > then install the mesa-utils package (for debian-based systems):

Code: (Select All)

sudo apt-get install mesa-utils

2- I hope you're not trying this on VPS-9!.. because it doesn't have a display unless you've explicitly created one with xvfb for example. In which point I don't see the point of looking for the GPU!.

> + If answer is yes : you have to give more details on what are you trying to do.
 + If answer is no and you're doing this on a GPU-backed system with its display and all that, then go to 3.

3- If you get to point 3 and still can't figure out your problem then you're on your own!..

Good luck!

• Yes i have VPS-9 ... 
  
• mesa-utils are installed 
  
• path of glxinfo is  " /usr/bin/glxinfo "
  
• with all these two commands "glxinfo | grep "OpenGL version" & [font=Monaco, Consolas, Courier, monospace]glxinfo | grep "OpenGL" ""  Got " Error: unable to open display" [/font]
  

---

# lshw -short
H/W path Device Class Description
==================================================
system KVM
/0 bus Motherboard
/0/0 memory 96KiB BIOS
/0/401 processor Intel Xeon E312xx (Sandy Bridge, IBRS upd
/0/402 processor Intel Xeon E312xx (Sandy Bridge, IBRS upd
/0/1000 memory 8GiB System Memory
/0/1000/0 memory 8GiB DIMM RAM
/0/100 bridge 440FX - 82441FX PMC [Natoma]
/0/100/1 bridge 82371SB PIIX3 ISA [Natoma/Triton II]
/0/100/1.1 storage 82371SB PIIX3 IDE [Natoma/Triton II]
/0/100/1.2 bus 82371SB PIIX3 USB [Natoma/Triton II]
/0/100/1.2/1 usb1 bus UHCI Host Controller
/0/100/1.2/1/1 input QEMU USB Tablet
/0/100/1.3 bridge 82371AB/EB/MB PIIX4 ACPI
/0/100/2 display GD 5446
/0/100/3 network Virtio network device
/0/100/3/0 eth0 network Ethernet interface
/0/100/4 storage Virtio block device
/0/100/4/0 /dev/vda disk 5368MB Virtual I/O device
/0/100/4/0/1 /dev/vda1 volume 5085MiB EXT3 volume
/0/100/4/0/2 /dev/vda2 volume 32MiB Linux swap volume
/0/100/5 memory RAM memory
/0/100/5/0 generic Virtual I/O device
/0/1 scsi1 storage
/0/1/0.0.0 /dev/cdrom disk QEMU DVD-ROM

[fChk]

• Yes i have VPS-9 ... 
  
• mesa-utils are installed 
  
• path of glxinfo is  " /usr/bin/glxinfo "
  
• with all these two commands "glxinfo | grep "OpenGL version" & [font=Monaco, Consolas, Courier, monospace]glxinfo | grep "OpenGL" ""  Got " Error: unable to open display" [/font]
  

Now, this feedback is more informative than the previous one. But if you followed the logic of my previous post you'll end up in this situation:

1- Does glxinfo command exist on your system ?
> How do you know that? Well just run this:

Code: (Select All)

which glxinfo

If it's installed you'll have the path of its binary.

> + If answer is yes > go to 2.

2- I hope you're not trying this on VPS-9!.. because it doesn't have a display unless you've explicitly created one with xvfb for example. In which point I don't see the point of looking for the GPU!.

> + If answer is yes : you have to give more details on what are you trying to do.

Anyway, the "Error: unable to open display" is a sign that your system doesn't have a display, so you can't open something if it's not there!!

What you should do is create one. The standard way is to set an X environment (aka GUI); but the subtle way -as I said before- is to install xvfb.

Again, even if you do that and fix that error and ending up running that command successfully to get something like this:

Code: (Select All)

[me @ vps9 ~]$ dmesg | grep '\[drm\]'
[   15.978277] [drm] Initialized cirrus 2.0.0 2019 for 0000:00:02.0 on minor 0

[me @ vps9 ~]$ glxinfo | grep ^OpenGL
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 9.0.0, 256 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.3.4
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.1 Mesa 19.3.4
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 19.3.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:
[me @ vps9 ~]$ xrandr --listproviders
Providers: number : 0

The fact is What ever you're intending to do GPU-wise shouldn't work because VPS-9 graphics are emulated and very basic. Hence why I asked for your end game.

[Amresh]

Will
lshw work?
I have never used it but have heard somewhere on stackexchange. Give it a try tho.

[tiwil]

I believe there is no way free VPS can have a GPU. VPS with a GPU is very expensive and should only be used for GPU-intensive work only. For example: https://cloud.google.com/compute/gpus-pricing. Google asks for $2263.00 per GPU monthly for NVIDIA A100. So there is no way Virmach would want to give you a free GPU while it costs so much money.

[sagher]

I believe there is no way free VPS can have a GPU. VPS with a GPU is very expensive and should only be used for GPU-intensive work only. For example: https://cloud.google.com/compute/gpus-pricing. Google asks for $2263.00 per GPU monthly for NVIDIA A100. So there is no way Virmach would want to give you a free GPU while it costs so much money.

Agreed with you, Using or hire a GPU on Rent is an another game, and uses of GPU to do some projects are totally different then any simple VPS server however free or paid, but just for my knowledge i try to know the GPU specs of my container.

[Amresh]

I believe there is no way free VPS can have a GPU. VPS with a GPU is very expensive and should only be used for GPU-intensive work only. For example: https://cloud.google.com/compute/gpus-pricing. Google asks for $2263.00 per GPU monthly for NVIDIA A100. So there is no way Virmach would want to give you a free GPU while it costs so much money.

LMAO in that much Price I can host a Home server with a Good RTX GPU and also it can cover leased lines cost xDxD isnt that overpriced?