[wdmaudiodev] Re: Indicates two revision levels are incompatible (USB inbox driver + custom APO)

  • From: "Matthew van Eerde" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "Matthew.van.Eerde" for DMARC)
  • To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Thu, 8 Aug 2019 18:18:57 +0000

USB Audio 2.0 devices have one of the following compatible IDs:
USB\Class_01&SubClass_00&Prot_20
USB\Class_01&SubClass_01&Prot_20
USB\Class_01&SubClass_02&Prot_20

The Prot_20 part is what marks it as USB Audio 2.0.

USB Audio 1.0 devices have the USB\Class_01 compat ID, but not any of the USB 
Audio 2.0 devices.

If you try to force the USB Audio 1.0 driver onto a USB Audio 2.0 device, or 
vice versa, it won’t work.

So if you want your APO to be loaded on a USB Audio 1.0 device, you will need 
to wrap wdma_usb.inf; if you want your APO to be loaded on a USB Audio 2.0 
device, you will need to wrap usbaudio2.inf.

________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on 
behalf of Edward Abramian <edwabr123@xxxxxxxxx>
Sent: Thursday, August 8, 2019 11:10:46 AM
To: wdmaudiodev@xxxxxxxxxxxxx <wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: Indicates two revision levels are incompatible (USB 
inbox driver + custom APO)

I only install APO. I believe that the problem is that this device is USB 2.0 
since in Events tabs in its properties it mentions usbaudio2.inf.

From: wdmaudiodev-bounce@xxxxxxxxxxxxx 
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Matthew van Eerde ;
(Redacted sender "Matthew.van.Eerde" for DMARC)
Sent: Thursday, August 8, 2019 10:56 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Indicates two revision levels are incompatible (USB 
inbox driver + custom APO)

This will grab logs: 
https://matthewvaneerde.wordpress.com/2016/09/26/report-problems-with-logs-and-suggest-features-with-the-feedback-hub/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatthewvaneerde.wordpress.com%2F2016%2F09%2F26%2Freport-problems-with-logs-and-suggest-features-with-the-feedback-hub%2F&data=02%7C01%7CMatthew.van.Eerde%40microsoft.com%7C60ed0a1f21cb430d285f08d71c2bcca1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637008846807973758&sdata=YoGm%2FiJn2UT%2BXMy63kpRa4r%2FWYEdStzX27Z1b39TByQ%3D&reserved=0>

We publish symbols for usbaudio2.sys, but not for usbaudio.sys, so you won’t be 
able to read the logs yourself.

Does your driver add anything else besides APOs? For example, do you have a 
filter driver? I don’t see how an APO could cause a CM_PROB_FAILED_START error 
in usbaudio.sys.

________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx
<wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on 
behalf of Edward Abramian <edwabr123@xxxxxxxxx<mailto:edwabr123@xxxxxxxxx>>
Sent: Thursday, August 8, 2019 10:48:27 AM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx
<wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>>
Subject: [wdmaudiodev] Re: Indicates two revision levels are incompatible (USB 
inbox driver + custom APO)

I am wrapping wdma_usb.inf. Where should I look for the logs?

From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Matthew van Eerde ;
(Redacted sender "Matthew.van.Eerde" for DMARC)
Sent: Thursday, August 8, 2019 9:20 AM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: Indicates two revision levels are incompatible (USB 
inbox driver + custom APO)

The “code X” values reported in device manager are documented in the cfg.h 
header file in the SDK and WDK.

Code 10 = 0xa is CM_PROB_FAILED_START: 
https://docs.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-failed-start<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Finstall%2Fcm-prob-failed-start&data=02%7C01%7CMatthew.van.Eerde%40microsoft.com%7C60ed0a1f21cb430d285f08d71c2bcca1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637008846807973758&sdata=e8pXJMTqqhP3cGVU%2BHRgVme6M91u1WziX1pz8Ye7FcE%3D&reserved=0>

This means that the driver loaded successfully, but IRP_MN_START_DEVICE failed. 
Grabbing logs for the particular USB inbox driver in question should help 
determine why. Are you wrapping wdma_usb.inf or usbaudio2.inf?

________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx
<wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on 
behalf of Edward Abramian <edwabr123@xxxxxxxxx<mailto:edwabr123@xxxxxxxxx>>
Sent: Thursday, August 8, 2019 12:44:32 AM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx
<wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>>
Subject: [wdmaudiodev] Indicates two revision levels are incompatible (USB 
inbox driver + custom APO)

Hi,

I have an .inf APO package that installs over Windows USB inbox driver. It 
works great with several USB headsets but causes a trouble with one. Windows 
will report the following issue and I am struggling to figure out what it means.

This device cannot start. (Code 10)
Indicates two revision levels are incompatible.

I hope someone points to the right direction.

Thanks,
Edward

Other related posts: