inxi is a CLI tool that lists information about your Linux system. This includes both hardware and software details. You get simple details like which computer model you have, which kernel, distribution and desktop environment you are using etc. You also get details like which RAM slot of your motherboard is occupied by memory modules etc.
It can also be used to monitor processes that are running on your computer that are either consuming CPU resources or memory resources, or both.
In this tutorial, I’ll show some of the popular use cases of inxi to get information for your Linux system.
But first, let me quickly show you how to install inxi.
Install inxi on your Linux distribution
Inxi is a popular software that is available in the repository of most Linux distributions. Not popular enough to have it installed by default.
To install inxi on Ubuntu and Debian based distributions, use this command:
sudo apt install inxi
To install inxi on Fedora and RHEL8-based distributions, use:
sudo dnf install -y epel-release
sudo dnf install -y inxi
To install inxi on Arch Linux and it’s derivatives, look for it in the AUR:
Using inxi to get Linux system details
You can get an overview of your system information by simply running the inxi command in your terminal.
inxi
As you can see in the image below, it gives a brief overview of CPU information, clockspeed, Kernel, RAM (displayed with Mem) and storage information along with number of running processes and shell version details.

You can also use the “-b” flag to show a more detailed overview of your system information. It will show more information regarding your CPU, drives, currently running processes, motherboard UEFI version, GPU, display resolution, network devices etc
inxi -b

As you might have noticed by the use of the “-b” flag, inxi, just like any command line utility, it has a lot of flags that influence the output of inxi once executed. You can use these flags or combine them to get only certain detailed information.
Let me show a few example.
Get details of audio devices
Using the “-A” flag will present you with information about your audio [output] devices. That will display the physical audio [output] devices, sound server and the audio driver details.
inxi -A

Get battery information
The “-B” flag will show details about your battery (if there is a battery present). You will get details like the current battery charge in Wh (Watt hours) and the condition.
Since I use a desktop, here is a sample output of what the output would look like if the “-B” flag was used with inxi with a battery attached
Battery: ID-1: BAT0 charge: 50.0 Wh (100.0%) condition: 50.0/50.0
Get detailed CPU information
The -C flag shows detailed CPU information. That includes your CPU cache size, speed in MHz (of each core, if there are multiple cores), number of cores, CPU model and also if your CPU is 32-bit or 64-bit.
inxi -C

Make note, if you run inxi -C in a virtual machine, detecting your CPU’s minimum and maximum CPU frequency can be quite tricky for inxi. Below is a sample output of using the “-C” flag with inxi in a quad core Debian 11 Virtual Machine.

Get even more detailed system information
The “-F” flag will show detailed system information (like the “-b” flag, but even more in depth). It includes almost everything to get a high level overview of the system that you are dealing with.
inxi -F

Get graphics related information
The “-G” flag displays the data about everything related to Graphics.
It shows you all your Graphics Devices (GPUs), the [GPU] driver that is being used (helpful to check if you are using the Nvidia driver or the nouveau driver), display output resolution and driver version.
inxi -G

Get running process info
The “-I” (upper case i) shows detailed information about running processes, your current shell, memory (and memory usage) and inxi version.

Get RAM information
As you might have guessed, the -m flag shows you memory (RAM) related information.
It provides information such as total available memory, maximum capacity of memory supported [by your hardware platform or by your CPU manufacturer], number of physical memory slots available on the motherboard, if ECC is present or not, the memory slots that are populated and also what is the size of each module along with the speed that said module is running at, per enumerated slot(s).
inxi -m
To take advantage of the in-depth details provided by the “-m” flag, like the maximum capacity, RAM module details that is at each slot, you need super-user privileges.
sudo inxi -m

If you just want the output to be short and not in this in-depth, you can use the “–memory-short” flag with inxi.
Using the “–memory-short” flag will only show total memory that is available and how much of it is currently in use.
See which package repository is in use
When you use the “-r” flag with inxi, it will present you with a list of all the repositories that your package manager is currently using or updating local repository cache with.

Get RAID devices details
The “-R” flag shows you information about all the RAID devices.
Surprisingly, it even shows information about ZFS RAID (because this file system is not included in many Linux distributions by default). It shows details about the file system on the RAID device, status – if it is online or offline, total size and available size.
inxi -R

Check weather information in Linux terminal (yes, that’s possible too)
And, as a bonus, you can even check the weather of any place on Earth with the “-W” flag.
The “-W” flag needs to be followed by either one of the following location descriptors
- Postal code or zip code
- Latitude,longitude
- City[,state],country (must not contain spaces; replace spaces with the “+” sign)
inxi -W Baroda,India

