From owner-freebsd-questions@FreeBSD.ORG Fri Mar 26 21:32:42 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B259C1065670 for ; Fri, 26 Mar 2010 21:32:42 +0000 (UTC) (envelope-from aimass@yabarana.com) Received: from mail-qy0-f200.google.com (mail-qy0-f200.google.com [209.85.221.200]) by mx1.freebsd.org (Postfix) with ESMTP id 537818FC1B for ; Fri, 26 Mar 2010 21:32:41 +0000 (UTC) Received: by qyk38 with SMTP id 38so2166308qyk.9 for ; Fri, 26 Mar 2010 14:32:41 -0700 (PDT) MIME-Version: 1.0 Sender: aimass@yabarana.com Received: by 10.229.98.138 with HTTP; Fri, 26 Mar 2010 14:32:41 -0700 (PDT) Date: Fri, 26 Mar 2010 17:02:41 -0430 X-Google-Sender-Auth: 0f7ed3fc9a759633 Received: by 10.229.222.14 with SMTP id ie14mr480810qcb.95.1269639161416; Fri, 26 Mar 2010 14:32:41 -0700 (PDT) Message-ID: From: Alejandro Imass To: FreeBSD Questions Content-Type: text/plain; charset=ISO-8859-1 Subject: xptioctl pass driver usb scsi driver problem (solved) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Mar 2010 21:32:42 -0000 Hello, Just wanted to share with the list that I solved this problem today, and looking at the recent archives this has come up recently without any solutions so here it is. FYI, there was an answer by Andrew Thompson in the thread "USB2 vs SCSI pass-through?" of Feb 25th 2010 which hinted at the solution but the OP never manifested if he had actually solved the problem. If you get this in dmesg when you plug in your usb mass storage device: xptioctl: pass driver is not in the kernel xptioctl: put "device pass" in your kernel config file It probably means that HAL (you are probably running Gnome) has interfered with the assigning if dev by the kernel. All you have to do is disable hal for a moment, unplug and replug and voila! it' s fixed. Then you safely start HAL back up again. There is no doubt, a better solution, like fixing the root of the HAL problem but this simple workaround will avoid ruining your day. 1) /usr/local/etc/rc.d/hald stop 2) unplug and re-plug the device 3) dmesg, camcontrol, mount, etc. 4) /usr/local/etc/rc.d/hald stop Best, Alejandro Imass