[lkml]   [2002]   [Mar]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Screen corruption in 2.4.18
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 <> -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:25    [W:0.147 / U:2.592 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site