inxi [-AbBCdDEfFGhiIjJlLmMnNopPrRsSuUVwzZ]
inxi [-c NUMBER] [--sensors-exclude SENSORS] [--sensors-use SENSORS] [-t [c|m|cm|mc][NUMBER]] [-v NUMBER] [-W LOCATION] [--weather-unit {m|i|mi|im}] [-y WIDTH]
inxi [--memory-modules] [--memory-short] [--recommends] [--sensors-default] [--slots]
inxi [-x|-xx|-xxx|-a] -OPTION(s)
All short form options have long form variants - see below for these and more advanced options.
inxi output varies depending on whether it is being used on CLI or IRC, with some default filters and color options applied only for IRC use. Script colors can be turned off if desired with -c 0, or changed using the -c color options listed in the STANDARD OPTIONS section below.
Because inxi is often used on forums for support, you can also trigger this filtering with the -z option (-Fz, for example). To override the IRC filter, you can use the -Z option. This can be useful in debugging network connection issues online in a private chat, for example.
Letters with numbers can have no gap or a gap at your discretion, except when using -t. Note that if you use an option that requires an additional argument, that must be last in the short form group of options. Otherwise you can use those separately as well.
For example: inxi -AG | inxi -A -G | inxi -b | inxi -c10 | inxi -FxxzJy90 | inxi -bay
Note that all the short form options have long form equivalents, which are listed below. However, usually the short form is used in examples in order to keep things simple.
Note that for charge:, the output shows the current charge, as well as its value as a percentage of the available capacity, which can be less than the original design capacity. In the following example, the actual current available capacity of the battery is 22.2 Wh.
charge: 20.1 Wh (95.4%)
The condition: item shows the remaining available capacity / original design capacity, and then this figure as a percentage of original capacity available in the battery.
condition: 22.2/36.4 Wh (61%)
With -x, or if voltage difference is critical, volts: item shows the current voltage, and the min: voltage. Note that if the current is below the minimum listed the battery is essentially dead and will not charge. Test that to confirm, but that's technically how it's supposed to work.
volts: 12.0 min: 11.4
With -x shows attached Device-x information (mouse, keyboard, etc.) if they are battery powered.
These color selectors run a color selector option prior to inxi starting which lets you set the config file value for the selection.
NOTE: All configuration file set color values are removed when output is piped or redirected. You must use the explicit runtime -c <color number> option if you want color codes to be present in the piped/redirected output.
Color selectors for each type display (NOTE: IRC and global only show safe color set):
Setting a specific color type removes the global color selection.
For certain CPUs (some ARM, and AMD Zen family) shows CPU die count.
The details for each CPU include a technical description e.g. type: MT MCP
* MT - Multi/Hyper Threaded CPU, more than 1 thread per core (previously HT).
* MCM - Multi Chip Model (more than 1 die per CPU).
* MCP - Multi Core Processor (more than 1 core per CPU).
* SMP - Symmetric Multi Processing (more than 1 physical CPU).
* UP - Uni (single core) Processor.
Note that min/max: speeds are not necessarily true in cases of overclocked CPUs or CPUs in turbo/boost mode. See -Ca for alternate base/boost: speed data.
If the system has RAID or other logical storage, and if inxi can determine the size of those vs their components, you will see the storage total raw and usable sizes, plus the percent used of the usable size. The no argument short form of inxi will show only the usable (or total if no usable) and used percent. If there is no logical storage detected, only total: and used: will show. Sample (with RAID logical size calculated):
Local Storage: total: raw: 5.49 TiB usable: 2.80 TiB used: 1.35 TiB (48.3%)
Without logical storage detected:
Local Storage: total: 2.89 TiB used: 1.51 TiB (52.3%)
Also shows per disk information: Disk ID, type (if present), vendor (if detected), model, and size. See Extra Data Options (-x options) and Admin Extra Data Options (--admin options) for many more features.
If bluetooth service is down or disabled, will show message.
Note that Report-ID: indicates that the HCI item was not able to be linked to a specific device, similar to IF-ID: in -n.
If your internal bluetooth device does not show, it's possible that it has been disabled, if you try enabling it using for example:
hciconfig hci0 up
and it returns a blocked by RF-Kill error, you can do one of these:
connmanctl enable bluetooth
or
rfkill list bluetooth
rfkill unblock bluetooth
Display: x11 server: Xorg 1.15.1
If protocol is not detected, shows:
Display: server: Xorg 1.15.1
Also shows screen resolution(s) (per monitor/X screen), OpenGL renderer, OpenGL core profile version/OpenGL version.
Compositor information will show if detected using -xx option or always if detected and Wayland.
Note: if -m is used or triggered, the memory item will show in the main Memory: report of -m, not in Info:.
Rasberry Pi only: uses vcgencmd get_mem gpu to get gpu RAM amount, if user is in video group and vcgencmd is installed. Uses this result to increase the Memory: amount and used: amounts.
Hubs and Devices are listed in order of BusID.
BusID is generally in this format: BusID-port[.port][.port]:DeviceID
Device ID is a number created by the kernel, and has no necessary ordering or sequence connection, but can be used to match this output to lsusb values, which generally shows BusID / DeviceID (except for tree view, which shows ports).
Examples: Device-3: 4-3.2.1:2 or Hub: 4-0:1
The rev: 2.0 item refers to the USB revision number, like 1.0 or 3.1.
Logical block devices can be thought of as devices that are made up out of either other logical devices, or physical devices. inxi does its best to show what each logical device is made out of. RAID devices form a subset of all possible Logical devices, but have their own section, -R.
If -R is used with -Lxx, -Lxx will not show RAID information for LVM RAID devices since it's redundant. If -R is not used, a simple RAID line will appear for LVM RAID in -Lxx.
-Lxx also shows all components and devices. Note that since components can go in many levels, each level per primary component is indicated by either another 'c', or ends with a 'p' device, the physical device. The number of c's or p's indicates the depth, so you can see which component belongs to which.
-L shows only the top level components/devices (like -R). -La shows component/device size, maj:min ID, mapped name (if applicable), and puts each component/device on its own line.
Sample:
Device-10: mybackup type: LUKS dm: dm-28 size: 6.36 GiB Components: c-1: md1 cc-1: dm-26 ppp-1: sdj2 cc-2: dm-27 ppp-1: sdk2
LV-5: lvm_raid1 type: raid1 dm: dm-16 size: 4.88 GiB RAID: stripes: 2 sync: idle copied: 100% mismatches: 0 Components: c-1: dm-10 pp-1: sdd1 c-2: dm-11 pp-1: sdd1 c-3: dm-13 pp-1: sde1 c-4: dm-15 pp-1: sde1
It is easier to follow the flow of components and devices using -y1. In this example, there is one primary component (c-1), md1, which is made up of two components (cc-1,2), dm-26 and dm-27. These are respectively made from physical devices (p-1) sdj2 and sdk2.
Device-10: mybackup
maj-min: 254:28
type: LUKS
dm: dm-28
size: 6.36 GiB
Components:
c-1: md1
maj-min: 9:1
size: 6.37 GiB
cc-1: dm-26
maj-min: 254:26
mapped: vg5-level1a
size: 12.28 GiB
ppp-1: sdj2
maj-min: 8:146
size: 12.79 GiB
cc-2: dm-27
maj-min: 254:27
mapped: vg5-level1b
size: 6.38 GiB
ppp-1: sdk2
maj-min: 8:162
size: 12.79 GiB
Other types of logical block handling like LUKS, bcache show as:
Device-[xx] [name/id] type: [LUKS|Crypto|bcache]:
Note: -m uses dmidecode, which must be run as root (or start inxi with sudo), unless you figure out how to set up doas[BSDs]/sudo to permit dmidecode to read /dev/mem as user. speed and bus-width will not show if No Module Installed is found in size.
Note: If -m is triggered RAM total/used report will appear in this section, not in -I or -tm items.
Because dmidecode data is extremely unreliable, inxi will try to make best guesses. If you see (check) after the capacity number, you should check it with the specifications. (est) is slightly more reliable, but you should still check the real specifications before buying RAM. Unfortunately there is nothing inxi can do to get truly reliable data about the system RAM; maybe one day the kernel devs will put this data into /sys, and make it real data, taken from the actual system, not dmi data. For most people, the data will be right, but a significant percentage of users will have either a wrong max module size, if present, or max capacity.
Under dmidecode, Speed: is the expected speed of the memory (what is advertised on the memory spec sheet) and Configured Clock Speed: is what the actual speed is now. To handle this, if speed and configured speed values are different, you will see this instead:
speed: spec: [specified speed] MT/S actual: [actual] MT/S
Also, if DDR, and speed in MHz, will change to: speed: [speed] MT/S ([speed] MHz)
If the detected speed is logically absurd, like 1 MT/s or 69910 MT/s, adds: note: check. Sample:
Memory: RAM: total: 31.38 GiB used: 20.65 GiB (65.8%) Array-1: capacity: N/A slots: 4 note: check EC: N/A Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz) Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz) actual: 61910 MT/s (30955 MHz) note: check Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz) Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz) actual: 2 MT/s (1 MHz) note: check
See --memory-modules and --memory-short if you want a shorter report.
Sample: Report: arrays: 1 slots: 4 modules: 2 type: DDR4
Device information requires either /sys or dmidecode. Note that 'other-vm?' is a type that means it's usually a VM, but inxi failed to detect which type, or positively confirm which VM it is. Primary VM identification is via systemd-detect-virt but fallback tests that should also support some BSDs are used. Less commonly used or harder to detect VMs may not be correctly detected. If you get an incorrect output, post an issue and we'll get it fixed if possible.
Due to unreliable vendor data, device type will show: desktop, laptop, notebook, server, blade, plus some obscure stuff that inxi is unlikely to ever run on.
<username> ALL = NOPASSWD: /usr/bin/file (sample)
BSD users: see man doas.conf for setup.
Does not show components (partitions that create the md-raid array) of md-raid arrays.
APK (Alpine Linux + derived versions)
APT (Debian, Ubuntu + derived versions, as well as RPM based APT distros like PCLinuxOS or Alt-Linux)
CARDS (NuTyX + derived versions)
EOPKG (Solus)
NIX (NixOS + other distros as alternate package manager)
PACMAN (Arch Linux, KaOS + derived versions)
PACMAN-G2 (Frugalware + derived versions)
PISI (Pardus + derived versions)
PKG (OpenBSD, FreeBSD, NetBSD + derived OS types)
PORTAGE (Gentoo, Sabayon + derived versions)
PORTS (OpenBSD, FreeBSD, NetBSD + derived OS types)
SCRATCHPKG (Venom + derived versions)
SLACKPKG (Slackware + derived versions)
TCE (TinyCore)
URPMI (Mandriva, Mageia + derived versions)
XBPS (Void)
YUM/ZYPP (Fedora, Red Hat, Suse + derived versions)
More will be added as distro data is collected. If yours is missing please show us how to get this information and we'll try to add it.
See -rx, -rxx, and -ra for installed package count information.
md-raid: If device is resyncing, also shows resync progress line.
Note: Only md-raid, ZFS and hardware RAID are currently supported. Other software RAID types may be added, if the software RAID actually can be made to give the required output.
The component ID numbers work like this: mdraid: the numerator is the actual mdraid component number; ZFS: the numerator is auto-incremented counter only. Eg. Online: 1: sdb1
If hardware RAID is detected, shows basic information. Due to complexity of adding hardware RAID device disk / RAID reports, those will only be added if there is demand, and reasonable reporting tools.
Make sure that there is no space between letters and numbers (e.g. write as -t cm10).
If inxi -h has no listing for -U then it's disabled.
Auto-update script. Note: if you installed as root, you must be root to update, otherwise user is fine. Also installs / updates this man page to: /usr/local/share/man/man1 (if /usr/local/share/man/ exists AND there is no inxi man page in /usr/share/man/man1, otherwise it goes to /usr/share/man/man1). This requires that you be root to write to that directory. See --man or --no-man to force or disable man install.
Supported levels: 0-8 Examples : inxi -v 4 or inxi -v4
DO NOT USE THIS FEATURE FOR AUTOMATED WEATHER UPDATES! You will be blocked from any further access. This feature is not meant for widget type weather monitoring, or Conky type use. It is meant to get weather when you need to see it, for example, on a remote server.
See https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 for current 2 letter country codes.
Use only ASCII letters in city/state/country names.
Examples: -W 95623,us OR -W Boston,MA OR -W 45.5234,-122.6762 OR -W new+york,ny OR -W bodo,norway.
DO NOT USE THIS FEATURE FOR AUTOMATED WEATHER UPDATES! Use of automated queries, will result in your access being blocked. If you try to work around the ban, you will be permanently banned from this service.
Please note that the data sources are not static per value, and can change any time, or be removed, so always test to verify which source is being used for each value if that is important to you. Data sources may be added or removed on occasions, so try each one and see which you prefer. If you get unsupported source message, it means that number has not been implemented.
If no integer value is given, sets width to default of 80.
Examples: inxi -Fxx -y 130 or inxi -Fxxy or inxi -bay1
These extra data triggers can be useful for getting more in-depth data on various options. They can be added to any long form option list, e.g.: -bxx or -Sxxx
There are 3 extra data levels:
-x, -xx, -xxx
OR
--extra 1, --extra 2, --extra 3
The following details show which lines / items display extra information for each extra data level.
- Adds version/port(s)/driver version (if available) for each device.
- Adds PCI/USB ID of each device.
- Adds non-running sound servers, if detected.
- Adds attached battery powered peripherals (Device-[number]:) if detected (keyboard, mouse, etc.).
- Adds battery volts:, min: voltages. Note that if difference is critical, that is current voltage is too close to minimum voltage, shows without -x.
- Adds boost: [enabled|disabled] if detected, aka turbo. Not all CPUs have this feature.
- Adds CPU Flags (short list). Use -f to see full flag/feature list.
- Adds CPU microarchitecture + revision (e.g. Sandy Bridge, K8, ARMv8, P6, etc.). Only shows data if detected. Newer microarchitectures will have to be added as they appear, and require the CPU family ID, model ID, and stepping.
Examples: arch: Sandy Bridge rev: 2, arch: K8 rev.F+ rev: 2
If unable to non-ambiguosly determine architecture, will show something like: arch: Amber Lake note: check rev: 9
Method 1: Systems running Linux kernels ~5.6 and newer should have drivetemp module data available. If so, drive temps will come from /sys data for each drive, and will not require root or hddtemp. This method is MUCH faster than using hddtemp. Note that NVMe drives do not require drivetemp.
If your drivetemp module is not enabled, enable it:
modprobe drivetemp
Once enabled, add drivetemp to /etc/modules or /etc/modules-load.d/***.conf so it starts automatically.
If you see drive temps running as regular user and you did not configure system to use doas[BSDs]/sudo hddtemp, then your system supports this feature. If no /sys data is found, inxi will try to use hddtemp methods instead for that drive. Hint: if temp is /sys sourced, the temp will be to 1 decimal, like 34.8, if hddtemp sourced, they will be integers.
Method 2: if you have hddtemp installed, if you are root or if you have added to /etc/sudoers (sudo v. 1.7 or newer):
<username> ALL = NOPASSWD: /usr/sbin/hddtemp (sample)
BSD users: see man doas.conf for setup.
You can force use of hddtemp for all drives using --hddtemp.
- If free LVM volume group size detected (root required), show lvm-free: on Local Storage line. This is how much unused space the VGs contain, that is, space not assigned to LVs.
- Adds PCI/USB Bus ID of each device.
- Adds driver version (if available) for each device.
- Adds (if available, and hciconfig only) LMP (HCI if no LMP data, and HCI if HCI/LMP versions are different) version (if available) for each HCI ID.
- Adds direct rendering status.
- Adds (for single GPU, nvidia driver) screen number that GPU is running on.
- Adds PCI/USB ID of each device.
Note that there is no way we are aware of to filter out the deprecated IP v6 scope site/global temporary addresses from the output of ifconfig. The ip tool shows that clearly.
ip-v6-temporary - (ip tool only), scope global temporary. Scope global temporary deprecated is not shown
ip-v6-global - scope global (ifconfig will show this for all types, global, global temporary, and global temporary deprecated, ip shows it only for global)
ip-v6-link - scope link (ip/ifconfig) - default for -i.
ip-v6-site - scope site (ip/ifconfig). This has been deprecated in IPv6, but still exists. ifconfig may show multiple site values, as with global temporary, and global temporary deprecated.
ip-v6-unknown - unknown scope
- Adds default system gcc. With -xx, also show other installed gcc versions.
- Adds current runlevel (not available with all init systems).
- Adds total packages discovered in system. See -xx and -a for per package manager types output. Moves to Repos if -rx.
If your package manager is not supported, please file an issue and we'll add it. That requires the full output of the query or method to discover all installed packages on your system, as well of course as the command or method used to discover those.
- If in shell (i.e. not in IRC client), adds shell version number, if available.
- Adds device type in the Device line.
- Adds version/port(s)/driver version (if available) for each device;
- Adds PCI/USB ID of each device.
Example: ID-4: /home ... dev: /dev/dm-6 mapped: ar0-home
- Hardware RAID: Adds driver version, Bus ID.
- Adds to Distro: base: if detected. System base will only be seen on a subset of distributions. The distro must be both derived from a parent distro (e.g. Mint from Ubuntu), and explicitly added to the supported distributions for this feature. Due to the complexity of distribution identification, these will only be added as relatively solid methods are found for each distribution system base detection.
- Adds wind speed and direction.
- Adds disk speed (if available). This is the theoretical top speed of the device as reported. This speed may be restricted by system board limits, eg. a SATA 3 drive on a SATA 2 board may report SATA 2 speeds, but this is not completely consistent, sometimes a SATA 3 device on a SATA 2 board reports its design speed.
NVMe drives: adds lanes, and (per direction) speed is calculated with lane speed * lanes * PCIe overhead. PCIe 1 and 2 have data rates of GT/s * .8 = Gb/s (10 bits required to transfer 8 bits of data). PCIe 3 and greater transfer data at a rate of GT/s * 128/130 * lanes = Gb/s (130 bits required to transfer 128 bits of data).
For a PCIe 3 NVMe drive, with speed of 8 GT/s and 4 lanes (8GT/s * 128/130 * 4 = 31.6 Gb/s):
speed: 31.6 Gb/s lanes: 4
- Adds (hciconfig only) LMP subversion (and/or HCI revision if applicable) for each device.
- Adds Xorg compositor, if found (always shows for Wayland systems).
- For free drivers, adds OpenGL compatibility version number if available. For nonfree drivers, the core version and compatibility versions are usually the same. Example:
v: 3.3 Mesa 11.2.0 compat-v: 3.0
- If available, shows alternate: Xorg drivers. This means a driver on the default list of drivers Xorg automatically checks for the device, but which is not installed. For example, if you have nouveau driver, nvidia would show as alternate if it was not installed. Note that alternate: does NOT mean you should have it, it's just one of the drivers Xorg checks to see if is present and loaded when checking the device. This can let you know there are other driver options. Note that if you have explicitly set the driver in xorg.conf, Xorg will not create this automatic check driver list.
- If available, shows Xorg dpi (s-dpi:) for the active Xorg Screen (not physical monitor). Note that the physical monitor dpi and the Xorg dpi are not necessarily the same thing, and can vary widely.
- Adds other detected installed gcc versions (if present).
- Adds system default runlevel, if detected. Supports Systemd/Upstart/SysVinit type defaults.
- Shows Packages: counts by discovered package manager types. In cases where only 1 type had results, does not show total after Packages:. Does not show installed package managers wtih 0 packages. See -a for full output. Moves to Repos if -rxx.
- Adds parent program (or tty) that started shell, if not IRC client.
- Adds full list of Components, sub-components, and their physical devices.
- For LVM RAID, adds a RAID report line (if not -R). Read up on LVM documentation to better understand their use of the term 'stripes'.
- Adds memory device Part Number (part-no:). Useful for ordering new or replacement memory sticks etc. Part numbers are unique, particularly if you use the word memory in the search as well. With -xxx, also shows serial number.
- Adds single/double bank memory, if data is found. Note, this may not be 100% right all of the time since it depends on the order that data is found in dmidecode output for type 6 and type 17.
- Hardware RAID: Adds Chip vendor:product ID.
- Adds, if run in X, window manager type (wm), if available. Not all window managers are supported. Some desktops support using more than one window manager, so this can be useful to see what window manager is actually running. If none found, shows nothing. Uses a less accurate fallback tool wmctrl if ps tests fail to find data.
- Adds desktop toolkit (tk), if available (Xfce/KDE/Trinity).
- Adds cloud cover, rain, snow, or precipitation (amount in previous hour to observation time), if available.
- Adds, if present, PCI/USB class ID.
- Adds attached device rechargeable: [yes|no] information.
- Adds disk partition scheme (in most cases), e.g. scheme: GPT. Currently not able to detect all schemes, but handles the most common, e.g. GPT or MBR.
- Adds disk rotation speed (in some but not all cases), e.g. rotation: 7200 rpm or rotation: SSD if positive SSD identification was made. If no rotation or positive SSD ID found, nothing shows. Not all disks report this speed, so even if they are spinnning, no data will show.
- Adds (hciconfig only) HCI version, revision.
- For Shell: adds (su|sudo|login) to shell name if present.
- For Shell: adds default: shell if different from running shell, and default shell v:, if available.
- For running-in: adds (SSH) to parent, if present. SSH detection uses the whoami test.
- Adds interfaces: for non hub devices.
- Adds, if available, USB speed in Mbits/s or Gbits/s.
- Adds, if present, USB class ID.
- Adds, if non 0, max power in mA.
- Adds device Type Detail, e.g. detail: DDR3 (Synchronous).
- Adds, if present, memory module voltage. Only some systems will have this data available.
- Adds device serial number.
- Adds, if present, PCI/USB class ID.
- zfs-raid: Adds portion allocated (used) by RAID array/device.
- Hardware RAID: Adds rev, ports, and (if available and/or relevant) vendor: item, which shows specific vendor [product] information.
- Adds (if present), window manager (wm) version number.
- Adds (if present), display manager (dm) version number.
- Adds (if available, and in display), virtual terminal (vt) number. These are the same as ctrl+alt+F[x] numbers usually. Some systems have this, some don't, it varies.
The --admin option sets -xxx, and only has to be used once. It will trigger the following features:
- Adds CPU microcode. Format is hexadecimal.
- Adds socket type (for motherboard CPU socket, if available). If results doubtful will list two socket types and note: check. Requires doas[BSDs]/sudo/root and dmidecode. The item in parentheses may simply be a different syntax for the same socket, but in general, check this before trusting it.
Sample: socket: 775 (478) note: check Sample: socket: AM4
- Adds DMI CPU base and boost/turbo speeds. Requires doas[BSDs]/sudo/root and dmidecode. In some cases, like with overclocking or 'turbo' or 'boost' modes, voltage and external clock speeds may be increased, or short term limits raised on max CPU speeds. These are often not reflected in /sys based CPU min/max: speed results, but often are using this source.
Samples:
CPU not overclocked, with boost, like Ryzen: Speed: 2861 MHz min/max: 1550/3400 MHz boost: enabled base/boost: 3400/3900 Overclocked 2900 MHz CPU, with no boost available: Speed: 2900 MHz min/max: 800/2900 MHz base/boost: 3350/3000 Overclocked 3000 MHz CPU, with boosted max speed: Speed: 4190 MHz min/max: 1200/3001 MHz base/boost: 3000/4000
Note that these numbers can be confusing, but basically, the base number is the actual normal top speed the CPU runs at without boost mode, and the boost number is the max speed the CPU reports itself able to run at. The actual max speed may be higher than either value, or lower. The boost number appears to be hard-coded into the CPU DMI data, and does not seem to reflect actual max speeds that overclocking or other combinations of speed boosters can enable, as you can see from the example where the CPU is running at a speed faster than the min/max or base/boost values.
Note that the normal min/max: speeds do NOT show actual overclocked OR boost/turbo mode speeds, and appear to be hard-coded values, not dynamic real values. The base/boost: values are sometimes real, and sometimes not. base appears in general to be real.
- Adds CPU Vulnerabilities (bugs) as known by your current kernel. Lists by Type: ... (status|mitigation): .... for systems that support this feature (Linux kernel 4.14 or newer, or patched older kernels).
Using smartctl (requires doas[BSDs]/sudo/root privileges).
- Adds device model family, like Caviar Black, if available.
- Adds SATA type (eg 1.0, 2.6, 3.0) if a SATA device.
- Adds device kernel major:minor number (Linux only).
- Adds SMART report line: status, enabled/disabled, health, powered on, cycles, and some error cases if out of range values. Note that for Pre-fail items, it will show the VALUE and THRESHOLD numbers. It will also fall back for unknown attributes that are or have been failing and print out the Attribute name, value, threshold, and failing message. This way even for unhandled Attribute names, you should get a solid report for full failure cases. Other cases may show if inxi believes that the item may be approaching failure. This is a guess so make sure to check the drive and smartctl full output to verify before taking any further action.
- Adds, for USB or other external drives, actual model name/serial if available, and different from enclosure model/serial, and corrects block sizes if necessary. Adds in drive temperature for some drives as well, and other useful data.
No support currently exists for Wayland since we so far can find no documentation or easy methods to extract this information from Wayland compositors. This unfortunate situation may change in the future, hopefully. However, most Wayland systems also come with xwayland, which should supply the tools necessary for the time being.
Further note that all references to Displays, Screens, and Monitors are referring to the X technical terms, not normal consumer usage. 1 Display runs 1 or more Screens, and a Screen runs 1 or more Monitors.
- Adds Display ID, for the Display running the Screen that runs the Monitors.
- Adds total number of Screens listed for the current Display.
- Adds default Screen ID if Screen (not monitor!) total is greater than 1.
- Adds Screen line, which includes the ID (Screen: 0) then s-res (Screen resolution), s-dpi, s-size and s-diag. Remember, this is an Xorg Screen, NOT a monitor screen, and the information listed is about the Xorg Screen! It may at times be the same as a single monitor system, but usually it's different in some ways.
- Adds Monitor ID(s). Monitors are a subset of a Screen, each of which can have one or more monitors. Normally a dual monitor setup is 2 monitors run by one Xorg Screen. Each monitor has the following data, if available:
- res: resolution in pixels. This is the individual monitor's reported pixel dimensions.
- hz: frequency in Herz, as reported to Xorg. Note that there have been and may continue to be bugs with how Xorg treats > 1 monitor frequencies.
- dpi: dpi (dots per inch), aka, ppi (pixels per inch). This is the physical screen dpi, which is calculated using the screen dimensions and its resolution.
- size: size in mm (inches). Note that this is the real monitor size, not the Xorg Screen size, which can be quite different (1 Xorg Screen can for instance contain two or more monitors).
- diag: monitor screen diagonal in mm (inches). Note that this is the real monitor size, not the Xorg full Screen diagonal size, which can be quite different.
Sample (with both xdpyinfo and xrandr data available):
inxi -aG Graphics: .... Display: x11 server: X.Org 1.20.6 driver: loaded: modesetting display ID: :0.0 screens: 1 Screen-1: 0 s-res: 2560x1024 s-dpi: 96 s-size: 677x271mm (26.7x10.7") s-diag: 729mm (28.7") Monitor-1: DVI-I-0 res: 1280x1024 hz: 60 dpi: 96 size: 338x270mm (13.3x10.6") diag: 433mm (17") Monitor-2: VGA-0 res: 1280x1024 hz: 60 dpi: 86 size: 376x301mm (14.8x11.9") diag: 482mm (19") ....- Adds, if present, possible alternate: kernel modules capable of driving each Device-x (not including the current loaded:). If no non-driver modules found, shows nothing. NOTE: just because it lists a module does NOT mean it is available in the system, it's just something the kernel knows could possibly be used instead.
inxi -aI Info: .... Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 5/6/7/8/9 Packages: apt: 3681 lib: 2096 rpm: 0 Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16 running-in: kate inxi: 3.1.04
- Adds service control tool, tested for in the following order: systemctl rc-service service sv /etc/rc.d /etc/init.d - useful to know which you need when using an unfamiliar machine.
For -P per swap physical partition:
swappiness: 60 (default) cache-pressure: 90 (default 100)
For -j row 1 output:
Kernel: swappiness: 60 (default) cache-pressure: 90 (default 100)
- Adds device kernel major:minor number (Linux only).
- Adds maj-min to LV and other devices.
raw-size: 60.00 GiB.
- Adds percent of raw size available to size: item, e.g.
size: 58.81 GiB (98.01%).
Note that used: 16.44 GiB (34.3%) percent refers to the available size, not the raw size.
- Adds partition filesystem block size if found (requires root and blockdev).
- Adds device kernel major:minor number (Linux only).
- Adds, if available, component size, major:minor number, state (Linux only). Turns Component report to 1 component per line if size and major:minor present.
Note that in some cases, --display will cause inxi to hang endlessly when running the option in console with Intel graphics. The situation regarding other free drivers such as nouveau/ATI is currently unknown. It may be that this is a bug with the Intel graphics driver - more information is required.
You can test this easily by running the following command out of X/display server: glxinfo -display :0
If it hangs, --display will not work.
inxi -MJ --force dmidecode,lsusb
- dmidecode - Force use of dmidecode. This will override /sys data in some lines, e.g. -M or -B.
- hddtemp - Force use of hddtemp instead of /sys temp data for disks.
- lsusb - Forces the USB data generator to use lsusb as data source (default). Overrides USB_SYS in user configuration file(s).
- usb-sys - Forces the USB data generator to use /sys as data source instead of lsusb (Linux only).
- vmstat - Forces use of vmstat for memory data.
- wmctl - Force System item wm to use wmctrl as data source, override default ps source.
SHOW_HOST='false' - Same as: SHOW_HOST='true'
This is an absolute override, the host will always show no matter what other switches you use.
This is an absolute override, the host will not show no matter what other switches you use.
dev-base - /dev partition identifier, like /dev/sda1. Note that it's an alphabetic sort, so sda12 is before sda2.
fs - Partition filesystem. Note that sorts will be somewhat random if all filesystems are the same.
id - Mount point of partition (default).
label - Label of partition. If partitions have no labels, sort will be random.
percent-used - Percentage of partition size used.
size - KiB size of partition.
uuid - UUID of the partition.
used - KiB used of partition.
Example: inxi -sxx --sensors-exclude k10temp-pci-00c3
Can be useful if the default sensor data used by inxi is not from the right sensor array. Note that all other sensor data will be removed, which may lead to undesired consequences. Please be aware that this can lead to many undesirable side-effects, since default behavior is to use all the sensors arrays and select which values to use from them following a set sequence of rules. So if you force one to be used, you may lose data that was used from another one.
Most likely best use is when one (or two) of the sensor arrays has all the sensor data you want, and you just want to make sure inxi doesn't use data from another array that has inacurate or misleading data.
Note that gpu, network, disk, and other specific device monitor chips are excluded by default, and should not be added since they do not provide cpu, board, system, etc, sensor data.
Example: inxi -sxx --sensors-use nct6791-isa-0290,k10temp-pci-00c3
inxi -Cxxx --sleep 0.15
Overrides default internal value and user configuration value:
CPU_SLEEP=0.25
The sign you need to use this is extra numbers before the key/value pairs of the output of your program. These are IRC, not TTY, color codes. Please post a github issue if you find you need to use --tty (including the full -Ixxx line) so we can figure out how to add your program to the list of whitelisted programs.
You can see what inxi believed started it in the -Ixxx line, Shell: or Client: item. Please let us know what that result was so we can add it to the parent start program whitelist.
The IP address from the URL must be the last item on the last (non-empty) line of the page content source code.
Same as configuration value (example):
WAN_IP_URL='https://mysite.com/ip.php'
WRAP_MAX=85 (previously INDENT_MIN)
Previously called: --indent-min.
* tree traversal data file(s) read from /proc and /sys, and other system data.
* xorg conf and log data, xrandr, xprop, xdpyinfo, glxinfo etc.
* data from dev, disks, partitions, etc.
inxi --ftp ftp.yourserver.com/incoming --debug 21
Only use the following in conjunction with --debug 2[012], and only use if you experienced a failure or hang, or were instructed to do so.
To run inxi in Konversation as a native script if your distribution or inxi package hasn't already done this for you, create this symbolic link:
KDE 4: ln -s /usr/local/bin/inxi /usr/share/kde4/apps/konversation/scripts/inxi
KDE 5: ln -s /usr/local/bin/inxi /usr/share/konversation/scripts/inxi
If inxi is somewhere else, change the path /usr/local/bin to wherever it is located.
If you are using KDE/QT 5, then you may also need to add the following to get the Konversation /inxi command to work:
ln -s /usr/share/konversation /usr/share/apps/
Then you can start inxi directly, like this:
/inxi [options]
OLD: /shell -o inxi [options]
Newer (2014 and later) WeeChats work pretty much the same now as other console IRC clients, with /exec -o inxi [options]. Newer WeeChats have dropped the -curses part of their program name, i.e.: weechat instead of weechat-curses.
/etc/inxi.conf contains the default configurations. These can be overridden by user configurations found in one of the following locations (inxi will store its config file using the following precedence: if $XDG_CONFIG_HOME is not empty, it will go there, else if $HOME/.conf/inxi.conf exists, it will go there, and as a last default, the legacy location is used), i.e.:
$XDG_CONFIG_HOME/inxi.conf > $HOME/.conf/inxi.conf > $HOME/.inxi/inxi.conf
See the documentation page for more complete information on how to set these up, and for a complete list of options:
https://smxi.org/docs/inxi-configuration.htm
COLS_MAX_CONSOLE The max display column width on terminal. If terminal/console width or --width is less than wrap width, wrapping of line starter occurs COLS_MAX_IRC The max display column width on IRC clients.
COLS_MAX_NO_DISPLAY The max display column width in console, out of GUI desktop.
CPU_SLEEP Decimal value 0 or more. Default is usually around 0.35 seconds. Time that inxi will 'sleep' before getting CPU speed data, so that it reflects actual system state.
DOWNLOADER Sets default inxi downloader: curl, fetch, ftp, perl, wget. See --recommends output for more information on downloaders and Perl downloaders.
FILTER_STRING Default <filter>. Any string you prefer to see instead for filtered values.
LIMIT Overrides default of 10 IP addresses per IF. This is only of interest to sys admins running servers with many IP addresses.
NO_DIG Set to 1 or true to disable WAN IP use of dig and force use of alternate downloaders.
NO_DOAS Set to 1 or true to disable internal use of doas.
NO_HTML_WAN Set to 1 or true to disable WAN IP use of HTML Downloaders and force use of dig only, or nothing if dig disabled as well. Same as --no-html-wan. Only use if dig is failing, and HTML downloaders are hanging.
NO_SUDO Set to 1 or true to disable internal use of sudo.
PARTITION_SORT Overrides default partition output sort. See --partition-sort for options.
PS_COUNT The default number of items showing per -t type, m or c. Default is 5.
SENSORS_CPU_NO In cases of ambiguous temp1/temp2 (inxi can't figure out which is the CPU), forces sensors to use either value 1 or 2 as CPU temperature. See the above configuration page on smxi.org for full info.
SENSORS_EXCLUDE Exclude supplied sensor array[s] from sensor output. Override with --sensors-default. See --sensors-exclude.
SENSORS_USE Use only supplied sensor array[s]. Override with --sensors-default. See --sensors-use.
SEP2_CONSOLE Replaces default key / value separator of ':'.
USB_SYS Forces all USB data to use /sys instead of lsusb.
WAN_IP_URL Forces -i to use supplied URL, and to not use dig (dig is generally much faster). URL must begin with http or ftp. Note that if you use this, the downloader set tests will run each time you start inxi whether a downloader feature is going to be used or not.
The IP address from the URL must be the last item on the last (non-empty) line of the URL's page content source code.
Same as --wan-ip-url [URL]
WEATHER_SOURCE Values: [0-9]. Same as --weather-source. Values 4-9 are not currently supported, but this can change at any time.
WEATHER_UNIT Values: [m|i|mi|im]. Same as --weather-unit.
WRAP_MAX (previously INDENT_MIN) The maximum width where the line starter wraps to its own line. If terminal/console width or --width is less than wrap width, wrapping of line starter occurs. Overrides default. See --wrap-max. If 80 or less, wrap will never happen.
NOTE: All default and configuration file set color values are removed when output is piped or redirected. You must use the explicit -c <color number> option if you want colors to be present in the piped/redirected output (creating a PDF for example).
CONSOLE_COLOR_SCHEME The color scheme for console output (not in X/Wayland).
GLOBAL_COLOR_SCHEME Overrides all other color schemes.
IRC_COLOR_SCHEME Desktop X/Wayland IRC CLI color scheme.
IRC_CONS_COLOR_SCHEME Out of X/Wayland, IRC CLI color scheme.
IRC_X_TERM_COLOR_SCHEME In X/Wayland IRC client terminal color scheme.
VIRT_TERM_COLOR_SCHEME Color scheme for virtual terminal output (in X/Wayland).
You may be asked to run the inxi debugger tool (see --debug 21/22), which will upload a data dump of system files for use in debugging inxi. These data dumps are very important since they provide us with all the real system data inxi uses to parse out its report.
https://smxi.org/docs/inxi.htm
inxi is a fork of locsmif's very clever infobash script.
Original infobash author and copyright holder: Copyright (C) 2005-2007 Michiel de Boer aka locsmif
inxi version: Copyright (C) 2008-2021 Harald Hope
This man page was originally created by Gordon Spencer (aka aus9) and is maintained by Harald Hope (aka h2 or TechAdmin).
Initial CPU logic, konversation version logic, occasional maintenance fixes, and the initial xiin.py tool for /sys parsing (obsolete, but still very much appreciated for all the valuable debugger data it helped generate): Scott Rogers
Further fixes (listed as known):
Horst Tritremmel <hjt at sidux.com>
Steven Barrett (aka: damentz) - USB audio patch; swap percent used patch.
Jarett.Stevens - dmidecode -M patch for older systems with no /sys.
The nice people at irc.oftc.net channels #linux-smokers-club and #smxi, who all really have to be considered to be co-developers because of their non-stop enthusiasm and willingness to provide real-time testing and debugging of inxi development.
Siduction forum members, who have helped get some features working by providing a large number of datasets that have revealed possible variations, particularly for the RAM -m option.
AntiX users and admins, who have helped greatly with testing and debugging, particularly for the 3.0.0 release.
ArcherSeven (Max), Brett Bohnenkamper (aka KittyKatt), and Iotaka, who always manage to find the weirdest or most extreme hardware and setups that help make inxi much more robust.
For the vastly underrated skill of output error/glitch catching, Pete Haddow. His patience and focus in going through inxi repeatedly to find errors and inconsistencies is much appreciated.
All the inxi package maintainers, distro support people, forum moderators, and in particular, sys admins with their particular issues, which almost always help make inxi better, and any others who contribute ideas, suggestions, and patches.
Without a wide range of diverse Linux kernel-based Free Desktop systems to test on, we could never have gotten inxi to be as reliable and solid as it's turning out to be.
And of course, a big thanks to locsmif, who figured out a lot of the core methods, logic, and tricks originally used in inxi Gawk/Bash.