From owner-freebsd-usb@FreeBSD.ORG Tue Feb 1 12:03:14 2005 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF14116A4CE for ; Tue, 1 Feb 2005 12:03:14 +0000 (GMT) Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C8A943D46 for ; Tue, 1 Feb 2005 12:03:14 +0000 (GMT) (envelope-from euro@i.com.ua) Message-ID: <003e01c50856$07165180$0cae9f83@beast1000> From: "Eugene Rogoza" To: Date: Tue, 1 Feb 2005 13:03:22 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: by amavisd-new/sophie/sophos at mailrelay1.informatik.tu-muenchen.de Subject: USB does not recognize any dynamically plugged devices X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Feb 2005 12:03:14 -0000 Hello everybody, I have a FreeBSD 5.3 release on my 855GM-based Dell Inspiron 700m laptop. There's a strange glitch: connected USB devices are being recognized and attached only at startup (just after bus probing). If I disconnect a device, the kernel says "detached", and everything is fine. But if I try to attach it again, nothing happens. This behavior started after I connected and disconnected an Olympus digital camera. After I plugged it in, it was correctly recognized and attached (umass0). But I realized that I had forgotten to include "device da" in my kernel to be able to access camera's memory. I compiled a new kernel, which differs from the previous one only by this "device da" string. Since then USB doesn't detect any devices plugged at run-time. Trying to boot with older kernels (and even with GENERIC) doesn't change the situation. Any helpful thoughts are being appreciated. Eugene Rogoza.