Host GPU, accelerator, CPU and memory inventory

Observed 2026-10-16 at 00:39:23 UTC from the assignment's restricted execution environment. This is a snapshot of hardware and software exposed to this process, not an unrestricted physical inspection of the machine.

Result: the visible PCI inventory contains one graphics controller, one encryption/security coprocessor, and one audio coprocessor. No general-purpose GPU compute accelerator, NPU, TPU or FPGA was identified. It would be inaccurate to say “no accelerator devices are attached”: the graphics and specialized coprocessor functions below are present. CPU topology reports 16 physical cores / 32 logical CPUs, and Linux reports 134,655,262,720 bytes (125.41 GiB) of total usable RAM. Evidence and qualifications follow.

Device count	Observed model and PCI address	Device memory	Driver evidence
1 graphics controller	ASPEED Graphics Family, vendor/device 1a03:2000, revision 52, 0000:09:00.0	Capacity unknown. PCI memory windows are reported as 16M and 256K; these are address-space mappings, not a verified VRAM capacity.	lspci reports no driver in use. ast is absent from the loaded-module list. Installed ast module metadata is readable, but its standalone version field is empty. Its kernel compatibility string begins 6.8.0-146-generic.
1 encryption/security coprocessor	AMD Family 19h PSP/CCP, 1022:1649, 0000:0e:00.2	Capacity unknown. PCI windows are 1M and 8K; these do not establish dedicated memory capacity.	ccp is bound according to lspci and appears in /proc/modules. Available module metadata reports version 1.1.0, description “AMD Secure Processor driver”, kernel compatibility 6.8.0-146-generic.
1 audio coprocessor	AMD ACP/ACP3X/ACP6x Audio Coprocessor, 1022:15e2, revision 62, 0000:0e:00.5	Capacity unknown. A 256K PCI window is visible.	snd_rpl_pci_acp6x is bound and loaded. Its standalone version field is empty; kernel compatibility is 6.8.0-146-generic.

These are three distinct PCI functions, not a claim of three separate add-in cards. The audio device is included because the request covers accelerators broadly. The ASPEED model is reported only at the family level established by PCI enumeration; an exact AST chip model is unverified. Driver metadata comes from modinfo; it does not independently prove the exact binary version currently loaded. Running kernel release is 6.8.0-146-generic. Sources: evidence E1 and E2 below.

CPU / memory fact	Observed value and basis
CPU model	AMD Ryzen 9 9950X 16-Core Processor, from /proc/cpuinfo
Physical cores	16, calculated from 16 distinct (physical id, core id) pairs; all records show physical ID 0, core IDs 0–15, and cpu cores: 16
Logical CPUs	32, processor IDs 0–31; independently reported by getconf _NPROCESSORS_ONLN
Total usable RAM	/proc/meminfo: MemTotal: 131499280 kB; multiplied by 1024 = 134,655,262,720 bytes, or 125.40748596191406 GiB; free -b reports the same byte count
Installed DIMM capacity / job resource allowance	Unverified. No DIMM inventory was obtained. Cgroup CPU and memory limit files were unavailable, so these totals are not asserted to be this job's allocation.

The physical-core count is a derivation from exposed kernel topology. lscpu failed because /sys/devices/system/cpu/possible was unavailable; /proc/cpuinfo supplied the fallback evidence. MemTotal describes usable RAM, which can be smaller than installed physical RAM. Swap is excluded. Sources: E3 and the Linux kernel documentation for /proc/meminfo.

Compute software checked	Presence / version / limits
NVIDIA CUDA	nvidia-smi and nvcc were not found on the executable search path. No CUDA/NVIDIA libraries matched the linker-cache search, and /usr/local/cuda/version.json and version.txt were unavailable. No driver or runtime version established.
AMD ROCm / HIP / HSA	rocminfo, rocm-smi, amd-smi, hipcc, and hipconfig were not found. No relevant runtime libraries matched; /opt/rocm/.info/version was unavailable. No runtime version established.
Intel oneAPI / Level Zero / SYCL	sycl-ls, icpx, and xpu-smi were not found. No relevant runtime libraries matched; /opt/intel/oneapi was unavailable. No runtime version established.
OpenCL	Loader library present: libOpenCL.so.1 loads successfully. clGetPlatformIDs(0, NULL, &count) returns -1001, meaning no platforms available through this loader. Vendor runtime / platform version unavailable. The .so.1 suffix is not an OpenCL API version.
Vulkan	Loader library present: libvulkan.so.1. vkEnumerateInstanceVersion succeeds and reports instance API 1.3.275. No Vulkan physical-device enumeration or compute workload was performed; this is not a GPU driver version or proof of a hardware compute device.
Other accelerator stacks	hl-smi, habana-smi, neuron-ls, neuron-top, xrt-smi, xbutil, and npu-smi were not found. No associated runtime versions established.

Source: E4. OpenCL's error interpretation follows the Khronos platform-enumeration reference and error constant definition. Vulkan's version query reports instance-level functionality, as specified in the Khronos reference.

