Unsolved
This post is more than 5 years old
1 Rookie
•
53 Posts
0
62171
January 27th, 2016 08:00
R515 - Trying to identify missing driver
I've just put Server 2008 on a PowerEdge R515, and the device manager showed the only missing drivers were the network drivers and a PCI Device. I installed the network drivers, no problem there. But I have no idea what the "PCI Device" is. I tried installing the driver automatically through Windows, but it couldn't find one. Does anyone know what this driver is?
No Events found!


Duup
1 Rookie
•
53 Posts
0
January 27th, 2016 08:00
Addendum, it's device ven_!002 dev_5A23 subsys_4891028
theflash1932
11 Legend
•
16.3K Posts
0
January 27th, 2016 10:00
Try this:
http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=0P26M&fileId=3498563295&osCode=WLHS1
Download and run to extract, then run C:\Openmanage\windows\setup.exe.
2008 or 2008 R2? If 2008, x86 or x64?
Duup
1 Rookie
•
53 Posts
0
January 27th, 2016 11:00
The software installed, but the device still reports that it's missing a driver.
Duup
1 Rookie
•
53 Posts
0
January 27th, 2016 11:00
2008 Standard x64 bit. I'm downloading this to try it now. Thanks!
theflash1932
11 Legend
•
16.3K Posts
0
January 27th, 2016 12:00
Assuming you meant to put 1002 as the VEN ID, that is AMD. The R515 uses AMD processors, so it has to do something with the chipset or a processor feature. The onboard video is a Matrox device.
So, you could try this:
Matrox Video:
http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=4RDNM
Or you could try using one of the driver packs to see if there is some obscure driver hidden in there somewhere:
http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=WMVV0
http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=6WNWD
You could also try the chipset drivers for 2003x64:
http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=5142J&fileId=2731094327&osCode=WX64
In case they aren't native to 2008 like they should be (or not working because of firmware mismatches, etc.).