NVME-SOLIDIGM-VS-(1)
πΈ NVME-SOLIDIGM-VS-(1): NAME πΈ
Okay bestie, welcome to the NVMe Manual page for nvme-solidigm-vs-fw-activate-history β the command that gets the firmware activation history log. That's literally the whole name and the whole job. π
π¦ SYNOPSIS π¦
Run it like this, no cap:
nvme [<global-options>] solidigm vs-fw-activate-history <device> [OPTIONS]
β¨ DESCRIPTION β¨
This command retrieves the firmware activation history log for Solidigm NVMe devices, and it redirects to the OCP plug-in for compatibility. So you ask for the history, and it hands things over to the OCP plug-in. That's the vibe. π«Ά
π OPTIONS π
π GLOBAL OPTIONS π
These options are defined at the top-level nvme command and are available to this subcommand too:
--dry-runβ prints the command that would be executed, but does not actually execute it. It's giving "look but don't touch." π--no-ioctl-probingβ disables probing for64-bit IOCTLsupport.--no-retriesβ disables retry logic on transient errors.-o <fmt>,--output-format=<fmt>β sets the reporting format tonormal,tabular,'json, orbinary. Only one output format may be used at a time, so pick your fave. β¨--output-format-version=<version>β selects the output format version. Version1uses the original field naming, while version2(the default) provides more consistent and script-friendly field names. Other versions are rejected. Periodt.--quietβ suppresses informational messages. Errors are still reported, and--quietcancels any--verbosefor the library log level. So it's quiet, but not "ignore actual problems" quiet. π--set-options=<key=value>[,<key=value>...]β sets libnvme library options for this invocation. Supported keys areforce-4k,mi-probe-enabled,test-base-dir, andtest-sysfs-dir. π--timeout=<ms>β sets the timeout for the command in milliseconds.infiniteor-1waits without a time limit (0xffffffff). No rush, bestie. β³-v,--verboseβ increases the level of detail in the output. May be specified multiple times to further increase verbosity. Say it with me: more-v, more lore. π₯
These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file, every single time. π
π₯ EXAMPLES π₯
- Print the firmware activation history log in normal format:
# nvme solidigm vs-fw-activate-history /dev/nvme0
- Print the firmware activation history log in JSON format:
# nvme solidigm vs-fw-activate-history /dev/nvme0 -o json
π NVME π
Part of the nvme-cli suite. Iconic. π
That's the whole page, bestie! π Source/version: NVMe. Date: 10/30/2026. Mwah! π«Ά
π¦ where this page comes from
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms