The inxi command is probably the single most frequently requested command that we ask users to run when they ask a support question on this site. Considering that some of these users may have just installed Linux for the first time, asking them to run inxi and finding out that it isn’t installed can be an understandably frustrating first experience. Given it’s usefulness for support purposes and fairly light (although not miniscule) dependency requirements, I suggest including it in desktop environment bases for future releases.
4 Likes
We have hwinfo in base system
1 Like
Is hwinfo in Workstation? I didn’t see it in the group comps. I always install it myself on Everything.
I do favour hwinfo, it’s much more straightforward. No single-letter flags like inxi, but I view that as not a bad thing, helps users to understand what they’re doing.
$ hwinfo --netcard --short
network:
enp3s0 Intel I211 Gigabit Network Connection
eno1 Intel Ethernet Connection (2) I219-V
wlp4s0 Intel Dual Band Wireless-AC 3168NGW [Stone Peak]
$ inxi -N
Network:
Device-1: Intel Ethernet I219-V driver: e1000e
Device-2: Intel I211 Gigabit Network driver: igb
Device-3: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
For verbose output just drop the --short. I don’t know how to get the correct level of verbose output with inxi. Is it -Nx, -Nxx, -Nxxx, -Nv, -Nv{1,8}, -Na, or something else? inxi --help is 500+ lines long; I’ve read it multiple times and never figured it out.
hwinfo also has fewer requirements, and isn’t a single 30k+ line Perl script 
3 Likes
I also suggest to the regulars to make use of fpaste --sysinfo more. It covers a lot of info that is relevant to common questions like distro version, kernel version, DE, pci/usb devices, dnf repolist and recent packages.
fpaste is included in Workstation. It’s also in @standard group so I think all (?) spins should include it.
1 Like