getpkg xdpyinfo did the trick for me.
Code: Select all
Device-1: NVIDIA GT216M [GeForce GT 330M] driver: nvidia v: 340.108
Device-2: Chicony USB 2.0 Camera type: USB driver: uvcvideo
Display: server: X.Org 1.20.14 driver: loaded: nvidia
resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GT 330M/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108
And it's a binary, and comes with a man page.
Code: Select all
/usr/bin/xdpyinfo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, stripped
Code: Select all
XDPYINFO(1) General Commands Manual XDPYINFO(1)
NAME
xdpyinfo - display information utility for X
SYNOPSIS
xdpyinfo [-display displayname] [-queryExtensions] [-ext extension-
name] [-version]
DESCRIPTION
Xdpyinfo is a utility for displaying information about an X server. It
is used to examine the capabilities of a server, the predefined values
for various parameters used in communicating between clients and the
server, and the different types of screens and visuals that are avail‐
able.
By default, numeric information (opcode, base event, base error) about
protocol extensions is not displayed. This information can be obtained
with the -queryExtensions option. Use of this option on servers that
dynamically load extensions will likely cause all possible extensions
to be loaded, which can be slow and can consume significant server re‐
sources.
Added in 3 minutes 6 seconds:
And now I have to write me a script that reminds me I need these activated if I see the need in using inxi (or activates all three [with testing if one or more modules are already activated] - when I feel like coding it. [*])
Code: Select all
inxi-3.3.12_1-noarch-1.xzm
perl-5.34.0-x86_64-2_slack15.0.xzm
xdpyinfo-1.3.2-x86_64-4.xzm
______________
[*] which currently I am not. </lazy>