Figure which OEMs are keeping their users on old Intel graphics drivers

NEW
Unassigned

Status

()

7 years ago
2 years ago

People

(Reporter: bjacob, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [platform-rel-Intel])

The AdapterSubsysID's in crash reports correspond to OEMs, the mapping can (with difficulty) be done by googling.

A quick check for old drivers on a crash report is: contains Layers- and is capable of Layers. Most recent GPUs are capable of Layers. Only the Intel G33 isn't (vendor 8086, device 29c2) due to lack of support for 4k textures. Also worth weeding out some common older Intel GPUs (2772, 2572).

So this bash command:

$ gzip -cd 20120209-pub-crashdata.csv.gz | grep Layers- | grep 8086 | grep -v 29c2 | grep -v 2772 | grep -v 2572 | grep AdapterSubsysID | sed 's/.*AdapterSubsysID[2]*..//g' | cut -f 1 -d ',' | sort | uniq -c | sort -rn | head -n 20
  10227 0000000c
   4815 00000000
    389 02aa1028
    292 022f1028
    276 01261028
    273 2e321849
    273 03491025
    227 01601028
    200 01791028
    180 25628086
    161 01f31028
    158 0000000e
    152 56418086
    140 75921462
    140 2e328086
    132 01c41028
    119 110a1565
    118 20b517aa
    113 1526103c
    113 00b90e11

OK, so let's start to collect this info in a table of the 'worst' sussysID's for old graphics drivers:

SubsysID | OEM name     | found by link
---------+--------------+-----------------------------------------------------
02aa1028 | Dell         | http://www.simbology.com/smf/index.php?topic=6438.0
022f1028 | Dell         | http://forum.driverpacks.net/viewtopic.php?id=3455
01261028 | Dell         | http://driverscollection.com/Search
         |              | /PCI%5CVEN_8086%26DEV_2562%26SUBSYS_01261028

Please continue expand this table
Summary: Figure which OEMs are keeping their users on old graphics drivers → Figure which OEMs are keeping their users on old Intel graphics drivers
Whiteboard: [platform-rel-Intel]
platform-rel: --- → ?
platform-rel: ? → ---
You need to log in before you can comment on or make changes to this bug.