I took a second look this morning now that the meeting is over, and
I've determined that it only crashes if chromium or google-chrome is
being run with the PRIME environment variables.
nvidia-smi output as well as temp sensor data indicated that the
nvidia gpu was being used for chrome as I had hoped, but something
about this prevents nvtop from working.
chrome prints the following to the console after being launched with
the aforementioned env vars:
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open amdgpu: /usr/lib/dri/amdgpu_dri.so: cannot
open shared object file: Permission denied (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix
_dri)
failed to load driver: amdgpu
MESA-LOADER: failed to open zink: /usr/lib/dri/zink_dri.so: cannot
open shared object file: Permission denied (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix
_dri)
failed to load driver: zink
MESA-LOADER: failed to open kms_swrast:
/usr/lib/dri/kms_swrast_dri.so: cannot open shared object file:
Permission denied (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix
_dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot
open shared object file: Permission denied (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix
_dri)
failed to load swrast driver
But otherwise works as expected.
sney
