Re: Problem with KMDF 1.1 driver installation

Does your INF file install more than one driver? i.e does it install a FDO
and a fileter driver? If so, you will see a problem upgrading from KMDF 1.0
to KMDF 1.1. The reason is that it installs the upgrade for the lower river
in the stack and then when it does the higher driver, it checks for an
upgrade, finds the current WDF file to be 1.1 already and says it can't
upgrade it. If you reboot at this point and do the upgrade again, it will
work.

Alternatively, I was told that you can tell it to use 1.1 for only the
lowest driver in the stack. the right version will get installed and it will
be used for both drivers. I havent' ried this because it feels like lying to
the OS and I'm afraid I'll get bitten by it later.

Beverly

"Gennady Mayko" <GMayko@xxxxxxxxx> wrote in message
news:1152529787.598198.91580@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,

I have a KMDF 1.0 driver that I can successfully install for my board.
I decided to move to the KMDF 1.1 and face some problems during it's
installation.

I change information in my *.inf file to use WdfCoInstaller01001.dll
and also change the version in the [*_WdfSelect] section to 1.1:
---
[*_WdfSect]
KmdfLibraryVersion = 1.1
---

During installation of the driver I got an error 39 and found the
following line in the setuapi.log file:
---
@ 12:02:02.281 #I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
---

I remembered that somehow Doron Holon explained the process KMDF driver
installation and binding with the proper WDF version using 2 drivers
(wdfldr.sys and wdfXXYYY.sys). I copied them from the
Kmdf11\bin\debug\x86 directory and after this I have error 37 and this
line in the setupapi.log:
---
@ 13:34:47.328 #I163 Device not started: Device has problem: 0x25:
CM_PROB_FAILED_DRIVER_ENTRY.
---
and also the following lines in the debug output:
---
WdfLdr: DllInitialize: enter
WdfLdr: DllInitialize: OsVersion(5.1)
WdfLdr: DllInitialize: exit
WdfLdr: WdfVersionBind: enter
WdfLdr: Component path
\Registry\Machine\System\CurrentControlSet\Control\Wdf\Kmdf\KmdfLibrary\Versions
WdfLdr: ZwOpenKey(1) failed: C0000034
WdfLdr: GetVersionServicePath() failed: C0000034
WdfLdr: WdfVersionBind: exit C0000034
---
As far as I understand, now wdfldr is started and trying to get the
version of the WDF and failed (error 0xC0000034 is probably
STATUS_OBJECT_NAME_NOT_FOUND).

I do find this registry key but in my case it is empty. So my questions
are:

1. Who is responsible for this registry key initialization?

2. What is the format of this key for the WDF 1.1 version?

3. Is it wdfldr.sys which looks for the KmdfLibraryVersion entry in the
*.inf file to bind to the correct version of the KMDF library?

4. In the WDF 1.1 we still have wdf01000.sys - is it OK?

Regards,
Gennady Mayko.



.

Relevant Pages

  • Re: XPSP2 Load Experience
    ... Problems with install, with workarounds. ... and did an in-place upgrade from XP SP1 to ... Unfortunately, the Recovery Console ... the driver in question was the Intel I845G video ...
    (NT-Bugtraq)
  • Re: [SLE] Problem-Disappearing Icons & Menus in OpenOffice 2 & SuSE 10.1
    ... Have you recently installed new video drivers? ... The only hitch is that you have to reinstall the driver if you ... upgrade the kernel. ... If you did a software update install from 10.0 to 10.1, ...
    (SuSE)
  • Re: Installation problem, keyboard & mouse disabled
    ... Now I'm having a problem after the upgrade. ... option that usually causes the USB keyboard and USB mouse not to work. ... This behavior can prevent Setup from completing: if Setup tries to install ... unsigned driver, an Unsigned Driver dialog box appears and requires user ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: flakey mouse problems
    ... upgrade, incidently, the mouse is fine in this ... If there was someway that I knew the exact driver required for this ... knew exactly how to install it...or it's path...I could probably tweak ...
    (Fedora)
  • Re: WDF Class Filter Driver Installation
    ... I've installed the driver as a boot time ... WdfLdr: DllInitialize - OsVersion ... It seems that making the driver an upper filter of the System Setup ... what right clicking on the inf file -> Install would do for non-Wdf ...
    (microsoft.public.development.device.drivers)