[ofw] Loading Ibbus.sys

[Fab Tillier]

Sophia Germans wrote on Thu, 4 Mar 2010 at 12:09:19

> I am trying to load ibbus.sys for a physical hardware device, built
> privately. I am already in testmode to load our HCA host driver which
> has a test signature. But I understand that, since we don't install
> drivers from a single package, we cannot use the same test signature
> for ib stack.

Why aren't you building the whole stack yourself?  Ibbus should be listed in your INF file as an upper filter for your HCA driver.

> Did you encounter any specific problem using
> IoRegisterPlugplaynotification  that made you to move to a new
> registration mechanism via IRP_MN_QUERY_INTERFACE (rdma verbs guid
> interface) ?

There used to be a virtual device for ibbus, but it created difficult to manage dependencies between the HCA device node and the ibbus device node - you'd have device A (ibbus) creating child devices for device B (HCA), that device B then reports to the system.  Having ibbus as an upper filter, especially since it creates child device nodes for the HCA, makes much more sense.

-Fab

> 
> Thanks very much
> Sophia.
> 
> 
> 
> -----Original Message-----
> From: Fab Tillier [mailto:ftillier at microsoft.com]
> Sent: Thursday, February 25, 2010 4:27 PM
> To: Sophia Germans; ofw at lists.openfabrics.org
> Subject: RE: Loading Ibbus.sys
> 
> Sophia Germans wrote on Thu, 25 Feb 2010 at 15:44:00
> 
>> Hi,
>> 
>> When I install free build of  ibbus.sys  via hardware wizard routine
>> using the driver installation file ibbus.inf, the driver fails to load
>> without a kernel debugger connected to it.
> 
> Are you trying to install ibbus.sys for a virtual device, or are you
> installing in response to a PnP enumeration of a physical HW device?
> 
>> I get an error message saying that system needs to be restarted. Unless
>> there is a debugger attached to the target,ibbus.sys fails to load. But
>> I see no assert statements / error messages while the driver gets
>> loaded.  I would much appreciate if any one can help me to understand /
>> work around this issue.
> 
> Are you loading a driver you built yourself?  If so, look at the WDK
> documentation about test signing drivers, including how to put the
> system into test mode so that test signed drivers will load.
> 
> -Fab