getting graphics driver to install properly #66
Comments
|
I posted on MSDN and someone replied that maybe there is a problem with updating the ASL. Here is my followup: DSDT info for update image (DSDT.AM) |
|
Hey @realitycheckrose When I try and compile the driver I don't get rosumd.dll |
|
I'd like to know what this error is about, because even when I compile without changing DSDT.ASL I still get this problem, and I strongly suspect that it's the asl version that's too high! DSDT.ASL: |
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:
0b51c4f#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
The text was updated successfully, but these errors were encountered: