X-Spam-Check-By: sourceware.org
Date: Sat, 24 Mar 2007 20:13:21 +0100 (CET)
From: Ton van Overbeek <ton AT v-overbeek DOT nl>
To: Samuel Thibault <samuel DOT thibault AT ens-lyon DOT org>
cc: cygwin AT cygwin DOT com
Subject: Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
In-Reply-To: <20070324151544.GA3541@interface.famille.thibault.fr>
Message-ID: <20070324200659.X11058-100000@xs2.xs4all.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by delorie.com id l2OJDYgK012471

On Sat, 24 Mar 2007, Samuel Thibault wrote:
> Hi,
>
> Ton van Overbeek, le Sat 24 Mar 2007 04:06:09 +0100, a écrit :
> > I believe I found the cause of the problem.
> > When running cygcheck on /usr/lib/libusb/libusb0.sys I get this:
> >
> > $ cygcheck /usr/lib/libusb/libusb0.sys
> > c:/Cygwin/lib/libusb/libusb0.sys
> > Error: could not find usbd.sys <---- !!!!
>
> Well, this happens with the old version too. But in the new version,
> libusb0.sys is started differently from the old version, that possibly
> makes the windows-provided usbd.sys discovery fail.
>

You are right. I get the same cygcheck output with the old version.

> > Somehow the Cygwin libusb0.sys must link to usbd.sys with the full path
> > i.e. c:\windows\system32\drivers\usbd.sys instead of assuming that
> > usbd.sys is located in the same directory as libusb0.sys.
>
> Err, no, usbd.sys is always installed in
> c:\windows\system32\drivers\usbd.sys, and that's precisely because
> libusb0.sys is not installed there too that the usual discovery fails.
>

Yes, I know. But copying usbd.sys to /usr/lib/libusb makes the problem
go away. At the next boot loading of libusb0.sys succeeds. See excerpt
from ntbtlog.txt below:
--------------------------------
....
Loaded driver btkrnl.sys
Loaded driver agp440.sys
Loaded driver \SystemRoot\System32\DRIVERS\intelppm.sys
Loaded driver \SystemRoot\System32\DRIVERS\CmBatt.sys
Loaded driver \SystemRoot\System32\DRIVERS\nv4_mini.sys
Loaded driver \SystemRoot\System32\DRIVERS\usbuhci.sys
Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys
Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys
Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys
Loaded driver \SystemRoot\System32\DRIVERS\usbehci.sys
Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys
Loaded driver \SystemRoot\System32\DRIVERS\b57xp32.sys
Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys
Loaded driver \SystemRoot\System32\DRIVERS\gticard.sys
Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys
Loaded driver \SystemRoot\system32\drivers\tiumfwl.sys
Loaded driver \SystemRoot\System32\DRIVERS\bcmwl5.sys
Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys
Loaded driver \SystemRoot\System32\DRIVERS\i8042prt.sys
Loaded driver \SystemRoot\System32\DRIVERS\Apfiltr.sys
Loaded driver \SystemRoot\System32\DRIVERS\mouclass.sys
....
--------------------------------
> Actually, I'm wondering: instead of trying to make libusb0.sys work
> from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in
> libusb-install, to just copy it into c:\windows\system32\drivers\ and
> then use the usual libusb-win32 filter setup?  That works fine and
> actually makes the patch simpler...
>

I am pretty sure that would solve the problem.

Ton


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/