Monitoring the usage of system resource(s) with inxi
Along with all the verbose information that inxi provides about your installed hardware and the software that drives it, it can also be used for resource monitoring purposes.
Use the “-t” flag to show processes. You can also use the non-mandatory options “c” (for CPU) and “m” (for RAM). These options can also be combined with a numerical value that lists desired amount of processes.
Below are a few examples of using the “-t” flag to monitor system resources.
inxi -t
If you run inxi with “-t” flag but without the non-mandatory options, it will output assuming that you typed added the “cm5” options.

inxi -t cm10

That’s fine for rare use but there are dedicated system resource monitoring tools that are easier to use and have more functionalities.
In the end…
For the individuals who have to diagnose issues with computers and it’s system information that they are not aware about, inxi can be incredibly helpful. It shows the processes that are consuming CPU, memory; you can check if the correct graphics drivers are being used, if the motherboard UEFI/BIOS is up to date, and much more.
In fact, on It’s FOSS Community forum, we ask members to share the output of inxi command while seeking help so that it is easier to see what kind of system is in use.
I know there are other tools that provide hardware info on Linux but inxi combines both hardware and software details and that’s why I like it.
Do you use inxi or some other tool? Share your experience in the comments please.
Usable at Termux in S9 plus Android 10
‘sudo inxi -v8’ will give you pretty much all available output (other than the weather) about your machine and OS. sudo required as elevated privileges are needed to access some RAM/memory info and serial numbers for some hardware.
I do a lot of system monitoring, so having a single tool to generate a full list of metrics to replace a long list of various `cat /sys…`, `lscpu` and `psutil` commands, really appeals.
But I stopped short when I saw the install size of 900 MB. Is this correct?
“`
$ sudo apt install inxi
Reading package lists… Done
…
After this operation, 900 MB of additional disk space will be used.
Do you want to continue? [Y/n]
“`
That seems excessive. Maybe your system doesn’t have the needed libs installed.
That’s absurd, 10 to 1 you didn’t use the –no-install-recommends option, inxi has only 1 hard dependency, Perl 5.08 or newer. The other tools almost all systems will have, like lspci. You probably want to hone your apt skills here a bit (note that almost all these shoiuld already be installed on any reasonably configured system). You clearly instigated a daisy chain of recommends installs by not using the correct install command, and failing to configure apt to not install recommends by default. As you can see, it has only 3 dependencies, and if you used apt, you already have Perl by definitioon, and you have pciutils, and you have procps, so there are zero extra packages to be installed with apt-get install inxi –no-install-recommends
apt-cache depends inxi
inxi
Depends: pciutils
pciutils:i386
Depends: procps
procps:i386
Depends:
perl:i386
perl
Recommends: dmidecode
dmidecode:i386
Recommends: dnsutils
bind9-dnsutils
Recommends: file
file:i386
|Recommends: iproute2
iproute2:i386
Recommends: net-tools
net-tools:i386
Recommends: kmod
kmod:i386
Recommends: lm-sensors
Recommends: mesa-utils
|Recommends: sudo
sudo-ldap
Recommends: doas
doas:i386
Recommends: tree
Recommends: usbutils
usbutils:i386
Recommends: x11-utils
x11-utils:i386
Recommends: x11-xserver-utils
Suggests: libxml-dumper-perl
|Suggests: wget
wget:i386
|Suggests: curl
curl:i386
Suggests: libhttp-tiny-perl
perl
Oh wow, I never paid attention to the recommends when using apt because I’d never assume that using default settings of apt would add 900Mb of unnecessary additional packages to a CLI tool for reporting system info.
I’ve learned something very useful today. Thanks!
While I really like almost everything about Debian, the decision to install recommends by default for apt leads to horrendous results, and I wish they would stop doing that. I’m going to update the docs to add the –no-install-recommends flag for apt installs. This is one of the most extreme cases of this issue I’ve ever seen however, which suggests to me that you may also be pulling in suggests with the recommends, which is a definite no no. inxi is about 1 MiB uncompressed, and in package form probably about 300 KiB or so.
I knew this from Garuda Linux – they make reporting `inxi -Faz` be a requirement when asking for support – and it’s pretty cool. Though I still just use neofetch or uname most of the time, when I’m not on Garuda’s forum.
Merci je vais L’utiliser régulièrement vraiment cool Simple efficace facilement utilisable même débutant en mal de recherches je vais partager salutations.