To all:
The discussion concerning getting a monitor firmware code correct brings
up an interesting question:
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?
lspci -k
If the name of a given device looks odd, check the date of your hwdata package.
-Ben
Sent from ProtonMail mobile
Original Message
On Mar 20, 2023, 5:29 PM, American Citizen wrote:
> To all: The discussion concerning getting a monitor firmware code correct
> brings u
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 l
"How do I assure that the CPU and drivers for the controllers are
correctly matched to the hardware?"
If they're not correctly matched those devices either won't be recognize,
they'll be listed as "unknown" in the lspci output or they won't work.
Also, there are cases when there might be a few
