On 3/20/23 17:29, American Citizen wrote: > I just ran lspci on my system (under root privileges) and got quite a > long list: > > How do I assure that the CPU and drivers for the controllers are > correctly matched to the hardware? > > Or do we naively assume that whatever (insert your favorite linux flavor > here) will get it right? Do we have to do some manual intervention here?
Use lspci -v or lspci -vv to get all the gory, or EXTRA gory, details, including which kernel modules are in use. You can use modinfo <name> to get some information on the module to see if it makes sense. Some of the lspci entries are subdevices of other devices and thus need no module or driver, or use the same one as the parent device. Linux gets it right most of the time. Very occasionally it grabs the wrong module - usually older devices that may have been rolled into new modules - so you just need to blacklist. You'll know pretty quick: the device is present but does not work. Sensor chips for example can be tricky. -Ed
