Command Line

Let’s Install INXI

INXI is something I mention a lot. In fact, I’ve done a whole INXI article before, I like it that much. It makes sharing detailed hardware information easy. The people trying to help you when you need support may need detailed information about your hardware, which is where INXI excels and why it exists.

You may notice that I didn’t actually link to said previous article. It was a very different article. This one is really just about installing INXI, so that you can toss it out as a quick link while asking for more information. I’ll rewrite the old article to suit this site, probably when I want an ‘easy’ article. Anyhow…

When you post on forums, such as Linux.org, your question may require sharing information about your hardware. Unless otherwise specified, the way I’d run INXI is this:

inxi -F

Or:

inxi -v 7

The output of either of those will give you an adequate amount of information and covers most all the bases. It’s most of the available information without being all of the available information. You may be asked to run a more specific command and you should post the data between the [code]<output from command>[/code] tags to make it more easily read.

So, why this article? Well, there might as well be an article that tells you how to install it. This? This is that article. You’re welcome!

Installing INXI:

Let’s get right to it and start with the easy way. Start by opening  your terminal by pressing CTRL + ALT + T. Once that’s open, use the following command as is appropriate for your distro’s package manager.

Debian/Ubuntu: 

sudo apt install inxi

RHEL/Fedora:

sudo yum install inxi

Manjaro:

sudo pacman -S inxi

OpenSUSE:

sudo zypper install inxi

Any of those should work with the right distro. INXI is a commonly used application and a great tool for your toolbox. So, depending on your distro, use one of those commands.

If you need to install it manually, and you’ll likely need elevated permissions for this, you can just run:

cd /usr/local/bin && wget -O inxi smxi.org/inxi && chmod +x inxi

Because that doesn’t include the man page, you can grab that and install it with a simple command:

inxi -U

If nothing else, those last two commands should work on every Linux desktop system out there, though I suppose you may need to first install wget and need permission to write to the correct directories.

Now that you have INXI (and the manual) installed, just use the inxi -h command. If you’re asking for support somewhere, they’ll probably tell you which command they want you to run when they ask you to run it.

See also: https://smxi.org/

Closure:

Yup… This is a short article, and intentionally so. The goal here is to write an article that helps people install INXI. I think I’ve done that. I may write an article that’s more detailed, meaning ways of using INXI, but today is not that day. Today, it’s just about installation.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

KGIII

Retired mathematician, residing in the mountains of Maine. I may be old and wise, but I am not infallible. Please point out any errors. And, as always, thanks again for reading.

View Comments

  • Nice.
    I have always been a fan of inxi [which was recently updated], As a hardware man it gives me an at a glance overview of someone's hardware in plain language, or more in depth information depending on the combination of codes used, I find it much quicker and easier to use than other terminal codes which present a long list of technical information that can be hard to follow at times. My most used codes are,
    inxi -Fnx , inxi -A ,inxi -G, inxi -N, inxi -S, and inxi -M [or sudo inxi -n].
    If you have never tried inxi I recommend you do so

    • inxi is pretty awesome. It has been around for a while now, but I can't recall when it was first released.

    • I was only using desktop Linux sparingly/pretty much never in 2005. It wasn't until 2007 that I was logistically able to switch completely. Pretty much as soon as I could, I did. I've used Linux exclusively ever since - though I may be faced with getting a Windows device for my music.

      Anyhow, 2005 wouldn't surprise me. I want to say that it existed at the time I started using desktop Linux exclusively.

      I'm not sure why I have to keep manually approving your posts. I'll check the settings.

Recent Posts

A Quick Look At The Shutdown Command

This is going to be just a quick article about a command many of you…

22 hours ago

Setting Up Coding Environments on Linux for Educational Use

With so many strong attributes, such as robustness and flexibility, Linux stands as a powerful…

3 days ago

View Detailed Hardware Information

There are many tools for showing your hardware information and today we'll get to view…

5 days ago

How To: Install Wine In Lubuntu

Today's article isn't going to be complicated or long as we are going to cover…

7 days ago

Update Python Packages (PIP)

We've had a run of Python packages recently and you can tell that I'm a…

1 week ago

Save A Command’s Output To A File (While Showing It In The Terminal)

The title is the best I can come up with to describe this exercise as…

2 weeks ago