diagnostics: new scriptmodule to collect system/runtime info#3391
Draft
cmitu wants to merge 3 commits intoRetroPie:masterfrom
Draft
diagnostics: new scriptmodule to collect system/runtime info#3391cmitu wants to merge 3 commits intoRetroPie:masterfrom
cmitu wants to merge 3 commits intoRetroPie:masterfrom
Conversation
Add a new RetroPie system item, used to collect diagnostic information and create an archive containing relevant information. The archive created can be optionally uploaded to a RetroPie diagnostics server or just saved locally. Information collected (grouped in folders): - system information: a summary produced by `inxi`, `dmesg` info, Linux kernel modules loaded, list of `.deb` packages installed. - RPI specific information: firmware version, RPIOS info, tvservice info about current video mode and supported modes, DRM modes for KMS platforms, RPI bootloader configuration. - EmulationStation information: configuration files, head of the log file, input configuration - Emulator log and configuration: runcommand's last log file, RetroArch configurations. - input device information: input devices present, `udevadm` info about each device, output from `evemu-desc` with detected device capabilities - RetroPie related configuration: release version, Git branches present, latest 3 log files, packages installed, RetroPie related configuration files from `$configdir/all` - audio information: local ALSA configuration, list of available devices, PulseAudio audio sinks listing (if detected running) Some info is filtered out from log files (IP addresses, username if not `pi`) using a filter function. The information collected can be extended by adding a new function `_<xyz>_diagnostics` and including `<xyz>` as a collection module in the `_generate_diagnostics` function - ex. `odroid` or `osmc` specific info can be added by defining the `_odroid_diagnostics` function similar to other collection functions.
Member
|
Sorry I've not had a chance to look over this properly yet. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a new RetroPie system item, used to collect diagnostic information and create an archive containing relevant information.
The archive created can be optionally uploaded to a RetroPie diagnostics server or just saved locally.
Information collected (grouped in folders):
inxi,dmesginfo, Linux kernel modules loaded, list of.debpackages installed.udevadminfo about each device, output fromevemu-descwith detected device capabilities$configdir/allSome info is filtered out from log files (IP addresses, username if not
pi) using a filter function.The information collected can be extended by adding a new function
_<xyz>_diagnosticsand including<xyz>as a collection module in the_generate_diagnosticsfunction - ex.odroidorosmcspecific info can be added by defining the_odroid_diagnosticsfunction similar to other collection functions.MISSING/TODOS: