Re: Screen corruption in 2.4.18

Andre Pang (ozone@algorithm.com.au)
Mon, 25 Mar 2002 14:00:21 +1100


On Sun, Mar 24, 2002 at 08:40:27PM -0600, Steven Walter wrote:

> I fear this as well. In fact, I'm relatively certain that they /do/
> both use the same PCI ID. Hence why lspci lists KT133/KM133. But I
> hope to big mistaken. If not, the only way I can see of detecting that
> it is a KM133 is by checking what device 01:00 is an S3 ProSavage.
> Yuck.

Is it possible to identify the KT133/KM133 by the vendor string,
rather than the PCI ID? It's, erm, kinda ugly, but it might be
the cleanest way to do it if the PCI ID isn't unique.

-- 
#ozone/algorithm <ozone@algorithm.com.au>          - trust.in.love.to.save
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/