Add guides on how to manually collect bug report system information #58

Merged
Alaska merged 39 commits from Alaska/blender-developer-docs:manual-system-information into main 2024-08-07 14:17:21 +02:00
Showing only changes of commit 91ca70fb51 - Show all commits

View File

@ -37,18 +37,26 @@ Run `echo $XDG_SESSION_TYPE` in a terminal.
## Graphics Card
TODO: Pick an option: `lspci -k | grep -EA3 'VGA|3D|Display'` or `glxinfo -B`
or something else?
`lspci` should be accessible on every Linux system, but the driver version is not
printed. Is this enough? `glxinfo` may need to be installed on some distros
(Ubuntu needs it installed), but it prints GPU and driver version.
But only of the active display GPU, which may not be the GPU the the user is
launching Blender with. `glxinfo` is usally provided as part of `mesa-utils`, so
the vast majority of distros should offer it.
There are two main ways we recommend to collect GPU information on Linux.
`glxinfo`, or `lspci` if `glxinfo` isn't avaliable.
We can write guides for each GPU vendor, but this means we need to keep it
updated as new GPU vendors are introduced (which may become more common if the
Blender foundation makes a ARM on Linux version).
#### glxinfo
Run `glxinfo -B` in a terminal (you may need to install glxinfo from your
package manager). This will provide you with the GPU name, driver type, and
driver version of the display GPU (the GPU usually used by Blender).
Combine these details together and include them on your bug report form like this:
`AMD Radeon RX 7800XT - Driver Mesa 24.1.0-devel`
TODO: Add image
#### lspci
Run `lspci -k | grep -EA3 'VGA|3D|Display` in a terminal.
This will tell you which graphics cards you have. Collect the GPU name
and include it on your bug report form like this: `Radeon RX 7700 XT / 7800 XT`
TODO: Add Image
## Blender Version