X-Spam-Check-By: sourceware.org Date: Fri, 23 Mar 2007 15:18:24 +0100 (CET) From: Ton van Overbeek To: cygwin AT cygwin DOT com cc: samuel DOT thibault AT ens-lyon DOT org Subject: Libusb-win32-0.1.12.1-1 makes system unusable after reboot. Message-ID: <20070323150454.V88283-100000@xs2.xs4all.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I have problems with the libusb-win32-0.1.12.1-1 Cygwin package. Installation went fine. After running /usr/sbin/libusb-install the test program worked OK and also my own libusb based program worked fine. The real problem started after the following reboot. The /usr/sbin/libusb-install installs the usb filter driver. This filter is inserted in the drivers for all possible device classes. At the following reboot the loading of all device drivers in these classes failed, with as a consequence that none of these devices were working. On my XP/SP2 system these classes were: - Universal Serial Bus Controllers - Sound, video and game controllers - Modems - Network adapters - Smart card readers - Imaging devices - Human Interface Devices - Palm OS Handheld Devices - Bluetooth Devices - Portable Devices This is pretty disastrous: no network, no sound, no ... The original non-Cygwin package from SourceForge does not have the problem. It installs the filter driver in c:\windows\system32\drivers\libusb0.sys and the dll in c:\windows\system32\libusb0.dll. The Cygwin package installs the dll in /usr/bin/cygusb0.dll and the filter driver in /usr/lib/libusb/libusb0.sys. Installing the SourceForge package after the Cygwin package also solves the problem, i.e. combining cygusb0.dll and c:\windows\system32\drivers\libusb0.sys works OK. My guess is that /usr/sbin/libusb-install omits some crucial step (registry? kernel service?) which makes device driver loading at boot fail. I checked the failures by enabling boot logging and inspecting c:\windows\ntbtlog.txt. All the devices show up with yellow exclamation marks in the device manager. I am not a windows driver expert, so for now I cannot use the Cygwin package. Ton van Overbeek -- 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/