How to provide good information in your posts

Try this hwinfo command I dreamed up if you want information about all your network components:

hwinfo --netcard --wlan --bluetooth | grep -Ei "model\:|driver\:|status\:|cmd\:|file\:|detected\:" | grep -v "Config Status" 

Ooh, I like that! Great helper for your "area of expertise."

No, not that one. The other one. :wink:

1 Like

Alright I admit it looks cool :sunglasses: but does'nt hwinfo --network do the same thing? I think it would work for regular trouble shooting anyway but maybe not for total infiltration.

Yes, hwinfo does exactly the same thing. but it outputs too much information that is not essential for troubleshooting. It also outputs sensitive information that really shouldn't be posted on a public forum. That is why I removed all the non-essential and sensitive information from the command output. The full hwifo output is not really what you want posted on a troubleshooting thread, best to be selective for those purposes I think.

1 Like

Ok I guess I see your point, the only other info I see is hardware address so I guess this is considered too sensitive. Not sure why or how that info could make a difference to the average user etc.... But anyway use whatever command you want of course.

If you feel the need to educate me further please pm instead of taking it up on the Tutorials thread.

1 Like

I ran it!

The magic
Model: "Intel Centrino Advanced-N 6200 2x2 AGN"
  Driver: "iwlwifi"
  Device File: wlp3s0
  Link detected: yes
    Driver Status: iwlwifi is active
    Driver Activation Cmd: "modprobe iwlwifi"
  Model: "Intel 82577LM Gigabit Network Connection"
  Driver: "e1000e"
  Device File: enp0s25
  Link detected: no
    Driver Status: e1000e is active
    Driver Activation Cmd: "modprobe e1000e"
  Model: "Broadcom BCM2045B (BDC-2.1)"
    Driver Status: btusb is active
    Driver Activation Cmd: "modprobe btusb"

We should encourage the use of the "details" option when posting

I am feeling the love, thanks for the Hearts folks. Taking My Time On My Ride, enjoy Manjaro.

--nohost should be --no-host


I fixed --no-host, and added the relevant output, as it was not.


--no-host will be activated with -z switch from now on.


well .. next release I guess - both manjaro and upstream github are on 3.0.37-1 from November.

1 Like

Removed --no-host as the current inxi does not seem to be printing host information on this machine at the present.
If this is not the case everywhere someone should let me know, thanks.

I think it is no longer needed with newest inxi versions.

At least on my desktop PC (KDE / Testing / kernel 4.19.106)

inxi -Fxxxza


inxi -Fxxxza --no-host

provide a different output. First command still displays the host.

Whoops, sheez my eyes must be bad. Thanks.

  1. Thanks for this post! I refer people to it thrice per day at a minimum! :grin:

  2. Can you change the

    inxi -Fxxxza --no-host


    inxi --full --verbosity=7 --filter --no-host


  1. The long format is understandable to N00bs as well
  2. It provides more information (E.G. Bluetooth adapter)
  3. It provides less personally identifiable information

Thank you!

Pretty please with :unicorn: :unicorn: and :rainbow: :rainbow: :question:


1 Like

Another tip: straight after the

First no matter what the problem ,

could you add the text below even before the inxi itself:

If you're running a language other than English, please type as the first command
export LANG=C
because not all of us understand Afrikaans, Deutsch, Français, עברית, عربى, हिन्दी, Русский язык or even Vloms... :innocent:
The export LANG=C will cause all subsequent output to be shown in English which most of us understand and some of us can even write! :grin:

:wink: :grin:


now exists manjaro-log-helper :wink:


Looks nice, will try it out.

Forum kindly sponsored by