GPU Monitoring (ARM / RaspberryPi)

[nicolargo]

Description

Monitor ARM GPU thanks to the vcdbg command line.

Have a look on the following Python code: https://github.com/MilhouseVH/bcmstat/blob/master/bcmstat.sh
Especial:

• https://github.com/MilhouseVH/bcmstat/blob/master/bcmstat.sh#L586

[nicolargo]

Man page for vcgencmd: http://www.elinux.org/RPI_vcgencmd_usage

Measure clock:

OpenELEC:~ # for src in arm core h264 isp v3d uart pwm emmc pixel vec hdmi dpi
> do
> echo -e "$src:\t$(vcgencmd measure_clock $src)"
> done
arm:	frequency(45)=600000000      <=== CPU
core:	frequency(1)=250000000        <=== GPU
h264:	frequency(28)=250000000
isp:	frequency(42)=250000000
v3d:	frequency(43)=0
uart:	frequency(22)=47999000
pwm:	frequency(25)=0
emmc:	frequency(47)=250000000
pixel:	frequency(29)=85500000
vec:	frequency(10)=0
hdmi:	frequency(9)=163683000
dpi:	frequency(4)=0

Memory:

OpenELEC:~ # vcgencmd get_mem gpu
gpu=256M

Temperature (to be added to the sensor module ?)

vcgencmd measure_temp
temp=49.4'C

[nicolargo]

No current consumption...

[nicolargo]

NVtop support the following GPUs:

• AMD
• Intel
• NVIDIA
• Adreno
• Apple
• Ascend (only tested on 910B)

NVTOP supports Adreno GPUs using the msm linux driver.

msm introduced the fdinfo interface in kernel 6.0 (browse kernel source). Hence, you will need a kernel with a version greater or equal to 6.0 to see the processes using Adreno GPUs.

[Ciantic]

NVtop got a Raspberry Pi's V3D support few weeks ago: Syllo/nvtop#315

[github-actions[bot]]

This issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution ! ✨

[nicolargo]

Feature implemented into develop branch.

Should be tested by one or more user with ARM GPU plugin !

Thanks :)

[serl]

I'd be glad to help (Raspi 3 and Raspi 3+).

How do I do? I did some poking around (cloning the repo on device and running from there), but I see no difference compared to the pip version, I guess I'm missing some parameters/configuration?

[nicolargo]

Hi @serl

thanks for the proposal, you can follow this procedure: https://github.com/nicolargo/glances/wiki/Install-and-test-Glances-DEVELOP-version

Let me know if you have any issue.

[serl]

Let's start by saying that I first launched glances in my life this same week, so I'm maybe looking in the wrong place, anyways, that's what I did:

git clone https://github.com/nicolargo/glances.git
cd glances
make install-uv
make venv
make run

I'm on a fresh Raspberry Pi OS Lite (Debian 13, Kernel 6.12.75+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1 (2026-03-11), aarch64).

This is what I see in the top bar:

And on the side:

While I would have expected to see somewhere the GPU clock (vcgencmd measure_clock core), memory (vcgencmd get_mem gpu) and temperature (vcgencmd measure_temp).
Also, not GPU-specific, but it would be very interesting to have somewhere the throttled status (alerts?), since it's something that could very well help debugging some cases (undervoltage for example).

The Raspi 3+ has Raspberry Pi OS non-lite, same kernel version and same result.

[nicolargo]