The linker cache also contains libdrm.so.2, libdrm_amdgpu.so.1, libdrm_intel.so.1, and libGLX_mesa.so.0. Their presence does not establish attached AMD/Intel graphics hardware or a working compute runtime. Package-release versions remain unknown: dpkg-query exited successfully but returned zero package records before filtering, despite the libraries being present. That query therefore cannot substantiate package absence. The survey did not search every private software installation or language environment.

Evidence and checks. The primary source is the local observation captured in evidence/inventory.json, using collect_inventory.py. The JSON preserves commands, exit statuses, stderr, selected procfs fields, filters, and timestamps. The following excerpts and outcomes make the main findings readable without those companion files:

E1 — PCI enumeration. lspci -Dnnk exited 0 and returned 46 PCI functions. Relevant entries:

0000:09:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 52)
0000:0e:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 19h PSP/CCP [1022:1649]
    Kernel driver in use: ccp
0000:0e:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor [1022:15e2] (rev 62)
    Kernel driver in use: snd_rpl_pci_acp6x

The ASPEED function is the only display-class entry. No processing-accelerator class [12xx] entry appears. Detailed lspci -vnn -s queries for these three addresses produced the memory windows in the device table. Each reported Capabilities: <access denied>. The complete listing, including devices outside the target categories, is retained under JSON commands.pci; detail records are commands.graphics_detail, crypto_detail, and audio_detail.

E2 — Drivers. uname -r returned 6.8.0-146-generic. The filtered /proc/modules scan returned:

snd_rpl_pci_acp6x 16384 0 - Live 0x0000000000000000
ccp 147456 1 kvm_amd, Live 0x0000000000000000

No loaded modules matched nvidia*, nouveau, amdgpu, radeon, i915, xe, ast, drm*, accel*, ivpu, intel_vpu, amdxdna, habanalabs*, neuron*, xocl, zocl, apex, or gasket. Built-in drivers are not necessarily represented by this list. modinfo -F version ccp returned 1.1.0. Equivalent version queries for ast and snd_rpl_pci_acp6x exited 0 with empty output. All three modinfo -F vermagic queries returned 6.8.0-146-generic SMP preempt mod_unload modversions. See JSON loaded_modules and commands.modinfo_*.

E3 — CPU and RAM. Selected /proc/cpuinfo fields are retained for all 32 processors under JSON cpuinfo. Their core IDs repeat 0–15 twice in physical package 0. getconf _NPROCESSORS_ONLN returned 32. The memory evidence is:

/proc/meminfo: MemTotal:       131499280 kB
free -b:      Mem total       134655262720

Both commands used for the CPU cross-check and memory cross-check exited 0. lscpu exited 1 with failed to determine number of CPUs: /sys/devices/system/cpu/possible: No such file or directory.

E4 — Runtime checks. The library-cache query exited 0; the retained filter and matches are under JSON commands.libraries. Tool lookup results are under tool_discovery. Calls through Python ctypes produced:

libOpenCL.so.1: clGetPlatformIDs return = -1001
libvulkan.so.1: vkEnumerateInstanceVersion return = 0
               encoded version = 4206867; decoded instance API = 1.3.275

The OpenCL count variable was initialized to zero; the no-platform conclusion relies on the return code, not on an output parameter after an error. See JSON runtime_queries.

E5 — Visibility checks and unsuccessful probes. All of the following were actually checked:

• No matching accelerator nodes appeared in /dev for prefixes nvidia, dri, kfd, accel, hl, davinci, neuron, apex, xlnx, vchiq, or mali.
• /sys/bus/pci/devices, /sys/bus/usb/devices, /sys/class/drm, /sys/class/accel, /sys/class/misc, /proc/driver/nvidia, /dev/dri, and /dev/accel returned “No such file or directory”.
• /sys/module/ccp/version and /sys/module/ast/version were unavailable. This prevents a sysfs version check of the running modules.
• lsusb exited 1: unable to initialize libusb: -99. USB accelerator absence is therefore not established.
• /sys/fs/cgroup/cpu.max and /sys/fs/cgroup/memory.max were unavailable. No resource-limit conclusion is drawn.

See JSON directories, device_nodes, files, and commands.usb. Missing interfaces are recorded as visibility limits, not evidence that an entire physical bus is empty.

Inference and unanswered questions. The available evidence supports “no general-purpose compute accelerator identified or demonstrated usable in this execution environment.” It does not prove that the physical host has none: hidden or disabled devices, USB devices, and installations outside the observed software view remain unverified. Exact ASPEED chip model, each coprocessor's physical memory capacity, complete installed runtime releases, exact loaded module build identities, installed DIMM capacity, and job resource limits remain unanswered. Resolving these requires a more complete host inventory interface; no values have been guessed.

Collection and consistency checks were performed locally without installing packages, loading drivers, modifying devices, or running a benchmark. The companion validation record documents internal checks only; it is not independent certification of the host or of the report's completeness.