search

microsoft / graphics-driver-samples

This repository contains graphics driver samples used to demonstrate how to write graphics driver for the windows platform.
Other
378 stars 132 forks source link

getting graphics driver to install properly #66

Open realitycheckrose opened 5 years ago

realitycheckrose commented 5 years ago

I am trying to get the render only graphics sample project (development included some MS engineers), located here: https://github.com/Microsoft/graphics-driver-samples/tree/master/render-only-sample to work correctly. Does anybody here have experience with it? I followed the instructions here: https://github.com/Microsoft/graphics-driver-samples/commit/0b51c4fd023623a410a42bcb13b74c7cde825cf2#diff-f2f6e5599ebefd9a87207862dce0e7b4 or here: https://github.com/Microsoft/graphics-driver-samples/wiki/Install-Driver-in-a-Windows-VM but get the same result: after using devcon to install the driver which it reports it did successfully. When I checked the device in device manager, it reports device did not start and error code 31. The error status is: not_supported and when I look in: \windows\inf\setupapi.dev the render only sample device reports: !!! dvi: Device not started: Device has problem: 0x1f (CM_PROB_FAILED_ADD), problem status: 0xc00000bb. When kernel debugging it on boot I see that the addadapter function is called and no errors appear, and very shortly afterward the remove adaprter is called. Also, testsigning is on, and the binaries and cat file are signed and there is no errors reported about signing issues in the setupapi.dev. which there usually is if there is a signing issue. I can post the whole log if someone is interested. Anybody have an idea what the problem could be? (The projects contributers include MS engineers so I hoped that one of them may read this) thanks for any assistance

realitycheckrose commented 5 years ago

I posted on MSDN and someone replied that maybe there is a problem with updating the ASL. Here is my followup: There are two sets of instruction links that I pasted in my original post. The first says to use devcon install, the second (the wiki) says to use devcon update with no install. When I tried using the devcon update the driver failed to installed.
This led me to think that perhaps adding the ROSD entry to the ASL and then calling asl /loadtable might not be doing what I thought even though it didn't report any errors. So I have tried several ways to update the ASL (incrementing the table number and adding the entry), call asl /loadtable -v ASL.AM and it reports something like what I pasted below. When I search the registry, I can find the MSFTVM03 entry and some data but not anything indicating 'renderonlysample' IDs for the CID and HID. If I try to run devcon update it will fail because it can't find a RenderOnlyDevice. Any thoughts? thanks again. asl output: Microsoft ACPI Source Language Assembler Version 5.0.0NT Copyright (c) 1996,2014 Microsoft Corporation Compliant with the ACPI 5.0 Specification

DSDT info for update image (DSDT.AM) Size of image: 116568 OEM id.......: MSFTVM OEM Table id.: MSFTVM03 OEM revision.: 00000003 Deleting value 00000000 Deleting value 00000001 Deleting value 00000002 Deleting value 00000003 Deleting value 00000004 Deleting value 00000005 Deleting value 00000006 Deleting value 00000007 Deleting value 00000008 Deleting value 00000009 Deleting value 0000000a Deleting value 0000000b Deleting value 0000000c Deleting value 0000000d Deleting value 0000000e Deleting value 0000000f Deleting value 00000010 Deleting value Action SetValue 00000000 SetValue 00000001 SetValue 00000002 SetValue 00000003 SetValue 00000004 SetValue 00000005 SetValue 00000006 SetValue 00000007 SetValue 00000008 SetValue 00000009 SetValue 0000000a SetValue 0000000b SetValue 0000000c SetValue 0000000d SetValue 0000000e SetValue 0000000f SetValue 00000010 SetValue Action Registry path: System\CurrentControlSet\Services\ACPI\Parameters\DSDT\MSFTVM\MSFTVM03\00000003 Table overloading succeeded. This will only be active when testsigning is enabled.

BelleNottelling commented 5 years ago

Hey @realitycheckrose When I try and compile the driver I don't get rosumd.dll Where are you getting it?