For the moment, Glances did not use the vcgencmd CLI. It only read DRM devices from /sys/class/drm and per-client stats from /proc/*/fdinfo via the standardised drm-driver fdinfo format (it requires Linux kernel >= 6.0).

Supported drivers: msm (Adreno), panfrost, panthor, v3d, lima, etnaviv.

Can you make a tree command on both folders ?

[serl]

Ok so I have some bad news:

$ tree /sys/class/drm/
/sys/class/drm/
├── card0 -> ../../devices/platform/soc/soc:gpu/drm/card0
├── card0-HDMI-A-1 -> ../../devices/platform/soc/soc:gpu/drm/card0/card0-HDMI-A-1
├── card0-Writeback-1 -> ../../devices/platform/soc/soc:gpu/drm/card0/card0-Writeback-1
├── renderD128 -> ../../devices/platform/soc/soc:gpu/drm/renderD128
└── version

$ tree /sys/class/drm/card0
/sys/class/drm/card0
├── card0-HDMI-A-1
│   ├── connector_id
│   ├── ddc -> ../../../../3f805000.i2c/i2c-2
│   ├── device -> ../../card0
│   ├── dpms
│   ├── edid
│   ├── enabled
│   ├── modes
│   ├── power
│   │   ├── autosuspend_delay_ms
│   │   ├── control
│   │   ├── runtime_active_time
│   │   ├── runtime_status
│   │   └── runtime_suspended_time
│   ├── status
│   ├── subsystem -> ../../../../../../../class/drm
│   └── uevent
├── card0-Writeback-1
│   ├── connector_id
│   ├── device -> ../../card0
│   ├── dpms
│   ├── edid
│   ├── enabled
│   ├── modes
│   ├── power
│   │   ├── autosuspend_delay_ms
│   │   ├── control
│   │   ├── runtime_active_time
│   │   ├── runtime_status
│   │   └── runtime_suspended_time
│   ├── status
│   ├── subsystem -> ../../../../../../../class/drm
│   └── uevent
├── dev
├── device -> ../../../soc:gpu
├── power
│   ├── autosuspend_delay_ms
│   ├── control
│   ├── runtime_active_time
│   ├── runtime_status
│   └── runtime_suspended_time
├── subsystem -> ../../../../../../class/drm
└── uevent

$ tree /sys/class/drm/card0/device
/sys/class/drm/card0/device
├── driver -> ../../../../bus/platform/drivers/vc4-drm
├── driver_override
├── drm
│   ├── card0
│   │   ├── card0-HDMI-A-1
│   │   │   ├── connector_id
│   │   │   ├── ddc -> ../../../../3f805000.i2c/i2c-2
│   │   │   ├── device -> ../../card0
│   │   │   ├── dpms
│   │   │   ├── edid
│   │   │   ├── enabled
│   │   │   ├── modes
│   │   │   ├── power
│   │   │   │   ├── autosuspend_delay_ms
│   │   │   │   ├── control
│   │   │   │   ├── runtime_active_time
│   │   │   │   ├── runtime_status
│   │   │   │   └── runtime_suspended_time
│   │   │   ├── status
│   │   │   ├── subsystem -> ../../../../../../../class/drm
│   │   │   └── uevent
│   │   ├── card0-Writeback-1
│   │   │   ├── connector_id
│   │   │   ├── device -> ../../card0
│   │   │   ├── dpms
│   │   │   ├── edid
│   │   │   ├── enabled
│   │   │   ├── modes
│   │   │   ├── power
│   │   │   │   ├── autosuspend_delay_ms
│   │   │   │   ├── control
│   │   │   │   ├── runtime_active_time
│   │   │   │   ├── runtime_status
│   │   │   │   └── runtime_suspended_time
│   │   │   ├── status
│   │   │   ├── subsystem -> ../../../../../../../class/drm
│   │   │   └── uevent
│   │   ├── dev
│   │   ├── device -> ../../../soc:gpu
│   │   ├── power
│   │   │   ├── autosuspend_delay_ms
│   │   │   ├── control
│   │   │   ├── runtime_active_time
│   │   │   ├── runtime_status
│   │   │   └── runtime_suspended_time
│   │   ├── subsystem -> ../../../../../../class/drm
│   │   └── uevent
│   ├── controlD64 -> card0
│   └── renderD128
│       ├── dev
│       ├── device -> ../../../soc:gpu
│       ├── power
│       │   ├── autosuspend_delay_ms
│       │   ├── control
│       │   ├── runtime_active_time
│       │   ├── runtime_status
│       │   └── runtime_suspended_time
│       ├── subsystem -> ../../../../../../class/drm
│       └── uevent
├── modalias
├── of_node -> ../../../../firmware/devicetree/base/soc/gpu
├── power
│   ├── autosuspend_delay_ms
│   ├── control
│   ├── runtime_active_time
│   ├── runtime_status
│   └── runtime_suspended_time
├── subsystem -> ../../../../bus/platform
└── uevent

So looks like the driver is unsupported: vc4-drm (I would have expected v3d on raspberry, no?), and there's no hwmon.

About /proc/*/fdinfo, they exist, but sudo grep -r drm /proc/*/fdinfo does not find anything.

[serl]

Seems like v3d exists only starting from Raspi 4 (from the Raspberry Pi forum: post and post)