How do you explore your hardware ?

Submitted by rodo on Wed 1 Apr 2009

Tags: , ,

 

lshw  <-> 14%198 votes
lspci  <-> 57%762 votes
dmidecode  <-> 6%81 votes
cat /proc/*  <-> 14%187 votes
cat /sys/*  <-> 3%41 votes
other tool  <-> 3%49 votes
Total 1322 votes

Posted by randallb (74.94.xx.xx) on Wed 1 Apr 2009 at 20:27
[ Send Message ]
lspci for "pci" devices. dmesg (with less or grep) for most other types of devices. lshw if I need to know even more info, like how many sticks of RAM.

[ Parent ]

Posted by daemon (146.231.xx.xx) on Thu 2 Apr 2009 at 21:16
[ Send Message | View Weblogs ]

I also use lsusb(8) quite a bit.

I have a small, informal, routine when we get new hardware to test or diagnose issues with. The first thing that happens is that I dig through the BIOS to see what's off or on by default, then I boot into the latest kubuntu liveCD to hand and check all of the choices from this poll and a few others, like `lsusb -v` and lsmod.

However, I voted for lspci, as there's usually almost all the info I need from a quick `lspci -vvv | less -S`

Cheers,
:wq

[ Parent ]

Posted by Anonymous (141.154.xx.xx) on Tue 21 Apr 2009 at 14:31
I find that "dmesg | less" (or tail/grep/etc) is often the simplest way of getting things like USB ids, hardware/driver errors, and so on. /sys/* is useful if you're looking for something specific, but there's nothing like a system log to give you the complete picture.

[ Parent ]

Posted by Anonymous (69.204.xx.xx) on Mon 6 Apr 2009 at 12:52
'lshal' is another option too.

[ Parent ]

Posted by Anonymous (74.125.xx.xx) on Tue 7 Apr 2009 at 12:06
Hi,

I find the lshw more informative than other commmand , correct me if iam wrong .

Thanks and Regrads
Zaffar ( reloadtheweb@gmail.com)




[ Parent ]

Posted by simonw (84.45.xx.xx) on Sun 12 Apr 2009 at 10:05
[ Send Message | View Weblogs ]
I suspect the whole poll is a bit of marketing for lshw ;)

[ Parent ]

Posted by Anonymous (82.169.xx.xx) on Tue 21 Apr 2009 at 23:20
You guys should explore the fruits of dmidecode! All lspci does is query the pci bus, as if that's the only information you need..?

[ Parent ]

Posted by Anonymous (81.138.xx.xx) on Wed 22 Apr 2009 at 09:17
Screwdriver, Torch, Magnifying glasses. :-/

[ Parent ]

Posted by Fragula (81.138.xx.xx) on Wed 22 Apr 2009 at 09:59
[ Send Message ]
Screwdriver, Torch, Magnifying glasses, tweezers (for "on the fly debugging") and another PC with a web browser open for hardware identification.

Is there another way? :-D

[ Parent ]

Posted by Anonymous (83.253.xx.xx) on Wed 29 Apr 2009 at 18:23
I voted lshw, but lspci is equally true. lshw tends to give way more info than you want (which can be a good thing when you want the serial number for sdc), while I use lspci to check things like NIC drivers.

[ Parent ]