From owner-freebsd-current@FreeBSD.ORG Mon Feb 16 18:41:21 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A6491065676; Mon, 16 Feb 2009 18:41:21 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id DE5EA8FC4E; Mon, 16 Feb 2009 18:41:19 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by yw-out-2324.google.com with SMTP id 2so1117859ywt.13 for ; Mon, 16 Feb 2009 10:41:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=7gDw1X/tFo4Xs/UJTH6Lc26C2JnyK5HpP/Mu4I5zpBc=; b=ssAEVDld+GA+g8pf7ZsIfPZ4wZvZtGmuSm8U2Cfn5KBZXY9ma/YDDrt4bs7+udgAf9 sDuidWh7WyiOEMBW0gffy4RfT5E3r3JTzfhElFun7lJkndLbDYBDWzb9AgGYkf8c7gDu gZ4qla0NxgO6xyuY7E8kG32wv5jzOrWiUGauE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=wHQDwURDDhD1Fz6vOrnjB1nVaooz+Sq3AJhSmtTPqa/xM1PNZrTcxkYjZ8rgVacLrm 0o+5M/xitosqgIH9LGi1u2JX5hPWOes4LqOYQ8Iq9HVTzBouHrs2TcRD17nj7nie8Mq+ bIiGvWygjdVunODB8N1nzHacxOxMqJSraH0IM= MIME-Version: 1.0 Received: by 10.151.44.14 with SMTP id w14mr366750ybj.111.1234809679385; Mon, 16 Feb 2009 10:41:19 -0800 (PST) In-Reply-To: <200902161930.25235.hselasky@freebsd.org> References: <87mycme9wc.fsf@kobe.laptop> <200902161752.56998.hselasky@freebsd.org> <87wsbqmeq4.fsf@kobe.laptop> <200902161930.25235.hselasky@freebsd.org> Date: Mon, 16 Feb 2009 10:41:19 -0800 Message-ID: From: Maksim Yevmenkin To: Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Giorgos Keramidas , Andrew Thompson Subject: Re: usb2 moused issue X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 18:41:22 -0000 On Mon, Feb 16, 2009 at 10:30 AM, Hans Petter Selasky wrote: > On Monday 16 February 2009, Giorgos Keramidas wrote: >> On Mon, 16 Feb 2009 17:52:56 +0100, Hans Petter Selasky > wrote: >> > On Monday 16 February 2009, Giorgos Keramidas wrote: >> >> I just rebuild my kernel after flipping the switch to usb2 in my kernel >> >> config file: >> >> >> >> >> >> [ dmesg output with hw.usb2.ums.debug=1 ] >> >> Feb 16 16:19:00 kobe kernel: ugen4.2: at usbus4 >> >> Feb 16 16:19:00 kobe kernel: ums0: > >> 3000 (Model 1056), class 0/0, rev 2.00/0.07, addr 2> on usbus4 Feb 16 >> >> 16:19:00 kobe kernel: ums0: 5 buttons and [XYZ] coordinates Feb 16 >> >> 16:19:00 kobe kernel: ums_attach:582: sc=0xc63c7000 >> > >> > If you "cat /dev/ums0" while having the debugging on, do you see >> > anything? >> >> Hmm, there's a dmesg line saying that: >> >> Feb 16 20:09:51 kobe kernel: Symlink: ums0 -> usb4.2.0.16 >> >> but there is no ums0 symlink in /dev: >> >> # ls -ld ums* >> ls: ums*: No such file or directory >> # > > Hi, > > The device is invisible. You should be able to cat it, if it's not already > opened. yeah, i've been bitten by the same "invisible device node" problem while converting ubtbcmfw(4) to usb2. for example, Feb 16 10:35:19 yak kernel: ugen0.2: at usbus0 Feb 16 10:35:19 yak kernel: ubtbcmfw0: on usbus0 Feb 16 10:35:19 yak kernel: Symlink: ubtbcmfw0 -> usb0.2.0.16 Feb 16 10:35:19 yak kernel: Symlink: ubtbcmfw0.1 -> usb0.2.0.16 Feb 16 10:35:19 yak kernel: Symlink: ubtbcmfw0.2 -> usb0.2.0.16 and > pwd /dev > ls -la usb0.2.* ls: No match. > ls -la usb0.2.0.16 crwxrwxrwx 1 root operator 0, 68 Feb 5 10:19 usb0.2.0.16 > ls -la ubtbcmfw* ls: No match. > ls -la ubtbcmfw0 crwxrwxrwx 1 root operator 0, 68 Feb 5 10:19 ubtbcmfw0 > ls -la ubtbcmfw0.* ls: No match. > ls -la ubtbcmfw0.1 crwxrwxrwx 1 root operator 0, 68 Feb 5 10:19 ubtbcmfw0.1 > ls -la ubtbcmfw0.2 crwxrwxrwx 1 root operator 0, 68 Feb 5 10:19 ubtbcmfw0.2 i suspect it probably has something to do with the way devfs cloning works (for example, i think, somewhat similar problem exists with /dev/tap, /dev/tun device nodes). of course, if one does not know that, the first reaction would be - wtf? where is my device nodes?! :) i wonder if there is any way to "fix" it... thanks, max