| Rev | Author | # | Line |
|---|---|---|---|
| 7 | ElroyLiddington | 1 | These are pages that have been created for Perry's PCI identification scripts. |
| 14 | JohnMcPherson | 2 | (see http://www.wlug.org.nz/~~perry/pci/) To find out about your hardware download http://www.wlug.org.nz/~~perry/pci/pci.sh |
| 7 | ElroyLiddington | 3 | and look at the URL it produces. |
| 4 | |||
| 5 | ---- | ||
| 6 | |||
| 12 | ElroyLiddington | 7 | !Maybe look at replacing this page with the following: |
| 7 | ElroyLiddington | 8 | |
| 9 | |||
| 9 | ElroyLiddington | 10 | (humourous example of a PCI ID and how it works will go here, with reference to companies mistakenly using anothers PCI ID) |
| 7 | ElroyLiddington | 11 | |
| 12 | ElroyLiddington | 12 | A __PCI ID__ is a '__P__eripheral __C__omponent __I__nterconnect' (i.e. a piece of hardware) '__ID__entifier'. |
| 7 | ElroyLiddington | 13 | |
| 14 | |||
| 15 | |||
| 16 | There is currently a list of _some_ PCI IDs located here: [http://pciids.sourceforge.net/pci.ids] (WARNING: File is ~500KB in size as of 7/2007). | ||
| 8 | ElroyLiddington | 17 | |
| 18 | More info available here: [http://pciids.sourceforge.net/]. | ||
| 19 | |||
| 20 | How to locate what a device is using this database and the PCI ID you have: | ||
| 21 | |||
| 22 | * Download the _latest_ PCI ID list from sources above. | ||
| 23 | |||
| 24 | * Get the PCI ID of your piece of hardware. | ||
| 25 | |||
| 26 | * Locate the PCI ID using your favourite text/word/whatever editor inside the pci-id database - read what is next to the entry for what your hardware _might_ be... | ||
| 27 | |||
| 28 | |||
| 9 | ElroyLiddington | 29 | NOTES: If your GNU/Linux box is showing ('lspci') your hardware as e.g. '0034 Unknown IDE Controller' etc: |
| 30 | |||
| 31 | * Download the latest PCI ID list. | ||
| 32 | |||
| 10 | ElroyLiddington | 33 | * Change to root user 'su root' |
| 9 | ElroyLiddington | 34 | |
| 10 | ElroyLiddington | 35 | * Locate current PCI ID file 'slocate pci.ids' |
| 9 | ElroyLiddington | 36 | |
| 10 | ElroyLiddington | 37 | * Backup current PCI ID file 'cp /path/to/current/file/pci.ids original.pci.ids' |
| 9 | ElroyLiddington | 38 | |
| 10 | ElroyLiddington | 39 | * Make sure our backup worked 'ls -lh' (check existence of copied file, and compare size to original - should be the same) |
| 40 | |||
| 41 | * Delete current pci.ids file (MAKE SURE IT WAS BACKED UP FIRST!) 'rm /path/to/current/file/pci.ids' | ||
| 42 | |||
| 43 | * Copy latest pci.ids to proper directory 'cp pci.ids /path/to/current/file/' | ||
| 9 | ElroyLiddington | 44 | |
| 11 | ElroyLiddington | 45 | * Check it worked - hopefully if your device has been added to the latest database (if not in there, _please add it_ via notes on pci.ids file homepage), an 'lspci' will come up and correctly identify your previously unknown piece of hardware :) |
| 9 | ElroyLiddington | 46 | |
| 47 | * Profit!!! | ||
| 13 | ElroyLiddington | 48 | |
| 49 | |||
| 50 | Misc Notes: | ||
| 51 | |||
| 52 | * Vendor ID; Product ID; Device ID - e.g. 8086:7e3t:u6i9 | ||
| 7 | ElroyLiddington | 53 | |
| 54 | ---- | ||
| 55 | |||
| 56 | <?plugin BackLinks?> | ||
| 57 | |||
| 58 | ---- | ||
| 59 | CategoryCategory CategoryHardware |
lib/blame.php:177: Warning: Invalid argument supplied for foreach()