Hello.
I installed CentOS 7 x86_64 and I want to understand which hardware not detected by Linux. Any tools or command?

Thank you.

one more

Is this a trick question??? If it's *NOT* detected by Linux, how exactly do you expect Linux to TELL YOU about it???

You've been here three years, and are approaching 1,300 posts..you've been told about lspci and lsusb in several other of your threads.

2 members found this post helpful.

I wasn't going to say that, "If it's *NOT* detected by Linux, how exactly do you expect Linux to TELL YOU about it" that was my first thought. but i seen answers to I just added one to it.

the only thing I can imagine is the logs, if you could find some lines about unrecognized devices. But as it was mentioned how do you expect any result if not detected. I'm sure that tool will/should report my old nokia phone too (or was that detected properly?)

For the OP I doubt lspci alone is very useful.

Something more useful in knowing which hardware is "detected" is to use: this will actually list the same hardware, but in the end have the info "kernel module" and "kernel driver in use". This information CAN be used to determin if there is some problematic module loading or hardware that does not have any module or "driver" loaded, or the incorrect one or something alike to that.

Another way to accomplish what the thread starter want is ofcourse to manually inspect the "dmesg" file.


Ps. lspci also comes with a "-vv" option. This will give even more info.. Same is valid for lsusb, but it does not give the useful module/kernel info of lspci.. But under the "iproduct" part it seems to give the Kernel module information.

My first port of call tends to be dmesg: see what the kernel said about it.

I thought it was obvious that Linux can't report what it doesn't detect. Telling OP how to find what Linux has detected sets him up to eliminate the hardware he knows he has from the hardware Linux detects. may be more information than a user who asks such a question wants on the first pass. If the next question is 'lspci detects my frammis, but Linux seems not to be using it', then is the next step.

Linux does the opposite for me: it detects USB hubs that aren't available, probably because the stock USB chip supports 4 but the computer has only 2 ports.

"Detect" is ofcourse a very funky term to use, I think the thread starter actually means isn't functioning as expected. If it isn't, and he truly means "detect", than the only way I guess is to compare the system hardware specifications against what is actually detected by his GNU/Linux system, and then deduct if something was not "detected".

Windows OS can show you which hardware are detected and their drivers are installed and which hardware not detected and need drivers. How about Linux?

As you were told in this thread (and in some of your other threads), you can use lsusb, lspci, dmesg, and other commands to see the 'raw' hardware. Not sure how many more times you'd like to hear those answers.

For an OS to be able to know hardware there has to be a way for hardware to report. PCI bus devices tend to have a chip that reports. The way usb works is it tends to have a way to report. If you have some device outside of those two formats then you may have to use other means to report it. Bios and uefi present devices differently so booting in CSM and UEFI may present different hardware to the OS.

plenty of answers given already.

also, "having a driver" is not the same as "detected", which you would know already if you had put in ANY effort at all.

-1

2 members found this post helpful.

I think what you want is something like Device Manager's little exclamation points next to "Unknown device"? What reason would there be for that? The kernel will already take care of connected hardware that it doesn't have drivers for -- I have a Panda Wireless PAU05 that comes with Linux drivers, yet in absence of their installation the "rt2x00 lib/usb" drivers are working just fine for it.