inxi :: a full featured system information script
Page Version: 2.5 Page Updated: 2018-07-21
- Feedback and bug reports
- Github sources – post issues, clone, or just look at the inxi source code. Includes other branches etc. Note that the master branch is the main branch (what was trunk in svn). Other branches may have things of interest as well, like data, tarballs, etc.
- Man page – html version of man page
- Program options – supported options you can use with inxi
- Program configuration – change display and output defaults; setup configuration files/ setup /etc/sudoers
- About inxi (history, reviews, videos)
- Origins and current status of inxi
- How to use inxi (shell and IRC)
- Tech info – technical inxi matters – dependencies (required programs) and recommends (recommended but not required programs to run inxi); programming conventions; specific components; irc client information.
- FAQs – some answers on issues related to using inxi
Basic -b output with --usb added:
Help! Post any inxi related question's you may have on the inxi support forums, or on IRC - server: OFTC channel: #smxi
But please read the information here on the documentation pages first, almost everything you need to know should be available on this site. For more technical issues, create an issue on the source repositories.
Feedback and bug reports
For us to help you the best, please make sure to include all relevant system data and output when you post bug reports. inxi includes built in data collection tools you can run that create either log files or more full system data. See inxi -h, the -@ series of options for more information. Usually the more of your system data we can get, the more easily we can fix the failed case, which is our goal.
Post any related issues or developer type questions in the script developer forums.
Or, Create an Issue to post bug reports or feature request.
Here's a few examples of typical useage.
Typical -F output for forum support:
Checking on an old server via SSH:
The development version pinxi running on an ARM Orange Pi single board computer (SBC):
Forum posted debugger sample:
System: Host: umaro Kernel: 4.17.8-1-ARCH x86_64 bits: 64 Console: tty 2 Distro: Arch Linux Machine: Type: Desktop Mobo: Gigabyte model: EP45-UD3R serial: <root required> BIOS: Award v: F12 date: 01/25/2010 CPU: Topology: Quad Core model: Intel Core2 Quad Q9650 bits: 64 type: MCP L2 cache: 6144 KiB Speed: 2666 MHz min/max: 2000/3000 MHz Core speeds (MHz): 1: 2730 2: 2535 3: 2764 4: 2571 Graphics: Card-1: AMD Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] driver: radeon v: kernel Display: server: No display server data found. Headless machine? tty: 80x24 Message: Unable to show advanced data. Required tool glxinfo missing. Audio: Card-1: Intel 82801JI HD Audio driver: snd_hda_intel Card-2: AMD Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] driver: snd_hda_intel Card-3: Creative Labs EMU20k1 [Sound Blaster X-Fi Series] driver: snd_ctxfi Sound Server: ALSA v: k4.17.8-1-ARCH Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> IF-ID-1: br-416fd823133a state: up speed: N/A duplex: N/A mac: <filter> IF-ID-2: br-426d78a02f57 state: up speed: N/A duplex: N/A mac: <filter> IF-ID-3: docker0 state: down mac: <filter> IF-ID-4: veth0f8bd52 state: up speed: 10000 Mbps duplex: full mac: <filter> IF-ID-5: veth4218766 state: up speed: 10000 Mbps duplex: full mac: <filter> IF-ID-6: veth513e6a2 state: up speed: 10000 Mbps duplex: full mac: <filter> IF-ID-7: veth52b8206 state: up speed: 10000 Mbps duplex: full mac: <filter> IF-ID-8: vethb9efcc5 state: up speed: 10000 Mbps duplex: full mac: <filter> IF-ID-9: vethe00393c state: up speed: 10000 Mbps duplex: full mac: <filter> IF-ID-10: vethe309c34 state: up speed: 10000 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 18.43 TiB used: 5.22 TiB (28.3%) ID-1: /dev/sda vendor: Samsung model: SSD 850 PRO 256GB size: 238.47 GiB ID-2: /dev/sdb vendor: Toshiba model: HDWE160 size: 5.46 TiB ID-3: /dev/sdc vendor: Toshiba model: HDWE160 size: 5.46 TiB ID-4: /dev/sdd vendor: Western Digital model: WD40EFRX-68WT0N0 size: 3.64 TiB ID-5: /dev/sde vendor: Western Digital model: WD40EFRX-68WT0N0 size: 3.64 TiB RAID: Device-1: storage type: zfs status: ONLINE size: 9.06 TiB free: 3.85 TiB array-1: mirror status: ONLINE size: 3.62 TiB free: 1.44 TiB Components: online: N/A array-2: mirror status: ONLINE size: 5.44 TiB free: 2.41 TiB Components: online: N/A Partition: ID-1: / size: 62.75 GiB used: 11.67 GiB (18.6%) fs: ext4 dev: /dev/sda1 ID-2: /home size: 162.86 GiB used: 1.81 GiB (1.1%) fs: ext4 dev: /dev/sda3 ID-3: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 45.0 C mobo: 35.0 C gpu: radeon temp: 40 C Fan Speeds (RPM): cpu: 1503 fan-2: 0 fan-3: 0 Info: Processes: 253 Uptime: 26m Memory: 7.79 GiB used: 6.27 GiB (80.5%) Init: systemd Shell: bash inxi: 3.0.18
inxi is developed to work on most GNU/Linux distributions. The script comes pre-installed in SolusOS, Crunchbang, Epidemic, Linux Mint and AntiX. Arch Linux, Debian, Ubuntu, Gentoo, Slackware, OpenSUSE, Redhat Epel, and many others have inxi packaged in either their primary or secondary repositories. We hope, as more maintainers and users discover and find inxi a nice tool, it will find its place in more distributions.
Some distributions are very bad about ever updating inxi, so you might be better off running inxi from the git sources instead if that's the case, since new features and bug fixes are released all the time. Hint: if your inxi version is a major release version lower than current inxi (like current is 3.0.12, and your repo version is 2.2.35), you probably want the git version. Current inxi will always run fine on your system, no matter how old it is.
See inxi options here for list of options. Always check inxi -h to get the full list of the latest options (the wiki page may become outdated).
Origins and current status of inxi
inxi is a full rewrite of locsmif's infobash script. h2 is the primary author, with a few contributions from trash80, damentz (of Liquorix fame), and various other contributors.
The original infobash scripting methods were not debuggable, readable, or maintainable, so we forked the script.
We started with a set of bug fixes and code readability updates. Then, once the potential became exposed, we added more features. The rewrites far exceeded the original utility, thus the inxi project began.
Version 3.0.0 was another full rewrite, this time to Perl 5.xx (5.08 minimum supported version). Once it had become obvious that Perl 6 was its own language, and Perl 5 was healthy and being developed actively, I decided that the headache of dealing with the Gawk/Bash mix was not worth it long term
The replacement language had to check all the following boxes: A: has been around a long time, B: doesn't break its language features all the time, C: supports complex data structures, D: can run on old systems without breaking, E: Fast (Perl 5 is VERY fast), and F: is a native Practical Extraction and Reporting Language. The latter is, conveniently, exactly what Perl 5 is, and what inxi does (extract and report system data). So in early 2018 inxi Perl, v 3.0.0 was released, and inxi 2.3.56 was put into the git inxi-legacy branch as an historical oddity.