Hardware Troubleshooting Commands (Demo)

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Time
21 hours 25 minutes
Difficulty
Intermediate
CEU/CPE
21
Video Transcription
00:00
>> Hi there Cybrarians and welcome back to
00:00
the Linux pklus course here at Cybrary,
00:00
I'm your instructor Rob Gills.
00:00
In today's lesson we're going to talk
00:00
about hardware troubleshooting commands.
00:00
Upon completion of this lesson,
00:00
you are going to be able to use
00:00
hardware troubleshooting commands to
00:00
identify hardware issues.
00:00
Right off the bat, we're going to talk about dmidecode,
00:00
and this command was created by
00:00
the Distributed Management Task Force.
00:00
They're are also the ones behind the standards,
00:00
the Desktop Management Interface or DMI,
00:00
and System Management BIOS or SMBOIS.
00:00
To use the DMTF standards,
00:00
you need to have a DMI or SMBIOS
00:00
>> complaint system and you
00:00
>> need to have a software interface that
00:00
talks to DMI and SMBIOS.
00:00
Now, in Linux, dmidecode is what provides
00:00
that software interface to the DMI and SMBIOS data.
00:00
What dmidecode actually does is gather information from
00:00
the sys file system and tables that are in
00:00
the sys firmware DMI tables directory.
00:00
Now, the dmidecode has a lot of options,
00:00
so it's always helpful to use the help or
00:00
dash h option to see all the options,
00:00
all the things you can do with the dmidecode.
00:00
Dmidecode dash h,
00:00
I use that a lot because I can
00:00
never remember all the options.
00:00
[LAUGHTER] Now, to pull
00:00
information about a hardware type,
00:00
you could use the dash t option along with a keyword.
00:00
For example, if you want to see
00:00
information about the baseboard or the motherboard,
00:00
you can do sudo dmidecode dash t baseboard,
00:00
and if you want to see information about
00:00
the memory, same thing,
00:00
sudo dmidecode dash t
00:00
and then the memory and that will
00:00
give you the memory information.
00:00
Now, the lshw utility or list hardware,
00:00
that's really useful when you're trying
00:00
to uncover hardware information,
00:00
and by comparison, this reads
00:00
this information from the proc filesystem.
00:00
Now, lshw is installed on most distros,
00:00
but if you can't find it,
00:00
it should be available in
00:00
the standard distros repository.
00:00
You shouldn't need to go out there and hunt for
00:00
some third party repo
00:00
and play repo games with adding things,
00:00
it should just be available.
00:00
You should just be able to do a DNF installer,
00:00
an app installing, you'll be off to the races.
00:00
Now, two helpful,
00:00
lshw options are short.
00:00
Short is what we see over on the right-hand side,
00:00
and it displays the lhsw output
00:00
in a table for metadata display.
00:00
Then bus info shows
00:00
information related to the hardware buses.
00:00
It's going to show information about SCSI,
00:00
USB, IDE or PCI.
00:00
Then finally, the lhsw command
00:00
also accepts what is called the class option.
00:00
This displays detailed information for
00:00
a particular hardware component or a class.
00:00
For example, we could use sudo lshw dashed
00:00
class memory and get a bunch of
00:00
information about the memory on the system.
00:00
With that, in this lesson,
00:00
we covered using hardware troubleshooting commands to
00:00
identify hardware issues such as dmidecode and lshw.
00:00
Thanks so much for being here and I look
00:00
forward to see you in the next lesson.
Up Next